From pinedev@shiva0.cac.washington.edu Fri Aug 1 18:03:06 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 1 Aug 2003 18:03:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72135xd016341; Fri, 1 Aug 2003 18:03:05 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72131WO004422 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Aug 2003 18:03:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7212mJ8024634; Fri, 1 Aug 2003 18:02:48 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7211j2x041212 for ; Fri, 1 Aug 2003 18:01:45 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7211i7e004202 for ; Fri, 1 Aug 2003 18:01:44 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h7211iMw106913 for ; Fri, 1 Aug 2003 18:01:44 -0700 (PDT) Message-Id: Date: Fri, 1 Aug 2003 18:01: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: Eduardo Chappa To: Pine Discussion Forum Subject: Bug or Feature: "Unverified Newsgroup Header" message is gone MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=X, Probability=10%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello, Today I received a personal message with a "Newsgroup:" header. If I had seen the same message in Pine4.53 I would have seen a warning "Unverified Newsgroup header -- Message MAY or MAY NOT have been posted" at the bottom of the screen. Pine4.56, however, did not give this warning. This contributed significantly to make my reply go to the newsgroup. In this case, no harm was done. However, I believe this is not a good thing. this change was not documented in the Release Notes of Pine. However, observe that the file "imap/docs/RELNOTES" says: Updated: 28 May 2003 imap-2002d is a minor release, released concurrently with Pine 4.56, and contains primarily bugfixes. Programs written for imap-2002 should build with this version without modification, with one exception. That exception is the ngbogus envelope flag, which stopped being used in imap-2002c and is now gone for good. The change described above caused the problem. Could the old behavior be brought back please? Thanks. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Sat Aug 2 07:26:48 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 2 Aug 2003 07:26:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72EQlxd006893; Sat, 2 Aug 2003 07:26:47 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72EQiWO024565 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 2 Aug 2003 07:26:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h72EQWJ8037720; Sat, 2 Aug 2003 07:26:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72EPR2x006958 for ; Sat, 2 Aug 2003 07:25:27 -0700 Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72EPQdL020115 for ; Sat, 2 Aug 2003 07:25:26 -0700 Received: from LITHIUM.chvlva.adelphia.net (localhost [127.0.0.1]) by ares.cs.Virginia.EDU (8.12.9/8.12.8/UVACS-2003031900) with ESMTP id h72EPML9006721 for ; Sat, 2 Aug 2003 10:25:23 -0400 (EDT) Message-Id: <0308021020590.3208@LITHIUM> Date: Sat, 2 Aug 2003 10:25:25 -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: Nicolas Christin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Eduardo, On Fri, 1 Aug 2003, Eduardo Chappa wrote: > Today I received a personal message with a "Newsgroup:" header. If I had > seen the same message in Pine4.53 I would have seen a warning > > "Unverified Newsgroup header -- Message MAY or MAY NOT have been posted" I looked at the code that generates this message when I wrote my User-Agent patch for 4.56. The test you're refering to was called as part of a relatively dirty piece of code (labeled as a kludge in the comments) in 4.55 and below. They removed the kludge, but got rid of that test as well, it seems. -- Nicolas From pinedev@shiva0.cac.washington.edu Sat Aug 2 10:59:28 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 2 Aug 2003 10:59:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72HxRxd011657; Sat, 2 Aug 2003 10:59:27 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72HxKWO029273 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 2 Aug 2003 10:59:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h72HxBKH012822; Sat, 2 Aug 2003 10:59:11 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72HwE2x059982 for ; Sat, 2 Aug 2003 10:58:14 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72Hw87e029895 for ; Sat, 2 Aug 2003 10:58:08 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h72HvcMw168373; Sat, 2 Aug 2003 10:57:38 -0700 (PDT) Message-Id: Date: Sat, 2 Aug 2003 10:57: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: Eduardo Chappa To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: <0308021020590.3208@LITHIUM> References: <0308021020590.3208@LITHIUM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nicolas Christin X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIII, Probability=5%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Nicolas Christin (nicolas@cs.Virginia.EDU) wrote in the pine-info list...: :) > Today I received a personal message with a "Newsgroup:" header. If :) > I had seen the same message in Pine4.53 I would have seen a warning :) > :) > "Unverified Newsgroup header -- Message MAY or MAY NOT have been :) > posted" :) :) I looked at the code that generates this message when I wrote my :) User-Agent patch for 4.56. The test you're refering to was called as :) part of a relatively dirty piece of code (labeled as a kludge in the :) comments) in 4.55 and below. They removed the kludge, but got rid of :) that test as well, it seems. Right, take a look at Nancy's web page and look at the link to the "comp.mail.pine fiasco". Maybe it will change your mind, or maybe not. I believe that this should not have changed, and since it changed it should have been added to the Release Notes. It was done in secrecy. Bad idea in my opinion. I believe the old behavior should be back. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Sat Aug 2 11:44:59 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 2 Aug 2003 11:44:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72Iiwxd012723; Sat, 2 Aug 2003 11:44:58 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72IitWO030260 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 2 Aug 2003 11:44:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h72IiiTB030510; Sat, 2 Aug 2003 11:44:44 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72Ii52x007066 for ; Sat, 2 Aug 2003 11:44:05 -0700 Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h72Ii4dL018629 for ; Sat, 2 Aug 2003 11:44:04 -0700 Received: from LITHIUM.chvlva.adelphia.net (localhost [127.0.0.1]) by ares.cs.Virginia.EDU (8.12.9/8.12.8/UVACS-2003031900) with ESMTP id h72IhxL9024419 for ; Sat, 2 Aug 2003 14:43:59 -0400 (EDT) Message-Id: <0308021439230.3208@LITHIUM> Date: Sat, 2 Aug 2003 14:44:02 -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: Nicolas Christin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: <0308021020590.3208@LITHIUM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Sat, 2 Aug 2003, Eduardo Chappa wrote: > *** Nicolas Christin (nicolas@cs.Virginia.EDU) wrote in the pine-info list...: > > :) > "Unverified Newsgroup header -- Message MAY or MAY NOT have been > :) > posted" > :) > :) I looked at the code that generates this message when I wrote my > :) User-Agent patch for 4.56. The test you're refering to was called as > :) part of a relatively dirty piece of code (labeled as a kludge in the > :) comments) in 4.55 and below. They removed the kludge, but got rid of > :) that test as well, it seems. > > Right, take a look at Nancy's web page and look at the link to the > "comp.mail.pine fiasco". Maybe it will change your mind, or maybe not. I think I haven't been very clear in my original post. I totally agree with you. I didn't advocate removing this piece of code, I was just saying that, judging from what I have seen while working on the User-Agent patch, the developers had gotten rid of that entire segment of code in 4.56, including the Newsgroup header test. > I believe that this should not have changed, and since it changed it > should have been added to the Release Notes. It was done in secrecy. > Bad idea in my opinion. I believe the old behavior should be back. I don't buy the conspiracy theory - presumably it was just a mistake. They had the good idea to clean up some of the code, but unfortunately ended up discarding something useful. That happens. That being said, yes, I think it should be back too. -- Nicolas From pinedev@shiva0.cac.washington.edu Sun Aug 3 23:28:29 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sun, 3 Aug 2003 23:28:29 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h746SRxd002855; Sun, 3 Aug 2003 23:28:27 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h746SOWO018924 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 3 Aug 2003 23:28:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h746RYTB025380; Sun, 3 Aug 2003 23:27:46 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h746QD2x056928 for ; Sun, 3 Aug 2003 23:26:13 -0700 Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h746QA7e014028 for ; Sun, 3 Aug 2003 23:26:11 -0700 Received: from async74-19.nas.onetel.net.uk (async74-19.nas.onetel.net.uk [212.67.115.74]) by msgdirector2.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGS77675; Mon, 4 Aug 2003 07:25:57 +0100 (BST) Message-Id: Date: Mon, 4 Aug 2003 07:26: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: Nancy McGough To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: <0308021439230.3208@LITHIUM> References: <0308021020590.3208@LITHIUM> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 2 Aug 2003 Nicolas Christin (nicolas@cs.Virginia.EDU) wrote: > > I don't buy the conspiracy theory - presumably it was just a mistake. > They had the good idea to clean up some of the code, but unfortunately > ended up discarding something useful. That happens. That being said, > yes, I think it should be back too. And added to the Pine test suite so it doesn't happen again! -- Nancy McGough Infinite Ink Writing about procmail, imap, pine, spam-deflexion strategies & more From pinedev@shiva0.cac.washington.edu Mon Aug 4 03:41:20 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 03:41:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74AfJxd010535; Mon, 4 Aug 2003 03:41:19 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74AfGof019334 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 03:41:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h74AeiOL084308; Mon, 4 Aug 2003 03:40:45 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74Adq2x052942 for ; Mon, 4 Aug 2003 03:39:52 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74AdmSC003695 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 4 Aug 2003 03:39:50 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h74AdefR022142 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 4 Aug 2003 14:39:41 +0400 (MSD) Message-Id: Date: Mon, 4 Aug 2003 14:39:35 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Translation of UTF-8 to 1-byte charset. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXF.dWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=XIIII, Probability=14%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! Imap-2002 has support for 1-byte to 1-byte character set translation. Pine has some (rather strange to me) support for japan multibyte to 1-byte translation. But I can't find support for translation of other character tables. As for me, I need UTF-8 -> KOI-8r translation. I can make a patch for UTF-8 -> (cyrillic encodings) just like it is done for japan. But adding another hack (like japan multibyte) doesn't seem a good idea to me. I'm rather new to pine source, so may be somebody has a good idea, how to implement it? Bye. Alex. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Aug 4 09:55:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 09:55:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74Gtfxd022778; Mon, 4 Aug 2003 09:55:41 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74GtZof030127 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 09:55:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h74Gt5TB029344; Mon, 4 Aug 2003 09:55:05 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74GsB2x032946 for ; Mon, 4 Aug 2003 09:54:11 -0700 Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74GsAC1012864 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 4 Aug 2003 09:54:10 -0700 Received: from localhost ([219.237.60.224]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h74Gs7WN003271 for ; Mon, 4 Aug 2003 09:54:08 -0700 Received: (qmail 6219 invoked by uid 0); 4 Aug 2003 11:23:59 -0000 Received: from unknown (HELO relay) (sm@sm.com@192.168.0.2) by soho.cd.com with SMTP; 4 Aug 2003 11:23:59 -0000 Message-Id: <200308041654.h74Gs7WN003271@mx1.cac.washington.edu> Date: Mon, 4 Aug 2003 19:22:42 +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: owner-pine-info@cac.washington.edu To: Pine Discussion Forum Subject: 一发天下应 Mime-Version: 1.0 Content-Type: text/html; charset="GB2312_CHARSET" X-Uwash-Spam: Gauge=XXXXXXXXXIIIIIII, Probability=97%, Report='__EVITE_CTYPE, __CTYPE_IS_HTML, __HAS_MSGID, __SANE_MSGID, NO_REAL_NAME, SUBJ_FULL_OF_8BITS, HEADER_8BITS, CTYPE_JUST_HTML, RCVD_IN_RFCI, HTTP_ESCAPED_HOST, MAILTO_LINK, HTML_FONT_COLOR_RED, HTML_FONT_COLOR_BLUE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN 来自邮件营销网的问候

尊敬的网友:您好!
  这是来自邮件营销网的问侯。感谢您收看这封邮件。如果此信息对您无用,请您把它删除,在此我们对您表示歉意!!
邮件营销网(www.sendmail.cn),我们将为您提供以下产品与服务:
一、80万行业邮件地址(适合于对中国境内企业进行针对性的推广宣传!)。
二、600万地区邮件地址(适合于对中国境内地区进行针对性的推广宣传!)。
三、280万精选邮件地址(适合于对中国境内个人客户进行针对性的推广宣传!)。
四、650万门户网站邮件地址(适合于对各大门户网站进行针对性的推广宣传!)。
五、1200万国内已验证邮址(适合于面向国内公司与个人的推广宣传!)。
六。提供邮件广告代发业务:http://www.sendmail.cn/shop/hotsell.asp.htm
欢迎访问邮件营销网:http://www.sendmail.cn
 咨询电话:013331012788
 电子信箱:(客户服务部)welcome@sendmail.cn welcome@263.net.cn
      (市场拓展部)welcome@sendmial.cn
welcome@263.net.cn

进入E时代,享受E生活,打造最贴近生活的公众网站,邮件营销网永远陪伴在您的身边!

      致
礼!
                                  邮件营销网

=======================================================================================
广告邮件对有用的人来说是信息,对无用人说的是垃圾。如果对您没用,我们万分抱歉!本邮件绝
对承诺只发送一次。如果您希望我们从列表中删除您的地址,请来信告诉我们您的地址。谢谢!
=======================================================================================


