From pinedev@shiva0.cac.washington.edu Tue Jun 1 05:36:18 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 1 Jun 1999 05:36:17 -0700 (PDT) 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 FAA11387 for ; Tue, 1 Jun 1999 05:36:16 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA27814; Tue, 1 Jun 1999 05:36:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA05650; Tue, 1 Jun 1999 05:35:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA37770 for ; Tue, 1 Jun 1999 05:29:59 -0700 Received: from pantheon-po01.its.yale.edu (pantheon-po01.its.yale.edu [130.132.143.32]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA10216 for ; Tue, 1 Jun 1999 05:29:59 -0700 Received: from minerva.cis.yale.edu (amj9@minerva.cis.yale.edu [130.132.143.250]) by pantheon-po01.its.yale.edu (8.8.8/8.8.8) with ESMTP id IAA23894 for ; Tue, 1 Jun 1999 08:29:57 -0400 (EDT) Received: from localhost (amj9@localhost) by minerva.cis.yale.edu (8.8.8/8.8.8) with SMTP id IAA19828 for ; Tue, 1 Jun 1999 08:29:56 -0400 (EDT) Message-Id: Date: Tue, 1 Jun 1999 08:29:56 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Aubrey Jennings To: Pine Discussion Forum Subject: Finger MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: minerva.cis.yale.edu: amj9 owned process doing -bs X-Sender: amj9@minerva.cis.yale.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a way for me to tell if someone has fingered me? -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Wed Jun 2 09:38:24 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 2 Jun 1999 09:38:24 -0700 (PDT) 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 JAA00974 for ; Wed, 2 Jun 1999 09:38:23 -0700 (PDT) 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 JAA28675; Wed, 2 Jun 1999 09:38:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA02536; Wed, 2 Jun 1999 09:37:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17160 for ; Wed, 2 Jun 1999 09:31:33 -0700 Received: from niwot.scd.ucar.edu (niwot.scd.ucar.edu [128.117.8.223]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA04451 for ; Wed, 2 Jun 1999 09:31:32 -0700 Received: from sedona.scd.ucar.edu (sedona.scd.ucar.edu [128.117.8.183]) by niwot.scd.ucar.edu (8.9.1a/8.9.1) with ESMTP id KAA28378; Wed, 2 Jun 1999 10:35:04 -0600 (MDT) Received: from localhost (era@localhost) by sedona.scd.ucar.edu (8.9.1b+Sun/8.8.0) with ESMTP id KAA09635; Wed, 2 Jun 1999 10:31:31 -0600 (MDT) Message-Id: Date: Wed, 2 Jun 1999 10:31:31 -0600 (MDT) Reply-To: era@ucar.edu Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ed Arnold To: Pine Discussion Forum Subject: Re: Request: Replying to self In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-To: Nancy McGough X-Cc: Pine Discussion Forum X-Authentication-Warning: sedona.scd.ucar.edu: era owned process doing -bs X-Sender: era@sedona.scd.ucar.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'd suggest that you include "To", "Cc", and "Bcc" in your "default-composer-hdrs" variable. This way, Pine will display all destinations so you're sure you get what you want. May also prevent political discomfort. :-) > Sorry about that test message I just sent to the list. I was trying > to send a test message to myself and so I just typed R for reply to a > message I had sent. Pine Developers: *PLEASE* ask the user if she wants > to reply to the addresses on the From, To, or Cc lines. It is not > intuitive to have a reply go to the address in the To header. >=20 > Thank you, >=20 > --=20 > For Pine info & links, see www.ii.com/internet/messaging/pine/ > =20 > =A9Nancy McGough http://www.ii.com Infinite Ink > --=3D Sent via PINE: Power Internet News & Email for Win/Unix =3D-- >=20 > --=20 > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see:=20 > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Wed Jun 2 21:20:16 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 2 Jun 1999 21:20:16 -0700 (PDT) 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 VAA03114 for ; Wed, 2 Jun 1999 21:20:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA12900; Wed, 2 Jun 1999 21:20:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA13870; Wed, 2 Jun 1999 21:19:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA44006 for ; Wed, 2 Jun 1999 21:15:10 -0700 Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA24786 for ; Wed, 2 Jun 1999 21:15:09 -0700 Received: from luomat.peak.org [207.141.129.168] by 1stpc.org with ESMTP (SMTPD32-4.04) id A108BDD3017A; Thu, 03 Jun 1999 00:14:00 EST Received: by luomat.peak.org (8.9.3/8.9.0) id AAA00635; Thu, 3 Jun 1999 00:14:56 -0400 (EDT) Message-Id: <199906030414.AAA00635@ocalhost> Date: Thu, 3 Jun 1999 00:14:53 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Finger In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Aubrey Jennings X-Cc: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Replying to message of Tue, 1 Jun 1999 08:29:56 -0400 (EDT) from Aubrey Jennings regarding ``Finger'' > Is there a way for me to tell if someone has fingered me? Wow, this is the most wildly offtopic post in quite some time... exactly what led you to post this to the PINE newsgroup? You might be able to find the answer in the FAQ for comp.unix.questions TjL From pinedev@shiva0.cac.washington.edu Wed Jun 2 22:59:04 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 2 Jun 1999 22:59:04 -0700 (PDT) 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 WAA25091 for ; Wed, 2 Jun 1999 22:59:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA14272; Wed, 2 Jun 1999 22:59:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA07307; Wed, 2 Jun 1999 22:58:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA31326 for ; Wed, 2 Jun 1999 22:53:16 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA03968 for ; Wed, 2 Jun 1999 22:53:16 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA20651; Thu, 3 Jun 1999 05:57:43 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 2 Jun 99 22:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA00973; Wed, 2 Jun 1999 22:49:34 -0700 Message-Id: Date: Wed, 2 Jun 1999 22:49:32 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Finger In-Reply-To: <199906030414.AAA00635@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 -- ListProcessor(tm) by CREN On Thu, 3 Jun 1999, Timothy J Luoma wrote: > Replying to message of Tue, 1 Jun 1999 08:29:56 -0400 (EDT) > from Aubrey Jennings > regarding ``Finger'' > > > Is there a way for me to tell if someone has fingered me? > > Wow, this is the most wildly offtopic post in quite some time... exactly > what led you to post this to the PINE newsgroup? I thought so too, I didn't bother replying... > You might be able to find the answer in the FAQ for comp.unix.questions I'm pretty sure the answer is in there, and I know the answer is yes. Just how, I don't know... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: From pinedev@shiva0.cac.washington.edu Fri Jun 4 13:34:48 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 4 Jun 1999 13:34:48 -0700 (PDT) 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 NAA30625 for ; Fri, 4 Jun 1999 13:34:47 -0700 (PDT) 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 NAA26361; Fri, 4 Jun 1999 13:34:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA15385; Fri, 4 Jun 1999 13:34:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA27688 for ; Fri, 4 Jun 1999 13:28:31 -0700 Received: from rwja.UMDNJ.EDU (root@rwja.UMDNJ.EDU [130.219.4.100]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA16675 for ; Fri, 4 Jun 1999 13:28:30 -0700 Received: from localhost (green@localhost [127.0.0.1]) by rwja.UMDNJ.EDU (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA27492 for ; Fri, 4 Jun 1999 16:28:29 -0400 (EDT) Message-Id: Date: Fri, 4 Jun 1999 16:28:29 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Cliff Green To: Pine Discussion Forum Subject: List mode MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN There's a "List mode" option when selecting addressees from a pine addressbook (local or global), and there's a "List mode" when selecting from several newsgroups to subscribe to. Will there ever be a "List mode" from an ldap search (assuming one has ldap support compiled in)? This would be helpful in building aliases in one's own addressbook, and would also make it possible to drop managing both a globaladdressbook and a directory service (let's skip the discussion of whether this is a Good Idea or not). c -- Clifford Green Internet - green@umdnj.edu Academic Computing Services voice - 732-235-5250 UMDNJ-IST fax - 732-235-5252 Exercise caution in your business affairs; for the world is full of trickery. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sat Jun 5 05:20:11 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 5 Jun 1999 05:20:11 -0700 (PDT) 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 FAA12296 for ; Sat, 5 Jun 1999 05:20:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA09321; Sat, 5 Jun 1999 05:20:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA15544; Sat, 5 Jun 1999 05:19:40 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA35354 for ; Sat, 5 Jun 1999 05:13:57 -0700 Received: from nyntq1.tink.com (SYSTEM@mail2.new-york.net [165.254.101.54]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA19668 for ; Sat, 5 Jun 1999 05:13:57 -0700 Received: from aleph.ii.com ("port 1146"@aleph.ii.com) by mail2.new-york.net (PMDF V5.1-10 #22883) with ESMTP id <01JC18XRE5DA8X0NJA@mail2.new-york.net> for pine-info@u.washington.edu; Sat, 5 Jun 1999 08:13:51 EDT Message-Id: Date: Sat, 05 Jun 1999 08:14:18 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nancy McGough To: Pine Discussion Forum Subject: Request: showing flags in message text window MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: nm@operamail.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I am viewing the text of a message it would be great if the title line at the top told me what flags were set for that message. So, for example, instead of this: PINE 4.10 MESSAGE TEXT Message 45 of 45 60% It said something like this: PINE 4.10 MESSAGE TEXT Message 45 of 45 *AD 60% The *AD tells me that I've flagged it important, I've answered it, and I've marked it for deletion. Thanks for considering this! 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 =-- -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sat Jun 5 17:47:14 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 5 Jun 1999 17:47:14 -0700 (PDT) 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 RAA18583 for ; Sat, 5 Jun 1999 17:47:13 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA11627; Sat, 5 Jun 1999 17:47:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA26553; Sat, 5 Jun 1999 17:46:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA51554 for ; Sat, 5 Jun 1999 17:41:04 -0700 Received: from ambr.mtholyoke.edu (ambr.mtholyoke.edu [138.110.1.10]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA21621 for ; Sat, 5 Jun 1999 17:41:03 -0700 Received: from mhc.mtholyoke.edu (mhc.mtholyoke.edu [138.110.1.1]) by ambr.mtholyoke.edu (8.9.1/v990319-1150) with ESMTP id UAA03300 for ; Sat, 5 Jun 1999 20:41:03 -0400 (EDT) Received: from localhost (mcrowley@localhost) by mhc.mtholyoke.edu (8.7.3/v990531-1235) with ESMTP id UAA04351; Sat, 5 Jun 1999 20:41:02 -0400 (EDT) Message-Id: Date: Sat, 5 Jun 1999 20:41:02 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Michael A Crowley To: Pine Discussion Forum Subject: 4.10 vs 3.96 newsreading performance In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: mcrowley@mhc.mtholyoke.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Comparing 3.96 to 4.10 when reading news via nntp, I'm finding pine 4.10 often takes 2 to 7 times longer. This includes both the initial opening and the time to jump from, say, the last message to the first. I've searched the pine-info list for any mention of this without success for any mention of this and so am wondering if others had experienced this also. I've tried toggling news-approximates-new-status and news-read-in-newsrc-order without any change. Here are some conditions: With a particularly nasty .newsrc entry: 1-4544,4546-4994,4996-4998,5003-5028,5030-5056,5060-5065,5067-5076,5081-5098,5100-5101,5103-5119,5121-5134,5136-5148,5157,5159-5160,5162-5200,5204,5215,5217-5233,5235-5239,5242-5252,5254-5290,5293-5294,5296-5318,5321-5339,5342-5373,5375-5384,5386-5400,5402-5404,5406-5407,5412-5427,5430-5449,5452-5457,5459-5468,5470-5485 the factor was about 7. Deleting all of the numbers for that newsgroup made 4.10 faster but 3.96 was still 2 times as fast. Marking just the last message as "read" (delete) so the .newsrc entry for that newsgroup read: 1-4427,5485 resulted in identical performance between 3.96 and 4.10. I'm wondering if this is an identified performance problem or am I missing some setting that should be changed. -mike ------------------------------------------------------------------------------ Michael A. Crowley Director of Networking mcrowley@mtholyoke.edu 216 Dwight Hall, Mount Holyoke College 413-538-2140 fax: 413-538-2331 South Hadley, MA 01075-6415 http://www.mtholyoke.edu/~mcrowley http://www.mtholyoke.edu/lits/network ------------------------------------------------------------------------------ -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sat Jun 5 23:37:50 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 5 Jun 1999 23:37:50 -0700 (PDT) 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 XAA15432 for ; Sat, 5 Jun 1999 23:37:47 -0700 (PDT) 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 XAA15826; Sat, 5 Jun 1999 23:37:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA06321; Sat, 5 Jun 1999 23:37:12 -0700 Received: from jason01.u.washington.edu (root@jason01.u.washington.edu [140.142.70.24]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA17498 for ; Sat, 5 Jun 1999 23:32:26 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA08982; Sat, 5 Jun 1999 23:32:25 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA10818; Sat, 5 Jun 1999 23:32:24 -0700 Message-Id: Date: Sat, 5 Jun 1999 23:32:24 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window 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 -- ListProcessor(tm) by CREN On Sat, 5 Jun 1999, Nancy McGough wrote: > When I am viewing the text of a message it would be great if the title > line at the top told me what flags were set for that message. So, for > example, instead of this: > > PINE 4.10 MESSAGE TEXT Message 45 of 45 60% > > It said something like this: > > PINE 4.10 MESSAGE TEXT Message 45 of 45 *AD 60% > > The *AD tells me that I've flagged it important, I've answered it, and > I've marked it for deletion. > > Thanks for considering this! > Nancy > Good idea. Even better yet, it should be specifiable like the index-format is. That way we could put FULLSTATUS up there if we wanted, or customize it however else we wanted. I just figured out how IMAPSTATUS works in my index-format, and I think I prefer that to just STATUS since I use incoming folders and the recent flag actually matters. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun Jun 6 00:26:53 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sun, 6 Jun 1999 00:26:52 -0700 (PDT) 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 AAA11539 for ; Sun, 6 Jun 1999 00:26:50 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA16417; Sun, 6 Jun 1999 00:26:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA02176; Sun, 6 Jun 1999 00:26:29 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA17424 for ; Sun, 6 Jun 1999 00:21:50 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id AAA14576 for ; Sun, 6 Jun 1999 00:21:49 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id HAA27554; Sun, 6 Jun 1999 07:26:40 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sun, 6 Jun 99 00:26 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id AAA29866; Sun, 6 Jun 1999 00:19:34 -0700 Message-Id: Date: Sun, 6 Jun 1999 00:19:33 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: 4.10 vs 3.96 newsreading performance In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael A Crowley X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 5 Jun 1999, Michael A Crowley wrote: > Marking just the last message as "read" (delete) so the .newsrc > entry for that newsgroup read: 1-4427,5485 resulted in identical > performance between 3.96 and 4.10. I'm wondering if the way that it is looking at the news is somehow diffrent (one using nntp, the other using imap?). That seems to make a huge diffrence on my system (4.10 will have similar types of responces as you sugest between nntp, and imap). Does this make sence? Actually, it is also similar between local spool, and imap, and pop3 and imap. (not that I use pine with pop3). Is this normal? I think imap is great, but the performance hit is significant... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: From pinedev@shiva0.cac.washington.edu Mon Jun 7 01:15:34 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 01:15:33 -0700 (PDT) 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 BAA04906 for ; Mon, 7 Jun 1999 01:15:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA10259; Mon, 7 Jun 1999 01:15:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA26332; Mon, 7 Jun 1999 01:14:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA11274 for ; Mon, 7 Jun 1999 01:08:06 -0700 Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id BAA11374 for ; Mon, 7 Jun 1999 01:08:00 -0700 Received: (qmail 8575 invoked from network); 7 Jun 1999 08:18:35 -0000 Received: from brane.geac.com.au (202.6.67.115) by caveman.geac.com.au with SMTP; 7 Jun 1999 08:18:35 -0000 Received: from fgh.geac.com.au by brane.geac.com.au with smtp\n (Smail3.1.29.1 #3) id m10quKF-0002g1C; Mon, 7 Jun 99 18:00 AEST Received: from localhost (dave@localhost) by fgh.geac.com.au?r with ESMTP id SAA24357; Mon, 7 Jun 1999 18:05:38 +1000 Message-Id: Date: Mon, 7 Jun 1999 18:05:38 +1000 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Horsfall To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Edward M Greshko X-Cc: Pine Discussion Forum X-Sender: dave@fgh X-No-Archive: Yes X-Witty-Saying: "Tesseract - Enter at own risk" X-Disclaimer: "Me, speak for us?" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 29 May 1999, Edward M Greshko wrote: > I run pine in much the same way that you do. However, I don't allow my > INBOX to grow as large as you have. Now you know why it's so large - it can be ages before I can respond :-) > If you frequently allow your INBOX to get this large you may wish to > consider switching to a different INBOX format. The mbx format is > probably best for your situation. If you pickup the imap distribution > there are 2 files in the docs directory which explain the different > formats available and their merits. Thanks for the tip. I guess that means I have to use IMAP (the mail server is also the local machine). > You should also consider upgrading to Solaris7 and then doing a recompile > on pine. Having done so, the binary itself reduces in size from about > 8Meg to 4Meg. Yes, I will eventually, but only after all our clients in turn have been upgraded. -- Dave Horsfall VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422 Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia From pinedev@shiva0.cac.washington.edu Mon Jun 7 01:46:35 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 01:46:35 -0700 (PDT) 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 BAA05410 for ; Mon, 7 Jun 1999 01:46:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA03198; Mon, 7 Jun 1999 01:46:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA16155; Mon, 7 Jun 1999 01:45:31 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA41438 for ; Mon, 7 Jun 1999 01:40:12 -0700 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.06) with ESMTP id BAA26353 for ; Mon, 7 Jun 1999 01:40:11 -0700 Received: from mail.asianexplorer.com.au (asi24111-2.gw.connect.com.au [202.21.8.207]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA10668 for ; Mon, 7 Jun 1999 01:40:10 -0700 Received: from florence (unverified [192.168.1.80]) by mail.asianexplorer.com.au (Rockliffe SMTPRA 2.1.7) with SMTP id ; Mon, 07 Jun 1999 18:41:52 +1000 Received: by localhost with Microsoft MAPI; Mon, 7 Jun 1999 18:35:29 +1000 Message-Id: <01BEB114.84893780.florence@asianexplorer.com.au> Date: Mon, 7 Jun 1999 18:35:28 +1000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florence Lee To: Pine Discussion Forum Subject: mail directory MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'pine'" X-Cc: "'pine1'" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN hello...i have 2 problems.... anybody with "pine" clashing with AIX 4.2.1 WITH FIXES FOR MAINTEMAMCE LEVEL 3 2) I HAD A "888" CRASH, AND USERS WERE IN pine...FOR SOME REASON, MY USERS SEEM TO GET THE SAME MAIL OVER AND OVER AGAIN WHEN SYSTEM CAME BACK....THERE IS A DIRECTORY I CAN DELETE THIS OFFENDING MAIL....PLs advise.... Thanks & Regards Florence -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Jun 7 03:34:11 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 03:34:11 -0700 (PDT) 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 DAA09767 for ; Mon, 7 Jun 1999 03:34:10 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA12201; Mon, 7 Jun 1999 03:34:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id DAA02647; Mon, 7 Jun 1999 03:33:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id DAA49524 for ; Mon, 7 Jun 1999 03:29:59 -0700 Received: from pantheon-po02.its.yale.edu (pantheon-po02.its.yale.edu [130.132.143.33]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id DAA21766 for ; Mon, 7 Jun 1999 03:29:58 -0700 Received: from minerva.cis.yale.edu (amj9@minerva.cis.yale.edu [130.132.143.250]) by pantheon-po02.its.yale.edu (8.8.8/8.8.8) with ESMTP id GAA06435; Mon, 7 Jun 1999 06:29:57 -0400 (EDT) Received: from localhost (amj9@localhost) by minerva.cis.yale.edu (8.8.8/8.8.8) with SMTP id GAA02844; Mon, 7 Jun 1999 06:29:56 -0400 (EDT) Message-Id: Date: Mon, 7 Jun 1999 06:29:56 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Aubrey Jennings To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dave Horsfall X-Cc: Pine Discussion Forum X-Authentication-Warning: minerva.cis.yale.edu: amj9 owned process doing -bs X-Sender: amj9@minerva.cis.yale.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I get off this list? From pinedev@shiva0.cac.washington.edu Mon Jun 7 07:51:05 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 07:51:05 -0700 (PDT) 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 HAA25466 for ; Mon, 7 Jun 1999 07:51:03 -0700 (PDT) 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 HAA08428; Mon, 7 Jun 1999 07:51:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA07157; Mon, 7 Jun 1999 07:50:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA33018 for ; Mon, 7 Jun 1999 07:45:53 -0700 Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id HAA04598 for ; Mon, 7 Jun 1999 07:45:52 -0700 Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Mon, 07 Jun 99 08:45:02 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id IAA16172 for ; Mon, 7 Jun 1999 08:45:02 -0600 (MDT) Message-Id: Date: Mon, 7 Jun 1999 08:45:02 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B450564133527-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Check the page that you used to join the list. On Mon, 7 Jun 1999, Aubrey Jennings wrote: > > > How do I get off this list? > From pinedev@shiva0.cac.washington.edu Mon Jun 7 08:15:23 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 08:15:23 -0700 (PDT) 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 IAA27790 for ; Mon, 7 Jun 1999 08:15:22 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA08947; Mon, 7 Jun 1999 08:15:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA03471; Mon, 7 Jun 1999 08:14:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA13346 for ; Mon, 7 Jun 1999 08:09:56 -0700 Received: from sttlpop2.sttl.uswest.net (sttlpop2.sttl.uswest.net [206.81.192.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id IAA07484 for ; Mon, 7 Jun 1999 08:09:55 -0700 Received: (qmail 20660 invoked by alias); 7 Jun 1999 15:09:54 -0000 Received: (qmail 20626 invoked by uid 0); 7 Jun 1999 15:09:53 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop2.sttl.uswest.net with SMTP; 7 Jun 1999 15:09:53 -0000 Message-Id: Date: Mon, 7 Jun 1999 08:08:55 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dave Horsfall X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jun 1999, Dave Horsfall wrote: > > If you frequently allow your INBOX to get this large you may wish to > > consider switching to a different INBOX format. The mbx format is > > probably best for your situation. If you pickup the imap distribution > > there are 2 files in the docs directory which explain the different > > formats available and their merits. > > Thanks for the tip. I guess that means I have to use IMAP (the > mail server is also the local machine). Negative. Pine understands the same set of mailbox formats as UW's imapd. (They are both built on top of the same messaging libraries.) If your needs grow to require multiple machines, we would encourage use of IMAP, but as long as Pine users and the mail store are on the same machine, IMAP is not required, even when mbx is the chosen format. I believe there are some words in the distribution about how to get the delivery program (tmail/dmail), the mail servers (imapd, ipopd), and Pine all to agree to create new folders in mbx format. There is also a utility in the distribution for converting amongst formats (mbxcvt). -teg From pinedev@shiva0.cac.washington.edu Mon Jun 7 08:38:05 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 08:38:05 -0700 (PDT) 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 IAA13520 for ; Mon, 7 Jun 1999 08:38:04 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA09498; Mon, 7 Jun 1999 08:38:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA23893; Mon, 7 Jun 1999 08:37:36 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA17446 for ; Mon, 7 Jun 1999 08:33:12 -0700 Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA06841 for ; Mon, 7 Jun 1999 08:33:11 -0700 Received: (from uucp@localhost) by mail.ntplx.net (8.9.1/NETPLEX) id LAA25087 for u.washington.edu!pine-info; Mon, 7 Jun 1999 11:33:10 -0400 (EDT) Received: from macdco by mail.ntplx.net; Mon, 7 Jun 1999 11:33 EDT Message-Id: Date: Mon, 7 Jun 1999 11:33:10 -0400 (EDT) >Date: Mon, 7 Jun 1999 11:36:06 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Giannelli To: Pine Discussion Forum In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dcg@macdco.com X-To: Pine Discussion Forum X-Sender: dcg@macdco X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > On Mon, 7 Jun 1999, Aubrey Jennings wrote: > > > > > > > How do I get off this list? > > > > To signoff from the list, email to listproc@u.washington.edu with the following request: signoff PINE-ANNOUNCE or unsubscribe PINE-ANNOUNCE -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Jun 7 09:49:31 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 09:49:31 -0700 (PDT) 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 JAA32690 for ; Mon, 7 Jun 1999 09:49:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA11410; Mon, 7 Jun 1999 09:49:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA08409; Mon, 7 Jun 1999 09:48:54 -0700 Received: from jason01.u.washington.edu (root@jason01.u.washington.edu [140.142.70.24]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA50026 for ; Mon, 7 Jun 1999 09:44:30 -0700 Received: from dante17.u.washington.edu (leibrand@dante17.u.washington.edu [140.142.15.67]) by jason01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA34762; Mon, 7 Jun 1999 09:44:29 -0700 Received: from localhost (leibrand@localhost) by dante17.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA53916; Mon, 7 Jun 1999 09:44:27 -0700 Message-Id: Date: Mon, 7 Jun 1999 09:44:27 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: your mail In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: David Giannelli X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Shouldn't that be: unsubscibe pine-info ? Pine-announce is a much more limited mailing list only for announcements, not for general discussions like we always have here. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Mon, 7 Jun 1999, David Giannelli wrote: > > > > On Mon, 7 Jun 1999, Aubrey Jennings wrote: > > > > > > > > > > > How do I get off this list? > > > > > > > > > To signoff from the list, email to listproc@u.washington.edu with the following request: > > signoff PINE-ANNOUNCE > or > unsubscribe PINE-ANNOUNCE > > > > From pinedev@shiva0.cac.washington.edu Mon Jun 7 10:34:32 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 10:34:31 -0700 (PDT) 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 KAA15033 for ; Mon, 7 Jun 1999 10:34:30 -0700 (PDT) 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 KAA12843; Mon, 7 Jun 1999 10:34:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA15686; Mon, 7 Jun 1999 10:34:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA38580 for ; Mon, 7 Jun 1999 10:28:59 -0700 Received: from nyntq1.tink.com (SYSTEM@mail2.new-york.net [165.254.101.54]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA26173 for ; Mon, 7 Jun 1999 10:28:57 -0700 Received: from aleph.ii.com ("port 1685"@aleph.ii.com) by mail2.new-york.net (PMDF V5.1-10 #22883) with ESMTP id <01JC4CIPVNSM8X21MX@mail2.new-york.net> for pine-info@u.washington.edu; Mon, 7 Jun 1999 13:28:41 EDT Message-Id: Date: Mon, 07 Jun 1999 13:28:25 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nancy McGough To: Pine Discussion Forum Subject: Suggestion: blank subject header MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=ISO-8859-1 Content-transfer-encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: nm@operamail.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN * Right now when you reply to a message that has a blank Subject line, Pine produces the subject `Re: your mail'. How about having it be `Re: your mail with no subject'. * If I am about to send a message with no subject, I would like Pine to ask me if I really want to do that. E.g., when I type ^X, I'd like Pine to say something like: Do you really want to send a message with no subject? And it would nice to let people have the option to turn off this prompt. Thanks for considering these, -- 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 =-- -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Jun 7 14:46:49 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 14:46:48 -0700 (PDT) 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 OAA17886 for ; Mon, 7 Jun 1999 14:46:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA27785; Mon, 7 Jun 1999 14:46:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA10804; Mon, 7 Jun 1999 14:46:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA37464 for ; Mon, 7 Jun 1999 14:41:47 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA07540 for ; Mon, 7 Jun 1999 14:41:46 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id OAA11952 for ; Mon, 7 Jun 1999 14:41:50 -0700 (PDT) Message-Id: Date: Mon, 7 Jun 1999 14:41:55 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Can You tell me where the flags in the following header should be? PINE 4.10 MESSAGE TEXT pine-info Msg 28 of 32 TOP NEW I do not see any space to put the flags. I'd rather have a word in the header than a symbol. Please don't make this configurable also. This is almost splitting hairs. You can not convince to a new user of pine that this makes his/her life easier. Eduardo http://www.math.washington.edu/~chappa/personal.html From pinedev@shiva0.cac.washington.edu Mon Jun 7 14:52:27 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 14:52:27 -0700 (PDT) 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 OAA19299 for ; Mon, 7 Jun 1999 14:52:26 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA20513; Mon, 7 Jun 1999 14:52:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA22466; Mon, 7 Jun 1999 14:52:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA38408 for ; Mon, 7 Jun 1999 14:47:41 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA17571 for ; Mon, 7 Jun 1999 14:47:41 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id OAA11349 for ; Mon, 7 Jun 1999 14:47:46 -0700 (PDT) Message-Id: Date: Mon, 7 Jun 1999 14:47:50 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN If you want that, maybe you may want to change the code by yourself. I think it is personal preference if you want to write or not a subject. When you send personal letters through the mail (the old fashion way, with stamps), you don't write a subject outside of them, so this tells me sometimes it is not necessary. In any case if you want to change the message go to "reply.c" and change line 1285 to the "right message" Eduardo http://www.math.washington.edu/~chappa/personal.html From pinedev@shiva0.cac.washington.edu Mon Jun 7 15:49:01 1999 -0700 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 15:49:01 -0700 (PDT) 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 PAA21659 for ; Mon, 7 Jun 1999 15:49:00 -0700 (PDT) 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 PAA30045; Mon, 7 Jun 1999 15:48:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA29985; Mon, 7 Jun 1999 15:48:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27786 for ; Mon, 7 Jun 1999 15:44:05 -0700 Received: from q7.q7.com (joey@q7.q7.com [206.58.126.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA29044 for ; Mon, 7 Jun 1999 15:44:04 -0700 Received: from localhost (joey@localhost) by q7.q7.com (8.9.3/8.9.3) with ESMTP id PAA09017 for ; Mon, 7 Jun 1999 15:44:04 -0700 (PDT) Message-Id: Date: Mon, 7 Jun 1999 15:44:03 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joe Pruett To: Pine Discussion Forum Subject: signature token parsing problem In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN there doesn't appear to be a way to get a backslash followed by an underscore into a signature file. i've looked at the code for token interpolation and it seems like 3 backslashes followed by underscore should do it, but that didn't work. i've tried lots of alternatives, but can't come up with a sequence that works. have i missed something? or is this a bug? -- ----------------------------------------------------------------- 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, 7 Jun 1999 16:19:54 -0700 (PDT) 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 QAA13633 for ; Mon, 7 Jun 1999 16:19:52 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA31035; Mon, 7 Jun 1999 16:19:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA00855; Mon, 7 Jun 1999 16:19:32 -0700 Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA11400 for ; Mon, 7 Jun 1999 16:15:50 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA33908 for ; Mon, 7 Jun 1999 16:15:49 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA54652 for ; Mon, 7 Jun 1999 16:15:48 -0700 Message-Id: Date: Mon, 7 Jun 1999 16:15:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > Can You tell me where the flags in the following header should be? > > > PINE 4.10 MESSAGE TEXT pine-info Msg 28 of 32 TOP NEW > > I do not see any space to put the flags. I'd rather have a word in the > header than a symbol. Please don't make this configurable also. This is > almost splitting hairs. You can not convince to a new user of pine that > this makes his/her life easier. > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > These kind of configurable options are not supposed to make a newbie's life easier. They're for those of us who are comfortable with Pine and would make it more useful for ourselves. Take IMAPSTATUS in the index-format, for example. There's no way a newbie would want that, but I find it quite useful. Similarly, I would like to be able to configure my title bar as something like: VERSION CURRRENTVIEW COLLECTION FOLDER CURRENTMESSAGE POSITION IMAPSTATUS Does that make sense? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 7 Jun 1999 16:32:43 -0700 (PDT) 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 QAA23476 for ; Mon, 7 Jun 1999 16:32:42 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA23859; Mon, 7 Jun 1999 16:32:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA16098; Mon, 7 Jun 1999 16:30:40 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA37448 for ; Mon, 7 Jun 1999 16:25:58 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA45426; Mon, 7 Jun 1999 16:25:57 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA18774; Mon, 7 Jun 1999 16:25:57 -0700 Message-Id: Date: Mon, 7 Jun 1999 16:25:57 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: signature token parsing problem In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Joe Pruett X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a known bug in Pine 4.10 (and possibly other 4.x versions). The Pine guys have told us it will be fixed in the next version. There's currently no workaround short of substituting a different character combination. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Mon, 7 Jun 1999, Joe Pruett wrote: > there doesn't appear to be a way to get a backslash followed by an > underscore into a signature file. i've looked at the code for token > interpolation and it seems like 3 backslashes followed by underscore > should do it, but that didn't work. i've tried lots of alternatives, but > can't come up with a sequence that works. have i missed something? or is > this a bug? > > > 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, 7 Jun 1999 16:50:33 -0700 (PDT) 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 QAA24670 for ; Mon, 7 Jun 1999 16:50:32 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA31907; Mon, 7 Jun 1999 16:50:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA28479; Mon, 7 Jun 1999 16:50:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA29446 for ; Mon, 7 Jun 1999 16:46:06 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA25191; Mon, 7 Jun 1999 16:46:04 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP; Mon, 7 Jun 1999 18:45:59 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Tue, 8 Jun 1999 07:45:56 +0800 Message-Id: <000701beb13f$e030c0a0$1511b381@twntpe.cdc.com> Date: Tue, 8 Jun 1999 07:45:51 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: signature token parsing problem In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Scott Leibrand" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > This is a known bug in Pine 4.10 (and possibly other 4.x versions). The > Pine guys have told us it will be fixed in the next version. There's > currently no workaround short of substituting a different character > combination. Of course the "\_" combination in the signature is probably due to the desire to make a "pretty picture" which takes up lots of space and infuriates quite a few people. So maybe the "bug" is a subversive attempt to thwart the evil do'ers. :-) :-) (Sorry, I just watched a re-run of "Conspiracy Theory". Regards, Ed 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, 7 Jun 1999 17:23:13 -0700 (PDT) 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 RAA24752 for ; Mon, 7 Jun 1999 17:23:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA32704; Mon, 7 Jun 1999 17:23:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA18202; Mon, 7 Jun 1999 17:22:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA20694 for ; Mon, 7 Jun 1999 17:19:13 -0700 Received: from neouvielle.enserb.u-bordeaux.fr (root@neouvielle.enserb.u-bordeaux.fr [147.210.18.138]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA29411 for ; Mon, 7 Jun 1999 17:19:12 -0700 Received: from matho (saffroy@matho [147.210.18.2]) by neouvielle.enserb.u-bordeaux.fr (8.9.3/8.6.10) with ESMTP id CAA22858 for ; Tue, 8 Jun 1999 02:19:10 +0200 (MET DST) Message-Id: Date: Tue, 8 Jun 1999 02:19:09 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jean-Marc Saffroy To: Pine Discussion Forum Subject: Pine crashes when posting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Sender: saffroy@matho X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I use Pine 4.10 on two platforms (Solaris 2.5/Sparc, Linux/PC), and I have found a bug in Pine, which I was able to reproduce several times : - browse a newsgroup where there is an unread message - delete the message (D), but stay in the group - start composing a reply to the message (R), then postpone it (^O) - leave the newsgroup (go to another), then get back (the original message, flagged D, should have disappeared) - continue your reply (C) and send it (^X) * and there you see Pine exit abnormally * Apparently it is aborted, the last message I see is : [Updating "Answered" Flags ] Problem detected: "Received abort signal". Pine Exiting. The reply is correctly sent, though. HTH JMS PS: Wouldn't it be more convenient (for us of course) to have a mailing list dedicated to bugs ? -- Jean-Marc Saffroy -- ENSERB Informatique 2čme année mailto:jms@migrantprogrammer.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; Mon, 7 Jun 1999 21:44:08 -0700 (PDT) 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 VAA26748 for ; Mon, 7 Jun 1999 21:44:05 -0700 (PDT) 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 VAA29434; Mon, 7 Jun 1999 21:44:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA10271; Mon, 7 Jun 1999 21:43:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA43974 for ; Mon, 7 Jun 1999 21:39:24 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA24865 for ; Mon, 7 Jun 1999 21:39:24 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id VAA26678 for ; Mon, 7 Jun 1999 21:39:28 -0700 (PDT) Message-Id: Date: Mon, 7 Jun 1999 21:39:32 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN :) :) These kind of configurable options are not supposed to make a newbie's :) life easier. They're for those of us who are comfortable with Pine and :) would make it more useful for ourselves. Take IMAPSTATUS in the :) index-format, for example. There's no way a newbie would want that, but I :) find it quite useful. Similarly, I would like to be able to configure my :) title bar as something like: :) :) VERSION CURRRENTVIEW COLLECTION FOLDER CURRENTMESSAGE POSITION IMAPSTATUS :) :) Does that make sense? :) Scott, you live in a country where acronyms are an acceptable way of communication. This is not the case in other countries, where a word is worth its value. I use IMAPSTATUS since a long time and find it useful even for a newbie (you are being condescending here). In any case, pine developers have the last word about it. We'll see in future releases in your prayers were listened. In my own opinion, it's not worth to waste the time improving the already excellent presentation of the program. And also, don't be condescending to me either, have a nice day, though. Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 7 Jun 1999 23:29:09 -0700 (PDT) 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 XAA15819 for ; Mon, 7 Jun 1999 23:29:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA05599; Mon, 7 Jun 1999 23:29:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA27094; Mon, 7 Jun 1999 23:28:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA24624 for ; Mon, 7 Jun 1999 23:25:01 -0700 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.06) with ESMTP id XAA11399 for ; Mon, 7 Jun 1999 23:25:01 -0700 Received: from mail.asianexplorer.com.au (asi24111-2.gw.connect.com.au [202.21.8.207]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA30828 for ; Mon, 7 Jun 1999 23:24:59 -0700 Received: from florence (unverified [192.168.1.80]) by mail.asianexplorer.com.au (Rockliffe SMTPRA 2.1.7) with SMTP id for ; Tue, 08 Jun 1999 16:26:39 +1000 Received: by localhost with Microsoft MAPI; Tue, 8 Jun 1999 16:20:14 +1000 Message-Id: <01BEB1CA.CA485240.florence@asianexplorer.com.au> Date: Tue, 8 Jun 1999 16:20:14 +1000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florence Lee To: Pine Discussion Forum Subject: FW: mail directory MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'pine'" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----Original Message----- From: Florence Lee [SMTP:florence@asianexplorer.com.au] Sent: Monday, 7 June 1999 18:35 To: Pine Discussion Forum Subject: mail directory hello...i have 2 problems.... anybody with "pine" clashing with AIX 4.2.1 WITH FIXES FOR MAINTEMAMCE LEVEL 3 2) I HAD A "888" CRASH, AND USERS WERE IN pine...FOR SOME REASON, MY USERS SEEM TO GET THE SAME MAIL OVER AND OVER AGAIN WHEN SYSTEM CAME BACK....THERE IS A DIRECTORY I CAN DELETE THIS OFFENDING MAIL....PLs advise.... Thanks & Regards Florence -- ----------------------------------------------------------------- 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; Mon, 7 Jun 1999 23:33:24 -0700 (PDT) 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 XAA28636 for ; Mon, 7 Jun 1999 23:33:22 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA30932; Mon, 7 Jun 1999 23:33:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA27174; Mon, 7 Jun 1999 23:33:02 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA22404 for ; Mon, 7 Jun 1999 23:26:35 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA22042; Mon, 7 Jun 1999 23:26:34 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA63186; Mon, 7 Jun 1999 23:26:34 -0700 Message-Id: Date: Mon, 7 Jun 1999 23:26:33 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm not sure why you consider that condescending. Based on answers you've given in this newsgroup regarding changing Pine's source (and other things), I definitely wouldn't consider you a newbie (which I define as a user who's pretty new to a subject and doesn't know much about it). In my view, the average student who knows little about computers and just wants to use Pine for writing e-mail would not want to have to learn about New, Unread, and Recent flags when a simple New flag would do. Also, I'm not clear on what you meant by your acronym comment. The only acronyms I used in my message were IMAP (Internet Mail Access Protocol) and RCW in my sig (Revised Code of Washington). I don't see what either has to do making Pine's title bar configurable. And aside from that, I know that other languages like Spanish use acronyms as well, though probably not as frequently as English. One that comes to mind is FARC (Fuerza Armas Revolutionarias de Columbia - please correct my spelling and grammar). -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > :) > :) These kind of configurable options are not supposed to make a newbie's > :) life easier. They're for those of us who are comfortable with Pine and > :) would make it more useful for ourselves. Take IMAPSTATUS in the > :) index-format, for example. There's no way a newbie would want that, but I > :) find it quite useful. Similarly, I would like to be able to configure my > :) title bar as something like: > :) > :) VERSION CURRRENTVIEW COLLECTION FOLDER CURRENTMESSAGE POSITION IMAPSTATUS > :) > :) Does that make sense? > :) > > Scott, you live in a country where acronyms are an acceptable way of > communication. This is not the case in other countries, where a word is > worth its value. I use IMAPSTATUS since a long time and find it useful even > for a newbie (you are being condescending here). In any case, pine > developers have the last word about it. We'll see in future releases in > your prayers were listened. In my own opinion, it's not worth to waste the > time improving the already excellent presentation of the program. > > And also, don't be condescending to me either, have a nice day, though. > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > > 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, 7 Jun 1999 23:49:20 -0700 (PDT) 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 XAA26571 for ; Mon, 7 Jun 1999 23:49:17 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA05879; Mon, 7 Jun 1999 23:49:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA12589; Mon, 7 Jun 1999 23:47:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA27730 for ; Mon, 7 Jun 1999 23:43:15 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id XAA30599 for ; Mon, 7 Jun 1999 23:43:15 -0700 Received: from mail.asianexplorer.com.au (asi24111-2.gw.connect.com.au [202.21.8.207]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA05765 for ; Mon, 7 Jun 1999 23:43:13 -0700 Received: from florence (unverified [192.168.1.80]) by mail.asianexplorer.com.au (Rockliffe SMTPRA 2.1.7) with SMTP id for ; Tue, 08 Jun 1999 16:44:54 +1000 Received: by localhost with Microsoft MAPI; Tue, 8 Jun 1999 16:38:29 +1000 Message-Id: <01BEB1CD.569E9CC0.florence@asianexplorer.com.au> Date: Tue, 8 Jun 1999 16:38:28 +1000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florence Lee To: Pine Discussion Forum Subject: pine and AIX 4.2.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'pine-usergroup'" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN anybody out there who can help us with fine-tuning pine and halifax we need support Thanks & Regards Florence -- ----------------------------------------------------------------- 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, 8 Jun 1999 08:48:38 -0700 (PDT) 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 IAA04894 for ; Tue, 8 Jun 1999 08:48:36 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA06988; Tue, 8 Jun 1999 08:48:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA06259; Tue, 8 Jun 1999 08:48:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA35076 for ; Tue, 8 Jun 1999 08:43:10 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA32521 for ; Tue, 8 Jun 1999 08:43:08 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id PAA29072; Tue, 8 Jun 1999 15:48:01 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 8 Jun 99 08:48 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id IAA19836; Tue, 8 Jun 1999 08:38:20 -0700 Message-Id: Date: Tue, 8 Jun 1999 08:38:19 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > Scott, you live in a country where acronyms are an acceptable way of > communication. This is not the case in other countries, where a word is > worth its value. I use IMAPSTATUS since a long time and find it useful even > for a newbie (you are being condescending here). In any case, pine > developers have the last word about it. We'll see in future releases in > your prayers were listened. In my own opinion, it's not worth to waste the > time improving the already excellent presentation of the program. I believe that what was being said is that having things configurable is important to the people who have used pine for a ``while'' (I have used it myself for around 7 years (not exclusively mind you)). I personanly like that things are configurable, I don't think that it is that large of a ``resource hog'' to make things configurable (putting unneeded features in is what does that), so, why not make changes configurable? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 8 Jun 1999 10:52:31 -0700 (PDT) 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 KAA07143 for ; Tue, 8 Jun 1999 10:52:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17608; Tue, 8 Jun 1999 10:52:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA23843; Tue, 8 Jun 1999 10:52:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17480 for ; Tue, 8 Jun 1999 10:47:14 -0700 Received: from bearmtn-e0.cgd.ucar.edu (bearmtn-e0.cgd.ucar.edu [128.117.24.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA24658 for ; Tue, 8 Jun 1999 10:47:13 -0700 Received: from redmtn.cgd.ucar.edu (redmtn [128.117.24.4]) by bearmtn-e0.cgd.ucar.edu (8.9.3/8.9.3) with ESMTP id LAA18144 for ; Tue, 8 Jun 1999 11:47:12 -0600 (MDT) Received: from localhost (ivan@localhost) by redmtn.cgd.ucar.edu (8.9.3/8.9.3) with ESMTP id LAA23333 for ; Tue, 8 Jun 1999 11:47:12 -0600 (MDT) Message-Id: Date: Tue, 8 Jun 1999 11:47:12 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ivan Lima To: Pine Discussion Forum Subject: send without confirm MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO X-Authentication-Warning: redmtn.cgd.ucar.edu: ivan owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it possible to get rid of the "Send message?" confimration prompt when you send a message (^X) ? Is there a 'send-without-confirm' setting or something similar? Thanks for any help, -- Ivan Lima -- ----------------------------------------------------------------- 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, 8 Jun 1999 16:15:36 -0700 (PDT) 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 QAA13927 for ; Tue, 8 Jun 1999 16:15:35 -0700 (PDT) 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 QAA25931; Tue, 8 Jun 1999 16:15:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA13539; Tue, 8 Jun 1999 16:15:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA35120 for ; Tue, 8 Jun 1999 16:11:14 -0700 Received: from mailout1.nyroc.rr.com (mailout1-1.nyroc.rr.com [24.92.226.146]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA26471 for ; Tue, 8 Jun 1999 16:11:13 -0700 Received: from bart ([24.92.254.63]) by mailout1.nyroc.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com for ; Tue, 8 Jun 1999 19:10:00 -0400 Message-Id: <003201beb204$4ca2bee0$3ffe5c18@twcny.rr.com> Date: Tue, 8 Jun 1999 19:11:52 -0400 Reply-To: "B. Szyszka" Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "B. Szyszka" To: Pine Discussion Forum Subject: Multiple POP mailboxes References: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I was wondering if anyone might be able to help me out with setting up pine so that I could choose which mailbox to download mail from. My e-mail host is 123HostMe and I have a main username for it. Then my mailboxes have their own usernames. I can only telnet in with my main username and pine seems to be downloading messages from the mailbox with its alias set to *. Any suggestions? How can I get pine to download from a POP server and allow me to choose which username/combo to download from? -- Bart Szyszka bart@bgrafyx.com ICQ:4982727 B Grafyx http://www.bgrafyx.com All Advantage: Get Paid To Surf the Web http://alladvantage.com/go.asp?refid=ARD582 -- ----------------------------------------------------------------- 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, 8 Jun 1999 18:12:19 -0700 (PDT) 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 SAA15114 for ; Tue, 8 Jun 1999 18:12:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA28674; Tue, 8 Jun 1999 18:12:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA02264; Tue, 8 Jun 1999 18:11:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA35292 for ; Tue, 8 Jun 1999 18:08:17 -0700 Received: from ns1.interq.or.jp (kevin@ns1.interq.or.jp [210.157.0.14]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA28155 for ; Tue, 8 Jun 1999 18:08:17 -0700 Received: from localhost (kevin@localhost) by ns1.interq.or.jp (8.8.8/8.8.5) with ESMTP id KAA13080; Wed, 9 Jun 1999 10:08:12 +0900 (JST) Message-Id: Date: Wed, 9 Jun 1999 10:08:12 +0900 (JST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Ying To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ivan Lima X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Jun 1999, Ivan Lima wrote: > Is it possible to get rid of the "Send message?" confimration prompt > when you send a message (^X) ? Is there a 'send-without-confirm' > setting or something similar? > Yes... go to the Main Menu, select Setup, then Config, and doing a search using the 'w' key can help you find "confirm". 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, 8 Jun 1999 18:36:30 -0700 (PDT) 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 SAA16047 for ; Tue, 8 Jun 1999 18:36:29 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA29023; Tue, 8 Jun 1999 18:36:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA15074; Tue, 8 Jun 1999 18:36:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA37694 for ; Tue, 8 Jun 1999 18:32:38 -0700 Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id SAA30695 for ; Tue, 8 Jun 1999 18:32:34 -0700 Received: (qmail 3311 invoked from network); 9 Jun 1999 01:43:37 -0000 Received: from brane.geac.com.au (202.6.67.115) by caveman.geac.com.au with SMTP; 9 Jun 1999 01:43:37 -0000 Received: from fgh.geac.com.au by brane.geac.com.au with smtp\n (Smail3.1.29.1 #3) id m10rX6f-0003j4C; Wed, 9 Jun 99 11:24 AEST Received: from localhost (dave@localhost) by fgh.geac.com.au?r with ESMTP id LAA29084; Wed, 9 Jun 1999 11:30:29 +1000 Message-Id: Date: Wed, 9 Jun 1999 11:30:28 +1000 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Horsfall To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ivan Lima X-Cc: Pine Discussion Forum X-Sender: dave@fgh X-No-Archive: Yes X-Witty-Saying: "Tesseract - Enter at own risk" X-Disclaimer: "Me, speak for us?" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 8 Jun 1999, Ivan Lima wrote: > Is it possible to get rid of the "Send message?" confimration prompt > when you send a message (^X) ? Is there a 'send-without-confirm' > setting or something similar? Trust me - you'll be sorry you did... -- Dave Horsfall VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422 Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia 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, 8 Jun 1999 18:54:20 -0700 (PDT) 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 SAA14377 for ; Tue, 8 Jun 1999 18:54:19 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA29298; Tue, 8 Jun 1999 18:54:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA04082; Tue, 8 Jun 1999 18:53:59 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA51554 for ; Tue, 8 Jun 1999 18:50:08 -0700 Received: from dante39.u.washington.edu (leibrand@dante39.u.washington.edu [140.142.15.199]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA28844; Tue, 8 Jun 1999 18:50:07 -0700 Received: from localhost (leibrand@localhost) by dante39.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA115832; Tue, 8 Jun 1999 18:50:06 -0700 Message-Id: Date: Tue, 8 Jun 1999 18:50:06 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Kevin Ying X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 9 Jun 1999, Kevin Ying wrote: > On Tue, 8 Jun 1999, Ivan Lima wrote: > > > Is it possible to get rid of the "Send message?" confimration prompt > > when you send a message (^X) ? Is there a 'send-without-confirm' > > setting or something similar? > > > Yes... go to the Main Menu, select Setup, then Config, and doing a search > using the 'w' key can help you find "confirm". > There's no send-without-confirm or anything similar in Pine 4.10 on the University of Washington's Unix machines. What version of Pine are you using? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 8 Jun 1999 19:01:51 -0700 (PDT) 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 TAA17577 for ; Tue, 8 Jun 1999 19:01:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA22471; Tue, 8 Jun 1999 19:01:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA19823; Tue, 8 Jun 1999 19:01:30 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA37822 for ; Tue, 8 Jun 1999 18:57:32 -0700 Received: from ns1.interq.or.jp (kevin@ns1.interq.or.jp [210.157.0.14]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA16047; Tue, 8 Jun 1999 18:57:31 -0700 Received: from localhost (kevin@localhost) by ns1.interq.or.jp (8.8.8/8.8.5) with ESMTP id KAA13564; Wed, 9 Jun 1999 10:57:29 +0900 (JST) Message-Id: Date: Wed, 9 Jun 1999 10:57:29 +0900 (JST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Kevin Ying To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I stand corrected... the send-without-confirm option no longer exists in Pine 4.10. Perhaps the authors took it out. On Tue, 8 Jun 1999, Scott Leibrand wrote: > On Wed, 9 Jun 1999, Kevin Ying wrote: > > > On Tue, 8 Jun 1999, Ivan Lima wrote: > > > > > Is it possible to get rid of the "Send message?" confimration prompt > > > when you send a message (^X) ? Is there a 'send-without-confirm' > > > setting or something similar? > > > > > Yes... go to the Main Menu, select Setup, then Config, and doing a search > > using the 'w' key can help you find "confirm". > > > > There's no send-without-confirm or anything similar in Pine 4.10 on the > University of Washington's Unix machines. What version of Pine are you > using? > > -- > Scott Leibrand > leibrand@u.washington.edu > How to contact me: > http://students.washington.edu/leibrand/howtocontactme.html > * RCW 19.190 notice: This email address is located in Washington State. * > * Unsolicited commercial email may be billed $500 per message. * > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 8 Jun 1999 19:56:08 -0700 (PDT) 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 TAA05534 for ; Tue, 8 Jun 1999 19:56:07 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA23319; Tue, 8 Jun 1999 19:56:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA06273; Tue, 8 Jun 1999 19:55:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA16124 for ; Tue, 8 Jun 1999 19:51:43 -0700 Received: from sttlpop1.sttl.uswest.net (sttlpop1.sttl.uswest.net [206.81.192.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id TAA05465 for ; Tue, 8 Jun 1999 19:51:43 -0700 Received: (qmail 9626 invoked by alias); 9 Jun 1999 02:51:40 -0000 Received: (qmail 9606 invoked by uid 0); 9 Jun 1999 02:51:40 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop1.sttl.uswest.net with SMTP; 9 Jun 1999 02:51:40 -0000 Message-Id: Date: Tue, 8 Jun 1999 19:50:41 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Kevin Ying X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry... there has never been a "send-without-confirm" option in any unmodified version of Pine. (*quit*-without-confirm, yes... but not *send*-without-confirm.) -teg On Wed, 9 Jun 1999, Kevin Ying wrote: > I stand corrected... the send-without-confirm option no longer exists in > Pine 4.10. Perhaps the authors took it out. 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, 8 Jun 1999 22:58:35 -0700 (PDT) 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 WAA18849 for ; Tue, 8 Jun 1999 22:58:33 -0700 (PDT) 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 WAA25850; Tue, 8 Jun 1999 22:58:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA27497; Tue, 8 Jun 1999 22:58:10 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA51620 for ; Tue, 8 Jun 1999 22:53:45 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA02746 for ; Tue, 8 Jun 1999 22:53:45 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id WAA20859; Tue, 8 Jun 1999 22:53:48 -0700 (PDT) Message-Id: Date: Tue, 8 Jun 1999 22:53:54 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: send without confirm In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE X-To: Ivan Lima X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Ivan Lima (ivan@cgd.ucar.edu) wrote Today: :) Is it possible to get rid of the "Send message?" confimration prompt :) when you send a message (^X) ? Is there a 'send-without-confirm' :) setting or something similar? :)=20 Hello Iv=E1n, Yes there is, by hacking the code. The easiest way is to delete lines 2182 to 2290 and 4642 to 4851 in send.c (You can use sed to do it with the command "sed '2182,2290d;4642,4851d' send.c") and rebuild. The bad thing about this, is that if you define roles, or have sending filters or you want to change anything when sending the message you will not be able to modify it. But if you don't have, then that's the solution. Good luck, have a nice day. Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 10 Jun 1999 14:05:53 -0700 (PDT) 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 OAA20348 for ; Thu, 10 Jun 1999 14:05:51 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA04790; Thu, 10 Jun 1999 14:05:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA28247; Thu, 10 Jun 1999 14:05:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA36332 for ; Thu, 10 Jun 1999 14:00:02 -0700 Received: from netins.net (pmr193.iowaclinic.com [216.81.154.193] (may be forged)) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id OAA17964 for ; Thu, 10 Jun 1999 14:00:01 -0700 Received: from 48-243 by netins.net;Thu, 10 Jun 1999 20:58:32 GMT Message-Id: <000501beb384$001ce060$08cda8c0@48-243.iowaclinic.com> Date: Thu, 10 Jun 1999 15:58:32 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Bob Eimers" To: Pine Discussion Forum Subject: Pine and AIX 4.3.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Pine has stopped working after we upgraded to AIX 4.3.2. Any messages being sent eventually come back as "undeliverable". We are on version 3.91 of Pine. Any suggestions would be appreciated. Thanks, Bob -- ----------------------------------------------------------------- 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, 10 Jun 1999 16:57:19 -0700 (PDT) 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 QAA22491 for ; Thu, 10 Jun 1999 16:57:18 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA16706; Thu, 10 Jun 1999 16:57:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA05048; Thu, 10 Jun 1999 16:55:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA47476 for ; Thu, 10 Jun 1999 16:51:31 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA17014 for ; Thu, 10 Jun 1999 16:51:30 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Thu, 10 Jun 1999 18:51:25 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 11 Jun 1999 07:51:23 +0800 Message-Id: <000a01beb39c$23551080$1511b381@twntpe.cdc.com> Date: Fri, 11 Jun 1999 07:51:20 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Pine and AIX 4.3.2 In-Reply-To: <000501beb384$001ce060$08cda8c0@48-243.iowaclinic.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Bob Eimers" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Bob, > Pine has stopped working after we upgraded to AIX 4.3.2. Any messages being > sent eventually come back as "undeliverable". We are on version 3.91 of > Pine. Any suggestions would be appreciated. I don't use AIX. However, providing a bit more detail, e.g. one non-delivery report, for us to look at may give us some clue to the problem you've encountered. Regards, Ed 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, 12 Jun 1999 22:17:50 -0700 (PDT) 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 WAA04145 for ; Sat, 12 Jun 1999 22:17:48 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA00148; Sat, 12 Jun 1999 22:17:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA00758; Sat, 12 Jun 1999 22:17:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA25656 for ; Sat, 12 Jun 1999 22:11:28 -0700 Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id WAA04914 for ; Sat, 12 Jun 1999 22:11:26 -0700 Received: (qmail 28860 invoked from network); 13 Jun 1999 05:23:33 -0000 Received: from brane.geac.com.au (202.6.67.115) by caveman.geac.com.au with SMTP; 13 Jun 1999 05:23:33 -0000 Received: from fgh.geac.com.au by brane.geac.com.au with smtp\n (Smail3.1.29.1 #3) id m10t2VB-0003nSC; Sun, 13 Jun 99 15:08 AEST Received: from localhost (dave@localhost) by fgh.geac.com.au?r with ESMTP id PAA08910; Sun, 13 Jun 1999 15:09:12 +1000 Message-Id: Date: Sun, 13 Jun 1999 15:09:12 +1000 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Horsfall To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Sender: dave@fgh X-No-Archive: Yes X-Witty-Saying: "Tesseract - Enter at own risk" X-Disclaimer: "Me, speak for us?" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 7 Jun 1999, Terry Gray wrote: > > Thanks for the tip. I guess that means I have to use IMAP (the > > mail server is also the local machine). > > Negative. Pine understands the same set of mailbox formats as UW's imapd. Better still - thanks! PS: Your messages are being trapped by my spam-filter because of the illegal timezone in the Date: header. You might want to fix that; it currently looks like: Date: Mon, 7 Jun 1999 08:08:55 -0700 (Pacific Daylight Time) "Pacific Daylight Time" is wrong, and is the signature of some spam-ware. -- Dave Horsfall VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422 Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia 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, 13 Jun 1999 15:17:30 -0700 (PDT) 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 PAA02008 for ; Sun, 13 Jun 1999 15:17:29 -0700 (PDT) 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 PAA05181; Sun, 13 Jun 1999 15:17:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA14725; Sun, 13 Jun 1999 15:17:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA35722 for ; Sun, 13 Jun 1999 15:12:56 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA00239 for ; Sun, 13 Jun 1999 15:12:50 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id WAA02268; Sun, 13 Jun 1999 22:17:43 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sun, 13 Jun 99 15:17 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA07422; Sun, 13 Jun 1999 15:00:25 -0700 Message-Id: Date: Sun, 13 Jun 1999 15:00:24 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: PINE loops on zero mail check interval In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dave Horsfall X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sun, 13 Jun 1999, Dave Horsfall wrote: > PS: Your messages are being trapped by my spam-filter because of the > illegal timezone in the Date: header. You might want to fix that; it > currently looks like: > > Date: Mon, 7 Jun 1999 08:08:55 -0700 (Pacific Daylight Time) > > "Pacific Daylight Time" is wrong, and is the signature of some spam-ware. I've not noticed this sort of signature before. Oddly, your message seems to be coming with a time signature that *I* don't consider ``correct''. It may very well be, which it looks like (EST I associate with ``Eastern Standard Time''), intrestingly enough, the zoneinfo files seem to agree with your ussage. Which indicates that the three letter code is rather ambiguous. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 13 Jun 1999 16:50:29 -0700 (PDT) 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 QAA02575 for ; Sun, 13 Jun 1999 16:50:28 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA06269; Sun, 13 Jun 1999 16:50:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA14587; Sun, 13 Jun 1999 16:50:05 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA22898 for ; Sun, 13 Jun 1999 16:46:32 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA07714 for ; Sun, 13 Jun 1999 16:46:31 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Sun, 13 Jun 1999 18:46:26 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Mon, 14 Jun 1999 07:46:22 +0800 Message-Id: <000101beb5f6$eb6723e0$1511b381@twntpe.cdc.com> Date: Mon, 14 Jun 1999 07:46:12 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Dave Horsfall" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dave, > PS: Your messages are being trapped by my spam-filter because of the > illegal timezone in the Date: header. You might want to fix that; it > currently looks like: > > Date: Mon, 7 Jun 1999 08:08:55 -0700 (Pacific Daylight Time) May I suggest a little light reading for you and Jessica? It is called RFC822. Here is an excerpt from it: Standard for ARPA Internet Text Messages 5. DATE AND TIME SPECIFICATION 5.1. SYNTAX date-time = [ day "," ] date time ; dd mm yy ; hh:mm:ss zzz day = "Mon" / "Tue" / "Wed" / "Thu" / "Fri" / "Sat" / "Sun" date = 1*2DIGIT month 2DIGIT ; day month year ; e.g. 20 Jun 82 month = "Jan" / "Feb" / "Mar" / "Apr" / "May" / "Jun" / "Jul" / "Aug" / "Sep" / "Oct" / "Nov" / "Dec" time = hour zone ; ANSI and Military hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT] ; 00:00:00 - 23:59:59 zone = "UT" / "GMT" ; Universal Time ; North American : UT / "EST" / "EDT" ; Eastern: - 5/ - 4 / "CST" / "CDT" ; Central: - 6/ - 5 / "MST" / "MDT" ; Mountain: - 7/ - 6 / "PST" / "PDT" ; Pacific: - 8/ - 7 / 1ALPHA ; Military: Z = UT; ; A:-1; (J not used) ; M:-12; N:+1; Y:+12 / ( ("+" / "-") 4DIGIT ) ; Local differential ; hours+min. (HHMM) You will note that in the case above the zone is "-0700". Jessica should note that in your case the zone is "+1000". In both case the text enclosed in "(" and ")" is comment only. Regareds, Ed 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, 13 Jun 1999 19:16:48 -0700 (PDT) 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 TAA03652 for ; Sun, 13 Jun 1999 19:16:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA15877; Sun, 13 Jun 1999 19:16:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA12091; Sun, 13 Jun 1999 19:16:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA37732 for ; Sun, 13 Jun 1999 19:12:24 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA11556 for ; Sun, 13 Jun 1999 19:12:22 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id CAA03673; Mon, 14 Jun 1999 02:17:19 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sun, 13 Jun 99 19:17 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id TAA09502; Sun, 13 Jun 1999 19:07:15 -0700 Message-Id: Date: Sun, 13 Jun 1999 19:07:13 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: <000101beb5f6$eb6723e0$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Jun 1999, Ed Greshko wrote: > Dave, > > > PS: Your messages are being trapped by my spam-filter because of the > > illegal timezone in the Date: header. You might want to fix that; it > > currently looks like: > > > > Date: Mon, 7 Jun 1999 08:08:55 -0700 (Pacific Daylight Time) ^^^^ > May I suggest a little light reading for you and Jessica? It is > called RFC822. Here is an excerpt from it: May I sugesst that clearly this portion of the specification is NOT correct? Notice the points that I have highlited. (Also, I HAVE read a good portion (if not all) of RFC822) > Standard for ARPA Internet Text Messages > > > 5. DATE AND TIME SPECIFICATION > > 5.1. SYNTAX > > date-time = [ day "," ] date time ; dd mm yy > ; hh:mm:ss zzz > > day = "Mon" / "Tue" / "Wed" / "Thu" > / "Fri" / "Sat" / "Sun" > > date = 1*2DIGIT month 2DIGIT ; day month year ^^^^^^ ; e.g. 20 Jun 82 > month = "Jan" / "Feb" / "Mar" / "Apr" > / "May" / "Jun" / "Jul" / "Aug" > / "Sep" / "Oct" / "Nov" / "Dec" > > time = hour zone ; ANSI and Military > > hour = 2DIGIT ":" 2DIGIT [":" 2DIGIT] > ; 00:00:00 - 23:59:59 > > zone = "UT" / "GMT" ; Universal Time > ; North American : UT > / "EST" / "EDT" ; Eastern: - 5/ - 4 > / "CST" / "CDT" ; Central: - 6/ - 5 > / "MST" / "MDT" ; Mountain: - 7/ - 6 > / "PST" / "PDT" ; Pacific: - 8/ - 7 > / 1ALPHA ; Military: Z = UT; > ; A:-1; (J not used) > ; M:-12; N:+1; Y:+12 > / ( ("+" / "-") 4DIGIT ) ; Local differential > ; hours+min. (HHMM) > > You will note that in the case above the zone is "-0700". Jessica should note > that in your case the zone is "+1000". In both case the text enclosed in "(" > and ")" is comment only. Thanks for clarifying the comment bit, if you didn't figure out what I was pointing out, we use a 4 digit year (have for as long as I remeber), and the standard specifies (explicately), a 2 digit year. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 13 Jun 1999 20:50:17 -0700 (PDT) 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 UAA04188 for ; Sun, 13 Jun 1999 20:50:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA17072; Sun, 13 Jun 1999 20:50:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA13372; Sun, 13 Jun 1999 20:49:45 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA20444 for ; Sun, 13 Jun 1999 20:45:14 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id UAA16348 for ; Sun, 13 Jun 1999 20:45:13 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Sun, 13 Jun 1999 22:45:09 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Mon, 14 Jun 1999 11:45:06 +0800 Message-Id: <000b01beb618$45b39560$1511b381@twntpe.cdc.com> Date: Mon, 14 Jun 1999 11:44:57 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jessica Rasku" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Jessica, > May I sugesst that clearly this portion of the specification is > NOT correct? Notice the points that I have highlited. (Also, I HAVE read > a good portion (if not all) of RFC822) Hummm.... Your Sunday not going well? You can suggest that this portion of the spec is incorrect....but you'd be wrong. You can't say that an adopted Internet standard is "incorrect". You can only you don't agree with it. I thought we were only talking about that last comment field? Don't know why you decided it was a good idea to jump down my throat about 99' v.s. 1999? If I'd known you wanted to talk about the year portion I may have included references to the extensions to RFC822. > Thanks for clarifying the comment bit, if you didn't figure out > what I was pointing out, we use a 4 digit year (have for as long as I > remeber), and the standard specifies (explicately), a 2 digit year. Well, since in your original message only talked about the timezone I didn't grasp that you were talking about the year. I could send you what you wrote if you've forgotten. Your welcome and regards, Ed 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, 13 Jun 1999 22:11:04 -0700 (PDT) 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 WAA04874 for ; Sun, 13 Jun 1999 22:11:02 -0700 (PDT) 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 WAA18083; Sun, 13 Jun 1999 22:11:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA20214; Sun, 13 Jun 1999 22:10:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA13486 for ; Sun, 13 Jun 1999 22:06:33 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA10451 for ; Sun, 13 Jun 1999 22:06:10 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA05184; Mon, 14 Jun 1999 05:11:02 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sun, 13 Jun 99 22:11 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id VAA12502; Sun, 13 Jun 1999 21:53:26 -0700 Message-Id: Date: Sun, 13 Jun 1999 21:53:25 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: <000b01beb618$45b39560$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Jun 1999, Ed Greshko wrote: > Jessica, > > > May I sugesst that clearly this portion of the specification is > > NOT correct? Notice the points that I have highlited. (Also, I HAVE read > > a good portion (if not all) of RFC822) > > Hummm.... Your Sunday not going well? It is people who get all high and mighty that make people's days go poorly... > You can suggest that this portion of the spec is incorrect....but you'd be > wrong. You can't say that an adopted Internet standard is "incorrect". You can > only you don't agree with it. You are quite right, I chose to word my comment poorly. I'm not saying that it's not correct really, or even that I don't agree with it, but more correctly, that it is NOT implemented the way that what you sent sais that it should be. > I thought we were only talking about that last comment field? Don't know why > you decided it was a good idea to jump down my throat about 99' v.s. 1999? If > I'd known you wanted to talk about the year portion I may have included > references to the extensions to RFC822. Um, who is jumping down WHO'S throat? I was SIMPLY pointing out a problem that you failed to notice. Um, these extensions, would they not be part of a DIFFRENT RFC? Would it not be correct that if they are part of a DIFFRENT RFC that they are not part of RFC822? > > Thanks for clarifying the comment bit, if you didn't figure out > > what I was pointing out, we use a 4 digit year (have for as long as I > > remeber), and the standard specifies (explicately), a 2 digit year. > > Well, since in your original message only talked about the timezone I didn't > grasp that you were talking about the year. I could send you what you wrote if > you've forgotten. What *I* wrote, was about how that coment field (not knowing it was a comment field (which I should have known)), can be CONFUSING. If you care to actually read the WHOLE post, before jumping on your reply key, maybe you'll see that. In fact, I have said nothing other than the year thing which is contrary to RFC822 Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 13 Jun 1999 22:40:09 -0700 (PDT) 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 WAA05062 for ; Sun, 13 Jun 1999 22:40:07 -0700 (PDT) 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 WAA10627; Sun, 13 Jun 1999 22:40:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA20929; Sun, 13 Jun 1999 22:39:48 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA25774 for ; Sun, 13 Jun 1999 22:35:17 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA32019 for ; Sun, 13 Jun 1999 22:35:17 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 14 Jun 1999 00:35:11 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Mon, 14 Jun 1999 13:35:03 +0800 Message-Id: <001201beb627$a1afb7e0$1511b381@twntpe.cdc.com> Date: Mon, 14 Jun 1999 13:34:54 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jessica Rasku" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Jessica, > It is people who get all high and mighty that make people's days > go poorly... ???? > You are quite right, I chose to word my comment poorly. I'm not > saying that it's not correct really, or even that I don't agree with it, > but more correctly, that it is NOT implemented the way that what you sent > sais that it should be. The comment field was the point of "debate". The "year", as far as I could tell wasn't. Pardon me for saying this...but if you "chose" to word (your) comments poorly then you should expect there to be misunderstandings. > Um, who is jumping down WHO'S throat? I was SIMPLY pointing out a > problem that you failed to notice. Um, these extensions, would they not > be part of a DIFFRENT RFC? Would it not be correct that if they are part > of a DIFFRENT RFC that they are not part of RFC822? ???? Just let me say that my sole purpose was to correct the misunderstanding of the comment portion of the Date: line. I'm sorry if you take my "suggestion" as being anything other than trying to be helpful. > What *I* wrote, was about how that coment field (not knowing it > was a comment field (which I should have known)), can be CONFUSING. If > you care to actually read the WHOLE post, before jumping on your reply > key, maybe you'll see that. In fact, I have said nothing other than the > year thing which is contrary to RFC822 Please tell me which part of your post I failed to read correctly which indicates you were addressing a "problem" with the year. In the original post from Dave he cited the "illegal timezone in the Date: header" as the source of his problem. Nothing about the "1999". When you responded to him you talked about EST. I didn't see anything which indicated a "year" problem. It is possible you've sent more than one post on this matter to the forum and it didn't reach me. Regards, Ed P.S. This seems like it is getting away from a "pine" discussion. Don't you agree? 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, 13 Jun 1999 23:50:34 -0700 (PDT) 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 XAA05678 for ; Sun, 13 Jun 1999 23:50:33 -0700 (PDT) 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 XAA11461; Sun, 13 Jun 1999 23:50:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA21654; Sun, 13 Jun 1999 23:50:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA20426 for ; Sun, 13 Jun 1999 23:46:04 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id XAA26251 for ; Sun, 13 Jun 1999 23:46:03 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id GAA05926; Mon, 14 Jun 1999 06:51:08 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sun, 13 Jun 99 23:51 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id XAA24927; Sun, 13 Jun 1999 23:10:44 -0700 Message-Id: Date: Sun, 13 Jun 1999 23:10:42 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: PINE loops on zero mail check interval In-Reply-To: <001201beb627$a1afb7e0$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 14 Jun 1999, Ed Greshko wrote: For sanity sake .... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 14 Jun 1999 07:04:02 -0700 (PDT) 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 HAA13377 for ; Mon, 14 Jun 1999 07:04:00 -0700 (PDT) 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 HAA25044; Mon, 14 Jun 1999 07:03:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA26365; Mon, 14 Jun 1999 07:03:37 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA25182 for ; Mon, 14 Jun 1999 06:59:48 -0700 Received: from bcx01.co.boulder.co.us (bcx01.co.boulder.co.us [161.98.128.4]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA11765 for ; Mon, 14 Jun 1999 06:59:47 -0700 Received: from localhost (swcxt@localhost) by bcx01.co.boulder.co.us (8.9.3/8.9.3) with ESMTP id HAA136622 for ; Mon, 14 Jun 1999 07:59:37 -0600 Message-Id: Date: Mon, 14 Jun 1999 07:59:37 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Shane Castle To: Pine Discussion Forum Subject: Re: Pine and AIX 4.3.2 In-Reply-To: <000501beb384$001ce060$08cda8c0@48-243.iowaclinic.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 10 Jun 1999, Bob Eimers wrote: >Pine has stopped working after we upgraded to AIX 4.3.2. Any messages being >sent eventually come back as "undeliverable". We are on version 3.91 of >Pine. Any suggestions would be appreciated. There's the obvious suggestion to upgrade to Pine 4.10. I upgraded to 4.10 before my AIX 4.1.5 -> 4.3.2 upgrade and Pine never hiccupped. Are you sure the problem is Pine and not the new Sendmail that IBM trashed^H^H^H^H^H^H^Hhacked^H^H^H^H^H^Hsent with 4.3.2? We, of course, are running Sendmail-8.9.3 and *not* IBM's downlevel version 8.8.8 that they supply as a cruel joke. -- Shane Castle | "Perfection, then, is finally achieved, not Boulder County Info Svcs | when there is nothing left to add, but when Boulder CO USA | there is nothing left to take away." | - Antoine de Saint-Exupery 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, 14 Jun 1999 08:52:25 -0700 (PDT) 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 IAA14848 for ; Mon, 14 Jun 1999 08:52:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA27432; Mon, 14 Jun 1999 08:52:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA09935; Mon, 14 Jun 1999 08:51:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA31566 for ; Mon, 14 Jun 1999 08:47:13 -0700 Received: from library.wustl.edu (library.wustl.edu [128.252.66.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA15625 for ; Mon, 14 Jun 1999 08:47:13 -0700 Received: from localhost (jerryp@localhost) by library.wustl.edu (8.8.5/8.8.5) with SMTP id KAA27167 for ; Mon, 14 Jun 1999 10:47:10 -0500 (CDT) Message-Id: Date: Mon, 14 Jun 1999 10:47:10 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jerry Pelikan To: Pine Discussion Forum Subject: Re-writing the "From: " line MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Having upgraded to sendmail 8.9.3, BrekelyDB 2.7.3 and Pine 4.10, I can't get sendmail to rewrite the "From: " line when using Pine. When sending directly with sendmail, the from line is properly rewritten by the userdb or the genericstable as reccomended by the folks at Sendmail. Any suggestions would be appriciated. Jerry Pelikan Jerry-Pelikan@library.wustl.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; Mon, 14 Jun 1999 12:08:35 -0700 (PDT) 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 MAA19775 for ; Mon, 14 Jun 1999 12:08:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA00555; Mon, 14 Jun 1999 12:08:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA17078; Mon, 14 Jun 1999 12:08:03 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA41456 for ; Mon, 14 Jun 1999 12:01:40 -0700 Received: from gatekeeper2.novartis.com (gatekeeper2.novartis.com [194.191.169.74]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA13923 for ; Mon, 14 Jun 1999 12:01:39 -0700 Received: from mta3.is.chbs (mta3.novartis.com [192.37.10.59]) by gatekeeper2.novartis.com (8.9.3/8.9.3) with ESMTP id VAA27217 for ; Mon, 14 Jun 1999 21:01:31 +0200 (MET DST) Received: from nts1.novartis.com ([192.168.50.131]) by mta3.is.chbs (8.9.3/8.9.3) with SMTP id VAA21292 for ; Mon, 14 Jun 1999 21:02:25 +0200 (MET DST) Received: by nts1.novartis.com(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999)) id 41256790.006DFE43 ; Mon, 14 Jun 1999 21:01:25 +0100 Message-Id: <41256790.006DFCC1.00@nts1.novartis.com> Date: Mon, 14 Jun 1999 21:01:13 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: martin.mokrejs@pharma.Novartis.com To: Pine Discussion Forum Subject: Proper text wrapping in pine Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Lotus-FromDomain: PH@N1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, does someone know if pine4.10 has those fancy abilities as this piece of SW? See http://www.xs4all.nl/~js/gnksa/gnksa-tools.html, follow link to wrapping.tar.gz in Related tools sect. There are some other nice tools too! I can't test right now, but as I remember, I always had problems with pico editor, even with 4.10. It claimed to be able to work with lines up-to 80 or 85 chars/line, but always mangled e-mails sent from stupid Windoze mailers. Specially, if the message was already quoted by sender, pico always while replying changed line endings. I think using these two functions would solve the problem. Is somewhere configurable to turn off text-wrapping in pine? TIA Martin -- ----------------------------------------------------------------- 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, 14 Jun 1999 13:01:20 -0700 (PDT) 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 NAA21121 for ; Mon, 14 Jun 1999 13:01:19 -0700 (PDT) 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 NAA01924; Mon, 14 Jun 1999 13:01:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA09359; Mon, 14 Jun 1999 13:00:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA20560 for ; Mon, 14 Jun 1999 12:55:08 -0700 Received: from chinet.chinet.com (root@chinet.chinet.com [209.219.112.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA29172 for ; Mon, 14 Jun 1999 12:55:08 -0700 Received: from localhost (ahk@localhost) by chinet.chinet.com (8.9.3/8.9.3) with ESMTP id OAA22970 for ; Mon, 14 Jun 1999 14:55:07 -0500 Message-Id: Date: Mon, 14 Jun 1999 14:55:07 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Proper text wrapping in pine In-Reply-To: <41256790.006DFCC1.00@nts1.novartis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN >From: martin.mokrejs@pharma.Novartis.com >Date: Mon, 14 Jun 1999 21:01:13 +0100 >I can't test right now, but as I remember, I always had problems >with pico editor, even with 4.10. It claimed to be able to work with >lines up-to 80 or 85 chars/line, but always mangled e-mails sent >from stupid Windoze mailers. Specially, if the message was already >quoted by sender, pico always while replying changed line endings. >I think using these two functions would solve the problem. >Is somewhere configurable to turn off text-wrapping in pine? No. It's a feature of the internal composer. So use a different text editor that's more to your liking. If you quote text and the reply goes to a mailing list or News, you need to reformat long lines regardless. It's rude to send long lines. If you have an actual need to retain the original line length, you may do so in an attachment. 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, 15 Jun 1999 17:53:35 -0700 (PDT) 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 RAA19939 for ; Tue, 15 Jun 1999 17:53:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA04881; Tue, 15 Jun 1999 17:53:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA05976; Tue, 15 Jun 1999 17:53:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA13490 for ; Tue, 15 Jun 1999 17:47:21 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA14093 for ; Tue, 15 Jun 1999 17:47:20 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA29859 for ; Tue, 15 Jun 1999 20:47:19 -0400 (EDT) Message-Id: Date: Tue, 15 Jun 1999 20:47:19 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't agree. I think that it's a perfectly reasonable suggestion, and one that the developers will consider and decide whether or not they want to implement it. The fact that it can be configurable is an even better thing, as if you don't like it you don't have to use it. This is very useful b/c I know I've inadvertently forgotten the subject _many_ times and would like such a reminder! Thanks Nancy! BINO On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > If you want that, maybe you may want to change the code by yourself. I > think it is personal preference if you want to write or not a subject. When > you send personal letters through the mail (the old fashion way, with > stamps), you don't write a subject outside of them, so this tells me > sometimes it is not necessary. In any case if you want to change the > message go to "reply.c" and change line 1285 to the "right message" > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > 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, 15 Jun 1999 17:58:37 -0700 (PDT) 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 RAA19987 for ; Tue, 15 Jun 1999 17:58:36 -0700 (PDT) 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 RAA29264; Tue, 15 Jun 1999 17:58:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA27698; Tue, 15 Jun 1999 17:58:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA40902 for ; Tue, 15 Jun 1999 17:52:51 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA31691 for ; Tue, 15 Jun 1999 17:52:50 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA29992; Tue, 15 Jun 1999 20:51:50 -0400 (EDT) Message-Id: Date: Tue, 15 Jun 1999 20:51:50 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Re: Request: showing flags in message text window In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Definitely. It was a good idea orginally, and making it configurable would be perfect. What's the problem with that? The point about acronyms is silly anyway as this will change nothing for people who don't want it... BINO On Tue, 8 Jun 1999, Jessica Rasku wrote: > > Scott, you live in a country where acronyms are an acceptable way of > > communication. This is not the case in other countries, where a word is > > worth its value. I use IMAPSTATUS since a long time and find it useful even > > for a newbie (you are being condescending here). In any case, pine > > developers have the last word about it. We'll see in future releases in > > your prayers were listened. In my own opinion, it's not worth to waste the > > time improving the already excellent presentation of the program. > > I believe that what was being said is that having things > configurable is important to the people who have used pine for a ``while'' > (I have used it myself for around 7 years (not exclusively mind you)). I > personanly like that things are configurable, I don't think that it is > that large of a ``resource hog'' to make things configurable (putting > unneeded features in is what does that), so, why not make changes > configurable? > > Jessica > > -- > Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, > LinuxBox: (250) 362-9668. > > List manager: majordomo@ArmispianSystems.Rossland.bc.ca > send command help ---- To get help with majordomo > or lists ---- To get a list of all lists on server. > > WWW: > > 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, 16 Jun 1999 06:41:56 -0700 (PDT) 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 CAA26418 for ; Wed, 16 Jun 1999 02:15:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA04008; Wed, 16 Jun 1999 02:15:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA15237; Wed, 16 Jun 1999 02:15:15 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA40708 for ; Wed, 16 Jun 1999 02:10:48 -0700 Received: from bru-noc.net (root@satanas.bru-noc.net [195.74.192.146]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA27583 for ; Wed, 16 Jun 1999 02:10:47 -0700 Received: from satanas.bru-noc.net (satanas.bru-noc.net [195.74.192.146]) by bru-noc.net (8.9.1/8.9.1) with ESMTP id LAA18718 for ; Wed, 16 Jun 1999 11:10:49 +0200 Message-Id: Date: Wed, 16 Jun 1999 11:10:48 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Xavier To: Pine Discussion Forum Subject: Global address book? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi *, Does somebody can give me more info about the global address book usage? I created a local glocal address book: 1. Pine says that the address book it "read only"? 2. How can all the pine users on the system, add entries in the file? X -- Visit: http://3276456082 | ICQ: 8398489 -- ----------------------------------------------------------------- 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, 16 Jun 1999 06:46:31 -0700 (PDT) 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 GAA02583 for ; Wed, 16 Jun 1999 06:46:26 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA15722; Wed, 16 Jun 1999 05:57:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA03756; Wed, 16 Jun 1999 05:57:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA11392 for ; Wed, 16 Jun 1999 05:52:53 -0700 Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA03939 for ; Wed, 16 Jun 1999 05:52:53 -0700 Received: (from uucp@localhost) by mail.ntplx.net (8.9.1/NETPLEX) id IAA23951 for u.washington.edu!pine-info; Wed, 16 Jun 1999 08:52:04 -0400 (EDT) Received: from macdco by mail.ntplx.net; Wed, 16 Jun 1999 08:52 EDT Message-Id: Date: Wed, 16 Jun 1999 08:52:04 -0400 (EDT) >Date: Wed, 16 Jun 1999 08:54:11 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Giannelli To: Pine Discussion Forum Subject: Re: Global address book? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dcg@macdco.com X-To: Xavier X-Cc: Pine Discussion Forum X-Sender: dcg@macdco X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Xavier, we update this file with custom applications where we store in tables additional information (addresses, phone#, relationships, etc.) about our business contacts. The custom apps are designed to update the pine "global address book" each time information is modified or added to this "Business Contact Table". Our "Business Contact Table" is editable by our entire company. Updating the global address book is easy as it is a text file which stores "Name", "Nickname", "E-Mail Address". David Giannelli On Wed, 16 Jun 1999, Xavier wrote: > Hi *, > > Does somebody can give me more info about the global address book usage? > I created a local glocal address book: > > 1. Pine says that the address book it "read only"? > > 2. How can all the pine users on the system, add entries in the file? > > X > > -- > Visit: http://3276456082 | ICQ: 8398489 > > -- > ----------------------------------------------------------------- > 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, 16 Jun 1999 08:48:54 -0700 (PDT) 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 IAA06027 for ; Wed, 16 Jun 1999 08:48:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA19599; Wed, 16 Jun 1999 08:48:50 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA23897; Wed, 16 Jun 1999 08:48:23 -0700 Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA31994 for ; Wed, 16 Jun 1999 08:43:39 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15250; Wed, 16 Jun 1999 08:43:38 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA08386; Wed, 16 Jun 1999 08:43:37 -0700 Message-Id: Date: Wed, 16 Jun 1999 08:43:37 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Global address book? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Xavier X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Xavier wrote: > Hi *, > > Does somebody can give me more info about the global address book usage? > I created a local glocal address book: > > 1. Pine says that the address book it "read only"? > > 2. How can all the pine users on the system, add entries in the file? > > X > Pine always makes global address books read-only. You have to set it up as a personal address book or us another program if you want to be able to add entries. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 16 Jun 1999 13:56:12 -0700 (PDT) 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 NAA14369 for ; Wed, 16 Jun 1999 13:56:11 -0700 (PDT) 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 NAA19651; Wed, 16 Jun 1999 13:56:09 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA29044; Wed, 16 Jun 1999 13:55:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA40810 for ; Wed, 16 Jun 1999 13:51:10 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA32309 for ; Wed, 16 Jun 1999 13:51:10 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id NAA06704 for ; Wed, 16 Jun 1999 13:51:09 -0700 (PDT) Message-Id: Date: Wed, 16 Jun 1999 13:51:07 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would hate that Pine take the place of a mom and told me what to do. I do hate when posting to a newsgroup already and pine complains about not having written a subject. I do not find absolutely necessary a configuration like that. Maybe someone will ask next for a message like "Spelling not checked, check now?" or "Message contains only your signature, send anyway?". I do not think this is necessary, not even to configure. I would really hate this kind of behavior in Pine. I do not find the subject is the important part of the message. I am not completely sure of this, but I suppose that you can use procamil to detect messages that do not contain a subject and change them to whatever you like, why do you need pine to be the police? Eduardo http://www.math.washington.edu/~chappa/personal.html *** Bino Gopal (bino@columbia.edu) wrote on Jun 15, 1999: :) I don't agree. I think that it's a perfectly reasonable suggestion, and :) one that the developers will consider and decide whether or not they want :) to implement it. The fact that it can be configurable is an even better :) thing, as if you don't like it you don't have to use it. This is very :) useful b/c I know I've inadvertently forgotten the subject _many_ times :) and would like such a reminder! Thanks Nancy! :) :) BINO :) :) :) On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: :) :) > If you want that, maybe you may want to change the code by yourself. I :) > think it is personal preference if you want to write or not a subject. When :) > you send personal letters through the mail (the old fashion way, with :) > stamps), you don't write a subject outside of them, so this tells me :) > sometimes it is not necessary. In any case if you want to change the :) > message go to "reply.c" and change line 1285 to the "right message" :) > :) > Eduardo :) > http://www.math.washington.edu/~chappa/personal.html :) > :) 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, 16 Jun 1999 14:09:29 -0700 (PDT) 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 OAA14676 for ; Wed, 16 Jun 1999 14:09:28 -0700 (PDT) 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 OAA20030; Wed, 16 Jun 1999 14:09:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA29738; Wed, 16 Jun 1999 14:09:09 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA20574 for ; Wed, 16 Jun 1999 14:04:33 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA40868; Wed, 16 Jun 1999 14:04:33 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA34574; Wed, 16 Jun 1999 14:04:32 -0700 Message-Id: Date: Wed, 16 Jun 1999 14:04:32 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I agree that such nagging should not be the default behavior. But I would like to be able to configure Pine to automatically spell-check before sending. And I wouldn't mind some of those nagging things, although I find the "Your message will be posted to thousands of people" quite annoying. That should be configurable, too. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > I would hate that Pine take the place of a mom and told me what to do. I > do hate when posting to a newsgroup already and pine complains about not > having written a subject. I do not find absolutely necessary a > configuration like that. Maybe someone will ask next for a message like > "Spelling not checked, check now?" or "Message contains only your > signature, send anyway?". I do not think this is necessary, not even to > configure. I would really hate this kind of behavior in Pine. > > I do not find the subject is the important part of the message. I am not > completely sure of this, but I suppose that you can use procamil to detect > messages that do not contain a subject and change them to whatever you > like, why do you need pine to be the police? > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > > > *** Bino Gopal (bino@columbia.edu) wrote on Jun 15, 1999: > > :) I don't agree. I think that it's a perfectly reasonable suggestion, and > :) one that the developers will consider and decide whether or not they want > :) to implement it. The fact that it can be configurable is an even better > :) thing, as if you don't like it you don't have to use it. This is very > :) useful b/c I know I've inadvertently forgotten the subject _many_ times > :) and would like such a reminder! Thanks Nancy! > :) > :) BINO > :) > :) > :) On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > :) > :) > If you want that, maybe you may want to change the code by yourself. I > :) > think it is personal preference if you want to write or not a subject. When > :) > you send personal letters through the mail (the old fashion way, with > :) > stamps), you don't write a subject outside of them, so this tells me > :) > sometimes it is not necessary. In any case if you want to change the > :) > message go to "reply.c" and change line 1285 to the "right message" > :) > > :) > Eduardo > :) > http://www.math.washington.edu/~chappa/personal.html > :) > > :) > > > 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, 16 Jun 1999 14:17:27 -0700 (PDT) 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 OAA14936 for ; Wed, 16 Jun 1999 14:17:26 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA20318; Wed, 16 Jun 1999 14:17:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA23853; Wed, 16 Jun 1999 14:16:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA34846 for ; Wed, 16 Jun 1999 14:12:41 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA03158 for ; Wed, 16 Jun 1999 14:12:38 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id VAA02190; Wed, 16 Jun 1999 21:17:42 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 14:17 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id OAA26202; Wed, 16 Jun 1999 14:04:53 -0700 Message-Id: Date: Wed, 16 Jun 1999 14:04:51 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > I do not find the subject is the important part of the message. I am not > completely sure of this, but I suppose that you can use procamil to detect > messages that do not contain a subject and change them to whatever you > like, why do you need pine to be the police? Hey, I have a problem with what is at least the default behaviour when posting to a newsgroup. Mind you, I've never really used Pine as a newsreader (I don't know that it makes a good newsreader). I agree that these features shouldn't be imposed on us, but how many features are there in Pine that MOST people don't use? I know there are a great many I don't use, but I still don't complain. Sure, code what you want into Pine, but if you don't want a feature you can just as easily go into the code and do that yourself... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 14:21:42 -0700 (PDT) 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 OAA14996 for ; Wed, 16 Jun 1999 14:21:41 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA29089; Wed, 16 Jun 1999 14:21:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA07415; Wed, 16 Jun 1999 14:21:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA34396 for ; Wed, 16 Jun 1999 14:14:36 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA03430; Wed, 16 Jun 1999 14:14:36 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id OAA07883; Wed, 16 Jun 1999 14:14:35 -0700 (PDT) Message-Id: Date: Wed, 16 Jun 1999 14:14:33 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I know that checkspelling is a good idea before sending a message, so if you are really thinking of adding this, please remember that there are some people out there that needs to write e-mail messages in more than one language, and it would be really annoying to have to either use the same checkspeller for all messages or select the checkspeller on the fly (or configure it with roles or nicknames or whatever method you decide. I do not write all my messages to the same person in a unique language). I do prefer the behavior that pine has today about spelling, but adding a configurable spelling seems to be a good idea, though. Eduardo http://www.math.washington.edu/~chappa/personal.html *** Scott Leibrand (leibrand@u.washington.edu) wrote Today: :) I agree that such nagging should not be the default behavior. But I would :) like to be able to configure Pine to automatically spell-check before :) sending. And I wouldn't mind some of those nagging things, although I :) find the "Your message will be posted to thousands of people" quite :) annoying. That should be configurable, too. :) :) -- :) Scott Leibrand :) leibrand@u.washington.edu :) How to contact me: :) http://students.washington.edu/leibrand/howtocontactme.html :) * RCW 19.190 notice: This email address is located in Washington State. * :) * Unsolicited commercial email may be billed $500 per message. * :) :) On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: :) :) > I would hate that Pine take the place of a mom and told me what to do. I :) > do hate when posting to a newsgroup already and pine complains about not :) > having written a subject. I do not find absolutely necessary a :) > configuration like that. Maybe someone will ask next for a message like :) > "Spelling not checked, check now?" or "Message contains only your :) > signature, send anyway?". I do not think this is necessary, not even to :) > configure. I would really hate this kind of behavior in Pine. :) > :) > I do not find the subject is the important part of the message. I am not :) > completely sure of this, but I suppose that you can use procamil to detect :) > messages that do not contain a subject and change them to whatever you :) > like, why do you need pine to be the police? :) > :) > Eduardo :) > http://www.math.washington.edu/~chappa/personal.html :) > :) > :) > *** Bino Gopal (bino@columbia.edu) wrote on Jun 15, 1999: :) > :) > :) I don't agree. I think that it's a perfectly reasonable suggestion, and :) > :) one that the developers will consider and decide whether or not they wan :) > :) to implement it. The fact that it can be configurable is an even better :) > :) thing, as if you don't like it you don't have to use it. This is very :) > :) useful b/c I know I've inadvertently forgotten the subject _many_ times :) > :) and would like such a reminder! Thanks Nancy! :) > :) :) > :) BINO :) > :) :) > :) :) > :) On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: :) > :) :) > :) > If you want that, maybe you may want to change the code by yourself. I :) > :) > think it is personal preference if you want to write or not a subject. :) > :) > you send personal letters through the mail (the old fashion way, with :) > :) > stamps), you don't write a subject outside of them, so this tells me :) > :) > sometimes it is not necessary. In any case if you want to change the :) > :) > message go to "reply.c" and change line 1285 to the "right message" :) > :) > :) > :) > Eduardo :) > :) > http://www.math.washington.edu/~chappa/personal.html :) > :) > :) > :) :) > :) > :) > :) 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, 16 Jun 1999 14:34:25 -0700 (PDT) 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 OAA15229 for ; Wed, 16 Jun 1999 14:34:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA20817; Wed, 16 Jun 1999 14:34:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA08031; Wed, 16 Jun 1999 14:34:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA31310 for ; Wed, 16 Jun 1999 14:29:28 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA01494 for ; Wed, 16 Jun 1999 14:29:27 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id OAA08638; Wed, 16 Jun 1999 14:29:19 -0700 (PDT) Message-Id: Date: Wed, 16 Jun 1999 14:29:16 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jessica Rasku (jrasku@ArmispianSystems.Rossland.bc.ca) wrote Today: :) On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: :) :) > I do not find the subject is the important part of the message. I am not :) > completely sure of this, but I suppose that you can use procamil to detect :) > messages that do not contain a subject and change them to whatever you :) > like, why do you need pine to be the police? :) :) Hey, I have a problem with what is at least the default behaviour :) when posting to a newsgroup. Mind you, I've never really used Pine as a :) newsreader (I don't know that it makes a good newsreader). I agree that :) these features shouldn't be imposed on us, but how many features are there :) in Pine that MOST people don't use? I know there are a great many I don't :) use, but I still don't complain. Sure, code what you want into Pine, but :) if you don't want a feature you can just as easily go into the code and do :) that yourself... Thanks for supporting my point: hack the code for whatever you don't like, which was my original point. The fact that "most" users don't use the configuration (no statistics provided by you) does not mean that the rest of us have to suffer unnecessary features. I'm sure all these must not be difficult to add, but I already have to answer at least 3 questions before I can reply to a message. I do not need pine to keep asking me or checking on me. Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 16 Jun 1999 14:50:20 -0700 (PDT) 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 OAA15546 for ; Wed, 16 Jun 1999 14:50:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA21302; Wed, 16 Jun 1999 14:50:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA29547; Wed, 16 Jun 1999 14:49:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA31330 for ; Wed, 16 Jun 1999 14:45:32 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA04106 for ; Wed, 16 Jun 1999 14:45:31 -0700 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 OAA06271 for ; Wed, 16 Jun 1999 14:45:31 -0700 (PDT) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA16766; Wed, 16 Jun 1999 14:45:30 PDT Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA15883; Wed, 16 Jun 1999 14:45:29 PDT Message-Id: Date: Wed, 16 Jun 1999 14:44:56 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: spell checking add-on 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 -- ListProcessor(tm) by CREN I can think of one other spell-checking add-on that I would like - a feature that would disable checking of anything that starts with http, www, or has a @ in it. Something like... [X] Disable spell-checking of URL's [X] Disable spell-checking of email addresses I don't often spell check for that very reason - I hate skipping every unique email name and URL, (While I'm wishing, I'd rather have a more Windows/Eudora/Netscape-like GUI interface with all the same functionality.) Robert On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > I know that checkspelling is a good idea before sending a message, so if > you are really thinking of adding this, please remember that there are some > people out there that needs to write e-mail messages in more than one > language, and it would be really annoying to have to either use the same > checkspeller for all messages or select the checkspeller on the fly (or > configure it with roles or nicknames or whatever method you decide. I do > not write all my messages to the same person in a unique language). I do > prefer the behavior that pine has today about spelling, but adding a > configurable spelling seems to be a good idea, though. > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > > > *** Scott Leibrand (leibrand@u.washington.edu) wrote Today: > > :) I agree that such nagging should not be the default behavior. But I would > :) like to be able to configure Pine to automatically spell-check before > :) sending. And I wouldn't mind some of those nagging things, although I > :) find the "Your message will be posted to thousands of people" quite > :) annoying. That should be configurable, too. > :) > :) -- > :) Scott Leibrand > :) leibrand@u.washington.edu > :) How to contact me: > :) http://students.washington.edu/leibrand/howtocontactme.html > :) * RCW 19.190 notice: This email address is located in Washington State. * > :) * Unsolicited commercial email may be billed $500 per message. * > :) > :) On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > :) > :) > I would hate that Pine take the place of a mom and told me what to do. I > :) > do hate when posting to a newsgroup already and pine complains about not > :) > having written a subject. I do not find absolutely necessary a > :) > configuration like that. Maybe someone will ask next for a message like > :) > "Spelling not checked, check now?" or "Message contains only your > :) > signature, send anyway?". I do not think this is necessary, not even to > :) > configure. I would really hate this kind of behavior in Pine. > :) > > :) > I do not find the subject is the important part of the message. I am not > :) > completely sure of this, but I suppose that you can use procamil to detect > :) > messages that do not contain a subject and change them to whatever you > :) > like, why do you need pine to be the police? > :) > > :) > Eduardo > :) > http://www.math.washington.edu/~chappa/personal.html > :) > > :) > > :) > *** Bino Gopal (bino@columbia.edu) wrote on Jun 15, 1999: > :) > > :) > :) I don't agree. I think that it's a perfectly reasonable suggestion, and > :) > :) one that the developers will consider and decide whether or not they wan > :) > :) to implement it. The fact that it can be configurable is an even better > :) > :) thing, as if you don't like it you don't have to use it. This is very > :) > :) useful b/c I know I've inadvertently forgotten the subject _many_ times > :) > :) and would like such a reminder! Thanks Nancy! > :) > :) > :) > :) BINO > :) > :) > :) > :) > :) > :) On Mon, 7 Jun 1999, Eduardo Chappa L. wrote: > :) > :) > :) > :) > If you want that, maybe you may want to change the code by yourself. I > :) > :) > think it is personal preference if you want to write or not a subject. > :) > :) > you send personal letters through the mail (the old fashion way, with > :) > :) > stamps), you don't write a subject outside of them, so this tells me > :) > :) > sometimes it is not necessary. In any case if you want to change the > :) > :) > message go to "reply.c" and change line 1285 to the "right message" > :) > :) > > :) > :) > Eduardo > :) > :) > http://www.math.washington.edu/~chappa/personal.html > :) > :) > > :) > :) > :) > > :) > > :) > > :) > > > ``````````````````````````````````````````````````````````````````````` ` 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; Wed, 16 Jun 1999 16:08:04 -0700 (PDT) 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 QAA17479 for ; Wed, 16 Jun 1999 16:08:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA23440; Wed, 16 Jun 1999 16:08:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA28108; Wed, 16 Jun 1999 16:07:40 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA26006 for ; Wed, 16 Jun 1999 16:03:10 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA30184; Wed, 16 Jun 1999 16:03:07 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA34720; Wed, 16 Jun 1999 16:03:07 -0700 Message-Id: Date: Wed, 16 Jun 1999 16:03:06 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Jessica Rasku wrote: > On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > > > I do not find the subject is the important part of the message. I am not > > completely sure of this, but I suppose that you can use procamil to detect > > messages that do not contain a subject and change them to whatever you > > like, why do you need pine to be the police? > > Hey, I have a problem with what is at least the default behaviour > when posting to a newsgroup. Mind you, I've never really used Pine as a > newsreader (I don't know that it makes a good newsreader). I agree that > these features shouldn't be imposed on us, but how many features are there > in Pine that MOST people don't use? I know there are a great many I don't > use, but I still don't complain. Sure, code what you want into Pine, but > if you don't want a feature you can just as easily go into the code and do > that yourself... > It's not always quite so simple to simply change the source code. Especially if you use PC-Pine. The source for that just isn't available. So I like things configurable via .pinerc. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 16 Jun 1999 16:18:36 -0700 (PDT) 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 QAA17742 for ; Wed, 16 Jun 1999 16:18:34 -0700 (PDT) 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 QAA32425; Wed, 16 Jun 1999 16:18:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA04821; Wed, 16 Jun 1999 16:18:13 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA22820 for ; Wed, 16 Jun 1999 16:13:44 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA19944; Wed, 16 Jun 1999 16:13:43 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA58594; Wed, 16 Jun 1999 16:13:43 -0700 Message-Id: Date: Wed, 16 Jun 1999 16:13:43 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: spell checking add-on In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Robert Larmon wrote: > I can think of one other spell-checking add-on that I would like - a > feature that would disable checking of anything that starts with http, > www, or has a @ in it. Something like... > > [X] Disable spell-checking of URL's > [X] Disable spell-checking of email addresses > > I don't often spell check for that very reason - I hate skipping every > unique email name and URL. Good idea. > (While I'm wishing, I'd rather have a more > Windows/Eudora/Netscape-like GUI interface with all the same > functionality.) Then why even bother using Pine? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 16 Jun 1999 16:48:07 -0700 (PDT) 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 QAA18489 for ; Wed, 16 Jun 1999 16:48:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA00592; Wed, 16 Jun 1999 16:48:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA29659; Wed, 16 Jun 1999 16:47:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA40906 for ; Wed, 16 Jun 1999 16:43:18 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA26172; Wed, 16 Jun 1999 16:43:17 -0700 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 QAA18464; Wed, 16 Jun 1999 16:43:16 -0700 (PDT) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA17759; Wed, 16 Jun 1999 16:43:15 PDT Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA17652; Wed, 16 Jun 1999 16:43:14 PDT Message-Id: Date: Wed, 16 Jun 1999 16:42:22 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: Re: spell checking add-on In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Scott Leibrand wrote: > On Wed, 16 Jun 1999, Robert Larmon wrote: > > > I can think of one other spell-checking add-on that I would like - a > > feature that would disable checking of anything that starts with http, > > www, or has a @ in it. Something like... > > > > [X] Disable spell-checking of URL's > > [X] Disable spell-checking of email addresses > > > > I don't often spell check for that very reason - I hate skipping every > > unique email name and URL. > > Good idea. > > > (While I'm wishing, I'd rather have a more > > Windows/Eudora/Netscape-like GUI interface with all the same > > functionality.) > > Then why even bother using Pine? Because it's free!!! (and a darn good program too) It also fits our remote needs and is relatively maintenance free. The reason I talk about a more GUI-like interface is that my users are starting to ask why Pine is still using a UNIX-style (they say DOS) interface for their office needs/wants. I have a 40%/60% mix of users who prefer GUI/functionality. Unfortunately for me the 40% are the ones who make the most noise. I'd love to give them a more GUI-ized PC-Pine so that they will be satisfied and I can still use and provide the product that I prefer. I can wish, can't I? :) Sorry for the divergence. Robert 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, 16 Jun 1999 17:46:05 -0700 (PDT) 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 RAA19894 for ; Wed, 16 Jun 1999 17:46:04 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA25929; Wed, 16 Jun 1999 17:46:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA14853; Wed, 16 Jun 1999 17:45:42 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA47154 for ; Wed, 16 Jun 1999 17:41:22 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA23506; Wed, 16 Jun 1999 17:41:21 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA51378; Wed, 16 Jun 1999 17:41:20 -0700 Message-Id: Date: Wed, 16 Jun 1999 17:41:20 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: spell checking add-on In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Robert Larmon wrote: > On Wed, 16 Jun 1999, Scott Leibrand wrote: > > > On Wed, 16 Jun 1999, Robert Larmon wrote: > > > > > I can think of one other spell-checking add-on that I would like - a > > > feature that would disable checking of anything that starts with http, > > > www, or has a @ in it. Something like... > > > > > > [X] Disable spell-checking of URL's > > > [X] Disable spell-checking of email addresses > > > > > > I don't often spell check for that very reason - I hate skipping every > > > unique email name and URL. > > > > Good idea. > > > > > (While I'm wishing, I'd rather have a more > > > Windows/Eudora/Netscape-like GUI interface with all the same > > > functionality.) > > > > Then why even bother using Pine? > > Because it's free!!! (and a darn good program too) It also fits our > remote needs and is relatively maintenance free. > > The reason I talk about a more GUI-like interface is that my users are > starting to ask why Pine is still using a UNIX-style (they say DOS) > interface for their office needs/wants. I have a 40%/60% mix of users who > prefer GUI/functionality. Unfortunately for me the 40% are the ones who > make the most noise. I'd love to give them a more GUI-ized PC-Pine so > that they will be satisfied and I can still use and provide the product > that I prefer. > > I can wish, can't I? :) Sorry for the divergence. > That's ok. I think Netscape and Outlook Express are starting to become petty good e-mail programs to work with Pine when the user wants a windows interface, though. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 16 Jun 1999 18:57:36 -0700 (PDT) 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 SAA20691 for ; Wed, 16 Jun 1999 18:57:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA27140; Wed, 16 Jun 1999 18:57:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA17154; Wed, 16 Jun 1999 18:57:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA25972 for ; Wed, 16 Jun 1999 18:52:15 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA02820 for ; Wed, 16 Jun 1999 18:52:13 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id BAA04086; Thu, 17 Jun 1999 01:57:14 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 18:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id SAA28221; Wed, 16 Jun 1999 18:46:34 -0700 Message-Id: Date: Wed, 16 Jun 1999 18:46:34 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > Thanks for supporting my point: hack the code for whatever you don't > like, which was my original point. The fact that "most" users don't use the > configuration (no statistics provided by you) does not mean that the rest > of us have to suffer unnecessary features. I'm sure all these must not be > difficult to add, but I already have to answer at least 3 questions before > I can reply to a message. I do not need pine to keep asking me or checking > on me. Well, what I'm sugesting that *YOU* do, is not complain about this, but instead hack the code if it REALLY bothers you that much. I very much was NOT supporting your view. Your view is that we should not have features. So use mail. Use, elm. Use something without features that you don't like. Or even write your own mail package. You could even do it based on the Pine package if you wanted to. Don't complain about feature glut. It runs NICELY on my 486/66. It may not run so nicely on something like an 8086, but those are incredibly rare (but not non-existant), these days. Provided the features can be turned on, or off, through configuration, you SO FAR, are not suffering from excesive features. If you still feel like you are, then hack the code yourself, don't ask the pine development team to do something for *you* that would ``disservice'' many of it's users. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 19:07:05 -0700 (PDT) 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 TAA20852 for ; Wed, 16 Jun 1999 19:07:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA27287; Wed, 16 Jun 1999 19:07:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA04723; Wed, 16 Jun 1999 19:06:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA22928 for ; Wed, 16 Jun 1999 19:02:06 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA03651; Wed, 16 Jun 1999 19:02:04 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id CAA04168; Thu, 17 Jun 1999 02:07:12 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 19:07 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id SAA28344; Wed, 16 Jun 1999 18:56:13 -0700 Message-Id: Date: Wed, 16 Jun 1999 18:56:12 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Scott Leibrand wrote: > It's not always quite so simple to simply change the source code. > Especially if you use PC-Pine. The source for that just isn't available. > So I like things configurable via .pinerc. Oh, I definately agree. I was really just commenting on the person who said ``hack the code if you want this feature, I don't want it'', and saying that *he* could hack the code himself. There IS no source for PC-Pine? Or is it just not easy to get (or is there a problem with the ``hook'' into the tcp-ip stack? I don't think that should be a problem, but maybe...). Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 19:57:21 -0700 (PDT) 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 TAA21334 for ; Wed, 16 Jun 1999 19:57:20 -0700 (PDT) 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 TAA03984; Wed, 16 Jun 1999 19:57:18 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA12957; Wed, 16 Jun 1999 19:56:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA44226 for ; Wed, 16 Jun 1999 19:52:35 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA11887 for ; Wed, 16 Jun 1999 19:52:35 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id CAA04577; Thu, 17 Jun 1999 02:57:44 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 19:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id TAA28519; Wed, 16 Jun 1999 19:12:04 -0700 Message-Id: Date: Wed, 16 Jun 1999 19:12:03 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: spell checking add-on In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Robert Larmon wrote: > > Then why even bother using Pine? > > Because it's free!!! (and a darn good program too) It also fits our > remote needs and is relatively maintenance free. Hm... I'm not sure that this in itself is a good reason... > The reason I talk about a more GUI-like interface is that my users are > starting to ask why Pine is still using a UNIX-style (they say DOS) > interface for their office needs/wants. I have a 40%/60% mix of users who > prefer GUI/functionality. Unfortunately for me the 40% are the ones who > make the most noise. I'd love to give them a more GUI-ized PC-Pine so > that they will be satisfied and I can still use and provide the product > that I prefer. Then why can't you let them use something like Eudora? Why must they use Pine? I LIKE pine, and I like that it is text mode. I would stick with the version that I was at, if it ever went gui. Even if it still provided a text mode. I know that a lot of energy goes into development of a GUI, and I don't want to see that energy taken away from the general development of Pine. > I can wish, can't I? :) Sorry for the divergence. You certianly can. But I think you will find that the vast majority of Pine users don't want a graphical version. There are various reasons, but that really doesn't matter... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 20:01:47 -0700 (PDT) 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 UAA21419 for ; Wed, 16 Jun 1999 20:01:46 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA04075; Wed, 16 Jun 1999 20:01:44 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA11394; Wed, 16 Jun 1999 20:01:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA47310 for ; Wed, 16 Jun 1999 19:52:37 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA14418 for ; Wed, 16 Jun 1999 19:52:35 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id CAA04573; Thu, 17 Jun 1999 02:57:43 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 19:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id TAA28456; Wed, 16 Jun 1999 19:06:20 -0700 Message-Id: Date: Wed, 16 Jun 1999 19:06:20 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Spell Checking... (was Re: Suggestion: blank subject header) In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > I know that checkspelling is a good idea before sending a message, so if > you are really thinking of adding this, please remember that there are some > people out there that needs to write e-mail messages in more than one > language, and it would be really annoying to have to either use the same > checkspeller for all messages or select the checkspeller on the fly (or > configure it with roles or nicknames or whatever method you decide. I do > not write all my messages to the same person in a unique language). I do > prefer the behavior that pine has today about spelling, but adding a > configurable spelling seems to be a good idea, though. Here is a feature that I personaly would consider a feature glut. Not, having the ability to do as you say above, configure the spell checker as you wish. But, to integrate a spell checker into pine. I know that people on a PC system, may not have a stand alone spell checker (this sort of philosophy has to change in the PC world I think), but if the pine development team wants to create a spell checker, make it entirely stand alone. I'm not sure if the message editor, (which I understand is pico), is totaly stand alone, or if it is compiled into the program, or how it works, but it is nice that pico is avalable stand alone. Even though I don't like Pico (it's fine for most of my message writing though). Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 20:10:17 -0700 (PDT) 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 UAA21582 for ; Wed, 16 Jun 1999 20:10:16 -0700 (PDT) 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 UAA04219; Wed, 16 Jun 1999 20:10:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA13458; Wed, 16 Jun 1999 20:09:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA22690 for ; Wed, 16 Jun 1999 20:05:39 -0700 Received: from mail.asianexplorer.com.au (asi24111-2.gw.connect.com.au [202.21.8.207]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id UAA15444 for ; Wed, 16 Jun 1999 20:05:37 -0700 Received: from florence (unverified [192.168.1.80]) by mail.asianexplorer.com.au (Rockliffe SMTPRA 2.1.7) with SMTP id ; Thu, 17 Jun 1999 13:11:53 +1000 Received: by localhost with Microsoft MAPI; Thu, 17 Jun 1999 13:00:26 +1000 Message-Id: <01BEB8C1.5E99F6E0.florence@asianexplorer.com.au> Date: Thu, 17 Jun 1999 13:00:26 +1000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florence Lee To: Pine Discussion Forum Subject: RE: spell checking add-on MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'Jessica Rasku'" , Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN THE last time we installed pine, it took 6 months...it's very technical... anybody finds it hard to install pine... -----Original Message----- From: Jessica Rasku [SMTP:jrasku@ArmispianSystems.Rossland.bc.ca] Sent: Thursday, 17 June 1999 12:12 To: Pine Discussion Forum Subject: Re: spell checking add-on On Wed, 16 Jun 1999, Robert Larmon wrote: > > Then why even bother using Pine? > > Because it's free!!! (and a darn good program too) It also fits our > remote needs and is relatively maintenance free. Hm... I'm not sure that this in itself is a good reason... > The reason I talk about a more GUI-like interface is that my users are > starting to ask why Pine is still using a UNIX-style (they say DOS) > interface for their office needs/wants. I have a 40%/60% mix of users who > prefer GUI/functionality. Unfortunately for me the 40% are the ones who > make the most noise. I'd love to give them a more GUI-ized PC-Pine so > that they will be satisfied and I can still use and provide the product > that I prefer. Then why can't you let them use something like Eudora? Why must they use Pine? I LIKE pine, and I like that it is text mode. I would stick with the version that I was at, if it ever went gui. Even if it still provided a text mode. I know that a lot of energy goes into development of a GUI, and I don't want to see that energy taken away from the general development of Pine. > I can wish, can't I? :) Sorry for the divergence. You certianly can. But I think you will find that the vast majority of Pine users don't want a graphical version. There are various reasons, but that really doesn't matter... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 20:14:31 -0700 (PDT) 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 UAA17493 for ; Wed, 16 Jun 1999 20:14:30 -0700 (PDT) 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 UAA04272; Wed, 16 Jun 1999 20:14:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id UAA13575; Wed, 16 Jun 1999 20:14:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA31252 for ; Wed, 16 Jun 1999 20:07:44 -0700 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.06) with ESMTP id UAA08832 for ; Wed, 16 Jun 1999 20:07:43 -0700 Received: from mail.asianexplorer.com.au (asi24111-2.gw.connect.com.au [202.21.8.207]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id UAA04180 for ; Wed, 16 Jun 1999 20:07:42 -0700 Received: from florence (unverified [192.168.1.80]) by mail.asianexplorer.com.au (Rockliffe SMTPRA 2.1.7) with SMTP id for ; Thu, 17 Jun 1999 13:13:59 +1000 Received: by localhost with Microsoft MAPI; Thu, 17 Jun 1999 13:02:33 +1000 Message-Id: <01BEB8C1.A9CDFA80.florence@asianexplorer.com.au> Date: Thu, 17 Jun 1999 13:02:32 +1000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Florence Lee To: Pine Discussion Forum Subject: halyfax MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-To: "'pine-usergroup'" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -------------------------------------------------------------------------------------------------------------- anybody using above product..it's intergrated or can be intergrated with pine Thanks & Regards Florence -- ----------------------------------------------------------------- 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, 16 Jun 1999 22:19:05 -0700 (PDT) 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 WAA22648 for ; Wed, 16 Jun 1999 22:19:04 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA06099; Wed, 16 Jun 1999 22:19:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA21963; Wed, 16 Jun 1999 22:18:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA24112 for ; Wed, 16 Jun 1999 22:12:48 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA18833 for ; Wed, 16 Jun 1999 22:12:48 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA05573; Thu, 17 Jun 1999 05:17:25 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 16 Jun 99 22:17 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA30214; Wed, 16 Jun 1999 22:03:19 -0700 Message-Id: Date: Wed, 16 Jun 1999 22:03:18 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: spell checking add-on In-Reply-To: <01BEB8C1.5E99F6E0.florence@asianexplorer.com.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Florence Lee X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Florence Lee wrote: > THE last time we installed pine, it took 6 months...it's very technical... > anybody finds it hard to install pine... The last time I installed Pine it took about 20 minutes, including compile time, etc. Maybe I am just totaly clueless and don't realise that these sorts of things should take months, not minutes. Saying that anybody finds it hard to install is totaly incorrect, as I for one found it to be incredibly plesant to install. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jun 1999 22:39:37 -0700 (PDT) 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 WAA22854 for ; Wed, 16 Jun 1999 22:39:36 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA30369; Wed, 16 Jun 1999 22:39:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA09932; Wed, 16 Jun 1999 22:39:03 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA32104 for ; Wed, 16 Jun 1999 22:34:47 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA25704 for ; Wed, 16 Jun 1999 22:34:47 -0700 Received: from goedel1.math.washington.edu (chappa@goedel1.math.washington.edu [128.95.224.2]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id WAA21673; Wed, 16 Jun 1999 22:34:45 -0700 (PDT) Message-Id: Date: Wed, 16 Jun 1999 22:34:42 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Oh Jessica, You are giving me a good laugh here, no ofense intended. I never asked for the famous feature, i opposed it. I do not need to hack the code, I want it to stay as it is. I guess you arrived late to this thread, so I excuse you, I hope you excuse my laugh too. Eduardo http://www.math.washington.edu/~chappa/personal.html *** Jessica Rasku (jrasku@ArmispianSystems.Rossland.bc.ca) wrote Today: :) On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: :) :) > Thanks for supporting my point: hack the code for whatever you don't :) > like, which was my original point. The fact that "most" users don't use the :) > configuration (no statistics provided by you) does not mean that the rest :) > of us have to suffer unnecessary features. I'm sure all these must not be :) > difficult to add, but I already have to answer at least 3 questions before :) > I can reply to a message. I do not need pine to keep asking me or checking :) > on me. :) :) Well, what I'm sugesting that *YOU* do, is not complain about :) this, but instead hack the code if it REALLY bothers you that much. I :) very much was NOT supporting your view. Your view is that we should not :) have features. So use mail. Use, elm. Use something without features :) that you don't like. Or even write your own mail package. You could even :) do it based on the Pine package if you wanted to. Don't complain about :) feature glut. It runs NICELY on my 486/66. It may not run so nicely on :) something like an 8086, but those are incredibly rare (but not :) non-existant), these days. Provided the features can be turned on, or :) off, through configuration, you SO FAR, are not suffering from excesive :) features. If you still feel like you are, then hack the code yourself, :) don't ask the pine development team to do something for *you* that would :) ``disservice'' many of it's users. :) :) Jessica :) :) -- :) Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, :) LinuxBox: (250) 362-9668. :) :) List manager: majordomo@ArmispianSystems.Rossland.bc.ca :) send command help ---- To get help with majordomo :) or lists ---- To get a list of all lists on server. :) :) WWW: :) :) 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, 16 Jun 1999 23:00:01 -0700 (PDT) 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 XAA23006 for ; Wed, 16 Jun 1999 23:00:00 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA06744; Wed, 16 Jun 1999 22:59:58 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA22765; Wed, 16 Jun 1999 22:59:10 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA32196 for ; Wed, 16 Jun 1999 22:55:07 -0700 Received: from sttlpop1.sttl.uswest.net (sttlpop1.sttl.uswest.net [206.81.192.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id WAA15663 for ; Wed, 16 Jun 1999 22:55:07 -0700 Received: (qmail 24069 invoked by alias); 17 Jun 1999 05:55:03 -0000 Received: (qmail 24043 invoked by uid 0); 17 Jun 1999 05:55:02 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop1.sttl.uswest.net with SMTP; 17 Jun 1999 05:55:02 -0000 Message-Id: Date: Wed, 16 Jun 1999 22:53:49 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: PC-Pine's GUI (was: spell checking add-on) (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Robert Larmon wrote: > > Then why even bother using Pine? > > Because it's free!!! (and a darn good program too) It also fits our > remote needs and is relatively maintenance free. > > The reason I talk about a more GUI-like interface is that my users are > starting to ask why Pine is still using a UNIX-style (they say DOS) > interface for their office needs/wants. I have a 40%/60% mix of users who > prefer GUI/functionality. Unfortunately for me the 40% are the ones who > make the most noise. I'd love to give them a more GUI-ized PC-Pine so > that they will be satisfied and I can still use and provide the product > that I prefer. Robert, This is an issue of interest to many of us. Is it fair to say that PC-Pine's viability is purely a question of aesthetics (we agree that PC-Pine is a bit homely in appearance :), or are there any specific GUI amenities your folks are looking for? Here's the current PC-Pine GUI check list: Mouse can be used in lieu of command keys Mouse can be used to select text, select messages, set marks, etc Right mouse button gives context-sensitive pop-up command list Toolbar (choice of top or bottom) Pull down menu Option for separate message viewing window Embedded URL recognition and browser dispatch Scroll-bars Dialogue boxes (though some of these are a bit rough) GUI font and color selection (though only monospaced fonts so far) Windows-based spell-checker Anything else? Of course a cardinal design goal of PC-Pine is to never *force* you to take your hands off the keyboard, so the idea is to provide all of the GUI capabilities while retaining full keyboard functionality. Comments welcome. -teg 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, 17 Jun 1999 08:56:38 -0700 (PDT) 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 IAA04674 for ; Thu, 17 Jun 1999 08:56:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA16514; Thu, 17 Jun 1999 08:56:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA26882; Thu, 17 Jun 1999 08:56:15 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA31402 for ; Thu, 17 Jun 1999 08:51:03 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA32579 for ; Thu, 17 Jun 1999 08:51:02 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id KAA19223; Thu, 17 Jun 1999 10:50:57 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 1999 10:50:57 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: Re: halyfax In-Reply-To: <01BEB8C1.A9CDFA80.florence@asianexplorer.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Florence Lee X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Florence Lee wrote: > anybody using above product..it's intergrated or can be intergrated with pine I assume the product is called 'halyfax'. I've never heard of it, but I was curious about what it was. I searched altavista and *nothing* came up. Are you sure you spelled it correctly? 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; Thu, 17 Jun 1999 09:09:35 -0700 (PDT) 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 JAA05017 for ; Thu, 17 Jun 1999 09:09:33 -0700 (PDT) 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 JAA08196; Thu, 17 Jun 1999 09:09:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA28826; Thu, 17 Jun 1999 09:09:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA22422 for ; Thu, 17 Jun 1999 09:04:25 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA28909 for ; Thu, 17 Jun 1999 09:04:22 -0700 Received: by gw.learjet.com; id LAA19029; Thu, 17 Jun 1999 11:04:16 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma018888; Thu, 17 Jun 99 11:03:23 -0500 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 LAA27428; Thu, 17 Jun 1999 11:03:22 -0500 (CDT) Received: from localhost (schaller@localhost) by hx02.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id LAA27783; Thu, 17 Jun 1999 11:03:21 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 1999 11:03:21 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff To: Pine Discussion Forum Subject: Re: halyfax In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Miller X-Cc: Pine Discussion Forum X-Authentication-Warning: hx02.learjet.com: schaller owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Mike Miller wrote: > On Thu, 17 Jun 1999, Florence Lee wrote: > > > anybody using above product..it's intergrated or can be > > intergrated with pine > > I assume the product is called 'halyfax'. I've never heard of it, but I > was curious about what it was. I searched altavista and *nothing* came > up. "Hylafax" http://www.hylafax.org/index.html A search for "pine" on the main site found 0 matches. There were 6 matches on their mailing list archives. I would suggest trying their mailing list: http://www.hylafax.org/mailing-lists.html -jeff -- .~. | Jeff Schaller /V\ | Phone = (316) 946-7255, Fax = x2809 // \\ | HP-UX Client/Server /( )\ | I do not speak for the <`~'> | Bombardier Aerospace Group. 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, 17 Jun 1999 10:08:36 -0700 (PDT) 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 KAA06410 for ; Thu, 17 Jun 1999 10:08:35 -0700 (PDT) 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 KAA09996; Thu, 17 Jun 1999 10:08:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA01317; Thu, 17 Jun 1999 10:08:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA41048 for ; Thu, 17 Jun 1999 10:02:34 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA10368 for ; Thu, 17 Jun 1999 10:02:33 -0700 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 KAA05375; Thu, 17 Jun 1999 10:02:25 -0700 (PDT) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA21102; Thu, 17 Jun 1999 10:02:24 PDT Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA23009; Thu, 17 Jun 1999 10:02:23 PDT Message-Id: Date: Thu, 17 Jun 1999 10:00:43 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: Re: spell checking add-on In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Jessica Rasku wrote: > On Wed, 16 Jun 1999, Robert Larmon wrote: > > > > Then why even bother using Pine? > > > > Because it's free!!! (and a darn good program too) It also fits our > > remote needs and is relatively maintenance free. > > Hm... I'm not sure that this in itself is a good reason... Jessica, Thanks for your opinion, but since I'm the one that supports it at my location, please allow me to make that decision. Forgive me for not stating that those were not the only reasons. If you would like a comprehensive list of why we use Pine, let me know privately and I will supply you with a list. > > > The reason I talk about a more GUI-like interface is that my users are > > starting to ask why Pine is still using a UNIX-style (they say DOS) > > interface for their office needs/wants. I have a 40%/60% mix of users who > > prefer GUI/functionality. Unfortunately for me the 40% are the ones who > > make the most noise. I'd love to give them a more GUI-ized PC-Pine so > > that they will be satisfied and I can still use and provide the product > > that I prefer. > > Then why can't you let them use something like Eudora? Why must > they use Pine? I LIKE pine, and I like that it is text mode. I would > stick with the version that I was at, if it ever went gui. Even if it > still provided a text mode. I know that a lot of energy goes into > development of a GUI, and I don't want to see that energy taken away from > the general development of Pine. See my comment above. > > > I can wish, can't I? :) Sorry for the divergence. > > You certianly can. But I think you will find that the vast > majority of Pine users don't want a graphical version. There are various > reasons, but that really doesn't matter... Did you ever think about being able to give users a choice between a less 'homely' GUI PC-Pine vs the existing one? That's why it's called a wish list. I would also like to point out that unless you can back up your claim of what 'users don't want' with some serious statistics, it's nothing more than just a claim. Now if you said "'majority of Pine users' on this list," I would agree emphatically. My concern is that I would have to stop providing Pine to my users because of aesthetic reasons. If aesthetics didn't matter, then why do projects like GNOME for Linux exist? Yes, it adds more functionality, but if that was all GNOME was about it too would look like PC-Pine or an old X-Windows. Whether I personally like/dislike a better GUI is irrelevant - it's about providing the best service to my users and part of that is the aesthetics. PC-Pine is a heck of a lot more popular here with it's Windows integration and web viewing capabilities than regular Pine. I see a natural trend, in general for any product, to become more integrated with the OS (Micro$loth makes a lot of $$$ off this concept), which means in Pine's case that the GUI has to improve as well. Pine may not be the best solution for us 2-3 years down the road, but I sure would like it to be. Features are definitely more important, but that last 10-20% of aesthetics and refinement are important too. If I err in this email please forgive me, but I don't think I should have to defend my own opinions in the first place. Robert p.s. If you (or anyone else) would like to discuss this topic further with me, please feel free to email me personally off-list. Otherwise I consider this discussion closed. 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, 17 Jun 1999 10:24:09 -0700 (PDT) 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 KAA06685 for ; Thu, 17 Jun 1999 10:24:08 -0700 (PDT) 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 KAA19160; Thu, 17 Jun 1999 10:24:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA02039; Thu, 17 Jun 1999 10:23:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18992 for ; Thu, 17 Jun 1999 10:18:55 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA13224 for ; Thu, 17 Jun 1999 10:18:54 -0700 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 KAA10434; Thu, 17 Jun 1999 10:18:53 -0700 (PDT) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA21274; Thu, 17 Jun 1999 10:18:50 PDT Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA23376; Thu, 17 Jun 1999 10:18:49 PDT Message-Id: Date: Thu, 17 Jun 1999 10:17:08 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: Re: PC-Pine's GUI (was: spell checking add-on) (fwd) 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: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Terry Gray wrote: > Robert, > This is an issue of interest to many of us. > > Is it fair to say that PC-Pine's viability is purely a question of > aesthetics (we agree that PC-Pine is a bit homely in appearance :), or are > there any specific GUI amenities your folks are looking for? Terry, There are a few minor amenities that my users requested, but all I can remember off the top of my head was a multi-pane view. (i.e. left pane - folderlist OR indexlist, top pane - folderlist OR indexlist, bottom right pane - main text of message) I'll send you more when I can find my list. Otherwise, yes, it is purely a question of aesthetics. I think the support for different fonts beyond mono-spaced would help a lot too. Also, support for web viewing without needing to rely on IE4 installed would be a big plus, esp. since we are delaying Win98 upgrades at least until Win98 SE is stable (maybe by next year? :) Thanks, and I hope this helps, Robert > > Here's the current PC-Pine GUI check list: > > Mouse can be used in lieu of command keys > Mouse can be used to select text, select messages, set marks, etc > Right mouse button gives context-sensitive pop-up command list > Toolbar (choice of top or bottom) > Pull down menu > Option for separate message viewing window > Embedded URL recognition and browser dispatch > Scroll-bars > Dialogue boxes (though some of these are a bit rough) > GUI font and color selection (though only monospaced fonts so far) > Windows-based spell-checker > > Anything else? > > Of course a cardinal design goal of PC-Pine is to never *force* you to > take your hands off the keyboard, so the idea is to provide all of the GUI > capabilities while retaining full keyboard functionality. > > Comments welcome. > > -teg > > ``````````````````````````````````````````````````````````````````````` ` 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; Thu, 17 Jun 1999 10:42:50 -0700 (PDT) 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 KAA07090 for ; Thu, 17 Jun 1999 10:42:49 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10931; Thu, 17 Jun 1999 10:42:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA01000; Thu, 17 Jun 1999 10:42:00 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA35460 for ; Thu, 17 Jun 1999 10:37:19 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA19718; Thu, 17 Jun 1999 10:37:19 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10078; Thu, 17 Jun 1999 10:37:18 -0700 Message-Id: Date: Thu, 17 Jun 1999 10:37:18 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nope, there is no PC-specific source code for Pine 4.0 and above. All I remember is that it was because some of the code they used was copyrighted by someone else. Search comp.mail.pine at www.deja.com if you want to read about it. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Wed, 16 Jun 1999, Jessica Rasku wrote: > On Wed, 16 Jun 1999, Scott Leibrand wrote: > > > It's not always quite so simple to simply change the source code. > > Especially if you use PC-Pine. The source for that just isn't available. > > So I like things configurable via .pinerc. > > Oh, I definately agree. I was really just commenting on the > person who said ``hack the code if you want this feature, I don't want > it'', and saying that *he* could hack the code himself. There IS no > source for PC-Pine? Or is it just not easy to get (or is there a problem > with the ``hook'' into the tcp-ip stack? I don't think that should be a > problem, but maybe...). > > Jessica > > 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, 17 Jun 1999 10:50:46 -0700 (PDT) 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 KAA07415 for ; Thu, 17 Jun 1999 10:50:43 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA20105; Thu, 17 Jun 1999 10:50:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA01296; Thu, 17 Jun 1999 10:50:26 -0700 Received: from jason01.u.washington.edu (root@jason01.u.washington.edu [140.142.70.24]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA28882 for ; Thu, 17 Jun 1999 10:45:23 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA36288; Thu, 17 Jun 1999 10:45:22 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA10210; Thu, 17 Jun 1999 10:45:21 -0700 Message-Id: Date: Thu, 17 Jun 1999 10:45:21 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Spell Checking... (was Re: Suggestion: blank subject header) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Jessica Rasku wrote: > Here is a feature that I personaly would consider a feature glut. > Not, having the ability to do as you say above, configure the spell > checker as you wish. But, to integrate a spell checker into pine. I > know that people on a PC system, may not have a stand alone spell checker > (this sort of philosophy has to change in the PC world I think), but if > the pine development team wants to create a spell checker, make it > entirely stand alone. I'm not sure if the message editor, (which I > understand is pico), is totaly stand alone, or if it is compiled into the > program, or how it works, but it is nice that pico is avalable stand > alone. Even though I don't like Pico (it's fine for most of my message > writing though). > I agree 100%. The PC-Pine spell-checker sucks compared to ispell. But I still think that Pine/Pico should be able to be configured to press ^T before sending. That way you could set up your dictionary to include whatever languages you want. Would that accomplish what you guys want? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 17 Jun 1999 11:00:44 -0700 (PDT) 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 LAA07735 for ; Thu, 17 Jun 1999 11:00:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA11516; Thu, 17 Jun 1999 11:00:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA09475; Thu, 17 Jun 1999 11:00:22 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA32052 for ; Thu, 17 Jun 1999 10:55:36 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA43664; Thu, 17 Jun 1999 10:55:34 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA06048; Thu, 17 Jun 1999 10:55:33 -0700 Message-Id: Date: Thu, 17 Jun 1999 10:55:33 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: PC-Pine's GUI (was: spell checking add-on) (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Terry Gray wrote: > Robert, > This is an issue of interest to many of us. > > Is it fair to say that PC-Pine's viability is purely a question of > aesthetics (we agree that PC-Pine is a bit homely in appearance :), or are > there any specific GUI amenities your folks are looking for? > > Here's the current PC-Pine GUI check list: > > Mouse can be used in lieu of command keys > Mouse can be used to select text, select messages, set marks, etc > Right mouse button gives context-sensitive pop-up command list > Toolbar (choice of top or bottom) > Pull down menu > Option for separate message viewing window > Embedded URL recognition and browser dispatch > Scroll-bars > Dialogue boxes (though some of these are a bit rough) > GUI font and color selection (though only monospaced fonts so far) > Windows-based spell-checker > > Anything else? > > Of course a cardinal design goal of PC-Pine is to never *force* you to > take your hands off the keyboard, so the idea is to provide all of the GUI > capabilities while retaining full keyboard functionality. > > Comments welcome. > > -teg > I think you guys have done a very good job with PC-Pine, but there are still a couple things on my PC-Pine-specific wish list. Firstly, I wish there were some way for PC-Pine to behave more intelligently over a slow modem link. As it is now, Pine will sit there for 10-30 seconds doing something, and not even tell us what it's doing. I'd like to be able to see what it's doing that's taking so long, cancel it if I feel like it, and most of all, be able to do things that don't require network traffic while Pine is waiting for a response. I realize that many of these problems are at the level of Windows' networking protocols, but I still think you can work around that and accomplish most of what I listed. Secondly, I'd like to see stand-alone spell-checkers like ispell available for DOS that we could configure PC-Pine to use. In my opinion, PC-Pine's integrated spell-checker violates your cardinal design rule: it forces users to use the mouse, or at least go through an unwieldy sequence of tabs, etc. to accomplish what would just take an A or I in Unix Pine (with ispell). -- Scott Leibrand leibrand@u.washington.edu Student Staff & Training Technical Support Lead University of Washington Computing and Communications How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 17 Jun 1999 11:05:30 -0700 (PDT) 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 LAA07823 for ; Thu, 17 Jun 1999 11:05:29 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA11681; Thu, 17 Jun 1999 11:05:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA09725; Thu, 17 Jun 1999 11:05:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA44184 for ; Thu, 17 Jun 1999 10:57:59 -0700 Received: from viruswall.tc.fluke.com (viruswall.tc.fluke.com [206.138.179.196]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id KAA19007 for ; Thu, 17 Jun 1999 10:57:58 -0700 Received: from 129.196.184.7 by viruswall.tc.fluke.com (InterScan E-Mail VirusWall NT); Thu, 17 Jun 1999 09:02:49 -0800 Received: from dd.tc.fluke.com (root@dd.tc.fluke.com [129.196.148.100]) by mailhub.tc.fluke.com (8.9.1/8.9.1) with ESMTP id JAA18863; Thu, 17 Jun 1999 09:02:48 -0700 (PDT) Received: from localhost (dcd@localhost [127.0.0.1]) by dd.tc.fluke.com (8.8.5/8.6.12) with ESMTP id JAA02028; Thu, 17 Jun 1999 09:02:48 -0700 Message-Id: Date: Thu, 17 Jun 1999 09:02:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Dyck To: Pine Discussion Forum Subject: Re: halyfax In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Miller X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Perhaps they are refering to: HylaFAX telecommunication software. HylaFAX is used for sending and receiving facsimiles as well as for sending alpha-numeric pages. http://www.hylafax.org/ On Thu, 17 Jun 1999, Mike Miller wrote: > Date: Thu, 17 Jun 1999 08:50:57 -0700 > From: Mike Miller > To: Pine Discussion Forum > Subject: Re: halyfax > > On Thu, 17 Jun 1999, Florence Lee wrote: > > > anybody using above product..it's intergrated or can be intergrated with pine > > I assume the product is called 'halyfax'. I've never heard of it, but I > was curious about what it was. I searched altavista and *nothing* came > up. > > Are you sure you spelled it correctly? > > 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; Thu, 17 Jun 1999 12:37:22 -0700 (PDT) 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 MAA09803 for ; Thu, 17 Jun 1999 12:37:21 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA13956; Thu, 17 Jun 1999 12:37:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA12636; Thu, 17 Jun 1999 12:36:58 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA32124 for ; Thu, 17 Jun 1999 12:32:08 -0700 Received: from lark.cc.ukans.edu (root@lark.cc.ukans.edu [129.237.34.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA27906 for ; Thu, 17 Jun 1999 12:32:07 -0700 Received: from falcon.cc.ukans.edu by lark.cc.ukans.edu (8.8.7/1.1.8.2/12Jan95-0207PM) id OAA0000003101; Thu, 17 Jun 1999 14:32:06 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 1999 14:32:06 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carine Ullom To: Pine Discussion Forum Subject: folder collections MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: cullom@falcon.cc.ukans.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, We're just upgraded from v. 3.95 to 4.10 on UNIX. Problem: When I attempt to save a read message, I am unable to advance to another folder collection using ^N. No error, just no response. All other ^n functions seem to work fine. Any ideas? Carine Carine Ullom Software Training Specialist Academic Computing Services University of Kansas Computer Center Lawrence, KS 66045 PH: 785-864-0467 FX: 785-864-0485 e-mail: carine@ukans.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; Thu, 17 Jun 1999 12:50:58 -0700 (PDT) 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 MAA09971 for ; Thu, 17 Jun 1999 12:50:56 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA14315; Thu, 17 Jun 1999 12:50:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA05518; Thu, 17 Jun 1999 12:50:33 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA38220 for ; Thu, 17 Jun 1999 12:45:19 -0700 Received: from min.net (root@min.net [208.222.210.19]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA02336 for ; Thu, 17 Jun 1999 12:45:19 -0700 Received: from min.net (berman@min.net [208.222.210.19]) by min.net (8.9.3/8.9.3) with ESMTP id PAA27682 for ; Thu, 17 Jun 1999 15:45:18 -0400 (EDT) Message-Id: Date: Thu, 17 Jun 1999 15:45:17 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Morris Berman To: Pine Discussion Forum Subject: Msg Advance in New Folder MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We are running Pine 4.05L. Previously, when I would 'tab' into a new folder in my "inbox" collection, the cursor would be positioned at the 1st unread message. Now, w/o intentional modification to the configuration by me, my cursor is set at the 1st msg in the folder instead of the 1st unread msg. I have searched the configuration parameters for one that looks like it would control this behaviour, but I can't find a suitable parameter. What would couse this behaviour and how can I reset it? -Mb ------------------------------------------------------------------------------- Morris Berman, berman@min.net '96 Kawasaki GPz1100, '82 GS650GL (DoD #1237), Scuba, Skiing, AMA (M/C) #446884 ------------------------------------------------------------------------------- No one is responsible for what I say...well, OK, maybe me. Managers are like cats in a litter box. They're always rearranging trying to cover up what they've done. --Scott Adams -- ----------------------------------------------------------------- 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, 17 Jun 1999 13:10:03 -0700 (PDT) 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 NAA10257 for ; Thu, 17 Jun 1999 13:10:02 -0700 (PDT) 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 NAA14812; Thu, 17 Jun 1999 13:10:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA08023; Thu, 17 Jun 1999 13:09:30 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA20596 for ; Thu, 17 Jun 1999 13:03:00 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA22340 for ; Thu, 17 Jun 1999 13:02:58 -0700 Received: by gw.learjet.com; id PAA11292; Thu, 17 Jun 1999 15:02:56 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma011277; Thu, 17 Jun 99 15:02:51 -0500 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 PAA21846; Thu, 17 Jun 1999 15:02:50 -0500 (CDT) Received: from localhost (schaller@localhost) by hx02.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id PAA00241; Thu, 17 Jun 1999 15:02:49 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 1999 15:02:49 -0500 (CDT) Reply-To: Jeff Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff To: Pine Discussion Forum Subject: Re: Msg Advance in New Folder In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Morris Berman X-Cc: Pine Info List X-Authentication-Warning: hx02.learjet.com: schaller owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Morris Berman wrote: > Previously, when I would 'tab' into a new folder in my "inbox" collection, > the cursor would be positioned at the 1st unread message. > > Now, w/o intentional modification to the configuration by me, my cursor is > set at the 1st msg in the folder instead of the 1st unread msg. While I haven't seen that exact behavior, I have seen: 1) TAB to a folder with new messages. 2) TAB again (or go back to INBOX) without reading any of those new messages. 3) TAB again (to look for folders with new messages), and the folder that you saw before in (1) won't be opened, even though it has unread messages. As far as your specific behavior, each time I open a folder with new messages in it, the cursor is placed on the first new message (not necessarily the _first_ message). Using pine 3.96 for hp-ux. -- .~. | Jeff Schaller /V\ | Phone = (316) 946-7255, Fax = x2809 // \\ | HP-UX Client/Server /( )\ | I do not speak for the <`~'> | Bombardier Aerospace Group. 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, 17 Jun 1999 13:15:30 -0700 (PDT) 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 NAA10363 for ; Thu, 17 Jun 1999 13:15:29 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA14955; Thu, 17 Jun 1999 13:15:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA01630; Thu, 17 Jun 1999 13:14:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA38774 for ; Thu, 17 Jun 1999 13:04:18 -0700 Received: from lark.cc.ukans.edu (root@lark.cc.ukans.edu [129.237.34.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA22540 for ; Thu, 17 Jun 1999 13:04:18 -0700 Received: from falcon.cc.ukans.edu by lark.cc.ukans.edu (8.8.7/1.1.8.2/12Jan95-0207PM) id PAA0000015836; Thu, 17 Jun 1999 15:04:17 -0500 (CDT) Message-Id: Date: Thu, 17 Jun 1999 15:04:17 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Carine Ullom To: Pine Discussion Forum Subject: folder collections solved MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: cullom@falcon.cc.ukans.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, I've solved my own problem but thought I'd post it for the benefit of others. Original problem: Pine 4.10 wouldn't allow me to move between folder collections after updgrading from 3.95 (UNIX). Solution/Explanation: My 3.95 version of Pine had 'hand made' folder groups before they were known as collections. Evidently, during the upgrade, when the folder collection list was created, all of my collections were given the same name (Mail on server.edu). Thus, Pine saw them as all the same collection and therefore had nothing to advance to (^N) when attempting to save to a collection other than the current one. Clear as mud? Carine Carine Ullom Software Training Specialist Academic Computing Services University of Kansas Computer Center Lawrence, KS 66045 PH: 785-864-0467 FX: 785-864-0485 e-mail: carine@ukans.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; Thu, 17 Jun 1999 15:28:56 -0700 (PDT) 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 PAA13032 for ; Thu, 17 Jun 1999 15:28:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27218; Thu, 17 Jun 1999 15:28:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA12234; Thu, 17 Jun 1999 15:28:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA31418 for ; Thu, 17 Jun 1999 15:22:41 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA23844 for ; Thu, 17 Jun 1999 15:22:36 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id WAA14632; Thu, 17 Jun 1999 22:27:32 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 17 Jun 99 15:27 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA00402; Thu, 17 Jun 1999 15:14:03 -0700 Message-Id: Date: Thu, 17 Jun 1999 15:14:02 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Suggestion: blank subject header In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 16 Jun 1999, Eduardo Chappa L. wrote: > Oh Jessica, > > You are giving me a good laugh here, no ofense intended. I never asked > for the famous feature, i opposed it. I do not need to hack the code, I > want it to stay as it is. I guess you arrived late to this thread, so I > excuse you, I hope you excuse my laugh too. You sugested that some features be removed. If you feel that I ``came late'' I'd like to inform you that I've been on this list since just prior to the release of 4.10 (I picked up the 4.05 source, and subscribed at the same time, then when I started recieving messages from the list, it was fairly quick that I was seeing messages about 4.10). Your total missunderstanding, I don't really understand. I have NEVER sugested that you asked for any feature. I in fact indicated that with YOUR opposition to features, instead of sugesting to people who have politely sugested that some features would be nice that they should hack the code, you could more easily hack the code yourself if you are so opposed to the features. Or, create an entirely new mailer for yourself. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 17 Jun 1999 15:35:35 -0700 (PDT) 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 PAA13129 for ; Thu, 17 Jun 1999 15:35:34 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA18506; Thu, 17 Jun 1999 15:35:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA12690; Thu, 17 Jun 1999 15:35:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA42216 for ; Thu, 17 Jun 1999 15:29:49 -0700 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.06) with ESMTP id PAA21280 for ; Thu, 17 Jun 1999 15:29:48 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27245 for ; Thu, 17 Jun 1999 15:29:48 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA22184 for ; Thu, 17 Jun 1999 15:29:47 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA52968 for ; Thu, 17 Jun 1999 15:29:46 -0700 Message-Id: Date: Thu, 17 Jun 1999 15:29:46 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Msg Advance in New Folder MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Morris Berman wrote: > We are running Pine 4.05L. > Previously, when I would 'tab' into a new folder in my "inbox" collection, > the cursor would be positioned at the 1st unread message. > > Now, w/o intentional modification to the configuration by me, my cursor is > set at the 1st msg in the folder instead of the 1st unread msg. > > I have searched the configuration parameters for one that looks like it > would control this behaviour, but I can't find a suitable parameter. > > What would couse this behaviour and how can I reset it? > > -Mb Here's the one I think you want: OPTION: incoming-startup-rule This value affects Pine's behavior when opening the "INBOX" or one of the "INCOMING MESSAGE FOLDERS". By default, when the "INBOX" or another incoming folder is first opened, the current message is set to the first unseen message which has not been marked deleted, or the last message if all of the messages have been seen previously. The four possible values for this option are: first-unseen This is the default described above. first-recent Similar to the default, but rather than starting on the first unseen message Pine starts you on the first recent message. A message is recent if it arrived since the last time the folder was open. This value causes the current message to be set to the first recent and undeleted message if there is one, otherwise the last message in the folder. First Simply starts you on the first undeleted message in the folder. If all messages are deleted you start on the last message. Last Simply starts you on the last undeleted message in the folder If all messages are deleted you start on the last message. Hope that helps, -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 17 Jun 1999 15:57:42 -0700 (PDT) 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 PAA13620 for ; Thu, 17 Jun 1999 15:57:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA27957; Thu, 17 Jun 1999 15:57:40 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA13646; Thu, 17 Jun 1999 15:57:20 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA37508 for ; Thu, 17 Jun 1999 15:52:33 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA29339 for ; Thu, 17 Jun 1999 15:52:32 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id WAA14839; Thu, 17 Jun 1999 22:57:38 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 17 Jun 99 15:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA00706; Thu, 17 Jun 1999 15:46:03 -0700 Message-Id: Date: Thu, 17 Jun 1999 15:46:02 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: folder collections solved In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Carine Ullom X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Carine Ullom wrote: > Hello, > I've solved my own problem but thought I'd post it for the benefit of > others. > Original problem: > Pine 4.10 wouldn't allow me to move between folder collections after > updgrading from 3.95 (UNIX). > > Solution/Explanation: > My 3.95 version of Pine had 'hand made' folder groups before they were > known as collections. Evidently, during the upgrade, when the folder > collection list was created, all of my collections were given the same > name (Mail on server.edu). Thus, Pine saw them as all the same collection > and therefore had nothing to advance to (^N) when attempting to save to a > collection other than the current one. Clear as mud? It's clear to me that you don't have the problem quite sussed out. It WAS changing, but because they just had the ``name'' portion as the same, you simply couldn't see it. The same thing happenend to me, I thought it wasn't changing, but on further examination, I could see that it actually was changing, just I couldn't see it. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 20 Jun 1999 12:14:17 -0700 (PDT) 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 MAA19475 for ; Sun, 20 Jun 1999 12:14:16 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA14268; Sun, 20 Jun 1999 12:14:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA27246; Sun, 20 Jun 1999 12:13:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA51584 for ; Sun, 20 Jun 1999 12:08:27 -0700 Received: from sunny.zdv.uni-tuebingen.de (sunny.zdv.uni-tuebingen.de [134.2.3.45]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA17734 for ; Sun, 20 Jun 1999 12:08:25 -0700 Received: from localhost (zrawo01@localhost) by sunny.zdv.uni-tuebingen.de (8.9.3/8.9.3) with ESMTP id VAA19433 for ; Sun, 20 Jun 1999 21:11:42 +0200 Message-Id: Date: Sun, 20 Jun 1999 21:11:41 +0200 (MEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Thomas Woerner To: Pine Discussion Forum Subject: pine-4.10-ssl In-Reply-To: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="42347779-1037901879-929905901=:16913" X-To: Pine Discussion Forum X-Authentication-Warning: sunny.zdv.uni-tuebingen.de: zrawo01 owned process doing -bs X-Sender: zrawo01@sunny.zdv.uni-tuebingen.de X-Listprocessor-Version: 8.1 -- 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. --42347779-1037901879-929905901=:16913 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, I have made a patch for pine-4.10 to work with OpenSSL-0.9.3a. It works fine for Linux (glibc), HPUX-10 and HPUX-11 - others not tested, yet. Features If pine is configured to make a connection to an imap server, it will first try to connect via SSL to port 993 (imaps) of the server. If this SSL connection fails the 'normal' uncrypted connection will be tried. Build Compile and install OpenSSL-0.9.3a Set the OPENSSLDIR if you have not installed in /usr/local/ssl (default) Extract the pine4.10 source Apply the patch: go into the pine directory and type 'patch -p1 < ../pine4.10-ssl.diff' Build pine: build lxs (for Linux) build hps (for HPUX) Ciao -tom- __ __ T h o m a s W o e r n e r _/ / ___ ____ Zentrum fuer Datenverarbeitung (ZDV) / _// _ \/ \ Wilhelmstrasse 106, 72074 Tuebingen, GERMANY / /_/ // / / / / EMAIL: thomas.woerner@zdv.uni-tuebingen.de \__/\___/_/_/_/ ROOM: 019 PHONE: +49-7071-2970281 ___________________________________________________________________________ --42347779-1037901879-929905901=:16913 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="pine4.10-ssl.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="pine4.10-ssl.diff" ZGlmZiAtY3JOIHBpbmU0LjEwL2J1aWxkIHBpbmU0LjEwLXNzbC9idWlsZA0K KioqIHBpbmU0LjEwL2J1aWxkCVdlZCBEZWMgMTYgMDA6NTM6MjkgMTk5OA0K LS0tIHBpbmU0LjEwLXNzbC9idWlsZAlTdW4gSnVuIDIwIDE3OjA5OjU1IDE5 OTkNCioqKioqKioqKioqKioqKg0KKioqIDEwMiwxMDcgKioqKg0KLS0tIDEw MiwxMDkgLS0tLQ0KICAgIA0KICBFT0YNCiAgICAgICAgICAgICAgICAgICAN CisgT1BFTlNTTERJUj0ke09QRU5TU0xESVI6LSIvdXNyL2xvY2FsL3NzbCJ9 DQorIGV4cG9ydCBPUEVOU1NMRElSDQogIA0KICAjIElmIG5vIGFyZ3MsIGJ1 aWxkIHdoYXQgd2FzIGJ1aWx0IGxhc3QgdGltZS4NCiAgaWYgWyAkIyAtZXEg MCBdDQoqKioqKioqKioqKioqKioNCioqKiAxOTYsMjAxICoqKioNCi0tLSAx OTgsMjA0IC0tLS0NCiAgICAgZ3M0KSBjY2x0YXJnPWdzbzsgICAgICAgcGlj b3Rhcmc9Z3NvOyAgICAgICBwaW5ldGFyZz0kbWFrZXRhcmcgOzsNCiAgICAg Z3M1KSBjY2x0YXJnPWdzbzsgICAgICAgcGljb3Rhcmc9Z3NvOyAgICAgICBw aW5ldGFyZz0kbWFrZXRhcmcgOzsNCiAgICAgaHB4KSBjY2x0YXJnPSRtYWtl dGFyZzsgcGljb3Rhcmc9aHBwOyAgICAgICBwaW5ldGFyZz0kbWFrZXRhcmcg OzsNCisgICAgaHBzKSBjY2x0YXJnPSRtYWtldGFyZzsgcGljb3Rhcmc9aHBw OyAgICAgICBwaW5ldGFyZz1ocHggOzsNCiAgICAgaHhkKSBjY2x0YXJnPSRt YWtldGFyZzsgcGljb3Rhcmc9aHBwOyAgICAgICBwaW5ldGFyZz1ocHggOzsN CiAgICAgbG5wKSBjY2x0YXJnPSRtYWtldGFyZzsgcGljb3Rhcmc9bG54OyAg ICAgICBwaW5ldGFyZz0kcGljb3RhcmcgOzsNCiAgICAgbngzKSBjY2x0YXJn PSRtYWtldGFyZzsgcGljb3Rhcmc9bnh0OyAgICAgICBwaW5ldGFyZz0kcGlj b3RhcmcgOzsNCioqKioqKioqKioqKioqKg0KKioqIDIwNSwyMTAgKioqKg0K LS0tIDIwOCwyMTQgLS0tLQ0KICAgICBzbHgpIGNjbHRhcmc9JG1ha2V0YXJn OyBwaWNvdGFyZz1sbng7ICAgICAgIHBpbmV0YXJnPSRwaWNvdGFyZyA7Ow0K ICAgICBzbDQpIGNjbHRhcmc9JG1ha2V0YXJnOyBwaWNvdGFyZz1sbng7ICAg ICAgIHBpbmV0YXJnPSRwaWNvdGFyZyA7Ow0KICAgICBzbDUpIGNjbHRhcmc9 JG1ha2V0YXJnOyBwaWNvdGFyZz1sbng7ICAgICAgIHBpbmV0YXJnPSRwaWNv dGFyZyA7Ow0KKyAgICBseHMpIGNjbHRhcmc9JG1ha2V0YXJnOyBwaWNvdGFy Zz1sbng7ICAgICAgIHBpbmV0YXJnPSRtYWtldGFyZyA7Ow0KICAgICBzbzQp IGNjbHRhcmc9c29sOyAgICAgICBwaWNvdGFyZz1zb2w7ICAgICAgIHBpbmV0 YXJnPSRtYWtldGFyZyA7Ow0KICAgICBzbzUpIGNjbHRhcmc9c29sOyAgICAg ICBwaWNvdGFyZz1zb2w7ICAgICAgIHBpbmV0YXJnPSRtYWtldGFyZyA7Ow0K ICAgICBzb3MpIGNjbHRhcmc9JG1ha2V0YXJnOyBwaWNvdGFyZz1vc2Y7ICAg ICAgIHBpbmV0YXJnPSRwaWNvdGFyZyA7Ow0KZGlmZiAtY3JOIHBpbmU0LjEw L2ltYXAvTWFrZWZpbGUgcGluZTQuMTAtc3NsL2ltYXAvTWFrZWZpbGUNCioq KiBwaW5lNC4xMC9pbWFwL01ha2VmaWxlCVRodSBKYW4gMjggMDA6MzM6MTEg MTk5OQ0KLS0tIHBpbmU0LjEwLXNzbC9pbWFwL01ha2VmaWxlCVN1biBKdW4g MjAgMTc6MDk6NTUgMTk5OQ0KKioqKioqKioqKioqKioqDQoqKiogMjQwLDI0 NSAqKioqDQotLS0gMjQwLDI0NiAtLS0tDQogICMgZ3VsCUdDQyBSSVNDIFVs dHJpeCAoREVDLTUwMDApDQogICMgaHBwCUhQLVVYIDkueA0KICAjIGhweAlI UC1VWCAxMC54DQorICMgaHBzCUhQLVVYIDEwLnggd2l0aCBPcGVuU1NMDQog ICMgaHhkCUhQLVVYIDEwLnggd2l0aCBEQ0Ugc2VjdXJpdHkNCiAgIyBpc2MJ SW50ZXJhY3RpdmUgU3lzdGVtcw0KICAjIGxueAlMaW51eCB3aXRoIHRyYWRp dGlvbmFsIHBhc3N3b3JkcyBhbmQgY3J5cHQoKSBpbiB0aGUgQyBsaWJyYXJ5 DQoqKioqKioqKioqKioqKioNCioqKiAyNjMsMjY4ICoqKioNCi0tLSAyNjQs MjcwIC0tLS0NCiAgIyBzbDQJTGludXggdXNpbmcgLWxzaGFkb3cgdG8gZ2V0 IHRoZSBjcnlwdCgpIGZ1bmN0aW9uDQogICMgc2w1CUxpbnV4IHdpdGggc2hh ZG93IHBhc3N3b3Jkcywgbm8gZXh0cmEgbGlicmFyaWVzDQogICMgc2x4CUxp bnV4IHVzaW5nIC1sY3J5cHQgdG8gZ2V0IHRoZSBjcnlwdCgpIGZ1bmN0aW9u DQorICMgbHhzCUxpbnV4IHVzaW5nIC1sY3J5cHQgdG8gZ2V0IHRoZSBjcnlw dCgpIGZ1bmN0aW9uIGFucyBPcGVuU1NMDQogICMgc254CVNpZW1lbnMgTml4 ZG9yZiBTSU5JTlggb3IgUmVsaWFudCBVTklYDQogICMgc29sCVNvbGFyaXMg KHdvbid0IHdvcmsgdW5sZXNzICJ1Y2JjYyIgd29ya3MgLS0gdXNlIGdzbyBp bnN0ZWFkKQ0KICAjIHNvcwlPU0YvMSB3aXRoIFNlY3VyZVdhcmUNCioqKioq KioqKioqKioqKg0KKioqIDI4MywyODkgKioqKg0KICANCiAgIyBOb3RlIG9u IFNDTyB5b3UgbWF5IGhhdmUgdG8gc2V0IExOIHRvICJsbiIuDQogIA0KISBh MzIgYTQxIGFpeCBiczMgYnNmIGJzaSBic28gZC1nIGQ1NCBkcnMgZXB4IGdh cyBnaDkgZ2hwIGdzNSBnc28gZ3N1IGd1bCBocHAgaHB4IGxucCBseW4gbWN0 IG1udCBuZWIgbnh0IG54MyBvc2Ygb3M0IHB0eCBxbnggc2M1IHNjbyBzZ2kg c2hwIHNsNCBzbDUgc2x4IHNueCBzb2wgc29zIHV3MjogYW4NCiAgCSQoQlVJ TEQpIE9TPSRADQogIA0KICAjIElmIHlvdSB1c2Ugc3Y0LCB5b3UgbWF5IGZp bmQgdGhhdCBpdCB3b3JrcyB0byBtb3ZlIGl0IHRvIHVzZSB0aGUgYW4gcHJv Y2Vzcy4NCi0tLSAyODUsMjkxIC0tLS0NCiAgDQogICMgTm90ZSBvbiBTQ08g eW91IG1heSBoYXZlIHRvIHNldCBMTiB0byAibG4iLg0KICANCiEgYTMyIGE0 MSBhaXggYnMzIGJzZiBic2kgYnNvIGQtZyBkNTQgZHJzIGVweCBnYXMgZ2g5 IGdocCBnczUgZ3NvIGdzdSBndWwgaHBwIGhweCBocHMgbG5wIGx5biBtY3Qg bW50IG5lYiBueHQgbngzIG9zZiBvczQgcHR4IHFueCBzYzUgc2NvIHNnaSBz aHAgc2w0IHNsNSBzbHggbHhzIHNueCBzb2wgc29zIHV3MjogYW4NCiAgCSQo QlVJTEQpIE9TPSRADQogIA0KICAjIElmIHlvdSB1c2Ugc3Y0LCB5b3UgbWF5 IGZpbmQgdGhhdCBpdCB3b3JrcyB0byBtb3ZlIGl0IHRvIHVzZSB0aGUgYW4g cHJvY2Vzcy4NCmRpZmYgLWNyTiBwaW5lNC4xMC9pbWFwL3NyYy9vc2RlcC91 bml4L01ha2VmaWxlIHBpbmU0LjEwLXNzbC9pbWFwL3NyYy9vc2RlcC91bml4 L01ha2VmaWxlDQoqKiogcGluZTQuMTAvaW1hcC9zcmMvb3NkZXAvdW5peC9N YWtlZmlsZQlXZWQgSmFuIDI3IDAwOjE5OjE5IDE5OTkNCi0tLSBwaW5lNC4x MC1zc2wvaW1hcC9zcmMvb3NkZXAvdW5peC9NYWtlZmlsZQlTdW4gSnVuIDIw IDE3OjA5OjU1IDE5OTkNCioqKioqKioqKioqKioqKg0KKioqIDMyOCwzMzMg KioqKg0KLS0tIDMyOCwzNDIgLS0tLQ0KICAJIEJBU0VMREZMQUdTPSItbG5l dCAtbFYzIiBcDQogIAkgUkFOTElCPXRydWUNCiAgDQorIGhwczoJIyBIUC1V WCAxMC54IHdpZHRoIE9wZW5TU0wNCisgCSQoQlVJTEQpIGBjYXQgRVhUUkFT UEVDSUFMU2AgT1M9aHBwIFNJR1RZUEU9cHN4IFwNCisgCSBTUE9PTERJUj0v dmFyIFwNCisgCSBBQ1RJVkVGSUxFPS92YXIvbmV3cy9hY3RpdmUgXA0KKyAJ IFJTSFBBVEg9L3Vzci9iaW4vcmVtc2ggXA0KKyAJIEJBU0VDRkxBR1M9Ii1n IC1BZSAtRE5GU0tMVURHRSAtREhBVkVfU1NMIC1JJChPUEVOU1NMRElSKS9p bmNsdWRlL29wZW5zc2wiIFwNCisgCSBCQVNFTERGTEFHUz0iLWxuZXQgLWxW MyAtTCQoT1BFTlNTTERJUikvbGliIC1sc3NsIC1sY3J5cHRvIiBcDQorIAkg UkFOTElCPXRydWUNCisgDQogIGlzYzoJIyBJbnRlcmFjdGl2ZQ0KICAJJChC VUlMRCkgYGNhdCBFWFRSQVNQRUNJQUxTYCBPUz0kQCBTSUdUWVBFPXN2NCBD SEVDS1BXPXN2NCBMT0dJTlBXPXN2NCBcDQogIAkgU1BPT0xESVI9L3Zhci9z cG9vbCBNQUlMU1BPT0w9L3Zhci9tYWlsIFwNCioqKioqKioqKioqKioqKg0K KioqIDQ5Miw0OTggKioqKg0KICAJIFNQT09MRElSPS92YXIvc3Bvb2wgXA0K ICAJIEFDVElWRUZJTEU9L3Zhci9saWIvbmV3cy9hY3RpdmUgXA0KICAJIFJT SFBBVEg9L3Vzci9iaW4vcnNoIFwNCiEgCSBCQVNFQ0ZMQUdTPSItZyAtZm5v LW9taXQtZnJhbWUtcG9pbnRlciAtTzYgLURORlNLTFVER0UiDQogIA0KICBz bng6CSMgU2llbWVucyBOaXhkb3JmIFNJTklYIGFuZCBSZWxpYW50IFVOSVgN CiAgCSQoQlVJTEQpIGBjYXQgRVhUUkFTUEVDSUFMU2AgT1M9c3Y0IFNJR1RZ UEU9cHN4IENIRUNLUFc9c3Y0IFwNCi0tLSA1MDEsNTE2IC0tLS0NCiAgCSBT UE9PTERJUj0vdmFyL3Nwb29sIFwNCiAgCSBBQ1RJVkVGSUxFPS92YXIvbGli L25ld3MvYWN0aXZlIFwNCiAgCSBSU0hQQVRIPS91c3IvYmluL3JzaCBcDQoh IAkgQkFTRUNGTEFHUz0iLWcgLWZuby1vbWl0LWZyYW1lLXBvaW50ZXIgLU82 IC1ETkZTS0xVREdFIiBcDQohIAkgQkFTRUxERkxBR1M9IiINCiEgDQohIGx4 czoJIyBMaW51eCBPcGVuU1NMDQohIAkkKEJVSUxEKSBgY2F0IEVYVFJBU1BF Q0lBTFNgIE9TPXNseCBTSUdUWVBFPXBzeCBDSEVDS1BXPXBzeCBcDQohIAkg U1BPT0xESVI9L3Zhci9zcG9vbCBcDQohIAkgQUNUSVZFRklMRT0vdmFyL2xp Yi9uZXdzL2FjdGl2ZSBcDQohIAkgUlNIUEFUSD0vdXNyL2Jpbi9yc2ggXA0K ISAJIEJBU0VDRkxBR1M9Ii1nIC1mbm8tb21pdC1mcmFtZS1wb2ludGVyIC1P NiAtRE5GU0tMVURHRSAtREhBVkVfU1NMIC1JJChPUEVOU1NMRElSKS9pbmNs dWRlL29wZW5zc2wiIFwNCiEgCSBCQVNFTERGTEFHUz0iLUwkKE9QRU5TU0xE SVIpL2xpYiAtbHNzbCAtbGNyeXB0byINCiAgDQogIHNueDoJIyBTaWVtZW5z IE5peGRvcmYgU0lOSVggYW5kIFJlbGlhbnQgVU5JWA0KICAJJChCVUlMRCkg YGNhdCBFWFRSQVNQRUNJQUxTYCBPUz1zdjQgU0lHVFlQRT1wc3ggQ0hFQ0tQ Vz1zdjQgXA0KZGlmZiAtY3JOIHBpbmU0LjEwL2ltYXAvc3JjL29zZGVwL3Vu aXgvdGNwX3VuaXguYyBwaW5lNC4xMC1zc2wvaW1hcC9zcmMvb3NkZXAvdW5p eC90Y3BfdW5peC5jDQoqKiogcGluZTQuMTAvaW1hcC9zcmMvb3NkZXAvdW5p eC90Y3BfdW5peC5jCVN1biBPY3QgMjUgMTc6Mjg6MDQgMTk5OA0KLS0tIHBp bmU0LjEwLXNzbC9pbWFwL3NyYy9vc2RlcC91bml4L3RjcF91bml4LmMJU3Vu IEp1biAyMCAxNzoxMzo1MyAxOTk5DQoqKioqKioqKioqKioqKioNCioqKiAx MjQsMTMwICoqKioNCiAgICogUmV0dXJuczogVENQL0lQIHN0cmVhbSBpZiBz dWNjZXNzIGVsc2UgTklMDQogICAqLw0KICANCiEgVENQU1RSRUFNICp0Y3Bf b3BlbiAoY2hhciAqaG9zdCxjaGFyICpzZXJ2aWNlLHVuc2lnbmVkIGxvbmcg cG9ydCkNCiAgew0KICAgIFRDUFNUUkVBTSAqc3RyZWFtID0gTklMOw0KICAg IGludCBpLGosc29jazsNCi0tLSAxMjQsMTMwIC0tLS0NCiAgICogUmV0dXJu czogVENQL0lQIHN0cmVhbSBpZiBzdWNjZXNzIGVsc2UgTklMDQogICAqLw0K ICANCiEgVENQU1RSRUFNICpfdGNwX29wZW4gKGNoYXIgKmhvc3QsY2hhciAq c2VydmljZSx1bnNpZ25lZCBsb25nIHBvcnQpDQogIHsNCiAgICBUQ1BTVFJF QU0gKnN0cmVhbSA9IE5JTDsNCiAgICBpbnQgaSxqLHNvY2s7DQoqKioqKioq KioqKioqKioNCioqKiAxMzYsMTQxICoqKioNCi0tLSAxMzYsMTQyIC0tLS0N CiAgICBjaGFyIGhvc3RuYW1lW01BSUxUTVBMRU5dOw0KICAgIGNoYXIgdG1w W01BSUxUTVBMRU5dOw0KICAgIHN0cnVjdCBzZXJ2ZW50ICpzdiA9IE5JTDsN CisgDQogICAgaWYgKHNlcnZpY2UpIHsJCS8qIHNlcnZpY2Ugc3BlY2lmaWVk PyAqLw0KICAgICAgaWYgKCpzZXJ2aWNlID09ICcqJykgewkvKiB5ZXMsIHNw ZWNpYWwgYWx0IGRyaXZlciBrbHVkZ2U/ICovDQogICAgICAgIGN0cnAgPSBO SUw7CQkvKiB5ZXMsIGRvbid0IGRvIG9wZW4gdGltZW91dCAqLw0KKioqKioq KioqKioqKioqDQoqKiogMjA1LDIxNCAqKioqDQogICAgICBpZiAoc3RyZWFt LT5pY3RyID0gY3RyKSAqKHN0cmVhbS0+aXB0ciA9IHN0cmVhbS0+aWJ1Zikg PSB0bXBbMF07DQogIAkJCQkvKiBjb3B5IG9mZmljaWFsIGhvc3QgbmFtZSAq Lw0KICAgICAgc3RyZWFtLT5ob3N0ID0gY3B5c3RyIChob3N0bmFtZSk7DQoh ICAgfQ0KICAgIHJldHVybiBzdHJlYW07CQkvKiByZXR1cm4gc3VjY2VzcyAq Lw0KICB9DQogIAwNCiAgLyogT3BlbiBhIFRDUCBzb2NrZXQNCiAgICogQWNj ZXB0czogSW50ZXJuZXQgc29ja2V0IGFkZHJlc3MgYmxvY2sNCiAgICoJICAg IHNjcmF0Y2ggYnVmZmVyDQotLS0gMjA2LDI4MCAtLS0tDQogICAgICBpZiAo c3RyZWFtLT5pY3RyID0gY3RyKSAqKHN0cmVhbS0+aXB0ciA9IHN0cmVhbS0+ aWJ1ZikgPSB0bXBbMF07DQogIAkJCQkvKiBjb3B5IG9mZmljaWFsIGhvc3Qg bmFtZSAqLw0KICAgICAgc3RyZWFtLT5ob3N0ID0gY3B5c3RyIChob3N0bmFt ZSk7DQohICAgfSAgDQohIA0KICAgIHJldHVybiBzdHJlYW07CQkvKiByZXR1 cm4gc3VjY2VzcyAqLw0KICB9DQogIAwNCisgLyogVENQL0lQIG9wZW4gd3Jh cHBlcg0KKyAgKiBBY2NlcHRzOiBob3N0IG5hbWUNCisgICoJICAgIGNvbnRh Y3Qgc2VydmljZSBuYW1lDQorICAqCSAgICBjb250YWN0IHBvcnQgbnVtYmVy DQorICAqIFJldHVybnM6IFRDUC9JUCBzdHJlYW0gaWYgc3VjY2VzcyBlbHNl IE5JTA0KKyAgKi8NCisgDQorIFRDUFNUUkVBTSAqdGNwX29wZW4gKGNoYXIg Kmhvc3QsY2hhciAqc2VydmljZSx1bnNpZ25lZCBsb25nIHBvcnQpDQorIC8q DQorICAqIHdyYXBwZXIgZm9yIHRjcF9vcGVuOg0KKyAgKiBtYWtlIGEgc3Ns IGNhbGwgaWYgc3VwcG9ydGVkIGFuZCBmYWxsIGJhY2sgdG8gbm9ybWFsIGNv bm5lY3Rpb24gaWYgZmFpbGVkDQorICAqIChjKSAxOTk5IFRob21hcyBXb2Vy bmVyLCBaRFYgVHVlYmluZ2VuIC0gR2VybWFueQ0KKyAgKiAgPHRob21hcy53 b2VybmVyQHpkdi51bmktdHVlYmluZ2VuLmRlPg0KKyAgKi8NCisgew0KKyAg ICAgVENQU1RSRUFNICpzdHJlYW0gPSBOSUw7DQorICNpZmRlZiBIQVZFX1NT TA0KKyAgICAgc3RhdGljIFNTTCAgICAgKnNzbDsNCisgICAgIHN0YXRpYyBT U0xfQ1RYICpzc2xfY3R4Ow0KKyAgICAgY2hhciB0bXBbMTAyNF07DQorIA0K KyAgICAgU1NMX2xvYWRfZXJyb3Jfc3RyaW5ncygpOw0KKyAgICAgU1NMZWF5 X2FkZF9zc2xfYWxnb3JpdGhtcygpOw0KKyAgICAgc3NsX2N0eD1TU0xfQ1RY X25ldyhTU0x2MjNfY2xpZW50X21ldGhvZCgpKTsNCisgICAgIFNTTF9DVFhf c2V0X29wdGlvbnMoc3NsX2N0eCxTU0xfT1BfQUxMKTsNCisgICAgIA0KKyAg ICAgc3NsID0gU1NMX25ldyhzc2xfY3R4KTsNCisgICAgIFNTTF9zZXRfdmVy aWZ5KHNzbCwgU1NMX1ZFUklGWV9OT05FLCBOVUxMKTsNCisgICAgIA0KKyAg ICAgc3RyZWFtID0gX3RjcF9vcGVuKGhvc3QsICJpbWFwcyIsIDk5Myk7DQor ICAgICBpZiAoc3RyZWFtICE9IE5JTCkgew0KKyAJc3RyZWFtLT51c2Vfc3Ns ID0gMTsNCisgCVNTTF9zZXRfZmQoc3NsLCBzdHJlYW0tPnRjcHNpKTsNCisg CQ0KKyAJLy8gdHJ5IHRvIG1ha2UgU1NMIGNvbm5lY3Rpb24NCisgCWlmIChT U0xfY29ubmVjdChzc2wpID4gMCkgew0KKyAvLwkgICAgUHV0TGluZTAoMSwg MCwgIlNTTCIpOw0KKyAJICAgIA0KKyAJICAgIHN0cmVhbS0+Y3R4ID0gc3Ns X2N0eDsNCisgCSAgICBzdHJlYW0tPnNzbCA9IHNzbDsNCisgDQorIAkgICAg cmV0dXJuIHN0cmVhbTsNCisgCX0NCisgCS8vIGNvbm5lY3Rpb24gZmFpbGVk IC4uDQorIAlzdHJlYW0tPnVzZV9zc2wgPSAwOw0KKyAvLwlzcHJpbnRmKHRt cCwgIlNTTF9jb25uZWN0IGVycm9yICVzIiwgRVJSX2Vycm9yX3N0cmluZyhF UlJfZ2V0X2Vycm9yKCksDQorIC8vCQkJCQkJCSAgICAgIE5VTEwpKTsNCisg Ly8JbW1fbG9nKHRtcCwgV0FSTik7DQorIA0KKyAJdGNwX2Nsb3NlKHN0cmVh bSk7DQorICAgICB9IGVsc2Ugew0KKyAJU1NMX2ZyZWUoc3NsKTsNCisgCVNT TF9DVFhfZnJlZShzc2xfY3R4KTsNCisgICAgIH0NCisgDQorICAgICBtbV9s b2coIlNTTCBjb25uZWN0aW9uIGZhaWxlZCAtIGZhbGxpbmcgYmFjayB0byBu b3JtYWwgbW9kZSIsIFdBUk4pOw0KKyAjZW5kaWYgLyogSEFWRV9TU0wgKi8N CisgDQorICAgICBzdHJlYW0tPnVzZV9zc2wgPSAwOw0KKyAgICAgc3RyZWFt ID0gX3RjcF9vcGVuKGhvc3QsIHNlcnZpY2UsIHBvcnQpOw0KKyANCisgICAg IHJldHVybiBzdHJlYW07CQkvKiByZXR1cm4gc3VjY2VzcyAqLw0KKyB9DQor IAwNCiAgLyogT3BlbiBhIFRDUCBzb2NrZXQNCiAgICogQWNjZXB0czogSW50 ZXJuZXQgc29ja2V0IGFkZHJlc3MgYmxvY2sNCiAgICoJICAgIHNjcmF0Y2gg YnVmZmVyDQoqKioqKioqKioqKioqKioNCioqKiAyNjIsMjY3ICoqKioNCi0t LSAzMjgsMzM0IC0tLS0NCiAgICAgICAgY2xvc2UgKHNvY2spOwkJLyogZmx1 c2ggc29ja2V0ICovDQogICAgICAgIHJldHVybiAtMTsNCiAgICAgIH0NCisg DQogICAgICB0bW8udHZfc2VjID0gdHRtb19vcGVuOwkvKiBvcGVuIHRpbWVv dXQgKi8NCiAgICAgIHRtby50dl91c2VjID0gMDsNCiAgICAgIEZEX1pFUk8g KCZmZHMpOwkJLyogaW5pdGlhbGl6ZSBzZWxlY3Rpb24gdmVjdG9yICovDQoq KioqKioqKioqKioqKioNCioqKiAyNzUsMjgxICoqKioNCiAgICAgICAgZmNu dGwgKHNvY2ssRl9TRVRGTCxmbGdzKTsvKiByZXN0b3JlIGJsb2NraW5nIHN0 YXR1cyAqLw0KICAgICAgICAvKiBUaGlzIHVzZWQgdG8gYmUgYSB6ZXJvLWJ5 dGUgcmVhZCgpLCBidXQgdGhhdCBjcmFzaGVzIFNvbGFyaXMgKi8NCiAgCQkJ CS8qIGdldCBzb2NrZXQgc3RhdHVzICovDQohICAgICAgIHdoaWxlICgoKGkg PSAqY3RyID0gcmVhZCAoc29jayx0bXAsMSkpIDwgMCkgJiYgKGVycm5vID09 IEVJTlRSKSk7DQogICAgICB9CQ0KICAgICAgaWYgKGkgPD0gMCkgewkJLyog dGltZW91dCBvciBlcnJvcj8gKi8NCiAgICAgICAgaSA9IGkgPyBlcnJubyA6 IEVUSU1FRE9VVDsvKiBkZXRlcm1pbmUgZXJyb3IgY29kZSAqLw0KLS0tIDM0 MiwzNTAgLS0tLQ0KICAgICAgICBmY250bCAoc29jayxGX1NFVEZMLGZsZ3Mp Oy8qIHJlc3RvcmUgYmxvY2tpbmcgc3RhdHVzICovDQogICAgICAgIC8qIFRo aXMgdXNlZCB0byBiZSBhIHplcm8tYnl0ZSByZWFkKCksIGJ1dCB0aGF0IGNy YXNoZXMgU29sYXJpcyAqLw0KICAJCQkJLyogZ2V0IHNvY2tldCBzdGF0dXMg Ki8NCiEgICAgICAgaSA9IDE7DQohIC8vIHRoaXMgbGluZSBjYXVzZXMgYSBT U0wgcHJvYmxlbXMgOi0oDQohIC8vICAgICAgd2hpbGUgKCgoaSA9ICpjdHIg PSByZWFkIChzb2NrLHRtcCwxKSkgPCAwKSAmJiAoZXJybm8gPT0gRUlOVFIp KTsNCiAgICAgIH0JDQogICAgICBpZiAoaSA8PSAwKSB7CQkvKiB0aW1lb3V0 IG9yIGVycm9yPyAqLw0KICAgICAgICBpID0gaSA/IGVycm5vIDogRVRJTUVE T1VUOy8qIGRldGVybWluZSBlcnJvciBjb2RlICovDQoqKioqKioqKioqKioq KioNCioqKiAyODYsMjkxICoqKioNCi0tLSAzNTUsMzYxIC0tLS0NCiAgICAg ICAgcmV0dXJuIC0xOw0KICAgICAgfQ0KICAgIH0NCisgDQogICAgcmV0dXJu IHNvY2s7CQkJLyogcmV0dXJuIHRoZSBzb2NrZXQgKi8NCiAgfQ0KICAMICAN CioqKioqKioqKioqKioqKg0KKioqIDMyOSwzMzQgKioqKg0KLS0tIDM5OSw0 MDUgLS0tLQ0KICAgIGlmICghcnNocGF0aCkgcnNocGF0aCA9IGNweXN0ciAo UlNIUEFUSCk7DQogICAgaWYgKCFyc2hjb21tYW5kKSByc2hjb21tYW5kID0g Y3B5c3RyICgiJXMgJXMgLWwgJXMgZXhlYyAvZXRjL3Ilc2QiKTsNCiAgCQkJ CS8qIGJ1aWxkIHJzaCBjb21tYW5kICovDQorIA0KICAgIHNwcmludGYgKHRt cCxyc2hjb21tYW5kLHJzaHBhdGgsaG9zdCxtYi0+dXNlclswXSA/IG1iLT51 c2VyIDogbXl1c2VybmFtZSAoKSwNCiAgCSAgIHNlcnZpY2UpOw0KICAgIGZv ciAoaSA9IDEscGF0aCA9IGFyZ3ZbMF0gPSBzdHJ0b2sgKHRtcCwiICIpOw0K KioqKioqKioqKioqKioqDQoqKiogNDg4LDQ5NSAqKioqDQogICAgICAgIGVs c2UgcmV0dXJuIHRjcF9hYm9ydCAoc3RyZWFtKTsNCiAgICAgIH0NCiAgICAg IGVsc2UgaWYgKGkgPCAwKSByZXR1cm4gdGNwX2Fib3J0IChzdHJlYW0pOw0K ISAgICAgd2hpbGUgKCgoaSA9IHJlYWQgKHN0cmVhbS0+dGNwc2ksc3RyZWFt LT5pYnVmLEJVRkxFTikpIDwgMCkgJiYNCiEgCSAgIChlcnJubyA9PSBFSU5U UikpOw0KICAgICAgaWYgKGkgPCAxKSByZXR1cm4gdGNwX2Fib3J0IChzdHJl YW0pOw0KICAgICAgc3RyZWFtLT5pcHRyID0gc3RyZWFtLT5pYnVmOy8qIHBv aW50IGF0IFRDUCBidWZmZXIgKi8NCiAgICAgIHN0cmVhbS0+aWN0ciA9IGk7 CQkvKiBzZXQgbmV3IGJ5dGUgY291bnQgKi8NCi0tLSA1NTksNTc0IC0tLS0N CiAgICAgICAgZWxzZSByZXR1cm4gdGNwX2Fib3J0IChzdHJlYW0pOw0KICAg ICAgfQ0KICAgICAgZWxzZSBpZiAoaSA8IDApIHJldHVybiB0Y3BfYWJvcnQg KHN0cmVhbSk7DQohIA0KISAgICAgaWYgKHN0cmVhbS0+dXNlX3NzbCkgew0K ISAjaWZkZWYgSEFWRV9TU0wNCiEgCXdoaWxlICgoKGkgPSBTU0xfcmVhZCAo c3RyZWFtLT5zc2wsc3RyZWFtLT5pYnVmLEJVRkxFTikpIDwgMCkgJiYNCiEg CSAgICAgICAoZXJybm8gPT0gRUlOVFIpKSBtbV9sb2coc3RyZWFtLT5pYnVm LCBFUlJPUik7DQohICNlbmRpZiAvKiBIQVZFX1NTTCAqLw0KISAgICAgfSBl bHNlDQohIAl3aGlsZSAoKChpID0gcmVhZCAoc3RyZWFtLT50Y3BzaSxzdHJl YW0tPmlidWYsQlVGTEVOKSkgPCAwKSAmJg0KISAJICAgICAgIChlcnJubyA9 PSBFSU5UUikpOw0KISANCiAgICAgIGlmIChpIDwgMSkgcmV0dXJuIHRjcF9h Ym9ydCAoc3RyZWFtKTsNCiAgICAgIHN0cmVhbS0+aXB0ciA9IHN0cmVhbS0+ aWJ1ZjsvKiBwb2ludCBhdCBUQ1AgYnVmZmVyICovDQogICAgICBzdHJlYW0t PmljdHIgPSBpOwkJLyogc2V0IG5ldyBieXRlIGNvdW50ICovDQoqKioqKioq KioqKioqKioNCioqKiA1MzgsNTQ0ICoqKioNCiAgICAgICAgZWxzZSByZXR1 cm4gdGNwX2Fib3J0IChzdHJlYW0pOw0KICAgICAgfQ0KICAgICAgZWxzZSBp ZiAoaSA8IDApIHJldHVybiB0Y3BfYWJvcnQgKHN0cmVhbSk7DQohICAgICB3 aGlsZSAoKChpID0gd3JpdGUgKHN0cmVhbS0+dGNwc28sc3RyaW5nLHNpemUp KSA8IDApICYmIChlcnJubyA9PSBFSU5UUikpOw0KICAgICAgaWYgKGkgPCAw KSByZXR1cm4gdGNwX2Fib3J0IChzdHJlYW0pOw0KICAgICAgc2l6ZSAtPSBp OwkJCS8qIGhvdyBtdWNoIHdlIHNlbnQgKi8NCiAgICAgIHN0cmluZyArPSBp Ow0KLS0tIDYxNyw2MzIgLS0tLQ0KICAgICAgICBlbHNlIHJldHVybiB0Y3Bf YWJvcnQgKHN0cmVhbSk7DQogICAgICB9DQogICAgICBlbHNlIGlmIChpIDwg MCkgcmV0dXJuIHRjcF9hYm9ydCAoc3RyZWFtKTsNCiEgDQohICAgICBpZiAo c3RyZWFtLT51c2Vfc3NsKSB7DQohICNpZmRlZiBIQVZFX1NTTA0KISAJd2hp bGUgKCgoaSA9IFNTTF93cml0ZSAoc3RyZWFtLT5zc2wsc3RyaW5nLHNpemUp KSA8IDApICYmDQohIAkgICAgICAgKGVycm5vID09IEVJTlRSKSk7DQohICNl bmRpZiAvKiBIQVZFX1NTTCAqLw0KISAgICAgfSBlbHNlDQohIAl3aGlsZSAo KChpID0gd3JpdGUgKHN0cmVhbS0+dGNwc28sc3RyaW5nLHNpemUpKSA8IDAp ICYmDQohIAkgICAgICAgKGVycm5vID09IEVJTlRSKSk7DQohIA0KICAgICAg aWYgKGkgPCAwKSByZXR1cm4gdGNwX2Fib3J0IChzdHJlYW0pOw0KICAgICAg c2l6ZSAtPSBpOwkJCS8qIGhvdyBtdWNoIHdlIHNlbnQgKi8NCiAgICAgIHN0 cmluZyArPSBpOw0KZGlmZiAtY3JOIHBpbmU0LjEwL2ltYXAvc3JjL29zZGVw L3VuaXgvdGNwX3VuaXguaCBwaW5lNC4xMC1zc2wvaW1hcC9zcmMvb3NkZXAv dW5peC90Y3BfdW5peC5oDQoqKiogcGluZTQuMTAvaW1hcC9zcmMvb3NkZXAv dW5peC90Y3BfdW5peC5oCVRodSBTZXAgMTcgMDM6MDQ6MDIgMTk5OA0KLS0t IHBpbmU0LjEwLXNzbC9pbWFwL3NyYy9vc2RlcC91bml4L3RjcF91bml4LmgJ U3VuIEp1biAyMCAxNzowOTo1NSAxOTk5DQoqKioqKioqKioqKioqKioNCioq KiAzMyw0NCAqKioqDQogICAqDQogICAqLw0KICANCiAgDQogIC8qIFRDUCBp bnB1dCBidWZmZXIgKi8NCiAgDQogICNkZWZpbmUgQlVGTEVOIDgxOTINCiAg DQotIA0KICAvKiBUQ1AgSS9PIHN0cmVhbSAqLw0KICANCiAgI2RlZmluZSBU Q1BTVFJFQU0gc3RydWN0IHRjcF9zdHJlYW0NCi0tLSAzMyw0OCAtLS0tDQog ICAqDQogICAqLw0KICANCisgI2lmZGVmIEhBVkVfU1NMDQorICNpbmNsdWRl IDxzdGRpby5oPg0KKyAjaW5jbHVkZSAiZXJyLmgiDQorICNpbmNsdWRlICJz c2wuaCINCisgI2VuZGlmIC8qIEhBVkVfU1NMICovDQogIA0KICAvKiBUQ1Ag aW5wdXQgYnVmZmVyICovDQogIA0KICAjZGVmaW5lIEJVRkxFTiA4MTkyDQog IA0KICAvKiBUQ1AgSS9PIHN0cmVhbSAqLw0KICANCiAgI2RlZmluZSBUQ1BT VFJFQU0gc3RydWN0IHRjcF9zdHJlYW0NCioqKioqKioqKioqKioqKg0KKioq IDUyLDU1ICoqKioNCi0tLSA1Niw2NSAtLS0tDQogICAgaW50IGljdHI7CQkJ LyogaW5wdXQgY291bnRlciAqLw0KICAgIGNoYXIgKmlwdHI7CQkJLyogaW5w dXQgcG9pbnRlciAqLw0KICAgIGNoYXIgaWJ1ZltCVUZMRU5dOwkJLyogaW5w dXQgYnVmZmVyICovDQorIA0KKyAgIGludCB1c2Vfc3NsOw0KKyAjaWZkZWYg SEFWRV9TU0wNCisgICBTU0wgICAgICpzc2w7DQorICAgU1NMX0NUWCAqY3R4 Ow0KKyAjZW5kaWYgLyogSEFWRV9TU0wgKi8NCiAgfTsNCmRpZmYgLWNyTiBw aW5lNC4xMC9waWNvL21ha2VmaWxlLmxueCBwaW5lNC4xMC1zc2wvcGljby9t YWtlZmlsZS5sbngNCioqKiBwaW5lNC4xMC9waWNvL21ha2VmaWxlLmxueAlU dWUgSnVuIDMwIDAxOjE3OjM3IDE5OTgNCi0tLSBwaW5lNC4xMC1zc2wvcGlj by9tYWtlZmlsZS5sbngJU3VuIEp1biAyMCAxNzowOTo1NSAxOTk5DQoqKioq KioqKioqKioqKioNCioqKiA0OCw1NCAqKioqDQogIExJQkFSR1M9CXJ1DQog IFJBTkxJQj0JCXJhbmxpYg0KICANCiEgTElCUz0JCSQoRVhUUkFMSUJFUykg LWx0ZXJtY2FwDQogIA0KICBPRklMRVM9CQlhdHRhY2gubyBiYXNpYy5vIGJp bmQubyBicm93c2UubyBidWZmZXIubyBcDQogIAkJY29tcG9zZXIubyBkaXNw bGF5Lm8gZmlsZS5vIGZpbGVpby5vIGxpbmUubyBwaWNvX29zLm8gXA0KLS0t IDQ4LDU0IC0tLS0NCiAgTElCQVJHUz0JcnUNCiAgUkFOTElCPQkJcmFubGli DQogIA0KISBMSUJTPQkJJChFWFRSQUxJQkVTKSAtbG5jdXJzZXMNCiAgDQog IE9GSUxFUz0JCWF0dGFjaC5vIGJhc2ljLm8gYmluZC5vIGJyb3dzZS5vIGJ1 ZmZlci5vIFwNCiAgCQljb21wb3Nlci5vIGRpc3BsYXkubyBmaWxlLm8gZmls ZWlvLm8gbGluZS5vIHBpY29fb3MubyBcDQpkaWZmIC1jck4gcGluZTQuMTAv cGluZS9tYWtlZmlsZS5ocHMgcGluZTQuMTAtc3NsL3BpbmUvbWFrZWZpbGUu aHBzDQoqKiogcGluZTQuMTAvcGluZS9tYWtlZmlsZS5ocHMJVGh1IEphbiAg MSAwMTowMDowMCAxOTcwDQotLS0gcGluZTQuMTAtc3NsL3BpbmUvbWFrZWZp bGUuaHBzCVN1biBKdW4gMjAgMTc6MDk6NTUgMTk5OQ0KKioqKioqKioqKioq KioqDQoqKiogMCAqKioqDQotLS0gMSwxMzQgLS0tLQ0KKyAjICRJZDogbWFr ZWZpbGUuaHBzLHYgNC40MSAxOTk4LzA4LzI3IDE2OjQ5OjMyIGh1YmVydCBF eHAgJA0KKyAjDQorICMgICAgICAgICAgICBUIEggRSAgICBQIEkgTiBFICAg IE0gQSBJIEwgICBTIFkgUyBUIEUgTQ0KKyAjDQorICMgICBMYXVyZW5jZSBM dW5kYmxhZGUgYW5kIE1pa2UgU2VpYmVsDQorICMgICBOZXR3b3JrcyBhbmQg RGlzdHJpYnV0ZWQgQ29tcHV0aW5nDQorICMgICBDb21wdXRpbmcgYW5kIENv bW11bmljYXRpb25zDQorICMgICBVbml2ZXJzaXR5IG9mIFdhc2hpbmd0b24N CisgIyAgIEFkbWluaXN0cmF0aW9uIEJ1aWxkaW5nLCBBRy00NA0KKyAjICAg U2VhdHRsZSwgV2FzaGluZ3RvbiwgOTgxOTUsIFVTQQ0KKyAjICAgSW50ZXJu ZXQ6IGxnbEBDQUMuV2FzaGluZ3Rvbi5FRFUNCisgIyAgICAgICAgICAgICBt aWtlc0BDQUMuV2FzaGluZ3Rvbi5FRFUNCisgIw0KKyAjICAgUGxlYXNlIGFk ZHJlc3MgYWxsIGJ1Z3MgYW5kIGNvbW1lbnRzIHRvICJwaW5lLWJ1Z3NAY2Fj Lndhc2hpbmd0b24uZWR1Ig0KKyAjDQorICMNCisgIyAgIFBpbmUgYW5kIFBp Y28gYXJlIHJlZ2lzdGVyZWQgdHJhZGVtYXJrcyBvZiB0aGUgVW5pdmVyc2l0 eSBvZiBXYXNoaW5ndG9uLg0KKyAjICAgTm8gY29tbWVyY2lhbCB1c2Ugb2Yg dGhlc2UgdHJhZGVtYXJrcyBtYXkgYmUgbWFkZSB3aXRob3V0IHByaW9yIHdy aXR0ZW4NCisgIyAgIHBlcm1pc3Npb24gb2YgdGhlIFVuaXZlcnNpdHkgb2Yg V2FzaGluZ3Rvbi4NCisgIw0KKyAjICAgUGluZSwgUGljbywgYW5kIFBpbG90 IHNvZnR3YXJlIGFuZCBpdHMgaW5jbHVkZWQgdGV4dCBhcmUgQ29weXJpZ2h0 DQorICMgICAxOTg5LTE5OTggYnkgdGhlIFVuaXZlcnNpdHkgb2YgV2FzaGlu Z3Rvbi4NCisgIw0KKyAjICAgVGhlIGZ1bGwgdGV4dCBvZiBvdXIgbGVnYWwg bm90aWNlcyBpcyBjb250YWluZWQgaW4gdGhlIGZpbGUgY2FsbGVkDQorICMg ICBDUFlSSUdIVCwgaW5jbHVkZWQgd2l0aCB0aGlzIGRpc3RyaWJ1dGlvbi4N CisgIw0KKyAjDQorICMgICBQaW5lIGlzIGluIHBhcnQgYmFzZWQgb24gVGhl IEVsbSBNYWlsIFN5c3RlbToNCisgIyAgICAqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKg0KKyAjICAgICogIFRoZSBFbG0gTWFpbCBTeXN0ZW0gIC0gIFJl dmlzaW9uOiAyLjEzICAgICAgICAgICAgICAgICAgICAgICAgICAgICAqDQor ICMgICAgKiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICoNCisgIyAgICAqIAkJ CUNvcHlyaWdodCAoYykgMTk4NiwgMTk4NyBEYXZlIFRheWxvciAgICAgICAg ICAgICAgICoNCisgIyAgICAqIAkJCUNvcHlyaWdodCAoYykgMTk4OCwgMTk4 OSBVU0VORVQgQ29tbXVuaXR5IFRydXN0ICAgICoNCisgIyAgICAqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKg0KKyAjDQorICMNCisgDQorIA0KKyAjDQor ICMgICAgIE1ha2UgZmlsZSBmb3IgdGhlIFBpbmUgbWFpbCBzeXN0ZW0gZm9y IEhQL1VYLg0KKyAjDQorICMgICBNb3N0IGNvbW1vbmx5IGZpZGRsZWQgZmxh Z3MgZm9yIGNvbXBpbGVyLg0KKyAjICAgVW5jb21tZW50IHRoZSBzZXR0dGlu Z3MgZGVzaXJlZCBoZXJlDQorICMNCisgUk09ICAgICAgICAgIHJtIC1mDQor IExOPSAgICAgICAgICBsbiAtcw0KKyBNQUtFPSAgICAgICAgbWFrZQ0KKyBP UFRJTUlaRT0gICAgIyAtTw0KKyBQUk9GSUxFPSAgICAgIyAtcGcNCisgREVC VUc9ICAgICAgIC1nIC1EREVCVUcNCisgDQorIENDTElFTlRESVI9ICAuLi9j LWNsaWVudA0KKyBQSUNPRElSPSAgICAgLi4vcGljbw0KKyANCisgIyBPbmx5 IG5lZWQgdG8gdW5jb21tZW50IG5leHQgdHdvIGxpbmVzIGlmIHlvdSBydW4g bWFrZSBmcm9tIHRoaXMgZGlyZWN0b3J5DQorICMgYW5kIHlvdSBkb24ndCB3 YW50IHRvIHN1cHBseSB0aGVtIGFzIGFyZ3VtZW50cyB0byB0aGUgbWFrZS4N CisgI0xEQVBMSUJTPSAgICAuLi9sZGFwL2xpYnJhcmllcy9saWJsZGFwLmEg Li4vbGRhcC9saWJyYXJpZXMvbGlibGJlci5hDQorICNMREFQQ0ZMQUdTPSAg LURFTkFCTEVfTERBUCAtSS4uL2xkYXAvaW5jbHVkZQ0KKyAjIE9iamVjdCBm aWxlcyB0aGF0IG5lZWQgdG8gYmUgcmVidWlsdCBpZiBFTkFCTEVfTERBUCBn ZXRzIGRlZmluZWQuDQorIExEQVBPRklMRVM9ICAgYWRkcmJvb2subyBhZHJi a2NtZC5vIGFyZ3MubyBibGRhZGRyLm8gaW5pdC5vIFwNCisgCSAgICAgIG90 aGVyLm8gcGluZS5vIHRha2VhZGRyLm8NCisgDQorIFNURExJQlM9ICAgICAt bHRlcm1jYXAgLUwkKE9QRU5TU0xESVIpL2xpYiAtbHNzbCAtbGNyeXB0bw0K KyBMT0NMSUJTPSAgICAgJChQSUNPRElSKS9saWJwaWNvLmEgJChDQ0xJRU5U RElSKS9jLWNsaWVudC5hDQorIExJQlM9ICAgICAgICAkKEVYVFJBTElCRVMp ICQoTE9DTElCUykgJChMREFQTElCUykgJChTVERMSUJTKSBcDQorICAgICAg ICAgICAgICBgY2F0ICQoQ0NMSUVOVERJUikvTERGTEFHU2ANCisgDQorIFNU RENGTEFHUz0gICAtRGNvbnN0PSAtQWEgLURfSFBVWF9TT1VSQ0UgLURIUFAg LURTWVNUWVBFPVwiSFBQXCIgLURNT1VTRSBcDQorIAkgICAgIC1ESEFWRV9T U0wgLUkkKE9QRU5TU0xESVIpL2luY2x1ZGUvb3BlbnNzbA0KKyBDRkxBR1M9 ICAgICAgJChPUFRJTUlaRSkgJChQUk9GSUxFKSAkKERFQlVHKSAkKEVYVFJB Q0ZMQUdTKSAkKExEQVBDRkxBR1MpIFwNCisgCSAgICAgJChTVERDRkxBR1Mp DQorIA0KKyBPRklMRVM9CWFkZHJib29rLm8gYWRyYmtjbWQubyBhZHJia2xp Yi5vIGFyZ3MubyBibGRhZGRyLm8gY29udGV4dC5vIGZpbHRlci5vIFwNCisg CWZvbGRlci5vIGhlbHAubyBoZWxwdGV4dC5vIGltYXAubyBpbml0Lm8gbWFp bGNhcC5vIG1haWxjbWQubyBcDQorIAltYWlsaW5keC5vIG1haWxwYXJ0Lm8g bWFpbHZpZXcubyBuZXdtYWlsLm8gb3RoZXIubyBwaW5lLm8gXA0KKyAJcmVw bHkubyBzY3JlZW4ubyBzZW5kLm8gc2lnbmFscy5vIHN0YXR1cy5vIHN0cmlu Z3MubyB0YWtlYWRkci5vIFwNCisgCW9zLm8NCisgDQorIEhGSUxFUz0JaGVh ZGVycy5oIG9zLmggcGluZS5oIGNvbnRleHQuaCBoZWxwdGV4dC5oIFwNCisg CSQoUElDT0RJUikvaGVhZGVycy5oICQoUElDT0RJUikvZXN0cnVjdC5oIFwN CisgCSQoUElDT0RJUikvZWRlZi5oICQoUElDT0RJUikvZWZ1bmMuaCBcDQor IAkkKFBJQ09ESVIpL3BpY28uaCAkKFBJQ09ESVIpL29zLmggXA0KKyAJJChD Q0xJRU5URElSKS9tYWlsLmggJChDQ0xJRU5URElSKS9vc2RlcC5oIFwNCisg CSQoQ0NMSUVOVERJUikvcmZjODIyLmggJChDQ0xJRU5URElSKS9taXNjLmgN CisgDQorICMgVGhlICYgbWVhbnMgbWFrZSBpbiBwYXJhbGxlbA0KKyBwaW5l OiAgJCYgJChPRklMRVMpICQoTE9DTElCUykNCisgCWVjaG8gImNoYXIgZGF0 ZXN0YW1wW109IlwiYGRhdGVgXCIiOyIgPiBkYXRlLmMNCisgCWVjaG8gImNo YXIgaG9zdHN0YW1wW109IlwiYGhvc3RuYW1lYFwiIjsiID4+IGRhdGUuYw0K KyAJJChQVVJJRlkpICQoUFVSSUZZT1BUSU9OUykgJChDQykgJChMREZMQUdT KSAkKENGTEFHUykgLW8gcGluZSAkKE9GSUxFUykgZGF0ZS5jICQoTElCUykN CisgDQorIGFib29rY3B5OglhYm9va2NweS5vICQoTE9DTElCRVMpDQorIAkk KENDKSAkKExERkxBR1MpICQoQ0ZMQUdTKSAtbyBhYm9va2NweSBhYm9va2Nw eS5vICQoTElCUykNCisgDQorIHBpbmUtdXNlOglwaW5lLXVzZS5jDQorIAkk KENDKSAtbyBwaW5lLXVzZSBwaW5lLXVzZS5jDQorIA0KKyBjbGVhbjoNCisg CSQoUk0pICoubyBvcy5oIG9zLmMgaGVscHRleHQuYyBoZWxwdGV4dC5oIHBp bmUNCisgCWNkIG9zZGVwOyBtYWtlIGNsZWFuOyBjZCAuLg0KKyANCisgb3Mu aDoJb3NkZXAvb3MtaHBwLmgNCisgCSQoUk0pIG9zLmgNCisgCSQoTE4pIG9z ZGVwL29zLWhwcC5oIG9zLmgNCisgDQorIG9zLmM6CW9zZGVwL29zLWhwcC5j DQorIAkkKFJNKSBvcy5jDQorIAkkKExOKSBvc2RlcC9vcy1ocHAuYyBvcy5j DQorIA0KKyAkKE9GSUxFUyk6CQkJCQkJJChIRklMRVMpDQorIGFkZHJib29r Lm8gYWRyYmtjbWQubyBhZHJia2xpYi5vIGJsZGFkZHIubyB0YWtlYWRkci5v OglhZHJia2xpYi5oDQorIGNvbnRleHQubzoJCQkJCQkkKENDTElFTlRESVIp L21pc2MuaA0KKyBzZW5kLm86CQkJCQkJCSQoQ0NMSUVOVERJUikvc210cC5o DQorICQoTERBUE9GSUxFUyk6CQkJCQkJJChMREFQTElCUykNCisgDQorIGhl bHB0ZXh0LmM6CXBpbmUuaGxwDQorIAkJLi9jbXBsaGVscC5zaCAgPCBwaW5l LmhscCA+IGhlbHB0ZXh0LmMNCisgDQorIGhlbHB0ZXh0Lmg6CXBpbmUuaGxw DQorIAkJLi9jbXBsaGxwMi5zaCAgPCBwaW5lLmhscCA+IGhlbHB0ZXh0LmgN CisgDQorIG9zZGVwL29zLWhwcC5jOglvc2RlcC9ibGRfcGF0aCBvc2RlcC9j YW5hY2NlcyBvc2RlcC9jYW5vbmljbCBcDQorIAkJb3NkZXAvY2huZ2VfcHcg b3NkZXAvY29yZWR1bXAgb3NkZXAvY3JlYXRkaXIgXA0KKyAJCW9zZGVwL2Rp c2txdW90LmhwcCBvc2RlcC9kb21uYW1lcyBvc2RlcC9lcnJfZGVzYyBcDQor IAkJb3NkZXAvZXhwbmZsZHIgb3NkZXAvZmdldHBvcyBvc2RlcC9maWxlc2l6 ZSBvc2RlcC9mbHRybmFtZSBcDQorIAkJb3NkZXAvZm5leHBhbmQgb3NkZXAv aGVhZGVyIG9zZGVwL2hvc3RuYW1lLnVuYSBcDQorIAkJb3NkZXAvam9iY250 cmwgb3NkZXAvbHN0Y21wbnQgb3NkZXAvbWltZWRpc3Agb3NkZXAvcGlwZSBc DQorIAkJb3NkZXAvcHJpbnQgb3NkZXAvcHdfc3R1ZmYgb3NkZXAvcmVhZGZp bGUgb3NkZXAvZGVidWdpbmcudGltIFwNCisgCQlvc2RlcC9yZW5hbWUgb3Nk ZXAvdGVtcGZpbGUgb3NkZXAvd3JpdF9kaXIgXA0KKyAJCW9zZGVwL3Rlcm1p bi51bnggb3NkZXAvdGVybW91dC51bnggXA0KKyAJCW9zZGVwL3Rlcm1pbi5n ZW4gb3NkZXAvdGVybW91dC5nZW4gXA0KKyAJCW9zZGVwL3NlbmRtYWlsIG9z ZGVwL2V4ZWN2aWV3IG9zZGVwL3NyYW5kb20uZHVtIFwNCisgCQlvc2RlcC9z dW5xdW90YSBvc2RlcC9wb3N0cmVhcC53dHAgb3NkZXAvb3MtaHBwLmljDQor IAkJY2Qgb3NkZXA7ICQoTUFLRSkgaW5jbHVkZXIgb3MtaHBwLmM7IGNkIC4u DQpkaWZmIC1jck4gcGluZTQuMTAvcGluZS9tYWtlZmlsZS5seHMgcGluZTQu MTAtc3NsL3BpbmUvbWFrZWZpbGUubHhzDQoqKiogcGluZTQuMTAvcGluZS9t YWtlZmlsZS5seHMJVGh1IEphbiAgMSAwMTowMDowMCAxOTcwDQotLS0gcGlu ZTQuMTAtc3NsL3BpbmUvbWFrZWZpbGUubHhzCVN1biBKdW4gMjAgMTc6MDk6 NTUgMTk5OQ0KKioqKioqKioqKioqKioqDQoqKiogMCAqKioqDQotLS0gMSwx MzIgLS0tLQ0KKyAjICRJZDogbWFrZWZpbGUubG5zLHYgMS40MCAxOTk4LzA4 LzI3IDE2OjQ5OjMyIGh1YmVydCBFeHAgJA0KKyAjDQorICMgICAgICAgICAg ICBUIEggRSAgICBQIEkgTiBFICAgIE0gQSBJIEwgICBTIFkgUyBUIEUgTQ0K KyAjDQorICMgICBMYXVyZW5jZSBMdW5kYmxhZGUgYW5kIE1pa2UgU2VpYmVs DQorICMgICBOZXR3b3JrcyBhbmQgRGlzdHJpYnV0ZWQgQ29tcHV0aW5nDQor ICMgICBDb21wdXRpbmcgYW5kIENvbW11bmljYXRpb25zDQorICMgICBVbml2 ZXJzaXR5IG9mIFdhc2hpbmd0b24NCisgIyAgIEFkbWluaXN0cmF0aW9uIEJ1 aWxkaW5nLCBBRy00NA0KKyAjICAgU2VhdHRsZSwgV2FzaGluZ3RvbiwgOTgx OTUsIFVTQQ0KKyAjICAgSW50ZXJuZXQ6IGxnbEBDQUMuV2FzaGluZ3Rvbi5F RFUNCisgIyAgICAgICAgICAgICBtaWtlc0BDQUMuV2FzaGluZ3Rvbi5FRFUN CisgIw0KKyAjICAgUGxlYXNlIGFkZHJlc3MgYWxsIGJ1Z3MgYW5kIGNvbW1l bnRzIHRvICJwaW5lLWJ1Z3NAY2FjLndhc2hpbmd0b24uZWR1Ig0KKyAjDQor ICMNCisgIyAgIFBpbmUgYW5kIFBpY28gYXJlIHJlZ2lzdGVyZWQgdHJhZGVt YXJrcyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBXYXNoaW5ndG9uLg0KKyAjICAg Tm8gY29tbWVyY2lhbCB1c2Ugb2YgdGhlc2UgdHJhZGVtYXJrcyBtYXkgYmUg bWFkZSB3aXRob3V0IHByaW9yIHdyaXR0ZW4NCisgIyAgIHBlcm1pc3Npb24g b2YgdGhlIFVuaXZlcnNpdHkgb2YgV2FzaGluZ3Rvbi4NCisgIw0KKyAjICAg UGluZSwgUGljbywgYW5kIFBpbG90IHNvZnR3YXJlIGFuZCBpdHMgaW5jbHVk ZWQgdGV4dCBhcmUgQ29weXJpZ2h0DQorICMgICAxOTg5LTE5OTggYnkgdGhl IFVuaXZlcnNpdHkgb2YgV2FzaGluZ3Rvbi4NCisgIw0KKyAjICAgVGhlIGZ1 bGwgdGV4dCBvZiBvdXIgbGVnYWwgbm90aWNlcyBpcyBjb250YWluZWQgaW4g dGhlIGZpbGUgY2FsbGVkDQorICMgICBDUFlSSUdIVCwgaW5jbHVkZWQgd2l0 aCB0aGlzIGRpc3RyaWJ1dGlvbi4NCisgIw0KKyAjDQorICMgICBQaW5lIGlz IGluIHBhcnQgYmFzZWQgb24gVGhlIEVsbSBNYWlsIFN5c3RlbToNCisgIyAg ICAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKg0KKyAjICAgICogIFRoZSBF bG0gTWFpbCBTeXN0ZW0gIC0gIFJldmlzaW9uOiAyLjEzICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAqDQorICMgICAgKiAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICoNCisgIyAgICAqIAkJCUNvcHlyaWdodCAoYykgMTk4NiwgMTk4 NyBEYXZlIFRheWxvciAgICAgICAgICAgICAgICoNCisgIyAgICAqIAkJCUNv cHlyaWdodCAoYykgMTk4OCwgMTk4OSBVU0VORVQgQ29tbXVuaXR5IFRydXN0 ICAgICoNCisgIyAgICAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0KKyAj DQorICMNCisgDQorIA0KKyAjDQorICMgICAgIE1ha2UgZmlsZSBmb3IgdGhl IFBpbmUgbWFpbCBzeXN0ZW0gZm9yIExpbnV4Lg0KKyAjDQorICMgICBNb3N0 IGNvbW1vbmx5IGZpZGRsZWQgZmxhZ3MgZm9yIGNvbXBpbGVyLg0KKyAjICAg VW5jb21tZW50IHRoZSBzZXR0dGluZ3MgZGVzaXJlZCBoZXJlDQorICMNCisg Uk09ICAgICAgICAgIHJtIC1mDQorIExOPSAgICAgICAgICBsbiAtcw0KKyBN QUtFPSAgICAgICAgbWFrZQ0KKyBPUFRJTUlaRT0gICAgLU8yDQorIFBST0ZJ TEU9ICAgICAjIC1wZw0KKyBERUJVRz0gICAgICAgIyAtZyAtRERFQlVHDQor IA0KKyBDQ0xJRU5URElSPSAgLi4vYy1jbGllbnQNCisgUElDT0RJUj0gICAg IC4uL3BpY28NCisgDQorICMgT25seSBuZWVkIHRvIHVuY29tbWVudCBuZXh0 IHR3byBsaW5lcyBpZiB5b3UgcnVuIG1ha2UgZnJvbSB0aGlzIGRpcmVjdG9y eQ0KKyAjIGFuZCB5b3UgZG9uJ3Qgd2FudCB0byBzdXBwbHkgdGhlbSBhcyBh cmd1bWVudHMgdG8gdGhlIG1ha2UuDQorICNMREFQTElCUz0gICAgLi4vbGRh cC9saWJyYXJpZXMvbGlibGRhcC5hIC4uL2xkYXAvbGlicmFyaWVzL2xpYmxi ZXIuYQ0KKyAjTERBUENGTEFHUz0gIC1ERU5BQkxFX0xEQVAgLUkuLi9sZGFw L2luY2x1ZGUNCisgIyBPYmplY3QgZmlsZXMgdGhhdCBuZWVkIHRvIGJlIHJl YnVpbHQgaWYgRU5BQkxFX0xEQVAgZ2V0cyBkZWZpbmVkLg0KKyBMREFQT0ZJ TEVTPSAgIGFkZHJib29rLm8gYWRyYmtjbWQubyBhcmdzLm8gYmxkYWRkci5v IGluaXQubyBcDQorIAkgICAgICBvdGhlci5vIHBpbmUubyB0YWtlYWRkci5v DQorIA0KKyBTVERMSUJTPSAgICAgLWxuY3Vyc2VzIC1MJChPUEVOU1NMRElS KS9saWIgLWxzc2wgLWxjcnlwdG8NCisgTE9DTElCUz0gICAgICQoUElDT0RJ UikvbGlicGljby5hICQoQ0NMSUVOVERJUikvYy1jbGllbnQuYQ0KKyBMSUJT PSAgICAgICAgJChFWFRSQUxJQkVTKSAkKExPQ0xJQlMpICQoTERBUExJQlMp ICQoU1RETElCUykgXA0KKyAgICAgICAgICAgICAgYGNhdCAkKENDTElFTlRE SVIpL0xERkxBR1NgDQorIA0KKyBTVERDRkxBR1M9ICAgLURMTlggLURTWVNU WVBFPVwiTE5YXCIgLURIQVZFX1NTTCAtSSQoT1BFTlNTTERJUikvaW5jbHVk ZS9vcGVuc3NsDQorIENGTEFHUz0gICAgICAkKE9QVElNSVpFKSAkKFBST0ZJ TEUpICQoREVCVUcpICQoRVhUUkFDRkxBR1MpICQoTERBUENGTEFHUykgXA0K KyAJICAgICAkKFNURENGTEFHUykNCisgDQorIE9GSUxFUz0JYWRkcmJvb2su byBhZHJia2NtZC5vIGFkcmJrbGliLm8gYXJncy5vIGJsZGFkZHIubyBjb250 ZXh0Lm8gZmlsdGVyLm8gXA0KKyAJZm9sZGVyLm8gaGVscC5vIGhlbHB0ZXh0 Lm8gaW1hcC5vIGluaXQubyBtYWlsY2FwLm8gbWFpbGNtZC5vIFwNCisgCW1h aWxpbmR4Lm8gbWFpbHBhcnQubyBtYWlsdmlldy5vIG5ld21haWwubyBvdGhl ci5vIHBpbmUubyBcDQorIAlyZXBseS5vIHNjcmVlbi5vIHNlbmQubyBzaWdu YWxzLm8gc3RhdHVzLm8gc3RyaW5ncy5vIHRha2VhZGRyLm8gXA0KKyAJb3Mu bw0KKyANCisgSEZJTEVTPQloZWFkZXJzLmggb3MuaCBwaW5lLmggY29udGV4 dC5oIGhlbHB0ZXh0LmggXA0KKyAJJChQSUNPRElSKS9oZWFkZXJzLmggJChQ SUNPRElSKS9lc3RydWN0LmggXA0KKyAJJChQSUNPRElSKS9lZGVmLmggJChQ SUNPRElSKS9lZnVuYy5oIFwNCisgCSQoUElDT0RJUikvcGljby5oICQoUElD T0RJUikvb3MuaCBcDQorIAkkKENDTElFTlRESVIpL21haWwuaCAkKENDTElF TlRESVIpL29zZGVwLmggXA0KKyAJJChDQ0xJRU5URElSKS9yZmM4MjIuaCAk KENDTElFTlRESVIpL21pc2MuaA0KKyANCisgcGluZTogICQoT0ZJTEVTKSAk KExPQ0xJQlMpDQorIAllY2hvICJjaGFyIGRhdGVzdGFtcFtdPSJcImBkYXRl YFwiIjsiID4gZGF0ZS5jDQorIAllY2hvICJjaGFyIGhvc3RzdGFtcFtdPSJc ImBob3N0bmFtZWBcIiI7IiA+PiBkYXRlLmMNCisgCSQoQ0MpICQoTERGTEFH UykgJChDRkxBR1MpIC1vIHBpbmUgJChPRklMRVMpIGRhdGUuYyAkKExJQlMp DQorIA0KKyBhYm9va2NweToJYWJvb2tjcHkubyAkKExPQ0xJQkVTKQ0KKyAJ JChDQykgJChMREZMQUdTKSAkKENGTEFHUykgLW8gYWJvb2tjcHkgYWJvb2tj cHkubyAkKExJQlMpDQorIA0KKyBwaW5lLXVzZToJcGluZS11c2UuYw0KKyAJ JChDQykgLW8gcGluZS11c2UgcGluZS11c2UuYw0KKyANCisgY2xlYW46DQor IAkkKFJNKSAqLm8gb3MuaCBvcy5jIGhlbHB0ZXh0LmMgaGVscHRleHQuaCBw aW5lDQorIAljZCBvc2RlcDsgbWFrZSBjbGVhbjsgY2QgLi4NCisgDQorIG9z Lmg6CW9zZGVwL29zLWxueC5oDQorIAkkKFJNKSBvcy5oDQorIAkkKExOKSBv c2RlcC9vcy1sbnguaCBvcy5oDQorIA0KKyBvcy5jOglvc2RlcC9vcy1sbngu Yw0KKyAJJChSTSkgb3MuYw0KKyAJJChMTikgb3NkZXAvb3MtbG54LmMgb3Mu Yw0KKyANCisgJChPRklMRVMpOgkJCQkJCSQoSEZJTEVTKQ0KKyBhZGRyYm9v ay5vIGFkcmJrY21kLm8gYWRyYmtsaWIubyBibGRhZGRyLm8gdGFrZWFkZHIu bzoJYWRyYmtsaWIuaA0KKyBjb250ZXh0Lm86CQkJCQkJJChDQ0xJRU5URElS KS9taXNjLmgNCisgc2VuZC5vOgkJCQkJCQkkKENDTElFTlRESVIpL3NtdHAu aA0KKyAkKExEQVBPRklMRVMpOgkJCQkJCSQoTERBUExJQlMpDQorIA0KKyBo ZWxwdGV4dC5jOglwaW5lLmhscA0KKyAJCS4vY21wbGhlbHAuc2ggIDwgcGlu ZS5obHAgPiBoZWxwdGV4dC5jDQorIA0KKyBoZWxwdGV4dC5oOglwaW5lLmhs cA0KKyAJCS4vY21wbGhscDIuc2ggIDwgcGluZS5obHAgPiBoZWxwdGV4dC5o DQorIA0KKyBvc2RlcC9vcy1sbnguYzoJb3NkZXAvYmxkX3BhdGggb3NkZXAv Y2FuYWNjZXMgb3NkZXAvY2Fub25pY2wgXA0KKyAJCW9zZGVwL2NobmdlX3B3 IG9zZGVwL2NvcmVkdW1wIG9zZGVwL2NyZWF0ZGlyIFwNCisgCQlvc2RlcC9k aXNrcXVvdC5ub24gb3NkZXAvZG9tbmFtZXMgb3NkZXAvZXJyX2Rlc2MgXA0K KyAJCW9zZGVwL2V4cG5mbGRyIG9zZGVwL2ZnZXRwb3Mubm9uIG9zZGVwL2Zp bGVzaXplIG9zZGVwL2ZsdHJuYW1lIFwNCisgCQlvc2RlcC9mbmV4cGFuZCBv c2RlcC9oZWFkZXIgb3NkZXAvaG9zdG5hbWUgXA0KKyAJCW9zZGVwL2pvYmNu dHJsIG9zZGVwL2xzdGNtcG50IG9zZGVwL21pbWVkaXNwIG9zZGVwL3BpcGUg XA0KKyAJCW9zZGVwL3ByaW50IG9zZGVwL3B3X3N0dWZmIG9zZGVwL3JlYWRm aWxlIG9zZGVwL2RlYnVnaW5nLnRpbSBcDQorIAkJb3NkZXAvcmVuYW1lIG9z ZGVwL3RlbXBmaWxlIG9zZGVwL3dyaXRfZGlyIFwNCisgCQlvc2RlcC90ZXJt aW4udW54IG9zZGVwL3Rlcm1vdXQudW54IFwNCisgCQlvc2RlcC90ZXJtaW4u Z2VuIG9zZGVwL3Rlcm1vdXQuZ2VuIFwNCisgCQlvc2RlcC9zZW5kbWFpbCBv c2RlcC9leGVjdmlldyBcDQorIAkJb3NkZXAvcG9zdHJlYXAud3RwIG9zZGVw L29zLWxueC5pYw0KKyAJCWNkIG9zZGVwOyAkKE1BS0UpIGluY2x1ZGVyIG9z LWxueC5jOyBjZCAuLg0K --42347779-1037901879-929905901=:16913-- -- ----------------------------------------------------------------- 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, 20 Jun 1999 17:46:46 -0700 (PDT) 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 RAA22252 for ; Sun, 20 Jun 1999 17:46:44 -0700 (PDT) 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 RAA18573; Sun, 20 Jun 1999 17:46:42 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA10373; Sun, 20 Jun 1999 17:46:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA35244 for ; Sun, 20 Jun 1999 17:41:37 -0700 Received: from blkbox.com (swhatley@blkbox.com [206.109.97.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA30780 for ; Sun, 20 Jun 1999 17:41:36 -0700 Received: from localhost (swhatley@localhost) by blkbox.com (8.8.7/8.8.7) with SMTP id TAA07746; Sun, 20 Jun 1999 19:41:33 -0500 (CDT) Message-Id: Date: Sun, 20 Jun 1999 19:41:33 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steven Whatley To: Pine Discussion Forum Subject: Re: pine-4.10-ssl In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Thomas Woerner X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > I have made a patch for pine-4.10 to work with OpenSSL-0.9.3a. It works > fine for Linux (glibc), HPUX-10 and HPUX-11 - others not tested, yet. Where do I find OpenSSL-0.9.3a? Do I need root access to install it? Can I install in my own directory to use OpenSSL? Thanks, Steven -- _|_ | _|_ "I am the way and the truth and the life. | --|-- | No one comes to the Father except through Steven Whatley | | | me. If you really knew me, you would Houston, Texas | know my Father as well. From now on, swhatley@blkbox.com | you do know him and have seen him." http://www.blkbox.com/~swhatley/ -- Jesus Christ (John 14:6-7 NIV) 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, 20 Jun 1999 18:55:06 -0700 (PDT) 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 SAA22746 for ; Sun, 20 Jun 1999 18:55:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA19414; Sun, 20 Jun 1999 18:55:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA14071; Sun, 20 Jun 1999 18:54:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA35118 for ; Sun, 20 Jun 1999 18:50:15 -0700 Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id SAA01429 for ; Sun, 20 Jun 1999 18:50:13 -0700 Received: (qmail 7743 invoked from network); 21 Jun 1999 02:04:43 -0000 Received: from brane.geac.com.au (202.6.67.115) by caveman.geac.com.au with SMTP; 21 Jun 1999 02:04:43 -0000 Received: from fgh.geac.com.au by brane.geac.com.au with smtp\n (Smail3.1.29.1 #3) id m10vtAV-0003uHC; Mon, 21 Jun 99 11:46 AEST Received: from localhost (dave@localhost) by fgh.geac.com.au?r with ESMTP id LAA16950 for ; Mon, 21 Jun 1999 11:47:57 +1000 Message-Id: Date: Mon, 21 Jun 1999 11:47:57 +1000 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Horsfall To: Pine Discussion Forum Subject: RE: spell checking add-on In-Reply-To: <01BEB8C1.5E99F6E0.florence@asianexplorer.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion List X-Sender: dave@fgh X-No-Archive: Yes X-Witty-Saying: "Tesseract - Enter at own risk" X-Disclaimer: "Me, speak for us?" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Florence Lee wrote: > THE last time we installed pine, it took 6 months...it's very technical... > anybody finds it hard to install pine... Six *MONTHS* to install Pine? Where's the problem? When a new version comes out, it takes me 5 minutes, not including compilation time. -- Dave Horsfall VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422 Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia 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, 20 Jun 1999 19:04:28 -0700 (PDT) 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 TAA22813 for ; Sun, 20 Jun 1999 19:04:27 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA19526; Sun, 20 Jun 1999 19:04:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA03841; Sun, 20 Jun 1999 19:04:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA35136 for ; Sun, 20 Jun 1999 18:59:53 -0700 Received: from caveman.geac.com.au (caveman.geac.com.au [203.30.73.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id SAA12568 for ; Sun, 20 Jun 1999 18:59:49 -0700 Received: (qmail 7898 invoked from network); 21 Jun 1999 02:14:17 -0000 Received: from brane.geac.com.au (202.6.67.115) by caveman.geac.com.au with SMTP; 21 Jun 1999 02:14:17 -0000 Received: from fgh.geac.com.au by brane.geac.com.au with smtp\n (Smail3.1.29.1 #3) id m10vtJg-0002hVC; Mon, 21 Jun 99 11:56 AEST Received: from localhost (dave@localhost) by fgh.geac.com.au?r with ESMTP id LAA17048 for ; Mon, 21 Jun 1999 11:57:25 +1000 Message-Id: Date: Mon, 21 Jun 1999 11:57:25 +1000 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Horsfall To: Pine Discussion Forum Subject: Re: halyfax In-Reply-To: <01BEB8C1.A9CDFA80.florence@asianexplorer.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion List X-Sender: dave@fgh X-No-Archive: Yes X-Witty-Saying: "Tesseract - Enter at own risk" X-Disclaimer: "Me, speak for us?" X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 17 Jun 1999, Florence Lee wrote: > anybody using above product..it's intergrated or can be intergrated with pine You must mean Hylafax, a free fax send/receive suite for Unix. It runs stand-alone (usually, via a command interface) but there's no reason why it cannot be integrated into other products, as it uses a client/server interface. You need a fax-modem, preferably Class 2. It would be easy to set up Sendmail (for example - I'm a Unix bigot*) to include a "fax" mailer, to divert everything to Hylafax, and sending faxes simply by addressing them to "1234567.fax" (or whatever). I intend to do this from home, some time. * I make no apologies for being a Unix bigot; there are enough free versions of Unix around (I run a coomercial one) that there is simply no excuse for using crappy Wintel stuff any more. -- Dave Horsfall VK2KFU dave@geac.com.au Ph: +61 2 9978-7493 Fx: +61 2 9978-7422 Geac Computers P/L (FGH Division) 2/57 Christie St, St Leonards 2065, Australia 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, 22 Jun 1999 05:39:13 -0700 (PDT) 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 FAA22894 for ; Tue, 22 Jun 1999 05:39:12 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA23395; Tue, 22 Jun 1999 05:39:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA26240; Tue, 22 Jun 1999 05:38:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA49646 for ; Tue, 22 Jun 1999 05:32:04 -0700 Received: from sobhan.bol.sharif.ac.ir ([194.225.42.50]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA02244 for ; Tue, 22 Jun 1999 05:31:24 -0700 Received: from localhost (majid@localhost) by sobhan.bol.sharif.ac.ir (8.8.6/8.8.6) with ESMTP id RAA00168 for ; Tue, 22 Jun 1999 17:03:00 +0430 Message-Id: Date: Tue, 22 Jun 1999 17:02:58 +0430 (IDT) Reply-To: majid@bol.sharif.ac.ir Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Majid Tajamolian To: Pine Discussion Forum Subject: PINE, IMAP and redhat 5.1 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: sobhan.bol.sharif.ac.ir: majid owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear LIST; Hello, I have a problem with the above configuration. Our mail server is a RedHat 5.1 and we connect to it via IMAP using PINE 4.10. PINE needs that the /var/spool/mail directory has 1777 permission, otherwise it will warning about "Mail box is vulnerable ...". When we set the permission to the 1777 (sticky bit is set) all is good, but sometimes the permission automatically is changed to the default value which is 0775. Did anyone see such problem previously? Any clue or guide? -- THX in advance, M. Tajamolian Jun 22 -- ----------------------------------------------------------------- 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, 22 Jun 1999 07:09:56 -0700 (PDT) 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 HAA23644 for ; Tue, 22 Jun 1999 07:09:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA00987; Tue, 22 Jun 1999 07:09:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA04752; Tue, 22 Jun 1999 07:09:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA40134 for ; Tue, 22 Jun 1999 07:02:59 -0700 Received: from issfire.co.palm-beach.fl.us (issfire.co.palm-beach.fl.us [151.132.50.198]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA18285 for ; Tue, 22 Jun 1999 07:02:58 -0700 Received: from issfire.co.palm-beach.fl.us (root@localhost) by issfire.co.palm-beach.fl.us with ESMTP id KAA03756; Tue, 22 Jun 1999 10:02:53 -0400 (EDT) Received: from ermasotelo.co.palm-beach.fl.us ([151.132.16.86]) by issfire.co.palm-beach.fl.us with SMTP id KAA03739; Tue, 22 Jun 1999 10:02:53 -0400 (EDT) Message-Id: <376F976C.3733@co.palm-beach.fl.us> Date: Tue, 22 Jun 1999 10:02:20 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alex Sotelo To: Pine Discussion Forum Subject: Re: PINE, IMAP and redhat 5.1 References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: majid@bol.sharif.ac.ir X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When you say "automatically" just what do you mean? every hour, every day, after every backup? right after you change it back? (east coast, west coast, night time, day time, peak time [cellular phone commercial, sorry I coud not contain myself] ;-) It could be that one of the users, probably root, is doing something on that directory at a certain point, and changing the permissions back. Majid Tajamolian wrote: > > Dear LIST; > Hello, I have a problem with the above configuration. Our mail server is a > RedHat 5.1 and we connect to it via IMAP using PINE 4.10. PINE needs that > the /var/spool/mail directory has 1777 permission, otherwise it will > warning about "Mail box is vulnerable ...". > When we set the permission to the 1777 (sticky bit is set) all is good, > but sometimes the permission automatically is changed to the default > value which is 0775. > Did anyone see such problem previously? Any clue or guide? > > -- THX in advance, > M. Tajamolian > Jun 22 > -- Alex Sotelo ---------------------------------------- "Yoda of Borg are we: Futile is resistance. Assimilate you, we will." 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, 22 Jun 1999 09:12:57 -0700 (PDT) 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 JAA25900 for ; Tue, 22 Jun 1999 09:12:54 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA04210; Tue, 22 Jun 1999 09:12:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA05587; Tue, 22 Jun 1999 09:11:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA23066 for ; Tue, 22 Jun 1999 09:06:39 -0700 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.06) with ESMTP id JAA29194 for ; Tue, 22 Jun 1999 09:06:38 -0700 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 ESMTP id JAA04017 for ; Tue, 22 Jun 1999 09:06:38 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id LAA05346 for ; Tue, 22 Jun 1999 11:06:31 -0500 (CDT) Message-Id: Date: Tue, 22 Jun 1999 11:06:31 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: rewriting FCC after postponement MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have Pine set up to Fcc to the default folder. It works fine, and I am allowed to change the Fcc if I please. But, when I postpone a message and then start working on it again, it changes the Fcc to that of the current default folder. Pine does not retain the Fcc that I entered previously, even if I changed it by hand. Looks more like a bug than a feature. :-) 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; Tue, 22 Jun 1999 22:19:49 -0700 (PDT) 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 WAA06671 for ; Tue, 22 Jun 1999 22:19:48 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA23226; Tue, 22 Jun 1999 22:19:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA00815; Tue, 22 Jun 1999 22:19:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA23184 for ; Tue, 22 Jun 1999 22:14:18 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA27384 for ; Tue, 22 Jun 1999 22:14:16 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA10230; Wed, 23 Jun 1999 05:19:29 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 22 Jun 99 22:19 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA20519; Tue, 22 Jun 1999 22:06:37 -0700 Message-Id: Date: Tue, 22 Jun 1999 22:06:34 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: rewriting FCC after postponement In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Miller X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 Jun 1999, Mike Miller wrote: > I have Pine set up to Fcc to the default folder. It works fine, and I am > allowed to change the Fcc if I please. But, when I postpone a message and > then start working on it again, it changes the Fcc to that of the current > default folder. Pine does not retain the Fcc that I entered previously, > even if I changed it by hand. Looks more like a bug than a feature. :-) Oh, I wouldn't call it a bug, I'd call it an incomplete implementation, or something like that. There is a folder that is created for your postponed messages (multiple are certianly allowed in 4.05, I can't remember about 3.96). I guess it just doesn't save the Fcc: header? You can look at that manually if you wish, to see exactly what is going on... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 22 Jun 1999 22:53:39 -0700 (PDT) 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 WAA07098 for ; Tue, 22 Jun 1999 22:53:37 -0700 (PDT) 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 WAA14385; Tue, 22 Jun 1999 22:53:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA10407; Tue, 22 Jun 1999 22:52:53 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA41486 for ; Tue, 22 Jun 1999 22:47:19 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA30017 for ; Tue, 22 Jun 1999 22:47:18 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id AAA28766 for ; Wed, 23 Jun 1999 00:47:11 -0500 (CDT) Message-Id: Date: Wed, 23 Jun 1999 00:47:10 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: Re: rewriting FCC after postponement In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 22 Jun 1999, Jessica Rasku wrote: > On Tue, 22 Jun 1999, Mike Miller wrote: > > > I have Pine set up to Fcc to the default folder. It works fine, and I am > > allowed to change the Fcc if I please. But, when I postpone a message and > > then start working on it again, it changes the Fcc to that of the current > > default folder. Pine does not retain the Fcc that I entered previously, > > even if I changed it by hand. Looks more like a bug than a feature. :-) > > Oh, I wouldn't call it a bug, I'd call it an incomplete > implementation, or something like that. There is a folder that is created > for your postponed messages (multiple are certianly allowed in 4.05, I > can't remember about 3.96). I guess it just doesn't save the Fcc: header? > You can look at that manually if you wish, to see exactly what is going > on... I followed your suggestion and looked at it manually (i.e., I looked at the postponed-messages folder) and I found that the Fcc *is* stored with the postponed message. Pine saves Fcc and then changes it when the message is retrieved. That is a bug, right? Nice try! 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; Tue, 22 Jun 1999 22:59:39 -0700 (PDT) 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 WAA07158 for ; Tue, 22 Jun 1999 22:59:38 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA14500; Tue, 22 Jun 1999 22:59:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA01952; Tue, 22 Jun 1999 22:59:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA23126 for ; Tue, 22 Jun 1999 22:54:03 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA30512 for ; Tue, 22 Jun 1999 22:54:02 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id AAA29224 for ; Wed, 23 Jun 1999 00:53:55 -0500 (CDT) Message-Id: Date: Wed, 23 Jun 1999 00:53:54 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: Re: rewriting FCC after postponement In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN One more thing. I think Pine does not usually change the Fcc, but it changes it when I have not written in the To field before postponing. When I go back to the message and enter an address in the To field, Pine automatically rewrites the Fcc (if I have a different folder open). 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; Tue, 22 Jun 1999 23:12:02 -0700 (PDT) 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 XAA07367 for ; Tue, 22 Jun 1999 23:12:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA14674; Tue, 22 Jun 1999 23:11:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA06089; Tue, 22 Jun 1999 23:11:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA50476 for ; Tue, 22 Jun 1999 23:06:26 -0700 Received: from sobhan.bol.sharif.ac.ir ([194.225.42.50]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id XAA31647 for ; Tue, 22 Jun 1999 23:05:55 -0700 Received: from localhost (majid@localhost) by sobhan.bol.sharif.ac.ir (8.8.6/8.8.6) with ESMTP id TAA00166; Tue, 22 Jun 1999 19:31:29 +0430 Message-Id: Date: Tue, 22 Jun 1999 19:31:29 +0430 (IDT) Reply-To: majid@bol.sharif.ac.ir Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Majid Tajamolian To: Pine Discussion Forum Subject: Re: PINE, IMAP and redhat 5.1 In-Reply-To: <376F976C.3733@co.palm-beach.fl.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Alex Sotelo X-Cc: Pine Discussion Forum X-Authentication-Warning: sobhan.bol.sharif.ac.ir: majid owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Alex, Usually after making some codes on the server machine! On Tue, 22 Jun 1999, Alex Sotelo wrote: > When you say "automatically" just what do you mean? every hour, every > day, after every backup? right after you change it back? (east coast, > west coast, night time, day time, peak time [cellular phone commercial, > sorry I coud not contain myself] ;-) > > It could be that one of the users, probably root, is doing something on > that directory at a certain point, and changing the permissions back. > > Majid Tajamolian wrote: > > > > Dear LIST; > > Hello, I have a problem with the above configuration. Our mail server is a > > RedHat 5.1 and we connect to it via IMAP using PINE 4.10. PINE needs that > > the /var/spool/mail directory has 1777 permission, otherwise it will > > warning about "Mail box is vulnerable ...". > > When we set the permission to the 1777 (sticky bit is set) all is good, > > but sometimes the permission automatically is changed to the default > > value which is 0775. > > Did anyone see such problem previously? Any clue or guide? > > > > -- THX in advance, > > M. Tajamolian > > Jun 22 > > > -- > Alex Sotelo > ---------------------------------------- > "Yoda of Borg are we: Futile is resistance. Assimilate you, we will." > -- Cheers, M. Tajamolian Jun 22 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, 23 Jun 1999 13:50:40 -0700 (PDT) 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 NAA26929 for ; Wed, 23 Jun 1999 13:50:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA00692; Wed, 23 Jun 1999 13:50:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA26758; Wed, 23 Jun 1999 13:49:52 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA40910 for ; Wed, 23 Jun 1999 13:43:54 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA20345 for ; Wed, 23 Jun 1999 13:43:53 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id UAA17967; Wed, 23 Jun 1999 20:47:46 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 23 Jun 99 13:47 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id NAA26426; Wed, 23 Jun 1999 13:32:28 -0700 Message-Id: Date: Wed, 23 Jun 1999 13:32:27 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: rewriting FCC after postponement In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Miller X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 23 Jun 1999, Mike Miller wrote: > I followed your suggestion and looked at it manually (i.e., I looked at > the postponed-messages folder) and I found that the Fcc *is* stored with > the postponed message. Pine saves Fcc and then changes it when the > message is retrieved. That is a bug, right? Or, at the very least, a strange implementation. It isn't really something that affects the overall opperation, it is something that is annoying. A bug I think is something which causes you not to be able to do something that the program was apparently designed for. This is getting pretty close, as it looks like somewhere it was designed to keep this information, and probably use it... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 23 Jun 1999 16:15:44 -0700 (PDT) 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 QAA30686 for ; Wed, 23 Jun 1999 16:15:43 -0700 (PDT) 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 QAA14819; Wed, 23 Jun 1999 16:15:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA12372; Wed, 23 Jun 1999 16:14:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA34784 for ; Wed, 23 Jun 1999 16:09:37 -0700 Received: from blkbox.com (swhatley@blkbox.com [206.109.97.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA15527 for ; Wed, 23 Jun 1999 16:09:36 -0700 Received: from localhost (swhatley@localhost) by blkbox.com (8.8.7/8.8.7) with SMTP id SAA22607 for ; Wed, 23 Jun 1999 18:09:34 -0500 (CDT) Message-Id: Date: Wed, 23 Jun 1999 18:09:34 -0500 (CDT) Reply-To: Steven Whatley Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steven Whatley To: Pine Discussion Forum Subject: OpenSSL and Exchange Server MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I'm not sure if I got the Pine 4.10 OpenSSL patch installed properly or understand it fully. Our Exchange server does not accept plain text passwords. I'm trying to figure out what it wants. Do I need to use SSL to connect to the Exchange server? Currently, the OpenSSL connection is failing and reverting to plain text AUTH connection. Thanks, Steven -- _|_ | _|_ "I am the way and the truth and the life. | --|-- | No one comes to the Father except through Steven Whatley | | | me. If you really knew me, you would Houston, Texas | know my Father as well. From now on, swhatley@blkbox.com | you do know him and have seen him." http://www.blkbox.com/~swhatley/ -- Jesus Christ (John 14:6-7 NIV) -- ----------------------------------------------------------------- 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, 24 Jun 1999 01:06:50 -0700 (PDT) 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 BAA03664 for ; Thu, 24 Jun 1999 01:06:49 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA24158; Thu, 24 Jun 1999 01:06:48 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA15993; Thu, 24 Jun 1999 01:05:17 -0700 Resent-Date: Thu, 24 Jun 1999 01:05:17 -0700 Resent-Message-Id: <199906240805.BAA15993@lists4.u.washington.edu> Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA20594 for ; Thu, 24 Jun 1999 01:00:27 -0700 Received: from rumms.uni-mannheim.de (rumms.uni-mannheim.de [134.155.50.52]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id BAA25268 for ; Thu, 24 Jun 1999 01:00:25 -0700 Received: from pciris.rz.uni-mannheim.de (pciris.rz.uni-mannheim.de [134.155.50.75]) by rumms.uni-mannheim.de (8.9.3/8.9.3) with SMTP id KAA17546 for ; Thu, 24 Jun 1999 10:00:20 +0200 (MET DST) Message-Id: <199906240800.KAA17546@rumms.uni-mannheim.de> Date: Thu, 24 Jun 1999 09:15:47 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: iris.mayer@rz.uni-mannheim.de To: Pine Discussion Forum Subject: pine 4.10: "opening INBOX" before asking for username and password Resent-To: Pine Discussion Forum MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 8BIT Resent-From: iris.mayer@rz.uni-mannheim.de X-To: Pine Discussion Forum X-cs: R X-RS-Flags: 0,0,1,1,0,0,0 X-RS-Sigset: 1 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I just installed pine 4.10 (on HP-UX systems, Version 10.2 and 9.05). My mailbox is located on a remote mailserver. In Version 4.05 and older, pine asked for username and password at once on startup. So does the binary 4.10 I got from the HP-Web- site, but not the version I compiled. I didn't change anything except the pathname for default configuration files and I also found no difference between my source and the source, HP used to create the binary. Thanks in advance for any hints and ideas! Iris -- ----------------------------------------------------------------- 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, 24 Jun 1999 02:22:37 -0700 (PDT) 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 CAA05912 for ; Thu, 24 Jun 1999 02:22:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA15794; Thu, 24 Jun 1999 02:22:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA20680; Thu, 24 Jun 1999 02:20:49 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA45954 for ; Thu, 24 Jun 1999 02:16:34 -0700 Received: from mailhub1.liv.ac.uk (mailhub1.liv.ac.uk [138.253.100.94]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA28596 for ; Thu, 24 Jun 1999 02:16:33 -0700 Received: from uxb.liv.ac.uk ([138.253.100.101]) by mailhub1.liv.ac.uk with esmtp (Exim 2.12 #1) id 10x5cW-0004BR-00 for pine-info@u.washington.edu; Thu, 24 Jun 1999 10:16:32 +0100 Received: (from qq11@localhost) by uxb.liv.ac.uk (8.8.7/ajt5) id KAA11818; Thu, 24 Jun 1999 10:16:31 +0100 (BST) Message-Id: Date: Thu, 24 Jun 1999 10:16:31 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alan Thew To: Pine Discussion Forum Subject: hhp: Remote pine exploit. (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine List X-Sender: qq11@uxb.liv.ac.uk X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've just rejoined the list to get away from the flame fest on comp.mail.pine (perhaps it's here as well ... ). This is a "heads up" Aplogies if you've seen this before. -- Alan Thew alan.thew@liverpool.ac.uk Computing Services,University of Liverpool Fax: +44 151 794-4442 ---------- Forwarded message ---------- Date: Tue, 22 Jun 1999 13:04:14 -0400 From: Elaich Of Hhp To: BUGTRAQ@netspace.org Subject: hhp: Remote pine exploit. The hhp presents... The hhp-pine remote exploit advisory. 6/22/99 By: elaich of the hhp. http://hhp.hemp.net/ #---------------------------------------------------------# A few months ago I found a bigger problem with the charset bug then imagined. With a uuencode/uudecode method in the charset, and an index.html of a site, it's possible to run any program/script wanted to on the remote system. When the email is read it launches lynx -source and grabs the index.html which is then uudecoded and ran. This includes root and non-root users infected. Many big servers run pine, and having fingerd running, most of the time allows us complete access to get every username on the server, which then is simple to send the infected emails to each user. We have tested this on our own systems with full success. These operating systems include BSD, Linux, IRIX, AIX, SCO, and SunOS. I'm sure this will be fixed in the newer version along with the patch already made for the current version. hhp-pine.tar is available to download at our site, http://hhp.hemp.net/. The current pine 4.10 patch is available to download at http://www.geek-girl.com/bugtraq/1999_1/0532.html Jobs/Probs/Bugs/Etc. -> hhp@hhp.hemp.net #---------------------------------------------------------# -elaich ----------------------------------------- elaich of the hhp. hhp-1999(c) Email: hhp@hhp.hemp.net Web: http://hhp.hemp.net/ Phone: 713-451-6972 hhp-ms: hhp.hemp.net, port:7777, pass:hhp ----------------------------------------- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: PGPfreeware 6.0 for non-commercial use mQGiBDcl8CwRBAD7xCp+A5ORiRzMLS4mPstL1aJadSCXSGyNKEZZ6kZwdO3YhLCf 2vkeJF0OGe8KRfd8LRxP0f/3syg7lfH77m0OP8NXeoOHD48T8K4Mabp2WEJmUW0r J6op94LjFUwqNqYuOa+bVULrotZY6iWlxBWunltu9wrqgP22RVtKAu0PVwCg/2SS rYoDCNTH4dlzNcVcza5XuhMEALbmuKISbjeOqsVETYYMdQfr0M/m1YfztjJ2tDS7 bGfOCFpQUFLyCUt/FHHmlInXQWUSVCgjkp0/giFoY9dX+4IB8wLgfu68BOZM5fft I5mxI0vyBSke2kHQTqf3vQ5Yveg6gIB8WW9Pi+MAwLMS3+Hmrar+4GCUOqe9w3yi u1q3BADcAM3VkORpkifjK8pWex1fdfvGmLBX5PBuCexl5dpeXdVC+Ktncis9u4yh 5f/PI/g/Uk4T2D/nF5PA4tSkNvRJaPVZCXjFRfc4K+rzQxuYRePwXFgaHSk9cDnd XBq5JM6iXLBGFIJpbbwWkftuFOaJLXdP/DqDaXkjbWXLbH9nN7QhZWxhaWNoIG9m IGhocC4gPGhocEBoaHAuaGVtcC5uZXQ+iQBLBBARAgALBQI3JfAsBAsDAgEACgkQ bSmqkM1thIxvkQCeIEUYJTwF5nC+T9DUcUqStqpwtiQAoIzw9fqSB026Q+w0CGWe BPX9LD5ruQINBDcl8DMQCAD2Qle3CH8IF3KiutapQvMF6PlTETlPtvFuuUs4INoB p1ajFOmPQFXz0AfGy0OplK33TGSGSfgMg71l6RfUodNQ+PVZX9x2Uk89PY3bzpnh V5JZzf24rnRPxfx2vIPFRzBhznzJZv8V+bv9kV7HAarTW56NoKVyOtQa8L9GAFgr 5fSI/VhOSdvNILSd5JEHNmszbDgNRR0PfIizHHxbLY7288kjwEPwpVsYjY67VYy4 XTjTNP18F1dDox0YbN4zISy1Kv884bEpQBgRjXyEpwpy1obEAxnIByl6ypUM2Zaf q9AKUJsCRtMIPWakXUGfnHy9iUsiGSa6q6Jew1XpMgs7AAICB/oCoABrcAodA+Qw 0QOzptm6arxtaRte4a6ZQs+N4Y63+S5oKBz4/atHGGIqgcxCUaaPCxfcqRMoz6Tw ZhxOKe3/xKA+qPRfLP19P3nHcTLZqa/orvohDu235OQHBd5Mi6sr2MUcUL1WfsU7 fPZEjwu6d3MuXpjJUeFzNezJzIbXNzqFAVQawVH6lV+xGfqjD0zceGFGALvvGVxL ANdmCzqjE1LFbqf1Zdd04lKYKSglX4PFz3Ly/jzi22GFxMuGf6ud4R80wUC0zBKO RZHX3jPqjrqfbY9dq1vpBNDEugOYPqv3/lNlkoxUzKhJCZLPUcbQQs+BuNUUcRW9 dEkl71kuiQBGBBgRAgAGBQI3JfAzAAoJEG0pqpDNbYSMFgIAoMUE0SGIfqg0oj9e oY9AHDAScmZtAKDgKF7STtRwB4KJ6/Q9HC3gUgGBbA== =GJ0e -----END PGP PUBLIC KEY BLOCK----- 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, 24 Jun 1999 15:00:16 -0700 (PDT) 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 PAA19595 for ; Thu, 24 Jun 1999 15:00:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA08621; Thu, 24 Jun 1999 15:00:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA12980; Thu, 24 Jun 1999 14:59:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA43434 for ; Thu, 24 Jun 1999 14:52:55 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA13788 for ; Thu, 24 Jun 1999 14:52:52 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id VAA04478; Thu, 24 Jun 1999 21:57:59 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 24 Jun 99 14:57 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id OAA04101; Thu, 24 Jun 1999 14:50:16 -0700 Message-Id: Date: Thu, 24 Jun 1999 14:50:14 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: hhp: Remote pine exploit. (fwd) In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Alan Thew X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 24 Jun 1999, Alan Thew wrote: > #---------------------------------------------------------# > > A few months ago I found a bigger problem with the > charset bug then imagined. With a uuencode/uudecode > method in the charset, and an index.html of a site, it's > possible to run any program/script wanted to on the remote > system. When the email is read it launches lynx -source > and grabs the index.html which is then uudecoded and ran. > This includes root and non-root users infected. Many big > servers run pine, and having fingerd running, most of the > time allows us complete access to get every username on the > server, which then is simple to send the infected emails to > each user. Can anyone explain this? I really find ``bug alerts'' that I don't really understand what is being alerted to be a bit odd. Maybe I'm missing something. This has only twigged a few of the ``hoax'' detectors. Or, more precicely, it has triggered detectors that say, there is significant, and important information missing here. It sounds like not a problem with Pine itself, but with a combination of Finger setup and mailcap entries, and other things of this nature, am I totaly confused? I'm not likely to apply a patch that is from a source that I don't know who they are, especialy when the main site is so obtainable as it is with Pine. Shouldn't this have gone though the University of Washington bug information site first before being announced on Bugtraq? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 25 Jun 1999 05:43:41 -0700 (PDT) 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 FAA01233 for ; Fri, 25 Jun 1999 05:43:40 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA22860; Fri, 25 Jun 1999 05:43:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA25075; Fri, 25 Jun 1999 05:43:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id FAA34814 for ; Fri, 25 Jun 1999 05:38:37 -0700 Received: from blkbox.com (swhatley@blkbox.com [206.109.97.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id FAA12481 for ; Fri, 25 Jun 1999 05:38:37 -0700 Received: from localhost (swhatley@localhost) by blkbox.com (8.8.7/8.8.7) with SMTP id HAA08851 for ; Fri, 25 Jun 1999 07:38:35 -0500 (CDT) Message-Id: Date: Fri, 25 Jun 1999 07:38:35 -0500 (CDT) Reply-To: Steven Whatley Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steven Whatley To: Pine Discussion Forum Subject: Exchange Server & AUTH=NTLM MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I'm having a difficult time trying to get pine to connect to the achange server at work. I was (again) reading the help and noticed the /debug option. The following is the result of the communication between pine and the Exchange server: About to open folder "INBOX" inbox: "INBOX" IMAP 13:25:44 6/24 mm_log babble: Trying IP address [xxx.xxx.xxx.xxx] IMAP DEBUG 13:25:44 6/24: * OK Microsoft Exchange IMAP4rev1 server version 5.5.2448.8 (exchange.host.com) ready IMAP DEBUG 13:25:44 6/24: 00000000 CAPABILITY IMAP DEBUG 13:25:44 6/24: * CAPABILITY IMAP4 IMAP4rev1 IDLE LITERAL+LOGIN-REFERRALS MAILBOX-REFERRALS NAMESPACE AUTH=NTLM IMAP DEBUG 13:25:44 6/24: 00000000 OK CAPABILITY completed. IMAP DEBUG 13:25:54 6/24: 00000001 LOGIN xxxxxxx xxxxxxx IMAP DEBUG 13:25:54 6/24: 00000001 NO Clear text passwords have been disabled for this protocol IMAP 13:25:54 6/24 mm_log warn: Clear text passwords have been disabled for this protocol IMAP 13:26:01 6/24 mm_log ERROR: Login aborted IMAP DEBUG 13:26:01 6/24: 00000002 LOGOUT IMAP DEBUG 13:26:01 6/24: * BYE Microsoft Exchange IMAP4rev1 server version 5.5.2448.8 signing off IMAP DEBUG 13:26:01 6/24: 00000002 OK LOGOUT completed. So, it seems that I have to use NTLM authorizing method. Is there any way to get pine to do this on a Solaris 2.6 SPARC box? Any info will be appreciated. Thanks, Steven -- _|_ | _|_ "I am the way and the truth and the life. | --|-- | No one comes to the Father except through Steven Whatley | | | me. If you really knew me, you would Houston, Texas | know my Father as well. From now on, swhatley@blkbox.com | you do know him and have seen him." http://www.blkbox.com/~swhatley/ -- Jesus Christ (John 14:6-7 NIV) -- ----------------------------------------------------------------- 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, 25 Jun 1999 07:15:37 -0700 (PDT) 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 HAA02147 for ; Fri, 25 Jun 1999 07:15:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA14107; Fri, 25 Jun 1999 07:15:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA27216; Fri, 25 Jun 1999 07:15:07 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA48200 for ; Fri, 25 Jun 1999 07:10:54 -0700 Received: from issfire.co.palm-beach.fl.us (issfire.co.palm-beach.fl.us [151.132.50.198]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA15848 for ; Fri, 25 Jun 1999 07:10:53 -0700 Received: from issfire.co.palm-beach.fl.us (root@localhost) by issfire.co.palm-beach.fl.us with ESMTP id KAA12140; Fri, 25 Jun 1999 10:10:48 -0400 (EDT) Received: from ermasotelo.co.palm-beach.fl.us ([151.132.16.86]) by issfire.co.palm-beach.fl.us with SMTP id KAA12136; Fri, 25 Jun 1999 10:10:47 -0400 (EDT) Message-Id: <37738DCB.2A88@co.palm-beach.fl.us> Date: Fri, 25 Jun 1999 10:10:19 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alex Sotelo To: Pine Discussion Forum Subject: Re: Exchange Server & AUTH=NTLM References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: Steven Whatley X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think the problem is that Win98 and NT don't send out a clear text password over the network by default. You can chage this in the registry. Look at the following links: NT: http://www.facetcorp.com/tnotes/facetwin/tn_fw_encrypted_nt4.html 98: http://www.facetcorp.com/tnotes/facetwin/tn_fw_encrypted_w98.html Alex Sotelo ========================================================= Thought of the day: "The problem with work is that is so daily." Steven Whatley wrote: > > Hi all, > > I'm having a difficult time trying to get pine to connect to the achange > server at work. I was (again) reading the help and noticed the /debug > option. The following is the result of the communication between pine and > the Exchange server: > > About to open folder "INBOX" inbox: "INBOX" > IMAP 13:25:44 6/24 mm_log babble: Trying IP address [xxx.xxx.xxx.xxx] > IMAP DEBUG 13:25:44 6/24: * OK Microsoft Exchange IMAP4rev1 server version 5.5.2448.8 (exchange.host.com) ready > IMAP DEBUG 13:25:44 6/24: 00000000 CAPABILITY > IMAP DEBUG 13:25:44 6/24: * CAPABILITY IMAP4 IMAP4rev1 IDLE LITERAL+LOGIN-REFERRALS MAILBOX-REFERRALS NAMESPACE AUTH=NTLM > IMAP DEBUG 13:25:44 6/24: 00000000 OK CAPABILITY completed. > IMAP DEBUG 13:25:54 6/24: 00000001 LOGIN xxxxxxx xxxxxxx > IMAP DEBUG 13:25:54 6/24: 00000001 NO Clear text passwords have been disabled for this protocol > IMAP 13:25:54 6/24 mm_log warn: Clear text passwords have been disabled for this protocol > IMAP 13:26:01 6/24 mm_log ERROR: Login aborted > IMAP DEBUG 13:26:01 6/24: 00000002 LOGOUT > IMAP DEBUG 13:26:01 6/24: * BYE Microsoft Exchange IMAP4rev1 server version 5.5.2448.8 signing off > IMAP DEBUG 13:26:01 6/24: 00000002 OK LOGOUT completed. > > So, it seems that I have to use NTLM authorizing method. Is there any way > to get pine to do this on a Solaris 2.6 SPARC box? Any info will be > appreciated. > > 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; Fri, 25 Jun 1999 10:20:09 -0700 (PDT) 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 KAA03793 for ; Fri, 25 Jun 1999 10:20:08 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA28696; Fri, 25 Jun 1999 10:20:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA11266; Fri, 25 Jun 1999 10:19:30 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA49582 for ; Fri, 25 Jun 1999 10:14:48 -0700 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.06) with ESMTP id KAA10468 for ; Fri, 25 Jun 1999 10:14:48 -0700 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA09698; Fri, 25 Jun 1999 10:14:45 -0700 Message-Id: Date: Fri, 25 Jun 1999 10:14:44 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Hubert To: Pine Discussion Forum Subject: Re: rewriting FCC after postponement In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mike Miller X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Mike, Thanks for spotting this bug. It will be fixed in the next version of pine. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 23 Jun 1999, Mike Miller wrote: > One more thing. I think Pine does not usually change the Fcc, but it > changes it when I have not written in the To field before postponing. When > I go back to the message and enter an address in the To field, Pine > automatically rewrites the Fcc (if I have a different folder open). > > 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; Sat, 26 Jun 1999 09:28:03 -0700 (PDT) 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 JAA26206 for ; Sat, 26 Jun 1999 09:28:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA19482; Sat, 26 Jun 1999 09:28:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA04303; Sat, 26 Jun 1999 09:25:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA36052 for ; Sat, 26 Jun 1999 09:20:34 -0700 Received: from sttlpop1.sttl.uswest.net (sttlpop1.sttl.uswest.net [206.81.192.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id JAA12504 for ; Sat, 26 Jun 1999 09:20:34 -0700 Received: (qmail 13912 invoked by alias); 26 Jun 1999 16:20:32 -0000 Received: (qmail 13879 invoked by uid 0); 26 Jun 1999 16:20:31 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop1.sttl.uswest.net with SMTP; 26 Jun 1999 16:20:31 -0000 Message-Id: Date: Sat, 26 Jun 1999 09:19:01 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: hhp: Remote pine exploit. (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Please see section 9.2 in http://www.washington.edu/pine/faq/security.html -teg On Thu, 24 Jun 1999, Jessica Rasku wrote: > > A few months ago I found a bigger problem with the > > charset bug then imagined. With a uuencode/uudecode > > method in the charset, and an index.html of a site, it's > > possible to run any program/script wanted to on the remote > > system. When the email is read it launches lynx -source > > and grabs the index.html which is then uudecoded and ran. > > This includes root and non-root users infected. Many big > > servers run pine, and having fingerd running, most of the > > time allows us complete access to get every username on the > > server, which then is simple to send the infected emails to > > each user. > > Can anyone explain this? I really find ``bug alerts'' that I > don't really understand what is being alerted to be a bit odd. Maybe I'm > missing something. This has only twigged a few of the ``hoax'' detectors. > Or, more precicely, it has triggered detectors that say, there is > significant, and important information missing here. It sounds like not a > problem with Pine itself, but with a combination of Finger setup and > mailcap entries, and other things of this nature, am I totaly confused? > I'm not likely to apply a patch that is from a source that I don't > know who they are, especialy when the main site is so obtainable as it is > with Pine. Shouldn't this have gone though the University of Washington > bug information site first before being announced on Bugtraq? 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, 26 Jun 1999 18:57:44 -0700 (PDT) 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 SAA30230 for ; Sat, 26 Jun 1999 18:57:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA26617; Sat, 26 Jun 1999 18:57:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA11500; Sat, 26 Jun 1999 18:57:07 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA50188 for ; Sat, 26 Jun 1999 18:53:33 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA06555 for ; Sat, 26 Jun 1999 18:53:32 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id XAA15135; Sat, 26 Jun 1999 23:58:51 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Sat, 26 Jun 99 16:58 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id SAA29189; Sat, 26 Jun 1999 18:22:22 -0700 Message-Id: Date: Sat, 26 Jun 1999 18:22:21 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: hhp: Remote pine exploit. (fwd) In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 26 Jun 1999, Terry Gray wrote: > Please see section 9.2 in http://www.washington.edu/pine/faq/security.html Thanks, I would say that as I suspected the whole actually is not with Pine. At least, based on what is in this document. The ``alert'' didn't even give as much info as the pine faq. The faq still lacks the information to ``manualy'' figure out if it is a potential problem. I really would like to see the actuall exploits myself, that would make testing of other systems much easier. But, I understand not publishing this information... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 27 Jun 1999 17:50:25 -0700 (PDT) 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 RAA13880 for ; Sun, 27 Jun 1999 17:50:24 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA11624; Sun, 27 Jun 1999 17:50:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA29905; Sun, 27 Jun 1999 17:49:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA36044 for ; Sun, 27 Jun 1999 17:45:12 -0700 Received: from wolfenet.com (ratty.wolfe.net [204.157.98.9]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA31363 for ; Sun, 27 Jun 1999 17:45:11 -0700 Received: from sea-pm3-9-p151.wolfenet.com (sea-pm3-9-p151.wolfenet.com [206.159.18.151]) by wolfenet.com (8.9.3/8.9.3) with ESMTP id RAA05080; Sun, 27 Jun 1999 17:45:09 -0700 (PDT) Message-Id: Date: Sun, 27 Jun 1999 17:43:07 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nancy McGough To: Pine Discussion Forum Subject: bug: read-only pinerc and PC-Pine 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@shell13.ba.best.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I was experimenting and changed the pinerc file to be read-only and then started PC-Pine. It didn't work properly (which is fine) BUT it would not let me quit. I had to CTRL-ALT-DEL to get out of PC-Pine. It seems like you should be able to quit in the normal way even though PC-Pine is unhappy with the read-only pinerc. Also, it would be nice to be able to have the option of having a read-only pinerc. Thanks, 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 =-- -- ----------------------------------------------------------------- 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, 28 Jun 1999 00:41:17 -0700 (PDT) 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 AAA17728 for ; Mon, 28 Jun 1999 00:41:16 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA05295; Mon, 28 Jun 1999 00:41:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA06385; Mon, 28 Jun 1999 00:40:45 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA30986 for ; Mon, 28 Jun 1999 00:36:48 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id AAA14321 for ; Mon, 28 Jun 1999 00:36:47 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 28 Jun 1999 02:36:43 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com for pine-info@u.washington.edu; Mon, 28 Jun 1999 15:36:37 +0800 Message-Id: <002401bec138$ddc30ef0$1511b381@twntpe.cdc.com> Date: Mon, 28 Jun 1999 15:35:59 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Nancy, > Also, it would be nice > to be able to have the option of having a read-only pinerc. What do you feel would be the value in that? Thanks, Ed 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, 28 Jun 1999 05:02:45 -0700 (PDT) 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 FAA24931 for ; Mon, 28 Jun 1999 05:02:43 -0700 (PDT) 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 FAA08964; Mon, 28 Jun 1999 05:02:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id FAA12982; Mon, 28 Jun 1999 05:02:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA34762 for ; Mon, 28 Jun 1999 04:58:14 -0700 Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id EAA30504 for ; Mon, 28 Jun 1999 04:58:13 -0700 Received: from luomat.peak.org [207.141.129.161] by 1stpc.org with ESMTP (SMTPD32-4.04) id A3B2B68103F4; Mon, 28 Jun 1999 07:59:46 EST Received: by luomat.peak.org (8.9.3/8.9.0) id HAA23797 for pine-info@u.washington.edu; Mon, 28 Jun 1999 07:54:32 -0400 (EDT) Message-Id: <199906281154.HAA23797@ocalhost> Date: Mon, 28 Jun 1999 07:54:30 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: read-only pinerc and PC-Pine In-Reply-To: <002401bec138$ddc30ef0$1511b381@twntpe.cdc.com> References: <002401bec138$ddc30ef0$1511b381@twntpe.cdc.com> 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 -- ListProcessor(tm) by CREN Replying to message of Mon, 28 Jun 1999 15:35:59 +0800 from "Ed Greshko" regarding ``RE: read-only pinerc and PC-Pine'' > > Also, it would be nice to be able to have the option of having > > a read-only pinerc. > > What do you feel would be the value in that? Well... speaking only for myself.... Flexibility, and the assurance that settings don't get changed without being sure that you want to change them (ie make file writable, then make changes, then make file read-only) 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, 28 Jun 1999 07:01:38 -0700 (PDT) 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 HAA26225 for ; Mon, 28 Jun 1999 07:01:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA22445; Mon, 28 Jun 1999 07:01:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA14472; Mon, 28 Jun 1999 07:01:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA35956 for ; Mon, 28 Jun 1999 06:56:35 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id GAA31732 for ; Mon, 28 Jun 1999 06:56:34 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 28 Jun 1999 08:25:53 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Mon, 28 Jun 1999 21:25:43 +0800 Message-Id: <000701bec169$a2561570$1511b381@twntpe.cdc.com> Date: Mon, 28 Jun 1999 21:25:05 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: <199906281154.HAA23797@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 V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, > Well... speaking only for myself.... > > Flexibility, and the assurance that settings don't get changed without being > sure that you want to change them (ie make file writable, then make changes, > then make file read-only) How does the assurance improve/differ over the process which asks you to confirm your changes? Other than adding to the complexity, find the pinerc file, make it writeable, go back to pine, make the changes, answer the "commit" question, make pinerc file read-only, I can't see where there is added value or security. But, I've been known to be dense. :-) Can you give me an example of the "flexibility" it will impart? Thanks, Ed 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, 28 Jun 1999 08:50:06 -0700 (PDT) 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 IAA28009 for ; Mon, 28 Jun 1999 08:50:05 -0700 (PDT) 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 IAA24807; Mon, 28 Jun 1999 08:50:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA18306; Mon, 28 Jun 1999 08:48:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA47796 for ; Mon, 28 Jun 1999 08:44:27 -0700 Received: from wolfenet.com (ratty.wolfe.net [204.157.98.9]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA10753 for ; Mon, 28 Jun 1999 08:44:27 -0700 Received: from sea-pm3-8-p119.wolfenet.com (sea-pm3-8-p119.wolfenet.com [206.159.18.119]) by wolfenet.com (8.9.3/8.9.3) with ESMTP id IAA13974; Mon, 28 Jun 1999 08:44:20 -0700 (PDT) Message-Id: Date: Mon, 28 Jun 1999 08:42:07 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nancy McGough To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: <002401bec138$ddc30ef0$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-To: Ed Greshko X-Cc: Pine Discussion Forum X-X-Sender: nm@operamail.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 28 Jun 1999, Ed Greshko wrote: > > Also, it would be nice > > to be able to have the option of having a read-only pinerc. > > What do you feel would be the value in that? Here are two reasons: * It would be a way to avoid those pesky messages that say `unexpected pinerc change -- do you want to overwrite your pinerc?' I get these msgs all the time (and have posted to this list about them) because I almost always have many instances of Pine running at the same time and Pine does not like it when the two instances get out of sync for some reason (usually I think it is the window position settings). * I help a lot of people with setting up, configuring, and optimizing Pine and it would be great if during part of that process I could change their pinerc to be read-only so I know it won't change on me while I'm doing an experiment. THIS is how I found the bug I reported. I hope this makes sense, 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, 28 Jun 1999 08:54:37 -0700 (PDT) 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 IAA28112 for ; Mon, 28 Jun 1999 08:54:36 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA24917; Mon, 28 Jun 1999 08:54:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA11467; Mon, 28 Jun 1999 08:54:03 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA20702 for ; Mon, 28 Jun 1999 08:48:13 -0700 Received: from wolfenet.com (ratty.wolfe.net [204.157.98.9]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA14609 for ; Mon, 28 Jun 1999 08:48:12 -0700 Received: from sea-pm3-8-p119.wolfenet.com (sea-pm3-8-p119.wolfenet.com [206.159.18.119]) by wolfenet.com (8.9.3/8.9.3) with ESMTP id IAA07617; Mon, 28 Jun 1999 08:48:10 -0700 (PDT) Message-Id: Date: Mon, 28 Jun 1999 08:45:58 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Nancy McGough To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: <000701bec169$a2561570$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-To: Pine Discussion Forum X-X-Sender: nm@operamail.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 28 Jun 1999, Ed Greshko wrote: > How does the assurance improve/differ over the process which asks > you to confirm your changes? Other than adding to the complexity, > find the pinerc file, make it writeable, go back to pine, make the > changes, answer the "commit" question, make pinerc file read-only, I > can't see where there is added value or security. But, I've been > known to be dense. :-) Pine makes some changes to the pinerc that it does not ask you to confirm so currently there is no way to prevent these changes that I know. Examples are last-version-used and last-time-pruned (I didn't go check the exact wording of these variables). Are you convinced yet Ed?! -- 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, 28 Jun 1999 09:37:30 -0700 (PDT) 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 JAA29403 for ; Mon, 28 Jun 1999 09:37:29 -0700 (PDT) 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 JAA14450; Mon, 28 Jun 1999 09:37:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA20792; Mon, 28 Jun 1999 09:36:48 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA16070 for ; Mon, 28 Jun 1999 09:32:38 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA18373 for ; Mon, 28 Jun 1999 09:32:37 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 28 Jun 1999 11:32:32 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Tue, 29 Jun 1999 00:31:58 +0800 Message-Id: <002701bec183$a688c3d0$1511b381@twntpe.cdc.com> Date: Tue, 29 Jun 1999 00:31:19 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Nancy McGough" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nancy, > * It would be a way to avoid those pesky messages that say `unexpected > pinerc change -- do you want to overwrite your pinerc?' I get these > msgs all the time (and have posted to this list about them) because > I almost always have many instances of Pine running at the same time > and Pine does not like it when the two instances get out of sync for > some reason (usually I think it is the window position settings). I wasn't aware that multiple instances of pcpine or pine was actually supported. In any event, if pine is re-writing its pinerc file with "widow position settings" then wouldn't it stand to reason that if you made the file read-only and pine may complain about not being able to write the position information. Also, even if it doesn't complain, I gather it is re-writing this information for a pupose. If the file is read-only you may be causing another feature to break. > * I help a lot of people with setting up, configuring, and optimizing > Pine and it would be great if during part of that process I could > change their pinerc to be read-only so I know it won't change on me > while I'm doing an experiment. THIS is how I found the bug I > reported. > > I hope this makes sense, To a degree. Regards, Ed 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, 28 Jun 1999 10:09:54 -0700 (PDT) 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 KAA30154 for ; Mon, 28 Jun 1999 10:09:52 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27423; Mon, 28 Jun 1999 10:09:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA15137; Mon, 28 Jun 1999 10:09:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA31552 for ; Mon, 28 Jun 1999 10:04:16 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA26550 for ; Mon, 28 Jun 1999 10:04:15 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 28 Jun 1999 12:04:11 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Tue, 29 Jun 1999 01:03:43 +0800 Message-Id: <002b01bec188$1663e0f0$1511b381@twntpe.cdc.com> Date: Tue, 29 Jun 1999 01:03:04 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Nancy McGough" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Nancy, > > How does the assurance improve/differ over the process which asks > > you to confirm your changes? Other than adding to the complexity, > > find the pinerc file, make it writeable, go back to pine, make the > > changes, answer the "commit" question, make pinerc file read-only, I > > can't see where there is added value or security. But, I've been > > known to be dense. :-) > > Pine makes some changes to the pinerc that it does not ask you to > confirm so currently there is no way to prevent these changes that I > know. Examples are last-version-used and last-time-pruned (I didn't go > check the exact wording of these variables). > > Are you convinced yet Ed?! Actually, you've convinced me that the pinerc file should *not* be made read-only. I'd forgotten about the "last-time-pruned" variable. Not allowing pine to re-write the file would seem to break the feature of pruning the sent mail folder at end/start of month. If an application relies on a file for certain status information then not allowing the application to update its status is doing a disservice to the implementation. Sounds like what you really need is the equivalent of the unix "pinerc.fixed" in the PC world. Regards, Ed 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, 28 Jun 1999 10:26:27 -0700 (PDT) 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 KAA30491 for ; Mon, 28 Jun 1999 10:26:26 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27999; Mon, 28 Jun 1999 10:26:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA21681; Mon, 28 Jun 1999 10:25:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18724 for ; Mon, 28 Jun 1999 10:22:13 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA29076 for ; Mon, 28 Jun 1999 10:22:12 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id RAA11341 for pine-info@u.washington.edu; Mon, 28 Jun 1999 17:27:31 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Mon, 28 Jun 99 10:27 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id KAA12560 for ; Mon, 28 Jun 1999 10:10:02 -0700 Message-Id: Date: Mon, 28 Jun 1999 10:10:01 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: <002701bec183$a688c3d0$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 29 Jun 1999, Ed Greshko wrote: > Nancy, > > > * It would be a way to avoid those pesky messages that say `unexpected > > pinerc change -- do you want to overwrite your pinerc?' I get these > > msgs all the time (and have posted to this list about them) because > > I almost always have many instances of Pine running at the same time > > and Pine does not like it when the two instances get out of sync for > > some reason (usually I think it is the window position settings). > > I wasn't aware that multiple instances of pcpine or pine was actually > supported. It is, and it isn't. It is just not designed to only allow one instance. I've not had this problem myself. I do run multiple instances fairly regularly (ussualy by accedent), and the only problem that I've run into is the speed at which it trys to obtain the lock for an open folder, and that it makes both instances read only. It's more an annoyance than anything in my mind... > In any event, if pine is re-writing its pinerc file with "widow > position settings" then wouldn't it stand to reason that if you made > the file read-only and pine may complain about not being able to write > the position information. Also, even if it doesn't complain, I gather > it is re-writing this information for a pupose. If the file is > read-only you may be causing another feature to break. As far as I know, Window possitions are not storred in the pinerc file. This was a bit confusing to me. Making the file read only will cause problems of various nature, but it really shouldn't break any feature. And the not being able to exit pine I'd say is a broken feature. And particularly badly broken... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 28 Jun 1999 13:29:34 -0700 (PDT) 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 NAA02174 for ; Mon, 28 Jun 1999 13:29:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA00585; Mon, 28 Jun 1999 13:29:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA26394; Mon, 28 Jun 1999 13:28:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA15240 for ; Mon, 28 Jun 1999 13:24:56 -0700 Received: from issfire.co.palm-beach.fl.us (issfire.co.palm-beach.fl.us [151.132.50.198]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA20965 for ; Mon, 28 Jun 1999 13:24:55 -0700 Received: from issfire.co.palm-beach.fl.us (root@localhost) by issfire.co.palm-beach.fl.us with ESMTP id QAA16715; Mon, 28 Jun 1999 16:24:46 -0400 (EDT) Received: from ermasotelo.co.palm-beach.fl.us ([151.132.16.86]) by issfire.co.palm-beach.fl.us with SMTP id QAA16711; Mon, 28 Jun 1999 16:24:44 -0400 (EDT) Message-Id: <3777D9EA.3961@co.palm-beach.fl.us> Date: Mon, 28 Jun 1999 16:24:10 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Alex Sotelo To: Pine Discussion Forum Subject: Re: read-only pinerc and PC-Pine References: <002b01bec188$1663e0f0$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't have PC-pine, but what I would do is put a batch file in the startup folder that will make a backup copy of the .pinerc file, that way you will always have something to rely upon in case they (or you) mess up the current .pinerc. Just my $0.02 Ed Greshko wrote: > > > > Are you convinced yet Ed?! > > Actually, you've convinced me that the pinerc file should *not* be made > read-only. > > I'd forgotten about the "last-time-pruned" variable. Not allowing pine to > re-write the file would seem to break the feature of pruning the sent mail > folder at end/start of month. > > If an application relies on a file for certain status information then not > allowing the application to update its status is doing a disservice to the > implementation. > > Sounds like what you really need is the equivalent of the unix "pinerc.fixed" in > the PC world. > > Regards, > Ed -- Alex Sotelo home: mailto:asotelo@freenet.tlh.fl.us work: mailto:asotelo@co.palm-beach.fl.us 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, 28 Jun 1999 14:27:03 -0700 (PDT) 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 OAA03154 for ; Mon, 28 Jun 1999 14:27:02 -0700 (PDT) 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 OAA02224; Mon, 28 Jun 1999 14:27:00 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA02548; Mon, 28 Jun 1999 14:26:37 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA16000 for ; Mon, 28 Jun 1999 14:23:02 -0700 Received: from dante15.u.washington.edu (leibrand@dante15.u.washington.edu [140.142.15.41]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA29826 for ; Mon, 28 Jun 1999 14:23:00 -0700 Received: from localhost (leibrand@localhost) by dante15.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA74418 for ; Mon, 28 Jun 1999 14:23:00 -0700 Message-Id: Date: Mon, 28 Jun 1999 14:22:59 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: <002b01bec188$1663e0f0$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 29 Jun 1999, Ed Greshko wrote: > Nancy, > > > Pine makes some changes to the pinerc that it does not ask you to > > confirm so currently there is no way to prevent these changes that I > > know. Examples are last-version-used and last-time-pruned (I didn't go > > check the exact wording of these variables). > > > > Are you convinced yet Ed?! > > Actually, you've convinced me that the pinerc file should *not* be made > read-only. > > I'd forgotten about the "last-time-pruned" variable. Not allowing pine to > re-write the file would seem to break the feature of pruning the sent mail > folder at end/start of month. > > If an application relies on a file for certain status information then not > allowing the application to update its status is doing a disservice to the > implementation. > > Sounds like what you really need is the equivalent of the unix "pinerc.fixed" in > the PC world. > Maybe so, but Pine should be able to quit when it can't write to the .pinerc. For example, it quits just fine if you answer no to the "unexpected pinerc change - overwrite with current config?" question. It should say something like "unable to write pinerc (read-only). quit without saving changes?". -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Mon, 28 Jun 1999 14:53:39 -0700 (PDT) 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 OAA03716 for ; Mon, 28 Jun 1999 14:53:38 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA03006; Mon, 28 Jun 1999 14:53:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA29242; Mon, 28 Jun 1999 14:53:00 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA25266 for ; Mon, 28 Jun 1999 14:49:05 -0700 Received: from nova.edmonds.wednet.edu (kidwellj@nova.edmonds.wednet.edu [168.99.160.78]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA00622 for ; Mon, 28 Jun 1999 14:49:05 -0700 Received: from localhost (kidwellj@localhost) by nova.edmonds.wednet.edu (8.8.7/8.8.7) with SMTP id OAA07296 for ; Mon, 28 Jun 1999 14:49:17 -0700 (PDT) Message-Id: Date: Mon, 28 Jun 1999 14:49:17 -0700 (PDT) Reply-To: kidwellj@nova.edmonds.wednet.edu Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeremy Kidwell To: Pine Discussion Forum Subject: Microsoft Exchange MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am working with MS Exchange and pine attempting some sort of migration. While there is support for the mailboxes and folders, I can't seem to find anything that will migrate the .addressbook to an exchange readable format. Has anyone come upon a similiar situation? Also - I am experiencing difficulties using my exchange inbox as a collection list. I get the error message "The special name "INBOX" cannot be used in this context." Any assistance would be greatly appreciated. -------------------------------- - Jeremy Kidwell - - kidwellj@edmonds.wednet.edu - - - - Telecommunications - SPU - - Tech Support - ESD - -------------------------------- -- ----------------------------------------------------------------- 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, 28 Jun 1999 15:27:27 -0700 (PDT) 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 PAA05002 for ; Mon, 28 Jun 1999 15:27:26 -0700 (PDT) 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 PAA24430; Mon, 28 Jun 1999 15:27:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA04783; Mon, 28 Jun 1999 15:26:59 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA47816 for ; Mon, 28 Jun 1999 15:23:16 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA03150; Mon, 28 Jun 1999 15:23:15 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id WAA13860; Mon, 28 Jun 1999 22:28:07 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Mon, 28 Jun 99 15:28 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA14925; Mon, 28 Jun 1999 15:19:44 -0700 Message-Id: Date: Mon, 28 Jun 1999 15:19:44 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 28 Jun 1999, Scott Leibrand wrote: > Maybe so, but Pine should be able to quit when it can't write to the > .pinerc. For example, it quits just fine if you answer no to the > "unexpected pinerc change - overwrite with current config?" question. It > should say something like "unable to write pinerc (read-only). quit > without saving changes?". My Pine (running on Linux), has absolutely no problem with a read only .pinerc. I didn't believe that this was a problem, in fact, I think that I have run into cases where the owner has been changed to root, and I as jrasku have not been able to write to it. Maybe this is a quirk with PC-Pine? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 28 Jun 1999 16:59:06 -0700 (PDT) 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 QAA07014 for ; Mon, 28 Jun 1999 16:59:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA06151; Mon, 28 Jun 1999 16:59:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA07781; Mon, 28 Jun 1999 16:58:39 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA43218 for ; Mon, 28 Jun 1999 16:55:15 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA15181; Mon, 28 Jun 1999 16:55:14 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP; Mon, 28 Jun 1999 18:55:09 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Tue, 29 Jun 1999 07:54:52 +0800 Message-Id: <000501bec1c1$85aba4a0$1511b381@twntpe.cdc.com> Date: Tue, 29 Jun 1999 07:54:12 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Scott Leibrand" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Scott, > Maybe so, but Pine should be able to quit when it can't write to the > .pinerc. For example, it quits just fine if you answer no to the > "unexpected pinerc change - overwrite with current config?" question. It > should say something like "unable to write pinerc (read-only). quit > without saving changes?". No disagreement on that point. Probably a simple problem with file status checking in the WinXX version of pine which has probably existed since day 1. My feeling is that the implementers never intended anyone to make the pinerc read-only and therefore never tested it. Regards, Ed 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, 28 Jun 1999 17:27:52 -0700 (PDT) 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 RAA07367 for ; Mon, 28 Jun 1999 17:27:50 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA06718; Mon, 28 Jun 1999 17:27:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA08357; Mon, 28 Jun 1999 17:27:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA50258 for ; Mon, 28 Jun 1999 17:24:05 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA24418 for ; Mon, 28 Jun 1999 17:24:04 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Mon, 28 Jun 1999 19:23:59 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Tue, 29 Jun 1999 08:23:19 +0800 Message-Id: <000801bec1c5$7e9f74d0$1511b381@twntpe.cdc.com> Date: Tue, 29 Jun 1999 08:22:38 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: read-only pinerc and PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jessica Rasku" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > I wasn't aware that multiple instances of pcpine or pine was actually > > supported. > > It is, and it isn't. It is just not designed to only allow one > instance. You may find it interesting to read the tech-notes supplied with pine. A portion of the document reads: PC-Pine does not do any folder locking. It depends on IMAP servers to handle locking of remote folders. It is assumed that only one Pine session can be running on the PC at a time, so there is no contention issue around folders on the PC itself. The text prior to that statement is also of interest as it discusses the Unix file locking employed by pine. I feel that if an application is "not designed" to allow a function or feature then the function or feature is "unsupported". > As far as I know, Window possitions are not storred in the pinerc > file. This was a bit confusing to me. Making the file read only will > cause problems of various nature, but it really shouldn't break any > feature. And the not being able to exit pine I'd say is a broken feature. > And particularly badly broken... >From the pinerc file of PCpine: # Window position in the format: CxR+X+Y # Where C and R are the window size in characters and X and Y are the # screen position of the top left corner of the window. window-position=98x32+17+1 You said, "Making the file read only will cause problems of various nature". If the file is read-only and pine can't write information it relies upon to make features/functions work in the way they were designed then that is a feature you've managed to break. Of course, the pine implementers could "fix" the problem by inserting a disclaimer into the source which indicates that a read-only pinerc is unsupported. I'm sure they'd have to get very specific in their wording. But, I don't really want to turn them into lawyers. :-) Regards, Ed 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, 29 Jun 1999 00:44:10 -0700 (PDT) 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 AAA11743 for ; Tue, 29 Jun 1999 00:44:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA13227; Tue, 29 Jun 1999 00:44:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id AAA14329; Tue, 29 Jun 1999 00:43:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id AAA25584 for ; Tue, 29 Jun 1999 00:39:10 -0700 Received: from mail.cs.tu-berlin.de (mail.cs.tu-berlin.de [130.149.17.13]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id AAA21383 for ; Tue, 29 Jun 1999 00:39:03 -0700 Received: from swamp.bayern.net (gator@gator.isdn.cs.tu-berlin.de [130.149.148.15]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id JAA03186 for ; Tue, 29 Jun 1999 09:36:00 +0200 (MET DST) Received: (from gator@localhost) by swamp.bayern.net (8.9.3/8.9.3) id JAA03324; Tue, 29 Jun 1999 09:35:19 +0200 Message-Id: Date: Tue, 29 Jun 1999 09:35:19 +0200 (MEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Daum To: Pine Discussion Forum Subject: read-only pinerc: desperately needed! In-Reply-To: <000801bec1c5$7e9f74d0$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: gator@gator.isdn.cs.tu-berlin.de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, some people here raised the question, whether being able to run Pine with a read-only configuration would be of any use. I personally am desperately looking for a good way how to do exactly this. Here's the background: I am maintaining a PC-pool (running Win98) at a university of social work. Most students use the pool very infrequently - often they only show up to print out something they have written elsewhere. For this reason, they normally don't have and don't need their own home directories - it simply wouldn't be worth the effort. What pretty much all of them do want, however, is access to email. For this, we create accounts for them on our mail server. Traditionally, users were telnetting to the mail server and running pine there. Many students have major difficulties with this. What I would like to do, is set up PC-pine in a network directory without write permission, pre-configured in a way, that users can access their email via IMAP. Actually, this works fairly well: On startup, pine will ask for the username and password and from there on function as expected - I did not notice any serious problem or crashes as it has been reported here. What is irritating, however, and will scare inexperienced users (pretty much all of them) is that pine will issue plenty of warnings and error messages about being unable to write to pinerc and other files. If there was a command line flag to tell pine that it is running read-only (basically just suppressing all those error messages), most of my problems with this setup would be solved. Did I overlook something? Anybody knows a better way? Or maybe a Windoze email client that is better suited for this purpose (I personally would prefer pine). It looks like the sources for PC-Pine are not available, so I can't just comment out any unwanted error message and recompile the program. Maybe any of the Pine developers can be convinced, that such a "read-only mode" would be a good thing (tm)? Regards, Peter -- __o Peter Daum _'\<_ - pgp messages welcome - ____(_)/(_) -- ----------------------------------------------------------------- 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, 29 Jun 1999 08:02:13 -0700 (PDT) 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 IAA20657 for ; Tue, 29 Jun 1999 08:02:11 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA19822; Tue, 29 Jun 1999 08:02:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA21170; Tue, 29 Jun 1999 08:01:41 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA48338 for ; Tue, 29 Jun 1999 07:57:45 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA30776 for ; Tue, 29 Jun 1999 07:57:44 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA18226 for ; Tue, 29 Jun 1999 07:57:43 -0700 Message-Id: Date: Tue, 29 Jun 1999 07:57:43 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: read-only pinerc: desperately needed! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I don't know if this would accomplish exactly what you want, but could you just run Pine with a -p c:\temp flag to force it to put everything in c:\temp, and then run a batch file to deltree c:\temp and mkdir c:\temp? This would let pine have write access to its config files, and then delete the config files as soon as they're no longer in use. If you don't want to restart between users, you could also have the batch file run every time you run pine. For example, the Pine icon could link to c:\pine.bat, which could say something like: deltree c:\temp mkdir c:\temp (if necessary) xcopy %networkpath%\pine\*.* c:\temp %networkpath%\pine\pine.exe -p c:\temp\pinerc Would that do any good? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Tue, 29 Jun 1999, Peter Daum wrote: > Hi, > > some people here raised the question, whether being able to run > Pine with a read-only configuration would be of any use. I > personally am desperately looking for a good way how to do > exactly this. Here's the background: > > I am maintaining a PC-pool (running Win98) at a university of > social work. Most students use the pool very infrequently - often > they only show up to print out something they have written > elsewhere. For this reason, they normally don't have and don't > need their own home directories - it simply wouldn't be worth the > effort. > > What pretty much all of them do want, however, is access to > email. For this, we create accounts for them on our mail server. > Traditionally, users were telnetting to the mail server and > running pine there. Many students have major difficulties with > this. > > What I would like to do, is set up PC-pine in a network directory > without write permission, pre-configured in a way, that users can > access their email via IMAP. Actually, this works fairly well: On > startup, pine will ask for the username and password and from > there on function as expected - I did not notice any serious > problem or crashes as it has been reported here. > > What is irritating, however, and will scare inexperienced users > (pretty much all of them) is that pine will issue plenty of > warnings and error messages about being unable to write to pinerc > and other files. If there was a command line flag to tell pine > that it is running read-only (basically just suppressing all > those error messages), most of my problems with this setup would > be solved. > > Did I overlook something? Anybody knows a better way? Or maybe a > Windoze email client that is better suited for this purpose (I > personally would prefer pine). It looks like the sources for > PC-Pine are not available, so I can't just comment out any > unwanted error message and recompile the program. Maybe any of > the Pine developers can be convinced, that such a "read-only > mode" would be a good thing (tm)? > > Regards, > Peter > 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, 29 Jun 1999 11:10:59 -0700 (PDT) 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 LAA24776 for ; Tue, 29 Jun 1999 11:10:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA25284; Tue, 29 Jun 1999 11:10:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA29264; Tue, 29 Jun 1999 11:10:26 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24428 for ; Tue, 29 Jun 1999 11:05:44 -0700 Received: from q7.q7.com (joey@q7.q7.com [206.58.126.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA16913 for ; Tue, 29 Jun 1999 11:05:43 -0700 Received: from localhost (joey@localhost) by q7.q7.com (8.9.3/8.9.3) with ESMTP id LAA07903 for ; Tue, 29 Jun 1999 11:05:43 -0700 (PDT) Message-Id: Date: Tue, 29 Jun 1999 11:05:43 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Joe Pruett To: Pine Discussion Forum Subject: the charset exploit In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN so, is it possible to restrict what are legal values for the charset option? it seems like alpha, numeric, and dashes should be enough. i'm guessing this is in some mime or other rfc. -- ----------------------------------------------------------------- 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, 29 Jun 1999 11:29:55 -0700 (PDT) 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 LAA25211 for ; Tue, 29 Jun 1999 11:29:54 -0700 (PDT) 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 LAA13502; Tue, 29 Jun 1999 11:29:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA05999; Tue, 29 Jun 1999 11:29:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA24394 for ; Tue, 29 Jun 1999 11:25:10 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA10366 for ; Tue, 29 Jun 1999 11:25:09 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id SAA09605; Tue, 29 Jun 1999 18:29:04 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 29 Jun 99 11:29 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id LAA24204; Tue, 29 Jun 1999 11:18:25 -0700 Message-Id: Date: Tue, 29 Jun 1999 11:18:16 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: read-only pinerc: desperately needed! In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Peter Daum X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 29 Jun 1999, Peter Daum wrote: > Did I overlook something? Anybody knows a better way? Or maybe a > Windoze email client that is better suited for this purpose (I > personally would prefer pine). It looks like the sources for > PC-Pine are not available, so I can't just comment out any > unwanted error message and recompile the program. Maybe any of > the Pine developers can be convinced, that such a "read-only > mode" would be a good thing (tm)? Now this may be a bit of a leap, but could you possibly set up the PC-Pine so that it will come up as read write, but gets over written every time that a person logs out? It sounds like you would have a single username/password combination to get into this setup, but wouldn't there be a way to run some sort of script to have the ``actuall files'' stored in a backup somewhere, and the ``working files'' created and destroyed with each login? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 29 Jun 1999 12:23:14 -0700 (PDT) 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 MAA26178 for ; Tue, 29 Jun 1999 12:23:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA15075; Tue, 29 Jun 1999 12:23:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA02481; Tue, 29 Jun 1999 12:22:35 -0700 Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA18896 for ; Tue, 29 Jun 1999 12:18:04 -0700 Received: from vergil01.u.washington.edu (leibrand@vergil01.u.washington.edu [140.142.12.6]) by jason02.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA39704; Tue, 29 Jun 1999 12:18:03 -0700 Received: from localhost (leibrand@localhost) by vergil01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA54290; Tue, 29 Jun 1999 12:18:02 -0700 Message-Id: Date: Tue, 29 Jun 1999 12:18:02 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: read-only pinerc: desperately needed! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 29 Jun 1999, Jessica Rasku wrote: > On Tue, 29 Jun 1999, Peter Daum wrote: > > > Did I overlook something? Anybody knows a better way? Or maybe a > > Windoze email client that is better suited for this purpose (I > > personally would prefer pine). It looks like the sources for > > PC-Pine are not available, so I can't just comment out any > > unwanted error message and recompile the program. Maybe any of > > the Pine developers can be convinced, that such a "read-only > > mode" would be a good thing (tm)? > > Now this may be a bit of a leap, but could you possibly set up the > PC-Pine so that it will come up as read write, but gets over written every > time that a person logs out? It sounds like you would have a single > username/password combination to get into this setup, but wouldn't there > be a way to run some sort of script to have the ``actuall files'' stored > in a backup somewhere, and the ``working files'' created and destroyed > with each login? > Exactly. With the batch file I started to write, for example, you could copy a "template" pinerc that had everything but the user's log-on info. They could then customize it, and when they log out it would get deleted. Is this the kind of think you want to do? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 29 Jun 1999 13:53:14 -0700 (PDT) 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 NAA28749 for ; Tue, 29 Jun 1999 13:53:13 -0700 (PDT) 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 NAA17425; Tue, 29 Jun 1999 13:53:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA12141; Tue, 29 Jun 1999 13:52:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA16808 for ; Tue, 29 Jun 1999 13:48:40 -0700 Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA25268 for ; Tue, 29 Jun 1999 13:48:34 -0700 Received: from swamp.bayern.net (gator@gator.isdn.cs.tu-berlin.de [130.149.148.15]) by mail.cs.tu-berlin.de (8.9.1/8.9.1) with ESMTP id WAA29504 for ; Tue, 29 Jun 1999 22:46:23 +0200 (MET DST) Received: (from gator@localhost) by swamp.bayern.net (8.9.3/8.9.3) id WAA02844; Tue, 29 Jun 1999 22:46:04 +0200 Message-Id: Date: Tue, 29 Jun 1999 22:46:04 +0200 (MEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Peter Daum To: Pine Discussion Forum Subject: Re: read-only pinerc: desperately needed! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: gator@gator.isdn.cs.tu-berlin.de X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, On Tue, 29 Jun 1999, Jessica Rasku wrote: [...] > Now this may be a bit of a leap, but could you possibly set up the > PC-Pine so that it will come up as read write, but gets over written every > time that a person logs out? It sounds like you would have a single > username/password combination to get into this setup, but wouldn't there > be a way to run some sort of script to have the ``actuall files'' stored > in a backup somewhere, and the ``working files'' created and destroyed > with each login? If there is no other way, I might do something like that, but it certainly would not be a particularly good solution and also possibly misleading for users who save a message and can't find it afterwards, because it was automatically deleted later on ... regards, Peter -- __o Peter Daum _'\<_ - pgp messages welcome - ____(_)/(_) 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, 1 Jul 1999 02:54:06 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id CAA01436 for ; Thu, 1 Jul 1999 02:54:05 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA06841; Thu, 1 Jul 1999 02:54:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA04704; Thu, 1 Jul 1999 02:53:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA17436 for ; Thu, 1 Jul 1999 02:47:26 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA22063 for ; Thu, 1 Jul 1999 02:47:24 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id PAA17858 for ; Thu, 1 Jul 1999 15:17:06 +0530 (IST) Message-Id: Date: Thu, 1 Jul 1999 15:17:06 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Sending HTML attachments MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I use Pine 4.10 for Solaris and am facing a problem *sending* HTML attachments. When I send a HTML attachment, Pine attaches it with 'Content-type header: text/plain' When the recepient tries to open the attachment by clicking on it, Netscape's browser for instance, seems to interpret the attached html file as a text file by reading the 'Content-type header' and displays the html source instead. While sending a mail, is there a way to configure Pine to attach a HTML file, with the Content-type header 'text/html', so that browsers can interpret the attachment correctly? I've searched through the Pine-Info archives but haven't found a suitable solution. Any help will be sincerely appreciated. -- Thanks in advance, Srikanth -- ----------------------------------------------------------------- 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, 1 Jul 1999 09:05:36 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA07688 for ; Thu, 1 Jul 1999 09:05:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA13055; Thu, 1 Jul 1999 09:05:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA12113; Thu, 1 Jul 1999 09:04:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA26734 for ; Thu, 1 Jul 1999 09:00:51 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA09633 for ; Thu, 1 Jul 1999 09:00:51 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id MAA14963 for ; Thu, 1 Jul 1999 12:00:49 -0400 (EDT) Message-Id: Date: Thu, 1 Jul 1999 12:00:48 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I'm using Pine 3.95 on a Solaris box. Here's what I want to do: A friend sends me a nice email with some important info the body of the message. He also sends a program/word doc/picture--any other sort of *BIG* attachment. I download this to my pc and want to delete the huge file from my inbox BUT I want to save the nice text part of the message... See where I'm going with this? Questions: 1) Is there a way to do this in Pine? Prune attachment or something? I've looked around but never seen anything like it--maybe I just missed it completely? Is it in 4.10? If there isn't a way to do it in Pine (yet), is it possible to add this feature (feature request! feature request! :). It seems like it'd be pretty useful for most anyone; I can see many instances of wanting to save the text of a message, but not wanting to keep the huge attachment around. 2) What's the easiest way to do this outside of Pine? Save the message to it's own folder, open it up in emacs (or another editor) and cut out the unwanted text? Can anyone think of a more elegant (and quicker) solution? Thanks in advance for any help/ideas/support! BINO -- Subject: Haiku for computer lovers Stay the patient course Of little worth is your ire The network is down -- ----------------------------------------------------------------- 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, 1 Jul 1999 09:53:26 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA08683 for ; Thu, 1 Jul 1999 09:53:25 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA14383; Thu, 1 Jul 1999 09:53:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA13434; Thu, 1 Jul 1999 09:52:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA17586 for ; Thu, 1 Jul 1999 09:48:55 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA03144 for ; Thu, 1 Jul 1999 09:48:54 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id LAA26628; Thu, 1 Jul 1999 11:48:35 -0500 (CDT) Message-Id: Date: Thu, 1 Jul 1999 11:48:35 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bino Gopal X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Bino Gopal wrote: > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > > A friend sends me a nice email with some important info the body of the > message. He also sends a program/word doc/picture--any other sort of > *BIG* attachment. I download this to my pc and want to delete the huge > file from my inbox BUT I want to save the nice text part of the message... > See where I'm going with this? > > Questions: > 1) Is there a way to do this in Pine? Prune attachment or something? > I've looked around but never seen anything like it--maybe I just missed > it completely? Is it in 4.10? Yes. It is in 4.10. You just go into View and delete the attachment. It's very useful! 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, 1 Jul 1999 10:44:44 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA10013 for ; Thu, 1 Jul 1999 10:44:43 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA15859; Thu, 1 Jul 1999 10:44:41 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA23878; Thu, 1 Jul 1999 10:43:55 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA17368 for ; Thu, 1 Jul 1999 10:38:59 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA22621 for ; Thu, 1 Jul 1999 10:38:58 -0700 Received: by gw.learjet.com; id MAA28948; Thu, 1 Jul 1999 12:38:56 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma028749; Thu, 1 Jul 99 12:37:57 -0500 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 MAA05356 for ; Thu, 1 Jul 1999 12:37:57 -0500 (CDT) Received: from localhost (schaller@localhost) by hx02.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with SMTP id MAA06073 for ; Thu, 1 Jul 1999 12:37:56 -0500 (CDT) Message-Id: Date: Thu, 1 Jul 1999 12:37:55 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jeff To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: hx02.learjet.com: schaller owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Bino Gopal wrote: > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > want to delete the huge file from my inbox BUT I want to save the > nice text part of the message... You could forward it to yourself and make to to not include the attachment. I do this quite often, even for plain text message bodies that I want to summarize. > Thanks in advance for any help/ideas/support! Welcome! -jeff -- .~. | Jeff Schaller /V\ | Phone = (316) 946-7255, Fax = x2809 // \\ | HP-UX Client/Server /( )\ | I do not speak for the <`~'> | Bombardier Aerospace Group. 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, 1 Jul 1999 11:08:55 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA02081 for ; Thu, 1 Jul 1999 11:08:54 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA16623; Thu, 1 Jul 1999 11:08:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA17922; Thu, 1 Jul 1999 11:08:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA38706 for ; Thu, 1 Jul 1999 11:03:22 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA27624 for ; Thu, 1 Jul 1999 11:03:22 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA02634; Thu, 1 Jul 1999 14:03:18 -0400 (EDT) Message-Id: Date: Thu, 1 Jul 1999 14:03:17 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Jeff X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Well, the problem is that this doesn't preserve the original headers for sorting in whatever folder I have the messages in (right?). I've tried it, and I don't like how the original headers aren't there (for sorting and selecting messages and such). Thanks for the idea though. BINO On Thu, 1 Jul 1999, Jeff wrote: > On Thu, 1 Jul 1999, Bino Gopal wrote: > > > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > > want to delete the huge file from my inbox BUT I want to save the > > nice text part of the message... > > You could forward it to yourself and make to to not include the > attachment. I do this quite often, even for plain text message bodies > that I want to summarize. > > > Thanks in advance for any help/ideas/support! > > Welcome! > > -jeff 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, 1 Jul 1999 11:14:58 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA02276 for ; Thu, 1 Jul 1999 11:14:57 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA16810; Thu, 1 Jul 1999 11:14:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA18377; Thu, 1 Jul 1999 11:14:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA35646 for ; Thu, 1 Jul 1999 11:06:13 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA03429 for ; Thu, 1 Jul 1999 11:06:12 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id OAA02753; Thu, 1 Jul 1999 14:06:10 -0400 (EDT) Message-Id: Date: Thu, 1 Jul 1999 14:06:09 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Mike Miller X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ok, I was afraid of that. Given that the acct that has 3.95 on it is not going to be upgraded soon, and so I'm stuck with it, do I take this to mean that there's no other way to do what I want?! Anyone know of even an add-on program that I can get to do this? (Hmm, I guess if I was feeling really ambitious, I could go get the source and compile it for Solaris and run it just for myself...I'm allowed to do that, right?) BINO On Thu, 1 Jul 1999, Mike Miller wrote: > On Thu, 1 Jul 1999, Bino Gopal wrote: > > > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > > > > A friend sends me a nice email with some important info the body of the > > message. He also sends a program/word doc/picture--any other sort of > > *BIG* attachment. I download this to my pc and want to delete the huge > > file from my inbox BUT I want to save the nice text part of the message... > > See where I'm going with this? > > > > Questions: > > 1) Is there a way to do this in Pine? Prune attachment or something? > > I've looked around but never seen anything like it--maybe I just missed > > it completely? Is it in 4.10? > > Yes. It is in 4.10. You just go into View and delete the attachment. > It's very useful! > > 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, 1 Jul 1999 11:24:40 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA10856 for ; Thu, 1 Jul 1999 11:24:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA17144; Thu, 1 Jul 1999 11:24:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA18629; Thu, 1 Jul 1999 11:23:48 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA42222 for ; Thu, 1 Jul 1999 11:18:31 -0700 Received: from dante32.u.washington.edu (leibrand@dante32.u.washington.edu [140.142.15.106]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA26400 for ; Thu, 1 Jul 1999 11:18:29 -0700 Received: from localhost (leibrand@localhost) by dante32.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA83044 for ; Thu, 1 Jul 1999 11:18:28 -0700 Message-Id: Date: Thu, 1 Jul 1999 11:18:28 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Mike Miller wrote: > On Thu, 1 Jul 1999, Bino Gopal wrote: > > > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > > > > A friend sends me a nice email with some important info the body of the > > message. He also sends a program/word doc/picture--any other sort of > > *BIG* attachment. I download this to my pc and want to delete the huge > > file from my inbox BUT I want to save the nice text part of the message... > > See where I'm going with this? > > > > Questions: > > 1) Is there a way to do this in Pine? Prune attachment or something? > > I've looked around but never seen anything like it--maybe I just missed > > it completely? Is it in 4.10? > > Yes. It is in 4.10. You just go into View and delete the attachment. > It's very useful! > > Mike Actually, it's a little more complicated than that. After going into the view message section in 4.10 and pressing D to delete the message, you have to save the message to a folder (the folder it's in will work) to preserve the changes. That's the only way of "expunging" the attachment. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 1 Jul 1999 11:29:24 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA11017 for ; Thu, 1 Jul 1999 11:29:22 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA17312; Thu, 1 Jul 1999 11:29:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA19389; Thu, 1 Jul 1999 11:28:49 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22304 for ; Thu, 1 Jul 1999 11:20:40 -0700 Received: from dante32.u.washington.edu (leibrand@dante32.u.washington.edu [140.142.15.106]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA33076 for ; Thu, 1 Jul 1999 11:20:38 -0700 Received: from localhost (leibrand@localhost) by dante32.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA96102 for ; Thu, 1 Jul 1999 11:20:38 -0700 Message-Id: Date: Thu, 1 Jul 1999 11:20:38 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, of course you can get a version of Pine to use for yourself, unless your account's policies prohibit that. You may even be able to find a precompiled binary for your OS on ftp.cac.washington.edu if you're lucky. As for 3.95, I no longer use it, but I suspect you may be able to turn on full headers and set the include headers in reply flag before you forward yourself the message. This will at least let you see the full headers as they were before you forwarded it. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Thu, 1 Jul 1999, Bino Gopal wrote: > Ok, I was afraid of that. Given that the acct that has 3.95 on it is not > going to be upgraded soon, and so I'm stuck with it, do I take this to > mean that there's no other way to do what I want?! > > Anyone know of even an add-on program that I can get to do this? (Hmm, I > guess if I was feeling really ambitious, I could go get the source and > compile it for Solaris and run it just for myself...I'm allowed to do > that, right?) > > BINO > > > On Thu, 1 Jul 1999, Mike Miller wrote: > > > On Thu, 1 Jul 1999, Bino Gopal wrote: > > > > > I'm using Pine 3.95 on a Solaris box. Here's what I want to do: > > > > > > A friend sends me a nice email with some important info the body of the > > > message. He also sends a program/word doc/picture--any other sort of > > > *BIG* attachment. I download this to my pc and want to delete the huge > > > file from my inbox BUT I want to save the nice text part of the message... > > > See where I'm going with this? > > > > > > Questions: > > > 1) Is there a way to do this in Pine? Prune attachment or something? > > > I've looked around but never seen anything like it--maybe I just missed > > > it completely? Is it in 4.10? > > > > Yes. It is in 4.10. You just go into View and delete the attachment. > > It's very useful! > > > > 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, 1 Jul 1999 11:48:57 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA11539 for ; Thu, 1 Jul 1999 11:48:56 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA17867; Thu, 1 Jul 1999 11:48:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA20155; Thu, 1 Jul 1999 11:48:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA34314 for ; Thu, 1 Jul 1999 11:43:33 -0700 Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA19989 for ; Thu, 1 Jul 1999 11:43:30 -0700 Received: from localhost (PPP3-48.bom.vsnl.net.in [202.54.3.48]) by bom2.vsnl.net.in (8.9.1/8.9.1) with ESMTP id AAA32756 for ; Fri, 2 Jul 1999 00:14:00 +0530 (IST) Received: from localhost (satyap@localhost) by localhost (8.8.7/8.8.7) with ESMTP id AAA00662 for ; Fri, 2 Jul 1999 00:10:30 +0530 Message-Id: Date: Fri, 2 Jul 1999 00:10:13 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Satya To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: satyap.org: satyap owned process doing -bs X-Sender: satyap@satyap.org X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Bino Gopal wrote: > A friend sends me a nice email with some important info the body of the > message. He also sends a program/word doc/picture--any other sort of > *BIG* attachment. I download this to my pc and want to delete the huge > file from my inbox BUT I want to save the nice text part of the message... i'm on 4.04, and extremely new to this mailing list. i think you can Export the message, after pressing full (H)eaders so you get the headers too. i just tried it and it seems to work. -- Satya. Freelance website designer and CGI/Perl programmer. http://satyaonline.cjb.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; Thu, 1 Jul 1999 11:56:31 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA11659 for ; Thu, 1 Jul 1999 11:56:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA18103; Thu, 1 Jul 1999 11:56:28 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA20521; Thu, 1 Jul 1999 11:56:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA25136 for ; Thu, 1 Jul 1999 11:52:05 -0700 Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA10830 for ; Thu, 1 Jul 1999 11:52:02 -0700 Received: from localhost (PPP3-48.bom.vsnl.net.in [202.54.3.48]) by bom2.vsnl.net.in (8.9.1/8.9.1) with ESMTP id AAA24606 for ; Fri, 2 Jul 1999 00:21:56 +0530 (IST) Received: from localhost (satyap@localhost) by localhost (8.8.7/8.8.7) with ESMTP id AAA00721 for ; Fri, 2 Jul 1999 00:18:01 +0530 Message-Id: Date: Fri, 2 Jul 1999 00:17:56 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Satya To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: satyap.org: satyap owned process doing -bs X-Sender: satyap@satyap.org X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Srikanth V. Vallabhaneni wrote: > Hi all, > > I use Pine 4.10 for Solaris and am facing a problem *sending* HTML > attachments. i dont know about solaris, but on my rh5.2 it says (see below) > When I send a HTML attachment, Pine attaches it with 'Content-type > header: text/plain' When the recepient tries to open the attachment by > clicking on it, Netscape's browser for instance, seems to interpret the > attached html file as a text file by reading the 'Content-type header' > and displays the html source instead. quoted from /usr/doc/pine-4.04/tech-notes/low-level.html#MIME-send : When an attachment is to be sent, Pine sniffs through it to try to set the right label (content-type and subtype). An attachment with any lines longer than 500 characters in it or more than 10% of the characters are 8-bit it will be considered binary data. Pine will recognize (and correctly label) a few special types including GIF, JPEG, PostScript, and some audio formats. Another method which can be more robust and flexible for determining the content-type and subtype is to base it on the file extension. This method uses a [16]MIME.Types File. So you'd have to check your mime.types file. dunno where it is on solaris. And from /usr/doc/pine-4.04/tech-notes/config-notes.html#mime.types : Pine's MIME-TYPE support is based on code contributed by Hans Drexler <drexler@mpi.nl>. Pine assigns MIME Content-Types according to file name extensions found in the system-wide files /usr/local/lib/mime.types and /etc/mime.types, and a user specific ~/.mime.types file. So you could check you ~/.mime.types I'm sorry if i've stepped on anyone's toes, please don't lart me too badly :) -- Satya. Freelance website designer and CGI/Perl programmer. http://satyaonline.cjb.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; Thu, 1 Jul 1999 14:41:37 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id OAA15098 for ; Thu, 1 Jul 1999 14:41:36 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA22273; Thu, 1 Jul 1999 14:41:34 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA26325; Thu, 1 Jul 1999 14:41:06 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA48636 for ; Thu, 1 Jul 1999 14:37:03 -0700 Received: from konichiwa.cc.columbia.edu (IDENT:cu43432@konichiwa.cc.columbia.edu [128.59.59.132]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA23427 for ; Thu, 1 Jul 1999 14:37:03 -0700 Received: from localhost (fbb6@localhost) by konichiwa.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id RAA12186; Thu, 1 Jul 1999 17:37:00 -0400 (EDT) Message-Id: Date: Thu, 1 Jul 1999 17:37:00 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Freda B Birnbaum To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: fbb6@columbia.edu X-To: Pine Discussion Forum X-Cc: Freda B Birnbaum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Bino Gopal wrote: > Questions: > 1) Is there a way to do this in Pine? Prune attachment or something? > I've looked around but never seen anything like it--maybe I just missed > it completely? Is it in 4.10? > > If there isn't a way to do it in Pine (yet), is it possible to add this > feature (feature request! feature request! :). It seems like it'd be > pretty useful for most anyone; I can see many instances of wanting to save > the text of a message, but not wanting to keep the huge attachment around. > > 2) What's the easiest way to do this outside of Pine? Save the message to > it's own folder, open it up in emacs (or another editor) and cut out the > unwanted text? Can anyone think of a more elegant (and quicker) solution? How about forwarding the message to yourself, but eliminating the unwanted stuff from the forwarded message, and then deleting the original? You can even make the Subject: be whatever you ewant. (I'm going to go try this now... just got something like that!) Freda Birnbaum, fbb6@columbia.edu "Call on God, but row away from the rocks" From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 1 Jul 1999 17:01:14 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id RAA18871 for ; Thu, 1 Jul 1999 17:01:13 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA26299; Thu, 1 Jul 1999 17:01:10 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA01204; Thu, 1 Jul 1999 17:00:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA17980 for ; Thu, 1 Jul 1999 16:56:46 -0700 Received: from quartz.nbnet.nb.ca (mailserv.nbnet.nb.ca [198.164.200.18]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA08602 for ; Thu, 1 Jul 1999 16:56:45 -0700 Received: from thekrow ([207.179.135.135]) by quartz.nbnet.nb.ca (Post.Office MTA v3.5.3 release 223 ID# 607-58282U90000L90000S0V35) with SMTP id ca for ; Thu, 1 Jul 1999 20:56:44 -0300 Message-Id: <002b01bec41d$c5c0dfc0$8787b3cf@nbnet.nb.ca> Date: Thu, 1 Jul 1999 20:59:35 -0300 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "The Krow" To: Pine Discussion Forum Subject: POP MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0028_01BEC404.9FC2A740" X-To: X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0028_01BEC404.9FC2A740 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable does PC-Pine support POP servers? and if so how does one configure it to = check accounts? Thanks ------=_NextPart_000_0028_01BEC404.9FC2A740 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
does PC-Pine support POP servers? and if so how does = one=20 configure it to check accounts?
 
Thanks
 
 
------=_NextPart_000_0028_01BEC404.9FC2A740-- -- ----------------------------------------------------------------- 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, 1 Jul 1999 22:46:49 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id WAA21729 for ; Thu, 1 Jul 1999 22:46:48 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id WAA31816; Thu, 1 Jul 1999 22:46:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA08370; Thu, 1 Jul 1999 22:46:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA38670 for ; Thu, 1 Jul 1999 22:42:26 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA20554 for ; Thu, 1 Jul 1999 22:42:26 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id FAA09875; Fri, 2 Jul 1999 05:47:43 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Thu, 1 Jul 99 22:47 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id WAA18175; Thu, 1 Jul 1999 22:39:43 -0700 Message-Id: Date: Thu, 1 Jul 1999 22:39:41 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bino Gopal X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Bino Gopal wrote: > Ok, I was afraid of that. Given that the acct that has 3.95 on it is not > going to be upgraded soon, and so I'm stuck with it, do I take this to > mean that there's no other way to do what I want?! I have an idea... Lets think about this a bit though... > Anyone know of even an add-on program that I can get to do this? (Hmm, I > guess if I was feeling really ambitious, I could go get the source and > compile it for Solaris and run it just for myself...I'm allowed to do > that, right?) Pine would work fine, and if there are no limitations for doing that on the system you are using, then you can do that. Another thing that you may be able to do is: save the message in it's own folder (this is just to make things easier and safer, you won't clobber all your messages if you mess up like I'm sure we are are prone to if we are doing something a little odd), go into your shell and open that folder in your favorite editor delete (in that editor), the attachment save the resulting file return to pine, and you should have what you want I have done things similar to this myself with messages that have inline html code attached which isn't aware that the message is being sent quoted printable (the href=" (I think that's it) crashes Pine's quoted printable decoder, and is very inpolite about what the problem REALLY is (it displays the up to the block that it failed on, and then complains that it doesn't understand)). This should work, but caution is deffinately warented, always ensure that you have at least one backup before doing this... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 2 Jul 1999 07:37:49 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id HAA30361 for ; Fri, 2 Jul 1999 07:37:48 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA06432; Fri, 2 Jul 1999 07:37:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA14973; Fri, 2 Jul 1999 07:37:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA31456 for ; Fri, 2 Jul 1999 07:32:01 -0700 Received: from watsol.cc.columbia.edu (IDENT:cu789@watsol.cc.columbia.edu [128.59.39.139]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id HAA12651 for ; Fri, 2 Jul 1999 07:32:01 -0700 Received: from localhost (bino@localhost) by watsol.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA12285; Fri, 2 Jul 1999 10:31:53 -0400 (EDT) Message-Id: Date: Fri, 2 Jul 1999 10:31:52 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bino Gopal To: Pine Discussion Forum Subject: Re: Eliminating unwanted text in messages sent to me... In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: bino@columbia.edu X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 1 Jul 1999, Jessica Rasku wrote: > Pine would work fine, and if there are no limitations for doing > that on the system you are using, then you can do that. Another thing > that you may be able to do is: > > save the message in it's own folder (this is just to make things easier > and safer, you won't clobber all your messages if you mess up > like I'm sure we are are prone to if we are doing something a > little odd), > go into your shell and open that folder in your favorite editor > delete (in that editor), the attachment > save the resulting file > return to pine, and you should have what you want > > I have done things similar to this myself with messages that have > inline html code attached which isn't aware that the message is being sent > quoted printable (the href=" (I think that's it) crashes Pine's quoted > printable decoder, and is very inpolite about what the problem REALLY is > (it displays the up to the block that it failed on, and then complains > that it doesn't understand)). This should work, but caution is > deffinately warented, always ensure that you have at least one backup > before doing this... > > Jessica Thanks for the tip Jessica, but the thing is when you try to do something like this with a 1MB message, it gets hard to load into the editor, and it takes a long time, and then you have to wait to select all the text, and it's basically a big pain...I guess I should have made the 'elegant' part more clear. :) And it was a lot harder the first time or two, _before_ I saved the message into it's own folder--quite a pain to find it, know what I mean?! :PP In any case, the thing that does work the best is to export the message, which saves the main text, and NOT any of the attachments! I had never noticed that particular 'feature' until Satya suggested it (thanks Satya! :) This also preserves the *original* headers, so you can sort based on those, and not the ones you create by forwardig it. Of course, this is only relevant if you're not running 4.10 yet, but I think there's still a number of people who might find it useful. Now the only thing I want to figure out is to see if there might be a way for Pine to save the *ORIGINAL* arrival date of the message--in other words, the FIRST time it hits any of my folders...if you know where I'm going with this, feel free to reply, but I think I'll expound more in another email. Big shot out to all those who helped out by replying! Thanks much! BINO 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, 2 Jul 1999 09:04:05 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA31863 for ; Fri, 2 Jul 1999 09:04:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA08520; Fri, 2 Jul 1999 09:04:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA18535; Fri, 2 Jul 1999 09:03:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA21424 for ; Fri, 2 Jul 1999 08:58:28 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA05342 for ; Fri, 2 Jul 1999 08:58:26 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id VAA11966; Fri, 2 Jul 1999 21:27:17 +0530 (IST) Message-Id: Date: Fri, 2 Jul 1999 21:27:17 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Satya X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Satya, Thanks for the pointer. I came across a section about sending messages in MIME in which my question has almost been answered. It also seems to rule out the mime.types file as a possible answer to my question. This is from: http://www.washington.edu/pine/tech-notes.4.04/low-level.html#MIME-send and it says... 'If it is not binary data (has only a small proportion of 8-bit characters in it,) the attachment is considered 8-bit text. 8-bit text attachments are labeled "text/plain" with charset set to the value of the user's character-set variable. If an attachment is ASCII (no 8-bit characters) and contains no ESCAPE, ^N, or ^O characters (the characters used by some international character sets), then it is considered plain ASCII text. Such attachments are given the MIME label "text/plain; charset=US-ASCII", regardless of the setting of the user's character-set variable.' I am still wondering if anyone has come across a workaround where one can distinguish between plain text and HTML files while sending mails. -- Thanks, Srikanth On Fri, 2 Jul 1999 at 12:17am +0530, Satya said: > On Thu, 1 Jul 1999, Srikanth V. Vallabhaneni wrote: > > > Hi all, > > > > I use Pine 4.10 for Solaris and am facing a problem *sending* HTML > > attachments. > > i dont know about solaris, but on my rh5.2 it says (see below) > > > When I send a HTML attachment, Pine attaches it with 'Content-type > > header: text/plain' When the recepient tries to open the attachment by > > clicking on it, Netscape's browser for instance, seems to interpret the > > attached html file as a text file by reading the 'Content-type header' > > and displays the html source instead. > > quoted from > /usr/doc/pine-4.04/tech-notes/low-level.html#MIME-send : > > When an attachment is to be sent, Pine sniffs through it to try to set > the right label (content-type and subtype). An attachment with any > lines longer than 500 characters in it or more than 10% of the > characters are 8-bit it will be considered binary data. Pine will > recognize (and correctly label) a few special types including GIF, > JPEG, PostScript, and some audio formats. Another method which can be > more robust and flexible for determining the content-type and subtype > is to base it on the file extension. This method uses a [16]MIME.Types > File. > > So you'd have to check your mime.types file. dunno where it is on solaris. > > And from > /usr/doc/pine-4.04/tech-notes/config-notes.html#mime.types : > > Pine's MIME-TYPE support is based on code contributed by Hans Drexler > <drexler@mpi.nl>. Pine assigns MIME Content-Types according to > file name extensions found in the system-wide files > /usr/local/lib/mime.types and /etc/mime.types, and a user specific > ~/.mime.types file. > > So you could check you ~/.mime.types > > I'm sorry if i've stepped on anyone's toes, please don't lart me too badly > :) > > 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, 2 Jul 1999 09:35:58 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA32582 for ; Fri, 2 Jul 1999 09:35:56 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA09369; Fri, 2 Jul 1999 09:35:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA22006; Fri, 2 Jul 1999 09:35:14 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA51946 for ; Fri, 2 Jul 1999 09:31:07 -0700 Received: from sttlpop2.sttl.uswest.net (sttlpop2.sttl.uswest.net [206.81.192.2]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id JAA09746 for ; Fri, 2 Jul 1999 09:31:07 -0700 Received: (qmail 29989 invoked by alias); 2 Jul 1999 16:31:05 -0000 Received: (qmail 29961 invoked by uid 0); 2 Jul 1999 16:31:04 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop2.sttl.uswest.net with SMTP; 2 Jul 1999 16:31:04 -0000 Message-Id: Date: Fri, 2 Jul 1999 09:29:25 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Srikanth V. Vallabhaneni" X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Are you saying that you tried the mime.types suggestion and it didn't work? Or is your complaint that the section you cite below doesn't refer to the mime.types override? -teg On Fri, 2 Jul 1999, Srikanth V. Vallabhaneni wrote: > I came across a section about sending messages in MIME in which my > question has almost been answered. It also seems to rule out the > mime.types file as a possible answer to my question. This is from: > > http://www.washington.edu/pine/tech-notes.4.04/low-level.html#MIME-send 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, 2 Jul 1999 09:51:41 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA00055 for ; Fri, 2 Jul 1999 09:51:40 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA09711; Fri, 2 Jul 1999 09:51:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA20913; Fri, 2 Jul 1999 09:51:14 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA31474 for ; Fri, 2 Jul 1999 09:46:07 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA11782 for ; Fri, 2 Jul 1999 09:46:05 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id WAA13106; Fri, 2 Jul 1999 22:15:25 +0530 (IST) Message-Id: Date: Fri, 2 Jul 1999 22:15:25 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN My mimetype search path points to my home directory and my .mime.types file in the same directory has the following entry: text/html html htm But in spite of that, when I try to attach a html file, it still interprets it as a plain text file and defines 'content-type' as text/plain My question is: Going by that what I've observed and what the section says, it seems to suggest that the .mime.types file will be overridden by the content of the attachment. Am I right here? and if I am, is there a workaround to define the 'content-type' header for a html attachment as text/html rather than text/plain so that external browsers can correctly interpret the attachment as a html file and not a text file? -- Thanks, Srikanth On Fri, 2 Jul 1999 at 9:29am -0700, Terry Gray said: > Are you saying that you tried the mime.types suggestion and it didn't > work? Or is your complaint that the section you cite below doesn't refer > to the mime.types override? > > -teg > > On Fri, 2 Jul 1999, Srikanth V. Vallabhaneni wrote: > > > I came across a section about sending messages in MIME in which my > > question has almost been answered. It also seems to rule out the > > mime.types file as a possible answer to my question. This is from: > > > > http://www.washington.edu/pine/tech-notes.4.04/low-level.html#MIME-send > > 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, 2 Jul 1999 10:18:07 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA00772 for ; Fri, 2 Jul 1999 10:18:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA10388; Fri, 2 Jul 1999 10:18:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA21856; Fri, 2 Jul 1999 10:17:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA46598 for ; Fri, 2 Jul 1999 10:13:35 -0700 Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA32761 for ; Fri, 2 Jul 1999 10:13:31 -0700 Received: from localhost (PPP3-49.bom.vsnl.net.in [202.54.3.49]) by bom2.vsnl.net.in (8.9.1/8.9.1) with ESMTP id WAA18498 for ; Fri, 2 Jul 1999 22:43:59 +0530 (IST) Received: from localhost (satyap@localhost) by localhost (8.8.7/8.8.7) with ESMTP id WAA00525 for ; Fri, 2 Jul 1999 22:40:28 +0530 Message-Id: Date: Fri, 2 Jul 1999 22:40:27 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Satya To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: satyap.org: satyap owned process doing -bs X-Sender: satyap@satyap.org X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN well, i'm not really surprised that pine thinks it's a plain text file, considering that that's precisely what it is. it's the extension (.htm or .html) that makes the difference -- that, and the markup. i really think you should match the file's extension with what all the *mime.types files on your system say. -- Satya. Freelance website designer and CGI/Perl programmer. http://satyaonline.cjb.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, 2 Jul 1999 10:22:35 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA00839 for ; Fri, 2 Jul 1999 10:22:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA10505; Fri, 2 Jul 1999 10:22:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA24161; Fri, 2 Jul 1999 10:22:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA25176 for ; Fri, 2 Jul 1999 10:15:31 -0700 Received: from sttlpop2.sttl.uswest.net (sttlpop2.sttl.uswest.net [206.81.192.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id KAA32398 for ; Fri, 2 Jul 1999 10:15:30 -0700 Received: (qmail 6986 invoked by alias); 2 Jul 1999 17:15:28 -0000 Received: (qmail 6961 invoked by uid 0); 2 Jul 1999 17:15:27 -0000 Received: from mdsl227.sttl.uswest.net (209.181.94.228) by sttlpop2.sttl.uswest.net with SMTP; 2 Jul 1999 17:15:27 -0000 Message-Id: Date: Fri, 2 Jul 1999 10:13:48 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Srikanth V. Vallabhaneni" X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 2 Jul 1999, Srikanth V. Vallabhaneni wrote: > My mimetype search path points to my home directory and my .mime.types > file in the same directory has the following entry: > > text/html html htm > > But in spite of that, when I try to attach a html file, it still > interprets it as a plain text file and defines 'content-type' as > text/plain > > My question is: > > Going by that what I've observed and what the section says, it seems > to suggest that the .mime.types file will be overridden by the content > of the attachment. Am I right here? No, I do not believe that was the intent. Moreover, I just took a zip file, renamed it to have a .html extension and attached it. It was marked as text/html. Suggest running pine -d 9, doing a compose and attach, and then examining the resulting .pine-debug1 file for evidence that the mime.types file was processed or not. -teg 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, 2 Jul 1999 11:39:24 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA02230 for ; Fri, 2 Jul 1999 11:39:23 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA12584; Fri, 2 Jul 1999 11:39:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA01857; Fri, 2 Jul 1999 11:30:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA53470 for ; Fri, 2 Jul 1999 11:18:45 -0700 Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id LAA27498 for ; Fri, 2 Jul 1999 11:18:45 -0700 Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Fri, 02 Jul 99 12:18:43 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id MAA17243 for ; Fri, 2 Jul 1999 12:18:43 -0600 (MDT) Message-Id: Date: Fri, 2 Jul 1999 12:18:43 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B63DD0932848-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > No, I do not believe that was the intent. Moreover, I just took a zip > file, renamed it to have a .html extension and attached it. It was marked > as text/html. I believe what he is talking about is if you rename a short ASCII text document to .html and then attach it. According to the description he cited, this will be attached as "text/plain" without even referencing the mime-types 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; Fri, 2 Jul 1999 11:40:22 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA02543 for ; Fri, 2 Jul 1999 11:40:21 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA12618; Fri, 2 Jul 1999 11:40:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA24734; Fri, 2 Jul 1999 11:38:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA53058 for ; Fri, 2 Jul 1999 11:31:48 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA29401 for ; Fri, 2 Jul 1999 11:31:42 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id XAA16014; Fri, 2 Jul 1999 23:58:56 +0530 (IST) Message-Id: Date: Fri, 2 Jul 1999 23:58:56 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 2 Jul 1999 at 10:13am -0700, Terry Gray said: > No, I do not believe that was the intent. Moreover, I just took a zip > file, renamed it to have a .html extension and attached it. It was marked > as text/html. > > Suggest running pine -d 9, doing a compose and attach, and then examining > the resulting .pine-debug1 file for evidence that the mime.types file was > processed or not. Running pine -d9 revealed the culprit. Turns out that pine was looking at the wrong mime.types file. I was finally able to change the content-type to text/html. Thanks much, Terry. -Srikanth > > -teg > > 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, 3 Jul 1999 02:11:32 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id CAA04010 for ; Sat, 3 Jul 1999 02:11:29 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA27681; Sat, 3 Jul 1999 02:11:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA13853; Sat, 3 Jul 1999 02:10:59 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA53970 for ; Sat, 3 Jul 1999 02:06:16 -0700 Received: from Deimos.MNF.NU (root@Deimos.MNF.NU [194.52.18.199]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA17167 for ; Sat, 3 Jul 1999 02:06:15 -0700 Received: from NS.MNF.NU ([194.52.18.192]:50695 "EHLO NS.MNF.NU" ident: "wuming") by Deimos.MNF.NU with ESMTP id <36314-393>; Sat, 3 Jul 1999 11:03:40 +0200 Message-Id: Date: Sat, 3 Jul 1999 11:03:40 +0200 (CEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: W U M I N G Z H A N G To: Pine Discussion Forum Subject: signature runing a cmd.. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I dont know if has been dissussed... but I can hardly make it work right.. I set signature-file = |./sig and sig file is a file like #!/bin/sh echo "my signature" date etc... but pine doesnt read my signature. any idea? (Wuming) -- ///Wuming Zhang :: Lhasa Produktion ;; 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; Sat, 3 Jul 1999 02:22:06 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id CAA15066 for ; Sat, 3 Jul 1999 02:22:05 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA27719; Sat, 3 Jul 1999 02:22:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA13969; Sat, 3 Jul 1999 02:21:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA30486 for ; Sat, 3 Jul 1999 02:17:43 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA02182 for ; Sat, 3 Jul 1999 02:17:42 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Sat, 3 Jul 1999 04:17:38 -0500 Received: from localhost by calvin.twntpe.cdc.com with ESMTP; Sat, 3 Jul 1999 17:17:21 +0800 Message-Id: Date: Sat, 3 Jul 1999 17:17:20 +0800 (GMT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Edward M Greshko To: Pine Discussion Forum Subject: Re: signature runing a cmd.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: W U M I N G Z H A N G X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 3 Jul 1999, W U M I N G Z H A N G wrote: > I dont know if has been dissussed... but I can hardly make it work right.. > > I set signature-file = |./sig The help on signature read: If the filename is followed by a vertical bar (|) then instead of reading the contents of the file the file is assumed to be a program which will produce the text to be used on its standard output. The program can't have any arguments and doesn't receive any input from Pine, but the rest of the processing works as if the contents came from a file. So, don't you want: signature-file = $HOME/sig| ? I don't think you want "./file-name" since you may start pine in more than one directory. Also, the | is after the file name as indicated above. Regards, 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 Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Tue, 6 Jul 1999 02:17:55 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id CAA32366 for ; Tue, 6 Jul 1999 02:17:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA16311; Tue, 6 Jul 1999 02:17:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA11676; Tue, 6 Jul 1999 02:16:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA53812 for ; Tue, 6 Jul 1999 02:11:19 -0700 Received: from skyhawk.nexor.co.uk (skyhawk.nexor.co.uk [193.63.53.10]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA25994 for ; Tue, 6 Jul 1999 02:11:18 -0700 Received: from skyhawk.nexor.co.uk by skyhawk.nexor.co.uk with SMTP (Messageware Mailer 3.0) with ESMTP; Tue, 6 Jul 1999 10:11:14 +0100 Message-Id: "Pine.GSO.4.10.9907060931540.20394-100000" Date: Tue, 6 Jul 1999 10:11:13 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Berthels To: Pine Discussion Forum Subject: Avoid re-typing filename when saving attachments MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Folks, I seem to recall a post to this list some time ago relating to pine's behaviour when saving an attachment. The issue is when navigating to a directory (using ^t for example) the filename from the MIME attachment is lost and must be re-typed. The ideal behaviour for me would be to have a 'save file here with original name' keystroke in the directory navigator. Is this: a) a FAQ b) a planned feature c) something someone has implemented in a patch d) something people would like implemented in a patch e) a bad idea in the first place (please enlighten) regards, jb -- John Berthels Email: j.berthels@nexor.co.uk X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ -- ----------------------------------------------------------------- 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, 6 Jul 1999 11:34:58 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA10798 for ; Tue, 6 Jul 1999 11:34:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA27593; Tue, 6 Jul 1999 11:34:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA01400; Tue, 6 Jul 1999 11:34:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22124 for ; Tue, 6 Jul 1999 11:29:06 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA25159 for ; Tue, 6 Jul 1999 11:29:06 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA31866; Tue, 6 Jul 1999 11:29:07 -0700 (PDT) Message-Id: Date: Tue, 6 Jul 1999 11:28:53 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I did the experiment of attaching a html file, with the mime file pointing to a valid .mime file, which was read by pine and pine displayed a message saying the attachment was a text/HTML file. Good it works!, however I sent the message to myself and the attachment says it is a "text/PLAIN" file. I think this result is not what was intended. Where is the problem? Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 6 Jul 1999 11:42:18 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA31328 for ; Tue, 6 Jul 1999 11:42:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA27252; Tue, 6 Jul 1999 11:42:15 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA01824; Tue, 6 Jul 1999 11:41:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA53006 for ; Tue, 6 Jul 1999 11:37:31 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA26427 for ; Tue, 6 Jul 1999 11:37:30 -0700 Received: from D-140-142-110-67.dhcp2.washington.edu (D-140-142-110-67.dhcp2.washington.edu [140.142.110.67]) by shiva1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA29596; Tue, 6 Jul 1999 11:37:28 -0700 Message-Id: Date: Tue, 6 Jul 1999 11:40:12 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: Sending HTML attachments In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999, Eduardo Chappa L. wrote: > I did the experiment of attaching a html file, with the mime file > pointing to a valid .mime file, which was read by pine and pine displayed a > message saying the attachment was a text/HTML file. Good it works!, however > I sent the message to myself and the attachment says it is a "text/PLAIN" > file. I think this result is not what was intended. Where is the problem? Eduardo, Do you mean that the message you sent to yourself ended up in your inbox with the attachment labelled text/plain, even though Pine said it was attaching it as text/html when you were sending it? If so, pls check the copy in your sentmail folder and see what it looks like. Also you might re-test with maximum debugging -d 9 and see if the .pine-debug1 shows any anomolies. Feel free to send an example of the problem and any supporting data to pine-bugs@cac.washington.edu -teg 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, 6 Jul 1999 11:46:54 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA11001 for ; Tue, 6 Jul 1999 11:46:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA27379; Tue, 6 Jul 1999 11:46:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA23366; Tue, 6 Jul 1999 11:46:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA22030 for ; Tue, 6 Jul 1999 11:39:38 -0700 Received: from skyhawk.nexor.co.uk (skyhawk.nexor.co.uk [193.63.53.10]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA04770 for ; Tue, 6 Jul 1999 11:39:35 -0700 Received: from skyhawk.nexor.co.uk by skyhawk.nexor.co.uk with SMTP (Messageware Mailer 3.0) with ESMTP; Tue, 6 Jul 1999 19:39:31 +0100 Message-Id: "Pine.GSO.4.10.9907061931060.21256-100000" Date: Tue, 6 Jul 1999 19:39:30 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: John Berthels To: Pine Discussion Forum Subject: Re: Avoid re-typing filename when saving attachments In-Reply-To: "Pine.GSO.4.10.9907060931540.20394-100000" MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Sorry to followup my own post, but here is a tiny patch which does the necessary. Its not ideal, but if you use the existing 'Add' button to create a file whilst in the browser it now defaults to inserting the MIME attachment name, so you can just hit multiple returns and end up with what you want. Does anyone have any interest in my cleaning this up for them? Any chance of similar feature going in a future release? [Perhaps as its own shortcut, rather than overloading 'Add'.] regards, jb On Tue, 6 Jul 1999, John Berthels wrote: > I seem to recall a post to this list some time ago relating to pine's > behaviour when saving an attachment. > > The issue is when navigating to a directory (using ^t for example) the > filename from the MIME attachment is lost and must be re-typed. > > The ideal behaviour for me would be to have a 'save file here with > original name' keystroke in the directory navigator. --- pine4.10/pico/browse.c Wed Sep 16 01:19:17 1998 +++ pine4.10-jb/pico/browse.c Tue Jul 6 19:28:38 1999 @@ -972,7 +972,12 @@ } i = 0; - child[0] = '\0'; + /* + * JB1 - Support default filename + * + * Set the default filename as that which we have already + */ + strcpy( child, fn ); while(!i){ @@ -991,9 +996,16 @@ i++; break; case FALSE: - i++; - mlerase(); - break; + /* + * JB1 - Support default filename + * + * False here means 'no change' which is OK since we + * now supply a default. Treat this the same as true. + * + * i++; + * mlerase(); + * break; + */ case TRUE: i++; -- John Berthels Email: j.berthels@nexor.co.uk X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ 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, 6 Jul 1999 15:12:43 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA15574 for ; Tue, 6 Jul 1999 15:12:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA00238; Tue, 6 Jul 1999 15:12:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA01407; Tue, 6 Jul 1999 15:12:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA46502 for ; Tue, 6 Jul 1999 15:07:29 -0700 Received: from hawk.csrv.uidaho.edu (root@hawk.csrv.uidaho.edu [129.101.119.220]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA24926 for ; Tue, 6 Jul 1999 15:07:28 -0700 Received: from raptor.csrv.uidaho.edu (dianeg@raptor.csrv.uidaho.edu [129.101.119.252]) by hawk.csrv.uidaho.edu (8.8.6 (PHNE_17135)/) with ESMTP id PAA10999 for ; Tue, 6 Jul 1999 15:07:25 -0700 (PDT) Received: from localhost (dianeg@localhost) by raptor.csrv.uidaho.edu (8.8.6 (PHNE_14041)/UI.ITS.MAIL) with ESMTP id PAA06637 for ; Tue, 6 Jul 1999 15:07:24 -0700 (PDT) Message-Id: Date: Tue, 6 Jul 1999 15:07:24 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Diane Griffitts To: Pine Discussion Forum Subject: Folder Format Problem PC-Pine/UNIX Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: raptor.csrv.uidaho.edu: dianeg owned process doing -bs X-Sender: dianeg@raptor.csrv.uidaho.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I'm looking for more information on how PC-Pine 4.10 handles folder files. I've consulted the following pages on the Pine web site. http://www.washington.edu/pine/faq/sysadmins.html http://www.washington.edu/pine/tech-notes.4.10/low-level.html I'm a network administrator and die-hard UNIX Pine user (currently using 4.05 on an HP-UX 10.2X server cluster). I keep ALL my email for future reference by archiving folder files on a monthly basis via FTP to my local hard drive. In the past, when I needed to browse an archived folder, I would temporarilty FTP it back to my mail directory on the UNIX host. Recently I installed PC-Pine 4.10 hoping for easier access to the archived materials and was pleased with the results. Note that I am not using PC-Pine to send and receive mail; I'm only using it to access folder files which I FTP'd from my UNIX space to my local hard drive. This has mostly eliminated the need to FTP a folder back to the UNIX side. Everything was fine until I wanted to forward an old message. I FTP'd the folder file back to UNIX, but when I tried to view it, UNIX Pine says it contains no messages. I can cat the file and see the messages, so I'm confident the file is all there. Also tried the same process on a second folder with the same results, so I don't think the file became corrupt. Looking further, I noticed the date and time stamps on these folder files were updated according to when I had accessed them earlier using PC-Pine. Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to the mbx format and my UNIX Pine implementation can't read them that way. So does anybody know: 1) is there any way to keep PC-Pine from doing such a conversion and 2) if my theory is true, is there any way to convert these folders back to the UNIX Berkeley mail format so UNIX Pine can read them? Any light anyone can shed on this would be much appreciated. _ ^ ______________________________________________ / \ Diane Griffitts - - dianeg@uidaho.edu / \ System Network Analyst | University of Idaho Boise Center __________________________________________________ -- ----------------------------------------------------------------- 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, 6 Jul 1999 15:31:24 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA16293 for ; Tue, 6 Jul 1999 15:31:23 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA01533; Tue, 6 Jul 1999 15:31:22 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA04225; Tue, 6 Jul 1999 15:30:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA18662 for ; Tue, 6 Jul 1999 15:26:31 -0700 Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id PAA04758 for ; Tue, 6 Jul 1999 15:26:30 -0700 Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Tue, 06 Jul 99 16:26:25 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id QAA09508 for ; Tue, 6 Jul 1999 16:26:23 -0600 (MDT) Message-Id: Date: Tue, 6 Jul 1999 16:26:22 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B9C5D1B41761-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Another possibility: Are there ^M's at the end of each line? If so, PC-PINE converted your mail folder to DOS text. > I'm looking for more information on how PC-Pine 4.10 handles folder files. > I've consulted the following pages on the Pine web site. > > http://www.washington.edu/pine/faq/sysadmins.html > http://www.washington.edu/pine/tech-notes.4.10/low-level.html Why did you FTP back? Why not just use the original? > Everything was fine until I wanted to forward an old message. I FTP'd the > folder file back to UNIX, but when I tried to view it, UNIX Pine says it > contains no messages. I can cat the file and see the messages, so I'm 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, 6 Jul 1999 15:59:49 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA04275 for ; Tue, 6 Jul 1999 15:59:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA01726; Tue, 6 Jul 1999 15:59:46 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA05269; Tue, 6 Jul 1999 15:59:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA17334 for ; Tue, 6 Jul 1999 15:54:08 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA14867 for ; Tue, 6 Jul 1999 15:54:05 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id WAA08862; Tue, 6 Jul 1999 22:59:19 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 6 Jul 99 15:59 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA30429; Tue, 6 Jul 1999 15:29:43 -0700 Message-Id: Date: Tue, 6 Jul 1999 15:29:40 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Diane Griffitts X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999, Diane Griffitts wrote: > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > the mbx format and my UNIX Pine implementation can't read them that way. > So does anybody know: 1) is there any way to keep PC-Pine from doing such > a conversion and 2) if my theory is true, is there any way to convert > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > them? Any light anyone can shed on this would be much appreciated. Based on a little experiment, and my personal experience with what seem like simmilar UNIX<>DOS incompatabilities, my feeling is that chances are it is as simple as the ``end of line'' marker being diffrent. DOS uses a ^M^J end of line marker, while UNIX uses ^J. If I convert a file to DOS format (insert the ^Ms in the file), the folder then contains ``0'' messages. I suspect that you simply have to watch this conversion, possibly you are transfering them to the PC as ASCII and back to UNIX as binary? Or, maybe PC-Pine converts UNIX files to PC files when it reads them. The ``file date'' has no effect on Pine as far as I know... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 6 Jul 1999 16:24:41 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA17500 for ; Tue, 6 Jul 1999 16:24:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA02896; Tue, 6 Jul 1999 16:24:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA06294; Tue, 6 Jul 1999 16:23:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA17188 for ; Tue, 6 Jul 1999 16:19:22 -0700 Received: from harrier.csrv.uidaho.edu (root@harrier.csrv.uidaho.edu [129.101.119.224]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA11852 for ; Tue, 6 Jul 1999 16:19:20 -0700 Received: from raptor.csrv.uidaho.edu (dianeg@raptor.csrv.uidaho.edu [129.101.119.252]) by harrier.csrv.uidaho.edu (8.8.6 (PHNE_17135)/) with ESMTP id QAA01568 for ; Tue, 6 Jul 1999 16:19:18 -0700 (PDT) Received: from localhost (dianeg@localhost) by raptor.csrv.uidaho.edu (8.8.6 (PHNE_14041)/UI.ITS.MAIL) with ESMTP id QAA11003 for ; Tue, 6 Jul 1999 16:19:16 -0700 (PDT) Message-Id: Date: Tue, 6 Jul 1999 16:19:16 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Diane Griffitts To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: raptor.csrv.uidaho.edu: dianeg owned process doing -bs X-Sender: dianeg@raptor.csrv.uidaho.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I can't see any ^M's when I cat the file... I wanted to FTP the folder back to the UNIX side in order to open it and forward one of the messages. The original folder no longer existed on the UNIX host. In this case, I worked around the problem by using the Export command in PC-Pine to store a copy of the one message, then FTP'd that file to my UNIX home directory where I could attach it to the message. I suppose I can continue to do this as needed, but I still would like to know if there's a way to keep PC-Pine from adulterating the folder files. On Tue, 6 Jul 1999, Daniel Sands wrote: > Another possibility: Are there ^M's at the end of each line? If so, PC-PINE > converted your mail folder to DOS text. > > > I'm looking for more information on how PC-Pine 4.10 handles folder files. > > I've consulted the following pages on the Pine web site. > > > > http://www.washington.edu/pine/faq/sysadmins.html > > http://www.washington.edu/pine/tech-notes.4.10/low-level.html > > Why did you FTP back? Why not just use the original? > > > Everything was fine until I wanted to forward an old message. I FTP'd the > > folder file back to UNIX, but when I tried to view it, UNIX Pine says it > > contains no messages. I can cat the file and see the messages, so I'm > > _ ^ ______________________________________________ / \ Diane Griffitts - - dianeg@uidaho.edu / \ System Network Analyst | University of Idaho Boise Center __________________________________________________ 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, 6 Jul 1999 16:32:51 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA17710 for ; Tue, 6 Jul 1999 16:32:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA02477; Tue, 6 Jul 1999 16:32:49 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA13698; Tue, 6 Jul 1999 16:32:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA45026 for ; Tue, 6 Jul 1999 16:26:54 -0700 Received: from hawk.csrv.uidaho.edu (root@hawk.csrv.uidaho.edu [129.101.119.220]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA03371 for ; Tue, 6 Jul 1999 16:26:52 -0700 Received: from raptor.csrv.uidaho.edu (dianeg@raptor.csrv.uidaho.edu [129.101.119.252]) by hawk.csrv.uidaho.edu (8.8.6 (PHNE_17135)/) with ESMTP id QAA25547 for ; Tue, 6 Jul 1999 16:26:36 -0700 (PDT) Received: from localhost (dianeg@localhost) by raptor.csrv.uidaho.edu (8.8.6 (PHNE_14041)/UI.ITS.MAIL) with ESMTP id QAA11415 for ; Tue, 6 Jul 1999 16:26:36 -0700 (PDT) Message-Id: Date: Tue, 6 Jul 1999 16:26:35 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Diane Griffitts To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: raptor.csrv.uidaho.edu: dianeg owned process doing -bs X-Sender: dianeg@raptor.csrv.uidaho.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I can't see any extra ^M's but maybe I'm not viewing the file in such a way that they are visible. If this is the cause of the problem, I'm not sure how to keep it from happening. When I FTP, I normally use the binary setting for everything; in this case the FTP action was the same as all the other times I have done this. I did go back and try the FTP set to ASCII, but it didn't seem to change anything (and didn't solve the problem). P.S. I was only noting the file date as evidence that PC-Pine had updated the file in some manner. In the meantime I have also noted that the file size has increased somewhat, so that fits with the conversion to DOS theory. But is there a way to convert back to UNIX text? On Tue, 6 Jul 1999, Jessica Rasku wrote: > On Tue, 6 Jul 1999, Diane Griffitts wrote: > > > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > > the mbx format and my UNIX Pine implementation can't read them that way. > > So does anybody know: 1) is there any way to keep PC-Pine from doing such > > a conversion and 2) if my theory is true, is there any way to convert > > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > > them? Any light anyone can shed on this would be much appreciated. > > Based on a little experiment, and my personal experience with what > seem like simmilar UNIX<>DOS incompatabilities, my feeling is that chances > are it is as simple as the ``end of line'' marker being diffrent. DOS > uses a ^M^J end of line marker, while UNIX uses ^J. If I convert a file > to DOS format (insert the ^Ms in the file), the folder then contains ``0'' > messages. I suspect that you simply have to watch this conversion, > possibly you are transfering them to the PC as ASCII and back to UNIX as > binary? Or, maybe PC-Pine converts UNIX files to PC files when it reads > them. The ``file date'' has no effect on Pine as far as I know... > > Jessica > > -- > Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, > LinuxBox: (250) 362-9668. > > List manager: majordomo@ArmispianSystems.Rossland.bc.ca > send command help ---- To get help with majordomo > or lists ---- To get a list of all lists on server. > > WWW: > > _ ^ ______________________________________________ / \ Diane Griffitts - - dianeg@uidaho.edu / \ System Network Analyst | University of Idaho Boise Center __________________________________________________ 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, 6 Jul 1999 16:38:12 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA17808 for ; Tue, 6 Jul 1999 16:38:11 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA02629; Tue, 6 Jul 1999 16:38:08 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA05126; Tue, 6 Jul 1999 16:37:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA20116 for ; Tue, 6 Jul 1999 16:28:48 -0700 Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id QAA13097 for ; Tue, 6 Jul 1999 16:28:47 -0700 Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Tue, 06 Jul 99 17:28:45 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id RAA17476 for ; Tue, 6 Jul 1999 17:28:44 -0600 (MDT) Message-Id: Date: Tue, 6 Jul 1999 17:28:44 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B9C4EA726536-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN CAT won't show those pesky ^M's. Try using VI on it. In any case, make sure you use ASCII to FTP the file to your UNIX station. > I can't see any ^M's when I cat the file... > > I wanted to FTP the folder back to the UNIX side in order to open it and > forward one of the messages. The original folder no longer existed on the > UNIX host. In this case, I worked around the problem by using the Export > command in PC-Pine to store a copy of the one message, then FTP'd that > file to my UNIX home directory where I could attach it to the message. I > suppose I can continue to do this as needed, but I still would like to > know if there's a way to keep PC-Pine from adulterating the folder files. 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, 6 Jul 1999 16:43:32 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA17866 for ; Tue, 6 Jul 1999 16:43:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA02766; Tue, 6 Jul 1999 16:43:29 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA07801; Tue, 6 Jul 1999 16:42:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA31318 for ; Tue, 6 Jul 1999 16:29:33 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA03747 for ; Tue, 6 Jul 1999 16:29:32 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Tue, 6 Jul 1999 18:29:28 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Wed, 7 Jul 1999 07:28:55 +0800 Message-Id: <000301bec807$4d3b49d0$1511b381@twntpe.cdc.com> Date: Wed, 7 Jul 1999 07:28:49 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Diane Griffitts" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Diane, > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > the mbx format and my UNIX Pine implementation can't read them that way. > So does anybody know: 1) is there any way to keep PC-Pine from doing such > a conversion and 2) if my theory is true, is there any way to convert > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > them? Any light anyone can shed on this would be much appreciated. You are 100% correct. PC-Pine does use mbx format. It is not a simple DOS/Unix file format difference. There is no way to keep PC-Pine from using mbx format. It is hardwired and was done so for good reason. The reason being "performance". The easiest way to convert back to Berkeley format is to use PC-Pine, point it to a folder collection on a Unix server running imapd, create a folder on the Unix side and then copy (via imap) the messages from the PC-Pine side to the Unix side. Regards, Ed 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, 6 Jul 1999 18:48:25 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id SAA18992 for ; Tue, 6 Jul 1999 18:48:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA04934; Tue, 6 Jul 1999 18:48:23 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA11151; Tue, 6 Jul 1999 18:47:59 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA53942 for ; Tue, 6 Jul 1999 18:43:41 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA00833 for ; Tue, 6 Jul 1999 18:43:36 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id BAA10159; Wed, 7 Jul 1999 01:49:05 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 6 Jul 99 18:49 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id SAA31854; Tue, 6 Jul 1999 18:36:28 -0700 Message-Id: Date: Tue, 6 Jul 1999 18:36:27 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Diane Griffitts X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999, Diane Griffitts wrote: > P.S. I was only noting the file date as evidence that PC-Pine had updated > the file in some manner. In the meantime I have also noted that the file > size has increased somewhat, so that fits with the conversion to DOS > theory. But is there a way to convert back to UNIX text? On the UNIX side something like: cat dosfile | tr -d "\r" > unixfile should strip the ^Ms from the file... That is probably the quickest, lowest resource method to use. You could probably also do something similar in your favorite editor. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 6 Jul 1999 18:58:16 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id SAA19041 for ; Tue, 6 Jul 1999 18:58:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA05708; Tue, 6 Jul 1999 18:58:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA18520; Tue, 6 Jul 1999 18:57:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA09342 for ; Tue, 6 Jul 1999 18:53:48 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id SAA01579 for ; Tue, 6 Jul 1999 18:53:44 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id BAA10268; Wed, 7 Jul 1999 01:59:13 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 6 Jul 99 18:59 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id SAA31914; Tue, 6 Jul 1999 18:41:56 -0700 Message-Id: Date: Tue, 6 Jul 1999 18:41:55 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: <000301bec807$4d3b49d0$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jul 1999, Ed Greshko wrote: > Diane, > > > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > > the mbx format and my UNIX Pine implementation can't read them that way. > > So does anybody know: 1) is there any way to keep PC-Pine from doing such > > a conversion and 2) if my theory is true, is there any way to convert > > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > > them? Any light anyone can shed on this would be much appreciated. > > You are 100% correct. PC-Pine does use mbx format. It is not a > simple DOS/Unix file format difference. This seems unlikely as the folder is still vissably the same. > There is no way to keep PC-Pine from using mbx format. It is > hardwired and was done so for good reason. The reason being > "performance". I find this hard to believe. Just as I found the ``binary only'' problem with PC-Pine (it has been confirmed that there is no reason that there is no source avalable). Performance is not a good enough reason to use a format that could cause problems (also, I find it hard to believe that the UNIX version does not understand mbx format). > The easiest way to convert back to Berkeley format is to use PC-Pine, > point it to a folder collection on a Unix server running imapd, create > a folder on the Unix side and then copy (via imap) the messages from > the PC-Pine side to the Unix side. Hm, this may not be possible. I don't know though. I don't know enough about the setup on this person's system to be sure, but some of what she is doing SOUNDS like maybe she doesn't have full ``internet'' access. And, it is indeed MORE likely there is no IMAP server, than the mbx format isn't supported I'd think... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 6 Jul 1999 19:32:53 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA19207 for ; Tue, 6 Jul 1999 19:32:52 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA05527; Tue, 6 Jul 1999 19:32:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA19323; Tue, 6 Jul 1999 19:32:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA23288 for ; Tue, 6 Jul 1999 19:28:24 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA04216 for ; Tue, 6 Jul 1999 19:28:23 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Tue, 6 Jul 1999 21:28:11 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Wed, 7 Jul 1999 10:28:04 +0800 Message-Id: <001301bec820$545aad50$1511b381@twntpe.cdc.com> Date: Wed, 7 Jul 1999 10:27:59 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-To: "Jessica Rasku" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Jessica, > > You are 100% correct. PC-Pine does use mbx format. It is not a > > simple DOS/Unix file format difference. > > This seems unlikely as the folder is still vissably the same. Sorry to burst your bubble but.... Looking at the top of the PC-Pine's mbx format folder we see (using vi in Unix after doing a binary xfer of the file): *mbx*^M 37828c4c00000000^M ^M ^M ^M Then, down much further we see.... 3-Jun-1999 14:37:43 +0000,1437;000000000000-00000000^M Return-Path: ^M The line with Jun-1999 is part of the mbx format. Actually, if you do a "more" on the folder you'd see something like: @@^PĂŕ^EŃxŕ^E)đ @@^G 3-Jun-1999 14:37:43 +0000,1437;000000000000-0000000 Furthermore, if you were to use "od" (octal dump) on the file you'd see null bytes and quite a few other "characters" which are *not* presented in an editor such as vi but *DO* have significance. > > There is no way to keep PC-Pine from using mbx format. It is > > hardwired and was done so for good reason. The reason being > > "performance". > > I find this hard to believe. Just as I found the ``binary only'' > problem with PC-Pine (it has been confirmed that there is no reason that > there is no source avalable). Performance is not a good enough reason to > use a format that could cause problems (also, I find it hard to believe > that the UNIX version does not understand mbx format). Believe it, or not, it is your choice. Also sorry to burst your bubble, but it matters not what mailbox format is in use. The translator is inherent in the imap protocol. We, Control Data Systems, have an imap product which uses an internal mailbox format unlike any supported by pine. Yet, I can freely move messages between PC and Unix versions of Pine as well as the beast known as MS-Outlook! Would you care to FTP the .pst files used by Outlook and see what can be done with those. :-) :-) Yet, with the procedure I've told you about...it is no problem for me to take a message from an Outlook folder to PC-Pine or Unix Pine and have it translated into the mailbox format needed. > > The easiest way to convert back to Berkeley format is to use PC-Pine, > > point it to a folder collection on a Unix server running imapd, create > > a folder on the Unix side and then copy (via imap) the messages from > > the PC-Pine side to the Unix side. > > Hm, this may not be possible. I don't know though. I don't know > enough about the setup on this person's system to be sure, but some of > what she is doing SOUNDS like maybe she doesn't have full ``internet'' > access. And, it is indeed MORE likely there is no IMAP server, than the > mbx format isn't supported I'd think... If you don't have the setup you need to perform the function, it would not be possible. That is obvious. However, the procedure that I've described worked quite well since I do always test my solutions before presenting them. It makes more sense then saying "try this, maybe it will work". The mbx format probably has a definition in a document. I've not searched for it. However, it should not be difficult to write a perl script to convert between mbx and Berkeley. Or, you may even be able to hack the source of the c-client library. Regards, Ed 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, 6 Jul 1999 19:37:08 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA14052 for ; Tue, 6 Jul 1999 19:37:07 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA06241; Tue, 6 Jul 1999 19:37:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA19521; Tue, 6 Jul 1999 19:36:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA09224 for ; Tue, 6 Jul 1999 19:28:24 -0700 Received: from olive.cac.washington.edu (olive.cac.washington.edu [128.95.135.99]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id TAA31840 for ; Tue, 6 Jul 1999 19:28:24 -0700 Received: from ldsl233.sttl.uswest.net by olive.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.21 ) id AA15042; Tue, 6 Jul 99 19:28:20 PDT Message-Id: Date: Tue, 6 Jul 1999 19:28:11 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999, Jessica Rasku wrote: > > There is no way to keep PC-Pine from using mbx format. It is > > hardwired and was done so for good reason. The reason being > > "performance". > > I find this hard to believe. Just as I found the ``binary only'' > problem with PC-Pine (it has been confirmed that there is no reason that > there is no source avalable). Really? I'd love to learn more about this so-called "confirmation". (Especially since some of the *actual* reasons have been posted more than once...) Reminds me of a button seen in Haight-Ashbury in the 60's: "Acid Indigestion? Check your source." > Performance is not a good enough reason to use a format that could > cause problems (also, I find it hard to believe that the UNIX version > does not understand mbx format). PC-Pine can read Unix mailbox format on a read-only basis, but if it *creates* the folder/messages, it *will* use an mbx-like format... yes, for efficiency. Unix Pine should be able to understand all formats, but at least some of the mailbox drivers have proven to be picky about newline conventions. Please note: PC-Pine was designed to operate in an IMAP environment. That it works in any other context is perhaps fortuitous, but definitely outside of its intended design center. -teg 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, 6 Jul 1999 19:42:01 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA18631 for ; Tue, 6 Jul 1999 19:42:00 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA06316; Tue, 6 Jul 1999 19:41:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA19692; Tue, 6 Jul 1999 19:41:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA45020 for ; Tue, 6 Jul 1999 19:37:33 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA04853 for ; Tue, 6 Jul 1999 19:37:32 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Tue, 6 Jul 1999 21:37:27 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Wed, 7 Jul 1999 10:37:24 +0800 Message-Id: <001601bec821$a1f6e1e0$1511b381@twntpe.cdc.com> Date: Wed, 7 Jul 1999 10:37:18 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jessica Rasku" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > > P.S. I was only noting the file date as evidence that PC-Pine had updated > > the file in some manner. In the meantime I have also noted that the file > > size has increased somewhat, so that fits with the conversion to DOS > > theory. But is there a way to convert back to UNIX text? > > On the UNIX side something like: > > cat dosfile | tr -d "\r" > unixfile > > should strip the ^Ms from the file... That is probably the > quickest, lowest resource method to use. You could probably also do > something similar in your favorite editor. This strips out ^M from the file. It doesn't convert between *mailbox* formats! If you really look at the file with a HEX editor you will see "null bytes" and other non-printable bytes which have significance in the mbx format. Using "visual" editors like vi will not show you bits and bytes which hold information needed by applications. BTW, some systems come with the command "dos2unix" and "unix2dos" which perform the "tr" functions plus other useful functions. Ed 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, 7 Jul 1999 07:28:24 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id HAA32371 for ; Wed, 7 Jul 1999 07:28:23 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA17266; Wed, 7 Jul 1999 07:28:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA21909; Wed, 7 Jul 1999 07:27:53 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA18538 for ; Wed, 7 Jul 1999 07:20:07 -0700 Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id HAA10040 for ; Wed, 7 Jul 1999 07:20:07 -0700 Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Wed, 07 Jul 99 08:20:04 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id IAA27854 for ; Wed, 7 Jul 1999 08:20:03 -0600 (MDT) Message-Id: Date: Wed, 7 Jul 1999 08:20:04 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B9DBD9E31289-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > PC-Pine can read Unix mailbox format on a read-only basis, but if it > *creates* the folder/messages, it *will* use an mbx-like format... yes, > for efficiency. Unix Pine should be able to understand all formats, but > at least some of the mailbox drivers have proven to be picky about newline > conventions. According to FAQ 7.2, PC-PINE 4.x "supports mbx, mtx, tenex, and unix formats, all read-write." So what do you mean, "read-only"? 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, 7 Jul 1999 09:07:30 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA29033 for ; Wed, 7 Jul 1999 09:07:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA18840; Wed, 7 Jul 1999 09:07:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA22143; Wed, 7 Jul 1999 09:06:57 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA31538 for ; Wed, 7 Jul 1999 09:02:06 -0700 Received: from shiva1.cac.washington.edu (shiva1.cac.washington.edu [140.142.100.201]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA22964 for ; Wed, 7 Jul 1999 09:02:06 -0700 Received: from D-140-142-110-67.dhcp2.washington.edu (D-140-142-110-67.dhcp2.washington.edu [140.142.110.67]) by shiva1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA19473; Wed, 7 Jul 1999 09:02:01 -0700 Message-Id: Date: Wed, 7 Jul 1999 09:04:34 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine 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: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jul 1999, Daniel Sands wrote: > > PC-Pine can read Unix mailbox format on a read-only basis, but if it > > *creates* the folder/messages, it *will* use an mbx-like format... yes, > > for efficiency. Unix Pine should be able to understand all formats, but > > at least some of the mailbox drivers have proven to be picky about newline > > conventions. > > According to FAQ 7.2, PC-PINE 4.x "supports mbx, mtx, tenex, and unix formats, > all read-write." So what do you mean, "read-only"? My mistake. What I said was true prior to PC-Pine 4.xx, but I had forgotten that one the (several) motivations we had for abandoning DOS compatibility last year was to allow read-write unix mailbox access. -teg 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, 7 Jul 1999 10:37:29 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA04213 for ; Wed, 7 Jul 1999 10:37:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA22272; Wed, 7 Jul 1999 10:37:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA28098; Wed, 7 Jul 1999 10:36:58 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA14738 for ; Wed, 7 Jul 1999 10:32:47 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA04727 for ; Wed, 7 Jul 1999 10:32:46 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id RAA16973; Wed, 7 Jul 1999 17:38:10 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 7 Jul 99 10:38 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id KAA05221; Wed, 7 Jul 1999 10:28:59 -0700 Message-Id: Date: Wed, 7 Jul 1999 10:28:58 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 6 Jul 1999, Terry Gray wrote: > > On Tue, 6 Jul 1999, Jessica Rasku wrote: > > > > There is no way to keep PC-Pine from using mbx format. It is > > > hardwired and was done so for good reason. The reason being > > > "performance". > > > > I find this hard to believe. Just as I found the ``binary only'' > > problem with PC-Pine (it has been confirmed that there is no reason that > > there is no source avalable). > > Really? I'd love to learn more about this so-called "confirmation". > (Especially since some of the *actual* reasons have been posted more > than once...) The reasons that I have heard are that there is NO code that can not be released. Now, there MAY be code that you WISH not to release, but there is no code that can NOT be released. Maybe since this HAS come up since I was on, and I DID ask about it in the past, explanation of why there is no source avalable. > Reminds me of a button seen in Haight-Ashbury in the 60's: > "Acid Indigestion? Check your source." My source, was from someone on the development team. Someone who has WORKED with that very source code. Maybe my ``interpretation'' is faulty, but my sounce itself isn't. Maybe before the development team starts saying things like ``check your source'' they should be very clear as to who knows what, and why. > > Performance is not a good enough reason to use a format that could > > cause problems (also, I find it hard to believe that the UNIX version > > does not understand mbx format). > > PC-Pine can read Unix mailbox format on a read-only basis, but if it > *creates* the folder/messages, it *will* use an mbx-like format... yes, > for efficiency. Unix Pine should be able to understand all formats, but > at least some of the mailbox drivers have proven to be picky about newline > conventions. On my version of Pine compiled on my Linux box, it DOES complain about new line conventions. In reality it shouldn't, but you would have to handle the file in a low level format in order to ensure that. You can't rely on the libraries installed on the system to be able to handle the three (or more) formats of end of line properly, and invisably. > Please note: PC-Pine was designed to operate in an IMAP environment. > That it works in any other context is perhaps fortuitous, but definitely > outside of its intended design center. What I don't understand, is why PC-Pine is SO diffrent from ``normal'' Pine. Yes, I realise that PC-Pine is designed to run in a diffrent envioronment, but why are there things like ``window possition'' stored in the PC-Pine pinerc, (yes it has been explained what FUNCTION it provides, but it seems an odd requirement. Maybe it's a problem with the windowing envioronment?), why does PC-Pine ``assume'' that there will only be one occurance running at a time? Why does PC-Pine have mouse control (maybe in X it works, I haven't tried it) while ``normal'' Pine does not? Maybe I'm ``picky'' but I think that products which seem to be merely diffrent ports of the same product should for the most part behave in the same way. The diffrences should be in how the operating system, or opperating envioronment behaves diffrently, not in functionality. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 7 Jul 1999 10:48:56 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA04588 for ; Wed, 7 Jul 1999 10:48:55 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA22569; Wed, 7 Jul 1999 10:48:53 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA06064; Wed, 7 Jul 1999 10:48:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA31594 for ; Wed, 7 Jul 1999 10:44:29 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA06873 for ; Wed, 7 Jul 1999 10:44:27 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id RAA17121; Wed, 7 Jul 1999 17:49:57 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 7 Jul 99 10:49 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id KAA05305; Wed, 7 Jul 1999 10:31:49 -0700 Message-Id: Date: Wed, 7 Jul 1999 10:31:47 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine 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 -- ListProcessor(tm) by CREN On Wed, 7 Jul 1999, Daniel Sands wrote: > > PC-Pine can read Unix mailbox format on a read-only basis, but if it > > *creates* the folder/messages, it *will* use an mbx-like format... yes, > > for efficiency. Unix Pine should be able to understand all formats, but > > at least some of the mailbox drivers have proven to be picky about newline > > conventions. > > According to FAQ 7.2, PC-PINE 4.x "supports mbx, mtx, tenex, and unix formats, > all read-write." So what do you mean, "read-only"? Oh, you really should check your source on that. :) I do love it when someone who rags on someone about checking sources is shown that if they had been more careful themself they would not have made the false claim... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 7 Jul 1999 11:02:17 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA04253 for ; Wed, 7 Jul 1999 11:02:15 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA22237; Wed, 7 Jul 1999 11:02:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA06505; Wed, 7 Jul 1999 11:01:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA24736 for ; Wed, 7 Jul 1999 10:57:48 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA11297 for ; Wed, 7 Jul 1999 10:57:46 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id SAA17197; Wed, 7 Jul 1999 18:03:04 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 7 Jul 99 11:03 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id KAA05469; Wed, 7 Jul 1999 10:54:24 -0700 Message-Id: Date: Wed, 7 Jul 1999 10:54:23 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: <001301bec820$545aad50$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jul 1999, Ed Greshko wrote: > Dear Jessica, > > > > You are 100% correct. PC-Pine does use mbx format. It is not a > > > simple DOS/Unix file format difference. > > > > This seems unlikely as the folder is still vissably the same. > > Sorry to burst your bubble but.... > > Looking at the top of the PC-Pine's mbx format folder we see (using vi in Unix > after doing a binary xfer of the file): > > *mbx*^M > 37828c4c00000000^M > ^M > ^M > ^M Hm, this is odd, my UNIX Berkly Style folders don't look like that. This was PRECICELY my point, and you have made it beutifully. mbx format folders DO look diffrent than non mbx format folders. SURE I may not be able to see WHAT everything is if I chose an editor poorly (as far as I know, vi displays all characters, but some characters are indistinguisable visualy if you don't have a character set that distinguises them. But, they are all ``displayed''. In fact, you probably can switch the mode of vi to display undisplayable charcters in a way that they are distinct. > Then, down much further we see.... > > 3-Jun-1999 14:37:43 +0000,1437;000000000000-00000000^M > Return-Path: ^M > > The line with Jun-1999 is part of the mbx format. > > Actually, if you do a "more" on the folder you'd see something like: > > @@^PĂŕ^EŃxŕ^E)đ @@^G 3-Jun-1999 14:37:43 +0000,1437;000000000000-0000000 > > Furthermore, if you were to use "od" (octal dump) on the file you'd see null > bytes and quite a few other "characters" which are *not* presented in an editor > such as vi but *DO* have significance. They may not be DISTINGUISHABLE on all machines, but I know that I used to be able (in DOS) to insert spaces by doing alt-2-5-5 but because of the character set I now have, that displayes quite distincly now... > > > There is no way to keep PC-Pine from using mbx format. It is > > > hardwired and was done so for good reason. The reason being > > > "performance". > > > > I find this hard to believe. Just as I found the ``binary only'' > > problem with PC-Pine (it has been confirmed that there is no reason that > > there is no source avalable). Performance is not a good enough reason to > > use a format that could cause problems (also, I find it hard to believe > > that the UNIX version does not understand mbx format). > > Believe it, or not, it is your choice. > > Also sorry to burst your bubble, but it matters not what mailbox format is in > use. The translator is inherent in the imap protocol. We, Control Data > Systems, have an imap product which uses an internal mailbox format unlike any > supported by pine. Yet, I can freely move messages between PC and Unix versions > of Pine as well as the beast known as MS-Outlook! HUH? Burst my bubble? Excuse me? Where do you read that I don't think that the format can be changed through IMAP? I said later on that maybe the configuration is such to make it difficult, or possibly ``impossible'' for a particular person to do that. But I don't believe that you can point to a SINGLE place that you can rightly interpret that I said that the conversion wouldn't work through IMAP. > Would you care to FTP the .pst files used by Outlook and see what can be done > with those. :-) :-) Yet, with the procedure I've told you about...it is no > problem for me to take a message from an Outlook folder to PC-Pine or Unix Pine > and have it translated into the mailbox format needed. Yes, the procedure you told us about should work. I NEVER questioned that. I have this thing personaly, in not forcing a person to change how they do things simply because there is something that works. > > > The easiest way to convert back to Berkeley format is to use PC-Pine, > > > point it to a folder collection on a Unix server running imapd, create > > > a folder on the Unix side and then copy (via imap) the messages from > > > the PC-Pine side to the Unix side. > > > > Hm, this may not be possible. I don't know though. I don't know > > enough about the setup on this person's system to be sure, but some of > > what she is doing SOUNDS like maybe she doesn't have full ``internet'' > > access. And, it is indeed MORE likely there is no IMAP server, than the > > mbx format isn't supported I'd think... > > If you don't have the setup you need to perform the function, it would not be > possible. That is obvious. Apparently not enough to you that you would be willing to say ``this may not work for you, but it does for me'' or the equivelent. Only obvious to you when it is pointed out to you. > However, the procedure that I've described worked quite well since I do always > test my solutions before presenting them. It makes more sense then saying "try > this, maybe it will work". Which is all fine and dandy if you have all the tools handy to do the testing. But for some people who can't run systems as fancy as you do, or for whatever reason find it impossible to test the ``specific circumstances'' (personaly, I think you are misleading people to say you've tested it, as you can't say that it WILL work, you at best can say that it ``does work for me'') that a person has presented. > The mbx format probably has a definition in a document. I've not searched for > it. However, it should not be difficult to write a perl script to convert > between mbx and Berkeley. Or, you may even be able to hack the source of the > c-client library. I BELIEVE that on most systems there should be a conversion utility that already exists. I couldn't locate it on my system as I don't know what it is called, but it was sugested that someone convert to mbx format and that there was a simple command to do so. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 7 Jul 1999 11:17:10 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA04499 for ; Wed, 7 Jul 1999 11:17:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA22745; Wed, 7 Jul 1999 11:17:07 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA27540; Wed, 7 Jul 1999 11:16:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA40462 for ; Wed, 7 Jul 1999 11:12:55 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA11269 for ; Wed, 7 Jul 1999 11:12:52 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id SAA17321; Wed, 7 Jul 1999 18:18:16 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 7 Jul 99 11:18 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id KAA05523; Wed, 7 Jul 1999 10:57:57 -0700 Message-Id: Date: Wed, 7 Jul 1999 10:57:57 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: <001601bec821$a1f6e1e0$1511b381@twntpe.cdc.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 7 Jul 1999, Ed Greshko wrote: > > > > P.S. I was only noting the file date as evidence that PC-Pine had updated > > > the file in some manner. In the meantime I have also noted that the file > > > size has increased somewhat, so that fits with the conversion to DOS > > > theory. But is there a way to convert back to UNIX text? > > > > On the UNIX side something like: > > > > cat dosfile | tr -d "\r" > unixfile > > > > should strip the ^Ms from the file... That is probably the > > quickest, lowest resource method to use. You could probably also do > > something similar in your favorite editor. > > This strips out ^M from the file. It doesn't convert between *mailbox* formats! > If you really look at the file with a HEX editor you will see "null bytes" and > other non-printable bytes which have significance in the mbx format. Using > "visual" editors like vi will not show you bits and bytes which hold information > needed by applications. This is what was asked. Or this is what I interpreted as being asked. It has been confirmed that the mbx format should not be a problem with UNIX Pine. It may be on SPECIFIC installs, but I suspect that to disable that would take a reasonable amount of hacking, which probably isn't that worth while... > BTW, some systems come with the command "dos2unix" and "unix2dos" which perform > the "tr" functions plus other useful functions. Yes, but the solution I gave should be avalable for just about anyone who has a shell account. It may not do the whole job, but it also does not dammage the orriginal file (unless you try to redirect back to the orriginal file, but I have learned through experience that that is a sure way to corrupt your files). Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 7 Jul 1999 13:04:57 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA07965 for ; Wed, 7 Jul 1999 13:04:56 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA26273; Wed, 7 Jul 1999 13:04:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA02209; Wed, 7 Jul 1999 13:04:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA30616 for ; Wed, 7 Jul 1999 12:59:24 -0700 Received: from a.cni.org (a.cni.org [192.100.21.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id MAA26924 for ; Wed, 7 Jul 1999 12:59:24 -0700 Received: by a.cni.org id ; Wed, 7 Jul 1999 15:59:09 -0400 Message-Id: <9907071959.AA04725@a.cni.org> Date: Wed, 7 Jul 1999 15:59:08 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Craig A Summerhill To: Pine Discussion Forum Subject: shared .addressbooks Content-Type: text X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I briefly reviewed the Pine Information Center on www.washington.edu and did not see the answer to this problem I am having. Nevertheless, I suspect this is an FAQ. Apologies in advance if it is obvious, but I can't find an answer... Environment: (Ancient) DEC 5000 w/ Ultrix 4.5 Pine 4.10 (pre-compiled binary from ftp.cac.washington.edu) Can somebody give me a quick start explanation of how to enable a shared addressbook in Pine. I do not have an IMAP server setup and running, so I am interested in doing this with local files. I have a couple of users (we'll say userA and userB) who want to share a common set of saved addresses so that they can keep their addressbooks in sync. I tried changing the permissions to 664 on ~userA/.addressbook and naming that file in ~userB/.pinerc file as the local addressbook for userB, but try as I might userB is always limited to READ ONLY access for the addressbook (when accessing the file from within the Pine Main Menu Addressbook function). This is frustrating, and I don't understand why. All file and directory permissions for the file and the path in question are properly set to allow each user to write to the file with the operating system, but Pine insists on blocking the non-owner's write access to the file. Feature or bug? I have also tried using a 'neutral' third party location and filename for the shared file (/usr/local/lib/shared_addressbook), but only the user with primary ownership of the file in question ever has write access from within Pine. What am I missing here? The only thing I can think of is that there is some kind of flag/macro which needs to be set at compile time to enable this, and that the pre-compiled binary for Ultrix I have been using off the UW CAC site doesn't have this capability enabled. Help, please... -- Craig A. Summerhill, Systems Coordinator and Program Officer Coalition for Networked Information 21 Dupont Circle, N.W., Washington, D.C. 20036 Internet: craig@cni.org AT&Tnet (202) 296-5098 -- ----------------------------------------------------------------- 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, 7 Jul 1999 13:15:34 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA08013 for ; Wed, 7 Jul 1999 13:15:33 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA26552; Wed, 7 Jul 1999 13:15:31 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA05521; Wed, 7 Jul 1999 13:15:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA48780 for ; Wed, 7 Jul 1999 13:10:51 -0700 Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA30922 for ; Wed, 7 Jul 1999 13:10:50 -0700 Received: (from uucp@localhost) by mail.ntplx.net (8.9.1/NETPLEX) id QAA25170 for u.washington.edu!pine-info; Wed, 7 Jul 1999 16:10:49 -0400 (EDT) >Received: (from dcg@localhost) by macdco.macdco.com (8.8.8/SCO5) id QAA03921; Wed, 7 Jul 1999 16:07:13 -0400 (EDT) Message-Id: Date: Wed, 7 Jul 1999 16:07:13 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: David Giannelli To: Pine Discussion Forum Subject: Pine 4.10 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: dcg@macdco X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am currently using Pine 3.96 for SCO Open Server 5. Would anyone know where I can get a later version of Pine (compiled)? Thanks in advance for the help. 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, 7 Jul 1999 15:58:21 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA12266 for ; Wed, 7 Jul 1999 15:58:20 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA31047; Wed, 7 Jul 1999 15:58:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA12287; Wed, 7 Jul 1999 15:57:40 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA51886 for ; Wed, 7 Jul 1999 15:53:50 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA09822 for ; Wed, 7 Jul 1999 15:53:49 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Wed, 7 Jul 1999 17:53:44 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Thu, 8 Jul 1999 06:53:11 +0800 Message-Id: <001901bec8cb$782ddb20$1511b381@twntpe.cdc.com> Date: Thu, 8 Jul 1999 06:53:03 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Diane Griffitts" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Diane, You're probably pretty tired of all this by now.... I know I am. :-) :-) > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > the mbx format and my UNIX Pine implementation can't read them that way. > So does anybody know: 1) is there any way to keep PC-Pine from doing such > a conversion and 2) if my theory is true, is there any way to convert > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > them? Any light anyone can shed on this would be much appreciated. In a previous email I directly answered your 2 questions. I did fail, however, to broaden my investigation. Other than not getting paid for this there probably is no excuse. :-) :-) Anyway, I did do a binary FTP (you shouldn't do ASCII FTP since it will damage the file) of a PC-Pine folder to both a Sun running pine 4.10 and an HP running pine 4.10 (GCC build of pine). In both cases pine was able to access/read/manipulate the folder without difficulty. You've not said much more about the problem. So, maybe you've fixed it (found a solution) in spite of us. :-) Ed 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, 9 Jul 1999 22:37:47 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id WAA30740 for ; Fri, 9 Jul 1999 22:37:46 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id WAA26645; Fri, 9 Jul 1999 22:37:45 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id WAA27554; Fri, 9 Jul 1999 22:37:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA60640 for ; Fri, 9 Jul 1999 22:31:29 -0700 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.06) with ESMTP id WAA23438 for ; Fri, 9 Jul 1999 22:31:29 -0700 Received: from taxa.psyc.missouri.edu (taxa.psyc.missouri.edu [128.206.45.83]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id WAA25963 for ; Fri, 9 Jul 1999 22:31:28 -0700 Received: from localhost (mbmiller@localhost) by taxa.psyc.missouri.edu (8.8.8+Sun/8.8.8) with ESMTP id AAA22527 for ; Sat, 10 Jul 1999 00:31:00 -0500 (CDT) Message-Id: Date: Sat, 10 Jul 1999 00:31:00 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Mike Miller To: Pine Discussion Forum Subject: search within message text MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE-INFO list X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN When I use 'select' to search within a message folder as follows: ;ta (text, all) it seems to include the message header. I wanted to search for 'miller' in a collection of messages to see if my name was mentioned, but all of the messages were flagged because 'mbmiller' was somewhere in the header of every message. Is there no way to search message text only (not header)? If not, I suggest that it would be a useful feature. Regards, Mike -- Michael B. Miller, M.S., Ph.D., M.P.E. Department of Psychology 210 McAlester Hall University of Missouri--Columbia Columbia, MO 65211 Phone: (573) 882-5671 Fax: (573) 882-7710 e-mail: mbmiller@taxa.psyc.missouri.edu web: http://taxa.psyc.missouri.edu/~mbmiller/ -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From 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, 12 Jul 1999 11:15:59 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA04352 for ; Mon, 12 Jul 1999 11:15:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA19888; Mon, 12 Jul 1999 11:15:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA20147; Mon, 12 Jul 1999 11:15:08 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA34734 for ; Mon, 12 Jul 1999 11:09:51 -0700 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.06) with ESMTP id LAA29805 for ; Mon, 12 Jul 1999 11:09:51 -0700 Received: from localhost (hubert@localhost) by shiva1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA07492; Mon, 12 Jul 1999 11:09:44 -0700 Message-Id: Date: Mon, 12 Jul 1999 11:09:43 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steve Hubert To: Pine Discussion Forum Subject: Re: shared .addressbooks In-Reply-To: <9907071959.AA04725@a.cni.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Craig A Summerhill X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Craig, It sounds like what you are trying to do should work. Make sure the permissions for the directory containing the addressbook file as well as the address book file have group write permission. I can't remember for sure, you may also need group write permission for the file .addressbook.lu. If still no luck try running pine -d7 from the account where it is failing and look for clues in the .pine-debug1 file after quitting pine. -- Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 7 Jul 1999, Craig A Summerhill wrote: > I briefly reviewed the Pine Information Center on www.washington.edu > and did not see the answer to this problem I am having. Nevertheless, > I suspect this is an FAQ. Apologies in advance if it is obvious, but > I can't find an answer... > > > Environment: > (Ancient) DEC 5000 w/ Ultrix 4.5 > Pine 4.10 (pre-compiled binary from ftp.cac.washington.edu) > > > Can somebody give me a quick start explanation of how to enable a > shared addressbook in Pine. I do not have an IMAP server setup and > running, so I am interested in doing this with local files. > > I have a couple of users (we'll say userA and userB) who want to > share a common set of saved addresses so that they can keep their > addressbooks in sync. I tried changing the permissions to 664 on > ~userA/.addressbook and naming that file in ~userB/.pinerc file as > the local addressbook for userB, but try as I might userB is always > limited to READ ONLY access for the addressbook (when accessing the > file from within the Pine Main Menu Addressbook function). This is > frustrating, and I don't understand why. All file and directory > permissions for the file and the path in question are properly set > to allow each user to write to the file with the operating system, > but Pine insists on blocking the non-owner's write access to the > file. > > Feature or bug? > > I have also tried using a 'neutral' third party location and filename > for the shared file (/usr/local/lib/shared_addressbook), but only the > user with primary ownership of the file in question ever has write > access from within Pine. > > > What am I missing here? The only thing I can think of is that there > is some kind of flag/macro which needs to be set at compile time to > enable this, and that the pre-compiled binary for Ultrix I have been > using off the UW CAC site doesn't have this capability enabled. > > Help, please... > 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, 12 Jul 1999 15:18:56 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA20815 for ; Mon, 12 Jul 1999 15:18:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA25939; Mon, 12 Jul 1999 15:18:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA29601; Mon, 12 Jul 1999 15:18:21 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA40998 for ; Mon, 12 Jul 1999 15:13:55 -0700 Received: from harrier.csrv.uidaho.edu (root@harrier.csrv.uidaho.edu [129.101.119.224]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA01970 for ; Mon, 12 Jul 1999 15:13:53 -0700 Received: from raptor.csrv.uidaho.edu (dianeg@raptor.csrv.uidaho.edu [129.101.119.252]) by harrier.csrv.uidaho.edu (8.8.6 (PHNE_17135)/) with ESMTP id PAA04775 for ; Mon, 12 Jul 1999 15:13:51 -0700 (PDT) Received: from localhost (dianeg@localhost) by raptor.csrv.uidaho.edu (8.8.6 (PHNE_14041)/UI.ITS.MAIL) with ESMTP id PAA11472 for ; Mon, 12 Jul 1999 15:13:49 -0700 (PDT) Message-Id: Date: Mon, 12 Jul 1999 15:13:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Diane Griffitts To: Pine Discussion Forum Subject: RE: Folder Format Problem PC-Pine/UNIX Pine In-Reply-To: <001901bec8cb$782ddb20$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: raptor.csrv.uidaho.edu: dianeg owned process doing -bs X-Sender: dianeg@raptor.csrv.uidaho.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks to Ed and everyone who contributed to this discussion (so far). I appreciate the helpful suggestions and information, and I figure the heated comments signify people who care a lot about the technology issues they are working with. As for solving the problem, I'm waiting for a reply from a UNIX administrator in our IT group to confirm my suspicion that our UNIX Pine implementation has been configured to not use the mbx folder format since we are in an NFS environment. In the meantime, I plan to try your suggestion of copying messages between PC-Pine and UNIX Pine folders via IMAP (we do have it, I just haven't been using it up to now). I'm curious how exactly to accomplish the transfer between different folder collections, but I'll see how it goes. Given my fairly limited needs for PC-Pine, I'm starting to wonder if I would be/would have been better off with a 3.9X version where the UNIX folder capabilities were read-only. However, since I'm reading them on a hard drive local to the PC, maybe that wouldn't help. Anyway, it's been very educational so far. On Thu, 8 Jul 1999, Ed Greshko wrote: > Diane, > > You're probably pretty tired of all this by now.... I know I am. :-) :-) > > > Based on FAQ 7.2, I'm thinking PC-Pine might have converted these files to > > the mbx format and my UNIX Pine implementation can't read them that way. > > So does anybody know: 1) is there any way to keep PC-Pine from doing such > > a conversion and 2) if my theory is true, is there any way to convert > > these folders back to the UNIX Berkeley mail format so UNIX Pine can read > > them? Any light anyone can shed on this would be much appreciated. > > In a previous email I directly answered your 2 questions. I did fail, however, > to broaden my investigation. Other than not getting paid for this there > probably is no excuse. :-) :-) > > Anyway, I did do a binary FTP (you shouldn't do ASCII FTP since it will damage > the file) of a PC-Pine folder to both a Sun running pine 4.10 and an HP running > pine 4.10 (GCC build of pine). In both cases pine was able to > access/read/manipulate the folder without difficulty. > > You've not said much more about the problem. So, maybe you've fixed it (found a > solution) in spite of us. :-) > > Ed > > > _ ^ ______________________________________________ / \ Diane Griffitts - - dianeg@uidaho.edu / \ System Network Analyst | University of Idaho Boise Center __________________________________________________ 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, 13 Jul 1999 13:00:53 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA08192 for ; Tue, 13 Jul 1999 13:00:52 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA17506; Tue, 13 Jul 1999 13:00:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA27631; Tue, 13 Jul 1999 13:00:14 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA16064 for ; Tue, 13 Jul 1999 12:55:46 -0700 Received: from indy1.calarts.edu (indy1.calarts.edu [156.3.140.68]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA24405 for ; Tue, 13 Jul 1999 12:55:45 -0700 Received: from calarts.edu (susan.calarts.edu [156.3.141.72]) by indy1.calarts.edu (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id MAA17329 for ; Tue, 13 Jul 1999 12:54:00 -0700 (PDT) Message-Id: <378B9A3D.EBC90C5@calarts.edu> Date: Tue, 13 Jul 1999 12:57:49 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Susan Lowenberg To: Pine Discussion Forum Subject: New Mail Not Displaying MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have a user who is getting the error message "New mail move failed disk quota exceeded" when accessing Pine. No new e-mail messages are being displayed in pine but they are being appended to the user's /var/mail file. The user's disk quotas are Filesystem usage quota limit timeleft files quota limit timeleft / 41 5000 6000 0 0 0 /var/mail 2668 5000 6000 1 0 0 /usr/people 4380 5000 6000 59 0 0 We are using version 4.05 of Pine. I've searched the archives but haven't found anything on this problem. Any clues as to the cause of this problem would be greatly appreciated. Thanks. -- Susan Lowenberg Information Resources Librarian California Institute of the Arts e-mail: susan@calarts.edu voice: 661-253-7888 fax: 661-254-4561 -- ----------------------------------------------------------------- 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, 13 Jul 1999 13:54:15 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA09744 for ; Tue, 13 Jul 1999 13:54:14 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA19079; Tue, 13 Jul 1999 13:54:12 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA01345; Tue, 13 Jul 1999 13:53:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA22766 for ; Tue, 13 Jul 1999 13:50:33 -0700 Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id NAA03168 for ; Tue, 13 Jul 1999 13:50:32 -0700 Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.5); Tue, 13 Jul 99 14:50:30 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id OAA09884 for ; Tue, 13 Jul 1999 14:50:30 -0600 (MDT) Message-Id: <77349FC5DC1CD211BAD900805FA7241A0685B0D6-100000@es01snlnt.sandia.gov> Date: Tue, 13 Jul 1999 14:50:31 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: New Mail Not Displaying In-Reply-To: <378B9A3D.EBC90C5@calarts.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B95791C71458-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 13 Jul 1999, Susan Lowenberg wrote: > I have a user who is getting the error message "New mail move failed > disk quota exceeded" when accessing Pine. No new e-mail messages are > being displayed in pine but they are being appended to the user's > /var/mail file. > > The user's disk quotas are > Filesystem usage quota limit timeleft files quota limit > timeleft > / 41 5000 6000 0 0 > 0 > /var/mail 2668 5000 6000 1 0 > 0 > /usr/people 4380 5000 6000 59 0 > 0 Pine is trying to move the mail into the user's personal space. If you notice the quota info, the user is already near the limit, and moving the mail would put him over that limit. 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, 14 Jul 1999 08:22:22 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id IAA31374 for ; Wed, 14 Jul 1999 08:22:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA26953; Wed, 14 Jul 1999 08:22:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA24268; Wed, 14 Jul 1999 08:21:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA19726 for ; Wed, 14 Jul 1999 08:17:58 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA26815 for ; Wed, 14 Jul 1999 08:17:56 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id UAA19593 for ; Wed, 14 Jul 1999 20:47:24 +0530 (IST) Message-Id: Date: Wed, 14 Jul 1999 20:47:24 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Viewing URLs from within Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I use Pine V4.10 for Solaris and I have a query on viewing URLs from within Pine. My Pine is configured for both Netscape and Lynx as url-viewers and they both work fine. I would like to know if there is a way by which, I can toggle between the choice of browsers with a hot-key rather than manually editing the application, everytime I switch browsers. I find it much faster to view text-based articles with Lynx than Netscape. If there is no direct way of doing this in V4.10, I think it would be a pretty nifty feature to have in later releases. -- Thanks, Srikanth -- ----------------------------------------------------------------- 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, 14 Jul 1999 12:23:05 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id MAA04426 for ; Wed, 14 Jul 1999 12:23:04 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA02490; Wed, 14 Jul 1999 12:23:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA05921; Wed, 14 Jul 1999 12:22:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA25954 for ; Wed, 14 Jul 1999 12:18:14 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id MAA25249 for ; Wed, 14 Jul 1999 12:18:14 -0700 Received: from goedel1.math.washington.edu (chappa@goedel1.math.washington.edu [128.95.224.2]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id MAA01976 for ; Wed, 14 Jul 1999 12:18:17 -0700 (PDT) Message-Id: Date: Wed, 14 Jul 1999 12:18:15 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: interupted message 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 -- ListProcessor(tm) by CREN Hello I have a very general question, but I want to know under which conditions pine does not create an interrupted message when the session is broken. I was writing a message at home, which intended to be long and I had to lift the phone (don't ask why, I had to do it). The communication got broken in a few seconds, and when I came back there was no interrupted message. Why not? Eduardo http://www.math.washington.edu/~chappa/personal.html -- ----------------------------------------------------------------- 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, 14 Jul 1999 12:51:41 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id MAA02461 for ; Wed, 14 Jul 1999 12:51:40 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id MAA02616; Wed, 14 Jul 1999 12:51:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id MAA06877; Wed, 14 Jul 1999 12:51:04 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id MAA41230 for ; Wed, 14 Jul 1999 12:46:56 -0700 Received: from hotmail.com (law2-f212.hotmail.com [216.32.181.212]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id MAA12784 for ; Wed, 14 Jul 1999 12:46:56 -0700 Received: (qmail 55960 invoked by uid 0); 14 Jul 1999 19:36:17 -0000 Received: from 216.99.198.109 by www.hotmail.com with HTTP; Wed, 14 Jul 1999 12:36:16 PDT Message-Id: <19990714193617.55959.qmail@hotmail.com> Date: Wed, 14 Jul 1999 12:36:16 PDT Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "STEVE CONRAD" To: Pine Discussion Forum Subject: too many addresses in header Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [216.99.198.109] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Pine List, I have created a huge global address book in order to send everyone at our company an email message. Is there a way to make pine send to a large group of people without showing all the addresses in the header. There are currently 5 or 5 pages of addresses before the message body. Any suggestions are muchly appreciated. Sincerely, Steve Conrad System Administrator McGuire Bearing Co. _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.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; Wed, 14 Jul 1999 14:42:30 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id OAA07460 for ; Wed, 14 Jul 1999 14:42:28 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA06117; Wed, 14 Jul 1999 14:42:27 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA09562; Wed, 14 Jul 1999 14:41:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA58716 for ; Wed, 14 Jul 1999 14:35:52 -0700 Received: from kens.com (kens.com [129.250.30.40]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id OAA18390 for ; Wed, 14 Jul 1999 14:35:51 -0700 Received: from kens.com (kens.com [129.250.30.40]) by kens.com (8.9.3/8.9.3-mod-for-majordomo) with ESMTP id RAA02030; Wed, 14 Jul 1999 17:35:51 -0400 (EDT) Message-Id: Date: Wed, 14 Jul 1999 17:35:51 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Ken Woods To: Pine Discussion Forum Subject: Re: too many addresses in header In-Reply-To: <19990714193617.55959.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: STEVE CONRAD X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Damn, I must get getting old. I can remember a time when the answer would have been "man pine" *sigh* c ^R (down arrow) (down arrow) (down arrow) (down arrow) (down arrow) ^g On Wed, 14 Jul 1999, STEVE CONRAD wrote: > company an email message. Is there a way to make pine send to a large group > of people without showing all the addresses in the header. There are -- 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; Wed, 14 Jul 1999 14:47:54 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id OAA07508 for ; Wed, 14 Jul 1999 14:47:54 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA05710; Wed, 14 Jul 1999 14:47:52 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA12165; Wed, 14 Jul 1999 14:47:13 -0700 Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA31420 for ; Wed, 14 Jul 1999 14:36:25 -0700 Received: from dante22.u.washington.edu (leibrand@dante22.u.washington.edu [140.142.15.72]) by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA04738 for ; Wed, 14 Jul 1999 14:36:24 -0700 Received: from localhost (leibrand@localhost) by dante22.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA56930 for ; Wed, 14 Jul 1999 14:36:23 -0700 Message-Id: Date: Wed, 14 Jul 1999 14:36:23 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: too many addresses in header In-Reply-To: <19990714193617.55959.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN While your cursor is on one of the headers, press ^R (Ctrl+R) to get Rich Headers. Enter the group or addresses in the Lcc: or Bcc: fields. Pine also has great context-sensitive help on both of them. To access it, press ^G with your cursor on the appropriate header. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Wed, 14 Jul 1999, STEVE CONRAD wrote: > Dear Pine List, > > I have created a huge global address book in order to send everyone at our > company an email message. Is there a way to make pine send to a large group > of people without showing all the addresses in the header. There are > currently 5 or 5 pages of addresses before the message body. > > Any suggestions are muchly appreciated. > > Sincerely, > > Steve Conrad > System Administrator > McGuire Bearing Co. > > > > _______________________________________________________________ > Get Free Email and Do More On The Web. Visit http://www.msn.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, 14 Jul 1999 16:41:04 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA10277 for ; Wed, 14 Jul 1999 16:41:03 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA08589; Wed, 14 Jul 1999 16:41:01 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA12945; Wed, 14 Jul 1999 16:40:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA37792 for ; Wed, 14 Jul 1999 16:35:23 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA27694 for ; Wed, 14 Jul 1999 16:35:22 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id XAA09066; Wed, 14 Jul 1999 23:41:01 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Wed, 14 Jul 99 16:41 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id QAA11027; Wed, 14 Jul 1999 16:26:23 -0700 Message-Id: Date: Wed, 14 Jul 1999 16:26:20 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: too many addresses in header In-Reply-To: <19990714193617.55959.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: STEVE CONRAD X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 14 Jul 1999, STEVE CONRAD wrote: > Dear Pine List, > > I have created a huge global address book in order to send everyone at our > company an email message. Is there a way to make pine send to a large group > of people without showing all the addresses in the header. There are > currently 5 or 5 pages of addresses before the message body. > > Any suggestions are muchly appreciated. My sugestion is in a case like this you probably want to use a lcc. This is a pine feature (may be implemented in other mailers), which hides all the individual addresses, but creates a ``false'' To: line (ie. one that has no actuall address in it), so that there is a valid To: line (which in some cases can cause problems. Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 14 Jul 1999 17:35:40 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id RAA11135 for ; Wed, 14 Jul 1999 17:35:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA10611; Wed, 14 Jul 1999 17:35:37 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA17504; Wed, 14 Jul 1999 17:35:10 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA37750 for ; Wed, 14 Jul 1999 17:30:02 -0700 Received: from dante16.u.washington.edu (leibrand@dante16.u.washington.edu [140.142.15.42]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA11752 for ; Wed, 14 Jul 1999 17:30:01 -0700 Received: from localhost (leibrand@localhost) by dante16.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA62842 for ; Wed, 14 Jul 1999 17:30:01 -0700 Message-Id: Date: Wed, 14 Jul 1999 17:30:00 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: interupted message question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What version of Pine are you using? We were experiencing similar problems at the UW with Pine 4.05 whenever the message got longer than about 3k (there was no exact cutoff, though). The problem was solved around the time we upgraded to 4.10, but I'm not sure that the upgrade was what fixed it. Would someone from the Pine team care to enlighten us as to exactly what the problem was and how it was fixed? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Wed, 14 Jul 1999, Eduardo Chappa L. wrote: > Hello > > I have a very general question, but I want to know under which > conditions pine does not create an interrupted message when the session is > broken. I was writing a message at home, which intended to be long and I > had to lift the phone (don't ask why, I had to do it). The communication > got broken in a few seconds, and when I came back there was no interrupted > message. Why not? > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > > 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, 15 Jul 1999 04:40:17 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id EAA21897 for ; Thu, 15 Jul 1999 04:40:16 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id EAA20478; Thu, 15 Jul 1999 04:40:14 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA08651; Thu, 15 Jul 1999 04:39:51 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA28490 for ; Thu, 15 Jul 1999 04:35:26 -0700 Received: from spira.plb.de (spira.plb.de [193.175.255.7]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id EAA30585 for ; Thu, 15 Jul 1999 04:34:40 -0700 Received: from spira.plb.de (bork@spira.plb.de [193.175.255.7]) by spira.plb.de (8.8.5/8.8.5) with SMTP id MAA05316 for ; Thu, 15 Jul 1999 12:07:27 -0200 Message-Id: Date: Thu, 15 Jul 1999 12:07:27 -0200 (GMT+2) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "H. Bork" To: Pine Discussion Forum Subject: POP and IMAP: password encryption ? In-Reply-To: <000301bec807$4d3b49d0$1511b381@twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello out there, here's a tiny question: is there any kind of password encryption for POP and/or IMAP clients when contacting their mailserver ? TIA kind regards, hal ;-) -- ----------------------------------------------------------------- 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, 15 Jul 1999 07:40:23 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id HAA17462 for ; Thu, 15 Jul 1999 07:40:22 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA22348; Thu, 15 Jul 1999 07:40:21 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA28940; Thu, 15 Jul 1999 07:39:49 -0700 Received: from jason01.u.washington.edu (root@jason01.u.washington.edu [140.142.70.24]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA49912 for ; Thu, 15 Jul 1999 07:35:49 -0700 Received: from dante22.u.washington.edu (leibrand@dante22.u.washington.edu [140.142.15.72]) by jason01.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA24996 for ; Thu, 15 Jul 1999 07:35:48 -0700 Received: from localhost (leibrand@localhost) by dante22.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA26594 for ; Thu, 15 Jul 1999 07:35:48 -0700 Message-Id: Date: Thu, 15 Jul 1999 07:35:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: POP and IMAP: password encryption ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes and no. If you're connecting from a Unix machine running Pine to a Unix mail server that supports SSH, you can tell Pine to use SSH to connect by modifying the rsh-path and rsh-command entries in the .pinerc. Of course, you'll need to change the paths to match the location of the files on your system. # Sets the name of the command used to open a UNIX remote shell # connection. The default is tyically /usr/ucb/rsh. rsh-path=/usr/local/bin/ssh # Sets the format of the command used to open a UNIX remote # shell connection. The default is "%s %s -l %s exec /etc/r%sd" # NOTE: the 4 (four) "%s" entries MUST exist in the provided command # where the first is for the command's path, the second is for the # host to connnect to, the third is for the user to connect as, and the # fourth is for the connection method (typically "imap") rsh-command=%s %s -q -l %s exec /etc/r%sd If you're connecting with PC-Pine, there is currently no publically available method of connecting securely. Outlook Express supports SSL IMAP connections, however, and I'm sure an encrypted version of PC-Pine will be released eventually. Of course, you could also use PGP or some such program to encrypt the actual e-mails before you send them... -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Thu, 15 Jul 1999, H. Bork wrote: > Hello out there, > here's a tiny question: > > is there any kind of password encryption > for POP and/or IMAP clients > when contacting their mailserver ? > > TIA kind regards, hal ;-) > > 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, 15 Jul 1999 08:28:21 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id IAA24230 for ; Thu, 15 Jul 1999 08:28:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA24410; Thu, 15 Jul 1999 08:28:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA01223; Thu, 15 Jul 1999 08:27:52 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA38096 for ; Thu, 15 Jul 1999 08:24:12 -0700 Received: from spira.plb.de (root@spira.plb.de [193.175.255.7]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id IAA23159; Thu, 15 Jul 1999 08:24:04 -0700 Received: from spira.plb.de (bork@spira.plb.de [193.175.255.7]) by spira.plb.de (8.8.5/8.8.5) with SMTP id PAA06821; Thu, 15 Jul 1999 15:56:58 -0200 Message-Id: Date: Thu, 15 Jul 1999 15:56:58 -0200 (GMT+2) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "H. Bork" To: Pine Discussion Forum Subject: 2Re: POP and IMAP: password encryption ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: Scott Leibrand X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks a lot, Scott, fine solution to one of my problems, u2u. >PC-Pine,...no...available method of connecting securely. ... >an encrypted version of PC-Pine will be released eventually. Any Washington hints when that great event might occur ? Just password encryption would do for the moment. TIA+kind regards, hal ;-) ps anyone ever heard of SSH for olde DOS andor Win311 ? well - just wanna ask :) 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, 15 Jul 1999 08:33:19 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id IAA24094 for ; Thu, 15 Jul 1999 08:33:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA23671; Thu, 15 Jul 1999 08:33:16 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA01277; Thu, 15 Jul 1999 08:32:44 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA15586 for ; Thu, 15 Jul 1999 08:29:36 -0700 Received: from mm02snlnto.sandia.gov (mm02snlnto.sandia.gov [132.175.109.21]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id IAA08867 for ; Thu, 15 Jul 1999 08:29:35 -0700 Received: from 132.175.109.1 by mm02snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.6); Thu, 15 Jul 99 09:29:30 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id JAA07389 for ; Thu, 15 Jul 1999 09:29:26 -0600 (MDT) Message-Id: Date: Thu, 15 Jul 1999 09:25:48 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: POP and IMAP: password encryption ? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B9321D048099-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Also, you can compile Kerberos into Pine. Then if your server supports it, you can use the /secure switch to use that auth method. Another possibility is to use the SSL hack that somebody posted a while back. Still another is that if the server is running rimapd, you don't even need to enter a password. On Thu, 15 Jul 1999, Scott Leibrand wrote: > Yes and no. If you're connecting from a Unix machine running Pine to a > Unix mail server that supports SSH, you can tell Pine to use SSH to > connect by modifying the rsh-path and rsh-command entries in the .pinerc. > Of course, you'll need to change the paths to match the location of the > files on your system. 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, 15 Jul 1999 09:14:28 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA24934 for ; Thu, 15 Jul 1999 09:14:27 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA25655; Thu, 15 Jul 1999 09:14:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA05106; Thu, 15 Jul 1999 09:13:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA37760 for ; Thu, 15 Jul 1999 09:09:38 -0700 Received: from gort.office.aol.com (pix-fw.wan.aol.com [152.163.190.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA30495 for ; Thu, 15 Jul 1999 09:09:38 -0700 Received: from DBPETE ([10.2.110.102]) by gort.office.aol.com with ESMTP (8.7.1/8.7.1) id MAA09924 for ; Thu, 15 Jul 1999 12:15:19 -0400 (EDT) Message-Id: Date: Thu, 15 Jul 1999 12:09:33 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dan Peterson To: Pine Discussion Forum Subject: Enabling Roles MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: pete@gort.office.aol.com X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is there a configuration setting that needs to be set to enable Roles? I've set up a role with only a "To" pattern (the rest of the fields are set to ""), but it never seems to match anything I reply to. If I set "confirm-role-even-for-default", then I'm prompted for a role, but it's always the "Default-Role". How do I get the Roles to be automatically selected? -- ----------------------------------------------------------------- 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, 15 Jul 1999 09:18:05 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA25016 for ; Thu, 15 Jul 1999 09:18:03 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA25801; Thu, 15 Jul 1999 09:18:02 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA05229; Thu, 15 Jul 1999 09:16:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA46066 for ; Thu, 15 Jul 1999 09:12:05 -0700 Received: from shiva2.cac.washington.edu (shiva2.cac.washington.edu [140.142.100.202]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA30910 for ; Thu, 15 Jul 1999 09:12:04 -0700 Received: from D-140-142-110-67.dhcp2.washington.edu (D-140-142-110-67.dhcp2.washington.edu [140.142.110.67]) by shiva2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA21386; Thu, 15 Jul 1999 09:11:56 -0700 Message-Id: Date: Thu, 15 Jul 1999 09:18:18 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Terry Gray To: Pine Discussion Forum Subject: Re: 2Re: POP and IMAP: password encryption ? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "H. Bork" X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 15 Jul 1999, H. Bork wrote: > >PC-Pine,...no...available method of connecting securely. ... > >an encrypted version of PC-Pine will be released eventually. > > Any Washington hints when that great event might occur ? > Just password encryption would do for the moment. Hal, We never know when a new release is actually going to appear (except that it is always much later than we anticipated)... but there is reason for some *cautious* optimism that a world-releasable form of SSL for PC-Pine will make it into the upcoming 4.20 release. That is certainly our goal, anyway. -teg 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, 15 Jul 1999 11:39:50 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA27581 for ; Thu, 15 Jul 1999 11:39:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA29847; Thu, 15 Jul 1999 11:39:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA08979; Thu, 15 Jul 1999 11:39:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA44554 for ; Thu, 15 Jul 1999 11:33:18 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA28082 for ; Thu, 15 Jul 1999 11:33:18 -0700 Received: from goedel1.math.washington.edu (chappa@goedel1.math.washington.edu [128.95.224.2]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA07025 for ; Thu, 15 Jul 1999 11:33:22 -0700 (PDT) Message-Id: Date: Thu, 15 Jul 1999 11:33:19 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: interupted message 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 -- ListProcessor(tm) by CREN *** Scott Leibrand (leibrand@u.washington.edu) wrote on Jul 14, 1999: :) What version of Pine are you using? We were experiencing similar problems :) at the UW with Pine 4.05 whenever the message got longer than about 3k From the headers in my message you can see I use pine4.10. I was lucky my message was not too long at that time, so I did not loose much. But I still do not understand why an interrupted message was not created. Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 15 Jul 1999 11:48:40 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA21907 for ; Thu, 15 Jul 1999 11:48:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA29238; Thu, 15 Jul 1999 11:48:36 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA11999; Thu, 15 Jul 1999 11:48:17 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA16960 for ; Thu, 15 Jul 1999 11:45:09 -0700 Received: from dante05.u.washington.edu (leibrand@dante05.u.washington.edu [140.142.15.7]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA13624 for ; Thu, 15 Jul 1999 11:45:08 -0700 Received: from localhost (leibrand@localhost) by dante05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA60740 for ; Thu, 15 Jul 1999 11:45:07 -0700 Message-Id: Date: Thu, 15 Jul 1999 11:45:07 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: interupted message question In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Thu, 15 Jul 1999, Eduardo Chappa L. wrote: > *** Scott Leibrand (leibrand@u.washington.edu) wrote on Jul 14, 1999: > > :) What version of Pine are you using? We were experiencing similar problems > :) at the UW with Pine 4.05 whenever the message got longer than about 3k > > From the headers in my message you can see I use pine4.10. I was lucky > my message was not too long at that time, so I did not loose much. But I > still do not understand why an interrupted message was not created. > > Eduardo Me neither. That's why I asked the Pine team to explain. :) If I were you, I'd do some tests by composing nonsense messages, disconnecting, and see under what conditions it saves an interrupted message. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Jul 1999 14:51:14 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id OAA31554 for ; Thu, 15 Jul 1999 14:51:13 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA02490; Thu, 15 Jul 1999 14:51:11 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA01100; Thu, 15 Jul 1999 14:50:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA44786 for ; Thu, 15 Jul 1999 14:47:20 -0700 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.06) with ESMTP id OAA19021 for ; Thu, 15 Jul 1999 14:47:19 -0700 Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with SMTP id OAA01576 for ; Thu, 15 Jul 1999 14:47:18 -0700 Received: from luomat.peak.org [207.141.129.114] by 1stpc.org with ESMTP (SMTPD32-4.04) id A78D48450180; Thu, 15 Jul 1999 17:50:05 EST Received: by luomat.peak.org (8.9.3/8.9.0) id RAA19414 for pine-info@cac.washington.edu; Thu, 15 Jul 1999 17:47:12 -0400 (EDT) Message-Id: <199907152147.RAA19414@ocalhost> Date: Thu, 15 Jul 1999 17:47:08 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timothy J Luoma To: Pine Discussion Forum Subject: order of "roles" 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 -- ListProcessor(tm) by CREN Does anyone else have this happen? I've got 5 roles defined: default peak ap usenet lists When I hit control-p/n (previous/next role) to scroll through the roles, they seem to change order. This is annoying, as I would like to be able to hit 'control-p' three times to always get to 'usenet' (for example). I don't much care what order they are in (although it would be nice to be able to specify) as long as they are consistent. 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; Thu, 15 Jul 1999 15:03:00 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA31581 for ; Thu, 15 Jul 1999 15:02:59 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA01925; Thu, 15 Jul 1999 15:02:57 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA17484; Thu, 15 Jul 1999 15:02:37 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA30486 for ; Thu, 15 Jul 1999 14:59:21 -0700 Received: from dante14.u.washington.edu (leibrand@dante14.u.washington.edu [140.142.15.40]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA11094 for ; Thu, 15 Jul 1999 14:59:20 -0700 Received: from localhost (leibrand@localhost) by dante14.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA32156 for ; Thu, 15 Jul 1999 14:59:19 -0700 Message-Id: Date: Thu, 15 Jul 1999 14:59:19 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: order of "roles" In-Reply-To: <199907152147.RAA19414@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I think what you may be seeing is that the role the selection starts on (before you press ^p or ^n) is different each time. Is that the case, or does their actual order change? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Thu, 15 Jul 1999, Timothy J Luoma wrote: > > Does anyone else have this happen? > > I've got 5 roles defined: > > default > peak > ap > usenet > lists > > When I hit control-p/n (previous/next role) to scroll through the roles, > they seem to change order. This is annoying, as I would like to be able to > hit 'control-p' three times to always get to 'usenet' (for example). > > I don't much care what order they are in (although it would be nice to be > able to specify) as long as they are consistent. > > 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; Thu, 15 Jul 1999 15:19:22 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA32096 for ; Thu, 15 Jul 1999 15:19:21 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA02459; Thu, 15 Jul 1999 15:19:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA02621; Thu, 15 Jul 1999 15:18:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA37692 for ; Thu, 15 Jul 1999 15:16:01 -0700 Received: from 1stpc.org (a147.ccgnv.net [207.141.129.147]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id PAA04823; Thu, 15 Jul 1999 15:16:00 -0700 Received: from luomat.peak.org [207.141.129.91] by 1stpc.org with ESMTP (SMTPD32-4.04) id AE49715A0278; Thu, 15 Jul 1999 18:18:49 EST Received: by luomat.peak.org (8.9.3/8.9.0) id SAA22046; Thu, 15 Jul 1999 18:15:56 -0400 (EDT) Message-Id: <199907152215.SAA22046@ocalhost> Date: Thu, 15 Jul 1999 18:15:52 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: order of "roles" In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Replying to message of Thu, 15 Jul 1999 14:59:19 -0700 (PDT) from Scott Leibrand regarding ``Re: order of "roles"'' > I think what you may be seeing is that the role the selection starts on > (before you press ^p or ^n) is different each time. Is that the case, or > does their actual order change? The order changes. It is always at 'Default' and sometimes control-n gets me 'peak' and sometimes it gets me 'ap' At least I'm 95% sure that's what's happening... will test more tomorrow, but I think that's true. 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; Fri, 16 Jul 1999 13:46:43 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA19811 for ; Fri, 16 Jul 1999 13:46:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA27762; Fri, 16 Jul 1999 13:46:39 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA20669; Fri, 16 Jul 1999 13:45:48 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA43444 for ; Fri, 16 Jul 1999 13:41:52 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA12071 for ; Fri, 16 Jul 1999 13:41:52 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id NAA05436 for ; Fri, 16 Jul 1999 13:41:52 -0700 (PDT) Message-Id: Date: Fri, 16 Jul 1999 13:41:46 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: printing a message from the index In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello This is the situation. I open my folder index, press "Y" to print, I choose message instead of index and then choose the printer. After this the message should be printed, however, what actually happens is that the message is opened, and then printed. Why is this bothersome?, because I have setup a display-filter, which actually opens another program, and the message is not printed until this program is closed. I would like that the message not be opened in the screen when printed from the Index. Thanks, have a nice day. Eduardo http://www.math.washington.edu/~chappa/personal.html -- ----------------------------------------------------------------- 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, 16 Jul 1999 16:37:52 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA22568 for ; Fri, 16 Jul 1999 16:37:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA31852; Fri, 16 Jul 1999 16:37:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA10618; Fri, 16 Jul 1999 16:36:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA40838 for ; Fri, 16 Jul 1999 16:33:24 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA25618 for ; Fri, 16 Jul 1999 16:33:23 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id XAA04915; Fri, 16 Jul 1999 23:38:59 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Fri, 16 Jul 99 16:38 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id QAA32229; Fri, 16 Jul 1999 16:22:50 -0700 Message-Id: Date: Fri, 16 Jul 1999 16:22:49 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: printing a message from the index In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 16 Jul 1999, Eduardo Chappa L. wrote: > Hello > > This is the situation. I open my folder index, press "Y" to print, I > choose message instead of index and then choose the printer. After this the > message should be printed, however, what actually happens is that the > message is opened, and then printed. Why is this bothersome?, because I > have setup a display-filter, which actually opens another program, and the > message is not printed until this program is closed. I would like that the > message not be opened in the screen when printed from the Index. > > Thanks, have a nice day. Are you sure that it is doing this? It doesn't seem to be displaying the message on my system. Now, maybe it is because of some ``setup'' thing, but I don't know... I've just mannaged to make it fail miserably, which causes the index to disapear, but the print results to show up. Hey, I really don't know that it's not doing what you say, and MAYBE the existence of the display filter has something to do with it? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jul 1999 16:47:50 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA23341 for ; Fri, 16 Jul 1999 16:47:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA32096; Fri, 16 Jul 1999 16:47:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA25746; Fri, 16 Jul 1999 16:47:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA19652 for ; Fri, 16 Jul 1999 16:44:31 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA02782 for ; Fri, 16 Jul 1999 16:44:30 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id QAA26248; Fri, 16 Jul 1999 16:44:29 -0700 (PDT) Message-Id: Date: Fri, 16 Jul 1999 16:44:26 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: printing a message from the index In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jessica Rasku X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jessica Rasku (jrasku@ArmispianSystems.Rossland.bc.ca) wrote Today: :) :) Are you sure that it is doing this? It doesn't seem to be :) displaying the message on my system. Now, maybe it is because of some :) ``setup'' thing, but I don't know... I've just mannaged to make it fail :) miserably, which causes the index to disapear, but the print results to :) show up. Hey, I really don't know that it's not doing what you say, and :) MAYBE the existence of the display filter has something to do with it? :) :) Jessica :) Absoutely sure. I have "print-index" enabled, I am printing from the index, and I have the option, after pressing "%" (or "Y"), of printing the index or the message (the default is the message), and the problem is the display-filter. This is activated by the printing command, even though I am not opening the message (opening the message activates the display-filter, which opens the other program, which actually does not print the message unless I close the display program..UF!). Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 16 Jul 1999 19:27:02 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA24901 for ; Fri, 16 Jul 1999 19:27:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA01229; Fri, 16 Jul 1999 19:26:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA29815; Fri, 16 Jul 1999 19:26:41 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA13820 for ; Fri, 16 Jul 1999 19:23:08 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id TAA24692 for ; Fri, 16 Jul 1999 19:23:07 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id CAA06241; Sat, 17 Jul 1999 02:28:47 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Fri, 16 Jul 99 19:28 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id TAA00861; Fri, 16 Jul 1999 19:18:47 -0700 Message-Id: Date: Fri, 16 Jul 1999 19:18:46 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: printing a message from the index In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 16 Jul 1999, Eduardo Chappa L. wrote: > Absoutely sure. I have "print-index" enabled, I am printing from the > index, and I have the option, after pressing "%" (or "Y"), of printing the > index or the message (the default is the message), and the problem is the > display-filter. This is activated by the printing command, even though I am > not opening the message (opening the message activates the display-filter, > which opens the other program, which actually does not print the message > unless I close the display program..UF!). Ah, I think I see your problem. As I understand the purpose of the display filter, it is not to operate as a program to display the message itself, but as a way to do some processing to the message, before it is displayed. I could be totaly out to lunch here. But when you open a message ``normally'' do you not end up with a Pine window showing the message? And, does this happen when you print from the index? Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 16 Jul 1999 21:18:07 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id VAA25684 for ; Fri, 16 Jul 1999 21:18:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id VAA02655; Fri, 16 Jul 1999 21:18:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA15959; Fri, 16 Jul 1999 21:17:50 -0700 Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA14774 for ; Fri, 16 Jul 1999 21:12:52 -0700 Received: from homer11.u.washington.edu (sleib@homer11.u.washington.edu [140.142.78.12]) by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA18166 for ; Fri, 16 Jul 1999 21:12:51 -0700 Received: from localhost (sleib@localhost) by homer11.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA98428 for ; Fri, 16 Jul 1999 21:12:50 -0700 Message-Id: Date: Fri, 16 Jul 1999 21:12:50 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: printing a message from the index In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Sender: sleib@homer11.u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN That sounds like what is going on, but it doesn't really solve his problem. Can you think of any way to disable the display filters when a message is printed? It would seem to me that it would require a change in Pine's code, since Pine must determine how to display the message before printing it... -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Fri, 16 Jul 1999, Jessica Rasku wrote: > On Fri, 16 Jul 1999, Eduardo Chappa L. wrote: > > > Absoutely sure. I have "print-index" enabled, I am printing from the > > index, and I have the option, after pressing "%" (or "Y"), of printing the > > index or the message (the default is the message), and the problem is the > > display-filter. This is activated by the printing command, even though I am > > not opening the message (opening the message activates the display-filter, > > which opens the other program, which actually does not print the message > > unless I close the display program..UF!). > > Ah, I think I see your problem. As I understand the purpose of > the display filter, it is not to operate as a program to display the > message itself, but as a way to do some processing to the message, before > it is displayed. I could be totaly out to lunch here. But when you open > a message ``normally'' do you not end up with a Pine window showing the > message? And, does this happen when you print from the index? > > Jessica > > 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, 19 Jul 1999 09:41:59 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA04105 for ; Mon, 19 Jul 1999 09:41:58 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA17547; Mon, 19 Jul 1999 09:41:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA15754; Mon, 19 Jul 1999 09:41:29 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA40798 for ; Mon, 19 Jul 1999 09:36:25 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA16077; Mon, 19 Jul 1999 09:36:25 -0700 Received: from goedel1.math.washington.edu (chappa@goedel1.math.washington.edu [128.95.224.2]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA20698; Mon, 19 Jul 1999 09:36:25 -0700 (PDT) Message-Id: Date: Mon, 19 Jul 1999 09:36:23 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: printing a message from the index In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Scott Leibrand (leibrand@u.washington.edu) wrote on Jul 16, 1999: :) That sounds like what is going on, but it doesn't really solve his :) problem. Can you think of any way to disable the display filters when a :) message is printed? It would seem to me that it would require a change in :) Pine's code, since Pine must determine how to display the message before :) printing it... :) Yes, I understand this, but the filter only affects my reading on display of it, I do not expect it to affect the printing of it. In my case to explain to you, my filter is triggered by the tags or (ok, same tag, but different for the filter), and it starts lynx. Upon exiting lynx I can print the message that I already wanted to print. That's why I was wondering about the filter. I do not think it should be started, unless what the printer did, was to print the outcome of the filter, which is not, as I can see (I print messages that are double space in the display, but are not in the printer). Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 20 Jul 1999 09:58:54 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA29355 for ; Tue, 20 Jul 1999 09:58:53 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA14366; Tue, 20 Jul 1999 09:58:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA22430; Tue, 20 Jul 1999 09:58:16 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA13554 for ; Tue, 20 Jul 1999 09:52:32 -0700 Received: from mercury.uwe.ac.uk (kerberos.uwe.ac.uk [164.11.135.10]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA29149 for ; Tue, 20 Jul 1999 09:52:31 -0700 Received: from zeus.uwe.ac.uk (zeus [164.11.89.2]) by mercury.uwe.ac.uk (2.0.4/SMS 2.0.4-devel) with SMTP id RAA08977 for ; Tue, 20 Jul 1999 17:52:30 +0100 (BST) Message-Id: Date: Tue, 20 Jul 1999 17:52:30 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: C A MITCHELL To: Pine Discussion Forum Subject: Viewing URLs from within Pine (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Further to Skrikanth Vallabhaneni's message to Pine, I wonder whether anyone can give any clues on using pine, or any computing package, calmly & relaxed! Carol Mitchell ca-mitchell@uwe.ac.uk ---------- Forwarded message ---------- Date: Wed, 14 Jul 1999 20:47:24 +0530 (IST) From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Viewing URLs from within Pine Hi all, I use Pine V4.10 for Solaris and I have a query on viewing URLs from within Pine. My Pine is configured for both Netscape and Lynx as url-viewers and they both work fine. I would like to know if there is a way by which, I can toggle between the choice of browsers with a hot-key rather than manually editing the application, everytime I switch browsers. I find it much faster to view text-based articles with Lynx than Netscape. If there is no direct way of doing this in V4.10, I think it would be a pretty nifty feature to have in later releases. -- Thanks, Srikanth -- ----------------------------------------------------------------- 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; Tue, 20 Jul 1999 10:14:09 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA29967 for ; Tue, 20 Jul 1999 10:14:08 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA13609; Tue, 20 Jul 1999 10:14:06 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA07360; Tue, 20 Jul 1999 10:13:16 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA37680 for ; Tue, 20 Jul 1999 10:09:56 -0700 Received: from ntcorp.dn.net (ntcorp.dn.net [207.226.172.79]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA26739 for ; Tue, 20 Jul 1999 10:09:56 -0700 Received: from localhost (fidelman@localhost) by ntcorp.dn.net (8.8.7/8.8.7) with ESMTP id NAA15988 for ; Tue, 20 Jul 1999 13:02:10 -0400 (EDT) Message-Id: Date: Tue, 20 Jul 1999 13:02:10 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Miles Fidelman To: Pine Discussion Forum Subject: how does pine recognize a URL? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: fidelman@ntcorp.dn.net X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I've noticed that pine sometimes makes a URL clickable, and sometimes doesn't. What rules does pine follow to recognize a URL inside a text message? ************************************************************************** The Center for Civic Networking PO Box 600618 Miles R. Fidelman, President & Newtonville, MA 02460-0006 Director, Municipal Telecommunications Strategies Program 617-558-3698 fax: 617-630-8946 mfidelman@civicnet.org http://civic.net/ccn.html Information Infrastructure: Public Spaces for the 21st Century Let's Start With: Internet Wall-Plugs Everywhere Say It Often, Say It Loud: "I Want My Internet!" ************************************************************************** -- ----------------------------------------------------------------- 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, 20 Jul 1999 10:41:41 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA30457 for ; Tue, 20 Jul 1999 10:41:40 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA14446; Tue, 20 Jul 1999 10:41:38 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA24275; Tue, 20 Jul 1999 10:41:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA23142 for ; Tue, 20 Jul 1999 10:37:58 -0700 Received: from bom2.vsnl.net.in (bom2.vsnl.net.in [202.54.1.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id KAA29633 for ; Tue, 20 Jul 1999 10:37:14 -0700 Received: from localhost (PPP3-27.bom.vsnl.net.in [202.54.3.27]) by bom2.vsnl.net.in (8.9.1/8.9.1) with ESMTP id XAA05739; Tue, 20 Jul 1999 23:07:07 +0530 (IST) Received: from localhost (satyap@localhost) by localhost (8.8.7/8.8.7) with ESMTP id XAA00699; Tue, 20 Jul 1999 23:07:32 +0530 Message-Id: Date: Tue, 20 Jul 1999 23:07:31 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Satya To: Pine Discussion Forum Subject: Re: Viewing URLs from within Pine (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: C A MITCHELL X-Cc: Pine Discussion Forum X-Authentication-Warning: hal9k.org: satyap owned process doing -bs X-Sender: satyap@hal9k.org X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 20 Jul 1999, C A MITCHELL wrote: > Further to Skrikanth Vallabhaneni's message to Pine, I wonder whether > anyone can give any clues on using pine, or any computing package, > calmly & relaxed! The best answer that I can come up with is: Read The Documentation :) -- Satya. Freelance website designer and CGI/Perl programmer. http://satyaonline.cjb.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, 20 Jul 1999 10:49:36 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id KAA30595 for ; Tue, 20 Jul 1999 10:49:35 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id KAA14675; Tue, 20 Jul 1999 10:49:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id KAA27217; Tue, 20 Jul 1999 10:49:03 -0700 Received: from jason05.u.washington.edu (root@jason05.u.washington.edu [140.142.78.6]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA27158 for ; Tue, 20 Jul 1999 10:45:51 -0700 Received: from dante16.u.washington.edu (leibrand@dante16.u.washington.edu [140.142.15.42]) by jason05.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA18396 for ; Tue, 20 Jul 1999 10:45:49 -0700 Received: from localhost (leibrand@localhost) by dante16.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id KAA37854 for ; Tue, 20 Jul 1999 10:45:48 -0700 Message-Id: Date: Tue, 20 Jul 1999 10:45:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: how does pine recognize a URL? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN It looks like it goes by how the URL starts (of course, it has other logic to determine the end of the URL). If it starts with http://something or ftp://something it should be clickable (as these nonsense examples probably are). Also, you can optionally have Pine try to find URLs that don't have the http:// or ftp:// by enabling: FEATURE: enable-msg-view-web-hostnames This feature modifies the behavior of Pine's MESSAGE TEXT screen. Setting this feature causes Pine to select possible web hostnames from the displayed text and display them in boldface for selection. This can be useful when you receive messages referencing World Wide Web sites without the use of complete URLs; for example, specifying only "www.washington.edu/pine/" (which will not become a selectable item by setting "enable-msg-view-urls") rather than explicitly "http://www.washington.edu/pine/". Does that answer your question? -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Tue, 20 Jul 1999, Miles Fidelman wrote: > I've noticed that pine sometimes makes a URL clickable, and sometimes > doesn't. What rules does pine follow to recognize a URL inside a text > message? > 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, 20 Jul 1999 17:37:02 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id RAA06391 for ; Tue, 20 Jul 1999 17:37:01 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA25402; Tue, 20 Jul 1999 17:36:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA06837; Tue, 20 Jul 1999 17:36:45 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA19620 for ; Tue, 20 Jul 1999 17:33:24 -0700 Received: from ns1.cdc.com (ns1.cdc.com [150.143.16.2]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id RAA24506 for ; Tue, 20 Jul 1999 17:33:23 -0700 Received: from [129.179.17.10] by ns1.cdc.com with ESMTP for pine-info@u.washington.edu; Tue, 20 Jul 1999 19:32:18 -0500 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Wed, 21 Jul 1999 08:31:32 +0800 Message-Id: <001901bed310$53058240$1511b381@twntpe.cdc.com> Date: Wed, 21 Jul 1999 08:31:07 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Viewing URLs from within Pine (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Satya" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Satya, > On Tue, 20 Jul 1999, C A MITCHELL wrote: > > > Further to Skrikanth Vallabhaneni's message to Pine, I wonder whether > > anyone can give any clues on using pine, or any computing package, > > calmly & relaxed! > > The best answer that I can come up with is: Read The Documentation :) I beg to differ. I've found the key to using pine, or any computing package, in a calm and relaxed manner is to have a glass (or bottle) of fine tawny port on hand. Further, to ensure the relaxed mood one should commence with a sipping action 30 minutes prior to interaction with any computer. Regards, Ed P.S. The above is not encouraged for minors, pregnant women, or anyone planning to operate a motor vehicle. 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, 22 Jul 1999 09:34:23 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA16412 for ; Thu, 22 Jul 1999 09:34:22 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA06411; Thu, 22 Jul 1999 09:34:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA23442; Thu, 22 Jul 1999 09:33:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA30608 for ; Thu, 22 Jul 1999 09:27:56 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA30153 for ; Thu, 22 Jul 1999 09:27:56 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA15612 for ; Thu, 22 Jul 1999 09:27:55 -0700 (PDT) Message-Id: Date: Thu, 22 Jul 1999 09:27:52 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: new mail MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it possible to have the imap server to write an environment variable thet lets you know about new mail. My idea is that instead of using a program to check for new mail, I would like the server to tell me when this happens, so that I do not waste time doing this. In this form, any program could have access to the variable and make a check for new mail. Thanks, Eduardo http://www.math.washington.edu/~chappa/personal.html -- ----------------------------------------------------------------- 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, 23 Jul 1999 15:56:23 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA17336 for ; Fri, 23 Jul 1999 15:56:22 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA13378; Fri, 23 Jul 1999 15:56:20 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA16166; Fri, 23 Jul 1999 15:56:04 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA33310 for ; Fri, 23 Jul 1999 15:52:10 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id PAA01579 for ; Fri, 23 Jul 1999 15:52:10 -0700 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 PAA25054 for ; Fri, 23 Jul 1999 15:52:05 -0700 (PDT) Received: from l2122.usc.edu by Law.USC.EDU (4.1/SMI-4.1) id AA29146; Fri, 23 Jul 1999 15:52:05 PDT Message-Id: Date: Fri, 23 Jul 1999 15:52:13 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: pine vs. PC-Pine Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi all, I was wondering what the main differences are between a telnet session and PC-Pine with regards to resolving hostnames. The reason I ask is that whenever our university's DNS servers go down or have a broadcast storm or whatever, I can telnet in to my server and use regular Pine, but I can't use PC-Pine. (error 10021 - can't get [hostname] , or something like that - it's working now so I can't recreate the error) Is PC-Pine or imap more reliant on DNS than a telnet session? If so, how does this work? Thanks for any info. (My boss' boss wants to know :) My system: Win98 Pentium III/450 Netterm (our telnet program) PC-Pine 4.10 My server: SunOS 4.1.x (Solaris 1.x) Pine 3.96 imap 3.x ``````````````````````````````````````````````````````````````````````` ` 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; Fri, 23 Jul 1999 16:22:54 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA17387 for ; Fri, 23 Jul 1999 16:22:52 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA12213; Fri, 23 Jul 1999 16:22:51 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA29399; Fri, 23 Jul 1999 16:22:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA19488 for ; Fri, 23 Jul 1999 16:19:22 -0700 Received: from nimbus.anzio.com (IDENT:bezell@nimbus.anzio.com [204.201.253.34]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA19888 for ; Fri, 23 Jul 1999 16:19:22 -0700 Received: from localhost (bezell@localhost) by nimbus.anzio.com (8.8.7/8.8.7) with ESMTP id QAA09299; Fri, 23 Jul 1999 16:21:56 -0700 Message-Id: Date: Fri, 23 Jul 1999 16:21:56 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Bobby Ezell To: Pine Discussion Forum Subject: Re: pine vs. PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How are you attaching over telnet? If you are connecting by IP address rather than name that will be the big difference. If the Pine on UNIX is on your mail server, it does not need DNS (it may be using a local hosts file or ....). Usually imap and pop services are dependent on a name such as "mail" (I don't even know if you can set your PC-Pine to work with IP addresses, and I don't know if your particular host daemons will work that way, but you might try). Bobby Ezell Rasmussen Software, Inc. On Fri, 23 Jul 1999, Robert Larmon wrote: > > Hi all, > I was wondering what the main differences are between a telnet > session and PC-Pine with regards to resolving hostnames. The reason I ask > is that whenever our university's DNS servers go down or have a broadcast > storm or whatever, I can telnet in to my server and use regular Pine, but > I can't use PC-Pine. (error 10021 - can't get [hostname] , or something > like that - it's working now so I can't recreate the error) Is PC-Pine or > imap more reliant on DNS than a telnet session? If so, how does this > work? Thanks for any info. (My boss' boss wants to know :) > > My system: > > Win98 > Pentium III/450 > Netterm (our telnet program) > PC-Pine 4.10 > > My server: > > SunOS 4.1.x (Solaris 1.x) > Pine 3.96 > imap 3.x > > > ``````````````````````````````````````````````````````````````````````` > ` 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/ > ----------------------------------------------------------------- > ------------------------------------------------------------------- Bobby Ezell E-Mail: bezell@anzio.com Technical Sales Support V-Mail: 503-624-0360 (voice) Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com Portland, OR 97223 http://www.anzio.com/~bezell ------------------------------------------------------------------- AnzioLite and AnzioWin for all your telnet needs Send sales & support questions to: rsi@anzio.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; Fri, 23 Jul 1999 18:46:02 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id SAA19372 for ; Fri, 23 Jul 1999 18:46:01 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id SAA16648; Fri, 23 Jul 1999 18:45:59 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id SAA28741; Fri, 23 Jul 1999 18:45:46 -0700 Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA47636 for ; Fri, 23 Jul 1999 18:42:23 -0700 Received: from homer24.u.washington.edu (sleib@homer24.u.washington.edu [140.142.78.14]) by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA10290 for ; Fri, 23 Jul 1999 18:42:22 -0700 Received: from localhost (sleib@localhost) by homer24.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id SAA135062 for ; Fri, 23 Jul 1999 18:42:22 -0700 Message-Id: Date: Fri, 23 Jul 1999 18:42:21 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: pine vs. PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Sender: sleib@homer24.u.washington.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Even if PC-Pine doesn't support IPs, you can make Windows resolve names on its own. What I do, for example, is put a line like: 140.142.x.x something.u.washington.edu in my c:\windows\hosts file. (Of course, x's aren't valid in actual IP addresses.) That way you don't need a DNS to look up your mail servers. Of course, this would be good only if your mail server's IP never changes. And also, this would only help if your DNS server went down. In your case, that might not be happening, since you can still telnet out. -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Fri, 23 Jul 1999, Bobby Ezell wrote: > > How are you attaching over telnet? If you are connecting by IP address > rather than name that will be the big difference. If the Pine on UNIX is > on your mail server, it does not need DNS (it may be using a local hosts > file or ....). Usually imap and pop services are dependent on a name such > as "mail" (I don't even know if you can set your PC-Pine to work with IP > addresses, and I don't know if your particular host daemons will work that > way, but you might try). > > Bobby Ezell > Rasmussen Software, Inc. > > On Fri, 23 Jul 1999, Robert Larmon wrote: > > > > > Hi all, > > I was wondering what the main differences are between a telnet > > session and PC-Pine with regards to resolving hostnames. The reason I ask > > is that whenever our university's DNS servers go down or have a broadcast > > storm or whatever, I can telnet in to my server and use regular Pine, but > > I can't use PC-Pine. (error 10021 - can't get [hostname] , or something > > like that - it's working now so I can't recreate the error) Is PC-Pine or > > imap more reliant on DNS than a telnet session? If so, how does this > > work? Thanks for any info. (My boss' boss wants to know :) > > > > My system: > > > > Win98 > > Pentium III/450 > > Netterm (our telnet program) > > PC-Pine 4.10 > > > > My server: > > > > SunOS 4.1.x (Solaris 1.x) > > Pine 3.96 > > imap 3.x > > > > > > ``````````````````````````````````````````````````````````````````````` > > ` 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/ > > ----------------------------------------------------------------- > > > > ------------------------------------------------------------------- > Bobby Ezell E-Mail: bezell@anzio.com > Technical Sales Support V-Mail: 503-624-0360 (voice) > Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) > 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com > Portland, OR 97223 http://www.anzio.com/~bezell > ------------------------------------------------------------------- > AnzioLite and AnzioWin for all your telnet needs > Send sales & support questions to: rsi@anzio.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; Sat, 24 Jul 1999 23:34:58 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id XAA04523 for ; Sat, 24 Jul 1999 23:34:57 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id XAA06414; Sat, 24 Jul 1999 23:34:54 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA23559; Sat, 24 Jul 1999 23:33:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id XAA53150 for ; Sat, 24 Jul 1999 23:29:21 -0700 Received: from lacebark.ntu.edu.au (lacebark.ntu.edu.au [138.80.63.12]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id XAA24969 for ; Sat, 24 Jul 1999 23:29:19 -0700 Received: (qmail 18398 invoked by uid 200); 25 Jul 1999 15:46:29 +1100 Message-Id: <19990725154629.A21179@lacebark.ntu.edu.au> Date: Sun, 25 Jul 1999 15:46:29 +1100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Salter-Duke To: Pine Discussion Forum Subject: Attaching html files. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In the archives for earlier this month there is a discussion about attaching html files which came out as text/plain not text/html. It ended when the original author said that pine -d 9 had showed him that it was reading the wrong .mime.types file. I think it is a real problem. Here is a bit out of the debug file:- It searches down my .mime.types file until- traverse: buffer="image/x-xwindowdump xwd " typespec="image/x-xwindowdump" traverse: trying ext "xwd" traverse: buffer="text/html html " typespec="text/html" traverse: trying ext "html" traverse: type=text, subtype=html. busy_alarm(1, Busy, 0, 0) cancel_busy_alarm(-1) q_status_message(File /home/ruth/index.html attached as t) fix_windsize() new win size -----<24 80>------ output_message(File /home/ruth/index.html attached as type TEXT/PLAIN) STATUS cmd:120, max:3, min0 This tells me that it found it was text/html but then promptly ignored this and made it text/plain. Is this correct? It certainly gets attached as text/plain. It seems to me that this accurs for all text files. E.g. I have "application/msword doc" in .mime.types. A proper MSWord *.doc file gets sent as application/msword, but a text file I just rename as *.doc gets sent as text/plain. Is there a way for forcing .mime.types file behaviour and no other behaviour? The guessing of behaviour is fine if the user has no .mime.types file, but is otherwise unacceptable. Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) Chemistry, Faculty of Science, IT and Education, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 b_duke@lacebark.ntu.edu.au http://www.smps.ntu.edu.au/chemistry/compchem.html -- ----------------------------------------------------------------- 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, 25 Jul 1999 04:43:38 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id EAA12019 for ; Sun, 25 Jul 1999 04:43:37 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id EAA10696; Sun, 25 Jul 1999 04:43:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id EAA25850; Sun, 25 Jul 1999 04:42:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id EAA33022 for ; Sun, 25 Jul 1999 04:38:47 -0700 Received: from vada.cisco.com (vada.cisco.com [192.122.173.18]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id EAA16019 for ; Sun, 25 Jul 1999 04:38:45 -0700 Received: from localhost (vvsri@localhost) by vada.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id RAA14367; Sun, 25 Jul 1999 17:07:02 +0530 (IST) Message-Id: Date: Sun, 25 Jul 1999 17:07:02 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Srikanth V. Vallabhaneni" To: Pine Discussion Forum Subject: Re: Attaching html files. In-Reply-To: <19990725154629.A21179@lacebark.ntu.edu.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Brian Salter-Duke X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Brian, I faced a similar problem with the attachments but then it turned out that my mimetype-search-path wasn't properly set. I suspect you've the same problem. Here's a bit out of my debug file: Debug output of the Pine program (debug=9 debug_imap=4). Version 4.10 Sun Jul 25 14:19:13 1999 mt_get_file_ext : filename="/users/vvsri/index.html", extension="html" - mt_srch_mime_type - mime_types: path: /users/vvsri/mime.types traverse: buffer="TEXT/HTML html htm" typespec="TEXT/HTML" traverse: trying ext "html" traverse: type=TEXT, subtype=HTML. q_status_message(File /users/vvsri/index.html attach) fix_windsize() new win size -----<24 80>------ output_message(File /users/vvsri/index.html attached as type TEXT/HTML) STATUS cmd:120, max:3, min0 Note the mime_types:path field. I don't see that specified in your debug output (or has been deleted). So, make sure you have it right. If you have specified the mimetype-search-path, then pine will look up the mime.types file (or whatever filename's been specified at the path) and treat the attachment accordingly. This is what I have in my mime-types file: TEXT/HTML html htm IMAGE/GIF gif IMAGE/JPEG jpeg jpg Hope this helps.. -Srikanth On Sun, 25 Jul 1999 at 3:46pm +1100, Brian Salter-Duke said: > In the archives for earlier this month there is a discussion about > attaching html files which came out as text/plain not text/html. It > ended when the original author said that pine -d 9 had showed him > that it was reading the wrong .mime.types file. I think it is a > real problem. Here is a bit out of the debug file:- > > It searches down my .mime.types file until- > > traverse: buffer="image/x-xwindowdump xwd " > typespec="image/x-xwindowdump" > traverse: trying ext "xwd" > traverse: buffer="text/html html " > typespec="text/html" > traverse: trying ext "html" > traverse: type=text, subtype=html. > busy_alarm(1, Busy, 0, 0) > cancel_busy_alarm(-1) > q_status_message(File /home/ruth/index.html attached as t) > fix_windsize() > new win size -----<24 80>------ > output_message(File /home/ruth/index.html attached as type TEXT/PLAIN) > STATUS cmd:120, max:3, min0 > > This tells me that it found it was text/html but then promptly ignored > this and made it text/plain. Is this correct? It certainly gets attached > as text/plain. > > It seems to me that this accurs for all text files. E.g. I have > "application/msword doc" in .mime.types. A proper MSWord *.doc > file gets sent as application/msword, but a text file I just rename as > *.doc gets sent as text/plain. > > Is there a way for forcing .mime.types file behaviour and no other > behaviour? The guessing of behaviour is fine if the user has no > .mime.types file, but is otherwise unacceptable. > > Cheers, Brian. > 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, 25 Jul 1999 19:51:34 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA05525 for ; Sun, 25 Jul 1999 19:51:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA22577; Sun, 25 Jul 1999 19:51:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA04029; Sun, 25 Jul 1999 19:51:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA31360 for ; Sun, 25 Jul 1999 19:47:52 -0700 Received: from lacebark.ntu.edu.au (lacebark.ntu.edu.au [138.80.63.12]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id TAA04191 for ; Sun, 25 Jul 1999 19:47:49 -0700 Received: (qmail 16897 invoked by uid 200); 26 Jul 1999 12:05:02 +1100 Message-Id: <19990726120501.B12427@lacebark.ntu.edu.au> Date: Mon, 26 Jul 1999 12:05:02 +1100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Salter-Duke To: Pine Discussion Forum Subject: Re: Attaching html files. In-Reply-To: ; from Srikanth V. Vallabhaneni on Sun, Jul 25, 1999 at 05:07:02PM +0530 References: <19990725154629.A21179@lacebark.ntu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: "Srikanth V. Vallabhaneni" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi Srikanth, Thank you for your help, but I do not believe it is the answer. See below. On Sun, Jul 25, 1999 at 05:07:02PM +0530, Srikanth V. Vallabhaneni wrote: > Brian, > > I faced a similar problem with the attachments but then it turned out > that my mimetype-search-path wasn't properly set. I suspect you've the > same problem. Here's a bit out of my debug file: > > Debug output of the Pine program (debug=9 debug_imap=4). Version 4.10 > Sun Jul 25 14:19:13 1999 > > > > mt_get_file_ext : filename="/users/vvsri/index.html", extension="html" > - mt_srch_mime_type - > mime_types: path: /users/vvsri/mime.types > traverse: buffer="TEXT/HTML html htm" > typespec="TEXT/HTML" > traverse: trying ext "html" > traverse: type=TEXT, subtype=HTML. You have TEXT/HTML as the first entry in mime.types so it finds it straight away. My situation is slightly different. > q_status_message(File /users/vvsri/index.html attach) > fix_windsize() > new win size -----<24 80>------ > output_message(File /users/vvsri/index.html attached as type TEXT/HTML) > STATUS cmd:120, max:3, min0 > > > > Note the mime_types:path field. I don't see that specified in your debug > output (or has been deleted). So, make sure you have it right. If you > have specified the mimetype-search-path, then pine will look up the > mime.types file (or whatever filename's been specified at the path) and > treat the attachment accordingly. My mime.types file is quite long and it is specified in the debug file alomg with its search through it. > This is what I have in my mime-types file: > TEXT/HTML html htm > IMAGE/GIF gif > IMAGE/JPEG jpeg jpg > > Hope this helps.. > > -Srikanth > > > On Sun, 25 Jul 1999 at 3:46pm +1100, Brian Salter-Duke said: > > > In the archives for earlier this month there is a discussion about > > attaching html files which came out as text/plain not text/html. It > > ended when the original author said that pine -d 9 had showed him > > that it was reading the wrong .mime.types file. I think it is a > > real problem. Here is a bit out of the debug file:- > > > > It searches down my .mime.types file until- > > It searches through many entries in mime.types so I deleted everything down to the one before text/html. > > traverse: buffer="image/x-xwindowdump xwd " > > typespec="image/x-xwindowdump" > > traverse: trying ext "xwd" > > traverse: buffer="text/html html " > > typespec="text/html" > > traverse: trying ext "html" > > traverse: type=text, subtype=html. OK. It has found the html extension as text/html. > > busy_alarm(1, Busy, 0, 0) > > cancel_busy_alarm(-1) > > q_status_message(File /home/ruth/index.html attached as t) The t at the end may be the problem. For one it gets right such as postscript there is txt in place of t. > > fix_windsize() > > new win size -----<24 80>------ > > output_message(File /home/ruth/index.html attached as type TEXT/PLAIN) Here it ignores what it found and uses text/plain. I think there is a problem here and it is not that it can not find my mime.types file. > > STATUS cmd:120, max:3, min0 > > > > This tells me that it found it was text/html but then promptly ignored > > this and made it text/plain. Is this correct? It certainly gets attached > > as text/plain. > > > > It seems to me that this accurs for all text files. E.g. I have > > "application/msword doc" in .mime.types. A proper MSWord *.doc > > file gets sent as application/msword, but a text file I just rename as > > *.doc gets sent as text/plain. > > > > Is there a way for forcing .mime.types file behaviour and no other > > behaviour? The guessing of behaviour is fine if the user has no > > .mime.types file, but is otherwise unacceptable. > > Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) Chemistry, Faculty of Science, IT and Education, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 b_duke@lacebark.ntu.edu.au http://www.smps.ntu.edu.au/chemistry/compchem.html 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, 26 Jul 1999 09:22:10 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA17927 for ; Mon, 26 Jul 1999 09:22:09 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA03013; Mon, 26 Jul 1999 09:22:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA28287; Mon, 26 Jul 1999 09:21:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA60064 for ; Mon, 26 Jul 1999 09:16:49 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA30167 for ; Mon, 26 Jul 1999 09:16:49 -0700 Received: from goedel3.math.washington.edu (chappa@goedel3.math.washington.edu [128.95.224.12]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id JAA19202 for ; Mon, 26 Jul 1999 09:16:48 -0700 (PDT) Message-Id: Date: Mon, 26 Jul 1999 09:16:42 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Problem attaching files of type Text/HTML In-Reply-To: <932900717.626.40@news.remarQ.com> References: <932900717.626.40@news.remarQ.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello The problem about attachments of HTML files has been a topic of discussion both in the pine-info list as in comp.mail.pine. The following message appeared in comp.mail.pine. I tried the patch suggested there and it worked! In my case uname -a says OSF1 goedel3 V4.0 878 alpha Thanks for the patch, it certainly did solve this problem for me. Eduardo http://www.math.washington.edu/~chappa/personal.html *** Jeremy Blackman (loki@maison-otaku.net) wrote on Jul 25, 1999: :)> I reported the same problem a few weeks ago, I received a message :)> from the pine team asking me for my .pine-debug files, and they :)> answered me that this one was a difficult one, they hadn't catch it :)> yet. Up to the moment no one has answered me why this occurs, if :)> someone lets you know, please let me know. I myself tried several :)> ways to change the headers, and could not do it. :) :) :) Hey, wait, me and one other person not only tracked this down but :) SUBMITTED A FIX several weeks ago. :) :) It's not, technically speaking, a bug in PINE. It is a bug in :) egcs/gcc, where in one particular case, an optimization causes a :) return result from one of the MIME handler routines to get utterly :) clobbered. (This is probably also why it does BASE64 encoding when :) quoted-printable would be more appropriate, but we didn't bother to :) try debugging that one. Step-debugging PINE for one bug is pain :) enough, thank you.) :) :) I know for a fact that this bug affects x86 versions of egcs/gcc :) after 2.7.2 (because I tried it on a variety of machines), and I've :) been told by someone that the Alpha architecture also has this :) problem. (The bug was submitted to the egcs/gcc team, as well.) :) The bug causes the return to contain a '0', no matter what the :) actual return result was, when the program returns to the calling :) function - this causes PINE to assume certain (incorrect) defaults. :) :) With a simple alteration to that particular routine in PINE to force :) egcs/gcc to be unable to optimize that one step (e.g. add :) 'sleep(0);' before the return), PINE correctly attaches things :) again. This particular bug affects several MIME types, text/html is :) merely the most noticable. :) :) The patch in question can be found at: :) ftp://ftp.listar.org/pub/listar/other/pine4.10-mimetype.patch :) :) (The bug was discovered while working on the MIME handling for the :) Listar mailing list package, hence the location of the patch. :) There's also a patch to add minimal RFC2369 support to PINE in that :) same directory, as pine4.10-listserv.patch) :) :) Hope that helps! :) :) :) :) 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, 26 Jul 1999 09:25:29 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA18003 for ; Mon, 26 Jul 1999 09:25:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA01527; Mon, 26 Jul 1999 09:25:26 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA28502; Mon, 26 Jul 1999 09:25:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA25464 for ; Mon, 26 Jul 1999 09:20:44 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA21423 for ; Mon, 26 Jul 1999 09:20:43 -0700 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 JAA13906; Mon, 26 Jul 1999 09:20:42 -0700 (PDT) Received: from l2122.usc.edu by Law.USC.EDU (4.1/SMI-4.1) id AA02371; Mon, 26 Jul 1999 09:20:41 PDT Message-Id: Date: Mon, 26 Jul 1999 09:20:31 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: Re: pine vs. PC-Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bobby Ezell X-Cc: Pine Discussion Forum X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN We use hostnames for PC-Pine and Telnet. It just seems odd that telnet would work where PC-Pine wouldn't. I wonder if this is an imap behavior. (Well, as soon as we upgrade to imap 4 we may notice a difference) Oh well, it's a moot question if the university can keep their nose clean :) Thanks, Robert On Fri, 23 Jul 1999, Bobby Ezell wrote: > > How are you attaching over telnet? If you are connecting by IP address > rather than name that will be the big difference. If the Pine on UNIX is > on your mail server, it does not need DNS (it may be using a local hosts > file or ....). Usually imap and pop services are dependent on a name such > as "mail" (I don't even know if you can set your PC-Pine to work with IP > addresses, and I don't know if your particular host daemons will work that > way, but you might try). > > Bobby Ezell > Rasmussen Software, Inc. > > On Fri, 23 Jul 1999, Robert Larmon wrote: > > > > > Hi all, > > I was wondering what the main differences are between a telnet > > session and PC-Pine with regards to resolving hostnames. The reason I ask > > is that whenever our university's DNS servers go down or have a broadcast > > storm or whatever, I can telnet in to my server and use regular Pine, but > > I can't use PC-Pine. (error 10021 - can't get [hostname] , or something > > like that - it's working now so I can't recreate the error) Is PC-Pine or > > imap more reliant on DNS than a telnet session? If so, how does this > > work? Thanks for any info. (My boss' boss wants to know :) > > > > My system: > > > > Win98 > > Pentium III/450 > > Netterm (our telnet program) > > PC-Pine 4.10 > > > > My server: > > > > SunOS 4.1.x (Solaris 1.x) > > Pine 3.96 > > imap 3.x > > > > > > ``````````````````````````````````````````````````````````````````````` > > ` 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/ > > ----------------------------------------------------------------- > > > > ------------------------------------------------------------------- > Bobby Ezell E-Mail: bezell@anzio.com > Technical Sales Support V-Mail: 503-624-0360 (voice) > Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) > 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com > Portland, OR 97223 http://www.anzio.com/~bezell > ------------------------------------------------------------------- > AnzioLite and AnzioWin for all your telnet needs > Send sales & support questions to: rsi@anzio.com > =================================================================== > ``````````````````````````````````````````````````````````````````````` ` 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, 26 Jul 1999 09:33:35 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id JAA18229 for ; Mon, 26 Jul 1999 09:33:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id JAA03306; Mon, 26 Jul 1999 09:33:32 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id JAA18171; Mon, 26 Jul 1999 09:33:11 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id JAA60002 for ; Mon, 26 Jul 1999 09:30:10 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id JAA06346; Mon, 26 Jul 1999 09:30:09 -0700 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 JAA16710; Mon, 26 Jul 1999 09:30:08 -0700 (PDT) Received: from l2122.usc.edu by Law.USC.EDU (4.1/SMI-4.1) id AA02446; Mon, 26 Jul 1999 09:30:07 PDT Message-Id: Date: Mon, 26 Jul 1999 09:29:56 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Robert Larmon To: Pine Discussion Forum Subject: Re: pine vs. PC-Pine In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Scott Leibrand X-Cc: Pine Discussion Forum X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I would not necessarily recommend using a hosts file on PCs, unless you modify it often. Some program installed a hosts file on my PC, unknown to me, and my browser couldn't find certain sites after they updated the ip address (especially Symantec and Sun education). I didn't even know that this was an option, but once I read MS's site for a few hours, I found a note about using the file. I deleted the file, and I could find the sites again! Anyways, I think DNS was working, but was overwhelmed with a broadcast storm. (If that's the correct terminology) Once you waited half an hour, everything was fine, but this happened two or three times over the course of two days. Somehow telnet, using hostnames, was able to get through. (maybe more quickly so it didn't time out?) I just hope it never happens again. Thanks for the tip, Robert On Fri, 23 Jul 1999, Scott Leibrand wrote: > Even if PC-Pine doesn't support IPs, you can make Windows resolve names on > its own. What I do, for example, is put a line like: > > 140.142.x.x something.u.washington.edu > > in my c:\windows\hosts file. (Of course, x's aren't valid in actual IP > addresses.) That way you don't need a DNS to look up your mail servers. > Of course, this would be good only if your mail server's IP never changes. > > And also, this would only help if your DNS server went down. In your > case, that might not be happening, since you can still telnet out. > > -- > Scott Leibrand > leibrand@u.washington.edu > How to contact me: > http://students.washington.edu/leibrand/howtocontactme.html > * RCW 19.190 notice: This email address is located in Washington State. * > * Unsolicited commercial email may be billed $500 per message. * > > > On Fri, 23 Jul 1999, Bobby Ezell wrote: > > > > > How are you attaching over telnet? If you are connecting by IP address > > rather than name that will be the big difference. If the Pine on UNIX is > > on your mail server, it does not need DNS (it may be using a local hosts > > file or ....). Usually imap and pop services are dependent on a name such > > as "mail" (I don't even know if you can set your PC-Pine to work with IP > > addresses, and I don't know if your particular host daemons will work that > > way, but you might try). > > > > Bobby Ezell > > Rasmussen Software, Inc. > > > > On Fri, 23 Jul 1999, Robert Larmon wrote: > > > > > > > > Hi all, > > > I was wondering what the main differences are between a telnet > > > session and PC-Pine with regards to resolving hostnames. The reason I ask > > > is that whenever our university's DNS servers go down or have a broadcast > > > storm or whatever, I can telnet in to my server and use regular Pine, but > > > I can't use PC-Pine. (error 10021 - can't get [hostname] , or something > > > like that - it's working now so I can't recreate the error) Is PC-Pine or > > > imap more reliant on DNS than a telnet session? If so, how does this > > > work? Thanks for any info. (My boss' boss wants to know :) > > > > > > My system: > > > > > > Win98 > > > Pentium III/450 > > > Netterm (our telnet program) > > > PC-Pine 4.10 > > > > > > My server: > > > > > > SunOS 4.1.x (Solaris 1.x) > > > Pine 3.96 > > > imap 3.x > > > > > > > > > ``````````````````````````````````````````````````````````````````````` > > > ` 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/ > > > ----------------------------------------------------------------- > > > > > > > ------------------------------------------------------------------- > > Bobby Ezell E-Mail: bezell@anzio.com > > Technical Sales Support V-Mail: 503-624-0360 (voice) > > Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) > > 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com > > Portland, OR 97223 http://www.anzio.com/~bezell > > ------------------------------------------------------------------- > > AnzioLite and AnzioWin for all your telnet needs > > Send sales & support questions to: rsi@anzio.com > > =================================================================== > > > > > ``````````````````````````````````````````````````````````````````````` ` 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, 26 Jul 1999 15:49:07 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id PAA26341 for ; Mon, 26 Jul 1999 15:49:06 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id PAA11994; Mon, 26 Jul 1999 15:49:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id PAA29368; Mon, 26 Jul 1999 15:48:44 -0700 Received: from jason04.u.washington.edu (root@jason04.u.washington.edu [140.142.78.5]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA22444 for ; Mon, 26 Jul 1999 15:45:32 -0700 Received: from dante32.u.washington.edu (leibrand@dante32.u.washington.edu [140.142.15.106]) by jason04.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA19204; Mon, 26 Jul 1999 15:45:31 -0700 Received: from localhost (leibrand@localhost) by dante32.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id PAA13100; Mon, 26 Jul 1999 15:45:30 -0700 Message-Id: Date: Mon, 26 Jul 1999 15:45:30 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Scott Leibrand To: Pine Discussion Forum Subject: Re: pine vs. PC-Pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Robert Larmon X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN What you say about hosts files is true. Don't use them unless you're aware of what they do (override your DNS server) and are prepared to change them when a site changes its IP. In my case, I only use if for a host name (dante01.u.washington.edu) that I only use when I run into network problems and can't use dante.u.washington.edu. Since that doesn't normally happen, my hosts file can't interfere with normal operation. As for the difference between Telnet and PC-Pine, I don't have a clue. :) -- Scott Leibrand leibrand@u.washington.edu How to contact me: http://students.washington.edu/leibrand/howtocontactme.html * RCW 19.190 notice: This email address is located in Washington State. * * Unsolicited commercial email may be billed $500 per message. * On Mon, 26 Jul 1999, Robert Larmon wrote: > > I would not necessarily recommend using a hosts file on PCs, unless you > modify it often. Some program installed a hosts file on my PC, unknown to > me, and my browser couldn't find certain sites after they updated the ip > address (especially Symantec and Sun education). I didn't even know that > this was an option, but once I read MS's site for a few hours, I found a > note about using the file. I deleted the file, and I could find the sites > again! > > Anyways, I think DNS was working, but was overwhelmed with a broadcast > storm. (If that's the correct terminology) Once you waited half an hour, > everything was fine, but this happened two or three times over the course > of two days. Somehow telnet, using hostnames, was able to get through. > (maybe more quickly so it didn't time out?) > > I just hope it never happens again. > > Thanks for the tip, > > Robert > > On Fri, 23 Jul 1999, Scott Leibrand wrote: > > > Even if PC-Pine doesn't support IPs, you can make Windows resolve names on > > its own. What I do, for example, is put a line like: > > > > 140.142.x.x something.u.washington.edu > > > > in my c:\windows\hosts file. (Of course, x's aren't valid in actual IP > > addresses.) That way you don't need a DNS to look up your mail servers. > > Of course, this would be good only if your mail server's IP never changes. > > > > And also, this would only help if your DNS server went down. In your > > case, that might not be happening, since you can still telnet out. > > > > -- > > Scott Leibrand > > leibrand@u.washington.edu > > How to contact me: > > http://students.washington.edu/leibrand/howtocontactme.html > > * RCW 19.190 notice: This email address is located in Washington State. * > > * Unsolicited commercial email may be billed $500 per message. * > > > > > > On Fri, 23 Jul 1999, Bobby Ezell wrote: > > > > > > > > How are you attaching over telnet? If you are connecting by IP address > > > rather than name that will be the big difference. If the Pine on UNIX is > > > on your mail server, it does not need DNS (it may be using a local hosts > > > file or ....). Usually imap and pop services are dependent on a name such > > > as "mail" (I don't even know if you can set your PC-Pine to work with IP > > > addresses, and I don't know if your particular host daemons will work that > > > way, but you might try). > > > > > > Bobby Ezell > > > Rasmussen Software, Inc. > > > > > > On Fri, 23 Jul 1999, Robert Larmon wrote: > > > > > > > > > > > Hi all, > > > > I was wondering what the main differences are between a telnet > > > > session and PC-Pine with regards to resolving hostnames. The reason I ask > > > > is that whenever our university's DNS servers go down or have a broadcast > > > > storm or whatever, I can telnet in to my server and use regular Pine, but > > > > I can't use PC-Pine. (error 10021 - can't get [hostname] , or something > > > > like that - it's working now so I can't recreate the error) Is PC-Pine or > > > > imap more reliant on DNS than a telnet session? If so, how does this > > > > work? Thanks for any info. (My boss' boss wants to know :) > > > > > > > > My system: > > > > > > > > Win98 > > > > Pentium III/450 > > > > Netterm (our telnet program) > > > > PC-Pine 4.10 > > > > > > > > My server: > > > > > > > > SunOS 4.1.x (Solaris 1.x) > > > > Pine 3.96 > > > > imap 3.x > > > > > > > > > > > > ``````````````````````````````````````````````````````````````````````` > > > > ` 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/ > > > > ----------------------------------------------------------------- > > > > > > > > > > ------------------------------------------------------------------- > > > Bobby Ezell E-Mail: bezell@anzio.com > > > Technical Sales Support V-Mail: 503-624-0360 (voice) > > > Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) > > > 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com > > > Portland, OR 97223 http://www.anzio.com/~bezell > > > ------------------------------------------------------------------- > > > AnzioLite and AnzioWin for all your telnet needs > > > Send sales & support questions to: rsi@anzio.com > > > =================================================================== > > > > > > > > > > > > ``````````````````````````````````````````````````````````````````````` > ` 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, 26 Jul 1999 19:24:38 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id TAA29388 for ; Mon, 26 Jul 1999 19:24:37 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id TAA16611; Mon, 26 Jul 1999 19:24:35 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id TAA27474; Mon, 26 Jul 1999 19:24:16 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA47740 for ; Mon, 26 Jul 1999 19:21:09 -0700 Received: from lacebark.ntu.edu.au (lacebark.ntu.edu.au [138.80.63.12]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id TAA13679 for ; Mon, 26 Jul 1999 19:21:07 -0700 Received: (qmail 16849 invoked by uid 200); 27 Jul 1999 11:38:13 +1100 Message-Id: <19990727113812.A19647@lacebark.ntu.edu.au> Date: Tue, 27 Jul 1999 11:38:12 +1100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Salter-Duke To: Pine Discussion Forum Subject: Re: Problem attaching files of type Text/HTML In-Reply-To: ; from Eduardo Chappa L. on Mon, Jul 26, 1999 at 09:16:42AM -0700 References: <932900717.626.40@news.remarQ.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: "Eduardo Chappa L." X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings Eduardo and other pine users. Thank you for the patch details. It worked! However, it does raise wider issues. The information below talks about a problem with gcc and alpha platforms. I am using a IBM RS6000 running AIX 3.2.5 and compiling with the AIX cc compiler. It looks as if this is a more general bug in version 4.10. I hope this patch fixes some related problems, but it certainly fixes the html problem. Cheers, Brian. On Mon, Jul 26, 1999 at 09:16:42AM -0700, Eduardo Chappa L. wrote: > Hello > > The problem about attachments of HTML files has been a topic of > discussion both in the pine-info list as in comp.mail.pine. The following > message appeared in comp.mail.pine. I tried the patch suggested there and > it worked! In my case uname -a says OSF1 goedel3 V4.0 878 alpha > > Thanks for the patch, it certainly did solve this problem for me. > > Eduardo > http://www.math.washington.edu/~chappa/personal.html > > > *** Jeremy Blackman (loki@maison-otaku.net) wrote on Jul 25, 1999: > > :)> I reported the same problem a few weeks ago, I received a message > :)> from the pine team asking me for my .pine-debug files, and they > :)> answered me that this one was a difficult one, they hadn't catch it > :)> yet. Up to the moment no one has answered me why this occurs, if > :)> someone lets you know, please let me know. I myself tried several > :)> ways to change the headers, and could not do it. > :) > :) > :) Hey, wait, me and one other person not only tracked this down but > :) SUBMITTED A FIX several weeks ago. > :) > :) It's not, technically speaking, a bug in PINE. It is a bug in > :) egcs/gcc, where in one particular case, an optimization causes a > :) return result from one of the MIME handler routines to get utterly > :) clobbered. (This is probably also why it does BASE64 encoding when > :) quoted-printable would be more appropriate, but we didn't bother to > :) try debugging that one. Step-debugging PINE for one bug is pain > :) enough, thank you.) > :) > :) I know for a fact that this bug affects x86 versions of egcs/gcc > :) after 2.7.2 (because I tried it on a variety of machines), and I've > :) been told by someone that the Alpha architecture also has this > :) problem. (The bug was submitted to the egcs/gcc team, as well.) > :) The bug causes the return to contain a '0', no matter what the > :) actual return result was, when the program returns to the calling > :) function - this causes PINE to assume certain (incorrect) defaults. > :) > :) With a simple alteration to that particular routine in PINE to force > :) egcs/gcc to be unable to optimize that one step (e.g. add > :) 'sleep(0);' before the return), PINE correctly attaches things > :) again. This particular bug affects several MIME types, text/html is > :) merely the most noticable. > :) > :) The patch in question can be found at: > :) ftp://ftp.listar.org/pub/listar/other/pine4.10-mimetype.patch > :) > :) (The bug was discovered while working on the MIME handling for the > :) Listar mailing list package, hence the location of the patch. > :) There's also a patch to add minimal RFC2369 support to PINE in that > :) same directory, as pine4.10-listserv.patch) > :) > :) Hope that helps! > :) > :) > :) > :) > -- Associate Professor Brian Salter-Duke (Brian Duke) Chemistry, Faculty of Science, IT and Education, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 b_duke@lacebark.ntu.edu.au http://www.smps.ntu.edu.au/school/compchem.html 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, 26 Jul 1999 21:27:08 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id VAA30584 for ; Mon, 26 Jul 1999 21:27:07 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id VAA20245; Mon, 26 Jul 1999 21:27:05 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id VAA12200; Mon, 26 Jul 1999 21:26:39 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id VAA17300 for ; Mon, 26 Jul 1999 21:23:15 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id VAA15872 for ; Mon, 26 Jul 1999 21:23:12 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id EAA03208; Tue, 27 Jul 1999 04:28:54 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Mon, 26 Jul 99 21:28 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id VAA21612; Mon, 26 Jul 1999 21:15:19 -0700 Message-Id: Date: Mon, 26 Jul 1999 21:15:16 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: Problem attaching files of type Text/HTML In-Reply-To: <19990727113812.A19647@lacebark.ntu.edu.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Brian Salter-Duke X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 27 Jul 1999, Brian Salter-Duke wrote: > Greetings Eduardo and other pine users. > > Thank you for the patch details. It worked! However, it does raise > wider issues. The information below talks about a problem with gcc > and alpha platforms. I am using a IBM RS6000 running AIX 3.2.5 > and compiling with the AIX cc compiler. It looks as if this is > a more general bug in version 4.10. I hope this patch fixes some > related problems, but it certainly fixes the html problem. This is a known problem (I believe) with GCC and EGCS (you seem to be talking about AIX cc causing a similar problem? intresting). In the recent Linux Kernel instructions it says to use gcc 2.7.2, as the 2.8 versions do ``bad things''. Unfortunately, it didn't say what these ``bad things'' are, and how to over ride them. Unfortunately other programs will not compile with gcc 2.7.2, which makes it very difficult to deal with both of these situations (and in my hunt to do this upgrade I couldn't locate EGCS, which MAY have allowed me to have that for those that need the ``modern'' compiler, while having GCC 2.7.2.1 avalable for programs that don't like the later compilers...). Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 27 Jul 1999 07:18:01 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id HAA07678 for ; Tue, 27 Jul 1999 07:17:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id HAA27134; Tue, 27 Jul 1999 07:17:56 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id HAA28162; Tue, 27 Jul 1999 07:17:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id HAA22472 for ; Tue, 27 Jul 1999 07:14:06 -0700 Received: from mm01snlnto.sandia.gov (mm01snlnto.sandia.gov [132.175.109.20]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id HAA15774 for ; Tue, 27 Jul 1999 07:14:05 -0700 Received: from 132.175.109.1 by mm01snlnto.sandia.gov with ESMTP ( WorldSecure Server SMTP Relay(WSS) v3.6); Tue, 27 Jul 99 08:14:04 -0600 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.3/8.9.3) with ESMTP id IAA16853 for ; Tue, 27 Jul 1999 08:14:03 -0600 (MDT) Message-Id: Date: Tue, 27 Jul 1999 08:14:38 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Daniel Sands" To: Pine Discussion Forum Subject: Re: compiler bugs In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Server-Uuid: 7edb479a-fd89-11d2-9a77-0090273cd58c X-WSS-ID: 1B83612647851-01-01 X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN > This is a known problem (I believe) with GCC and EGCS (you seem to > be talking about AIX cc causing a similar problem? intresting). In the > recent Linux Kernel instructions it says to use gcc 2.7.2, as the 2.8 > versions do ``bad things''. Unfortunately, it didn't say what these ``bad > things'' are, and how to over ride them. Unfortunately other programs > will not compile with gcc 2.7.2, which makes it very difficult to deal > with both of these situations (and in my hunt to do this upgrade I > couldn't locate EGCS, which MAY have allowed me to have that for those > that need the ``modern'' compiler, while having GCC 2.7.2.1 avalable for > programs that don't like the later compilers...). This is off-topic, but: EGCS can be found at egcs.cygnus.com Also, if you upgrade to the 2.2.x kernels, you can build them with the latest compilers. So I have thrown away 2.7.x already. 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, 27 Jul 1999 14:49:28 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id OAA17406 for ; Tue, 27 Jul 1999 14:49:27 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id OAA08920; Tue, 27 Jul 1999 14:49:25 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id OAA09129; Tue, 27 Jul 1999 14:48:28 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id OAA57192 for ; Tue, 27 Jul 1999 14:44:37 -0700 Received: from hotmail.com (law2-f235.hotmail.com [216.32.181.235]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id OAA18607 for ; Tue, 27 Jul 1999 14:44:37 -0700 Received: (qmail 855 invoked by uid 0); 27 Jul 1999 21:44:33 -0000 Received: from 216.99.208.182 by www.hotmail.com with HTTP; Tue, 27 Jul 1999 14:44:33 PDT Message-Id: <19990727214433.854.qmail@hotmail.com> Date: Tue, 27 Jul 1999 14:44:33 PDT Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "STEVE CONRAD" To: Pine Discussion Forum Subject: alias and sendmail.cf Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [216.99.208.182] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Dear Pine People, I used an alias file to create a distribution list to many many people. If the file has more than 6 users, it queues it but never sends. If less than 6, no problem. I ran sendmail -bv and it looks good, I ran sendmail -bm -q90m to make sure and clear the queue but it doesn't, when I run sendmail -bp their are tons of messages from the alias file sitting there. Also, can I clear the queue by mv /var/spool/mqueue /var/spool/mqueue.old and then mk /var/spool/mqueue ? I know this isnt really a pine question but we are using 3.95 on hpux 10.2 and I didn't have a better place to ask. As usual, thank you in advance. Sincerely, Steve conrad System Admin McGuire Bearing Co. _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.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; Tue, 27 Jul 1999 16:08:36 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id QAA19672 for ; Tue, 27 Jul 1999 16:08:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id QAA09526; Tue, 27 Jul 1999 16:08:33 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id QAA08070; Tue, 27 Jul 1999 16:06:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id QAA18932 for ; Tue, 27 Jul 1999 16:02:42 -0700 Received: from kootcom.kootenay.net (kootcom.kootenay.net [209.52.230.1]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id QAA27510 for ; Tue, 27 Jul 1999 16:02:42 -0700 Received: (from uucp@localhost) by kootcom.kootenay.net (8.7.5/8.7.3) id XAA28605; Tue, 27 Jul 1999 23:08:32 GMT Received: from ArmispianSystems.Rossland.bc.ca by kootcom.kootenay.net; Tue, 27 Jul 99 16:08 PDT Received: from ArmispianSystems.Rossland.bc.ca (jrasku@ArmispianSystems.Rossland.bc.ca [172.16.0.2]) by ArmispianSystems.Rossland.bc.ca (8.8.5/8.8.5) with ESMTP id PAA30074; Tue, 27 Jul 1999 15:57:59 -0700 Message-Id: Date: Tue, 27 Jul 1999 15:57:58 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Jessica Rasku To: Pine Discussion Forum Subject: Re: alias and sendmail.cf In-Reply-To: <19990727214433.854.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: STEVE CONRAD X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 27 Jul 1999, STEVE CONRAD wrote: > Dear Pine People, > > I used an alias file to create a distribution list to many many people. If > the file has more than 6 users, it queues it but never sends. If less than > 6, no problem. I ran sendmail -bv and it looks good, I ran sendmail -bm > -q90m to make sure and clear the queue but it doesn't, when I run sendmail > -bp their are tons of messages from the alias file sitting there. I don't know about what all the options youu are passing mean, so I can't really say if any of that is ``wrong'', but I wonder if it could be that when you get over 6 users, the alias is not being stored properly? Or, maybe, what is happening is it's not delivering to one (or more), of the users, so the message remains queued, even though it's delivered to all of the addresses except a few? Have you tried sending to the list that you are using directly (ie. not using the alias)? > Also, can > I clear the queue by > mv /var/spool/mqueue /var/spool/mqueue.old and then mk /var/spool/mqueue ? > I know this isnt really a pine question but we are using 3.95 on hpux 10.2 > and I didn't have a better place to ask. > As usual, thank you in advance. That would clear the queue, or if there is a specific message that is sitting there you can remove it by simply deleting it (I think there is a control file, and the message). I am not ``live'' so if I send a message to say joesmith@[123.213.12.4] it ends up not clearing my queue unfortunately. (I think I have that format correct, yes I do, now I need to clear that message. Naw, I'll just let it expire... Jessica -- Jessica Rasku, Box 270, Rossland, B.C., V0G 1Y0, (250) 362-5701, LinuxBox: (250) 362-9668. List manager: majordomo@ArmispianSystems.Rossland.bc.ca send command help ---- To get help with majordomo or lists ---- To get a list of all lists on server. WWW: 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, 27 Jul 1999 23:01:22 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id XAA24222 for ; Tue, 27 Jul 1999 23:01:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id XAA16736; Tue, 27 Jul 1999 23:01:19 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id XAA24616; Tue, 27 Jul 1999 23:00:27 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id WAA49450 for ; Tue, 27 Jul 1999 22:57:10 -0700 Received: from bru-noc.net (root@satanas.bru-noc.net [195.74.192.146]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id WAA03786 for ; Tue, 27 Jul 1999 22:57:09 -0700 Received: from satanas.bru-noc.net (satanas.bru-noc.net [195.74.192.146]) by bru-noc.net (8.9.1/8.9.1) with ESMTP id HAA01624 for ; Wed, 28 Jul 1999 07:57:08 +0200 Message-Id: Date: Wed, 28 Jul 1999 07:57:08 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Xavier To: Pine Discussion Forum Subject: Pine & PGP MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi *, Does anyone have good URLs,FAQs about integrating PGP in Pine? Tx! -- Visit: http://3276456082 | ICQ: 8398489 -- ----------------------------------------------------------------- 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, 28 Jul 1999 01:07:33 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id BAA25732 for ; Wed, 28 Jul 1999 01:07:32 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id BAA18608; Wed, 28 Jul 1999 01:07:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id BAA04886; Wed, 28 Jul 1999 01:06:41 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id BAA29138 for ; Wed, 28 Jul 1999 01:03:47 -0700 Received: from bru-cse-171.cisco.com (bru-cse-171.cisco.com [144.254.3.229]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id BAA11734 for ; Wed, 28 Jul 1999 01:03:46 -0700 Received: from localhost (gfaini@localhost) by bru-cse-171.cisco.com (8.8.5/CA/950118) with ESMTP id KAA11951 for ; Wed, 28 Jul 1999 10:03:45 +0200 (MET DST) Message-Id: Date: Wed, 28 Jul 1999 10:03:45 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Giulio Faini To: Pine Discussion Forum Subject: Kep Mappiing to access folders MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I am using Pine 4.10 on Solaris and I would like to map the function keys (F1..F12) to different folders. For example pressing F1, I want to go directly to folder INBOX, with F2 to another folder, and so on... All the time using keys '<' or '>' to move around the folders is quite stressing and also coming back to List folders page. Is that possible?? Thanks, Giulio Ps: Function keys can be accessed with an ESC sequence, something like ESC O O and I have seen also in the FAQ that I should use these settings in my ..Xdefaults: Pine*VT100.Translations: #override \n\ Delete: string(0x04) \n\ End: string(0x05) \n\ Escape: string(0x03) \n\ Home: string(0x01) \n\ Next: string(0x16) \n\ Prior: string(0x19) \n\ KP_Enter: string(0x18) \n\ -- ----------------------------------------------------------------- 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, 28 Jul 1999 02:18:07 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id CAA28426 for ; Wed, 28 Jul 1999 02:18:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id CAA19913; Wed, 28 Jul 1999 02:18:04 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id CAA27782; Wed, 28 Jul 1999 02:16:22 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA42306 for ; Wed, 28 Jul 1999 02:13:09 -0700 Received: from bru-cse-171.cisco.com (bru-cse-171.cisco.com [144.254.3.229]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA14630 for ; Wed, 28 Jul 1999 02:13:08 -0700 Received: from localhost (gfaini@localhost) by bru-cse-171.cisco.com (8.8.5/CA/950118) with ESMTP id LAA12319; Wed, 28 Jul 1999 11:13:00 +0200 (MET DST) Message-Id: Date: Wed, 28 Jul 1999 11:13:00 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Giulio Faini To: Pine Discussion Forum Subject: Re: Pine & PGP In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Xavier X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN You can try this one (bery brief), http://www.fit.qut.edu.au/~mlooi/pgppine.html Hope that helps. Giulio On Wed, 28 Jul 1999, Xavier wrote: > Hi *, > > Does anyone have good URLs,FAQs about integrating PGP in Pine? > > Tx! > > -- > Visit: http://3276456082 | ICQ: 8398489 > > -- > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > --- Giulio Faini, CSE Cisco Systems Belgium Pegasus Park De Kleetlaan 6A, b.1 1831 Diegem - Belgium Tel (direct) : +32-2-704-5190 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, 28 Jul 1999 03:04:33 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id DAA30716 for ; Wed, 28 Jul 1999 03:04:32 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id DAA20734; Wed, 28 Jul 1999 03:04:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id DAA24038; Wed, 28 Jul 1999 03:02:54 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id CAA18842 for ; Wed, 28 Jul 1999 02:59:12 -0700 Received: from ux-2s02.inf.fh-rhein-sieg.de (ux-2s02.inf.fh-rhein-sieg.de [194.95.66.3]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id CAA24758 for ; Wed, 28 Jul 1999 02:59:07 -0700 Received: from pc-2m10.inf.fh-rhein-sieg.de (pc-2m10.inf.fh-rhein-sieg.de [194.95.66.10]) by ux-2s02.inf.fh-rhein-sieg.de (8.9.1/8.9.1) with ESMTP id LAA09867 for ; Wed, 28 Jul 1999 11:58:51 +0200 (MET DST) Message-Id: Date: Wed, 28 Jul 1999 11:59:55 +0200 (CET) Reply-To: Steffen.Kaiser@fh-rhein-sieg.de Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Steffen Kaiser To: Pine Discussion Forum Subject: PC-Pine and display filter MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: skaise2a@ux-2s02.inf.fh-rhein-sieg.de X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I've tried to setup a display filter in PC-Pine v4.10. The filter is a .BAT file and is started, but PC-Pine does not wait until the filter returns. So the filter cannot do anything, in fact it always complains about that the temporary file (_TMPFILE_) does no longer exist. When I try to run the filter as filter (no temp file), PC-Pine crashs with a GPF. What am I missing? (Except for an OS.) Bye, -- Steffen Kaiser FH Rhein-Sieg | e-mail: Steffen.Kaiser@FH-Rhein-Sieg.DE FB Angewandte Informatik | Rathausallee 10 | phone : +49 2241/865-203 53757 Sankt Augustin | Germany - Deutschland | fax : +49 2241/865-761 -- ----------------------------------------------------------------- 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, 28 Jul 1999 08:16:26 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id IAA03757 for ; Wed, 28 Jul 1999 08:16:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id IAA27895; Wed, 28 Jul 1999 08:16:24 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id IAA24543; Wed, 28 Jul 1999 08:15:59 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id IAA05492 for ; Wed, 28 Jul 1999 08:12:16 -0700 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id IAA32414 for ; Wed, 28 Jul 1999 08:12:15 -0700 Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Wed Jul 28 11:10:03 EDT 1999 Received: from physics.div111.bell-labs.com ([135.3.80.4]) by grubby; Wed Jul 28 11:10:15 EDT 1999 Received: from lucent.com by physics.div111.bell-labs.com (8.9.3/TK040299) id LAA27912; Wed, 28 Jul 1999 11:02:04 -0400 (EDT) Message-Id: <379F0F4B.80257C34@lucent.com> Date: Wed, 28 Jul 1999 23:10:19 +0900 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Srinivasa SA To: Pine Discussion Forum Subject: Q: Using pine Offline with IMAP? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Accept-Language: en X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Is it possible to use pine with IMAP server for offline mail reading and replying. Specifically I am looking at a facility, similar to what is available in Netscape 4.06 and above. What I want to do is: 1. Dial a PPP account. 2. Open Pine/PC-Pine and get all the message headers from IMAP server 3. Download specific message folders for offline reading 4. Disconnect PPP connection 5. Read/answer mails, manipulate mail folders. 6. Dial my PPP account 7. Update all my mail folder changes to IMAP server/Send queued mails etc... 8. Done Can this be done in PC-Pine 4.10 ? If so, could you kind-hearted people tellme how / direct me to appropriate document? Thanks in advance. -Sas -- ----------------------------------------------------------------- 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, 28 Jul 1999 11:30:21 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA08745 for ; Wed, 28 Jul 1999 11:30:19 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA32147; Wed, 28 Jul 1999 11:30:17 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA23043; Wed, 28 Jul 1999 11:29:56 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA57760 for ; Wed, 28 Jul 1999 11:26:04 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA12993 for ; Wed, 28 Jul 1999 11:26:04 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA16404; Wed, 28 Jul 1999 11:26:01 -0700 (PDT) Message-Id: Date: Wed, 28 Jul 1999 11:26:00 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: alias and sendmail.cf In-Reply-To: <19990727214433.854.qmail@hotmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: STEVE CONRAD X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN \{fl:Hello} Steve, The way I would attack a problem like this would be to write a script that sends the mail from the your list one by one. This is easy to write, and your problem will go away. \{fl;Eduardo}\ http://www.math.washington.edu/~chappa/personal.html 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, 28 Jul 1999 11:51:50 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id LAA09269 for ; Wed, 28 Jul 1999 11:51:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id LAA00091; Wed, 28 Jul 1999 11:51:47 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id LAA12387; Wed, 28 Jul 1999 11:51:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id LAA53584 for ; Wed, 28 Jul 1999 11:48:22 -0700 Received: from euler.math.washington.edu (root@euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id LAA16589 for ; Wed, 28 Jul 1999 11:48:21 -0700 Received: from goedel2.math.washington.edu (chappa@goedel2.math.washington.edu [128.95.224.11]) by euler.math.washington.edu (8.9.3/8.9.3) with ESMTP id LAA11041; Wed, 28 Jul 1999 11:48:18 -0700 (PDT) Message-Id: Date: Wed, 28 Jul 1999 11:48:13 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "Eduardo Chappa L." To: Pine Discussion Forum Subject: Re: Q: Using pine Offline with IMAP? In-Reply-To: <379F0F4B.80257C34@lucent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Srinivasa SA X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Srinivasa SA (sas@lucent.com) wrote Today: :) Is it possible to use pine with IMAP server for offline mail reading :) and replying. Specifically I am looking at a facility, similar to what is :) available in Netscape 4.06 and above. :) :) What I want to do is: :) 1. Dial a PPP account. :) 2. Open Pine/PC-Pine and get all the message headers from IMAP server :) 3. Download specific message folders for offline reading :) 4. Disconnect PPP connection :) 5. Read/answer mails, manipulate mail folders. :) 6. Dial my PPP account :) 7. Update all my mail folder changes to IMAP server/Send queued mails etc... :) 8. Done :) I did it at least in Unix pine, and I expect the way I will describe you here will work in PC-pine also. The trick consists in changing the path of your inbox. Say in step 3. above you save messages to a folder called "download", then you could either go to your configuration and change the location of your INBOX to be the complete path of this folder or restart PINE with another .pinerc whose inbox location is the path of this folder. There you can work offline and once you are done repeat the process backwards (change your inbox again to be your old inbox location). Unfortunately there is no way (in unix pine) to do this with a few keystrokes, say, having a list of INBOXes that you can select at any time, making one of them the default, kind of choosing folder collection or printer. I think this would be useful for you and I still don't see why the pine team does not allow you such a thing. Any enlightening here would be appreciated. Have a nice day, Eduardo http://www.math.washington.edu/~chappa/personal.html 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, 28 Jul 1999 17:33:06 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id RAA16190 for ; Wed, 28 Jul 1999 17:33:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA09514; Wed, 28 Jul 1999 17:33:03 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA25273; Wed, 28 Jul 1999 17:32:43 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA40680 for ; Wed, 28 Jul 1999 17:29:19 -0700 Received: from hotmail.com (law2-f49.hotmail.com [216.32.181.49]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id RAA19211 for ; Wed, 28 Jul 1999 17:29:19 -0700 Received: (qmail 83495 invoked by uid 0); 29 Jul 1999 00:29:15 -0000 Received: from 216.99.198.67 by www.hotmail.com with HTTP; Wed, 28 Jul 1999 17:29:15 PDT Message-Id: <19990729002915.83494.qmail@hotmail.com> Date: Wed, 28 Jul 1999 17:29:15 PDT Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: "STEVE CONRAD" To: Pine Discussion Forum Subject: sendmail alias file Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-Originating-IP: [216.99.198.67] X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thank you all for your suggestions, got any more? I want to build an alias files(s) with many users in them, if I put more than 5, it stays in the queue. I made sure all the users are valid and checked syntax, sendmail even says they are deliverable with sendmail -bv. I checked that I am not forking the process in sendmail.cf. I then made an alias with an include file and have the same problem, if the include file has 5 users or less, no problem, it stays in the queue on the sixth. Thanks for your assistance, Sincerely, Steve Conrad Systems Administrator McGuire Bearing Co. _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.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, 29 Jul 1999 13:13:58 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id NAA00623 for ; Thu, 29 Jul 1999 13:13:57 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id NAA32484; Thu, 29 Jul 1999 13:13:55 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id NAA07847; Thu, 29 Jul 1999 13:13:28 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id NAA51670 for ; Thu, 29 Jul 1999 13:09:47 -0700 Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by mxu3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with ESMTP id NAA24683 for ; Thu, 29 Jul 1999 13:09:46 -0700 Received: from wilde.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-12 #29083) with ESMTP id <0FFN0045REKTI7@rfd1.oit.umass.edu> for pine-info@u.washington.edu; Thu, 29 Jul 1999 16:07:41 -0400 (EDT) Received: from localhost (dlutz@localhost) by wilde.oit.umass.edu (8.9.3/8.8.6) with ESMTP id QAA14486; Thu, 29 Jul 1999 16:07:40 -0400 (EDT) Message-Id: Date: Thu, 29 Jul 1999 16:07:38 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Dave Lutz To: Pine Discussion Forum Subject: Deleting folders: Pine 4.10 vs. Cyrus IMAP 1.5.24 MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Sender: dlutz@wilde.oit.umass.edu X-Authentication-warning: wilde.oit.umass.edu: dlutz owned process doing -bs X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Greetings, We're in the process of rolling out a new IMAP mail system based on Cyrus (currently version 1.5.24). Part of that process involves migration from Pine 3.96 to Pine 4.10. During testing of Pine 4.10 against the Cyrus server, we notice what appears to be a problem with the way Pine deletes directories on an IMAP server where the delimiter is a '.' instead of a '/' character. Problem specifics: The folder-collections option in Pine is defined to have the following collection: {servername}[] Alternatively, the following collection defintions also work, and exhibit the same problem: {servername}user.dlutz.[] or {servername}INBOX.[] With any of the above collection definitions, when I go to that collection with Pine 4.10, I can see all the subsidiary folders, I can create new folders, and I can rename existing ones without problem. However, when I try to delete a folder, the deletion fails with a "no such mailbox" error. Running Pine with -d 9 shows what it is attempting: deleting folder "GRAB2" () in context "{mail-d}user.dlutz.%s" same_stream: {mail-d}user.dlutz.GRAB2 == {mail-1.oit.umass.edu:143/imap/user=dlutz}INBOX IMAP DEBUG 10:45:06 7/29: 0000000a Delete user.dlutz.GRAB2. IMAP DEBUG 10:45:06 7/29: 0000000a NO Mailbox does not exist IMAP 10:45:06 7/29 mm_log ERROR: Mailbox does not exist q_status_message(Mailbox does not exist) q_status_message(Delete of "GRAB2" Failed!) In this particular case, I had my collection defined as: {server}user.dlutz.[] however, the failure symptoms are the same no matter if the collection is defined in any of the 3 ways listed above. There is definitely a "GRAB2" folder present, and I can delete it without problem using cyradm manually. It looks like Pine is adding an extra delimiter character ('.') to the end of the mailbox name, which causes Cyrus to fail the request. Has anyone seen this? Is it a Pine bug, or am I doing something wrong? Thanks, -David Lutz Network Analyst University of Massachusetts OIT/Network Systems and Services Amherst, MA USA 01003-4640 dlutz@nic.umass.edu voice: 413-545-9633 fax: 413-545-3203 -- ----------------------------------------------------------------- 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, 29 Jul 1999 17:41:33 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id RAA07372 for ; Thu, 29 Jul 1999 17:41:32 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id RAA05448; Thu, 29 Jul 1999 17:41:30 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id RAA27929; Thu, 29 Jul 1999 17:41:05 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA15876 for ; Thu, 29 Jul 1999 17:37:53 -0700 Received: from lacebark.ntu.edu.au (lacebark.ntu.edu.au [138.80.63.12]) by mxu2.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.06) with SMTP id RAA31064 for ; Thu, 29 Jul 1999 17:37:48 -0700 Received: (qmail 19584 invoked by uid 200); 30 Jul 1999 09:54:38 +1100 Message-Id: <19990730095437.A18534@lacebark.ntu.edu.au> Date: Fri, 30 Jul 1999 09:54:37 +1100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: Brian Salter-Duke To: Pine Discussion Forum Subject: Allowed MIME types Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine List X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN In the documentation it says that only the standard seven MIME types are allowed, but in practice it seems that one can use anything. If you invent a mime type, say foo/x-bar and put foo/x-bar bar in your mime.types file, it will send the mail as foo/x-bar. If you have an appropriate viewer for foo/x-bar in a mailcap file, it will work fine on receipt of a message in pine. Is this the expected behaviour? I see various body_types defined in c-client/rfc822.c and various other references to mime types in mailindx.c and send.c but I can not figure out whether this is expected behaviour or not. I would welcome thoughts on this topic. Cheers, Brian. -- Associate Professor Brian Salter-Duke (Brian Duke) Chemistry, Faculty of Science, IT and Education, Northern Territory University, Darwin, NT 0909, Australia. Phone 08-89466702. Fax 08-89466847 b_duke@lacebark.ntu.edu.au http://www.smps.ntu.edu.au/school/compchem.html -- ----------------------------------------------------------------- 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, 31 Jul 1999 06:43:15 -0700 (PDT) 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.06/8.9.3+UW99.01) with ESMTP id GAA06759 for ; Sat, 31 Jul 1999 06:43:14 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA09997; Sat, 31 Jul 1999 06:43:13 -0700 Received: from host (server@lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with SMTP id GAA17933; Sat, 31 Jul 1999 06:42:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id GAA31596 for ; Sat, 31 Jul 1999 06:37:02 -0700 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.06) with ESMTP id GAA27327 for ; Sat, 31 Jul 1999 06:37:02 -0700 Received: from bureau6.utcc.utoronto.ca (bureau6.utcc.utoronto.ca [128.100.132.16]) by mx2.cac.washington.edu (8.9.3+UW99.06/8.9.3+UW99.01) with ESMTP id GAA09907 for ; Sat, 31 Jul 1999 06:37:01 -0700 Received: from log3.in.utoronto.ca ([128.100.100.195] HELO log3.in.utoronto.ca ident: NO-IDENT-SERVICE [port 58545]) by bureau6.utcc.utoronto.ca with SMTP id <464202-20895>; Sat, 31 Jul 1999 09:36:58 -0400 Message-Id: Date: Sat, 31 Jul 1999 09:36:42 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk List-Help: List-Unsubscribe: List-Subscribe: List-Owner: (Human contact for the list) List-Post: From: dominic.williams@utoronto.ca To: Pine Discussion Forum Subject: addressbook MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Sender: 05810728@log3.in.utoronto.ca X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN to whom it may concern i have been having problems saving entries in my address book. I have just set up an email account with university of toronto, which uses pine and have been having problems saving entries in my address book. I have tried using the save and exit command but it does not seem to work. any advise would be greatly appreciated sincerely dominic -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ -----------------------------------------------------------------