From pinedev@shiva0.cac.washington.edu Mon Aug 4 16:27:51 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 16:27:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NRoxd010431; Mon, 4 Aug 2003 16:27:50 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NRlWO019238 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 16:27:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h74NRIJ8041032; Mon, 4 Aug 2003 16:27:18 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NQa2x016476 for ; Mon, 4 Aug 2003 16:26:36 -0700 Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NQXrM005068 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 4 Aug 2003 16:26:34 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NQWoa005029; Mon, 4 Aug 2003 16:26:32 -0700 Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h74NQWXa016141 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Mon, 4 Aug 2003 16:26:32 -0700 Message-Id: Date: Mon, 4 Aug 2003 16:26: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: Jeff Franklin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Eduardo Chappa X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 1 Aug 2003, Eduardo Chappa wrote: > Today I received a personal message with a "Newsgroup:" header. If I had > seen the same message in Pine4.53 I would have seen a warning > > "Unverified Newsgroup header -- Message MAY or MAY NOT have been posted" > > at the bottom of the screen. Pine4.56, however, did not give this warning. > This contributed significantly to make my reply go to the newsgroup. You are correct that we did take out this behavior, and it is unfortunately something that got left off of the Release Notes. As Nicolas Christin mentioned in his response, that piece of code was based on a kludge, and we decided that that code made some rather arbitrary assumptions that don't make sense anymore. We took out the message entirely, as it seemed to us a message with very little information, and one that probably confused more people than it helped. There are still safeguards to prevent messages from accidentally getting sent out, such as the prompt to Post or Followup, and especially the "Posted message may go to thousands of readers. Really post?". Jeff From pinedev@shiva0.cac.washington.edu Mon Aug 4 17:09:50 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 17:09:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7509nxd012520; Mon, 4 Aug 2003 17:09:50 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7509iof015010 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 17:09:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7509GJ8037772; Mon, 4 Aug 2003 17:09:16 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7508e2x061794 for ; Mon, 4 Aug 2003 17:08:40 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7508ddL019821 for ; Mon, 4 Aug 2003 17:08:39 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h7508bMw330125; Mon, 4 Aug 2003 17:08:37 -0700 (PDT) Message-Id: Date: Mon, 4 Aug 2003 17:08: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: Eduardo Chappa To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff Franklin X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_05_08' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jeff Franklin (jpf@cac.washington.edu) wrote today: :) On Fri, 1 Aug 2003, Eduardo Chappa wrote: :) :) > Today I received a personal message with a "Newsgroup:" header. If :) > I had seen the same message in Pine4.53 I would have seen a warning :) > :) > "Unverified Newsgroup header -- Message MAY or MAY NOT have been :) > posted" :) > :) > at the bottom of the screen. Pine4.56, however, did not give this :) > warning. This contributed significantly to make my reply go to the :) > newsgroup. :) :) You are correct that we did take out this behavior, and it is :) unfortunately something that got left off of the Release Notes. As :) Nicolas Christin mentioned in his response, that piece of code was :) based on a kludge, and we decided that that code made some rather :) arbitrary assumptions that don't make sense anymore. :) :) We took out the message entirely, as it seemed to us a message with :) very little information, and one that probably confused more people :) than it helped. There are still safeguards to prevent messages from :) accidentally getting sent out, such as the prompt to Post or Followup, :) and especially the "Posted message may go to thousands of readers. :) Really post?". Hi Jeff, There's one thing that is good about the kludge. It would have made me check if the message actually went to the newsgroup before I replied. I would not have replied to it and posted it in the newsgroup, had I known any better. I suppose I can be considered a power user of Pine and none of the work arounds that you suggest really work for me. I would not mind if I had to enable this warning, but please do not just eliminate it. It's really useful, I mean it. Thank you for your consideration. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Mon Aug 4 23:42:22 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 23:42:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756gLxd023737; Mon, 4 Aug 2003 23:42:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756gIof024920 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 23:42:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h756fkKH027500; Mon, 4 Aug 2003 23:41:46 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756eb2x032988 for ; Mon, 4 Aug 2003 23:40:38 -0700 Received: from msgdirector2.onetel.net.uk (msgdirector2.onetel.net.uk [212.67.96.149]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756eZC0024738 for ; Mon, 4 Aug 2003 23:40:36 -0700 Received: from [213.78.92.251] ([213.78.92.251]) by msgdirector2.onetel.net.uk (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGU12913; Tue, 5 Aug 2003 07:40:09 +0100 (BST) Message-Id: Date: Tue, 5 Aug 2003 07:40:43 +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: Nancy McGough To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 4 Aug 2003 Jeff Franklin (jpf@cac.washington.edu) wrote: > On Fri, 1 Aug 2003, Eduardo Chappa wrote: > > > Today I received a personal message with a "Newsgroup:" header. If I had > > seen the same message in Pine4.53 I would have seen a warning > > > You are correct that we did take out this behavior, and it is > unfortunately something that got left off of the Release Notes. As > Nicolas Christin mentioned in his response, that piece of code was based > on a kludge, and we decided that that code made some rather arbitrary > assumptions that don't make sense anymore. > > We took out the message entirely, as it seemed to us a message with very > little information, and one that probably confused more people than it > helped. There are still safeguards to prevent messages from accidentally > getting sent out, such as the prompt to Post or Followup, and especially > the "Posted message may go to thousands of readers. Really post?". But what if the message you are replying to was a *personal* email message that happens to have a Newsgroups header for informational purposes only (i.e., it was not actually posted to a Newsgroup)? It seems like we are back to the way things were during "The 1995 Newsgroups Header Fiasco," which I talk about here: Is the kludge that you took out the one that checked for a Path header? This (I hope) is not going to be as disasterous as it was in 1995 because 1) there are not as many people using newsreaders, such as nn, that include a Newsgroups header in email-only message and 2) maybe less people are *both* posting and emailing a reply because the world of email has turned into a cesspool of spam and fake From addresses. -- Nancy McGough Infinite Ink Writing about procmail, imap, pine, spam-deflexion strategies & more From pinedev@shiva0.cac.washington.edu Mon Aug 4 23:48:52 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 23:48:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756mpxd023910; Mon, 4 Aug 2003 23:48:51 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756mmof025048 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 23:48:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h756mKJ8028218; Mon, 4 Aug 2003 23:48:20 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756lp2x016548 for ; Mon, 4 Aug 2003 23:47:51 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756lmZG030131 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 4 Aug 2003 23:47:50 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h756lefR029603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 5 Aug 2003 10:47:41 +0400 (MSD) Message-Id: Date: Tue, 5 Aug 2003 10:47:35 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: "From" in message list. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXQggWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=XIII, Probability=13%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SUBJECT_IS_LIST, MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! Some mail lists rewrite "From" address of messages to list address, inserting non-address part of it into brackets. Like this: From: "Alexander V Alekseev" becomes like this: From: (Alexander V Alekseev) or even like this: From: (=?koi8-r?B?5MDLz9fBIOXLwdTF0snOwQ==?=) In such case, pine shows only list address in "From" header field. Is the a way to see part in () ? Bye. Alex. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Mon Aug 4 23:51:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 4 Aug 2003 23:51:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756pYxd024003; Mon, 4 Aug 2003 23:51:34 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756pWof025122 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 4 Aug 2003 23:51:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h756ovTB021516; Mon, 4 Aug 2003 23:50:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756oT2x016430 for ; Mon, 4 Aug 2003 23:50:29 -0700 Received: from msgdirector1.onetel.net.uk (msgdirector1.onetel.net.uk [212.67.96.148]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h756oRdL018863 for ; Mon, 4 Aug 2003 23:50:27 -0700 Received: from [213.78.92.251] ([213.78.92.251]) by msgdirector1.onetel.net.uk (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id AGL78512; Tue, 5 Aug 2003 07:50:04 +0100 (BST) Message-Id: Date: Tue, 5 Aug 2003 07:50:37 +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: Nancy McGough To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Message-Flag: Worried about bugs & viruses? Switch to Mac/Unix/PC Pine - info @ www.ii.com X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On 5 Aug 2003 Nancy McGough (nm-reverse-spam-filter@ii.deflexion.com) wrote: > > in 1995 because 1) there are not as many people using > newsreaders, such as nn, that include a Newsgroups header in > email-only message and 2) maybe less people are *both* posting > and emailing a reply because the world of email has turned into a > cesspool of spam and fake From addresses. Oops, what I meant to say for #2 is: maybe there are less people now who send a reply to a newsgroup message with *only* an email message (as opposed to with only a news posting or with both a news posting and a cc'd email message) because the world of email has turned into a cesspool of spam and fake From addresses. -- Nancy McGough Infinite Ink Writing about procmail, imap, pine, spam-deflexion strategies & more From pinedev@shiva0.cac.washington.edu Tue Aug 5 06:50:03 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 06:50:03 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75Dnxxd003617; Tue, 5 Aug 2003 06:49:59 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75Dnuof002600 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 06:49:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75DnPKH020666; Tue, 5 Aug 2003 06:49:25 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75DmX2x048530 for ; Tue, 5 Aug 2003 06:48:34 -0700 Received: from concept.ocis.temple.edu (concept.ocis.temple.edu [155.247.27.102]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75DmWJL023655 for ; Tue, 5 Aug 2003 06:48:32 -0700 Received: from concept.ocis.temple.edu (localhost [127.0.0.1]) by concept.ocis.temple.edu (8.12.8p1/8.12.8) with ESMTP id h75DmVAT023637 for ; Tue, 5 Aug 2003 09:48:31 -0400 (EDT) Received: from localhost (sbirl@localhost) by concept.ocis.temple.edu (8.12.8p1/8.12.8/Submit) with ESMTP id h75DmVBE023628 for ; Tue, 5 Aug 2003 09:48:31 -0400 (EDT) Message-Id: Date: Tue, 5 Aug 2003 09:48:31 -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: Birl To: Pine Discussion Forum Subject: Re: "From" in message list. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: concept.ocis.temple.edu: sbirl owned process doing -bs X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-CONCEPT: sbirl at concept dot temple dot edu composed this message. X-Uwash-Spam: Gauge=XXIIIIIII, Probability=27%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __IN_REP_TO, SUBJECT_IS_LIST, __REFERENCES, X_AUTH_WARNING, REFERENCES, IN_REP_TO, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, MISSING_MIMEOLE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As it was written on Aug 5, thus Alexander V Alekseev spake unto Pine...: Alex: Date: Tue, 5 Aug 2003 10:47:35 +0400 (MSD) Alex: From: Alexander V Alekseev Alex: To: Pine Discussion Forum Alex: Subject: "From" in message list. Alex: Alex: Hello! Alex: Alex: Some mail lists rewrite "From" address of messages Alex: to list address, inserting non-address part of it into Alex: brackets. Like this: Alex: Alex: From: "Alexander V Alekseev" Alex: Alex: becomes like this: Alex: From: (Alexander V Alekseev) Alex: or even like this: Alex: From: (=?koi8-r?B?5MDLz9fBIOXLwdTF0snOwQ==?=) Alex: Alex: In such case, pine shows only list address in "From" Alex: header field. Is the a way to see part in () ? Alex: Alex: Bye. Alex. Have you tried turning on full headers? Thanks Scott Birl Senior Systems Administrator Computer Services Temple University 1805 North Broad Street Philadelphia Pennsylvania 19122 United States ====*====*====*====*====*====*====*====+====*====*====*====*====*====*====*====* From pinedev@shiva0.cac.washington.edu Tue Aug 5 07:07:45 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 07:07:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75E7jxd004215; Tue, 5 Aug 2003 07:07:45 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75E7fof003079 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 07:07:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75E7ATB011732; Tue, 5 Aug 2003 07:07:10 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75E6A2x048426 for ; Tue, 5 Aug 2003 07:06:10 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75E61dM012134 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 5 Aug 2003 07:06:08 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h75E5bfR011899 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 18:05:38 +0400 (MSD) Message-Id: Date: Tue, 5 Aug 2003 18:05:32 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Re: "From" in message list. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Birl X-Cc: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXm1hWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SUBJECT_IS_LIST, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! On Tue, 5 Aug 2003, Birl wrote: > As it was written on Aug 5, thus Alexander V Alekseev spake unto Pine...: > > Alex: Some mail lists rewrite "From" address of messages > Alex: to list address, inserting non-address part of it into > Alex: brackets. Like this: > Alex: > Alex: From: "Alexander V Alekseev" > Alex: > Alex: becomes like this: > Alex: From: (Alexander V Alekseev) > Alex: or even like this: > Alex: From: (=?koi8-r?B?5MDLz9fBIOXLwdTF0snOwQ==?=) > Alex: > Alex: In such case, pine shows only list address in "From" > Alex: header field. Is the a way to see part in () ? > > Have you tried turning on full headers? Yes. Of course it works (it would be strange, if it doesn't). But: 1) I can't see 'full headers' in message list. 2) It's rather difficult to read undecoded mail (in full headers mode). ;-)) Bye. Alex. From pinedev@shiva0.cac.washington.edu Tue Aug 5 08:58:09 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 08:58:09 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75Fw8xd009203; Tue, 5 Aug 2003 08:58:08 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75Fw5of007358 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 08:58:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75FvaOL077676; Tue, 5 Aug 2003 08:57:36 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75Fut2x044266 for ; Tue, 5 Aug 2003 08:56:58 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75FuqZG017945 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 5 Aug 2003 08:56:54 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h75FunfR014373 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 5 Aug 2003 19:56:50 +0400 (MSD) Message-Id: Date: Tue, 5 Aug 2003 19:56:44 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Bug in subject decoding. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXGeiWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=XI, Probability=11%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, __UPPERCASE_25_50, UPPERCASE_25_50' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! BTW: pine has a bug in decoding. Header like this: -------------------------------------------------------- Subject: Re: [apache-talk] Re[2]: [apache-talk] =?KOI8-R?Q?=ED=CF=D6=CE=CF?= =?KOI8-R?Q?_=CC=C9_=D3=C4=C5=CC=C1=D4=D8_=D2=C5=C7=C9=D3=D4=D2=CF=CE?= =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D -------------------------------------------------------- is decoded only up to the 3rd line, leaving the last line "as is". It looks like: -------------------------------------------------------- Subject Re: [apache-talk] Re[2]: [apache-talk] <...skipped...> =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D -------------------------------------------------------- Does anyone knows why? Bye. Alex. From pinedev@shiva0.cac.washington.edu Tue Aug 5 10:37:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 10:37:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75HbIxd014293; Tue, 5 Aug 2003 10:37:18 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75HbEof011540 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 10:37:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75HajKH020052; Tue, 5 Aug 2003 10:36:45 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75HZq2x024198 for ; Tue, 5 Aug 2003 10:35:52 -0700 Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75HZoC0001436 for ; Tue, 5 Aug 2003 10:35:50 -0700 Received: from mailspool2.panix.com (mailspool2.panix.com [166.84.1.79]) by mail3.panix.com (Postfix) with ESMTP id 2D03A98261 for ; Tue, 5 Aug 2003 13:35:49 -0400 (EDT) Received: from eng-23.pacdigital (66.238.63.180.ptr.us.xo.net [66.238.63.180]) by mailspool2.panix.com (Postfix) with ESMTP id D3B2636DE2 for ; Tue, 5 Aug 2003 13:35:48 -0400 (EDT) Message-Id: Date: Tue, 5 Aug 2003 10:35: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: Kenneth Crudup To: Pine Discussion Forum Subject: "automatic" VCARD processing? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kenny@eng-23.pacdigital X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, FORGED_RCVD_TRAIL, SPAM_PHRASE_00_01, SIGNATURE_LONG_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I *swear* I remember that at one time, you could do a "S"ave(? I think) on an attached VCARD and Pine would prompt to save the readily-mapped fields into your address book. Is this right, or am I on crack? -Kenny -- Kenneth R. Crudup Sr. SW Engineer, Scott County Consulting, Los Angeles H: 3801 E. Pacific Coast Hw #9, Long Beach, CA 90804-2014 (888) 454-8181 W: 2052 Alton Parkway, Irvine, CA 92606-4905 (949) 252-1111-X240 -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Tue Aug 5 16:16:19 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 16:16:19 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NGIxd032551; Tue, 5 Aug 2003 16:16:18 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NGFof025893 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 16:16:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h75NFkTB019168; Tue, 5 Aug 2003 16:15:46 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NF92x007090 for ; Tue, 5 Aug 2003 16:15:09 -0700 Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NF77e018750 for ; Tue, 5 Aug 2003 16:15:07 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout3.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NF6gG029756; Tue, 5 Aug 2003 16:15:06 -0700 Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h75NF3Xa006129 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Tue, 5 Aug 2003 16:15:06 -0700 Message-Id: Date: Tue, 5 Aug 2003 16:15: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: Jeff Franklin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Eduardo Chappa X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 4 Aug 2003, Eduardo Chappa wrote: > Hi Jeff, > > There's one thing that is good about the kludge. It would have made me > check if the message actually went to the newsgroup before I replied. I > would not have replied to it and posted it in the newsgroup, had I known > any better. Hi Eduardo, I'm still trying to figure out why the "Followup, Reply, or Both" prompt and the "Posted message may go to thousands of readers. Really post?" prompt are not sufficient enough to prevent most accidents from happening. Also, why is the old message more useful at view time? That the message shows at view time seems unnecessary and distracting, wouldn't such a message be more useful at compose time? "Unverified Newsgroup Header" doesn't tell me much. Any message not in a newsgroup with a Newsgroup header is unverified, and it seems to me to be overly paranoid to warn whenever a user views a such a message. It's easy enough to add a warning back into the code. I am soliciting from you your suggestions as to when such a message should appear (and under what conditions), and why you don't think the two prompts are enough. We'll probably just do whatever you suggest. Thanks, Jeff From pinedev@shiva0.cac.washington.edu Tue Aug 5 19:38:41 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 19:38:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h762cfxd006603; Tue, 5 Aug 2003 19:38:41 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h762cbof031847 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 19:38:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h762bmKH004736; Tue, 5 Aug 2003 19:37:48 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h762b52x044162 for ; Tue, 5 Aug 2003 19:37:05 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h762b3rL029135 for ; Tue, 5 Aug 2003 19:37:03 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h762b1Mw437171; Tue, 5 Aug 2003 19:37:01 -0700 (PDT) Message-Id: Date: Tue, 5 Aug 2003 19:37: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: Eduardo Chappa To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff Franklin X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_05_08' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jeff Franklin (jpf@cac.washington.edu) wrote in the pine-info list today: :) On Mon, 4 Aug 2003, Eduardo Chappa wrote: :) :) > Hi Jeff, :) > :) > There's one thing that is good about the kludge. It would have made :) > me check if the message actually went to the newsgroup before I :) > replied. I would not have replied to it and posted it in the :) > newsgroup, had I known any better. :) :) Hi Eduardo, :) :) I'm still trying to figure out why the "Followup, Reply, or Both" :) prompt and the "Posted message may go to thousands of readers. Really :) post?" prompt are not sufficient enough to prevent most accidents from :) happening. Hi Jeff, I think we agree on this point. I wish I could find a way to replace "most" by "all" in your above quoted sentence. :) Also, why is the old message more useful at view time? That the :) message shows at view time seems unnecessary and distracting, wouldn't :) such a message be more useful at compose time? I see your point, but I am not sure when it would be convenient to see this message. I find it more of a problem when you actually compose the reply of the message, because verifying that the message was posted (or not), ultimately decides where are you going to send your reply. In my case, this would mean that I would receive the warning twice, for as long as that message lasted in the screen. It would become annoying very rapidly. :) "Unverified Newsgroup Header" doesn't tell me much. Any message not in :) a newsgroup with a Newsgroup header is unverified, and it seems to me :) to be overly paranoid to warn whenever a user views a such a message. Granted, but the kludge tried to identify clients that used the newsgroup header in the way that you intended it to be used (as a signal that the message had been sent to a newsgroup), so for example, messages posted and mailed by Pine did not get that warning. That's a good compromise I think. Of course, the ideal would be not to have that kludge, but I can't see a way to eliminate it either. I got an e-mail which proves to me that that kludge is still useful. :) It's easy enough to add a warning back into the code. I am soliciting :) from you your suggestions as to when such a message should appear (and :) under what conditions), and why you don't think the two prompts are :) enough. We'll probably just do whatever you suggest. I've been thinking about this, and I am quite convinced that I want this warning before I press the 'R' key to reply. Here there are two ideas: 1) To keep the old behavior exactly as it was (that means to return the ngbogus field to the c-client library, and all the old code taken from Pine), but I would change the text of the warning. Here are some ideas: "Newsgroup header indicates that this message MAY have been posted" "This message MAY have been posted (verify before replying)" 2) To add a handle at the bottom of the message that says something like [ Note: Message MAY have been posted. Verify it now ] following that handle would take you to a screen with the list of all the newsgroups in the newsgroup fields, which when selected allow you to open the above said newsgroup, where you can check if the message was posted by looking at the index. I'm not quite sure that this is a god idea but I thought I would comment on it, instead of deleting it totally from this message. The drawbacks of the first and second method are the same. Even if the message was posted, there's no reason to believe that it will be in the newsgroup in, say, 15 days, so actually verifying that the message was posted may turn out unsuccessful, but what is good, is that there was a warning, and so you'll think twice when you hit the 'R' key to reply about what you want to do next with your message. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Tue Aug 5 20:05:35 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 5 Aug 2003 20:05:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7635Yxd007300; Tue, 5 Aug 2003 20:05:34 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7635RWO005825 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 5 Aug 2003 20:05:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7634xJ8021128; Tue, 5 Aug 2003 20:04:59 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7634K2x016506 for ; Tue, 5 Aug 2003 20:04:20 -0700 Received: from laplace.sag.gwu.edu (laplace.sag.gwu.edu [128.164.127.72]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7634I7e003920 for ; Tue, 5 Aug 2003 20:04:19 -0700 Received: from lopes.sag.gwu.edu (lopes.sag.gwu.edu [192.168.61.125]) by laplace.sag.gwu.edu (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0HJ600IDJGJ3MH@laplace.sag.gwu.edu> for pine-info@u.washington.edu; Tue, 5 Aug 2003 23:04:15 -0400 (EDT) Received: from lovelace.nit.gwu.edu (localhost [127.0.0.1]) by lopes.sag.gwu.edu (8.10.2+Sun/8.10.2) with ESMTP id h762nKJ02916 for ; Tue, 05 Aug 2003 22:49:20 -0400 (EDT) Received: from acad1 (acad.gwu.edu [128.164.127.128]) by lovelace.nit.gwu.edu (8.12.9/8.12.9) with ESMTP id h7634tBJ011723 for ; Tue, 05 Aug 2003 23:04:55 -0400 (EDT) Message-Id: Date: Tue, 05 Aug 2003 23:04:14 -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: Jeff Baxter To: Pine Discussion Forum Subject: Directories and Folders... MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-To: Pine Discussion Forum X-X-Sender: jbaxter@acad1 X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello all - Not so much a bug, as a request for some advice... We use Pine on a few servers (differing versions, but this seems to affect all of them - 4.44 for example) to connect to our IMAP server. We previously used Sun Internet Mail Server, SIMS version 4. When a directory was created (as opposed to a mail folder), it appeared with a [/] suffix - and hitting "Enter" or ">" took you to a listing of the mail folders (or other directories) within. Probably because Pine knew SIMS didn't support having mail in a directory, just in folders.. We migrated this weekend to Sun One Messaging (also known as iPlanet Messaging Server), version 5.2. All of a sudden every folder is now a directory with a [/] suffix - probably just a "feature" of the migration. That's livable. Here's the problem. Any directories from before (not folders, directories) at first appeared to have nothing in them. What we eventually discovered was the distinction between using the ">" key to enter the directory and see the sub-folders (which were all there) and using the "Enter" key to view messages actually in the directory (of which there were none). So.... long story short... isn't there any way to make this more intuitive? For example, have "Enter" list the sub-directories if there's no actual mail in the directory itself? Or have it so that when you hit "Enter" it shows you the sub-directories *and* the mail itself (or at least an option saying "View mail in this actual directory?) Right now, we have users who think they have "lost" mail folders because they enter a directory and see nothing when using the "Enter" key. We are trying to re-educate them, but it seems like there should be a better way. I've searched the setable options, and don't see anything on point for this. Thanks for any help! Jeff Baxter Manager, Technology Engineering Information Systems and Services George Washington University -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Wed Aug 6 00:08:31 2003 -0700 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 00:08:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7678Uxd013721; Wed, 6 Aug 2003 00:08:30 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7678Sof005708 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 00:08:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7677vJ8014918; Wed, 6 Aug 2003 00:07:57 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7671i2x016826 for ; Wed, 6 Aug 2003 00:01:44 -0700 Received: from lisa.goe.net (lisa.JS.Jura.Uni-Goettingen.de [134.76.166.209]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7671grM003870 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 6 Aug 2003 00:01:43 -0700 Received: from mutter.goe.net (mutter-lisa0.a11.local [192.168.31.26]) by lisa.goe.net (8.12.6/8.12.6) with ESMTP id h7671b8i015162; Wed, 6 Aug 2003 09:01:37 +0200 Received: from hase.a11.local ([192.168.28.33]) by mutter.goe.net with esmtp (Exim 4.20) id 19kIIj-0002ce-5N; Wed, 06 Aug 2003 09:01:37 +0200 Received: by hase.a11.local (Postfix, from userid 500) id D2D3551BB3; Wed, 6 Aug 2003 09:06:51 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by hase.a11.local (Postfix) with ESMTP id C7DA117778; Wed, 6 Aug 2003 09:06:51 +0200 (CEST) Message-Id: Date: Wed, 6 Aug 2003 09:06:51 +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: Bernhard Kaindl To: Pine Discussion Forum Subject: Re: Bug in subject decoding. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Alexander V Alekseev X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello Alexander, On Tue, 5 Aug 2003, Alexander V Alekseev wrote: > > BTW: pine has a bug in decoding. Header like this: > -------------------------------------------------------- > Subject: Re: [apache-talk] Re[2]: [apache-talk] > =?KOI8-R?Q?=ED=CF=D6=CE=CF?= > =?KOI8-R?Q?_=CC=C9_=D3=C4=C5=CC=C1=D4=D8_=D2=C5=C7=C9=D3=D4=D2=CF=CE?= > =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D Does the last line really look like what I quote it above? While the two lines above it look like containing valid encoded-words as specified, in RFC 2047, it looks the last line is not a 'encoded-word' like I read http://www.ietf.org/rfc/rfc2047.txt. Naturally speaking it says: | Generally, an "encoded-word" is a sequence of printable ASCII characters | that begins with "=?", ends with "?=", and has two "?"s in between. The exact syntax is: | encoded-word = "=?" charset "?" encoding "?" encoded-text "?=" More rules apply, but this is the basic requirement for an 'encoded-word' and it must not contain line breaks, so even if the "?=" would come later, it would be too late. To a human, the last line looks like containing such 'encoded-word', but while the word suspectible to be a 'encoded-word', it does not end with "?=", and so it does not conform to the syntax covered by RFC 2047, as I read it, so it has to be displayed as-is, which pine does. Maybe it conforms to an other RFC which tells how to handl such strings, but I don't know it, but I'm also not an expert in these issues. > is decoded only up to the 3rd line, leaving the last line "as > is". It looks like: > -------------------------------------------------------- > Subject Re: [apache-talk] Re[2]: [apache-talk] <...skipped...> =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D > -------------------------------------------------------- This looks correct according to RFC 2047 to me, the last line does not contain anything which is covered by it, and I think at least pine does not implement other RFCs for MIME Message Header Header Extensions which encode non US-ASCII strings. My assumption is that the message may have been corrupted on the way to pine, maybe by the sending email program. Maybe it has a limited number of bytes it can use internally to handle long encoded subject strings and maybe this limit has been reached or even overflown(which would be bad for the user of this program) Maybe you want to ask the sender if his program crashed some time after sending this mail(which would also have security implications) Bernhard -- "The exclusive right to invention [is] given not of natural right, but for the benefit of society." -- Thomas Jefferson -- The European Parliament has postponed the vote on the software patent directive, enforcing 30.000 patents on abstract rules as used in software back to the original date of 1st of September, thereby rejecting initially successful efforts to rush to vote on June 30th. There is time again, but not much: -- The democratic process to prevent this, will have ended in 25 days! http://www.softwarepatents.co.uk/now/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 00:19:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h767Jpxd013988; Wed, 6 Aug 2003 00:19:51 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h767Jmof005980 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 00:19:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h767JKOL085872; Wed, 6 Aug 2003 00:19:20 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h767Ih2x061284 for ; Wed, 6 Aug 2003 00:18:43 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h767Ie7e016173 for ; Wed, 6 Aug 2003 00:18:42 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h767IRfR010929 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 11:18:27 +0400 (MSD) Message-Id: Date: Wed, 6 Aug 2003 11:18:22 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Re: Bug in subject decoding. In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bernhard Kaindl X-Cc: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXkCjWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_01_02' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! It seems, you're right. On Wed, 6 Aug 2003, Bernhard Kaindl wrote: > > =?KOI8-R?Q?=C5=DA=D2=C5=C7=C9=D3=D4=D2=CF=CE=C5=DA=C1=D7=C9=D > > Does the last line really look like what I quote it above? Yes. > The exact syntax is: > > | encoded-word = "=?" charset "?" encoding "?" encoded-text "?=" [...skipped...] > My assumption is that the message may have been corrupted on the > way to pine, maybe by the sending email program. Maybe it has It seems, it's bug on sender side. Searching in mail archive, I found exactly last line as a substring of another encoded line. So, it's really corrupted. Thank you for valuable help. Bye. Alex. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 13:02:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76K2Gxd010549; Wed, 6 Aug 2003 13:02:16 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76K2Bof029949 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 13:02:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h76K1eJ8041134; Wed, 6 Aug 2003 13:01:40 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76K0h2x027608 for ; Wed, 6 Aug 2003 13:00:43 -0700 Received: from concept.ocis.temple.edu (concept.ocis.temple.edu [155.247.27.102]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76K0cdL014162 for ; Wed, 6 Aug 2003 13:00:42 -0700 Received: from concept.ocis.temple.edu (localhost [127.0.0.1]) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8) with ESMTP id h76K0bOc012414 for ; Wed, 6 Aug 2003 16:00:37 -0400 (EDT) Received: from localhost (sbirl@localhost) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8/Submit) with ESMTP id h76K0aKA012385 for ; Wed, 6 Aug 2003 16:00:36 -0400 (EDT) Message-Id: Date: Wed, 6 Aug 2003 16:00:35 -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: Birl To: Pine Discussion Forum Subject: Future request: Different levels of importance MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: concept.ocis.temple.edu: sbirl owned process doing -bs X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-CONCEPT: sbirl at concept dot temple dot edu composed this message. X-Uwash-Spam: Gauge=XXXIIIIIIII, Probability=38%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, X_AUTH_WARNING, PRIORITY_NO_NAME, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE, MISSING_MIMEOLE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As I read through the various mailing lists, I often flag messages as Important. A question just occured to me: Will Pine support different levels of importance, or shall I say priority? Something that can be easily seen whether index-format=IMAPSTATUS or index-format=STATUS I would love to see this in future releases. Suggestion: Instead of using a *, use a numbering system (1-5) like the X-Priority header uses. Thanks Scott Birl Senior Systems Administrator Computer Services Temple University 1805 North Broad Street Philadelphia Pennsylvania 19122 United States ====*====*====*====*====*====*====*====+====*====*====*====*====*====*====*====* -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 16:15:06 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NF2xd020505; Wed, 6 Aug 2003 16:15:03 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NEwof005087 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 16:14:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h76NERJ8101650; Wed, 6 Aug 2003 16:14:27 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NDZ2x045818 for ; Wed, 6 Aug 2003 16:13:35 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NDTC1010100 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 6 Aug 2003 16:13:29 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NDSin029365 for ; Wed, 6 Aug 2003 16:13:28 -0700 Received: from [128.95.135.3] ([128.95.135.3]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h76NDSXa024633 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Wed, 6 Aug 2003 16:13:28 -0700 Message-Id: Date: Wed, 6 Aug 2003 16:13:28 -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: Steve Hubert To: Pine Discussion Forum Subject: Re: "automatic" VCARD processing? In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Aug 2003, Kenneth Crudup wrote: > I *swear* I remember that at one time, you could do a "S"ave(? I think) > on an attached VCARD and Pine would prompt to save the readily-mapped > fields into your address book. Is this right, or am I on crack? > > -Kenny That's right. It still seems to work for me. It is Save. Maybe pine isn't recognizing it as a genuine VCARD attachment. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 17:17:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770Hdxd023641; Wed, 6 Aug 2003 17:17:39 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770HZof007435 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 17:17:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h770GvTB032902; Wed, 6 Aug 2003 17:16:57 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770GA2x040890 for ; Wed, 6 Aug 2003 17:16:10 -0700 Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770G8ZG022480 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 6 Aug 2003 17:16:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout4.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770G7CK011348; Wed, 6 Aug 2003 17:16:07 -0700 Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h770G64A026781 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Wed, 6 Aug 2003 17:16:07 -0700 Message-Id: Date: Wed, 6 Aug 2003 17:16:05 -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: Jeff Franklin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Eduardo Chappa X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Aug 2003, Eduardo Chappa wrote: > Granted, but the kludge tried to identify clients that used the newsgroup > header in the way that you intended it to be used (as a signal that the > message had been sent to a newsgroup), so for example, messages posted and > mailed by Pine did not get that warning. That's a good compromise I think. This is the part of the old code that will most likely not be returning. The new behavior would warn for ALL messages in non-nntp mailboxes that have a Newsgroup header. The presence of "Pine" in the Message-id is by no means an indication that the message was posted. I'm now picturing a warning to be shown after a user says to Followup this type of message, saying something like "Replying to message that may or may not have been posted to newsgroup". Unless I hear any objections, consider it added. Jeff From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 6 Aug 2003 21:48:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h774mVxd030765; Wed, 6 Aug 2003 21:48:31 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h774mQof014203 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 6 Aug 2003 21:48:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h774luTB030620; Wed, 6 Aug 2003 21:47:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h774lA2x053158 for ; Wed, 6 Aug 2003 21:47:11 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h774l9C0012896 for ; Wed, 6 Aug 2003 21:47:09 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h774l7Mw018813; Wed, 6 Aug 2003 21:47:07 -0700 (PDT) Message-Id: Date: Wed, 6 Aug 2003 21:47: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 To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff Franklin X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_05_08' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jeff Franklin (jpf@cac.washington.edu) wrote in the pine-info list today: :) On Tue, 5 Aug 2003, Eduardo Chappa wrote: :) :) > Granted, but the kludge tried to identify clients that used the :) > newsgroup header in the way that you intended it to be used (as a :) > signal that the message had been sent to a newsgroup), so for :) > example, messages posted and mailed by Pine did not get that warning. :) > That's a good compromise I think. :) :) This is the part of the old code that will most likely not be :) returning. The new behavior would warn for ALL messages in non-nntp :) mailboxes that have a Newsgroup header. The presence of "Pine" in the :) Message-id is by no means an indication that the message was posted. :) I'm now picturing a warning to be shown after a user says to Followup :) this type of message, saying something like "Replying to message that :) may or may not have been posted to newsgroup". Unless I hear any :) objections, consider it added. Hi Jeff, Consider my earlier message my objection. What will happen will be that a user will press 'R' to reply, they'll recive the warning, cancel the reply to check if the message was posted (which may take a long time), then go back to the folder, press 'R' again and see the same message again, for as many seconds as that will take (3 to 4 seconds of inactivity each time?). I find this worse than the old behavior. Thank you for your consideration. Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 7 Aug 2003 06:29:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77DTDxd013879; Thu, 7 Aug 2003 06:29:13 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77DT6WO001402 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 7 Aug 2003 06:29:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h77DSZKH014948; Thu, 7 Aug 2003 06:28:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77DRj2x016446 for ; Thu, 7 Aug 2003 06:27:45 -0700 Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.137.19]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77DRidL028249 for ; Thu, 7 Aug 2003 06:27:44 -0700 Received: from LITHIUM.chvlva.adelphia.net (localhost [127.0.0.1]) by ares.cs.Virginia.EDU (8.12.9/8.12.8/UVACS-2003031900) with ESMTP id h77DRdL9006476 for ; Thu, 7 Aug 2003 09:27:40 -0400 (EDT) Message-Id: <0308070913330.3936@LITHIUM> Date: Thu, 7 Aug 2003 09:27:54 -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: Nicolas Christin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Tue, 5 Aug 2003, Eduardo Chappa wrote: > Granted, but the kludge tried to identify clients that used the > newsgroup header in the way that you intended it to be used (as a > signal that the message had been sent to a newsgroup), so for example, > messages posted and mailed by Pine did not get that warning. That's a > good compromise I think. Eduardo, I do not think identifying a few clients is the way to go. The kludge was pretty horrible. It was checking against a few "good" MUAs, with some ad-hoc tests, such as verifying the Message-ID starts with "Pine.". Needless to say, a simple patch such as moving the "Pine" field to a User-Agent header would break the whole thing. (That's why my User-Agent patch was _not_ a two-liner in 4.55 and below.) In addition, as far as I remember, the kludge did not check against some more recent newsgroup readers such as slrn, Mozilla, did not check the presence of a User-Agent field, etc. I, for one, am glad this kludge is gone. On the other hand, any other method of identifying that the Newsgroup header has been properly used would be very welcome. If you don't see any way of doing that other than checking for a few "reasonable" mailers (which again I think is a bad idea), I suggest you revisit the kludge in question. Move the Pine.ABC.xxx to the User-Agent field (see the patch for that to save you some effort), and test whether a User-Agent field has been set. Except for pine, pretty much all "reasonable" mailers/newsreaders use one. -- Nicolas From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 7 Aug 2003 12:22:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JMsxd029140; Thu, 7 Aug 2003 12:22:54 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JMpWO014737 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 7 Aug 2003 12:22:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h77JMCTB009842; Thu, 7 Aug 2003 12:22:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JLD2x041010 for ; Thu, 7 Aug 2003 12:21:13 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JLBSC032587 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 7 Aug 2003 12:21:12 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.33.9]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JLAxu013837; Thu, 7 Aug 2003 12:21:11 -0700 Received: from pigeon.cac.washington.edu (pigeon.cac.washington.edu [128.95.135.112]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77JL6Xa002482 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT); Thu, 7 Aug 2003 12:21:10 -0700 Message-Id: Date: Thu, 7 Aug 2003 12:21:05 -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: Jeff Franklin To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Eduardo Chappa X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Wed, 6 Aug 2003, Eduardo Chappa wrote: > Consider my earlier message my objection. What will happen will be that > a user will press 'R' to reply, they'll recive the warning, cancel the > reply to check if the message was posted (which may take a long time), > then go back to the folder, press 'R' again and see the same message > again, for as many seconds as that will take (3 to 4 seconds of inactivity > each time?). I think we should look at this warning as a measure to prevent people from shooting themselves in the foot. Someone that is concerned about the legitimacy of the mail they're responding to can take the time to verify it as they see fit, whether it be by trusting the message-id header or by opening the newsgroup to check for the message. What Nicolas Christin says is spot on. There are so many "trustworthy" news readers that to compare against a list of them is futile. Also, those headers can easily be faked. Jeff From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 7 Aug 2003 13:07:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77K7oxd031756; Thu, 7 Aug 2003 13:07:50 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77K7jof009289 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 7 Aug 2003 13:07:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h77K7ETB029398; Thu, 7 Aug 2003 13:07:15 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77K6B2x027572 for ; Thu, 7 Aug 2003 13:06:11 -0700 Received: from euler.math.washington.edu (euler.math.washington.edu [128.95.224.1]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h77K697e008934 for ; Thu, 7 Aug 2003 13:06:09 -0700 Received: from goedel.math.washington.edu (goedel.math.washington.edu [128.95.224.10]) by euler.math.washington.edu (8.12.9/8.12.9) with ESMTP id h77K67Mw058100; Thu, 7 Aug 2003 13:06:07 -0700 (PDT) Message-Id: Date: Thu, 7 Aug 2003 13:06: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 To: Pine Discussion Forum Subject: Re: Bug or Feature: "Unverified Newsgroup Header" message is gone In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff Franklin X-Cc: Pine Discussion Forum X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, SPAM_PHRASE_03_05' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN *** Jeff Franklin (jpf@cac.washington.edu) wrote today: :) On Wed, 6 Aug 2003, Eduardo Chappa wrote: :) :) > Consider my earlier message my objection. What will happen will be :) > that a user will press 'R' to reply, they'll recive the warning, :) > cancel the reply to check if the message was posted (which may take a :) > long time), then go back to the folder, press 'R' again and see the :) > same message again, for as many seconds as that will take (3 to 4 :) > seconds of inactivity each time?). :) :) I think we should look at this warning as a measure to prevent people :) from shooting themselves in the foot. Someone that is concerned about :) the legitimacy of the mail they're responding to can take the time to :) verify it as they see fit, whether it be by trusting the message-id :) header or by opening the newsgroup to check for the message. :) :) What Nicolas Christin says is spot on. There are so many "trustworthy" :) news readers that to compare against a list of them is futile. Hi Jeff, I was not talking about the way that Pine checks for trustworthiness of the fact that the message was posted (I'll talk about this later). What I said was that it is annoying to have a message that will be there for 4 seconds at least twice in the screen. It's disruptive, especially the second time. I admit that one would like to have a system of checking for trustowrthiness of the newsgroup header that does not depend on the newsreader used by the sender, that may not possible yet and simply declaring that it can not be done and ignoring the extra information is a complete disregard of the reality that we live in and where Pine should fit in. I think Pine needs to try harder, whatever method you decide to use to do this. I believe that the old behavior, even though not perfect, and maybe a kludge, was far better that what you are going to do now. I guess we'll have to agree to disagree and I will have to hack Pine. So glad I don't have to use PC-Pine. :) Also, those headers can easily be faked. There are so many headers that can and are faked, I haven't seen anyone protesting about verifying the FROM field in the index, even when it's wrong. Why?, because every one seems to either believe it 100% (like in a personal message), or disregard it (like in spam). In fact, this header is used to construct the To: header in a reply. Maybe you should be doing the case that Pine should give a warning saying "From field not verified". When Pine sorts by thread, it has to use the Date field, which is unverified. In fact, there are many fields that are used and all of them can be faked. Not because of this, Pine does not do threads. You are free to use as many fields as you can to determine a thread. The fact is that Pine does not verify any headers, so saying that you can't trust a newsgroup header ever is simply stating something that Pine does with any field, it does not single out the newsgroup header. As with threads, you can use as many fields as you like to determine if a message was posted to a newsgroup with a certain degree of certainty. As you know, not even the algorithm for threads is 100% fool proof, not everything is correctly threaded, but nobody is going to stop using threads because of this. People will encourage you to use more fields (or the fields that you used in a better way) if they know what was missing when threading was done. I hereby encourage you to use the message-id (or other headers) to determine certainty that the message was posted, and if you have a good certainty that the message was posted do not make me wait for 8 seconds until the message is gone. Thanks, Eduardo http://www.math.washington.edu/~chappa/pine/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 00:11:21 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h787BKxd022615; Fri, 8 Aug 2003 00:11:20 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h787BIof029598 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 00:11:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h787AlJ8024670; Fri, 8 Aug 2003 00:10:47 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h787672x041488 for ; Fri, 8 Aug 2003 00:06:07 -0700 Received: from gw02.holdiko.com (gw02.holdiko.com [202.155.43.68]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h787637e001046 for ; Fri, 8 Aug 2003 00:06:05 -0700 Received: from [192.168.0.50] ([192.168.0.50]) by gw02.holdiko.com (8.11.6/8.11.6) with ESMTP id h786x3403315 for ; Fri, 8 Aug 2003 13:59:03 +0700 Message-Id: Date: Fri, 8 Aug 2003 14:05:48 +0700 (WIT) 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 Sudjiman To: Pine Discussion Forum Subject: For to prune MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=XXXIIIII, Probability=35%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, FORGED_YAHOO_RCVD, L33T_SP34K, PGP_SIGNATURE, SPAM_PHRASE_00_01, LINES_OF_YELLING, __UPPERCASE_25_50, SIGNATURE_SHORT_DENSE, UPPERCASE_25_50' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear All, I just update my prune table. How can I force my pine to prunse folders? thx .dave Generally speaking, the Way of the warrior is resolute acceptance of death. -- Miyamoto Musashi, 1645 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE/M0vV7SUrJYWHOyoRAh16AJwJW+z9kBmwk/28ftF3c4QB7N44vgCbBiWD O9cTuheV7FjbbsM/fiqm/p8= =Rz4i -----END PGP SIGNATURE----- -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 08:31:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FVuxd004495; Fri, 8 Aug 2003 08:31:56 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FVrWO016252 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 08:31:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78FVLKH032684; Fri, 8 Aug 2003 08:31:21 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FUQ2x048704 for ; Fri, 8 Aug 2003 08:30:26 -0700 Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FUNrM027087 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 8 Aug 2003 08:30:25 -0700 Received: from localhost (localhost [127.0.0.1]) by aslan.narnia.pp.se (8.12.3p2/8.11.3) with ESMTP id h78FUMFX059117 for ; Fri, 8 Aug 2003 17:30:22 +0200 (CEST) (envelope-from mats@dufberg.se) Message-Id: <20030808162816.R52755@aslan.narnia.pp.se> Date: Fri, 8 Aug 2003 17:30:22 +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: Mats Dufberg To: Pine Discussion Forum Subject: Reading attachments with external program MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dufberg@aslan.narnia.pp.se X-To: Pine Discussion Forum X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/ X-Uwash-Spam: Gauge=XII, Probability=12%, Report='__HAS_MSGID, __SANE_MSGID, MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_01_02, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN How do I configure pine (under unix) so that I can read an attachment with an external program? I'd like to be able to open PDF attachments with xpdf and MS-WORD files with antiword without having to extract the files. Mats ----------------------------------------------------------------- Mats Dufberg mats@dufberg.se Blaoarvsgraend 42 +46-8-38 48 59 SE-162 45 Vaellingby, Sweden +46-70-258 2588 -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 08:42:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FgWxd005018; Fri, 8 Aug 2003 08:42:32 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FgSWO016706 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 08:42:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78Fg0KH025840; Fri, 8 Aug 2003 08:42:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FfL2x032938 for ; Fri, 8 Aug 2003 08:41:21 -0700 Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78FfJC0018876 for ; Fri, 8 Aug 2003 08:41:20 -0700 Received: from rigel (rigel.cse.sc.edu [129.252.130.115]) by moultrie.cse.sc.edu (Postfix) with ESMTP id AF89F1E4CE for ; Fri, 8 Aug 2003 11:41:18 -0400 (EDT) Message-Id: Date: Fri, 8 Aug 2003 10:41:18 -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: Gopi Sundaram To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: <20030808162816.R52755@aslan.narnia.pp.se> References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: gopalan@rigel X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Aug 2003, Mats Dufberg wrote: > How do I configure pine (under unix) so that I can read an attachment with > an external program? Make sure that the MIME-type of the attachment is correct, and add the application to handle it in your mailcap file. You may want to add an entry to your mime.types file to identify extensions with MIME-types. -- Gopi Sundaram http://www.zrox.net/Mail/Pine/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 10:08:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78H8Vxd009041; Fri, 8 Aug 2003 10:08:31 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78H8Sof013170 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 10:08:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78H7sOL077662; Fri, 8 Aug 2003 10:07:55 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78H722x048348 for ; Fri, 8 Aug 2003 10:07:02 -0700 Received: from concept.ocis.temple.edu (concept.ocis.temple.edu [155.247.27.102]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78H707e017511 for ; Fri, 8 Aug 2003 10:07:01 -0700 Received: from concept.ocis.temple.edu (localhost [127.0.0.1]) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8) with ESMTP id h78H6x1x018257 for ; Fri, 8 Aug 2003 13:06:59 -0400 (EDT) Received: from localhost (sbirl@localhost) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8/Submit) with ESMTP id h78H6xTS018254 for ; Fri, 8 Aug 2003 13:06:59 -0400 (EDT) Message-Id: Date: Fri, 8 Aug 2003 13:06:58 -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: Birl To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: concept.ocis.temple.edu: sbirl owned process doing -bs X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-CONCEPT: sbirl at concept dot temple dot edu composed this message. X-Uwash-Spam: Gauge=XIIIII, Probability=15%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __IN_REP_TO, __REFERENCES, X_AUTH_WARNING, REFERENCES, IN_REP_TO, PRIORITY_NO_NAME, EMAIL_ATTRIBUTION, SPAM_PHRASE_00_01, MISSING_MIMEOLE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN As it was written on Aug 8, thus Gopi Sundaram spake unto Pine Discussion Forum: Gopi: Date: Fri, 8 Aug 2003 10:41:18 -0500 (CDT) Gopi: From: Gopi Sundaram Gopi: To: Pine Discussion Forum Gopi: Subject: Re: Reading attachments with external program Gopi: Gopi: On Fri, 8 Aug 2003, Mats Dufberg wrote: Gopi: Gopi: > How do I configure pine (under unix) so that I can read an attachment with Gopi: > an external program? Gopi: Gopi: Make sure that the MIME-type of the attachment is correct, and add the Gopi: application to handle it in your mailcap file. You may want to add an Gopi: entry to your mime.types file to identify extensions with MIME-types. Gopi: Gopi: -- Gopi: Gopi Sundaram Gopi: http://www.zrox.net/Mail/Pine/ That may not be sufficent. If Mats is running under X (or CDE, etc), 2 commands might need to be executed: As root: xhost + localhost As user: setenv DISPLAY :0 In my situation, Im in CDE (under Solaris 9) as root, yet Im checking my email through a dtterm as my non-privleged self. My non-privleged account uses Netscape to view URLs and image attachments, but without those 2 commands, Netscape will not attach to root's CDE screen. Just something to think about. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 10:15:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78HFbxd009690; Fri, 8 Aug 2003 10:15:37 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78HFWof013833 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 10:15:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78HF4J8034564; Fri, 8 Aug 2003 10:15:05 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78HEO2x061884 for ; Fri, 8 Aug 2003 10:14:24 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78HEGC1009797 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 8 Aug 2003 10:14:23 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h78HDufR027104 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 21:13:56 +0400 (MSD) Message-Id: Date: Fri, 8 Aug 2003 21:13:50 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Birl X-Cc: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXjMrWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! On Fri, 8 Aug 2003, Birl wrote: > That may not be sufficent. If Mats is running under X (or CDE, etc), > 2 commands might need to be executed: > > > As root: xhost + localhost It seems to be much secure to copy ~/.Xauthority from root to non-priviledged user. > As user: setenv DISPLAY :0 Bye. Alex. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 11:33:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IXuxd013437; Fri, 8 Aug 2003 11:33:56 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IXrWO024291 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 11:33:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78IXOOL084428; Fri, 8 Aug 2003 11:33:24 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IWl2x061946 for ; Fri, 8 Aug 2003 11:32:47 -0700 Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IWidL019860 for ; Fri, 8 Aug 2003 11:32:45 -0700 Received: from rigel (rigel.cse.sc.edu [129.252.130.115]) by moultrie.cse.sc.edu (Postfix) with ESMTP id DAE311E4CE for ; Fri, 8 Aug 2003 14:32:43 -0400 (EDT) Message-Id: Date: Fri, 8 Aug 2003 13:32:43 -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: Gopi Sundaram To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: gopalan@rigel X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Aug 2003, Alexander V Alekseev wrote (quoting Alexander): >> That may not be sufficent. If Mats is running under X (or CDE, etc), >> 2 commands might need to be executed: That refers only to when your Pine session is running under different privileges than your X session. > It seems to be much secure to copy ~/.Xauthority from root to > non-priviledged user. Many Unix flavors support setting the XAUTHORITY env var to the path to the .Xauthority file you want to use. -- Gopi Sundaram http://www.zrox.net/Mail/Pine/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 11:46:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IkQxd014002; Fri, 8 Aug 2003 11:46:26 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IkMWO024791 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 11:46:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78IjsOL019294; Fri, 8 Aug 2003 11:45:54 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IjJ2x048302 for ; Fri, 8 Aug 2003 11:45:19 -0700 Received: from mail.cboss.ru (relay.cboss.ru [195.245.232.9]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78IjH7e019933 for ; Fri, 8 Aug 2003 11:45:18 -0700 Received: from alemate.int.cboss.ru ([10.97.254.14]) by mail.cboss.ru (8.12.8/8.12.8) with ESMTP id h78IjBfR007269 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 22:45:11 +0400 (MSD) Message-Id: Date: Fri, 8 Aug 2003 22:45:06 +0400 (MSD) 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: Alexander V Alekseev To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Gopi Sundaram X-Cc: Pine Discussion Forum X-X-Sender: alex@alemate.int.cboss.ru X-Archived: msg.XXFSrWDa@mail X-Archived: msg.XXCyQGGb@mail X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_02_03' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hello! On Fri, 8 Aug 2003, Gopi Sundaram wrote: > > It seems to be much secure to copy ~/.Xauthority from root to > > non-priviledged user. > > Many Unix flavors support setting the XAUTHORITY env var to the path to > the .Xauthority file you want to use. You're right. But that works only if you need to start X applications under only one user, other than root. (Because file must not be readable by users other than root and the user we expect to. That's why, we have to "chown our_user ~root/.Xauthority" to let it work, and also give all(or only that one) users access to the directory with it. Really, it's usually much more difficult to do, than just copy file.) Bye. Alex. PS: It's seems to be off-topic ;-)) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 14:22:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78LMvxd020480; Fri, 8 Aug 2003 14:22:57 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78LMsof023334 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 14:22:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h78LMOJ8024648; Fri, 8 Aug 2003 14:22:25 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78LK32x022524 for ; Fri, 8 Aug 2003 14:20:03 -0700 Received: from aslan.narnia.pp.se (aslan.narnia.pp.se [212.247.3.100]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h78LJxrM018433 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 8 Aug 2003 14:20:01 -0700 Received: from localhost (localhost [127.0.0.1]) by aslan.narnia.pp.se (8.12.3p2/8.11.3) with ESMTP id h78LJuFX060030; Fri, 8 Aug 2003 23:19:57 +0200 (CEST) (envelope-from mats@dufberg.se) Message-Id: <20030808230629.B59974@aslan.narnia.pp.se> Date: Fri, 8 Aug 2003 23:19:56 +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: Mats Dufberg To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: References: <20030808162816.R52755@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: dufberg@aslan.narnia.pp.se X-To: Gopi Sundaram X-Cc: Pine Discussion Forum X-message-flag: Tired of your mail client? Get pine! http://www.washington.edu/pine/ X-Uwash-Spam: Gauge=III, Probability=3%, Report='__HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SPAM_PHRASE_00_01' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Aug 8, 2003, 10:41 (-0500) Gopi Sundaram wrote: > On Fri, 8 Aug 2003, Mats Dufberg wrote: > > > How do I configure pine (under unix) so that I can read an attachment with > > an external program? > > Make sure that the MIME-type of the attachment is correct, and add the > application to handle it in your mailcap file. You may want to add an > entry to your mime.types file to identify extensions with MIME-types. I've added the following lines to .mailcap, Application/MSWORD;/usr/local/bin/antiword %s Application/PDF;/usr/X11R6/bin/xpdf %s When I try a PDF attachment, it works as expected, but for MSWORD attachment, something seems to happen in the background, but it is not shown to me. Do I have to open an xterm window in some way? Mats ----------------------------------------------------------------- Mats Dufberg mats@dufberg.se Blaoarvsgraend 42 +46-8-38 48 59 SE-162 45 Vaellingby, Sweden +46-70-258 2588 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 8 Aug 2003 23:05:58 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7965wxd003098; Fri, 8 Aug 2003 23:05:58 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7965sWO011236 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 8 Aug 2003 23:05:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7965PKH014906; Fri, 8 Aug 2003 23:05:26 -0700 Received: from mxu7.u.washington.edu (mxu7.u.washington.edu [140.142.32.165]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7964e2x062830 for ; Fri, 8 Aug 2003 23:04:41 -0700 Received: from moultrie.cse.sc.edu (moultrie.cse.sc.edu [129.252.138.7]) by mxu7.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7964dZF018136 for ; Fri, 8 Aug 2003 23:04:39 -0700 Received: from rigel (rigel.cse.sc.edu [129.252.130.115]) by moultrie.cse.sc.edu (Postfix) with ESMTP id 6BA1E1E405 for ; Sat, 9 Aug 2003 02:04:38 -0400 (EDT) Message-Id: Date: Sat, 9 Aug 2003 01:04:38 -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: Gopi Sundaram To: Pine Discussion Forum Subject: Re: Reading attachments with external program In-Reply-To: <20030808230629.B59974@aslan.narnia.pp.se> References: <20030808162816.R52755@aslan.narnia.pp.se> <20030808230629.B59974@aslan.narnia.pp.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: gopalan@rigel X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Aug 2003, Mats Dufberg wrote: > When I try a PDF attachment, it works as expected, but for MSWORD > attachment, something seems to happen in the background, but it is not > shown to me. Do I have to open an xterm window in some way? I've never used antiword, so I don't know. Try writing a wrapper script around antiword and using that as the application for word attachments. Put a sleep at the end of the wrapper script, so you have time to see what happens before it ends. -- Gopi Sundaram http://www.zrox.net/Mail/Pine/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 9 Aug 2003 12:32:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h79JWbxd021584; Sat, 9 Aug 2003 12:32:37 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h79JWYof021788 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 9 Aug 2003 12:32:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h79JW2OL092540; Sat, 9 Aug 2003 12:32:02 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h79JUq2x062846 for ; Sat, 9 Aug 2003 12:30:52 -0700 Received: from tecoma.mccc.edu (tecoma.mccc.edu [198.133.170.1]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h79JUmSB015790 for ; Sat, 9 Aug 2003 12:30:48 -0700 Received: from tecoma (tecoma [198.133.170.1]) by tecoma.mccc.edu (8.11.7+Sun/8.11.4) with ESMTP id h79JUgx16865 for ; Sat, 9 Aug 2003 15:30:42 -0400 (EDT) Message-Id: Date: Sat, 9 Aug 2003 15:30: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: Pete Holsberg To: Pine Discussion Forum Subject: New PC User MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi, I just installed v4.56 on my PC after having been a pine user under Unix for about 10 years. I have some questions that I couldn't find in the archives. 1) Is there a way to do away with having to type my password each time I log in to the POP3 server where my mail is gathered? 2) Is there a way to tranfer all my saved message folders (with contents) from the Unix box to my PC? 3) When I delete a message in PC Pine, it seems to also delete it from the POP3 server. Is that the only way messages on the server are managed? Thanks, Pete -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 11 Aug 2003 09:52:36 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGqZxd026140; Mon, 11 Aug 2003 09:52:35 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGqXof021091 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Aug 2003 09:52:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7BGq0OL073606; Mon, 11 Aug 2003 09:52:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGoW2x033648 for ; Mon, 11 Aug 2003 09:50:32 -0700 Received: from mxout2.cac.washington.edu (mxout2.cac.washington.edu [140.142.33.4]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGoUC1009111 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 11 Aug 2003 09:50:30 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGoTxu021239 for ; Mon, 11 Aug 2003 09:50:29 -0700 Received: from [128.95.135.3] ([128.95.135.3]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BGoT4A021955 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Mon, 11 Aug 2003 09:50:29 -0700 Message-Id: Date: Mon, 11 Aug 2003 09:50:29 -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: Steve Hubert To: Pine Discussion Forum Subject: Re: For to prune In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 8 Aug 2003, David Sudjiman wrote: > Dear All, > > I just update my prune table. How can I force my pine to prunse folders? > > thx > .dave You have a config variable called "last-time-prune-questioned". Set it back a month. That is, change it from 103.8 to 103.7. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 11 Aug 2003 11:59:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BIxUxd032246; Mon, 11 Aug 2003 11:59:30 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BIxQof025606 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 11 Aug 2003 11:59:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7BIwoJ8101742; Mon, 11 Aug 2003 11:58:50 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BIuS2x060788 for ; Mon, 11 Aug 2003 11:56:29 -0700 Received: from concept.ocis.temple.edu (concept.ocis.temple.edu [155.247.27.102]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7BIuMC0012478 for ; Mon, 11 Aug 2003 11:56:26 -0700 Received: from concept.ocis.temple.edu (localhost [127.0.0.1]) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8) with ESMTP id h7BIuC1x010912 for ; Mon, 11 Aug 2003 14:56:12 -0400 (EDT) Received: from localhost (sbirl@localhost) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8/Submit) with ESMTP id h7BIuCO9010909 for ; Mon, 11 Aug 2003 14:56:12 -0400 (EDT) Message-Id: Date: Mon, 11 Aug 2003 14:56:12 -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: Birl To: Pine Discussion Forum Subject: Pine 4.55 crash when attaching during -dimap=4,verbose=5 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: concept.ocis.temple.edu: sbirl owned process doing -bs X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-CONCEPT: sbirl at concept dot temple dot edu composed this message. X-Uwash-Spam: Gauge=XXXXI, Probability=41%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, X_AUTH_WARNING, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE, MISSING_MIMEOLE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Ive noticed that when I run Pine with "-dimap=4,verbose=5" options that the program will crash (no core) after I add an attachment to the Attchmnt field. ----------------------------------------------------------- Problem detected: "Received abort signal(sig=?)". Pine Exiting. Abort ----------------------------------------------------------- Id attach the .pine-debug file, but .... Debug output of the Pine program (debug=5 debug_imap=4). Version 4.55 (GSO) Mon Aug 11 14:42:14 2003 Debug file: /export/home/sbirl/.pine-debug1 (level=5 imap=4) "/usr/local/bin/pine" "-dimap=4,verbose=5" Setting home dir from $HOME: "/export/home/sbirl" -- init_pinerc -- Global config "/usr/local/lib/pine.conf" is default Personal config "/export/home/sbirl/.pinerc" is default Exceptions config not set on cmdline checking for default "/export/home/sbirl/.pinercex" in pinerc dir no, there is no exceptions config Global config: /usr/local/lib/pine.conf Personal config: /export/home/sbirl/.pinerc Exceptions config: Fixed config: /usr/local/lib/pine.conf.fixed init_vars: reading_pinerc "/usr/local/lib/pine.conf" Open failed: No such file or directory reading_pinerc "/export/home/sbirl/.pinerc" Read 43863 characters: default-fcc : /var/mail/sbirl feature-list : enable-bounce-cmd : no-signature-at-bottom : expunge-without-confirm : quit-without-confirm : delete-skips-deleted : enable-jump-shortcut : enable-tab-completion : expanded-view-of-addressbooks : news-post-without-validation : enable-mail-check-cue : enable-incoming-folders : save-will-advance : select-without-confirm : expanded-view-of-folders : compose-sets-newsgroup-without-confirm : show-selected-in-boldface : use-current-dir : enable-cruise-mode : no-enable-dot-files : enable-dot-folders : enable-flag-cmd : enable-flag-screen-implicitly : enable-full-header-cmd : enable-msg-view-forced-arrows : enable-search-and-replace : enable-partial-match-lists : expunge-without-confirm-everywhere : show-cursor : no-quell-lock-failure-warnings : quell-dead-letter-on-cancel : include-header-in-reply : include-text-in-reply : include-attachments-in-reply : combined-subdirectory-display : quell-empty-directories : separate-folder-and-directory-entries : compose-maps-delete-key-to-ctrl-d : enable-alternate-editor-cmd : no-enable-alternate-editor-implicitly : use-sender-not-x-sender : news-deletes-across-groups : check-newmail-when-quitting : no-alternate-compose-menu : print-offers-custom-cmd-prompt : no-reply-always-uses-reply-to : mark-for-cc : no-tab-visits-next-new-message-only : prefer-plain-text : enable-rules-under-take : enable-reply-indent-string-editing : enable-print-via-y-command : enable-suspend : enable-aggregate-command-set : news-offers-catchup-on-close : news-approximates-new-status : quell-extra-post-prompt : enable-delivery-status-notification : fcc-on-bounce : no-selectable-item-nobold : no-spell-check-before-sending : disable-sender : no-enable-8bit-esmtp-negotiation : warn-if-blank-subject : thread-index-shows-important-color : return-to-inbox-without-confirm : enable-msg-view-attachments : enable-msg-view-urls : enable-msg-view-web-hostnames : pass-control-characters-as-is : print-includes-from-line : print-formfeed-between-messages : enable-full-header-and-text : enable-goto-in-file-browser : enable-unix-pipe-cmd : confirm-role-even-for-default : enable-mouse-in-xterm : enable-newmail-in-xterm-icon : expose-hidden-config : show-plain-text-internally : slash-collapses-entire-thread : no-disable-password-caching : disable-pipes-in-sigs : disable-pipes-in-templates : disable-shared-namespaces : quell-news-envelope-update : ldap-result-to-addrbook-add : expanded-view-of-distribution-lists default-composer-hdr : From: Birl : To : Cc : Fcc : Attchmnt : Subject customized-hdrs : From: Birl : Expires : Return-Receipt-To : Reply-To : Reply-By : Expiry-Date : X-Status : Priority : X-Priority: 3 (Normal) : X-Message-Flag : Importance: Normal : Sensitivity: Normal : X-MSMail-Priority: Normal : X-CONCEPT: sbirl at concept dot temple dot edu composed this message. saved-msg-name-rule : default-folder fcc-name-rule : by-recipient sort-key : Arrival editor : /bin/vi : /usr/local/bin/pico image-viewer : /usr/dt/bin/sdtimage printer : kinkos [] lpr -h -Pkinkos personal-print-comma : kinkos [] lpr -h -Pkinkos last-time-prune-ques : 103.8 last-version-used : 4.55 incoming-startup-rul : first-recent reply-indent-string : _FROM_: personal-print-categ : 3 index-format : IMAPSTATUS MSGNO SMARTDATE FROMORTO(33%) SIZE SUBJECT(67%) mail-check-interval : 30 newsrc-path : /export/home/sbirl/.newsrc-free.teranews.com user-input-timeout : 3 url-viewers : /usr/dt/bin/netscape color-style : force-ansi-8color reply-leadin : _NEWS_("", "As it was written on _DATE_, thus _FROM_ spake unto _RECIPSANDNEWS_:", "As my eyes traversed _NEWS_, I saw the following:") normal-foreground-co : black normal-background-co : color015 quote1-foreground-co : color012 quote1-background-co : color015 quote3-foreground-co : color012 quote3-background-co : color015 prompt-foreground-co : white prompt-background-co : black index-important-fore : color015 index-important-back : color009 index-deleted-foregr : color011 index-deleted-backgr : black index-unseen-foregro : color012 index-unseen-backgro : color014 pruning-rule : ask-ask threading-index-styl : coll threading-expanded-c : - current-indexline-st : flip-colors titlebar-color-style : indexline folder-reopen-rule : yes-ask-y nntp-range : 1000 read_pinerc: time_pinerc_written = 1060363513 reading_pinerc "/usr/local/lib/pine.conf.fixed" Open failed: No such file or directory ======= Current_val options set ======= user-domain : concept.temple.edu nntp-server : free.teranews.com : news.temple.edu inbox-path : inbox default-fcc : /var/mail/sbirl default-saved-msg-fo : saved-messages postponed-folder : postponed-msgs signature-file : .signature feature-list : allow-changing-from : enable-bounce-cmd : no-signature-at-bottom : expunge-without-confirm : quit-without-confirm : delete-skips-deleted : enable-jump-shortcut : enable-tab-completion : expanded-view-of-addressbooks : news-post-without-validation : enable-mail-check-cue : enable-incoming-folders : save-will-advance : select-without-confirm : expanded-view-of-folders : compose-sets-newsgroup-without-confirm : show-selected-in-boldface : use-current-dir : enable-cruise-mode : no-enable-dot-files : enable-dot-folders : enable-flag-cmd : enable-flag-screen-implicitly : enable-full-header-cmd : enable-msg-view-forced-arrows : enable-search-and-replace : enable-partial-match-lists : expunge-without-confirm-everywhere : show-cursor : no-quell-lock-failure-warnings : quell-dead-letter-on-cancel : include-header-in-reply : include-text-in-reply : include-attachments-in-reply : combined-subdirectory-display : quell-empty-directories : separate-folder-and-directory-entries : compose-maps-delete-key-to-ctrl-d : enable-alternate-editor-cmd : no-enable-alternate-editor-implicitly : use-sender-not-x-sender : news-deletes-across-groups : check-newmail-when-quitting : no-alternate-compose-menu : print-offers-custom-cmd-prompt : no-reply-always-uses-reply-to : mark-for-cc : no-tab-visits-next-new-message-only : prefer-plain-text : enable-rules-under-take : enable-reply-indent-string-editing : enable-print-via-y-command : enable-suspend : enable-aggregate-command-set : news-offers-catchup-on-close : news-approximates-new-status : quell-extra-post-prompt : enable-delivery-status-notification : fcc-on-bounce : no-selectable-item-nobold : no-spell-check-before-sending : disable-sender : no-enable-8bit-esmtp-negotiation : warn-if-blank-subject : thread-index-shows-important-color : return-to-inbox-without-confirm : enable-msg-view-attachments : enable-msg-view-urls : enable-msg-view-web-hostnames : pass-control-characters-as-is : print-includes-from-line : print-formfeed-between-messages : enable-full-header-and-text : enable-goto-in-file-browser : enable-unix-pipe-cmd : confirm-role-even-for-default : enable-mouse-in-xterm : enable-newmail-in-xterm-icon : expose-hidden-config : show-plain-text-internally : slash-collapses-entire-thread : no-disable-password-caching : disable-pipes-in-sigs : disable-pipes-in-templates : disable-shared-namespaces : quell-news-envelope-update : ldap-result-to-addrbook-add : expanded-view-of-distribution-lists default-composer-hdr : From: Birl : To : Cc : Fcc : Attchmnt : Subject customized-hdrs : From: Birl : Expires : Return-Receipt-To : Reply-To : Reply-By : Expiry-Date : X-Status : Priority : X-Priority: 3 (Normal) : X-Message-Flag : Importance: Normal : Sensitivity: Normal : X-MSMail-Priority: Normal : X-CONCEPT: sbirl at concept dot temple dot edu composed this message. saved-msg-name-rule : default-folder fcc-name-rule : by-recipient sort-key : Arrival addrbook-sort-rule : fullname-with-lists-last folder-sort-rule : alphabetical goto-default-rule : inbox-or-folder-in-recent-collection incoming-startup-rul : first-recent pruning-rule : ask-ask folder-reopen-rule : yes-ask-y threading-display-st : struct threading-index-styl : coll threading-indicator- : > threading-expanded-c : - threading-lastreply- : | editor : /bin/vi : /usr/local/bin/pico composer-wrap-column : 74 reply-indent-string : _FROM_: reply-leadin : _NEWS_("", "As it was written on _DATE_, thus _FROM_ spake unto _RECIPSANDNEWS_:", "As my eyes traversed _NEWS_, I saw the following:") empty-header-message : undisclosed-recipients image-viewer : /usr/dt/bin/sdtimage use-only-domain-name : no bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu suggest-fullname : Pine Developers suggest-address : pine-suggestions@cac.washington.edu local-fullname : Local Support local-address : postmaster kblock-passwd-count : 1 index-format : IMAPSTATUS MSGNO SMARTDATE FROMORTO(33%) SIZE SUBJECT(67%) viewer-overlap : 2 scroll-margin : 0 status-message-delay : 0 mail-check-interval : 30 maildrop-check-minim : 60 nntp-range : 1000 newsrc-path : /export/home/sbirl/.newsrc-free.teranews.com url-viewers : /usr/dt/bin/netscape mail-directory : mail news-collections : Temple NNTP *{news.temple.edu/nntp}[] : GRC.com NNTP *{news.grc.com/nntp}[] : TeraNews NNTP *{free.teranews.com/nntp}[] address-book : .addressbook standard-printer : lp last-time-prune-ques : 103.8 last-version-used : 4.55 user-input-timeout : 3 remote-abook-history : 3 remote-abook-validit : 5 printer : kinkos [] lpr -h -Pkinkos personal-print-comma : kinkos [] lpr -h -Pkinkos personal-print-categ : 3 elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no color-style : force-ansi-8color current-indexline-st : flip-colors titlebar-color-style : indexline normal-foreground-co : black normal-background-co : color015 keylabel-foreground- : black keylabel-background- : color015 selectable-item-fore : black selectable-item-back : color015 quote1-foreground-co : color012 quote1-background-co : color015 quote2-foreground-co : black quote2-background-co : color015 quote3-foreground-co : color012 quote3-background-co : color015 prompt-foreground-co : white prompt-background-co : black index-important-fore : color015 index-important-back : color009 index-deleted-foregr : color011 index-deleted-backgr : black index-unseen-foregro : color012 index-unseen-backgro : color014 ======= Command_line_val options set ======= ======= User_val options set (/export/home/sbirl/.pinerc) ======= personal-name : Birl user-domain : concept.temple.edu nntp-server : free.teranews.com : news.temple.edu default-fcc : /var/mail/sbirl feature-list : enable-bounce-cmd : no-signature-at-bottom : expunge-without-confirm : quit-without-confirm : delete-skips-deleted : enable-jump-shortcut : enable-tab-completion : expanded-view-of-addressbooks : news-post-without-validation : enable-mail-check-cue : enable-incoming-folders : save-will-advance : select-without-confirm : expanded-view-of-folders : compose-sets-newsgroup-without-confirm : show-selected-in-boldface : use-current-dir : enable-cruise-mode : no-enable-dot-files : enable-dot-folders : enable-flag-cmd : enable-flag-screen-implicitly : enable-full-header-cmd : enable-msg-view-forced-arrows : enable-search-and-replace : enable-partial-match-lists : expunge-without-confirm-everywhere : show-cursor : no-quell-lock-failure-warnings : quell-dead-letter-on-cancel : include-header-in-reply : include-text-in-reply : include-attachments-in-reply : combined-subdirectory-display : quell-empty-directories : separate-folder-and-directory-entries : compose-maps-delete-key-to-ctrl-d : enable-alternate-editor-cmd : no-enable-alternate-editor-implicitly : use-sender-not-x-sender : news-deletes-across-groups : check-newmail-when-quitting : no-alternate-compose-menu : print-offers-custom-cmd-prompt : no-reply-always-uses-reply-to : mark-for-cc : no-tab-visits-next-new-message-only : prefer-plain-text : enable-rules-under-take : enable-reply-indent-string-editing : enable-print-via-y-command : enable-suspend : enable-aggregate-command-set : news-offers-catchup-on-close : news-approximates-new-status : quell-extra-post-prompt : enable-delivery-status-notification : fcc-on-bounce : no-selectable-item-nobold : no-spell-check-before-sending : disable-sender : no-enable-8bit-esmtp-negotiation : warn-if-blank-subject : thread-index-shows-important-color : return-to-inbox-without-confirm : enable-msg-view-attachments : enable-msg-view-urls : enable-msg-view-web-hostnames : pass-control-characters-as-is : print-includes-from-line : print-formfeed-between-messages : enable-full-header-and-text : enable-goto-in-file-browser : enable-unix-pipe-cmd : confirm-role-even-for-default : enable-mouse-in-xterm : enable-newmail-in-xterm-icon : expose-hidden-config : show-plain-text-internally : slash-collapses-entire-thread : no-disable-password-caching : disable-pipes-in-sigs : disable-pipes-in-templates : disable-shared-namespaces : quell-news-envelope-update : ldap-result-to-addrbook-add : expanded-view-of-distribution-lists default-composer-hdr : From: Birl : To : Cc : Fcc : Attchmnt : Subject customized-hdrs : From: Birl : Expires : Return-Receipt-To : Reply-To : Reply-By : Expiry-Date : X-Status : Priority : X-Priority: 3 (Normal) : X-Message-Flag : Importance: Normal : Sensitivity: Normal : X-MSMail-Priority: Normal : X-CONCEPT: sbirl at concept dot temple dot edu composed this message. saved-msg-name-rule : default-folder fcc-name-rule : by-recipient sort-key : Arrival incoming-startup-rul : first-recent pruning-rule : ask-ask folder-reopen-rule : yes-ask-y threading-index-styl : coll threading-expanded-c : - editor : /bin/vi : /usr/local/bin/pico reply-indent-string : _FROM_: reply-leadin : _NEWS_("", "As it was written on _DATE_, thus _FROM_ spake unto _RECIPSANDNEWS_:", "As my eyes traversed _NEWS_, I saw the following:") image-viewer : /usr/dt/bin/sdtimage index-format : IMAPSTATUS MSGNO SMARTDATE FROMORTO(33%) SIZE SUBJECT(67%) mail-check-interval : 30 nntp-range : 1000 newsrc-path : /export/home/sbirl/.newsrc-free.teranews.com url-viewers : /usr/dt/bin/netscape news-collections : Temple NNTP *{news.temple.edu/nntp}[] : GRC.com NNTP *{news.grc.com/nntp}[] : TeraNews NNTP *{free.teranews.com/nntp}[] last-time-prune-ques : 103.8 last-version-used : 4.55 user-input-timeout : 3 printer : kinkos [] lpr -h -Pkinkos personal-print-comma : kinkos [] lpr -h -Pkinkos personal-print-categ : 3 color-style : force-ansi-8color current-indexline-st : flip-colors titlebar-color-style : indexline normal-foreground-co : black normal-background-co : color015 quote1-foreground-co : color012 quote1-background-co : color015 quote3-foreground-co : color012 quote3-background-co : color015 prompt-foreground-co : white prompt-background-co : black index-important-fore : color015 index-important-back : color009 index-deleted-foregr : color011 index-deleted-backgr : black index-unseen-foregro : color012 index-unseen-backgro : color014 ======= PostloadUser_val options set (postload) ======= ======= Global_val options set (/usr/local/lib/pine.conf) ======= inbox-path : inbox default-fcc : sent-mail default-saved-msg-fo : saved-messages postponed-folder : postponed-msgs signature-file : .signature saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last folder-sort-rule : alphabetical goto-default-rule : inbox-or-folder-in-recent-collection incoming-startup-rul : first-unseen pruning-rule : ask-ask folder-reopen-rule : ask-no-n threading-display-st : struct threading-index-styl : exp threading-indicator- : > threading-expanded-c : . threading-lastreply- : | composer-wrap-column : 74 reply-indent-string : > reply-leadin : default empty-header-message : undisclosed-recipients use-only-domain-name : no bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu suggest-fullname : Pine Developers suggest-address : pine-suggestions@cac.washington.edu local-fullname : Local Support local-address : postmaster kblock-passwd-count : 1 viewer-overlap : 2 scroll-margin : 0 status-message-delay : 0 mail-check-interval : 150 maildrop-check-minim : 60 nntp-range : 0 mail-directory : mail folder-collections : mail/[] address-book : .addressbook standard-printer : lp user-input-timeout : 0 remote-abook-history : 3 remote-abook-validit : 5 printer : attached-to-ansi elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no color-style : no-color current-indexline-st : flip-colors titlebar-color-style : default normal-foreground-co : black normal-background-co : cyan ======= Fixed_val options set (NO pine.conf.fixed) ======= ========== Feature settings ========== no-alternate-compose-menu no-compose-cut-from-cursor compose-maps-delete-key-to-ctrl-d no-compose-rejects-unqualified-addrs no-compose-send-offers-first-filter enable-alternate-editor-cmd no-enable-alternate-editor-implicitly enable-search-and-replace no-enable-sigdashes quell-dead-letter-on-cancel no-spell-check-before-sending no-quell-user-lookup-in-passwd-file enable-reply-indent-string-editing include-attachments-in-reply include-header-in-reply include-text-in-reply no-reply-always-uses-reply-to no-signature-at-bottom no-strip-from-sigdashes-on-reply disable-sender no-enable-8bit-esmtp-negotiation no-enable-background-sending enable-delivery-status-notification no-enable-verbose-smtp-posting fcc-on-bounce no-fcc-only-without-confirm no-fcc-without-attachments no-mark-fcc-seen no-send-without-confirm use-sender-not-x-sender no-warn-if-blank-to-and-cc-and-newsgroups warn-if-blank-subject combined-subdirectory-display no-combined-folder-display enable-dot-folders enable-incoming-folders no-enable-lame-list-mode expanded-view-of-folders quell-empty-directories separate-folder-and-directory-entries no-single-column-folder-list no-vertical-folder-list no-combined-addrbook-display expanded-view-of-addressbooks expanded-view-of-distribution-lists ldap-result-to-addrbook-add no-auto-open-next-unread thread-index-shows-important-color no-continue-tab-without-confirm delete-skips-deleted enable-cruise-mode no-enable-cruise-mode-delete mark-for-cc no-next-thread-without-confirm return-to-inbox-without-confirm no-tab-visits-next-new-message-only enable-msg-view-attachments enable-msg-view-urls enable-msg-view-web-hostnames no-enable-msg-view-addresses enable-msg-view-forced-arrows prefer-plain-text pass-control-characters-as-is compose-sets-newsgroup-without-confirm no-enable-8bit-nntp-posting news-approximates-new-status news-deletes-across-groups news-offers-catchup-on-close news-post-without-validation no-news-read-in-newsrc-order quell-extra-post-prompt enable-print-via-y-command print-offers-custom-cmd-prompt print-includes-from-line no-print-index-enabled print-formfeed-between-messages enable-aggregate-command-set no-enable-arrow-navigation no-enable-arrow-navigation-relaxed enable-bounce-cmd no-enable-exit-via-lessthan-command enable-flag-cmd enable-flag-screen-implicitly enable-full-header-cmd enable-full-header-and-text enable-goto-in-file-browser enable-jump-shortcut enable-partial-match-lists enable-tab-completion enable-unix-pipe-cmd no-allow-talk no-assume-slow-link no-auto-move-read-msgs no-auto-unzoom-after-apply no-auto-zoom-after-select check-newmail-when-quitting confirm-role-even-for-default no-disable-2022-jp-conversions no-disable-charset-conversions no-disable-keymenu no-disable-take-last-comma-first no-enable-dot-files no-enable-fast-recent-test enable-mail-check-cue enable-mouse-in-xterm enable-newmail-in-xterm-icon enable-rules-under-take enable-suspend no-enable-take-export expose-hidden-config no-expunge-only-manually expunge-without-confirm expunge-without-confirm-everywhere no-preserve-start-stop-characters no-quell-attachment-extra-prompt no-quell-content-id no-quell-timezone-comment-when-sending no-quell-folder-internal-msg no-quell-lock-failure-warnings no-quell-status-message-beeping quit-without-confirm save-will-advance no-save-will-not-delete no-save-will-quote-leading-froms no-scramble-message-id select-without-confirm show-cursor show-plain-text-internally show-selected-in-boldface slash-collapses-entire-thread no-try-alternative-authentication-driver-first no-unselect-will-not-advance use-current-dir no-use-subshell-for-suspend no-use-function-keys allow-changing-from no-cache-remote-pinerc no-disable-busy-alarm no-disable-config-cmd no-disable-keyboard-lock-cmd no-disable-password-caching no-disable-password-cmd disable-pipes-in-sigs disable-pipes-in-templates no-disable-roles-setup-cmd no-disable-roles-sig-edit no-disable-roles-template-edit no-disable-setlocale-collate disable-shared-namespaces no-disable-signature-edit-cmd no-enable-mailcap-param-substitution no-enable-setlocale-ctype no-quell-berkeley-format-timezone no-quell-imap-envelope-update no-quell-maildomain-warning quell-news-envelope-update no-quell-partial-fetching no-quell-personal-name-prompt no-quell-user-id-prompt no-save-aggregates-copy-sequence no-selectable-item-nobold no-termdef-takes-precedence Userid: sbirl Fullname: "Birl" User domain name being used "concept.temple.edu" Local Domain name being used "ocis.temple.edu" Host name being used "concept.ocis.temple.edu" Mail Domain name being used (by c-client too)"concept.temple.edu" Context mail/%s: serv:"", ref:"", view: "" new win size -----<39 132>------ Terminal type: vt100 Context %s: serv:"", ref:"", view: "" Context mail/%s: serv:"", ref:"", view: "" Context mail/.MailingLists/%s: serv:"", ref:"", view: "" Context mail/.YAHOO/%s: serv:"", ref:"", view: "" Context mail/.MSN/%s: serv:"", ref:"", view: "" Context mail/.SmartGroups/%s: serv:"", ref:"", view: "" Context {imap.temple.edu/ssl/novalidate-cert}%s: serv:imap.temple.edu/ssl/novalidate-cert, ref:"", view: "" Context {news.temple.edu/nntp}#news.%s: serv:news.temple.edu/nntp, ref:"", view: "" Context {news.grc.com/nntp}#news.%s: serv:news.grc.com/nntp, ref:"", view: "" Context {free.teranews.com/nntp}#news.%s: serv:free.teranews.com/nntp, ref:"", view: "" About to open folder "INBOX" inbox: "INBOX" === mm_exists(1928,/var/mail/sbirl) called === Opened folder "/var/mail/sbirl" with 1928 messages process_filter_patterns(stream=inbox, recent=0) Sorting by Arrival First_sorted_flagged didn't find a winner, look for undeleted First_sorted_flagged returning winner = 1928 First_sorted_flagged returning winner = 1928 ==== expire_mail called ==== ---- MAIN_MENU_SCREEN ---- ---- COMPOSE SCREEN (not in pico yet) ---- mm_list "mail/postponed-msgs": delim: '/', , no inferiors, unmarked === mm_exists(1,/export/home/sbirl/mail/postponed-msgs) called === Want_to read: n (110) Want_to read: ^T (20) Want_to read: y (121) === send called === - build_address - (Birl ) -- init_addrbooks(Closed, 0, 0, 1) -- - init_abook - - init_abook - - build_address - (Pine Discussion Forum ) - init_abook - - build_address - (Pine Discussion Forum ) - init_abook - ---- COMPOSER ---- new win size -----<39 132>------ new win size -----<39 132>------ - build_address - () ... composer returns (0x11) new win size -----<39 132>------ -- pine_encode_body: 0 pine_send:SUSPEND handling mm_list "mail/postponed-msgs": delim: '/', , no inferiors, unmarked -- pine_rfc822_output -- pine_encode_body: 0 -- pine_rfc822_output_body: 0 -- pine_rfc822_output_body: segment 156 bytes -- gf_pipe: done. Writing postponed message bold no-termdef-takes-precedence Userid: sbirl Fullname: "Birl" User domain name being used "concept.temple.edu" Local Domain name being used "ocis.temple.edu" Host name being used "concept.ocis.temple.edu" Mail Domain name being used (by c-client too)"concept.temple.edu" Context mail/%s: serv:"", ref:"", view: "" new win size -----<39 132>------ Terminal type: vt100 Context %s: serv:"", ref:"", view: "" Context mail/%s: serv:"", ref:"", view: "" Context mail/.MailingLists/%s: serv:"", ref:"", view: "" Context mail/.YAHOO/%s: serv:"", ref:"", view: "" Context mail/.MSN/%s: serv:"", ref:"", view: "" Context mail/.SmartGroups/%s: serv:"", ref:"", view: "" Context {imap.temple.edu/ssl/novalidate-cert}%s: serv:imap.temple.edu/ssl/novalidate-cert, ref:"", view: "" Context {news.temple.edu/nntp}#news.%s: serv:news.temple.edu/nntp, ref:"", view: "" Context {news.grc.com/nntp}#news.%s: serv:news.grc.com/nntp, ref:"", view: "" Context {free.teranews.com/nntp}#news.%s: serv:free.teranews.com/nntp, ref:"", view: "" About to open folder "INBOX" inbox: "INBOX" === mm_exists(1928,/var/mail/sbirl) called === Opened folder "/var/mail/sbirl" with 1928 messages process_filter_patterns(stream=inbox, recent=0) Sorting by Arrival First_sorted_flagged didn't find a winner, look for undeleted First_sorted_flagged returning winner = 1928 First_sorted_flagged returning winner = 1928 ==== expire_mail called ==== ---- MAIN_MENU_SCREEN ---- ---- COMPOSE SCREEN (not in pico yet) ---- mm_list "mail/postponed-msgs": delim: '/', , no inferiors, unmarked === mm_exists(1,/export/home/sbirl/mail/postponed-msgs) called === Want_to read: n (110) Want_to read: ^T (20) Want_to read: y (121) === send called === - build_address - (Birl ) -- init_addrbooks(Closed, 0, 0, 1) -- - init_abook - - init_abook - - build_address - (Pine Discussion Forum ) - init_abook - - build_address - (Pine Discussion Forum ) - init_abook - ---- COMPOSER ---- new win size -----<39 132>------ new win size -----<39 132>------ - build_address - () ... composer returns (0x11) new win size -----<39 132>------ -- pine_encode_body: 0 pine_send:SUSPEND handling mm_list "mail/postponed-msgs": delim: '/', , no inferiors, unmarked -- pine_rfc822_output -- pine_encode_body: 0 -- pine_rfc822_output_body: 0 -- pine_rfc822_output_body: segment 156 bytes -- gf_pipe: done. Writing postponed message done. === send returning === ---- MAIN_MENU_SCREEN ---- ---- COMPOSE SCREEN (not in pico yet) ---- mm_list "mail/postponed-msgs": delim: '/', , no inferiors, marked === mm_exists(2,/export/home/sbirl/mail/postponed-msgs) called === Want_to read: n (110) Want_to read: n (110) get_signature(/export/home/sbirl/.signature) === send called === - build_address - (Birl ) - init_abook - ---- COMPOSER ---- new win size -----<39 132>------ - build_address - () - build_address - () new win size -----<39 132>------ mt_get_file_ext : filename="/export/home/sbirl/test", end_signals(1) auger_in_signal(sig=?) about to end_tty_driver end_signals(1) Pine Panic: Received abort signal(sig=?) -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Aug 2003 01:00:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D80hxd017501; Wed, 13 Aug 2003 01:00:43 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D80cWO032388 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Aug 2003 01:00:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7D800J8017920; Wed, 13 Aug 2003 01:00:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D7vT2x009772 for ; Wed, 13 Aug 2003 00:57:29 -0700 Received: from mail.aculink.net (65-173-158-7.aculink.net [65.173.158.7]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7D7vRC1023238 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 13 Aug 2003 00:57:28 -0700 Received: from cdm01.deedsmiscentral.net ([204.118.157.191]) by mail.aculink.net (Merak 5.9.4) with ESMTP id EDA37003 for ; Wed, 13 Aug 2003 01:57:25 -0600 Received: from cdm01.deedsmiscentral.net (IDENT:redneck@localhost [127.0.0.1]) by cdm01.deedsmiscentral.net (8.12.5/8.12.5/ver) with ESMTP id h7D7uJWG018926 for ; Wed, 13 Aug 2003 01:56:19 -0600 Received: (from redneck@localhost) by cdm01.deedsmiscentral.net (8.12.5/8.12.5/Submit) id h7D7uIZV018918; Wed, 13 Aug 2003 01:56:18 -0600 Message-Id: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> Date: Wed, 13 Aug 2003 01:56:18 -0600 Reply-To: , 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: SoloCDM To: Pine Discussion Forum Subject: Invisible Attachments Content-Type: text/plain; charset=iso-8859-1 X-Sender: deedsmis@aculink.net X-To: "PINE-Info (Listproc)" X-no-archive: yes X-Uwash-Spam: Gauge=XXXXI, Probability=41%, Report='__EVITE_CTYPE, __HAS_MSGID, __SANE_MSGID, FORGED_RCVD_TRAIL, MSG_ID_ADDED_BY_MTA_3, SPAM_PHRASE_05_08, SIGNATURE_LONG_SPARSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Recently, while using PINE 4.50, I sent out an email with attachments. The recipient couldn't view the attachments. The recipient couldn't find them anywhere. When the recipient decided to forward the message to me so I could see the problem, while using M$ IE, the attachments appeared. Is PINE causing the attachments to be included without meeting all RPC requirements and is it compatible with all email readers? In the past, this hasn't happened. Has anyone else experienced this type of fluke? -- Note: When you reply to this message, please include the mailing list address and my email address in To: and/or Cc: with any proper combination ********************************************************************* Signed, SoloCDM -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Aug 2003 06:35:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDZLxd028254; Wed, 13 Aug 2003 06:35:21 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDZIWO007989 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Aug 2003 06:35:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7DDYnKH024236; Wed, 13 Aug 2003 06:34:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDXs2x009750 for ; Wed, 13 Aug 2003 06:33:54 -0700 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDXqJL032741 for ; Wed, 13 Aug 2003 06:33:53 -0700 Received: from dierauer.net ([12.210.69.236]) by attbi.com (rwcrmhc13) with SMTP id <200308131333510150046vdfe>; Wed, 13 Aug 2003 13:33:51 +0000 Message-Id: Date: Wed, 13 Aug 2003 09:33: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: David Dierauer To: Pine Discussion Forum Subject: Re: Invisible Attachments In-Reply-To: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> References: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: deedsmis@aculink.net, Pine Discussion Forum X-X-Sender: david@davids-g3.local X-Uwash-Spam: Gauge=IIIIII, Probability=6%, Report='__IN_REP_TO, __USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, RCVD_IN_UNCONFIRMED_DSBL, RCVD_IN_MULTIHOP_DSBL, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SIGNATURE_LONG_SPARSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Yes, I have seen this with Pine 4.53 on Mac OS X. One user of MS Outlook (Outlook 2003, I think? on Windows XP) can never see the attachments I send him, even though they are in his attachments folder when he checks there. -- David Dierauer david@dierauer.net On Wed, 13 Aug 2003, SoloCDM wrote: > Recently, while using PINE 4.50, I sent out an email with > attachments. The recipient couldn't view the attachments. > The recipient couldn't find them anywhere. When the recipient > decided to forward the message to me so I could see the problem, > while using M$ IE, the attachments appeared. Is PINE causing the > attachments to be included without meeting all RPC requirements > and is it compatible with all email readers? In the past, this > hasn't happened. Has anyone else experienced this type of fluke? > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Aug 2003 06:52:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDqNxd028607; Wed, 13 Aug 2003 06:52:23 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDqKof032295 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Aug 2003 06:52:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7DDpoOL083824; Wed, 13 Aug 2003 06:51:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DDpC2x009874 for ; Wed, 13 Aug 2003 06:51:13 -0700 Received: from neptun.sns-felb.debis.de (neptun.sns-felb.debis.de [53.122.101.2]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7DDp9C0030849 for ; Wed, 13 Aug 2003 06:51:11 -0700 Received: by neptun.sns-felb.debis.de; id PAA27781; Wed, 13 Aug 2003 15:51:08 +0200 Received: from unknown(53.113.82.10) by neptun.sns-felb.debis.de via smap (V5.0) id xma027768; Wed, 13 Aug 03 15:51:08 +0200 Received: from mail1.c1.dsh.de (localhost [127.0.0.1]) by dshmail1.dsh.de (8.9.1/8.8.7) with ESMTP id PAA08952; Wed, 13 Aug 2003 15:44:53 +0200 (MET DST) Received: from chnb124.clients.win.c1.dsh.de (chnb124.clients.win.c1.dsh.de [172.19.32.88]) by mail1.c1.dsh.de (8.10.0/8.10.0) with ESMTP id h7DDp6v12767; Wed, 13 Aug 2003 15:51:06 +0200 Message-Id: Date: Wed, 13 Aug 2003 15:51:06 +0200 (=?iso-8859-1?Q?Westeurop=E4ische_Sommerzeit?=) Reply-To: Rico Barth 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: Rico Barth To: Pine Discussion Forum Subject: Re: Invisible Attachments In-Reply-To: References: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: David Dierauer X-Cc: Pine Discussion Forum X-X-Sender: ribarth@galaxy.c1.dsh.de X-Uwash-Spam: Gauge=III, Probability=3%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, MSG_ID_ADDED_BY_MTA_3, REFERENCES, IN_REP_TO, WEIRD_PORT, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT, SIGNATURE_LONG_SPARSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hi David! On Wed, 13 Aug 2003, David Dierauer wrote: > Yes, I have seen this with Pine 4.53 on Mac OS X. One user of MS Outlook > (Outlook 2003, I think? on Windows XP) can never see the attachments I > send him, even though they are in his attachments folder when he checks > there. This is why the microsoft programmers have implemented the RFC for MIME-attachments in Outlook incorrectly. The RFC says [BASE64] could write with upper case or lower case characters but M$ has only coded the lower case version. Pine uses the upper case characters. Hope that helps. Bye Rico -- Dipl.-Math. Rico Barth T-Systems Systems Integration Berater BU Sachsen Anschrift: Clausstrasse 3 , 09126 Chemnitz Telefon: +49 ( 371) 5359 - 350 Telefax: +49 ( 371) 5359 - 133 Mobil: +49 ( 160) 94 82 15 82 E-Mail: Rico.Barth@t-systems.com Internet: http://www.t-systems.com PGP-Key: Fingerprint: 8A56 C021 6240 EAD5 AB42 EA2B 9B2E 1405 874C 8377 http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0x874C8377 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Wed, 13 Aug 2003 09:26:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGQOxd001416; Wed, 13 Aug 2003 09:26:24 -0700 Received: from list2.u.washington.edu (list2.u.washington.edu [140.142.14.165]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGQLof004790 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 13 Aug 2003 09:26:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7DGPoTB025706; Wed, 13 Aug 2003 09:25:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGP92x039896 for ; Wed, 13 Aug 2003 09:25:09 -0700 Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGP7JM007409 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 13 Aug 2003 09:25:08 -0700 Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGOvin018099; Wed, 13 Aug 2003 09:24:58 -0700 Received: from [128.95.135.3] ([128.95.135.3]) (authenticated bits=0) by smtp.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7DGOv4A007485 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Aug 2003 09:24:57 -0700 Message-Id: Date: Wed, 13 Aug 2003 09:24:57 -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: Steve Hubert To: Pine Discussion Forum Subject: Re: Invisible Attachments In-Reply-To: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> References: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: deedsmis@aculink.net, Pine Discussion Forum X-Uwash-Spam: Gauge=IIII, Probability=4%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Here is the help text for the pine option "quell-content-id". Maybe setting this option would help. FEATURE: quell-content-id This feature changes the behavior of Pine when sending messages. It is intended to work around a bug in Microsoft's Outlook XP mail user agent. As of this writing, Microsoft has acknowledged the bug but has not added it to the Knowledge Base. We have been told that there will be a post-SP1 hotfix for Outlook XP. This particular bug has bug fix number OfficeQFE:4781. The nature of the bug is that messages with attachments which contain a Content-ID header (which standard Pine attachments do) do not show the attachment indicator (a paperclip) when viewed with Outlook XP. So the user has no indication that the message contains an attachment. If this feature is set then Pine will remove most Content-ID headers before sending a message. If an attachment is of type MESSAGE, then the existing Content-ID headers inside the message will be left intact. This would only happen with Pine if a message was forwarded as an attachment or if a message with a message attached was forwarded. Similarly if an attachment of type MULTIPART/ALTERNATIVE is forwarded, the Content-ID headers of the alternative parts will not be removed. Because the Content-ID header is a standard part of MIME it is possible that setting this feature will break something. For example, if an attachment has a Content-ID header which is necessary for the correct functioning of that attachment, it is possible that Pine may remove that header when the attachment is forwarded. However, it seems fairly safe at this time. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 14 Aug 2003 06:14:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EDENxd011054; Thu, 14 Aug 2003 06:14:23 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EDEKof007818 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Aug 2003 06:14:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7EDDjOL056004; Thu, 14 Aug 2003 06:13:45 -0700 Received: from mxu6.u.washington.edu (mxu6.u.washington.edu [140.142.33.12]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EDCX2x015692 for ; Thu, 14 Aug 2003 06:12:33 -0700 Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mxu6.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EDCV7e011658 for ; Thu, 14 Aug 2003 06:12:31 -0700 Received: from dierauer.net ([12.210.69.236]) by attbi.com (rwcrmhc11) with SMTP id <20030814131231013007bm3ve>; Thu, 14 Aug 2003 13:12:31 +0000 Message-Id: Date: Thu, 14 Aug 2003 09:12: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: David Dierauer To: Pine Discussion Forum Subject: Re: Invisible Attachments In-Reply-To: References: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Steve Hubert X-Cc: Pine Discussion Forum X-X-Sender: david@davids-g3.local X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, FORGED_RCVD_TRAIL, IN_REP_TO, RCVD_IN_UNCONFIRMED_DSBL, RCVD_IN_MULTIHOP_DSBL, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks! That worked for me and the recipient of my emails who had previously been unable to see the attachments. -- -David david@dierauer.net On Wed, 13 Aug 2003, Steve Hubert wrote: > Here is the help text for the pine option "quell-content-id". Maybe > setting this option would help. > > FEATURE: quell-content-id > > This feature changes the behavior of Pine when sending messages. It is > intended to work around a bug in Microsoft's Outlook XP mail user agent. > As of this writing, Microsoft has acknowledged the bug but has not added > it to the Knowledge Base. We have been told that there will be a post-SP1 > hotfix for Outlook XP. This particular bug has bug fix number > OfficeQFE:4781. The nature of the bug is that messages with attachments > which contain a Content-ID header (which standard Pine attachments do) do > not show the attachment indicator (a paperclip) when viewed with Outlook > XP. So the user has no indication that the message contains an > attachment. > > If this feature is set then Pine will remove most Content-ID headers > before sending a message. If an attachment is of type MESSAGE, then the > existing Content-ID headers inside the message will be left intact. This > would only happen with Pine if a message was forwarded as an attachment > or if a message with a message attached was forwarded. Similarly if an > attachment of type MULTIPART/ALTERNATIVE is forwarded, the Content-ID > headers of the alternative parts will not be removed. > > Because the Content-ID header is a standard part of MIME it is possible > that setting this feature will break something. For example, if an > attachment has a Content-ID header which is necessary for the correct > functioning of that attachment, it is possible that Pine may remove that > header when the attachment is forwarded. However, it seems fairly safe at > this time. > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Thu, 14 Aug 2003 12:15:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJFPxd025835; Thu, 14 Aug 2003 12:15:25 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJFKof020611 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 14 Aug 2003 12:15:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7EJEkOL077730; Thu, 14 Aug 2003 12:14:47 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.32.133]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJDW2x031674 for ; Thu, 14 Aug 2003 12:13:32 -0700 Received: from mail.aculink.net (65-173-158-7.aculink.net [65.173.158.7]) by mxu3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7EJDQJM011868 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 14 Aug 2003 12:13:26 -0700 Received: from cdm01.deedsmiscentral.net ([204.118.157.95]) by mail.aculink.net (Merak 5.9.4) with ESMTP id EDA37003 for ; Thu, 14 Aug 2003 13:13:21 -0600 Received: from cdm01.deedsmiscentral.net (IDENT:redneck@cdm01.deedsmiscentral.net [192.168.20.1]) by cdm01.deedsmiscentral.net (8.12.5/8.12.5/ver) with ESMTP id h7EJ8jWH017342 for ; Thu, 14 Aug 2003 13:09:21 -0600 Message-Id: Date: Thu, 14 Aug 2003 13:08:45 -0600 (MDT) Reply-To: SoloCDM , "PINE-Info (Listproc)" 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: SoloCDM To: Pine Discussion Forum Subject: Re: Invisible Attachments In-Reply-To: References: <200308130756.h7D7uIZV018918@cdm01.deedsmiscentral.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "PINE-Info (Listproc)" X-no-archive: yes X-Priority: 3 X-Uwash-Spam: Gauge=X, Probability=10%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __IN_REP_TO, FORGED_RCVD_TRAIL, MSG_ID_ADDED_BY_MTA_3, IN_REP_TO, PRIORITY_NO_NAME, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Thanks Steve!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ********************************************************************* Signed, SoloCDM ___________________________Reply_Separator___________________________ On Wed, 13 Aug 2003, Steve Hubert wrote: > Date: Wed, 13 Aug 2003 09:24:57 -0700 (Pacific Daylight Time) > From: Steve Hubert > To: deedsmis@aculink.net, Pine Discussion Forum > Subject: Re: Invisible Attachments > > Here is the help text for the pine option "quell-content-id". Maybe > setting this option would help. > > FEATURE: quell-content-id > > This feature changes the behavior of Pine when sending messages. It > is intended to work around a bug in Microsoft's Outlook XP mail user > agent. As of this writing, Microsoft has acknowledged the bug but has > not added it to the Knowledge Base. We have been told that there will > be a post-SP1 hotfix for Outlook XP. This particular bug has bug fix > number OfficeQFE:4781. The nature of the bug is that messages with > attachments which contain a Content-ID header (which standard Pine > attachments do) do not show the attachment indicator (a paperclip) > when viewed with Outlook XP. So the user has no indication that the > message contains an attachment. > > If this feature is set then Pine will remove most Content-ID headers > before sending a message. If an attachment is of type MESSAGE, > then the existing Content-ID headers inside the message will be > left intact. This would only happen with Pine if a message was > forwarded as an attachment or if a message with a message attached was > forwarded. Similarly if an attachment of type MULTIPART/ALTERNATIVE is > forwarded, the Content-ID headers of the alternative parts will not be > removed. > > Because the Content-ID header is a standard part of MIME it is > possible that setting this feature will break something. For example, > if an attachment has a Content-ID header which is necessary for the > correct functioning of that attachment, it is possible that Pine may > remove that header when the attachment is forwarded. However, it seems > fairly safe at this time. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Fri, 15 Aug 2003 07:15:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FEF6xd027306; Fri, 15 Aug 2003 07:15:07 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FEEwof018027 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 15 Aug 2003 07:14:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7FEESKH009530; Fri, 15 Aug 2003 07:14:29 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.132]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FE8l2x035520 for ; Fri, 15 Aug 2003 07:08:47 -0700 Received: from concept.ocis.temple.edu (concept.ocis.temple.edu [155.247.27.102]) by mxu1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7FE8jdL021668 for ; Fri, 15 Aug 2003 07:08:45 -0700 Received: from concept.ocis.temple.edu (localhost [127.0.0.1]) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8) with ESMTP id h7FE8f1x000503 for ; Fri, 15 Aug 2003 10:08:41 -0400 (EDT) Received: from localhost (sbirl@localhost) by concept.ocis.temple.edu (8.12.9+Sun/8.12.8/Submit) with ESMTP id h7FE8eJt000497 for ; Fri, 15 Aug 2003 10:08:40 -0400 (EDT) Message-Id: Date: Fri, 15 Aug 2003 10:08:40 -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: Birl To: Pine Discussion Forum Subject: url-viewers feature MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: concept.ocis.temple.edu: sbirl owned process doing -bs X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-CONCEPT: sbirl at concept dot temple dot edu composed this message. X-Uwash-Spam: Gauge=XXXXI, Probability=41%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, X_AUTH_WARNING, PRIORITY_NO_NAME, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE, MISSING_MIMEOLE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I have my Pine 4.55 setup with: url-viewers = /usr/dt/bin/netscape But it never runs in the background. I cannot append the & to the end. Anyway to get url-viewers to run the background? Thanks. Birl -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Sat, 16 Aug 2003 22:53:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7H5rNxd022769; Sat, 16 Aug 2003 22:53:23 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7H5rLWO019382 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 16 Aug 2003 22:53:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7H5qmOL077654; Sat, 16 Aug 2003 22:52:48 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7H5pZ2x046216 for ; Sat, 16 Aug 2003 22:51:35 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7H5pWC1007458 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Sat, 16 Aug 2003 22:51:33 -0700 Received: from sdf.lonestar.org (ol.freeshell.org [192.94.73.20]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7H5pVoe009027 for ; Sat, 16 Aug 2003 22:51:31 -0700 Received: from sdf.lonestar.org (IDENT:bluesman@norge.freeshell.org [192.94.73.3]) by sdf.lonestar.org (8.12.9/8.12.8) with ESMTP id h7H5pQEK016147 for ; Sun, 17 Aug 2003 05:51:26 GMT Received: (from bluesman@localhost) by sdf.lonestar.org (8.12.9/8.12.8/Submit) id h7H5pPB3016707; Sun, 17 Aug 2003 05:51:25 GMT Message-Id: Date: Sun, 17 Aug 2003 05:51:25 +0000 (UTC) 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: jack zimmerman To: Pine Discussion Forum Subject: security problem in pine 4.33 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-X-Sender: bluesman@norge.freeshell.org X-Uwash-Spam: Gauge=XI, Probability=11%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, SPAM_PHRASE_03_05, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Howdy good people. Well this is a poser but I reckon I'm in the right place. I'm switching isp's. Not happy with earthlink anymore. too much for too little, however be that as it may, when I try and log onto the pop3 server using my local addition of pine it says security problem insecure server advertised pop3 authentication cancelled So I give tech support at ev1.net a clang and they said that most email clients have a security setting that needs to be unchecked to use their system. So I went and looked in the pine config but could not find anything like that to do with security, and boys and girls they's a lot you can configure. Anybody got any clues on this one?? If you need any further illucidation let me know. I wanna use this isp like really bad. Save me 11 bucks a month. On the advice of a friend I tried putting /notls after the pop 3 server address, and got a totally new error message saying auth plain. near as I could make out I'm a blind fella using a braille display. also checked out the pine tech notes and found disable-these-authenticators, but couldn't find that listing in the config of my version of pine 4.33. I should perhaps tell you I'm using the braille notetaker called the elba 20 Please send any and all helpful hints or insulting remarks to mailto:bluesman@sdf.lonestar.org thanks for any help. at all.. Jack -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Mon, 18 Aug 2003 23:59:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J6xWxd012284; Mon, 18 Aug 2003 23:59:32 -0700 Received: from list4.u.washington.edu (list4.u.washington.edu [140.142.14.167]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J6xRWO000971 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 18 Aug 2003 23:59:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7J6wuOL091002; Mon, 18 Aug 2003 23:58:56 -0700 Received: from mxu5.u.washington.edu (mxu5.u.washington.edu [140.142.32.164]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J6vm2x056904 for ; Mon, 18 Aug 2003 23:57:48 -0700 Received: from ella.pscs.org (ella.pscs.org [216.231.32.24]) by mxu5.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7J6vlrM013371 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 18 Aug 2003 23:57:48 -0700 Received: from ella.pscs.org (localhost [127.0.0.1]) by ella.pscs.org (8.12.8/8.12.8) with ESMTP id h7J6vlBZ003315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Aug 2003 23:57:47 -0700 Received: from localhost (andy@localhost) by ella.pscs.org (8.12.8/8.12.8/Submit) with ESMTP id h7J6vlYI003311 for ; Mon, 18 Aug 2003 23:57:47 -0700 Message-Id: Date: Mon, 18 Aug 2003 23:57: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: Andy Smallman To: Pine Discussion Forum Subject: ^O Command in OSX MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info List X-Authentication-Warning: ella.pscs.org: andy owned process doing -bs X-Uwash-Spam: Gauge=IIIIIIIII, Probability=9%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, X_AUTH_WARNING, SPAM_PHRASE_00_01, SIGNATURE_SHORT_DENSE' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN Hey All, I just upgraded my Mac to OSX and am using Terminal to get to my server's shell and to Pine. All of my command keys work in Pine except ^O, Postpone. I've gone through every configuration option in Terminal I can find and can't seem to figure out why ^O will not work. Can anyone solve this frustrating problem for me?? Thanks so much, ---Andy =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Andrew Smallman, Director Puget Sound Community School andy@pscs.org || http://www.pscs.org (206) 324-4350 =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ -- ----------------------------------------------------------------- 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-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 19 Aug 2003 08:02:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JF2exd028346; Tue, 19 Aug 2003 08:02:40 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JF2aWO013584 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 08:02:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7JF26J8030980; Tue, 19 Aug 2003 08:02:06 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JF0x2x037654 for ; Tue, 19 Aug 2003 08:00:59 -0700 Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JF0rC0005874 for ; Tue, 19 Aug 2003 08:00:53 -0700 Received: from dierauer.net ([12.210.69.236]) by attbi.com (rwcrmhc13) with SMTP id <2003081915005201500a2bdre>; Tue, 19 Aug 2003 15:00:52 +0000 Message-Id: Date: Tue, 19 Aug 2003 11:00: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: David Dierauer To: Pine Discussion Forum Subject: Re: ^O Command in OSX In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Andy Smallman X-Cc: Pine Discussion Forum X-X-Sender: david@davids-g3.local X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, FORGED_RCVD_TRAIL, REFERENCES, IN_REP_TO, RCVD_IN_UNCONFIRMED_DSBL, RCVD_IN_MULTIHOP_DSBL, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN I use pine 4.53 (installed by fink) on OS X, 10.2.6, and do not see this problem. I have always been able to postpone messages using ^O in the Terminal. (You are using the letter 'o', not the number zero, right?) Feel free to email me privately for details on my Terminal configuration. -- -David david@dierauer.net On Mon, 18 Aug 2003, Andy Smallman wrote: > Hey All, > > I just upgraded my Mac to OSX and am using Terminal to get to my server's > shell and to Pine. All of my command keys work in Pine except ^O, > Postpone. I've gone through every configuration option in Terminal I can > find and can't seem to figure out why ^O will not work. Can anyone solve > this frustrating problem for me?? > > Thanks so much, > > ---Andy > > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ > Andrew Smallman, Director > Puget Sound Community School > andy@pscs.org || http://www.pscs.org > (206) 324-4350 > =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 19 Aug 2003 09:24:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGOAxd014261; Tue, 19 Aug 2003 09:24:10 -0700 Received: from list3.u.washington.edu (list3.u.washington.edu [140.142.8.100]) by mx2.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGO6of007792 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 09:24:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list3.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7JGNRKH009556; Tue, 19 Aug 2003 09:23:27 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGMe2x043864 for ; Tue, 19 Aug 2003 09:22:41 -0700 Received: from niwot.scd.ucar.edu (niwot.scd.ucar.edu [128.117.8.223]) by mxu2.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGMaC0001735 for ; Tue, 19 Aug 2003 09:22:37 -0700 Received: from sedona.scd.ucar.edu (sedona.scd.ucar.edu [128.117.8.183]) by niwot.scd.ucar.edu (8.11.7+Sun/8.9.1) with ESMTP id h7JGMUU05740; Tue, 19 Aug 2003 10:22:30 -0600 (MDT) Received: from sedona.scd.ucar.edu (localhost [IPv6:::1]) by sedona.scd.ucar.edu (8.12.9+Sun/8.12.5) with ESMTP id h7JGMUjX015060; Tue, 19 Aug 2003 10:22:30 -0600 (MDT) Received: from localhost (era@localhost) by sedona.scd.ucar.edu (8.12.9+Sun/8.12.5/Submit) with ESMTP id h7JGMT9T015057; Tue, 19 Aug 2003 10:22:29 -0600 (MDT) Message-Id: Date: Tue, 19 Aug 2003 10:22:29 -0600 (MDT) Reply-To: era@ucar.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: Ed Arnold To: Pine Discussion Forum Subject: Re: url-viewers feature In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Birl 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-Uwash-Spam: Gauge=I, Probability=1%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, X_AUTH_WARNING, IN_REP_TO, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Fri, 15 Aug 2003, Birl wrote: > I have my Pine 4.55 setup with: > url-viewers = /usr/dt/bin/netscape > > But it never runs in the background. I cannot append the & to the end. > Anyway to get url-viewers to run the background? > > > > Thanks. > Birl We've kicked this solution around on -discussion. My .pinerc reads: url-viewers=/fs/scd/home0/era/bin/ns7 The "ns7" script invokes netscape7 into the background. The baroque "if" tests are left over from netscape4 and probably don't work correctly for netscape7, er, mozilla. #!/bin/sh # short script to invoke netscape7 from within pine as a background # process, so pine can continue. Only arg is the URL. # Author: Ed Arnold , but modified by Mike Miller & John # Soper NETSCAPE=/fs/local/bin/netscape7 URL=`echo $1 | sed 's/,/%2C/g'` # # handle viewing HTML attachment or message files # ATTACH=`echo $URL | grep /tmp/img-HTM | wc -l` if [ $ATTACH = 1 ]; then cp $URL ${URL}.html URL=${URL}.html fi trap "" 1 2 3 13 15 18 # nohup blows LOCK=`/bin/find $HOME/.mozilla -name lock -print` if [ -h "$LOCK" ]; then cmd="$NETSCAPE -noraise -remote openURL($URL)" $cmd & else cmd="$NETSCAPE $URL" $cmd & fi From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-2000(13) (invoked by user mailnull) for mailarch+pine-info; Tue, 19 Aug 2003 09:27:39 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.140]) by groupms.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGRdxd016139; Tue, 19 Aug 2003 09:27:39 -0700 Received: from list1.u.washington.edu (list1.u.washington.edu [140.142.8.99]) by mx1.cac.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGRQWO019615 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 19 Aug 2003 09:27:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by list1.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with SMTP id h7JGQwJ8037736; Tue, 19 Aug 2003 09:26:58 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGQM2x046994 for ; Tue, 19 Aug 2003 09:26:22 -0700 Received: from post.webmailer.de (natsmtp01.webmailer.de [192.67.198.81]) by mxu4.u.washington.edu (8.12.9+UW03.06/8.12.9+UW03.06) with ESMTP id h7JGQASB007246 for ; Tue, 19 Aug 2003 09:26:11 -0700 Received: from localhost (ACB0003E.ipt.aol.com [172.176.0.62]) by post.webmailer.de (8.12.9/8.8.7) with ESMTP id h7JGQ5fc002010; Tue, 19 Aug 2003 18:26:05 +0200 (MEST) Received: by localhost (Postfix, from userid 501) id EEE262FE52F; Tue, 19 Aug 2003 09:31:30 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 837312FE529; Tue, 19 Aug 2003 09:31:30 +0200 (CEST) Message-Id: Date: Tue, 19 Aug 2003 09:31:30 +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: Claus Atzenbeck To: Pine Discussion Forum Subject: Re: ^O Command in OSX In-Reply-To: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Andy Smallman X-Cc: Pine Discussion Forum X-X-Sender: claus@cumulus.local X-Uwash-Spam: Gauge=II, Probability=2%, Report='__USER_AGENT_PINE, __HAS_MSGID, __SANE_MSGID, __IN_REP_TO, __REFERENCES, REFERENCES, IN_REP_TO, X_OSIRU_DUL_FH, RCVD_IN_OSIRUSOFT_COM, EMAIL_ATTRIBUTION, QUOTED_EMAIL_TEXT' X-Listprocessor-Version: 8.1 -- ListProcessor(tm) by CREN On Mon, 18 Aug 2003, Andy Smallman wrote: > I just upgraded my Mac to OSX and am using Terminal to get to my server's > shell and to Pine. All of my command keys work in Pine except ^O, > Postpone. I've gone through every configuration option in Terminal I can > find and can't seem to figure out why ^O will not work. Can anyone solve > this frustrating problem for me?? I have experienced similar problems with ^U in editor mode. Use + + . This should work. Claus