From pinedev@shiva0.cac.washington.edu Thu Oct 1 01:35:14 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 01:35:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA30431 for ; Thu, 1 Oct 1998 01:35:13 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA11638; Thu, 1 Oct 1998 01:35:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA19342; Thu, 1 Oct 1998 01:33:39 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA32690 for ; Thu, 1 Oct 1998 01:31:27 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA32662 for ; Thu, 1 Oct 1998 01:31:25 -0700 Received: from fireball.control-risks.de (port249.koeln.ndh.net [195.94.92.249]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id KAA14867 for ; Thu, 1 Oct 1998 10:31:21 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id KAA27207; Thu, 1 Oct 1998 10:05:58 +0200 Message-Id: <19981001100557.A27138@fireball.control-risks.de> Date: Thu, 1 Oct 1998 10:05:57 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Filtering (was: Re: 4.05 wierdness) In-Reply-To: ; from Ian Hall-Beyer on Wed, Sep 30, 1998 at 06:18:11PM -0600 References: <361277CC.30A2FA9D@mcps.k12.md.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Ian Hall-Beyer (manuka@rmi.net): > On Wed, 30 Sep 1998, Carmen Dennis wrote: > > > Does anybody know of a way, using PINE, to only accept messages within a > > certain size limit OR how to filter out messages from a specified > > recipient. > > AFAIK, Pine does not do this natively. This is the domain of mail processors > such as procmail. I can't remember the URL off the top of my head, but there > is a good FAQ on setting up filters using procmail. Actually, it should be done by the MTA, eg fetchmail, not by the MDA. Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Thu Oct 1 01:48:54 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 01:48:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA27520 for ; Thu, 1 Oct 1998 01:48:52 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA11800; Thu, 1 Oct 1998 01:48:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA08366; Thu, 1 Oct 1998 01:45:41 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA32536 for ; Thu, 1 Oct 1998 01:43:58 -0700 Received: from mg2.rockymtn.net (mailserv.rockymtn.net [166.93.205.12]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA10755 for ; Thu, 1 Oct 1998 01:43:58 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg2.rockymtn.net (8.8.7/8.8.7) with ESMTP id CAA29559 for ; Thu, 1 Oct 1998 02:43:56 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id CAA21988 for ; Thu, 1 Oct 1998 02:41:37 -0600 (MDT) Message-Id: Date: Thu, 1 Oct 1998 02:39:59 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Filtering (was: Re: 4.05 wierdness) In-Reply-To: <19981001100557.A27138@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 1 Oct 1998, Robin S. Socha wrote: > Actually, it should be done by the MTA, eg fetchmail, not by the MDA. Well, that would depend on the type of filtering you want to do. Spam/Domain blocking would definitely be done by the MTA. A user who wants to sort his mail out is more the domain of utilities like fetchmail, or in some cases, the client itself (but not pine). -Ian From pinedev@shiva0.cac.washington.edu Thu Oct 1 02:59:09 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 02:59:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id CAA29898 for ; Thu, 1 Oct 1998 02:59:05 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA04885; Thu, 1 Oct 1998 02:31:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA08887; Thu, 1 Oct 1998 02:30:02 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA14086 for ; Thu, 1 Oct 1998 02:28:16 -0700 Received: from lancaster.nexor.co.uk (lancaster.nexor.co.uk [128.243.9.1]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA29989 for ; Thu, 1 Oct 1998 02:28:15 -0700 Received: from skyhawk.nexor.co.uk by lancaster.nexor.co.uk with SMTP (NEXOR MMTA 2.2) with ESMTP; Thu, 1 Oct 1998 10:28:11 +0100 Message-Id: Date: Thu, 1 Oct 1998 10:28:09 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: John Berthels To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: <1956992.3116166880@pippin.york.ac.uk> MIME-Version: 1.0 Content-Type: text/PLAIN; charset="US-ASCII" X-To: Mike Brudenell X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > The idea is to set the mail spool directory so that any user can create a > > new file in it. This is needed so that Pine can write its lock file. Is there a DoS vulnerability with users creating pseudo lock-files in the spool directory? e.g. /usr/spool/mail/victim already exists and is mode 600, spool itself is mode 1777. Can user 'nasty' create /usr/spool/mail/victim.lock (or similar named file) and leave it there, so that even though mail gets delivered, etc pine will think the mailbox is locked? Or is the locking not implented this way? jb -- John Berthels Email: j.berthels@nexor.co.uk X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ From pinedev@shiva0.cac.washington.edu Thu Oct 1 03:01:39 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 03:01:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA28205 for ; Thu, 1 Oct 1998 03:01:32 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA12407; Thu, 1 Oct 1998 02:39:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA19568; Thu, 1 Oct 1998 02:38:32 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA20436 for ; Thu, 1 Oct 1998 02:36:42 -0700 Received: from tilmax.tatainfotech.co.in (tilmax.tatainfotech.co.in [202.54.16.130]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA02220 for ; Thu, 1 Oct 1998 02:36:38 -0700 Received: from seepzmail.in.tatainfotech.com (163-122-3222.unisys.com [163.122.32.22]) by tilmax.tatainfotech.co.in (8.7.4/8.7.3) with SMTP id OAA13427 for ; Thu, 1 Oct 1998 14:56:03 +0530 Received: from seepzmail by seepzmail.in.tatainfotech.com (8.6.10/SMI-4.1) id JAA27301; Thu, 1 Oct 1998 09:46:10 GMT Message-Id: Date: Thu, 1 Oct 1998 15:16:10 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nayan Jain To: Pine Discussion Forum Subject: Random Signature ! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: nayan.jain@seepzmail X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi All ! I have about 100 files which i would like to use as my signature file. Now the problem is that if i write anything in signature file (.signature) then it is constant till i change it to some other file. What i want is to randomly take any signature from 100 files that i have and append it to my mail whenever i compose it. Also can there be a provision that it ask me for appending a signature or not. Any and Every tips will be appreciated. Thanks , Nayan..! ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Oct 1 03:35:20 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 03:35:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA25943 for ; Thu, 1 Oct 1998 03:35:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA13155; Thu, 1 Oct 1998 03:35:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA20085; Thu, 1 Oct 1998 03:34:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA37788 for ; Thu, 1 Oct 1998 03:31:27 -0700 Received: from hex.de.uu.net (hex.de.uu.net [192.76.144.27]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA31882 for ; Thu, 1 Oct 1998 03:31:26 -0700 Received: from gate1.ife-le.de (gate1.ife-le.de [194.115.104.202]:1269) by hex.de.uu.net with ESMTP (5.65+:004/3.0.2) id MAB11349; Thu, 1 Oct 1998 12:30:18 +0200 (MET DST) Received: by gate1.ife-le.de with esmtp (Exim 2.03 #1) id 0zOfwZ-0007Tu-00; Thu, 1 Oct 1998 12:26:43 +0200 Received: with local-esmtp (Exim 2.03 #1) id 0zOfwY-0000nm-01; Thu, 1 Oct 1998 12:26:42 +0200 Message-Id: <0zOfwZ-0007Tu-00@ife-le.de> Date: Thu, 1 Oct 1998 12:26:41 +0200 (MET DST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Rudolf Kompf To: Pine Discussion Forum Subject: Re: Random Signature ! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nayan Jain X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Set "signature-file" in your .pinerc empty and write a sending-filter (see HELP for option "sending-filters") Hope this helps Rudolf On Thu, 1 Oct 1998, Nayan Jain wrote: -> Date: Thu, 1 Oct 1998 15:16:10 +0530 (IST) -> From: Nayan Jain -> To: Pine Discussion Forum -> Subject: Random Signature ! -> -> Hi All ! -> -> I have about 100 files which i would like to use as my signature file. -> Now the problem is that if i write anything in signature file (.signature) -> then it is constant till i change it to some other file. -> -> What i want is to randomly take any signature from 100 files that i have -> and append it to my mail whenever i compose it. -> -> Also can there be a provision that it ask me for appending a signature or -> not. -> -> Any and Every tips will be appreciated. -> Thanks , -> Nayan..! -- ----------------------------------------------------------------------- Rudolf Kompf | E-mail: kompf@ife-le.de From pinedev@shiva0.cac.washington.edu Thu Oct 1 04:31:12 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 04:31:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA00050 for ; Thu, 1 Oct 1998 04:31:11 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA14091; Thu, 1 Oct 1998 04:30:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA20935; Thu, 1 Oct 1998 04:29:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA24938 for ; Thu, 1 Oct 1998 04:27:48 -0700 Received: from mg2.rockymtn.net (mailserv.rockymtn.net [166.93.205.12]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA01266 for ; Thu, 1 Oct 1998 04:27:48 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg2.rockymtn.net (8.8.7/8.8.7) with ESMTP id FAA01034 for ; Thu, 1 Oct 1998 05:27:47 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id FAA07892 for ; Thu, 1 Oct 1998 05:25:27 -0600 (MDT) Message-Id: Date: Thu, 1 Oct 1998 05:23:47 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Random Signature ! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 1 Oct 1998, Nayan Jain wrote: > What i want is to randomly take any signature from 100 files that i have > and append it to my mail whenever i compose it. I have seen some perl-based random .signature scripts out there. I suspect you can find someting in comp.mail.pine. I think all you have to do is put the script itself in your signature file, and then have the script read from a data file (such as a fortune database) and randomly pull something from it. HTH, -Ian From pinedev@shiva0.cac.washington.edu Thu Oct 1 05:58:11 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 05:58:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id FAA31564 for ; Thu, 1 Oct 1998 05:58:10 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA15109; Thu, 1 Oct 1998 05:58:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA22998; Thu, 1 Oct 1998 05:55:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA43540 for ; Thu, 1 Oct 1998 05:28:49 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA19171 for ; Thu, 1 Oct 1998 05:28:48 -0700 Received: from fireball.control-risks.de (port221.koeln.ndh.net [195.94.92.221]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id OAA12060 for ; Thu, 1 Oct 1998 14:28:44 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id OAA28935; Thu, 1 Oct 1998 14:07:44 +0200 Message-Id: <19981001140743.D28565@fireball.control-risks.de> Date: Thu, 1 Oct 1998 14:07:43 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Random Signature ! In-Reply-To: ; from Ian Hall-Beyer on Thu, Oct 01, 1998 at 05:23:47AM -0600 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Ian Hall-Beyer (manuka@rmi.net): > On Thu, 1 Oct 1998, Nayan Jain wrote: > > > What i want is to randomly take any signature from 100 files that i have > > and append it to my mail whenever i compose it. > > I have seen some perl-based random .signature scripts out there. I suspect > you can find someting in comp.mail.pine. I'm still looking for some more of these for this page: > I think all you have to do is put the script itself in your signature file, > and then have the script read from a data file (such as a fortune database) > and randomly pull something from it. Having it as a sending filter should be much more convenient. The sad thing about pine not having hooks likt mutt or Gnus is that it isn't exactly straightforward to implement nested sending filters (actually, the inability to toy around with pgp *and* a sig selector made me check mutt in the first place). Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Thu Oct 1 06:32:53 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 06:32:53 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA03043 for ; Thu, 1 Oct 1998 06:32:52 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA15643; Thu, 1 Oct 1998 06:32:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA24537; Thu, 1 Oct 1998 06:31:22 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA39082 for ; Thu, 1 Oct 1998 06:29:32 -0700 Received: from mailhost.cybermania.net.ma (root@[194.204.198.70]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA08509 for ; Thu, 1 Oct 1998 06:29:31 -0700 Received: from mailhost.cybermania.net.ma (tdaoud@mailhost.cybermania.net.ma [194.204.198.70]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id NAA18566; Thu, 1 Oct 1998 13:17:56 GMT Message-Id: Date: Thu, 1 Oct 1998 13:17:56 +0000 (WET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: John Berthels X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Is there a DoS vulnerability with users creating pseudo lock-files in the > spool directory? The lock files are created in order to protect the INBOX files from corruption. > e.g. /usr/spool/mail/victim already exists and is mode 600, spool itself > is mode 1777. > > Can user 'nasty' create /usr/spool/mail/victim.lock (or similar named > file) and leave it there, so that even though mail gets delivered, etc > pine will think the mailbox is locked? > > Or is the locking not implented this way? I guess the best explanation so far came from Tim DiLauro : ===== Start Quote ===== "The idea is to set the mail spool directory so that any user can create a new file in it. This is needed so that Pine can write its lock file. And mode 1777 does not mean world writeable, although it might look that way. Mode 1777 means that any user can create/rename/delete (basically do directory operations for) a file that is owned by that user. You can't do these things to other people's files. Individuals mailboxes should have the protections that they need to work with your mail system -- ideally they are mode 600 (read/write by the owner only)." ===== End Quote ===== -Tawfik _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Thu Oct 1 06:46:02 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 06:46:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA06496 for ; Thu, 1 Oct 1998 06:46:01 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA15837; Thu, 1 Oct 1998 06:45:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA13842; Thu, 1 Oct 1998 06:44:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA42950 for ; Thu, 1 Oct 1998 06:42:27 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA24428 for ; Thu, 1 Oct 1998 06:42:26 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id HAA23725 for ; Thu, 1 Oct 1998 07:42:25 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id HAA04935 for ; Thu, 1 Oct 1998 07:40:05 -0600 (MDT) Message-Id: Date: Thu, 1 Oct 1998 07:38:28 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 1 Oct 1998, Tawfik Daoud wrote: > Individuals mailboxes should have the protections that they need to work > with your mail system -- ideally they are mode 600 (read/write by the > owner only)." Indeed. However, for some strange reason, Pine on my machine also wants exec permission on that folder. so 700 it is. -Ian From pinedev@shiva0.cac.washington.edu Thu Oct 1 07:49:35 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 07:49:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA22090 for ; Thu, 1 Oct 1998 07:49:34 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA09676; Thu, 1 Oct 1998 07:49:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA27561; Thu, 1 Oct 1998 07:47:24 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA40386 for ; Thu, 1 Oct 1998 07:42:44 -0700 Received: from lcjdap.soroscj.ro (lcjdap.soroscj.ro [193.226.84.253]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA29477 for ; Thu, 1 Oct 1998 07:42:41 -0700 Received: (qmail 2011 invoked by uid 723); 1 Oct 1998 14:46:12 -0000 Message-Id: Date: Thu, 1 Oct 1998 17:46:12 +0300 (EEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: PINE list To: Pine Discussion Forum Subject: Maildir support for pine 4.05 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Really isn't out there anyone who can make a patch for pine 4.05 to support maildir style inbox format? There are lotsa people waiting for it... I am one too... :( ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Oct 1 08:27:42 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 08:27:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA15636 for ; Thu, 1 Oct 1998 08:27:41 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA17877; Thu, 1 Oct 1998 08:27:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA29503; Thu, 1 Oct 1998 08:26:13 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA38918 for ; Thu, 1 Oct 1998 08:23:18 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA23682 for ; Thu, 1 Oct 1998 08:23:16 -0700 Received: from fireball.control-risks.de (port217.koeln.ndh.net [195.94.92.217]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id RAA06913 for ; Thu, 1 Oct 1998 17:23:13 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id RAA30014; Thu, 1 Oct 1998 17:03:52 +0200 Message-Id: <19981001170352.B29997@fireball.control-risks.de> Date: Thu, 1 Oct 1998 17:03:52 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Maildir support for pine 4.05 In-Reply-To: ; from PINE list on Thu, Oct 01, 1998 at 05:46:12PM +0300 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting PINE list (pine-l@lcjdap.soroscj.ro): Your parents must hate you, DuDE... > Really isn't out there anyone who can make a patch for pine 4.05 > to support maildir style inbox format? > > There are lotsa people waiting for it... I am one too... :( Quit whining, start coding. For someone with a butt ugly name, you're pretty demanding. You know... free software: contribute nothing, expect nothing. Damn, life can be, like, real easy and stuff... Ro"youreusing4.02anyway"bin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Thu Oct 1 08:52:20 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 08:52:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA00663 for ; Thu, 1 Oct 1998 08:52:18 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA11538; Thu, 1 Oct 1998 08:52:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA20614; Thu, 1 Oct 1998 08:49:44 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA42916 for ; Thu, 1 Oct 1998 08:46:58 -0700 Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA04599 for ; Thu, 1 Oct 1998 08:46:57 -0700 Received: from dawn.cs.rice.edu (dawn.cs.rice.edu [128.42.1.127]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id KAA12658; Thu, 1 Oct 1998 10:46:56 -0500 (CDT) Received: (from srampell@localhost) by dawn.cs.rice.edu (8.9.0/8.9.0) id KAA06104; Thu, 1 Oct 1998 10:46:55 -0500 (CDT) Message-Id: Date: Thu, 1 Oct 1998 10:46:55 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Sonny To: Pine Discussion Forum Subject: Re: Maildir support for pine 4.05 In-Reply-To: <19981001170352.B29997@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Robin .... I'm amazed by this reponse and flatout out of words to reply in a professional way. 1. My parents have nothing to do with this and they had more love and passion than you will ever experience. 2. I'm PROUD of my name and family name. 3. If whining is refering to asking for assistance then that is your problem. 4. Contribute nothing . expect nothing ????? Get a class in communication !!!! Sal J. Rampelli On Thu, 1 Oct 1998, Robin S. Socha wrote: > Quoting PINE list (pine-l@lcjdap.soroscj.ro): > > Your parents must hate you, DuDE... > > > Really isn't out there anyone who can make a patch for pine 4.05 > > to support maildir style inbox format? > > > > There are lotsa people waiting for it... I am one too... :( > > Quit whining, start coding. For someone with a butt ugly name, you're pretty > demanding. You know... free software: contribute nothing, expect nothing. > Damn, life can be, like, real easy and stuff... > > Ro"youreusing4.02anyway"bin > > -- > Robin S. Socha > > From pinedev@shiva0.cac.washington.edu Thu Oct 1 09:19:37 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 09:19:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA06336 for ; Thu, 1 Oct 1998 09:19:35 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA12606; Thu, 1 Oct 1998 09:19:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA02993; Thu, 1 Oct 1998 09:17:55 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA27802 for ; Thu, 1 Oct 1998 09:15:14 -0700 Received: from pilsener.ucs.ualberta.ca (pilsener.ucs.ualberta.ca [129.128.5.19]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA30762 for ; Thu, 1 Oct 1998 09:15:12 -0700 Received: from gpu5.srv.ualberta.ca (gpu5.srv.ualberta.ca [129.128.98.19]) by pilsener.ucs.ualberta.ca (8.9.0/8.9.0) with ESMTP id KAA09262 for ; Thu, 1 Oct 1998 10:15:11 -0600 (MDT) Received: from localhost (maldridg@localhost) by gpu5.srv.ualberta.ca (8.8.5/8.8.5) with SMTP id KAA84392 for ; Thu, 1 Oct 1998 10:15:11 -0600 Message-Id: Date: Thu, 1 Oct 1998 10:15:10 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Lea To: Pine Discussion Forum Subject: re filtering, again In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Information List X-Sender: maldridg@gpu5.srv.ualberta.ca X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > AFAIK, Pine does not do this natively. This is the domain of mail > processors such as procmail. I can't remember the URL off the top of my > head, but there is a good FAQ on setting up filters using procmail. What is the URL for Nancy McGeogh's (sp?) page on using Elm's mail filter for pine? Lea --- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Oct 1 10:03:50 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 10:03:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA06802 for ; Thu, 1 Oct 1998 10:03:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA21236; Thu, 1 Oct 1998 10:03:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA05401; Thu, 1 Oct 1998 10:00:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA43826 for ; Thu, 1 Oct 1998 09:57:01 -0700 Received: from emh1.otc.cc.mo.us (glooney@emh1.otc.cc.mo.us [198.209.160.5]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA16426 for ; Thu, 1 Oct 1998 09:57:00 -0700 Received: from localhost (glooney@localhost) by emh1.otc.cc.mo.us (8.8.5/8.8.5) with SMTP id LAA10417 for ; Thu, 1 Oct 1998 11:58:36 -0500 (CDT) Message-Id: Date: Thu, 1 Oct 1998 11:58:36 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Greg Looney To: Pine Discussion Forum Subject: Postponed msgs MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We have a few users that have strange things happening with postponed messages. When you start to compose a message they get the message that there are postponed messages, when they tell pine to continue a postponed message pine tells them that there are not any. Has anyone seen this, and have a fix? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Oct 1 10:16:23 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 10:16:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA25981 for ; Thu, 1 Oct 1998 10:16:22 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA21620; Thu, 1 Oct 1998 10:16:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA07768; Thu, 1 Oct 1998 10:14:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA40906 for ; Thu, 1 Oct 1998 10:11:30 -0700 Received: from ns3.quik.com (ns3.quik.com [209.213.143.1]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA06374 for ; Thu, 1 Oct 1998 10:11:30 -0700 Received: from ops_svr (ip225.anaheim.quik.com [209.213.139.225]) by ns3.quik.com (8.8.7/8.8.5) with SMTP id RAA50570; Thu, 1 Oct 1998 17:09:56 GMT Message-Id: <000001bded5d$6e499760$e18bd5d1@ops_svr> Date: Thu, 1 Oct 1998 10:03:37 -0700 Reply-To: Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Colin J. Raven" To: Pine Discussion Forum Subject: RE: re filtering, again In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-To: "Lea" , "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Point your browser of choice at: http://www.ii.com/internet/faqs/launchers/mail/filtering-faq/ HTH & Regards, -Colin --- Colin J. Raven Operations Manager, HDS Lab, Inc. Costa Mesa, CA  |  Harrison, NY http://linus.uhmc.sunysb.edu/~colin >-----Original Message----- >From: PINE-INFO-owner@u.washington.edu >[mailto:PINE-INFO-owner@u.washington.edu]On Behalf Of Lea >Sent: Thursday, October 01, 1998 09:15 >To: Pine Discussion Forum >Subject: re filtering, again > > > >> AFAIK, Pine does not do this natively. This is the domain of mail >> processors such as procmail. I can't remember the URL off the top of my >> head, but there is a good FAQ on setting up filters using procmail. > >What is the URL for Nancy McGeogh's (sp?) page on using Elm's mail filter >for pine? > >Lea >--- > > > > > > >----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ >----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Thu Oct 1 10:42:25 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 10:42:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA06484 for ; Thu, 1 Oct 1998 10:42:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22396; Thu, 1 Oct 1998 10:42:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA07681; Thu, 1 Oct 1998 10:39:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA43096 for ; Thu, 1 Oct 1998 10:37:52 -0700 Received: from lancaster.nexor.co.uk (lancaster.nexor.co.uk [128.243.9.1]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA22686 for ; Thu, 1 Oct 1998 10:37:44 -0700 Received: from skyhawk.nexor.co.uk by lancaster.nexor.co.uk with SMTP (NEXOR MMTA 2.2) with ESMTP; Thu, 1 Oct 1998 18:37:06 +0100 Message-Id: Date: Thu, 1 Oct 1998 18:37:04 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: John Berthels To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: MIME-Version: 1.0 Content-Type: text/PLAIN; charset="US-ASCII" X-To: Tawfik Daoud X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >> Is there a DoS vulnerability with users creating pseudo lock-files in >> the spool directory? > The lock files are created in order to protect the INBOX files from > corruption. Sorry not to have made my question clear the first time: If I (maliciously) create a lock file for another user's mailbox, will PINE consider that users mailbox to be locked and so not allow that user to receive mail? i.e. Since the lock file for a user does not exist whilst they are not reading their mail (is this correct?) I can create it (even taking mode 1777 into account). Next time they try to read their mail a lock file (my bogus one) will exist. Will PINE permit them to read their mail under these conditions? [I'd try this here, but I get my mail via procmail, not out of the spool dir - this is purely a theoretical interest.] regards, jb -- John Berthels Email: j.berthels@nexor.co.uk X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ From pinedev@shiva0.cac.washington.edu Thu Oct 1 12:20:16 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 12:20:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA01977 for ; Thu, 1 Oct 1998 12:20:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA18774; Thu, 1 Oct 1998 12:20:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA14978; Thu, 1 Oct 1998 12:18:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA38600 for ; Thu, 1 Oct 1998 12:16:25 -0700 Received: from orca.ucd.ie (orca.ucd.ie [137.43.4.16]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA04741 for ; Thu, 1 Oct 1998 12:16:23 -0700 Received: (qmail 27492 invoked by uid 532); 1 Oct 1998 19:16:22 -0000 Message-Id: Date: Thu, 1 Oct 1998 20:16:22 +0100 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Finbarr O'Kane - netsoc Sysadmin" To: Pine Discussion Forum Subject: Re: Maildir support for pine 4.05 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi With perhaps a slightly more positive tone, may I suggest that you look at http://www.qmail.org There is a section dedicated to maildir and people who have contributed patches and code to work with this mailbox format. There is a c-client patch for pine 4 which will probably do what you want nicely This, before someone else points out, is entirely unsupported, and I have in the past been informed that there are no plans to add support for a variety of reasons Just thought Id throw in my few cents/pence :) Just another maildir-user fin On Thu, 1 Oct 1998, Robin S. Socha wrote: {} Quoting PINE list (pine-l@lcjdap.soroscj.ro): {} {} Your parents must hate you, DuDE... {} {} > Really isn't out there anyone who can make a patch for pine 4.05 {} > to support maildir style inbox format? {} > {} > There are lotsa people waiting for it... I am one too... :( {} {} Quit whining, start coding. For someone with a butt ugly name, you're pretty {} demanding. You know... free software: contribute nothing, expect nothing. {} Damn, life can be, like, real easy and stuff... {} {} Ro"youreusing4.02anyway"bin {} {} -- {} Robin S. Socha {} {} {} From pinedev@shiva0.cac.washington.edu Thu Oct 1 12:39:49 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 12:39:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA02513 for ; Thu, 1 Oct 1998 12:39:47 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA19387; Thu, 1 Oct 1998 12:39:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA16248; Thu, 1 Oct 1998 12:36:42 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA24330 for ; Thu, 1 Oct 1998 12:34:06 -0700 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA07289 for ; Thu, 1 Oct 1998 12:34:05 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id ; Thu, 1 Oct 1998 15:35:27 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394EFA@POISON> Date: Thu, 1 Oct 1998 15:35:16 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: Is there anyway using Pine (IMAP) can corrupt an exchange server database? MIME-Version: 1.0 Content-Type: text/plain X-To: "'Pine List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN We have a bunch of 486's running W95 with only 100mb or so free drive space. I don't want to waste that space, as well as slow down the W95 anymore than it is already with Exchange or Outlook, so we have chosen PC-Pine. The Administrator for the NT network (includes the mail exchange server) is concerned about running two protocols (1 being the exchange protocol, the other IMAP) on the system. Since all we need is simple folder maintenance email in & email out, PC-Pine fits the bill. Would there be any potential problems for the exchange server by haveing some users accessing their inbox via PC-Pine vs using MS exchange/Outlook? By problems, I don't mean disadvantages to the user such as lack of features, In this case I'd prefer the KISS scenerio for these users. I'm more concerned with, can using IMAP instead of Exch/Outlook in any way corrupt the exchange database, that is NOT possible by using exchange or outlook only on all machines. Thanx George Gallen ggallen@slackinc.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Thu Oct 1 15:42:13 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 15:42:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA14373 for ; Thu, 1 Oct 1998 15:42:11 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA02152; Thu, 1 Oct 1998 15:42:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA26055; Thu, 1 Oct 1998 15:37:07 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA37232 for ; Thu, 1 Oct 1998 14:40:28 -0700 Received: from nimbus.anzio.com (bezell@nimbus.anzio.com [204.201.253.34]) by mxu2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA22608 for ; Thu, 1 Oct 1998 14:40:26 -0700 Received: from localhost (bezell@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id OAA16312; Thu, 1 Oct 1998 14:39:29 -0700 Message-Id: Date: Thu, 1 Oct 1998 14:39:29 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bobby Ezell To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: John Berthels X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I know this subject is getting over-talked about, but I did the experiment and this is what I observed: 1) yes, if no file exists yet, I can create a /var/spool/mail/test file, i.e. cp /dev/null /var/spool/mail/test result is test -rw-r--r-- me users 3) pico test (and I can edit it and put "junk" in it"). At this point if user test tries to access his/her mail box with pine you get a message about invalid inbox format (or something like that) and access is not allowed. 4) I then send mail to test through pine and the mail box gets cleared and a new one created with the imfamous not-visible "Do Not Remove..." message as the first one in the box, and then the message just sent. My "junk" goes away. Also permissions change to test -rw------ test users 5) user test can now read mail with pine... It seems like sendmail (I am on LINUX) now takes care of it's mail folders after the first good message sent. I have seen this happen with student accounts at a local college where I use to work on Solaris and it seems to hold on Linux too. Of course the solution would be for the adduser script to build in a NEW mail folder under /var/spool/mail/ with proper permissions set (as it should have in this case but I commented those lines out). Anyone else get different results? On Thu, 1 Oct 1998, John Berthels wrote: > > >> Is there a DoS vulnerability with users creating pseudo lock-files in > >> the spool directory? > > > The lock files are created in order to protect the INBOX files from > > corruption. > > Sorry not to have made my question clear the first time: > > If I (maliciously) create a lock file for another user's mailbox, will > PINE consider that users mailbox to be locked and so not allow that user > to receive mail? > > i.e. Since the lock file for a user does not exist whilst they are not > reading their mail (is this correct?) I can create it (even taking mode > 1777 into account). Next time they try to read their mail a lock file (my > bogus one) will exist. Will PINE permit them to read their mail under > these conditions? > > [I'd try this here, but I get my mail via procmail, not out of the spool > dir - this is purely a theoretical interest.] > > regards, > > jb > -- > John Berthels > Email: j.berthels@nexor.co.uk > X.400: /G=john/S=berthels/O=nexor/P=nexor/A=cwmail/C=gb/ > > > > ------------------------------------------------------------------- Bobby Ezell E-Mail: bezell@anzio.com Technical Sales Support V-Mail: 503-624-0360 (voice) Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com Portland, OR 97223 http://www.anzio.com/~bezell ------------------------------------------------------------------- AnzioLite and AnzioWin for all your telnet needs Send sales & support questions to: rsi@anzio.com =================================================================== From pinedev@shiva0.cac.washington.edu Thu Oct 1 15:47:10 1998 -0700 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 15:47:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA15999 for ; Thu, 1 Oct 1998 15:47:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA25212; Thu, 1 Oct 1998 15:47:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA17414; Thu, 1 Oct 1998 15:43:27 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA19660 for ; Thu, 1 Oct 1998 15:14:56 -0700 Received: from indigo.cs.bgu.ac.il ([132.72.42.23]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA28733 for ; Thu, 1 Oct 1998 15:14:53 -0700 Received: from cyan.cs.bgu.ac.il (elad@cyan.cs.bgu.ac.il [132.72.42.12]) by indigo.cs.bgu.ac.il (8.6.9/8.6.10) with ESMTP id AAA19384 for ; Fri, 2 Oct 1998 00:14:01 +0200 Received: from localhost (elad@localhost) by cyan.cs.bgu.ac.il (8.9.0/8.6.9) with SMTP id AAA27929 for ; Fri, 2 Oct 1998 00:14:00 +0200 (IST) Message-Id: Date: Fri, 2 Oct 1998 00:14:00 +0200 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Elad Eyal To: Pine Discussion Forum Subject: Re: Postponed msgs (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: cyan.cs.bgu.ac.il: elad owned process doing -bs X-Sender: elad@cyan.bgu.ac.il X-Attribution: EE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Good morning, > We have a few users that have strange things happening with postponed > messages.When you start to compose a message they get the message that > there are postponed messages, when they tell pine to continue a postponed > message pine tells them that there are not any. Has anyone seen this, and > have a fix? If I may contribute of my modest expirience... I've seen it alot in my PCPine 4.04. It means, in a nutshell, something like "You do have a postponed folder, but it's empty. Possibly not totally empty, like zero-size. Could be only those pseudo-messages Pine uses. Oh, and ask the barman for one them little drinks with an umbrella with it, if you'd be so kind". Solution: rm ~jbond/mail/posponed or whatever. _ (_ / _ / ( E-mail pigeons nest in binary trees ) (__/__(/\_(/ http://www.cs.bgu.ac.il/~elad From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 16:08:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA09139 for ; Thu, 1 Oct 1998 16:08:32 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA25954; Thu, 1 Oct 1998 16:08:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA20008; Thu, 1 Oct 1998 16:06:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA42074 for ; Thu, 1 Oct 1998 16:04:59 -0700 Received: from mailhost.cybermania.net.ma (root@[194.204.198.70]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA23573 for ; Thu, 1 Oct 1998 16:04:57 -0700 Received: from mailhost.cybermania.net.ma (tdaoud@mailhost.cybermania.net.ma [194.204.198.70]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id WAA19683; Thu, 1 Oct 1998 22:53:46 GMT Message-Id: Date: Thu, 1 Oct 1998 22:53:46 +0000 (WET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: re: 4.05 wierdness In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bobby Ezell X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > 3) pico test (and I can edit it and put "junk" in it"). At this > point if user test tries to access his/her mail box with pine > you get a message about invalid inbox format (or something like > that) and access is not allowed. Of course you are not going to access the created TEST file because it is corrupted (or in fact not in MIME format). > Of course the solution would be for the adduser script to build in a NEW > mail folder under /var/spool/mail/ with proper permissions set (as it > should have in this case but I commented those lines out). Actually, you do not have to create that file with proper permissions, since sendmail takes care of that. Let me illustrate this scenario when sendmail receives an email: 1. First check if user exists if no then (2) else (3) 2. Case User does not exist: send a message informing both postmaster and email FROM: 3. Case User exists: check whether there exists a file name "username" in directory /var/spool/mail (or /usr/spool/mail or whatever) if yes then (4) otherwise (5) 4. Append message to file "username" 5. Create a file name called "username" mode 600 and add the received email -Tawfik _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 1 Oct 1998 22:03:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id WAA10100 for ; Thu, 1 Oct 1998 22:03:21 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA02572; Thu, 1 Oct 1998 22:03:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA13541; Thu, 1 Oct 1998 22:01:25 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA41332 for ; Thu, 1 Oct 1998 21:57:58 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA30717 for ; Thu, 1 Oct 1998 21:57:57 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id WAA08382 for ; Thu, 1 Oct 1998 22:57:56 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id WAA04660 for ; Thu, 1 Oct 1998 22:55:35 -0600 (MDT) Message-Id: Date: Thu, 1 Oct 1998 22:53:56 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Postponed msgs (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 2 Oct 1998, Elad Eyal wrote: > If I may contribute of my modest expirience... I've seen it alot in my > PCPine 4.04. It means, in a nutshell, something like "You do have a I had a similar problem under linux until about 4.02, and it seems to be fixed now. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 2 Oct 1998 08:21:59 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA31011 for ; Fri, 2 Oct 1998 08:21:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA19139; Fri, 2 Oct 1998 08:21:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA27027; Fri, 2 Oct 1998 08:19:39 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA42168 for ; Fri, 2 Oct 1998 08:17:24 -0700 Received: from jemez.lovelace.com (jemez.lovelace.com [204.134.123.11]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA01119 for ; Fri, 2 Oct 1998 08:17:22 -0700 Received: by corp.lovelace.com with Internet Mail Service (5.5.2232.9) id ; Fri, 2 Oct 1998 09:13:52 -0600 Message-Id: <3BC62AA0578CD111B75C0000F875345D6F39F5@corp.lovelace.com> Date: Fri, 2 Oct 1998 09:13:48 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ifversen, Jody M" To: Pine Discussion Forum Subject: RE: Is there anyway using Pine (IMAP) can corrupt an exchange ser ver database? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-To: "'George Gallen'" , Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi George, We are using Exchange here with both Outlook and PINE. From the server perspective, everything is fine. About the only possible issue I can think of is memory on the server. If that is running near the max now, you may want to increase it before adding a bunch of IMAP clients. Otherwise the process works just fine (with the standard disclaimers about MS 'oddities' in their implementation of 'standards'.) On the client end, however, you may experience some issues which do appear to be Exchange related. The biggest one of these is the occasional truncation of messages. We have noticed this phenomenon a number of times, but have not tracked down the actual cause as of yet. I am guessing it is related to how the message is formatted. Good luck. --Jody Jody Ifversen Network Administrator Lovelace Health Systems -----Original Message----- From: George Gallen [mailto:ggallen@slackinc.com] Sent: Thursday, October 01, 1998 1:35 PM To: Pine Discussion Forum Subject: Is there anyway using Pine (IMAP) can corrupt an exchange server database? We have a bunch of 486's running W95 with only 100mb or so free drive space. I don't want to waste that space, as well as slow down the W95 anymore than it is already with Exchange or Outlook, so we have chosen PC-Pine. The Administrator for the NT network (includes the mail exchange server) is concerned about running two protocols (1 being the exchange protocol, the other IMAP) on the system. Since all we need is simple folder maintenance email in & email out, PC-Pine fits the bill. Would there be any potential problems for the exchange server by haveing some users accessing their inbox via PC-Pine vs using MS exchange/Outlook? By problems, I don't mean disadvantages to the user such as lack of features, In this case I'd prefer the KISS scenerio for these users. I'm more concerned with, can using IMAP instead of Exch/Outlook in any way corrupt the exchange database, that is NOT possible by using exchange or outlook only on all machines. Thanx George Gallen ggallen@slackinc.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 2 Oct 1998 09:20:23 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA30616 for ; Fri, 2 Oct 1998 09:20:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13169; Fri, 2 Oct 1998 09:20:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA29979; Fri, 2 Oct 1998 09:17:44 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA42020 for ; Fri, 2 Oct 1998 09:15:04 -0700 Received: from monet.artisan.calpoly.edu (gwestlu@monet.artisan.calpoly.edu [129.65.60.33]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA07579 for ; Fri, 2 Oct 1998 09:14:55 -0700 Received: from localhost (gwestlu@localhost) by monet.artisan.calpoly.edu (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id JAA15877 for ; Fri, 2 Oct 1998 09:14:51 -0700 (PDT) Message-Id: Date: Fri, 2 Oct 1998 09:14:51 -0700 (PDT) Reply-To: gwestlun@calpoly.edu Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "George L. Westlund" To: Pine Discussion Forum Subject: Using UNIX pine with an OpenMail IMAP server MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: monet.artisan.calpoly.edu: gwestlu owned process doing -bs X-Sender: gwestlu@monet.artisan.calpoly.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am able to get the program to connect and login to the OpenMail IMAP server, but each time I go into a different folder, I must login again. Has anyone had any experience with this? I'm running PINE 4.03 currently. The OpenMail server is version 5.10. Other IMAP clients such as Netscape and Outlook seem to work fine. George L. Westlund || Internet: gwestlun@calpoly.edu Instructional Applications Support || UNIX System: gwestlu@polymail.calpoly.edu Cal Poly || Phone/FAX: (805)756-6543/(805)756-1536 San Luis Obispo, CA 93407 || URL=http://www.calpoly.edu/~gwestlu/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 2 Oct 1998 13:06:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA05666 for ; Fri, 2 Oct 1998 13:06:44 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA28369; Fri, 2 Oct 1998 13:06:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA14200; Fri, 2 Oct 1998 13:02:40 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA12140 for ; Fri, 2 Oct 1998 13:00:26 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA07141 for ; Fri, 2 Oct 1998 13:00:25 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.C39CFE30@smtpgate.uvm.edu>; Fri, 2 Oct 1998 16:00:23 -0400 Message-Id: Date: Fri, 2 Oct 1998 16:00:20 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Using UNIX pine with an OpenMail IMAP server In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN what are your setting settings in your pinerc file(i.e. check them d\by going to setup/config. Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer On Fri, 2 Oct 1998, George L. Westlund wrote: > I am able to get the program to connect and login to the OpenMail IMAP > server, but each time I go into a different folder, I must login again. > Has anyone had any experience with this? I'm running PINE 4.03 currently. > The OpenMail server is version 5.10. Other IMAP clients such as Netscape > and Outlook seem to work fine. > > George L. Westlund || Internet: gwestlun@calpoly.edu > Instructional Applications Support || UNIX System: gwestlu@polymail.calpoly.edu > Cal Poly || Phone/FAX: (805)756-6543/(805)756-1536 > San Luis Obispo, CA 93407 || URL=http://www.calpoly.edu/~gwestlu/ > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 01:00:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA17907 for ; Mon, 5 Oct 1998 01:00:45 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA12218; Mon, 5 Oct 1998 01:00:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA26889; Mon, 5 Oct 1998 00:58:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA20566 for ; Mon, 5 Oct 1998 00:51:18 -0700 Received: from admin.inetport.com (inetport.com [204.96.100.2]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA22427 for ; Sun, 4 Oct 1998 22:24:07 -0700 Received: from expwncog (ip34.boston-xcom.ma.pub-ip.psi.net [38.26.199.34]) by admin.inetport.com (8.8.8/8.8.5) with SMTP id AAA29206; Mon, 5 Oct 1998 00:24:16 -0500 (CDT) Message-Id: Date: Mon, 5 Oct 1998 01:24:12 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Jonathan E. D. Richmond" To: Pine Discussion Forum Subject: Pinerc supplied is corrupt MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine mailing list X-X-Sender: richmond@mail.inetport.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm a wicked so-called "end-user" infiltrating this list as I think I've found a bug or so. I have quite thoroughly checked this, although I could always be wrong. Two issues -- both relating to the functioning of the pinerc file in PC-PINE. 1: When you go to setup-config within PC-PINE there is no entry for "folder-collections" and a few other items that should be there are missing as well. These items are all included in pinerc but do not appear to map over to PC-PINE's config. utility. 2: The file extension setting does not appear to be working. The default should be .mtx (as is indicated in the setup-config) but the actual setting appears to be nothing (ie. no extension). Folders are therefore all listed with .mtx after their names and to save incoming mail to a folder it is necessary to include .mtx in the save to folder name. I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM -- to make sure it wasn't the computer playing up and the same things happened in both cases. I only tried PC-PINE 4.05 on one computer, but the same things happened. I have therefore gone back to PC-PINE 3.96 for the time being. Please check and see if you get the same problems... Any ideas on solutions? ----- Jonathan E. D. Richmond (617) 864-6394 Fellow (617) 496-3194 Taubman Center for State and Local Government FAX: (617) 496-1722 Kennedy School of Government Harvard University Cambridge MA 02138 e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu WWW: http://the-tech.mit.edu/~richmond/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 06:27:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA30558 for ; Mon, 5 Oct 1998 06:27:10 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA19973; Mon, 5 Oct 1998 06:27:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA01666; Mon, 5 Oct 1998 06:25:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA20884 for ; Mon, 5 Oct 1998 06:22:21 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA14974 for ; Mon, 5 Oct 1998 06:22:20 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.A63EDCC0@smtpgate.uvm.edu>; Mon, 5 Oct 1998 9:22:18 -0400 Message-Id: Date: Mon, 5 Oct 1998 09:22:16 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Pinerc supplied is corrupt In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN You are right. I have submitted the complaint that there is no folder-collection entry in the setup/config screen. doesn't mean you can' edit that information. this is how you do it. find your pinerc file, which is mostly likely in the same directory as pine.exe. open the file in some text editor, for example notepad. then look for folder-collections. its there. and that is where you have to edit that information. people have had the file extension problem too. it seems to be not working with any versions of the 4.0X. I would hope the pine-development team would be aware of these problems. but they haven't been fixed yet. Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer On Mon, 5 Oct 1998, Jonathan E. D. Richmond wrote: > > I'm a wicked so-called "end-user" infiltrating this list as I think I've > found a bug or so. I have quite thoroughly checked this, although I could > always be wrong. > > Two issues -- both relating to the functioning of the pinerc file in > PC-PINE. > > 1: When you go to setup-config within PC-PINE there is no entry for > "folder-collections" and a few other items that should be there are > missing as well. These items are all included in pinerc but do not appear > to map over to PC-PINE's config. utility. > > 2: The file extension setting does not appear to be working. The default > should be .mtx (as is indicated in the setup-config) but the actual > setting appears to be nothing (ie. no extension). Folders are therefore > all listed with .mtx after their names and to save incoming mail to a > folder it is necessary to include .mtx in the save to folder name. > > I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM > -- to make sure it wasn't the computer playing up and the same things > happened in both cases. I only tried PC-PINE 4.05 on one computer, but the > same things happened. I have therefore gone back to PC-PINE 3.96 for the > time being. > > Please check and see if you get the same problems... Any ideas on > solutions? > > ----- > > Jonathan E. D. Richmond (617) 864-6394 > Fellow (617) 496-3194 > Taubman Center for State and Local Government FAX: (617) 496-1722 > Kennedy School of Government > Harvard University > Cambridge MA 02138 > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > WWW: http://the-tech.mit.edu/~richmond/ > > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 11:06:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA01820 for ; Mon, 5 Oct 1998 11:06:35 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28027; Mon, 5 Oct 1998 11:06:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA16949; Mon, 5 Oct 1998 11:03:46 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA21844 for ; Mon, 5 Oct 1998 11:00:44 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA09077 for ; Mon, 5 Oct 1998 11:00:44 -0700 Received: from D-140-142-110-126.dhcp2.washington.edu (D-140-142-110-126.dhcp2.washington.edu [140.142.110.126]) by mailhost2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA18619; Mon, 5 Oct 1998 11:00:33 -0700 Message-Id: Date: Mon, 5 Oct 1998 11:02:32 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: Pinerc supplied is corrupt In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jonathan_Richmond@harvard.edu, "Aaron S. Hawley" X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN With Pine 4.xx, the "folder collections" section of Setup/Config screen moved to its own setup screen: Setup/CollectionList -teg On Mon, 5 Oct 1998, Aaron S. Hawley wrote: > You are right. I have submitted the complaint that there is no > folder-collection entry in the setup/config screen. doesn't mean you can' > edit that information. this is how you do it. find your pinerc file, > which is mostly likely in the same directory as pine.exe. open the file > in some text editor, for example notepad. then look for > folder-collections. its there. and that is where you have to edit that > information. > > people have had the file extension problem too. it seems to be not > working with any versions of the 4.0X. > > I would hope the pine-development team would be aware of these problems. > but they haven't been fixed yet. > > Aaron S. Hawley > ashawley@zoo.uvm.edu > 802.656.7396 > http://www.uvm.edu/~ashawley > University of Vermont > Home: Vergennes, VT, USA > PC-Pine 4.05 mailer > > On Mon, 5 Oct 1998, Jonathan E. D. Richmond wrote: > > > > > I'm a wicked so-called "end-user" infiltrating this list as I think I've > > found a bug or so. I have quite thoroughly checked this, although I could > > always be wrong. > > > > Two issues -- both relating to the functioning of the pinerc file in > > PC-PINE. > > > > 1: When you go to setup-config within PC-PINE there is no entry for > > "folder-collections" and a few other items that should be there are > > missing as well. These items are all included in pinerc but do not appear > > to map over to PC-PINE's config. utility. > > > > 2: The file extension setting does not appear to be working. The default > > should be .mtx (as is indicated in the setup-config) but the actual > > setting appears to be nothing (ie. no extension). Folders are therefore > > all listed with .mtx after their names and to save incoming mail to a > > folder it is necessary to include .mtx in the save to folder name. > > > > I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM > > -- to make sure it wasn't the computer playing up and the same things > > happened in both cases. I only tried PC-PINE 4.05 on one computer, but the > > same things happened. I have therefore gone back to PC-PINE 3.96 for the > > time being. > > > > Please check and see if you get the same problems... Any ideas on > > solutions? > > > > ----- > > > > Jonathan E. D. Richmond (617) 864-6394 > > Fellow (617) 496-3194 > > Taubman Center for State and Local Government FAX: (617) 496-1722 > > Kennedy School of Government > > Harvard University > > Cambridge MA 02138 > > > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > > WWW: http://the-tech.mit.edu/~richmond/ > > > > > > > > ----------------------------------------------------------------- > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/pine/pine-info/ > > ----------------------------------------------------------------- > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 13:01:31 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA30789 for ; Mon, 5 Oct 1998 13:01:30 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA16365; Mon, 5 Oct 1998 13:01:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA14999; Mon, 5 Oct 1998 12:58:26 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA37902 for ; Mon, 5 Oct 1998 12:55:30 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA25401 for ; Mon, 5 Oct 1998 12:55:29 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.92A43A20@smtpgate.uvm.edu>; Mon, 5 Oct 1998 15:55:28 -0400 Message-Id: Date: Mon, 5 Oct 1998 15:55:25 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Pinerc supplied is corrupt In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN why doesn't it let you delete the local folder, c:\mail in that screen? Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer On Mon, 5 Oct 1998, Terry Gray wrote: > With Pine 4.xx, the "folder collections" section of Setup/Config screen > moved to its own setup screen: Setup/CollectionList > > -teg > > On Mon, 5 Oct 1998, Aaron S. Hawley wrote: > > > You are right. I have submitted the complaint that there is no > > folder-collection entry in the setup/config screen. doesn't mean you can' > > edit that information. this is how you do it. find your pinerc file, > > which is mostly likely in the same directory as pine.exe. open the file > > in some text editor, for example notepad. then look for > > folder-collections. its there. and that is where you have to edit that > > information. > > > > people have had the file extension problem too. it seems to be not > > working with any versions of the 4.0X. > > > > I would hope the pine-development team would be aware of these problems. > > but they haven't been fixed yet. > > > > Aaron S. Hawley > > ashawley@zoo.uvm.edu > > 802.656.7396 > > http://www.uvm.edu/~ashawley > > University of Vermont > > Home: Vergennes, VT, USA > > PC-Pine 4.05 mailer > > > > On Mon, 5 Oct 1998, Jonathan E. D. Richmond wrote: > > > > > > > > I'm a wicked so-called "end-user" infiltrating this list as I think I've > > > found a bug or so. I have quite thoroughly checked this, although I could > > > always be wrong. > > > > > > Two issues -- both relating to the functioning of the pinerc file in > > > PC-PINE. > > > > > > 1: When you go to setup-config within PC-PINE there is no entry for > > > "folder-collections" and a few other items that should be there are > > > missing as well. These items are all included in pinerc but do not appear > > > to map over to PC-PINE's config. utility. > > > > > > 2: The file extension setting does not appear to be working. The default > > > should be .mtx (as is indicated in the setup-config) but the actual > > > setting appears to be nothing (ie. no extension). Folders are therefore > > > all listed with .mtx after their names and to save incoming mail to a > > > folder it is necessary to include .mtx in the save to folder name. > > > > > > I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM > > > -- to make sure it wasn't the computer playing up and the same things > > > happened in both cases. I only tried PC-PINE 4.05 on one computer, but the > > > same things happened. I have therefore gone back to PC-PINE 3.96 for the > > > time being. > > > > > > Please check and see if you get the same problems... Any ideas on > > > solutions? > > > > > > ----- > > > > > > Jonathan E. D. Richmond (617) 864-6394 > > > Fellow (617) 496-3194 > > > Taubman Center for State and Local Government FAX: (617) 496-1722 > > > Kennedy School of Government > > > Harvard University > > > Cambridge MA 02138 > > > > > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > > > WWW: http://the-tech.mit.edu/~richmond/ > > > > > > > > > > > > ----------------------------------------------------------------- > > > For information about this mailing list, and its archives, see: > > > http://www.washington.edu/pine/pine-info/ > > > ----------------------------------------------------------------- > > > > > > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 16:12:41 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA13138 for ; Mon, 5 Oct 1998 16:12:39 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA22782; Mon, 5 Oct 1998 16:12:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA06985; Mon, 5 Oct 1998 16:10:36 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA20716 for ; Mon, 5 Oct 1998 16:07:44 -0700 Received: from emerald.tufts.edu (pmdf@emerald.tufts.edu [130.64.1.16]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA19893 for ; Mon, 5 Oct 1998 16:07:43 -0700 Received: from localhost by emerald.tufts.edu (PMDF V5.1-12 #29517) with SMTP id <0F0D00401MWTGE@emerald.tufts.edu> for pine-info@u.washington.edu; Mon, 5 Oct 1998 19:07:41 -0400 (EDT) Message-Id: Date: Mon, 05 Oct 1998 19:07:41 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bernd Schoch To: Pine Discussion Forum Subject: Re: Pinerc supplied is corrupt In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-To: "Aaron S. Hawley" X-Cc: Pine Discussion Forum X-Envelope-to: pine-info@u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi : Just a simple question to a newcomer: I want to sent a list to a number of people without listing each name on the screen? How can the list be sent without showing all the names in pine? Thanks for the tips Bernd On Mon, 5 Oct 1998, Aaron S. Hawley wrote: > why doesn't it let you delete the local folder, c:\mail in that screen? > > Aaron S. Hawley > ashawley@zoo.uvm.edu > 802.656.7396 > http://www.uvm.edu/~ashawley > University of Vermont > Home: Vergennes, VT, USA > PC-Pine 4.05 mailer > > On Mon, 5 Oct 1998, Terry Gray wrote: > > > With Pine 4.xx, the "folder collections" section of Setup/Config screen > > moved to its own setup screen: Setup/CollectionList > > > > -teg > > > > On Mon, 5 Oct 1998, Aaron S. Hawley wrote: > > > > > You are right. I have submitted the complaint that there is no > > > folder-collection entry in the setup/config screen. doesn't mean you can' > > > edit that information. this is how you do it. find your pinerc file, > > > which is mostly likely in the same directory as pine.exe. open the file > > > in some text editor, for example notepad. then look for > > > folder-collections. its there. and that is where you have to edit that > > > information. > > > > > > people have had the file extension problem too. it seems to be not > > > working with any versions of the 4.0X. > > > > > > I would hope the pine-development team would be aware of these problems. > > > but they haven't been fixed yet. > > > > > > Aaron S. Hawley > > > ashawley@zoo.uvm.edu > > > 802.656.7396 > > > http://www.uvm.edu/~ashawley > > > University of Vermont > > > Home: Vergennes, VT, USA > > > PC-Pine 4.05 mailer > > > > > > On Mon, 5 Oct 1998, Jonathan E. D. Richmond wrote: > > > > > > > > > > > I'm a wicked so-called "end-user" infiltrating this list as I think I've > > > > found a bug or so. I have quite thoroughly checked this, although I could > > > > always be wrong. > > > > > > > > Two issues -- both relating to the functioning of the pinerc file in > > > > PC-PINE. > > > > > > > > 1: When you go to setup-config within PC-PINE there is no entry for > > > > "folder-collections" and a few other items that should be there are > > > > missing as well. These items are all included in pinerc but do not appear > > > > to map over to PC-PINE's config. utility. > > > > > > > > 2: The file extension setting does not appear to be working. The default > > > > should be .mtx (as is indicated in the setup-config) but the actual > > > > setting appears to be nothing (ie. no extension). Folders are therefore > > > > all listed with .mtx after their names and to save incoming mail to a > > > > folder it is necessary to include .mtx in the save to folder name. > > > > > > > > I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM > > > > -- to make sure it wasn't the computer playing up and the same things > > > > happened in both cases. I only tried PC-PINE 4.05 on one computer, but the > > > > same things happened. I have therefore gone back to PC-PINE 3.96 for the > > > > time being. > > > > > > > > Please check and see if you get the same problems... Any ideas on > > > > solutions? > > > > > > > > ----- > > > > > > > > Jonathan E. D. Richmond (617) 864-6394 > > > > Fellow (617) 496-3194 > > > > Taubman Center for State and Local Government FAX: (617) 496-1722 > > > > Kennedy School of Government > > > > Harvard University > > > > Cambridge MA 02138 > > > > > > > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > > > > WWW: http://the-tech.mit.edu/~richmond/ > > > > > > > > > > > > > > > > ----------------------------------------------------------------- > > > > For information about this mailing list, and its archives, see: > > > > http://www.washington.edu/pine/pine-info/ > > > > ----------------------------------------------------------------- > > > > > > > > > > > > > > > > ************************************************************* Bernd J. Schoch The Fletcher School of Law and Diplomacy P.O. Box 441957 Somerville, MA0214 bschoch@emerald.tufts.edu ************************************************************** From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 19:08:25 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA01907 for ; Mon, 5 Oct 1998 19:08:24 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA26924; Mon, 5 Oct 1998 19:08:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA12068; Mon, 5 Oct 1998 19:05:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA22376 for ; Mon, 5 Oct 1998 19:02:24 -0700 Received: from jedi.DataCurrent.Com (listmail@[207.225.232.200]) by mxu1.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA14864 for ; Mon, 5 Oct 1998 19:02:23 -0700 Received: from localhost (listmail@localhost) by jedi.DataCurrent.Com (8.8.7/8.8.7) with SMTP id TAA21060; Mon, 5 Oct 1998 19:01:46 -0700 Message-Id: Date: Mon, 5 Oct 1998 21:01:46 -0500 (CWT) Reply-To: DataCurrent ListMail Account Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: DataCurrent ListMail Account To: Pine Discussion Forum Subject: LCC [was Re: Pinerc supplied is corrupt] In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bernd Schoch X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Use enriched headers. Move your PINE cursor to the header and push Ctrl+R. To get help on LCC, move your cursor over LCC and push Ctrl+G. I hope this helps. --Sean ------------------------------ DataCurrent Corp. ListMail@DataCurrent.Com ------------------------------ On Mon, 5 Oct 1998, Bernd Schoch wrote: > Date: Mon, 05 Oct 1998 19:07:41 -0400 (EDT) > From: Bernd Schoch > To: Pine Discussion Forum > Subject: Re: Pinerc supplied is corrupt > > Hi : > > Just a simple question to a newcomer: I want to sent a list to a number > of people without listing each name on the screen? How can the list be > sent without showing all the names in pine? > > Thanks for the tips > Bernd > On Mon, 5 Oct 1998, Aaron S. > Hawley wrote: > > > why doesn't it let you delete the local folder, c:\mail in that screen? > > > > Aaron S. Hawley > > ashawley@zoo.uvm.edu > > 802.656.7396 > > http://www.uvm.edu/~ashawley > > University of Vermont > > Home: Vergennes, VT, USA > > PC-Pine 4.05 mailer > > > > On Mon, 5 Oct 1998, Terry Gray wrote: > > > > > With Pine 4.xx, the "folder collections" section of Setup/Config screen > > > moved to its own setup screen: Setup/CollectionList > > > > > > -teg > > > > > > On Mon, 5 Oct 1998, Aaron S. Hawley wrote: > > > > > > > You are right. I have submitted the complaint that there is no > > > > folder-collection entry in the setup/config screen. doesn't mean you can' > > > > edit that information. this is how you do it. find your pinerc file, > > > > which is mostly likely in the same directory as pine.exe. open the file > > > > in some text editor, for example notepad. then look for > > > > folder-collections. its there. and that is where you have to edit that > > > > information. > > > > > > > > people have had the file extension problem too. it seems to be not > > > > working with any versions of the 4.0X. > > > > > > > > I would hope the pine-development team would be aware of these problems. > > > > but they haven't been fixed yet. > > > > > > > > Aaron S. Hawley > > > > ashawley@zoo.uvm.edu > > > > 802.656.7396 > > > > http://www.uvm.edu/~ashawley > > > > University of Vermont > > > > Home: Vergennes, VT, USA > > > > PC-Pine 4.05 mailer > > > > > > > > On Mon, 5 Oct 1998, Jonathan E. D. Richmond wrote: > > > > > > > > > > > > > > I'm a wicked so-called "end-user" infiltrating this list as I think I've > > > > > found a bug or so. I have quite thoroughly checked this, although I could > > > > > always be wrong. > > > > > > > > > > Two issues -- both relating to the functioning of the pinerc file in > > > > > PC-PINE. > > > > > > > > > > 1: When you go to setup-config within PC-PINE there is no entry for > > > > > "folder-collections" and a few other items that should be there are > > > > > missing as well. These items are all included in pinerc but do not appear > > > > > to map over to PC-PINE's config. utility. > > > > > > > > > > 2: The file extension setting does not appear to be working. The default > > > > > should be .mtx (as is indicated in the setup-config) but the actual > > > > > setting appears to be nothing (ie. no extension). Folders are therefore > > > > > all listed with .mtx after their names and to save incoming mail to a > > > > > folder it is necessary to include .mtx in the save to folder name. > > > > > > > > > > I have tried setting up PC-PINE 4.04 on two computers -- an HP and an IBM > > > > > -- to make sure it wasn't the computer playing up and the same things > > > > > happened in both cases. I only tried PC-PINE 4.05 on one computer, but the > > > > > same things happened. I have therefore gone back to PC-PINE 3.96 for the > > > > > time being. > > > > > > > > > > Please check and see if you get the same problems... Any ideas on > > > > > solutions? > > > > > > > > > > ----- > > > > > > > > > > Jonathan E. D. Richmond (617) 864-6394 > > > > > Fellow (617) 496-3194 > > > > > Taubman Center for State and Local Government FAX: (617) 496-1722 > > > > > Kennedy School of Government > > > > > Harvard University > > > > > Cambridge MA 02138 > > > > > > > > > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > > > > > WWW: http://the-tech.mit.edu/~richmond/ > > > > > > > > > > > > > > > > > > > > ----------------------------------------------------------------- > > > > > For information about this mailing list, and its archives, see: > > > > > http://www.washington.edu/pine/pine-info/ > > > > > ----------------------------------------------------------------- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ************************************************************* > > Bernd J. Schoch > > The Fletcher School of Law and Diplomacy > > P.O. Box 441957 > Somerville, MA0214 > > bschoch@emerald.tufts.edu > > ************************************************************** > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 5 Oct 1998 19:10:13 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id TAA15974 for ; Mon, 5 Oct 1998 19:10:12 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA12451; Mon, 5 Oct 1998 19:10:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA11028; Mon, 5 Oct 1998 19:08:05 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA22548 for ; Mon, 5 Oct 1998 19:04:09 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA06135 for ; Mon, 5 Oct 1998 19:04:08 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.12CDA4B0@smtpgate.uvm.edu>; Mon, 5 Oct 1998 22:04:07 -0400 Message-Id: Date: Mon, 5 Oct 1998 22:04:02 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN want information on: How do I send a message to multiple recipients without showing all their names? it's online at the Pine Information Center at http://www.washington.edu/pine/faq/problems.html#xtocid159737 you should check the Pine Infromation Center first, if you have time to answer questions at http://www.washington.edu/pine Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Tue, 6 Oct 1998 20:38:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA10348 for ; Tue, 6 Oct 1998 20:38:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA16226; Tue, 6 Oct 1998 20:38:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA07804; Tue, 6 Oct 1998 20:27:32 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA20918 for ; Tue, 6 Oct 1998 20:22:41 -0700 Received: from imc01.ex.nus.edu.sg (imc01.ex.nus.edu.sg [137.132.14.60]) by mxu3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA21241 for ; Tue, 6 Oct 1998 20:22:31 -0700 Received: by imc01.ex.nus.edu.sg with Internet Mail Service (5.5.2120.0) id ; Wed, 7 Oct 1998 11:24:13 +0800 Message-Id: <762388C091FAD01180FF00A02462137815C989@EXS01> Date: Wed, 7 Oct 1998 11:24:04 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Yeo Eng Hee To: Pine Discussion Forum Subject: build on SGI Origin MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-To: Pine Discussion Forum X-Priority: 1 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I managed to build Pine 4.05 on an SGI Origin but with many warning messages. I wonder if the warnings can be safely ignored, especially those on nested comments. Has anyone any comments? The script of the build process is below. Yeo Eng Hee Supercomputing & Visualisation Unit, NUS Computer Centre, 10 Kent Ridge Crescent, Singapore 119260 Tel: (65) 874 5085; Fax: (65) 778 0198; email: cceyeoeh@nus.edu.sg Script started on Fri Oct 2 09:48:26 1998 cougar 1# ./build clean make args are CC=cc Cleaning c-client and imapd Removing old processed sources and binaries... sh -c 'rm -rf an ua OSTYPE c-client mtest imapd ipopd || true' cd tools;make clean sh -c 'rm -f *.o uahelper || true' Cleaning Pine rm -f *.o os.h os.c helptext.c helptext.h pine cd osdep; make clean; cd .. rm -f os-a32.c os-a41.c os-aix.c os-asv.c os-aux.c os-bs2.c os-bsd.c os-bsf.c os-bsi.c os-cvx.c os-dos.c os-dpx.c os-dyn.c os-gen.c os-hpp.c os-hpx.c os-isc.c os-lnx.c os-lyn.c os-mnt.c os-neb.c os-nxt.c os-os2.c os-osf.c os-pt1.c os-ptx.c os-s40.c os-sc5.c os-sco.c os-sgi.c os-so5.c os-sun.c os-sv4.c os-ult.c os-win.c os-wnt.c includer Cleaning pico rm -f *.a *.o *~ pico_os.c os.h pico pilot cd osdep; make clean; cd .. rm -f os-a32.c os-a41.c os-aix.c os-asv.c os-aux.c os-bsd.c os-bsf.c os-bsi.c os-cvx.c os-dos.c os-dpx.c os-dyn.c os-gen.c os-hpp.c os-isc.c os-lnx.c os-lyn.c os-mnt.c os-neb.c os-nxt.c os-os2.c os-osf.c os-pt1.c os-ptx.c os-s40.c os-sco.c os-sgi.c os-sun.c os-sv4.c os-ult.c os-win.c os-wnt.c os-3b1.c os-att.c os-sc5.c includer Done cougar 2# ./build sgi make args are CC=cc Cannot create c-client: File exists Cannot create mtest: File exists Cannot create imapd: File exists Making c-client library, mtest and imapd make CC=cc sgi Applying an process to sources... tools/an "ln -s" src/c-client c-client tools/an "ln -s" src/ansilib c-client tools/an "ln -s" src/charset c-client ln -s `pwd`/src/kerberos/* c-client tools/an "ln -s" src/osdep/unix c-client tools/an "ln -s" src/mtest mtest tools/an "ln -s" src/ipopd ipopd tools/an "ln -s" src/imapd imapd ln -s tools/an . make build EXTRACFLAGS="" EXTRALDFLAGS="" EXTRADRIVERS="mbox" EXTRAAUTHENTICATORS="" PASSWDTYPE=std AFSDIR=/usr/afsws GSSDIR=/usr/local EXTRASPECIALS="" OS=sgi Building c-client for sgi... cd c-client;make sgi BUILDOPTIONS='EXTRACFLAGS="" EXTRALDFLAGS="" EXTRADRIVERS="mbox" EXTRAAUTHENTICATORS="" PASSWDTYPE=std AFSDIR=/usr/afsws GSSDIR=/usr/local' \ EXTRASPECIALS="" make build EXTRACFLAGS="" EXTRALDFLAGS="" EXTRADRIVERS="mbox" EXTRAAUTHENTICATORS="" PASSWDTYPE=std AFSDIR=/usr/afsws GSSDIR=/usr/local OS=sgi SIGTYPE=sv4 \ MAILSPOOL=/usr/mail \ RSHPATH=/usr/bsd/rsh \ BASECFLAGS="-g -ansi -DNFSKLUDGE" \ RANLIB=true sh -c 'rm -rf auths.c flockbsd.c linkage.[ch] siglocal.c osdep*.[ch] *.o ARCHIVE *FLAGS *TYPE c-client.a || true' Once-only environment setup... ./drivers mbox imap nntp pop3 mh mx mbx tenex mtx mmdf unix news phile dummy ./mkauths log echo cc > CCTYPE echo -g -ansi -DNFSKLUDGE > CFLAGS echo -DSTDPROTO=unixproto -DMAILSPOOL=\"/usr/mail\" \ -DANONYMOUSHOME=\"/usr/mail/anonymous\" \ -DACTIVEFILE=\"/usr/lib/news/active\" -DNEWSSPOOL=\"/usr/spool/news\" \ -DRSHPATH=\"/usr/bsd/rsh\" > OSCFLAGS echo > LDFLAGS echo "ar rc c-client.a mail.o misc.o newsrc.o smanager.o osdep.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a" >> ARCHIVE ln -s os_sgi.h osdep.h ln -s os_sgi.c osdepbas.c ln -s log_std.c osdeplog.c ln -s sig_sv4.c siglocal.c sh -c '(test -f /usr/include/sys/statvfs.h -a sgi != sc5 -a sgi != sco) && ln -s flocksun.c flockbsd.c || ln -s flocksv4.c flockbsd.c' ln -s ckp_std.c osdepckp.c sh -c 'rm -rf osdep.c || true' cat osdepbas.c osdepckp.c osdeplog.c > osdep.c cc -g -ansi -DNFSKLUDGE -c mail.c "mail.c", line 281: warning(1048): cast between pointer-to-object and pointer-to-function mailgets = (mailgets_t) value; ^ "mail.c", line 283: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailgets; ^ "mail.c", line 286: warning(1048): cast between pointer-to-object and pointer-to-function mailreadprogress = (readprogress_t) value; ^ "mail.c", line 288: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailreadprogress; ^ "mail.c", line 291: warning(1048): cast between pointer-to-object and pointer-to-function mailcache = (mailcache_t) value; ^ "mail.c", line 293: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailcache; ^ "mail.c", line 296: warning(1048): cast between pointer-to-object and pointer-to-function mail822out = (rfc822out_t) value; ^ "mail.c", line 298: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mail822out; ^ "mail.c", line 301: warning(1048): cast between pointer-to-object and pointer-to-function mailsmtpverbose = (smtpverbose_t) value; ^ "mail.c", line 303: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailsmtpverbose; ^ "mail.c", line 306: warning(1048): cast between pointer-to-object and pointer-to-function mailproxycopy = (mailproxycopy_t) value; ^ "mail.c", line 308: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailproxycopy; ^ "mail.c", line 311: warning(1048): cast between pointer-to-object and pointer-to-function mailparsephrase = (parsephrase_t) value; ^ "mail.c", line 313: warning(1048): cast between pointer-to-object and pointer-to-function ret = (void *) mailparsephrase; ^ "mail.c", line 1440: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t mg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "mail.c", line 1509: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t mg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "mail.c", line 1561: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t mg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "mail.c", line 1583: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t mg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "mail.c", line 2748: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t omg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "mail.c", line 2750: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters (NIL,SET_GETS,(void *) mail_search_gets); ^ "mail.c", line 2769: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters (NIL,SET_GETS,(void *) omg); ^ "mail.c", line 2906: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%.900s",st->text.data); ^ cc -g -ansi -DNFSKLUDGE -c misc.c cc -g -ansi -DNFSKLUDGE -c newsrc.c cc -g -ansi -DNFSKLUDGE -c smanager.c cc -g -ansi -DNFSKLUDGE `cat OSCFLAGS` -c osdep.c "tcp_unix.c", line 64: warning(1048): cast between pointer-to-object and pointer-to-function tmoh = (tcptimeout_t) value; ^ "tcp_unix.c", line 67: warning(1048): cast between pointer-to-object and pointer-to-function value = (void *) tmoh; ^ "tcp_unix.c", line 242: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Can't connect to %.80s,%d: %s",hst,port,strerror (errno)); ^ "tcp_unix.c", line 265: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Connection failed to %.80s,%d: %s",hst,port,strerror(errno)); ^ cc -g -ansi -DNFSKLUDGE -c utf8.c cc -g -ansi -DNFSKLUDGE -c siglocal.c cc -g -ansi -DNFSKLUDGE -c dummy.c cc -g -ansi -DNFSKLUDGE -c pseudo.c cc -g -ansi -DNFSKLUDGE -c netmsg.c cc -g -ansi -DNFSKLUDGE -c flstring.c cc -g -ansi -DNFSKLUDGE -c fdstring.c cc -g -ansi -DNFSKLUDGE -c rfc822.c "rfc822.c", line 1045: warning(1048): cast between pointer-to-object and pointer-to-function parsephrase_t pp = (parsephrase_t) mail_parameters (NIL,GET_PARSEPHRASE,NIL); ^ "rfc822.c", line 1403: warning(1048): cast between pointer-to-object and pointer-to-function rfc822out_t r822o = (rfc822out_t) mail_parameters (NIL,GET_RFC822OUTPUT,NIL); ^ "rfc822.c", line 1431: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%ld-%ld-%ld=:%ld",gethostid (),random (),time (0), ^ "rfc822.c", line 1498: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%ld-%ld-%ld=:%ld",gethostid (),random (),time (0), ^ cc -g -ansi -DNFSKLUDGE -c nntp.c "nntp.c", line 775: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mailcache = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "nntp.c", line 886: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mailcache = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "nntp.c", line 964: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ cc -g -ansi -DNFSKLUDGE -c smtp.c "smtp.c", line 436: warning(1048): cast between pointer-to-object and pointer-to-function smtpverbose_t pv = (smtpverbose_t) mail_parameters (NIL,GET_SMTPVERBOSE,NIL); ^ cc -g -ansi -DNFSKLUDGE -c imap4r1.c "imap4r1.c", line 181: warning(1048): cast between pointer-to-object and pointer-to-function imap_envelope = (imapenvelope_t) value; ^ "imap4r1.c", line 184: warning(1048): cast between pointer-to-object and pointer-to-function value = (void *) imap_envelope; ^ "imap4r1.c", line 187: warning(1048): cast between pointer-to-object and pointer-to-function imap_referral = (imapreferral_t) value; ^ "imap4r1.c", line 190: warning(1048): cast between pointer-to-object and pointer-to-function value = (void *) imap_referral; ^ "imap4r1.c", line 422: warning(1048): cast between pointer-to-object and pointer-to-function (imapreferral_t) mail_parameters (stream,GET_IMAPREFERRAL,NIL); ^ "imap4r1.c", line 471: warning(1048): cast between pointer-to-object and pointer-to-function (imapreferral_t) mail_parameters (stream,GET_IMAPREFERRAL,NIL); ^ "imap4r1.c", line 540: warning(1048): cast between pointer-to-object and pointer-to-function (imapreferral_t) mail_parameters (stream,GET_IMAPREFERRAL,NIL); ^ "imap4r1.c", line 992: warning(1551): variable "t" is used before its value is set if (last != start) sprintf (t,":%lu,%lu",last,i); ^ "imap4r1.c", line 996: warning(1551): variable "len" is used before its value is set fs_resize ((void **) s,len += MAILTMPLEN); ^ "imap4r1.c", line 1532: warning(1551): variable "t" is used before its value is set if (last != start) sprintf (t,":%lu,%lu",last,i); ^ "imap4r1.c", line 1536: warning(1551): variable "len" is used before its value is set fs_resize ((void **) s,len += MAILTMPLEN); ^ "imap4r1.c", line 1691: warning(1048): cast between pointer-to-object and pointer-to-function (imapreferral_t) mail_parameters (stream,GET_IMAPREFERRAL,NIL); ^ "imap4r1.c", line 1693: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "imap4r1.c", line 1732: warning(1048): cast between pointer-to-object and pointer-to-function (imapreferral_t) mail_parameters (stream,GET_IMAPREFERRAL,NIL); ^ "imap4r1.c", line 1772: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mc = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "imap4r1.c", line 2384: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mc = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "imap4r1.c", line 2399: warning(1048): cast between pointer-to-object and pointer-to-function (imapenvelope_t) mail_parameters (stream,GET_IMAPENVELOPE,NIL); ^ "imap4r1.c", line 3223: warning(1048): cast between pointer-to-object and pointer-to-function mailgets_t mg = (mailgets_t) mail_parameters (NIL,GET_GETS,NIL); ^ "imap4r1.c", line 3225: warning(1048): cast between pointer-to-object and pointer-to-function (readprogress_t) mail_parameters (NIL,GET_READPROGRESS,NIL); ^ cc -g -ansi -DNFSKLUDGE -c pop3.c "pop3.c", line 691: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ cc -g -ansi -DNFSKLUDGE -c unix.c "unix.c", line 405: warning(1184): possible use of "=" where "==" was intended (read (fd,tmp,i) == i) && !(tmp[i] = 0) && (i = atol (tmp))) { ^ "unix.c", line 426: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%d",getpid ()); ^ "unix.c", line 752: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "unix.c", line 1001: warning(1178): argument is incompatible with corresponding format string conversion sprintf (hitch,"%s.%d.%d.",lock,time (0),getpid ()); ^ "unix.c", line 1001: warning(1178): argument is incompatible with corresponding format string conversion sprintf (hitch,"%s.%d.%d.",lock,time (0),getpid ()); ^ "unix.c", line 1144: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mc = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "unix.c", line 1162: warning(1178): argument is incompatible with corresponding format string conversion LOCAL->filesize,sbuf.st_size); ^ "unix.c", line 1162: warning(1178): argument is incompatible with corresponding format string conversion LOCAL->filesize,sbuf.st_size); ^ cc -g -ansi -DNFSKLUDGE -c mbox.c "mbox.c", line 276: warning(1178): argument is incompatible with corresponding format string conversion sysinbox (),size,sbuf.st_size); ^ cc -g -ansi -DNFSKLUDGE -c mbx.c "mbx.c", line 684: warning(1178): argument is incompatible with corresponding format string conversion else sprintf (tmp,"%lu:%lu",1,r); ^ "mbx.c", line 849: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "mbx.c", line 1007: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp+26,",%lu;%08lx%04x-00000000\015\012",size,uf,f); ^ "mbx.c", line 1061: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Mailbox shrank from %lu to %lu!",curpos,sbuf.st_size); ^ "mbx.c", line 1061: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Mailbox shrank from %lu to %lu!",curpos,sbuf.st_size); ^ "mbx.c", line 1092: warning(1178): argument is incompatible with corresponding format string conversion curpos,sbuf.st_size,i ? strerror (errno) : "no data read"); ^ "mbx.c", line 1092: warning(1178): argument is incompatible with corresponding format string conversion curpos,sbuf.st_size,i ? strerror (errno) : "no data read"); ^ "mbx.c", line 1100: warning(1178): argument is incompatible with corresponding format string conversion curpos,i,LOCAL->buf); ^ "mbx.c", line 1109: warning(1178): argument is incompatible with corresponding format string conversion curpos,LOCAL->buf); ^ "mbx.c", line 1119: warning(1178): argument is incompatible with corresponding format string conversion curpos,LOCAL->buf); ^ "mbx.c", line 1129: warning(1178): argument is incompatible with corresponding format string conversion curpos,LOCAL->buf); ^ "mbx.c", line 1139: warning(1178): argument is incompatible with corresponding format string conversion curpos,LOCAL->buf,s,t); ^ "mbx.c", line 1147: warning(1178): argument is incompatible with corresponding format string conversion curpos,curpos + i + j,sbuf.st_size); ^ "mbx.c", line 1147: warning(1178): argument is incompatible with corresponding format string conversion curpos,curpos + i + j,sbuf.st_size); ^ "mbx.c", line 1147: warning(1178): argument is incompatible with corresponding format string conversion curpos,curpos + i + j,sbuf.st_size); ^ "mbx.c", line 1156: warning(1178): argument is incompatible with corresponding format string conversion elt->private.uid,elt->msgno); ^ "mbx.c", line 1175: warning(1178): argument is incompatible with corresponding format string conversion curpos,LOCAL->buf); ^ cc -g -ansi -DNFSKLUDGE -c mmdf.c "mmdf.c", line 385: warning(1184): possible use of "=" where "==" was intended (read (fd,tmp,i) == i) && !(tmp[i] = 0) && (i = atol (tmp))) { ^ "mmdf.c", line 406: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%d",getpid ()); ^ "mmdf.c", line 732: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "mmdf.c", line 968: warning(1178): argument is incompatible with corresponding format string conversion sprintf (hitch,"%s.%d.%d.",lock,time (0),getpid ()); ^ "mmdf.c", line 968: warning(1178): argument is incompatible with corresponding format string conversion sprintf (hitch,"%s.%d.%d.",lock,time (0),getpid ()); ^ "mmdf.c", line 1111: warning(1048): cast between pointer-to-object and pointer-to-function mailcache_t mc = (mailcache_t) mail_parameters (NIL,GET_CACHE,NIL); ^ "mmdf.c", line 1129: warning(1178): argument is incompatible with corresponding format string conversion LOCAL->filesize,sbuf.st_size); ^ "mmdf.c", line 1129: warning(1178): argument is incompatible with corresponding format string conversion LOCAL->filesize,sbuf.st_size); ^ cc -g -ansi -DNFSKLUDGE -c tenex.c "tenex.c", line 702: warning(1178): argument is incompatible with corresponding format string conversion else sprintf (tmp,"%lu:%lu",1,r); ^ "tenex.c", line 807: warning(1178): argument is incompatible with corresponding format string conversion pos,LOCAL->filesize,delta); ^ "tenex.c", line 807: warning(1178): argument is incompatible with corresponding format string conversion pos,LOCAL->filesize,delta); ^ "tenex.c", line 846: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "tenex.c", line 1073: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Mailbox shrank from %ld to %ld!",curpos,sbuf.st_size); ^ "tenex.c", line 1084: warning(1178): argument is incompatible with corresponding format string conversion curpos,sbuf.st_size,i ? strerror (errno) : "no data read"); ^ "tenex.c", line 1138: warning(1178): argument is incompatible with corresponding format string conversion elt->private.special.offset,curpos,sbuf.st_size); ^ cc -g -ansi -DNFSKLUDGE -c mtx.c "mtx.c", line 644: warning(1178): argument is incompatible with corresponding format string conversion else sprintf (tmp,"%lu:%lu",1,r); ^ "mtx.c", line 749: warning(1178): argument is incompatible with corresponding format string conversion pos,LOCAL->filesize,delta); ^ "mtx.c", line 749: warning(1178): argument is incompatible with corresponding format string conversion pos,LOCAL->filesize,delta); ^ "mtx.c", line 788: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ "mtx.c", line 998: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"Mailbox shrank from %ld to %ld!",curpos,sbuf.st_size); ^ "mtx.c", line 1009: warning(1178): argument is incompatible with corresponding format string conversion curpos,sbuf.st_size,i ? strerror (errno) : "no data read"); ^ "mtx.c", line 1065: warning(1178): argument is incompatible with corresponding format string conversion elt->private.special.offset,curpos,sbuf.st_size); ^ cc -g -ansi -DNFSKLUDGE -c news.c "news.c", line 347: warning(1164): argument of type "int (*)(const void *, const void *)" is incompatible with parameter of type "int (*)(dirent_t **, dirent_t **)" if ((nmsgs = scandir (tmp,&names,news_select,news_numsort)) >= 0) { ^ "news.c", line 589: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ cc -g -ansi -DNFSKLUDGE -c phile.c "phile.c", line 490: warning(1048): cast between pointer-to-object and pointer-to-function (mailproxycopy_t) mail_parameters (stream,GET_MAILPROXYCOPY,NIL); ^ cc -g -ansi -DNFSKLUDGE -c mh.c "mh.c", line 639: warning(1164): argument of type "int (*)(const void *, const void *)" is incompatible with parameter of type "int (*)(dirent_t **, dirent_t **)" long nfiles = scandir (LOCAL->dir,&names,mh_select,mh_numsort); ^ "mh.c", line 900: warning(1164): argument of type "int (*)(const void *, const void *)" is incompatible with parameter of type "int (*)(dirent_t **, dirent_t **)" if ((nfiles = scandir (tmp,&names,mh_select,mh_numsort)) > 0) { ^ cc -g -ansi -DNFSKLUDGE -c mx.c "mx.c", line 564: warning(1164): argument of type "int (*)(const void *, const void *)" is incompatible with parameter of type "int (*)(dirent_t **, dirent_t **)" long nfiles = scandir (LOCAL->dir,&names,mx_select,mx_numsort); ^ sh -c 'rm -rf c-client.a || true' ar rc c-client.a mail.o misc.o newsrc.o smanager.o osdep.o utf8.o siglocal.o dummy.o pseudo.o netmsg.o flstring.o fdstring.o rfc822.o nntp.o smtp.o imap4r1.o pop3.o unix.o mbox.o mbx.o mmdf.o tenex.o mtx.o news.o phile.o mh.o mx.o;true c-client.a echo sgi > OSTYPE touch rebuild sh -c 'rm -rf rebuild || true' Building bundled tools... cd mtest;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c mtest.c `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o mtest mtest.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` cd ipopd;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c ipop2d.c "ipop2d.c", line 114: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop2d.c", line 114: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop2d.c", line 114: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop2d.c", line 114: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop2d ipop2d.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -c ipop3d.c "ipop3d.c", line 121: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop3d.c", line 121: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop3d.c", line 121: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop3d.c", line 121: warning(1164): argument of type "void (*)()" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "ipop3d.c", line 374: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 374: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 374: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 374: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 398: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 398: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 398: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 398: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 420: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 420: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 420: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 420: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 487: warning(1164): argument of type "unsigned char *" is incompatible with parameter of type "const char *" return (char *) rfc822_base64 (t,strlen (t),rlen ? rlen : &i); ^ "ipop3d.c", line 499: warning(1164): argument of type "unsigned char *" is incompatible with parameter of type "char *" while (!fgets (resp,RESPBUFLEN-1,stdin)) { ^ "ipop3d.c", line 504: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 504: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 504: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 504: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 518: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 518: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 518: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "ipop3d.c", line 518: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -o ipop3d ipop3d.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` cd imapd;make `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DALERTFILE=\"/etc/imapd.alert\" -DANOFILE=\"/etc/anonymous.newsgroups\" -c imapd.c "imapd.c", line 253: warning(1164): argument of type "void (*)(void)" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "imapd.c", line 253: warning(1164): argument of type "void (*)(void)" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "imapd.c", line 253: warning(1164): argument of type "void (*)(void)" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "imapd.c", line 253: warning(1164): argument of type "void (*)(void)" is incompatible with parameter of type "void *" server_traps (clkint,kodint,hupint,trmint); ^ "imapd.c", line 254: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters (NIL,SET_MAILPROXYCOPY,(void *) proxycopy); ^ "imapd.c", line 307: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 307: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 307: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 307: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1198: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1198: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1198: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1198: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1220: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1220: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1220: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1220: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1240: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1240: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1240: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1240: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1259: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1259: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1259: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1259: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1288: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1288: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1288: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1288: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1314: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1314: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1314: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 1314: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 2783: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 2783: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 2783: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ "imapd.c", line 2783: warning(1164): argument of type "SIG_PF" is incompatible with parameter of type "void *" server_traps (SIG_IGN,SIG_IGN,SIG_IGN,SIG_IGN); ^ `cat ../c-client/CCTYPE` -I../c-client `cat ../c-client/CFLAGS` -DALERTFILE=\"/etc/imapd.alert\" -DANOFILE=\"/etc/anonymous.newsgroups\" -o imapd imapd.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` Making Pico and Pilot make CC=cc -f makefile.sgi rm -f os.h ln -s osdep/os-sgi.h os.h cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c attach.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "attach.c", line 306: warning(1116): non-void function "AskAttach" (declared at line 60) should return a value } ^ "attach.c", line 1241: warning(1116): non-void function "sinserts" (declared at line 1206) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c basic.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "basic.c", line 718: warning(1116): non-void function "scrollto" (declared at line 668) should return a value } ^ "basic.c", line 867: warning(1116): non-void function "mousepress" (declared at line 827) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c bind.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "bind.c", line 184: warning(1116): non-void function "whelp" (declared at line 134) should return a value } ^ "bind.c", line 392: warning(1116): non-void function "rebindfunc" (declared at line 380) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c browse.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "browse.c", line 1417: warning(1110): statement is unreachable break; ^ "browse.c", line 1862: warning(1116): non-void function "BrowserKeys" (declared at line 1840) should return a value } ^ "browse.c", line 1887: warning(1116): non-void function "layoutcells" (declared at line 1869) should return a value } ^ "browse.c", line 1928: warning(1116): non-void function "percdircells" (declared at line 1894) should return a value } ^ "browse.c", line 2008: warning(1116): non-void function "zotfcells" (declared at line 1997) should return a value } ^ "browse.c", line 2021: warning(1116): non-void function "zotmaster" (declared at line 2014) should return a value } ^ "browse.c", line 2086: warning(1116): non-void function "set_browser_title" (declared at line 2082) should return a value } ^ "browse.c", line 2148: warning(1116): non-void function "BrowserAnchor" (declared at line 2092) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c buffer.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "buffer.c", line 324: warning(1116): non-void function "readbuf" (declared at line 272) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c composer.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "composer.c", line 1859: warning(1116): non-void function "HeaderPaintCursor" (declared at line 1856) should return a value } ^ "composer.c", line 2216: warning(1116): non-void function "PaintBody" (declared at line 2203) should return a value } ^ "composer.c", line 2284: warning(1116): non-void function "ArrangeHeader" (declared at line 2269) should return a value } ^ "composer.c", line 2683: warning(1116): non-void function "NewTop" (declared at line 2668) should return a value } ^ "composer.c", line 3637: warning(1116): non-void function "ShowPrompt" (declared at line 3585) should return a value } ^ "composer.c", line 3737: warning(1116): non-void function "zotheader" (declared at line 3731) should return a value } ^ "composer.c", line 3753: warning(1116): non-void function "zotentry" (declared at line 3743) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c display.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "display.c", line 229: warning(1116): non-void function "vttidy" (declared at line 222) should return a value } ^ "display.c", line 242: warning(1116): non-void function "vtmove" (declared at line 237) should return a value } ^ "display.c", line 280: warning(1116): non-void function "vtputc" (declared at line 251) should return a value } ^ "display.c", line 319: warning(1116): non-void function "vtpute" (declared at line 287) should return a value } ^ "display.c", line 336: warning(1116): non-void function "vteeol" (declared at line 326) should return a value } ^ "display.c", line 777: warning(1116): non-void function "update" (declared at line 346) should return a value } ^ "display.c", line 809: warning(1116): non-void function "updext" (declared at line 785) should return a value } ^ "display.c", line 930: warning(1116): non-void function "updateline" (declared at line 818) should return a value } ^ "display.c", line 973: warning(1233): explicit type is missing ("int" assumed) register i; /* loop index */ ^ "display.c", line 974: warning(1233): explicit type is missing ("int" assumed) register lchar; /* character to draw line in buffer with */ ^ "display.c", line 1070: warning(1116): non-void function "modeline" (declared at line 939) should return a value } ^ "display.c", line 1087: warning(1116): non-void function "movecursor" (declared at line 1079) should return a value } ^ "display.c", line 1096: warning(1116): non-void function "clearcursor" (declared at line 1093) should return a value } ^ "display.c", line 1748: warning(1116): non-void function "mlputi" (declared at line 1731) should return a value } ^ "display.c", line 1771: warning(1116): non-void function "mlputli" (declared at line 1754) should return a value } ^ "display.c", line 1817: warning(1116): non-void function "scrolldown" (declared at line 1783) should return a value } ^ "display.c", line 1861: warning(1116): non-void function "scrollup" (declared at line 1825) should return a value } ^ "display.c", line 1892: warning(1116): non-void function "pprints" (declared at line 1868) should return a value } ^ "display.c", line 2059: warning(1116): non-void function "showCompTitle" (declared at line 2038) should return a value } ^ "display.c", line 2077: warning(1116): non-void function "zotdisplay" (declared at line 2066) should return a value } ^ "display.c", line 2114: warning(1116): non-void function "pputc" (declared at line 2102) should return a value } ^ "display.c", line 2126: warning(1116): non-void function "pputs" (declared at line 2120) should return a value } ^ "display.c", line 2144: warning(1116): non-void function "peeol" (declared at line 2133) should return a value } ^ "display.c", line 2175: warning(1116): non-void function "pclear" (declared at line 2165) should return a value } ^ "display.c", line 2415: warning(1116): non-void function "wkeyhelp" (declared at line 2321) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c file.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "file.c", line 424: warning(1178): argument is incompatible with corresponding format string conversion nline, (nline > 1) ? "s" : ""); ^ "file.c", line 611: warning(1110): statement is unreachable break; ^ "file.c", line 825: warning(1178): argument is incompatible with corresponding format string conversion sprintf(line,"Inserted %d line%s", nline, (nline>1) ? "s" : ""); ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c fileio.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c line.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "line.c", line 159: warning(1116): non-void function "lfree" (declared at line 115) should return a value } ^ "line.c", line 189: warning(1116): non-void function "lchange" (declared at line 169) should return a value } ^ "line.c", line 201: warning(1116): non-void function "insspace" (declared at line 196) should return a value } ^ "line.c", line 649: warning(1116): non-void function "pkbufdel" (declared at line 641) should return a value } ^ cd osdep; make includer os-sgi.c; cd .. cc -o includer includer.c "includer.c", line 75: warning(1116): non-void function "readfile" (declared at line 38) should return a value } ^ ./includer < os-sgi.ic > os-sgi.c rm -f pico_os.c ln -s osdep/os-sgi.c pico_os.c cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c pico_os.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "pico_os.c", line 131: warning(1116): non-void function "picosigs" (declared at line 121) should return a value } ^ "pico_os.c", line 190: warning(1116): non-void function "ttgetwinsz" (declared at line 166) should return a value } ^ "pico_os.c", line 310: warning(1110): statement is unreachable break; ^ "pico_os.c", line 323: warning(1116): non-void function "ReadyForKey" (declared at line 304) should return a value } ^ "pico_os.c", line 416: warning(1110): statement is unreachable break; ^ "pico_os.c", line 458: warning(1110): statement is unreachable break; ^ "pico_os.c", line 1531: warning(1116): non-void function "fixpath" (declared at line 1498) should return a value } ^ "pico_os.c", line 2267: warning(1116): non-void function "chkptinit" (declared at line 2232) should return a value } ^ "pico_os.c", line 3531: warning(1116): non-void function "tinfoopen" (declared at line 3481) should return a value } ^ "pico_os.c", line 3545: warning(1116): non-void function "tinfoclose" (declared at line 3534) should return a value } ^ "pico_os.c", line 3564: warning(1116): non-void function "tinfoinsert" (declared at line 3552) should return a value } ^ "pico_os.c", line 3579: warning(1116): non-void function "tinfodelete" (declared at line 3570) should return a value } ^ "pico_os.c", line 3623: warning(1116): non-void function "o_scrolldown" (declared at line 3587) should return a value } ^ "pico_os.c", line 3664: warning(1116): non-void function "o_scrollup" (declared at line 3631) should return a value } ^ "pico_os.c", line 3703: warning(1116): non-void function "tinfomove" (declared at line 3699) should return a value } ^ "pico_os.c", line 3709: warning(1116): non-void function "tinfoeeol" (declared at line 3706) should return a value } ^ "pico_os.c", line 3715: warning(1116): non-void function "tinfoeeop" (declared at line 3712) should return a value } ^ "pico_os.c", line 3733: warning(1116): non-void function "tinforev" (declared at line 3718) should return a value } ^ "pico_os.c", line 3739: warning(1116): non-void function "tinfobeep" (declared at line 3736) should return a value } ^ "pico_os.c", line 3746: warning(1116): non-void function "putpad" (declared at line 3742) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c pico.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "pico.c", line 474: warning(1116): non-void function "edinit" (declared at line 406) should return a value } ^ "pico.c", line 592: warning(1116): non-void function "quickexit" (declared at line 577) should return a value } ^ "pico.c", line 657: warning(1116): non-void function "suspend_composer" (declared at line 650) should return a value } ^ "pico.c", line 800: warning(1116): non-void function "func_init" (declared at line 776) should return a value } ^ "pico.c", line 841: warning(1116): non-void function "zotedit" (declared at line 824) should return a value } ^ "pico.c", line 1429: warning(1116): non-void function "pico_puts" (declared at line 1423) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c random.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c region.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "region.c", line 373: warning(1116): non-void function "unmarkbuffer" (declared at line 355) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c search.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "search.c", line 379: warning(1116): non-void function "get_pat_cases" (declared at line 368) should return a value } ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c window.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c word.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ ar ru libpico.a attach.o basic.o bind.o browse.o buffer.o composer.o display.o file.o fileio.o line.o pico_os.o pico.o random.o region.o search.o window.o word.o ar: Warning: creating libpico.a /bin/true libpico.a cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c main.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE main.o libpico.a -ltermcap -lc -o pico cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE -c pilot.c "os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ cc -g -DDEBUG -ansi -Dsgi -DJOB_CONTROL -DMOUSE pilot.o libpico.a -ltermcap -lc -o pilot Making Pine. make CC=cc -f makefile.sgi rm -f os.h ln -s osdep/os-sgi.h os.h ./cmplhlp2.sh < pine.hlp > helptext.h cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c addrbook.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "addrbook.c", line 594: warning(1116): non-void function "dlist" (declared at line 571) should return a value } ^ "addrbook.c", line 623: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, ^ "addrbook.c", line 821: warning(1178): argument is incompatible with corresponding format string conversion dprint(10, (debugfile, "- get_display_line(%d) -\n", global_row)); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c adrbkcmd.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "adrbkcmd.c", line 2360: warning(1178): argument is incompatible with corresponding format string conversion "About to delete the contents of address book (%ld entries), really delete ", adrbk_count(pab->address_book)); ^ "adrbkcmd.c", line 2451: warning(1185): enumerated type mixed with another type pab->access = adrbk_access(pab); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c adrbklib.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "adrbklib.c", line 77: warning(1233): explicit type is missing ("int" assumed) static forced_rebuilds = 0; /* forced rebuild even though mtime looks right */ ^ "adrbklib.c", line 78: warning(1233): explicit type is missing ("int" assumed) static trouble_rebuilds = 0; /* all rebuilds caused by goto trouble; */ ^ "adrbklib.c", line 2143: warning(1178): argument is incompatible with corresponding format string conversion sprintf(vers, "%ld", REMOTE_ABOOK_VERS_NUM); ^ "adrbklib.c", line 3973: warning(1551): variable "p_msg" is used before its value is set if(!*p_msg) ^ "adrbklib.c", line 4294: warning(1198): the format string ends before this argument dprint(2, (debugfile, " : uid_nick %ld uid_addr %ld offset\n", ^ "adrbklib.c", line 5535: warning(1178): argument is incompatible with corresponding format string conversion dprint(7, (debugfile, ^ "adrbklib.c", line 6353: warning(1178): argument is incompatible with corresponding format string conversion dprint(1, (debugfile, ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c args.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c bldaddr.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "bldaddr.c", line 308: warning(1110): statement is unreachable break; ^ "bldaddr.c", line 320: warning(1110): statement is unreachable break; ^ "bldaddr.c", line 332: warning(1110): statement is unreachable break; ^ "bldaddr.c", line 348: warning(1110): statement is unreachable break; ^ "bldaddr.c", line 362: warning(1110): statement is unreachable break; ^ "bldaddr.c", line 3936: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(NIL, SET_PARSEPHRASE, (void *)massage_phrase_addr); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c context.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c filter.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "filter.c", line 548: warning(1116): non-void function "so_truncate" (declared at line 510) should return a value } ^ "filter.c", line 994: warning(1116): non-void function "gf_link_filter" (declared at line 964) should return a value } ^ "filter.c", line 1174: warning(1177): argument is incompatible with formal parameter gf_link_filter(gf_terminal, NULL); ^ "filter.c", line 2677: warning(1116): non-void function "html_push" (declared at line 2661) should return a value } ^ "filter.c", line 2726: warning(1116): non-void function "html_pop" (declared at line 2684) should return a value } ^ "filter.c", line 2740: warning(1116): non-void function "html_handoff" (declared at line 2732) should return a value } ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c folder.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "folder.c", line 2836: warning(1178): argument is incompatible with corresponding format string conversion (diff > 0) ? diff : old_tot + diff, ^ "folder.c", line 2998: warning(1116): non-void function "folder_lister_listmode" (declared at line 2986) should return a value } ^ "folder.c", line 3385: warning(1183): pointless comparison of unsigned integer with zero max(0,(fd->display_cols/2)-(strlen(s)/2)), s); ^ "folder.c", line 6204: warning(1116): non-void function "dump_contexts" (declared at line 6185) should return a value } ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c help.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "help.c", line 388: warning(1116): non-void function "init_helper_getc" (declared at line 382) should return a value } ^ ./cmplhelp.sh < pine.hlp > helptext.c cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c helptext.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c imap.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c init.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "init.c", line 512: warning(1116): non-void function "init_init_vars" (declared at line 508) should return a value } ^ "init.c", line 4670: warning(1198): the format string ends before this argument dprint(1, (debugfile, "Error context_deleting %s in \n", ^ "init.c", line 4680: warning(1009): nested comment is not allowed /* break; /* skip out of the whole thing when he says no */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c mailcap.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "mailcap.c", line 247: warning(1177): argument is incompatible with formal parameter MC_USER_FILE, MC_PATH_SEPARATOR, MC_STDPATH); ^ "mailcap.c", line 1078: warning(1177): argument is incompatible with formal parameter MT_USER_FILE, MT_PATH_SEPARATOR, MT_STDPATH); ^ "mailcap.c", line 1126: warning(1116): non-void function "mt_srch_mime_type" (declared at line 1068) should return a value } ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c mailcmd.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "mailcmd.c", line 662: warning(1178): argument is incompatible with corresponding format string conversion dprint(8,(debugfile, "Expunge max:%ld cur:%ld kill:%d\n", ^ "mailcmd.c", line 4253: warning(1198): the format string ends before this argument sprintf(prompt, "GOTO folder %s: ", expanded, *expanded ? " " : ""); ^ "mailcmd.c", line 4604: warning(1178): argument is incompatible with corresponding format string conversion dprint(7, (debugfile, "%ld %ld %x\n", ^ "mailcmd.c", line 5573: warning(1233): explicit type is missing ("int" assumed) static capture = 1, raw = 0, delimit = 0, newpipe = 0; ^ "mailcmd.c", line 5573: warning(1233): explicit type is missing ("int" assumed) static capture = 1, raw = 0, delimit = 0, newpipe = 0; ^ "mailcmd.c", line 5573: warning(1233): explicit type is missing ("int" assumed) static capture = 1, raw = 0, delimit = 0, newpipe = 0; ^ "mailcmd.c", line 5573: warning(1233): explicit type is missing ("int" assumed) static capture = 1, raw = 0, delimit = 0, newpipe = 0; ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c mailindx.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c mailpart.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "mailpart.c", line 3284: warning(1184): possible use of "=" where "==" was intended else if(rc = 3) ^ "mailpart.c", line 4142: warning(1178): argument is incompatible with corresponding format string conversion sprintf(tmp_20k_buf, "%ld", random()); ^ "mailpart.c", line 4327: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(g_fr_desc->stream, SET_GETS, (void *) fetch_gets); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c mailview.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "mailview.c", line 2796: warning(1116): non-void function "url_external_specific_handler" (declared at line 2744) should return a value } ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c newmail.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "newmail.c", line 207: warning(1178): argument is incompatible with corresponding format string conversion dprint(7, (debugfile, ^ "newmail.c", line 207: warning(1178): argument is incompatible with corresponding format string conversion dprint(7, (debugfile, ^ "newmail.c", line 213: warning(1178): argument is incompatible with corresponding format string conversion mn_get_total(pine_state->msgmap))); ^ "newmail.c", line 489: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "freq %d tm %d changes %d since_1st_change %d\n", ^ "newmail.c", line 491: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "since_status_chg %d chk_cnt_ave %d (tenths)\n", ^ "newmail.c", line 491: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "since_status_chg %d chk_cnt_ave %d (tenths)\n", ^ "newmail.c", line 493: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "adj_chk_cnt_ave %d (tenths)\n", adj_cca)); ^ "newmail.c", line 494: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "Check:if changes(%d)xadj_cca(%d) >= freq(%d)x200\n", ^ "newmail.c", line 496: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, " is %d >= %d ?\n", ^ "newmail.c", line 505: warning(1178): argument is incompatible with corresponding format string conversion dprint(7, (debugfile, ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c other.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "other.c", line 960: warning(1185): enumerated type mixed with another type if(lv < (j = strlen(sort_name(i)))) ^ "other.c", line 981: warning(1185): enumerated type mixed with another type lv, sort_name(i), ^ "other.c", line 5271: warning(1110): statement is unreachable break; ^ "other.c", line 5825: warning(1548): transfer of control bypasses initialization of: variable "maxwidth" (declared at line 5480) goto replace_text; ^ "other.c", line 5834: warning(1548): transfer of control bypasses initialization of: variable "maxwidth" (declared at line 5480) goto add_text; ^ "other.c", line 6087: warning(1116): non-void function "screen_exit_cmd" (declared at line 6066) should return a value } ^ "other.c", line 8251: warning(1183): pointless comparison of unsigned integer with zero max(0, ps->ttyo->screen_cols - cl->valoffset - 13 ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c pine.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "pine.c", line 330: warning(1048): cast between pointer-to-object and pointer-to-function (void) mail_parameters(NULL, SET_READPROGRESS, (void *)pine_read_progress); ^ "pine.c", line 345: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(NULL, SET_TIMEOUT, (void *) pine_tcptimeout); ^ "pine.c", line 354: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(NULL, SET_IMAPENVELOPE, (void *) pine_imap_envelope); ^ "pine.c", line 364: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(NULL, SET_IMAPREFERRAL, (void *) imap_referral); ^ "pine.c", line 365: warning(1048): cast between pointer-to-object and pointer-to-function mail_parameters(NULL, SET_MAILPROXYCOPY, (void *) imap_proxycopy); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c reply.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "reply.c", line 2322: warning(1178): argument is incompatible with corresponding format string conversion mn_total_cur(pine_state->msgmap)); ^ "reply.c", line 2325: warning(1178): argument is incompatible with corresponding format string conversion mn_total_cur(pine_state->msgmap)); ^ "reply.c", line 3052: warning(1178): argument is incompatible with corresponding format string conversion cnt, getpid(), ps_global->hostname); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c screen.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c send.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "send.c", line 2424: warning(1178): argument is incompatible with corresponding format string conversion dprint(9, (debugfile, "flags: %x\n", pbuf->pine_flags)); ^ "send.c", line 3427: warning(1178): argument is incompatible with corresponding format string conversion i, reply->data.uid.validity, ^ "send.c", line 5275: warning(1048): cast between pointer-to-object and pointer-to-function (void)mail_parameters(NULL, SET_RFC822OUTPUT, (void *)post_rfc822_output); ^ "send.c", line 5281: warning(1048): cast between pointer-to-object and pointer-to-function (void *) pine_smtp_verbose_out); ^ "send.c", line 7332: warning(1178): argument is incompatible with corresponding format string conversion sprintf (tmp,"%ld-%ld-%ld=:%ld",gethostid (),random (),time (0), ^ "send.c", line 7915: warning(1048): cast between pointer-to-object and pointer-to-function (void *)post_rfc822_output); ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c signals.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "signals.c", line 440: warning(1082): storage class is not first static winch_signal SIG_PROTO((int sig)) ^ "signals.c", line 933: warning(1116): non-void function "ttyfix" (declared at line 904) should return a value } ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c status.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c strings.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c takeaddr.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "takeaddr.c", line 679: warning(1110): statement is unreachable break; ^ cd osdep; make includer os-sgi.c; cd .. cc -o includer includer.c "includer.c", line 75: warning(1116): non-void function "readfile" (declared at line 38) should return a value } ^ ./includer < os-sgi.ic > os-sgi.c rm -f os.c ln -s osdep/os-sgi.c os.c cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -c os.c "../pico/os.h", line 21: warning(1009): nested comment is not allowed /* #define void char /* no void in compiler */ ^ "../pico/os.h", line 42: warning(1009): nested comment is not allowed /* #include /* To make matching and sorting work right */ ^ "../pico/os.h", line 56: warning(1009): nested comment is not allowed /* #include /* only one or the other */ ^ "../pico/os.h", line 59: warning(1009): nested comment is not allowed /* #define SigType int /* value returned by sig handlers is int */ ^ "../pico/os.h", line 61: warning(1009): nested comment is not allowed /* #define POSIX_SIGNALS /* use POSIX signal semantics (ttyin.c) */ ^ "../pico/os.h", line 87: warning(1009): nested comment is not allowed /* #define QSType char /* qsort arg is of type char * */ ^ "../pico/os.h", line 92: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO O_NONBLOCK /* POSIX style */ ^ "../pico/os.h", line 93: warning(1009): nested comment is not allowed /*#define NON_BLOCKING_IO FNDELAY /* good ol' bsd style */ ^ "../pico/os.h", line 102: warning(1009): nested comment is not allowed /* #include /* BSD-based systems */ ^ "../pico/os.h", line 105: warning(1009): nested comment is not allowed /* #define HAVE_TERMIO /* this is for pure System V */ ^ "../pico/os.h", line 106: warning(1009): nested comment is not allowed /* #include /* Sys V */ ^ "../pico/os.h", line 117: warning(1009): nested comment is not allowed /* #define USE_POLL /* use the poll() system call instead of select() */ ^ "../pico/os.h", line 123: warning(1009): nested comment is not allowed /* #define USE_TERMCAP /* use termcap */ ^ "../pico/os.h", line 128: warning(1009): nested comment is not allowed /* #define HAVE_WAIT_UNION /* the arg to wait is a union wait * */ ^ "os.h", line 63: warning(1009): nested comment is not allowed /* #define USE_QUOTAS /* comment out if you never want quotas checked */ ^ "os.h", line 79: warning(1009): nested comment is not allowed /* #define NEVER_ALLOW_CHANGING_FROM /* probably not needed */ ^ "os.h", line 90: warning(1009): nested comment is not allowed /* #define BACKGROUND_POST /* comment out to disable posting from child */ ^ "os.h", line 222: warning(1009): nested comment is not allowed /* #define SENDNEWS "/usr/local/bin/inews -h" /* news posting cmd */ ^ "os.h", line 233: warning(1009): nested comment is not allowed /* #define MAXPATH (512) /* Longest pathname we ever expect */ ^ "os.c", line 1038: warning(1116): non-void function "stop_process" (declared at line 1026) should return a value } ^ "os.c", line 1172: warning(1116): non-void function "change_passwd" (declared at line 1158) should return a value } ^ "os.c", line 2899: warning(1116): non-void function "check_for_timeout" (declared at line 2852) should return a value } ^ "os.c", line 3101: warning(1116): non-void function "read_char" (declared at line 2918) should return a value } ^ "os.c", line 3959: warning(1171): expression has no effect *passwd == 2; /* only blat once */ ^ "os.c", line 5117: warning(1116): non-void function "CleartoEOS" (declared at line 5109) should return a value } ^ echo "char datestamp[]="\"`date`\"";" > date.c echo "char hoststamp[]="\"`hostname`\"";" >> date.c cc -g -DDEBUG -ansi -DSGI -DSYSTYPE=\"SGI\" -DMOUSE -o pine addrbook.o adrbkcmd.o adrbklib.o args.o bldaddr.o context.o filter.o folder.o help.o helptext.o imap.o init.o mailcap.o mailcmd.o mailindx.o mailpart.o mailview.o newmail.o other.o pine.o reply.o screen.o send.o signals.o status.o strings.o takeaddr.o os.o date.c ../pico/libpico.a ../c-client/c-client.a -ltermlib `cat ../c-client/LDFLAGS` Links to executables are in bin directory: bin/pine: Section Size Physical Virtual Address Address .interp 21 268435732 268435732 .MIPS.options 128 268435760 268435760 .reginfo 24 268435888 268435888 .dynamic 304 268435912 268435912 .dynamic_2 72 268436216 268436216 .liblist 60 268436288 268436288 .dynstr 49437 268436348 268436348 .hash 29896 268485788 268485788 .dynsym 54016 268515684 268515684 .MIPS.symlib 3369 268569700 268569700 .rel.dyn 24008 268573072 268573072 .msym 27008 268597080 268597080 .MIPS.stubs 3604 268624088 268624088 .text 2295688 268627696 268627696 .init 24 270923392 270923392 .rodata 779138 270925824 270925824 .data 144168 271704968 271704968 .got 9344 271849136 271849136 .srdata_1 48962 271858480 271858480 .sdata_1 348 271907448 271907448 .sbss_1 596 271907800 271907800 .got_2 3948 271908396 271908396 .sbss_2 192 271912344 271912344 .srdata_2 4846 271912536 271912536 .lit4_2 8 271917384 271917384 .sdata_2 96 271917392 271917392 .bss 35380 271917488 271917488 2541467 + 937838 + 35380 = 3514685 bin/mtest: Section Size Physical Virtual Address Address .interp 21 268435732 268435732 .MIPS.options 128 268435760 268435760 .reginfo 24 268435888 268435888 .dynamic 264 268435912 268435912 .liblist 40 268436176 268436176 .dynstr 11604 268436216 268436216 .hash 7920 268447820 268447820 .dynsym 15264 268455740 268455740 .MIPS.symlib 954 268471004 268471004 .msym 7632 268471960 268471960 .MIPS.stubs 2264 268479592 268479592 .text 519928 268481856 268481856 .init 24 269001792 269001792 .rodata 194346 269070336 269070336 .data 21736 269264688 269264688 .got 2716 269286424 269286424 .srdata 4334 269289144 269289144 .sdata 104 269293480 269293480 .sbss 184 269293584 269293584 .bss 2244 269293776 269293776 570401 + 219086 + 2244 = 791731 bin/imapd: Section Size Physical Virtual Address Address .interp 21 268435732 268435732 .MIPS.options 128 268435760 268435760 .reginfo 24 268435888 268435888 .dynamic 272 268435912 268435912 .liblist 40 268436184 268436184 .dynstr 12411 268436224 268436224 .hash 12320 268448636 268448636 .dynsym 16480 268460956 268460956 .MIPS.symlib 1030 268477436 268477436 .msym 8240 268478468 268478468 .conflict 4 268486708 268486708 .MIPS.stubs 2244 268486712 268486712 .text 569640 268488960 268488960 .init 24 269058608 269058608 .rodata 197738 269127680 269127680 .data 21808 269325424 269325424 .got 3052 269347232 269347232 .srdata 4910 269350288 269350288 .sbss 184 269355200 269355200 .sdata 96 269355384 269355384 .bss 9572 269355488 269355488 627788 + 222878 + 9572 = 860238 bin/pico: Section Size Physical Virtual Address Address .interp 21 268435732 268435732 .MIPS.options 128 268435760 268435760 .reginfo 24 268435888 268435888 .dynamic 272 268435912 268435912 .liblist 60 268436184 268436184 .dynstr 5522 268436244 268436244 .hash 6356 268441768 268441768 .dynsym 9008 268448124 268448124 .MIPS.symlib 563 268457132 268457132 .msym 4504 268457696 268457696 .MIPS.stubs 1724 268462200 268462200 .text 240484 268463936 268463936 .init 24 268704432 268704432 .rodata 19235 268771328 268771328 .data 3096 268790568 268790568 .got 1992 268793664 268793664 .srdata 3143 268795656 268795656 .sbss 100 268798800 268798800 .sdata 4 268798900 268798900 .lit4 8 268798904 268798904 .bss 1876 268798912 268798912 271833 + 24435 + 1876 = 298144 bin/pilot: Section Size Physical Virtual Address Address .interp 21 268435732 268435732 .MIPS.options 128 268435760 268435760 .reginfo 24 268435888 268435888 .dynamic 272 268435912 268435912 .liblist 60 268436184 268436184 .dynstr 5519 268436244 268436244 .hash 6352 268441764 268441764 .dynsym 8992 268448116 268448116 .MIPS.symlib 562 268457108 268457108 .msym 4496 268457672 268457672 .MIPS.stubs 1724 268462168 268462168 .text 238756 268463904 268463904 .init 24 268702672 268702672 .rodata 18827 268771328 268771328 .data 2968 268790160 268790160 .got 1976 268793128 268793128 .srdata 3119 268795104 268795104 .sbss 100 268798224 268798224 .sdata 4 268798324 268798324 .lit4 8 268798328 268798328 .bss 1876 268798336 268798336 270049 + 23883 + 1876 = 295808 Done cougar 3# exit exit script done on Fri Oct 2 09:50:33 1998 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 7 Oct 1998 03:22:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA20061 for ; Wed, 7 Oct 1998 03:22:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA22268; Wed, 7 Oct 1998 03:22:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA26804; Wed, 7 Oct 1998 03:19:17 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA09594 for ; Wed, 7 Oct 1998 03:16:19 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA14597 for ; Wed, 7 Oct 1998 03:16:18 -0700 Received: from bom6.vsnl.net.in (bom6.vsnl.net.in [202.54.4.38]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA04559 for ; Wed, 7 Oct 1998 03:16:12 -0700 Received: from localhost (ushaintl@localhost) by bom6.vsnl.net.in (8.9.0/8.9.0) with SMTP id PAA25882 for ; Wed, 7 Oct 1998 15:53:03 +0500 (IST) Message-Id: Date: Wed, 7 Oct 1998 15:53:03 +0500 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: usha international ltd To: Pine Discussion Forum Subject: Re: file attachment In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Sender: ushaintl@bom6 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > To : Anybudy who is using pine > > Fm : ushaintl@bom6.vsnl.net.in > > Can we attach any text file to compose a message for e-mail. > Twxt file which was created through any text editor. > > If yes how ?. please mail me to above address. > > Thanks > > -akhilesh malviya > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 03:06:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id DAA11263 for ; Thu, 8 Oct 1998 03:06:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA22857; Thu, 8 Oct 1998 03:06:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA16905; Thu, 8 Oct 1998 03:04:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA20044 for ; Thu, 8 Oct 1998 03:01:00 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA02495 for ; Thu, 8 Oct 1998 03:01:00 -0700 Received: from bom6.vsnl.net.in (bom6.vsnl.net.in [202.54.4.38]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA05064 for ; Thu, 8 Oct 1998 03:00:54 -0700 Received: from localhost (ushaintl@localhost) by bom6.vsnl.net.in (8.9.0/8.9.0) with SMTP id PAA29571 for ; Thu, 8 Oct 1998 15:37:44 +0500 (IST) Message-Id: Date: Thu, 8 Oct 1998 15:37:44 +0500 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: usha international ltd To: Pine Discussion Forum Subject: Text file attachment in pine In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: pine-info@cac.washington.edu X-Sender: ushaintl@bom6 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 8 Oct 1998, usha international ltd wrote: > > To : Anybudy who is using pine in this universe > > Fm : ushaintl@bom6.vsnl.net.in > > I am holding a shell A/c and using procom+ utility for conectivity. > > I am using pine for my e-mails. I am facing a problem with attachment of > text file from my computer to pine for e-mail. I want copy my text file > from my computer to our local server (host). This facility is not > available in pine (I think so). My esp is VSNL i.e. Videsh Sanchar Nigam > Limited in india. > > Please mail me if any solution in pine or in other way is available with > you. > > Thanking you. > > -Akhilesh Malviya - ushaintl@bom6.vsnl.net.in ( Bhopal-MP-India) > > > > ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 08:11:48 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA17998 for ; Thu, 8 Oct 1998 08:11:47 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA09524; Thu, 8 Oct 1998 08:11:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA03676; Thu, 8 Oct 1998 08:09:05 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA43122 for ; Thu, 8 Oct 1998 08:05:43 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA15717 for ; Thu, 8 Oct 1998 08:05:41 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Thu, 8 Oct 1998 23:05:34 +0800 Message-Id: <001201bdf2cd$10c1b670$1511b381@edspc17.twntpe.cdc.com> Date: Thu, 8 Oct 1998 23:05:19 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Text file attachment in pine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "usha international ltd" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > > To : Anybudy who is using pine in this universe Does the fact that I got this message establish that I am in "this" universe? :-) > > I am holding a shell A/c and using procom+ utility for conectivity. Don't hold it too tightly as it won't be able to breathe. :-) > > I am using pine for my e-mails. I am facing a problem with attachment of > > text file from my computer to pine for e-mail. I want copy my text file > > from my computer to our local server (host). This facility is not > > available in pine (I think so). My esp is VSNL i.e. Videsh Sanchar Nigam > > Limited in india. Ahhh...VSNL my favorite ISP. *NOT*.... > > Please mail me if any solution in pine or in other way is available with > > you. I'm not too familiar with procom+ (I used to be....but I've not used that sort of SW in a long time). However, procom+ should support client/server file transfers using "xmodem" or "zmodem" protocols. Check your documentation. And, you can always try to contact the VSNL helpdesk. Regards, Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 08:50:28 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA18315 for ; Thu, 8 Oct 1998 08:50:27 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10677; Thu, 8 Oct 1998 08:50:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA05495; Thu, 8 Oct 1998 08:46:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA17022 for ; Thu, 8 Oct 1998 08:44:01 -0700 Received: from xmission.xmission.com (root@xmission.xmission.com [198.60.22.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA12987 for ; Thu, 8 Oct 1998 08:44:00 -0700 Received: from wencor.com (root@wencor.com [207.135.128.153]) by xmission.xmission.com (8.8.8/8.7.5) with ESMTP id JAA19594 for ; Thu, 8 Oct 1998 09:43:58 -0600 (MDT) Received: from marvin.wencor.com (marvin.wencor.com [172.16.59.1]) by wencor.com (8.8.8/8.8.8/Debian/GNU) with SMTP id JAA04327 for ; Thu, 8 Oct 1998 09:43:55 -0600 Received: from localhost by marvin.wencor.com (8.6.14/200.17.1.3) id JAA18760; Thu, 8 Oct 1998 09:41:51 -0600 Message-Id: Date: Thu, 8 Oct 1998 09:41:51 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris Wood To: Pine Discussion Forum Subject: Spell Check, then lose email? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just upgraded our system from 4.02a to 4.05. We have ispell installed also. With 4.05, if a user runs the spell checker (ctrl-t), when they come back from ispell, they cannot down arrow. If they up arrow it takes them to the subject, then if they down arrow it deletes the entire email!!! It's gone, can't uncut it. 4.02a didn't have this problem. Anyone else out there running into this? Any tips on trying to figure out what it is? -=-=-=-=-=- Chris Wood Kitco, Inc. 801-489-2097 Wencor West, Inc. [cwood@wencor.com] Durham Aircraft Services -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 10:41:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA21995 for ; Thu, 8 Oct 1998 10:41:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02319; Thu, 8 Oct 1998 10:41:23 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA12362; Thu, 8 Oct 1998 10:38:47 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA09758 for ; Thu, 8 Oct 1998 10:36:00 -0700 Received: from admin.inetport.com (inetport.com [204.96.100.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA04443 for ; Thu, 8 Oct 1998 10:35:59 -0700 Received: from expwncog (ip5.boston-xcom.ma.pub-ip.psi.net [38.26.199.5]) by admin.inetport.com (8.8.8/8.8.5) with SMTP id MAA29041; Thu, 8 Oct 1998 12:35:57 -0500 (CDT) Message-Id: Date: Thu, 8 Oct 1998 13:35:59 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Jonathan E. D. Richmond" To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? In-Reply-To: <85256697.00571B80.00@ksg.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Chris Wood X-Cc: Pine Discussion Forum X-X-Sender: richmond@mail.inetport.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The problem with PINE is that it gets released with too many bugs in it. The file extension problem I mentioned earlier (MTX does not register correctly, resulting in .MTXs being added to all files) is another example. Instead of issuing a new version every other week, it might make sense for the PINE people to take an extra month or so to thoroughly test their new versions and try to eliminate as many bugs as possible! On Thu, 8 Oct 1998, Chris Wood wrote: > Chris Wood > 10/08/98 03:41 PM GMT > > To: Pine Discussion Forum > > cc: > > > > > I just upgraded our system from 4.02a to 4.05. We have ispell installed > also. With 4.05, if a user runs the spell checker (ctrl-t), when they > come back from ispell, they cannot down arrow. If they up arrow it takes > them to the subject, then if they down arrow it deletes the entire > email!!! It's gone, can't uncut it. > > 4.02a didn't have this problem. Anyone else out there running into this? > Any tips on trying to figure out what it is? > > > -=-=-=-=-=- > Chris Wood Kitco, Inc. > 801-489-2097 Wencor West, Inc. > [cwood@wencor.com] Durham Aircraft Services > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > > > ----- Jonathan E. D. Richmond (617) 864-6394 Fellow (617) 496-3194 Taubman Center for State and Local Government FAX: (617) 496-1722 Kennedy School of Government Harvard University Cambridge MA 02138 e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu WWW: http://the-tech.mit.edu/~richmond/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 13:22:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA24080 for ; Thu, 8 Oct 1998 13:22:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA19836; Thu, 8 Oct 1998 13:22:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA14785; Thu, 8 Oct 1998 13:20:03 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA19332 for ; Thu, 8 Oct 1998 13:16:55 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA27578 for ; Thu, 8 Oct 1998 13:16:54 -0700 Received: from D-140-142-110-126.dhcp2.washington.edu (D-140-142-110-126.dhcp2.washington.edu [140.142.110.126]) by mailhost2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA05827; Thu, 8 Oct 1998 13:16:50 -0700 Message-Id: Date: Thu, 8 Oct 1998 13:18:22 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Terry Gray To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Jonathan E. D. Richmond" X-Cc: Pine Discussion Forum X-X-Sender: gray@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Even better would be if we didn't release it at all, since many of these bugs don't occur in the environment we use (and test in)... -teg On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > The problem with PINE is that it gets released with too many bugs in it. > The file extension problem I mentioned earlier (MTX does not register > correctly, resulting in .MTXs being added to all files) is another > example. Instead of issuing a new version every other week, it might make > sense for the PINE people to take an extra month or so to thoroughly test > their new versions and try to eliminate as many bugs as possible! > > > On Thu, 8 Oct 1998, Chris Wood wrote: > > > Chris Wood > > 10/08/98 03:41 PM GMT > > > > To: Pine Discussion Forum > > > > cc: > > > > I just upgraded our system from 4.02a to 4.05. We have ispell installed > > also. With 4.05, if a user runs the spell checker (ctrl-t), when they > > come back from ispell, they cannot down arrow. If they up arrow it takes > > them to the subject, then if they down arrow it deletes the entire > > email!!! It's gone, can't uncut it. > > > > 4.02a didn't have this problem. Anyone else out there running into this? > > Any tips on trying to figure out what it is? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 13:48:43 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA22571 for ; Thu, 8 Oct 1998 13:48:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA20545; Thu, 8 Oct 1998 13:48:35 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA23055; Thu, 8 Oct 1998 13:45:39 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA48414 for ; Thu, 8 Oct 1998 13:42:54 -0700 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA31311 for ; Thu, 8 Oct 1998 13:42:52 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRNCM4>; Thu, 8 Oct 1998 16:46:37 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394F31@POISON> Date: Thu, 8 Oct 1998 16:46:37 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: Spell Check, then lose email? MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Kinda reminds me when I tried to give away a TV set for free. Everyone picked it up, looked at it, smelled it, asked if it worked, wanted to know could they give it back if it didn't. After two hours it sat. Later, I placed a sign on it for $1.00, it sold in 5 minutes no questions asked. Amazing, people want everything when it's free but are willing to settle when they pay for it? I would think if someone paid for the software then it would be more appropriate to demand better testing or more appropriately more varied testing (which is what beta testing is all about and why it says don't stop using the older version until your sure the newer version works). Funny George Gallen ggallen@slackinc.com -----Original Message----- From: Terry Gray [mailto:gray@cac.washington.edu] Sent: Thursday, October 08, 1998 4:18 PM To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? Even better would be if we didn't release it at all, since many of these bugs don't occur in the environment we use (and test in)... -teg On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > The problem with PINE is that it gets released with too many bugs in it. > The file extension problem I mentioned earlier (MTX does not register > correctly, resulting in .MTXs being added to all files) is another > example. Instead of issuing a new version every other week, it might make > sense for the PINE people to take an extra month or so to thoroughly test > their new versions and try to eliminate as many bugs as possible! > > > On Thu, 8 Oct 1998, Chris Wood wrote: > > > Chris Wood > > 10/08/98 03:41 PM GMT > > > > To: Pine Discussion Forum > > > > cc: > > > > I just upgraded our system from 4.02a to 4.05. We have ispell installed > > also. With 4.05, if a user runs the spell checker (ctrl-t), when they > > come back from ispell, they cannot down arrow. If they up arrow it takes > > them to the subject, then if they down arrow it deletes the entire > > email!!! It's gone, can't uncut it. > > > > 4.02a didn't have this problem. Anyone else out there running into this? > > Any tips on trying to figure out what it is? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 13:50:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA26146 for ; Thu, 8 Oct 1998 13:50:56 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA20637; Thu, 8 Oct 1998 13:50:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA16284; Thu, 8 Oct 1998 13:48:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA51420 for ; Thu, 8 Oct 1998 13:44:56 -0700 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id NAA31623 for ; Thu, 8 Oct 1998 13:44:55 -0700 Received: from spike by webster (SMI-8.6/SMI-SVR4) id QAA01506; Thu, 8 Oct 1998 16:47:58 -0400 Message-Id: Date: Thu, 8 Oct 1998 16:46:41 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Terry Gray X-Cc: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Terry, Please don't say things like that! You're scaring me. Shawn Jeffries ujefsh81@vetri.com "Proud user of Pine since 3.89" On Thu, 8 Oct 1998, Terry Gray wrote: >Even better would be if we didn't release it at all, since many of these >bugs don't occur in the environment we use (and test in)... > >-teg > >On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > >> The problem with PINE is that it gets released with too many bugs in it. >> The file extension problem I mentioned earlier (MTX does not register >> correctly, resulting in .MTXs being added to all files) is another >> example. Instead of issuing a new version every other week, it might make >> sense for the PINE people to take an extra month or so to thoroughly test >> their new versions and try to eliminate as many bugs as possible! >> >> >> On Thu, 8 Oct 1998, Chris Wood wrote: >> >> > Chris Wood >> > 10/08/98 03:41 PM GMT >> > >> > To: Pine Discussion Forum >> > >> > cc: >> > >> > I just upgraded our system from 4.02a to 4.05. We have ispell installed >> > also. With 4.05, if a user runs the spell checker (ctrl-t), when they >> > come back from ispell, they cannot down arrow. If they up arrow it takes >> > them to the subject, then if they down arrow it deletes the entire >> > email!!! It's gone, can't uncut it. >> > >> > 4.02a didn't have this problem. Anyone else out there running into this? >> > Any tips on trying to figure out what it is? > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 14:17:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA22469 for ; Thu, 8 Oct 1998 14:17:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA21378; Thu, 8 Oct 1998 14:17:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA21867; Thu, 8 Oct 1998 14:09:01 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA53498 for ; Thu, 8 Oct 1998 14:06:18 -0700 Received: from xmission.xmission.com (root@xmission.xmission.com [198.60.22.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA28935 for ; Thu, 8 Oct 1998 14:06:17 -0700 Received: from wencor.com (root@wencor.com [207.135.128.153]) by xmission.xmission.com (8.8.8/8.7.5) with ESMTP id PAA29415 for ; Thu, 8 Oct 1998 15:06:05 -0600 (MDT) Received: from marvin.wencor.com (marvin.wencor.com [172.16.59.1]) by wencor.com (8.8.8/8.8.8/Debian/GNU) with SMTP id PAA05074 for ; Thu, 8 Oct 1998 15:05:51 -0600 Received: from localhost by marvin.wencor.com (8.6.14/200.17.1.3) id PAA28780; Thu, 8 Oct 1998 15:03:46 -0600 Message-Id: Date: Thu, 8 Oct 1998 15:03:46 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris Wood To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN :) I fully understand what the Pine Development team faces and actually am glad Pine supports DG/UX. What's the best way to find out what is causing this problem? Is there an official bug-report method? Also, would there be a contact person for the dg/ux port of Pine to see if my situation is unique or common across dg/ux? My System: Data General Aviion 5900 (Intel) DG/UX 4.2mu02 On Thu, 8 Oct 1998, Terry Gray wrote: > Even better would be if we didn't release it at all, since many of these > bugs don't occur in the environment we use (and test in)... > > -teg > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 16:39:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA24186 for ; Thu, 8 Oct 1998 16:39:11 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA25359; Thu, 8 Oct 1998 16:39:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA23247; Thu, 8 Oct 1998 16:37:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA49574 for ; Thu, 8 Oct 1998 16:34:14 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA17364 for ; Thu, 8 Oct 1998 16:34:12 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 9 Oct 1998 07:34:06 +0800 Message-Id: <002701bdf314$1a241630$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 9 Oct 1998 07:33:49 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Terry Gray" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Even better would be if we didn't release it at all, since many of these > bugs don't occur in the environment we use (and test in)... You forgot the :-) face at the end, right? Got some bad drugs, right? As is said to Ann Landers many a times.... You blew this one Terry. The proper answer would be, Dear Jonathan, Pine is tested by our development team and a group of beta testers. We will consider asking you to be one of our beta testers. However, we have to warn you that it takes time and dedication. You will be asked to perform testing on a tight schedule and to provide detailed and accurate bug reports. Thanks... > On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > > > The problem with PINE is that it gets released with too many bugs in it. > > The file extension problem I mentioned earlier (MTX does not register > > correctly, resulting in .MTXs being added to all files) is another > > example. Instead of issuing a new version every other week, it > might make > > sense for the PINE people to take an extra month or so to > thoroughly test > > their new versions and try to eliminate as many bugs as possible! > > > > > > On Thu, 8 Oct 1998, Chris Wood wrote: > > > > > Chris Wood > > > 10/08/98 03:41 PM GMT > > > > > > To: Pine Discussion Forum > > > > > > cc: > > > > > > I just upgraded our system from 4.02a to 4.05. We have > ispell installed > > > also. With 4.05, if a user runs the spell checker (ctrl-t), when they > > > come back from ispell, they cannot down arrow. If they up > arrow it takes > > > them to the subject, then if they down arrow it deletes the entire > > > email!!! It's gone, can't uncut it. > > > > > > 4.02a didn't have this problem. Anyone else out there > running into this? > > > Any tips on trying to figure out what it is? > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 17:14:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA26865 for ; Thu, 8 Oct 1998 17:14:28 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA26410; Thu, 8 Oct 1998 17:14:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA27613; Thu, 8 Oct 1998 17:12:51 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA50078 for ; Thu, 8 Oct 1998 17:10:13 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA21919 for ; Thu, 8 Oct 1998 17:10:11 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.A6B3B140@smtpgate.uvm.edu>; Thu, 8 Oct 1998 20:10:10 -0400 Message-Id: Date: Thu, 8 Oct 1998 20:10:01 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN more like, they never fixed the problem in the first place. when they went from 3.xx to 4.xx, that is when you start getting lots of bugs. the releases they make every week (like 4.01 through 4.05), don't have many bugs from version to version, chris wood's example is a rare example Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer http://www.washington.edu/pine On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > > > The problem with PINE is that it gets released with too many bugs in it. > The file extension problem I mentioned earlier (MTX does not register > correctly, resulting in .MTXs being added to all files) is another > example. Instead of issuing a new version every other week, it might make > sense for the PINE people to take an extra month or so to thoroughly test > their new versions and try to eliminate as many bugs as possible! > > > > On Thu, 8 Oct 1998, Chris Wood wrote: > > > Chris Wood > > 10/08/98 03:41 PM GMT > > > > To: Pine Discussion Forum > > > > cc: > > > > > > > > > > I just upgraded our system from 4.02a to 4.05. We have ispell installed > > also. With 4.05, if a user runs the spell checker (ctrl-t), when they > > come back from ispell, they cannot down arrow. If they up arrow it takes > > them to the subject, then if they down arrow it deletes the entire > > email!!! It's gone, can't uncut it. > > > > 4.02a didn't have this problem. Anyone else out there running into this? > > Any tips on trying to figure out what it is? > > > > > > -=-=-=-=-=- > > Chris Wood Kitco, Inc. > > 801-489-2097 Wencor West, Inc. > > [cwood@wencor.com] Durham Aircraft Services > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > > > > > > > ----------------------------------------------------------------- > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/pine/pine-info/ > > ----------------------------------------------------------------- > > > > > > > > ----- > > Jonathan E. D. Richmond (617) 864-6394 > Fellow (617) 496-3194 > Taubman Center for State and Local Government FAX: (617) 496-1722 > Kennedy School of Government > Harvard University > Cambridge MA 02138 > > e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu > WWW: http://the-tech.mit.edu/~richmond/ > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 17:17:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA28401 for ; Thu, 8 Oct 1998 17:17:33 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14068; Thu, 8 Oct 1998 17:17:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA27730; Thu, 8 Oct 1998 17:15:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA51228 for ; Thu, 8 Oct 1998 17:12:00 -0700 Received: from sparky.harvard.edu. (sparky.harvard.edu [128.103.190.81]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA21825 for ; Thu, 8 Oct 1998 17:11:59 -0700 Received: from [128.103.18.49] by sparky.harvard.edu. (SMI-8.6/SMI-SVR4) id UAA21615; Thu, 8 Oct 1998 20:13:50 -0400 Message-Id: Date: Thu, 8 Oct 1998 20:13:30 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Jonathan E. D. Richmond" To: Pine Discussion Forum Subject: RE: Spell Check, then lose email? In-Reply-To: <85256697.008219A3.00@ksg.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ed Greshko X-Cc: Pine Discussion Forum X-X-Sender: richmond@mail.inetport.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I guess the problem is that PINE is developed on a non-commercial basis but has become such an excellent project that a vast array of users depend on it. Especially with the availability of complementary UNIX and PC-PINE versions, this is one of the most flexible emailing programs available, and there's no question that when you're, say, in an Internet cafe in Tibet, the IMAP protocol PINE uses is a million times more desirable than an endlessly slow POP download. Because it has become so popular and widely-used, it is more important to get things right the first time around. There really shouldn't be four versions in one month except to a select group of beta testers! One of my favorite programs is Quark Express. They didn't come up with an upgrade for three years, but when they finally released it, it was virtually flawless... On Thu, 8 Oct 1998, Ed Greshko wrote: > "Ed Greshko" > 10/08/98 11:33 PM GMT > > To: Pine Discussion Forum > > cc: > > > > > > Even better would be if we didn't release it at all, since many of these > > bugs don't occur in the environment we use (and test in)... > > You forgot the :-) face at the end, right? Got some bad drugs, right? > > As is said to Ann Landers many a times.... > > You blew this one Terry. The proper answer would be, > > Dear Jonathan, > > Pine is tested by our development team and a group of beta testers. We > will > consider asking you to be one of our beta testers. However, we have to > warn > you that it takes time and dedication. You will be asked to perform > testing > on a tight schedule and to provide detailed and accurate bug reports. > > Thanks... > > > > On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: > > > > > The problem with PINE is that it gets released with too many bugs in > it. > > > The file extension problem I mentioned earlier (MTX does not register > > > correctly, resulting in .MTXs being added to all files) is another > > > example. Instead of issuing a new version every other week, it > > might make > > > sense for the PINE people to take an extra month or so to > > thoroughly test > > > their new versions and try to eliminate as many bugs as possible! > > > > > > > > > On Thu, 8 Oct 1998, Chris Wood wrote: > > > > > > > Chris Wood > > > > 10/08/98 03:41 PM GMT > > > > > > > > To: Pine Discussion Forum > > > > > > > > cc: > > > > > > > > I just upgraded our system from 4.02a to 4.05. We have > > ispell installed > > > > also. With 4.05, if a user runs the spell checker (ctrl-t), when > they > > > > come back from ispell, they cannot down arrow. If they up > > arrow it takes > > > > them to the subject, then if they down arrow it deletes the entire > > > > email!!! It's gone, can't uncut it. > > > > > > > > 4.02a didn't have this problem. Anyone else out there > > running into this? > > > > Any tips on trying to figure out what it is? > > > > > ----- Jonathan E. D. Richmond (617) 864-6394 Fellow (617) 496-3194 Taubman Center for State and Local Government FAX: (617) 496-1722 Kennedy School of Government Harvard University Cambridge MA 02138 e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu WWW: http://the-tech.mit.edu/~richmond/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 17:34:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA29681 for ; Thu, 8 Oct 1998 17:34:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14427; Thu, 8 Oct 1998 17:34:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA28401; Thu, 8 Oct 1998 17:32:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA60310 for ; Thu, 8 Oct 1998 17:29:56 -0700 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA24059 for ; Thu, 8 Oct 1998 17:29:55 -0700 Received: from spike by webster (SMI-8.6/SMI-SVR4) id UAA04716; Thu, 8 Oct 1998 20:33:04 -0400 Message-Id: Date: Thu, 8 Oct 1998 20:31:47 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: RE: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Jonathan E. D. Richmond" X-Cc: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN But Jonathan - How much did you pay for that upgrade? 1> If you've got a bug to report, that's fine. I am sure that the whole development team would love to here from you. 2> If you want to write some code which fixes something you don't like, by all means, do so. They'll look at it. 3> If you don't like all the version releases because you say they have too many bugs, then just DON'T INSTALL THEM ALL. Shawn Jeffries ujefsh81@vetri.com "I here Eudora's on sale, real cheap." On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: >I guess the problem is that PINE is developed on a non-commercial >basis but has become such an excellent project that a vast array >of users depend on it. Especially with the availability of >complementary UNIX and PC-PINE versions, this is one of the most >flexible emailing programs available, and there's no question that >when you're, say, in an Internet cafe in Tibet, the IMAP protocol >PINE uses is a million times more desirable than an endlessly >slow POP download. > >Because it has become so popular and widely-used, it is more >important to get things right the first time around. There really >shouldn't be four versions in one month except to a select group >of beta testers! > >One of my favorite programs is Quark Express. They didn't come up >with an upgrade for three years, but when they finally released it, >it was virtually flawless... > > > >On Thu, 8 Oct 1998, Ed Greshko wrote: > >> "Ed Greshko" >> 10/08/98 11:33 PM GMT >> >> To: Pine Discussion Forum >> >> cc: >> >> >> >> >> > Even better would be if we didn't release it at all, since many of these >> > bugs don't occur in the environment we use (and test in)... >> >> You forgot the :-) face at the end, right? Got some bad drugs, right? >> >> As is said to Ann Landers many a times.... >> >> You blew this one Terry. The proper answer would be, >> >> Dear Jonathan, >> >> Pine is tested by our development team and a group of beta testers. We >> will >> consider asking you to be one of our beta testers. However, we have to >> warn >> you that it takes time and dedication. You will be asked to perform >> testing >> on a tight schedule and to provide detailed and accurate bug reports. >> >> Thanks... >> >> >> > On Thu, 8 Oct 1998, Jonathan E. D. Richmond wrote: >> > >> > > The problem with PINE is that it gets released with too many bugs in >> it. >> > > The file extension problem I mentioned earlier (MTX does not register >> > > correctly, resulting in .MTXs being added to all files) is another >> > > example. Instead of issuing a new version every other week, it >> > might make >> > > sense for the PINE people to take an extra month or so to >> > thoroughly test >> > > their new versions and try to eliminate as many bugs as possible! >> > > >> > > >> > > On Thu, 8 Oct 1998, Chris Wood wrote: >> > > >> > > > Chris Wood >> > > > 10/08/98 03:41 PM GMT >> > > > >> > > > To: Pine Discussion Forum >> > > > >> > > > cc: >> > > > >> > > > I just upgraded our system from 4.02a to 4.05. We have >> > ispell installed >> > > > also. With 4.05, if a user runs the spell checker (ctrl-t), when >> they >> > > > come back from ispell, they cannot down arrow. If they up >> > arrow it takes >> > > > them to the subject, then if they down arrow it deletes the entire >> > > > email!!! It's gone, can't uncut it. >> > > > >> > > > 4.02a didn't have this problem. Anyone else out there >> > running into this? >> > > > Any tips on trying to figure out what it is? >> > >> >> >> > >----- > >Jonathan E. D. Richmond (617) 864-6394 >Fellow (617) 496-3194 >Taubman Center for State and Local Government FAX: (617) 496-1722 >Kennedy School of Government >Harvard University >Cambridge MA 02138 > >e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu >WWW: http://the-tech.mit.edu/~richmond/ > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 17:41:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA30040 for ; Thu, 8 Oct 1998 17:41:19 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14540; Thu, 8 Oct 1998 17:41:12 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA26251; Thu, 8 Oct 1998 17:39:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA13088 for ; Thu, 8 Oct 1998 17:36:28 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA29552 for ; Thu, 8 Oct 1998 17:36:25 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 9 Oct 1998 08:36:18 +0800 Message-Id: <002901bdf31c$ca619ab0$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 9 Oct 1998 08:36:01 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Spell Check, then lose email? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jonathan E. D. Richmond" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > I guess the problem is that PINE is developed on a non-commercial > basis but has become such an excellent project that a vast array > of users depend on it. Especially with the availability of > complementary UNIX and PC-PINE versions, this is one of the most > flexible emailing programs available, and there's no question that > when you're, say, in an Internet cafe in Tibet, the IMAP protocol > PINE uses is a million times more desirable than an endlessly > slow POP download. > > Because it has become so popular and widely-used, it is more > important to get things right the first time around. There really > shouldn't be four versions in one month except to a select group > of beta testers! > > One of my favorite programs is Quark Express. They didn't come up > with an upgrade for three years, but when they finally released it, > it was virtually flawless... Some people don't mind the number of releases of pine. In truth, not all the bugs fixed in the various releases were a bother to the majority of people. FWIW, I'd been running at 4.02 until I recently had a slow day and decided...what the heck. There were no bug fixes that had an effect on my operations which made it critical to update. I've not heard of Quark Express...but I wonder how many platforms they support and if they also release the source code? The wonderful world of porting to MS-Windows is littered with mine-fields. This is especially true when you talk about MAPI implementations. I've got some lovely horror stories which are currently being experienced. BTW, I'd be cautious about proclaiming Quark Express "virtually flawless". Maybe it just worked for you. I say this since I've experienced a situation where about 3000 seats of a commercial SW package were installed in an Enterprise. Out of the 3000 seats, 2999 of them worked as designed. (That doesn't mean everyone was happy with every feature of the product.) In one case it was just impossible to get it running. Everything possible, short of reinstalling the OS (WinNT) was done. I just have to many applications on my PC and I don't trust a reinstall to try any further. But, getting back to the point, since pine is free and nobody is forcing anyone to use it it may be a better choice on your part to move back to Quark Express. Regards, Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 17:53:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA22185 for ; Thu, 8 Oct 1998 17:53:09 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14691; Thu, 8 Oct 1998 17:53:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA04339; Thu, 8 Oct 1998 17:51:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA56558 for ; Thu, 8 Oct 1998 17:49:05 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA25383 for ; Thu, 8 Oct 1998 17:49:03 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 9 Oct 1998 08:48:57 +0800 Message-Id: <002c01bdf31e$8f316770$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 9 Oct 1998 08:48:41 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: Apples and Oranges MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I've just been made aware that QuarkExpress is actually destop publishing software. So, it would appear, that its comparison with pine was irrelevant to the discussion. Regards, Ed -- Edward M. Greshko Technical Manager, Electronic Commerce GSM: +65-9751-0860 Control Data Asia/Pacific Region PGPKeyID:4B5EDDBF Print:E082 E2FC 2D14 C10D 8E06 3B60 2BCF C959 4B5E DDBF ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Thu, 8 Oct 1998 18:07:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id SAA29816 for ; Thu, 8 Oct 1998 18:07:36 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA27463; Thu, 8 Oct 1998 18:07:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA27521; Thu, 8 Oct 1998 18:06:18 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA43550 for ; Thu, 8 Oct 1998 18:03:38 -0700 Received: from mailhost.cybermania.net.ma ([194.204.198.70]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA32301 for ; Thu, 8 Oct 1998 18:03:36 -0700 Received: from mailhost.cybermania.net.ma (tdaoud@mailhost.cybermania.net.ma [194.204.198.70]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id AAA04275 for ; Fri, 9 Oct 1998 00:53:11 GMT Message-Id: Date: Fri, 9 Oct 1998 00:53:11 +0000 (WET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: Who came first Egg or Chicken? In-Reply-To: <002c01bdf31e$8f316770$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dear All, Latetly our mail boxes were filled with long stream of characters regarding Pine and alternatives. I guess this is not the place to put such comments. Most of the people here do use pine on daily basis and they are here to get help or help the others. Such comments are out of this Discussion list scope. Regards, _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 01:50:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id BAA23844 for ; Fri, 9 Oct 1998 01:50:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA03533; Fri, 9 Oct 1998 01:50:08 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA20325; Fri, 9 Oct 1998 01:48:43 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA20208 for ; Fri, 9 Oct 1998 01:45:23 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA26140 for ; Fri, 9 Oct 1998 01:45:17 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id KAA01462 for ; Fri, 9 Oct 1998 10:45:06 +0200 (CEST) Message-Id: Date: Fri, 9 Oct 1998 10:43:53 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: <002c01bdf31e$8f316770$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi! On Fri, 9 Oct 1998, Ed Greshko wrote: > Hi, > > I've just been made aware that QuarkExpress is actually destop publishing > software. So, it would appear, that its comparison with pine was irrelevant > to the discussion. I'm not sure about that. The number of bugs in a new release *is* relevant. But the problem lies in comparing two completely different models of development. QE is commercial software (http://www.quark.com/), priced at around $700 , i.e., someone is making money out of your copy, Pine is freeware, supported and developed by enthusiasts who are doing it for free! It is *this* difference that makes the comparison irrelevant, like comparing Microsoft Windows (incidentally, do you really trust a company named after its' owner's private parts? sorry, couldn't resist }:-) and Linux. What I'm trying to say is that for your e-mail user agent you can use commercial software (not QE, obviously, but Eudora and other similar products), where you pay for the product, expect it to be bug-free (VERY wishful thinking), and have little or no influence on the features in the next release. On the other hand you can use something like Pine, which is free, in which you do expect an occasional bug to crop up, but where YOU can fix the bug and add new features, if you wish and have the know-how to do so. And even if you cannot do it, there is always someone else in the crowd of many thousands of users and the number of "official" developpers who can and *will* listen to your complaints. Incidentally, has anyone heard of any commercial software that has had 5 bug-fix releases and one patch in just over two months? Now that's rapid response to bug reports! One of the complaints in this thread was about too many releases in too short a time. I just wish I could say the same for the M$ Windows. The solution to the too-many-releases is simple: Just say no! Nobody's forcing anyone to use newer versions. Pine 3.96 was around for about a year and a half and it worked fine. When 4.00 came out I downloaded and compiled it right away because of new features, *expecting* to maybe have some problems (which I didn't have) but also *knowing* that whatever they would be, they would get fixed quickly. Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 04:24:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA06265 for ; Fri, 9 Oct 1998 04:24:16 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA05792; Fri, 9 Oct 1998 04:24:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA12557; Fri, 9 Oct 1998 04:22:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA38362 for ; Fri, 9 Oct 1998 04:18:29 -0700 Received: from violet.csi.cam.ac.uk (violet.csi.cam.ac.uk [131.111.8.58]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA31715 for ; Fri, 9 Oct 1998 04:18:27 -0700 Received: from quinag.csi.cam.ac.uk ([131.111.10.53] helo=cam.ac.uk) by violet.csi.cam.ac.uk with smtp (Exim 2.04 #1) id 0zRaYu-0005S9-00 for pine-info@u.washington.edu; Fri, 9 Oct 1998 12:18:20 +0100 Message-Id: Date: Fri, 9 Oct 1998 12:19:17 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Barry Landy To: Pine Discussion Forum Subject: repeated password requests (pine 4.05) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: bl10@imap.hermes.cam.ac.uk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have had a complaint from someone using Pine4.05 on linux against a multi-host IMAP4 system, that if he gets different hosts as the result of different DNS requests (say for INBOX and a folder-collection) then he is asked for his password more than once. Specifically, he is accessing imap.hermes.x.y.z the DNS says that imap.hermes is actually 2 systems red.p.y.z and green.p.y.z; first access is to red; second to green; then he needs to give the password to permit access to green even though both are the same overwall system under the cover of imap.hermes. Anyone experienced this? ---------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 1223 334600 Head of Systems and Development Direct line: +44 1223 334713 University of Cambridge Computing Service New Museums Site Email:bl10@cam.ac.uk Pembroke Street, Cambridge CB2 3QG ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 04:59:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id EAA05109 for ; Fri, 9 Oct 1998 04:59:51 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA23761; Fri, 9 Oct 1998 04:59:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA13220; Fri, 9 Oct 1998 04:57:53 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA47460 for ; Fri, 9 Oct 1998 04:55:14 -0700 Received: from europe.std.com (europe.std.com [199.172.62.20]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA03810 for ; Fri, 9 Oct 1998 04:55:13 -0700 Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id HAA17670; Fri, 9 Oct 1998 07:55:12 -0400 (EDT) Received: from localhost by world.std.com (TheWorld/Spike-2.0) id AA22473; Fri, 9 Oct 1998 07:55:12 -0400 Message-Id: Date: Fri, 9 Oct 1998 07:55:12 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN thank you jan for expressing what many of us feel... open source is the wave of the future. i still use pine v3.95 and have made pine my choice since 1992 because it simply works! of course, the cost is nice; but that is not the major factor. knowing that i can jump on the internet and get answers is the biggest factor for me. and it is nice that i can keep my 'mouse' hand free for drinking coffee and not HAVE to point and click endlessly to write a note. -jeff On Fri, 9 Oct 1998, Jan Kalin wrote: > Incidentally, has anyone heard of any commercial software that has had 5 > bug-fix releases and one patch in just over two months? Now that's rapid > response to bug reports! One of the complaints in this thread was about > too many releases in too short a time. I just wish I could say the same > for the M$ Windows. The solution to the too-many-releases is simple: Just > say no! > > Nobody's forcing anyone to use newer versions. Pine 3.96 was around for > about a year and a half and it worked fine. When 4.00 came out I > downloaded and compiled it right away because of new features, *expecting* > to maybe have some problems (which I didn't have) but also *knowing* that > whatever they would be, they would get fixed quickly. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 06:28:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA07491 for ; Fri, 9 Oct 1998 06:28:40 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA24822; Fri, 9 Oct 1998 06:28:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA24742; Fri, 9 Oct 1998 06:27:02 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA52072 for ; Fri, 9 Oct 1998 06:24:10 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA05275 for ; Fri, 9 Oct 1998 06:24:02 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id PAA08403 for ; Fri, 9 Oct 1998 15:24:00 +0200 (CEST) Message-Id: Date: Fri, 9 Oct 1998 15:22:53 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Jeff A Kinsey wrote: > thank you jan for expressing what many of us feel... open source is > the wave of the future. i still use pine v3.95 and have made pine my > choice since 1992 because it simply works! of course, the cost is > nice; but that is not the major factor. knowing that i can jump > on the internet and get answers is the biggest factor for me. > > and it is nice that i can keep my 'mouse' hand free for drinking > coffee and not HAVE to point and click endlessly to write a note. Not to mention the fact that Pine is the only mail client I know of which works exactly the same on all the platforms I use (PC, SGI Indy and Sun Sparcstation) or am likely to use. Add to this the ability to store addressbooks on the server without having to install directory server programs (e.g., LDAP) and the availability of vim (Vi IMproved editor) on both PC and Unix systems, and I now have a single mail program which behaves exactly the same from wherever I choose to access my mail and which enables me to have exactly the same state of my mail folders whenever I use it. And even when I occasionally want to access mail from somewhere else, I can always telnet to one of the machines and I'm in business. Correct me if I'm wrong, but I can't think of any other setup which would come near this. This is also the only mailer I've seen which *really* is simple enough for a complete beginner to use and has enough features to satisfy probably the most demanding power users (hooks for filters, external editor...) . To illustrate, my girlfriend barely sat down in front of computer before I left Slovenia for a temporary job in Belgium (she's almost has a computerphobia), but is now happily using Pine (and solitaire :) She's even happier with the v4.00 which can fire up Netscape to look at URLs I send her through the mail (before this she wasn't quite sure what to do with the URLs in spite of instructions). But then the readers of this forum are probably aware of the advantages of Pine so I'm probably just gathering points with the developers in case I have something I'd like to see in Pine ;) Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 06:48:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA09119 for ; Fri, 9 Oct 1998 06:47:59 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA25064; Fri, 9 Oct 1998 06:47:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA15903; Fri, 9 Oct 1998 06:45:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA34586 for ; Fri, 9 Oct 1998 06:42:35 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA06805 for ; Fri, 9 Oct 1998 06:42:31 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id PAA08602 for ; Fri, 9 Oct 1998 15:42:29 +0200 (CEST) Message-Id: Date: Fri, 9 Oct 1998 15:41:16 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: repeated password requests (pine 4.05) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Barry Landy wrote: > I have had a complaint from someone using Pine4.05 on linux against a > multi-host IMAP4 system, that if he gets different hosts as the result > of different DNS requests (say for INBOX and a folder-collection) then > he is asked for his password more than once. > > Specifically, he is accessing imap.hermes.x.y.z > the DNS says that imap.hermes is actually 2 systems red.p.y.z and > green.p.y.z; first access is to red; second to green; then he needs to > give the password to permit access to green even though both are the > same overwall system under the cover of imap.hermes. > > Anyone experienced this? Not exactly this, but something similar. My .pinerc has mail.zag.si (one of the aliases for the mail server) listed as the mail server, but the password prompt is for gluon.zag.si (the 'real' name). A simple solution would be to just specify either red... or green... as the mail server (and of course the location of folder collections), but that's probably not what you want... Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 07:01:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA09137 for ; Fri, 9 Oct 1998 07:01:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA07740; Fri, 9 Oct 1998 07:01:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA16504; Fri, 9 Oct 1998 07:00:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA31212 for ; Fri, 9 Oct 1998 06:57:23 -0700 Received: from violet.csi.cam.ac.uk (violet.csi.cam.ac.uk [131.111.8.58]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA07669 for ; Fri, 9 Oct 1998 06:57:18 -0700 Received: from quinag.csi.cam.ac.uk ([131.111.10.53] helo=cam.ac.uk) by violet.csi.cam.ac.uk with smtp (Exim 2.04 #1) id 0zRd2a-00040E-00; Fri, 9 Oct 1998 14:57:08 +0100 Message-Id: Date: Fri, 9 Oct 1998 14:58:05 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Barry Landy To: Pine Discussion Forum Subject: Re: repeated password requests (pine 4.05) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jan Kalin X-Cc: Pine Discussion Forum X-X-Sender: bl10@imap.hermes.cam.ac.uk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Jan Kalin wrote: :>On Fri, 9 Oct 1998, Barry Landy wrote: :> :>> I have had a complaint from someone using Pine4.05 on linux against a :>> multi-host IMAP4 system, that if he gets different hosts as the result :>> of different DNS requests (say for INBOX and a folder-collection) then :>> he is asked for his password more than once. :>> :>> Specifically, he is accessing imap.hermes.x.y.z :>> the DNS says that imap.hermes is actually 2 systems red.p.y.z and :>> green.p.y.z; first access is to red; second to green; then he needs to :>> give the password to permit access to green even though both are the :>> same overwall system under the cover of imap.hermes. :>> :>> Anyone experienced this? :> :>Not exactly this, but something similar. My .pinerc has mail.zag.si (one :>of the aliases for the mail server) listed as the mail server, but the :>password prompt is for gluon.zag.si (the 'real' name). :> :>A simple solution would be to just specify either red... or green... as :>the mail server (and of course the location of folder collections), but :>that's probably not what you want... no, and it is (for very good reasons) forbidden locally (indeed, I hold the rules...!) - of course, we upgrade the machines regularly and it is pften necessary to change the names to get a transparent upgrade. ---------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 1223 334600 Head of Systems and Development Direct line: +44 1223 334713 University of Cambridge Computing Service New Museums Site Email:bl10@cam.ac.uk Pembroke Street, Cambridge CB2 3QG From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 08:22:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA08363 for ; Fri, 9 Oct 1998 08:22:42 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA09355; Fri, 9 Oct 1998 08:22:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA29392; Fri, 9 Oct 1998 08:20:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA38888 for ; Fri, 9 Oct 1998 08:17:14 -0700 Received: from xmission.xmission.com (root@xmission.xmission.com [198.60.22.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA18408 for ; Fri, 9 Oct 1998 08:17:14 -0700 Received: from wencor.com (root@wencor.com [207.135.128.153]) by xmission.xmission.com (8.8.8/8.7.5) with ESMTP id JAA17372 for ; Fri, 9 Oct 1998 09:17:10 -0600 (MDT) Received: from marvin.wencor.com (marvin.wencor.com [172.16.59.1]) by wencor.com (8.8.8/8.8.8/Debian/GNU) with SMTP id JAA08019 for ; Fri, 9 Oct 1998 09:17:08 -0600 Received: from localhost by marvin.wencor.com (8.6.14/200.17.1.3) id JAA27760; Fri, 9 Oct 1998 09:15:04 -0600 Message-Id: Date: Fri, 9 Oct 1998 09:15:04 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris Wood To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Not to mention the fact that Pine is the only mail client I know of which > works exactly the same on all the platforms I use (PC, SGI Indy and Sun > Sparcstation) or am likely to use. Add to this the ability to store > addressbooks on the server without having to install directory server > programs (e.g., LDAP) and the availability of vim (Vi IMproved editor) on I have been in search of how to let a pc-pine 4.x see the addressbook on my unix machine that all of my unix pine 4.x people use. How do I go about this without using LDAP? -=-=-=-=-=- Chris Wood Kitco, Inc. [cwood@wencor.com] Durham Aircraft Services -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 09:19:45 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA10450 for ; Fri, 9 Oct 1998 09:19:44 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA11058; Fri, 9 Oct 1998 09:19:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA23043; Fri, 9 Oct 1998 09:17:40 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA51824 for ; Fri, 9 Oct 1998 09:15:45 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA23630 for ; Fri, 9 Oct 1998 09:15:42 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id SAA10527 for ; Fri, 9 Oct 1998 18:15:40 +0200 (CEST) Message-Id: Date: Fri, 9 Oct 1998 18:14:34 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Chris Wood wrote: > > Not to mention the fact that Pine is the only mail client I know of which > > works exactly the same on all the platforms I use (PC, SGI Indy and Sun > > Sparcstation) or am likely to use. Add to this the ability to store > > addressbooks on the server without having to install directory server > > programs (e.g., LDAP) and the availability of vim (Vi IMproved editor) on > > I have been in search of how to let a pc-pine 4.x see the addressbook on > my unix machine that all of my unix pine 4.x people use. How do I go > about this without using LDAP? This is an excerpt from "HELP ON CONFIGURING ADDRESS BOOKS" from Pine 4.05: ======================================================================== Please note: Remote address books stored on an IMAP server are of an entirely different format (namely, a special-purpose "mail folder") than that of the local addressbook familiar to Pine users. Therefore, you cannot use "add a remote address book" to make an existing Pine .addressbook file you may have on a remote IMAP server accessible to Pine running on a different host. ======================================================================== So you cannot direcly access a Unix local address book. What you can do is install an IMAP server on the Unix box (if it isn't already running), move Unix local address books to 'remote' address books actually residing on the Unix machine and have PCPine access the same remote address books. Here's how I did it: My setup: - login account on "mail.zag.si" (also the mail server, so no need for extra IMAP installation) - username "jkalin" - personal mail directory "~/mail" - personal address book "~/mail/.addressbook" In both Unix Pine and PCPine I have added the personal address book (with ain / etup / ddressBooks / dd Pers Abook): Server Name : mail.zag.si/user=jkalin Folder Name : mail/.addressbook Nickname : I have then copied with Unix Pine all of the entries in the (former) Unix address book to the new remote address book by (thanks to someone on the forum - I don't remember who - for this tip) - going to ain / ddress Book - opening the local address book - selecting all with <;> / select ll - and saving them with pply / ave / ave to the remote address book If the login account is on a different machine than the mail server, you will presumably be prompted for the login password when you first access the address book in a Pine session. I hope this answers your question. Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 11:14:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA13455 for ; Fri, 9 Oct 1998 11:14:29 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA01603; Fri, 9 Oct 1998 11:14:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA09586; Fri, 9 Oct 1998 11:11:19 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA50166 for ; Fri, 9 Oct 1998 11:09:09 -0700 Received: from admin.inetport.com (inetport.com [204.96.100.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA07043 for ; Fri, 9 Oct 1998 11:09:08 -0700 Received: from expwncog (ip45.boston-xcom.ma.pub-ip.psi.net [38.26.199.45]) by admin.inetport.com (8.8.8/8.8.5) with SMTP id NAA11078; Fri, 9 Oct 1998 13:08:50 -0500 (CDT) Message-Id: Date: Fri, 9 Oct 1998 14:08:51 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Jonathan E. D. Richmond" To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: <85256698.0030CAB1.00@ksg.harvard.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jan Kalin X-Cc: Pine Discussion Forum X-X-Sender: richmond@mail.inetport.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN AH... But PINE is so much better than commercial products like Eudora! Elegantly designed. highly functional and flexible! I would be happy to pay for it -- in fact, I do pay for it in a way because my School's system won't run UNIX PINE (which is available in other parts of Harvard which won't, however, allow us accounts) and I pay to use an ISP in Texas, which is the nearest one I could find that does IMAP! The point is that because PINE is such a high quality product and has a huge user base -- including many computer novice types (eg. Humanistically-inclined freshmen using email for the first time) that a little restraint is in order over the number of updates to allow more time for bug-checking. On Fri, 9 Oct 1998, Jan Kalin wrote: > Jan Kalin > 10/09/98 08:43 AM GMT > > To: Pine Discussion Forum > > cc: > > > > Hi! > > On Fri, 9 Oct 1998, Ed Greshko wrote: > > > Hi, > > > > I've just been made aware that QuarkExpress is actually destop publishing > > software. So, it would appear, that its comparison with pine was > irrelevant > > to the discussion. > > I'm not sure about that. The number of bugs in a new release *is* > relevant. But the problem lies in comparing two completely different > models of development. > > QE is commercial software (http://www.quark.com/), priced at around $700 , > i.e., someone is making money out of your copy, Pine is freeware, > supported and developed by enthusiasts who are doing it for free! It is > *this* difference that makes the comparison irrelevant, like comparing > Microsoft Windows (incidentally, do you really trust a company named after > its' owner's private parts? sorry, couldn't resist }:-) and Linux. > > What I'm trying to say is that for your e-mail user agent you can use > commercial software (not QE, obviously, but Eudora and other similar > products), where you pay for the product, expect it to be bug-free (VERY > wishful thinking), and have little or no influence on the features in the > next release. > > On the other hand you can use something like Pine, which is free, in which > you do expect an occasional bug to crop up, but where YOU can fix the bug > and add new features, if you wish and have the know-how to do so. And even > if you cannot do it, there is always someone else in the crowd of many > thousands of users and the number of "official" developpers who can and > *will* listen to your complaints. > > Incidentally, has anyone heard of any commercial software that has had 5 > bug-fix releases and one patch in just over two months? Now that's rapid > response to bug reports! One of the complaints in this thread was about > too many releases in too short a time. I just wish I could say the same > for the M$ Windows. The solution to the too-many-releases is simple: Just > say no! > > Nobody's forcing anyone to use newer versions. Pine 3.96 was around for > about a year and a half and it worked fine. When 4.00 came out I > downloaded and compiled it right away because of new features, *expecting* > to maybe have some problems (which I didn't have) but also *knowing* that > whatever they would be, they would get fixed quickly. > > Cheers, > Jan > > -- > Jan Kalin (male, preferred languages: Slovene, English) > contact information > > > > ----- Jonathan E. D. Richmond (617) 864-6394 Fellow (617) 496-3194 Taubman Center for State and Local Government FAX: (617) 496-1722 Kennedy School of Government Harvard University Cambridge MA 02138 e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu WWW: http://the-tech.mit.edu/~richmond/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 11:32:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA05322 for ; Fri, 9 Oct 1998 11:32:57 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA14986; Fri, 9 Oct 1998 11:32:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA02976; Fri, 9 Oct 1998 11:30:18 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA47468 for ; Fri, 9 Oct 1998 11:28:30 -0700 Received: from fluke.com (mail.fluke.com [206.138.179.7]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA09985 for ; Fri, 9 Oct 1998 11:28:29 -0700 Received: by gateway2.fluke.com id <27879>; Fri, 9 Oct 1998 11:28:01 -0700 Message-Id: <98Oct9.112801pdt.27879@gateway2.fluke.com> Date: Fri, 9 Oct 1998 11:28:14 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: David Dyck To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Jonathan E. D. Richmond" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Jonathan E. D. Richmond wrote: > ... that a little restraint is in order over the number of updates to > allow more time for bug-checking. But shouldn't the restraint be on the system administrators that are installing the latest versions, (until they have checked out the features, or waited for other pioniers to test them out) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 11:48:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA11890 for ; Fri, 9 Oct 1998 11:48:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA15474; Fri, 9 Oct 1998 11:48:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA09056; Fri, 9 Oct 1998 11:42:57 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA38210 for ; Fri, 9 Oct 1998 11:40:32 -0700 Received: from nimbus.anzio.com (bezell@nimbus.anzio.com [204.201.253.34]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA12231 for ; Fri, 9 Oct 1998 11:40:31 -0700 Received: from localhost (bezell@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id LAA30024; Fri, 9 Oct 1998 11:39:36 -0700 Message-Id: Date: Fri, 9 Oct 1998 11:39:36 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bobby Ezell To: Pine Discussion Forum Subject: Re: Apples and Oranges In-Reply-To: <98Oct9.112801pdt.27879@gateway2.fluke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: David Dyck X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, David Dyck wrote: > On Fri, 9 Oct 1998, Jonathan E. D. Richmond wrote: > > > ... that a little restraint is in order over the number of updates to > > allow more time for bug-checking. > > But shouldn't the restraint be on the system administrators > that are installing the latest versions, (until they have > checked out the features, or waited for other pioniers to > test them out) Agreed - especially since the hardest part of any released software is testing it under all the circumstances and with all the oddities out there. Sometimes calling it "beta" just doesn't cut it as most of us will really avoid it then. Overall, if a sysadmin finds a problem in their test criteria it should not be handed over to end-user use (or the sysadmin needs to expand their testing). ------------------------------------------------------------------- Bobby Ezell E-Mail: bezell@anzio.com Technical Sales Support V-Mail: 503-624-0360 (voice) Rasmussen Software, Inc. F-Mail: 503-624-0760 (fax) 10240 SW Nimbus Ave., Ste L9 http://www.anzio.com Portland, OR 97223 http://www.anzio.com/~bezell ------------------------------------------------------------------- AnzioLite and AnzioWin for all your telnet needs Send sales & support questions to: rsi@anzio.com =================================================================== From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 12:13:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA15251 for ; Fri, 9 Oct 1998 12:13:50 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA16139; Fri, 9 Oct 1998 12:13:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA11202; Fri, 9 Oct 1998 12:11:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA39946 for ; Fri, 9 Oct 1998 12:09:45 -0700 Received: from xmission.xmission.com (root@xmission.xmission.com [198.60.22.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA16666 for ; Fri, 9 Oct 1998 12:09:45 -0700 Received: from wencor.com (root@wencor.com [207.135.128.153]) by xmission.xmission.com (8.8.8/8.7.5) with ESMTP id NAA05824 for ; Fri, 9 Oct 1998 13:09:42 -0600 (MDT) Received: from marvin.wencor.com (marvin.wencor.com [172.16.59.1]) by wencor.com (8.8.8/8.8.8/Debian/GNU) with SMTP id NAA08630 for ; Fri, 9 Oct 1998 13:09:39 -0600 Received: from localhost by marvin.wencor.com (8.6.14/200.17.1.3) id NAA26655; Fri, 9 Oct 1998 13:07:35 -0600 Message-Id: Date: Fri, 9 Oct 1998 13:07:35 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chris Wood To: Pine Discussion Forum Subject: Remote Address Books (was Re: Apples and Oranges) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Jan Kalin wrote: > > So you cannot direcly access a Unix local address book. What you can do is > install an IMAP server on the Unix box (if it isn't already running), move > Unix local address books to 'remote' address books actually residing on > the Unix machine and have PCPine access the same remote address books. Is this assuming that the unix pine is accessing things via IMAP just as pc-pine is? or... is this assuming unix pine is accessing things locally and pc-pine is accessing things via IMAP? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Fri, 9 Oct 1998 14:17:30 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id OAA05940 for ; Fri, 9 Oct 1998 14:17:29 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA19504; Fri, 9 Oct 1998 14:17:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA10815; Fri, 9 Oct 1998 14:15:45 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA18800 for ; Fri, 9 Oct 1998 14:13:33 -0700 Received: from indigo.cs.bgu.ac.il (indigo.cs.bgu.ac.il [132.72.42.23]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id OAA01182 for ; Fri, 9 Oct 1998 14:13:30 -0700 Received: from cyan.cs.bgu.ac.il (elad@cyan.cs.bgu.ac.il [132.72.42.12]) by indigo.cs.bgu.ac.il (8.6.9/8.6.10) with ESMTP id XAA03821 for ; Fri, 9 Oct 1998 23:13:21 +0200 Received: from localhost (elad@localhost) by cyan.cs.bgu.ac.il (8.9.0/8.6.9) with SMTP id XAA01178 for ; Fri, 9 Oct 1998 23:13:21 +0200 (IST) Message-Id: Date: Fri, 9 Oct 1998 23:13:21 +0200 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Elad Eyal To: Pine Discussion Forum Subject: Local vs Remote addressbooks (Was: Apples and Oranges) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: cyan.cs.bgu.ac.il: elad owned process doing -bs X-Sender: elad@cyan.bgu.ac.il X-Attribution: EE X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Good morning, > ======================================================================== > Please note: Remote address books stored on an IMAP server are of an > entirely different format (namely, a special-purpose "mail folder") than > that of the local addressbook familiar to Pine users. Therefore, you > cannot use "add a remote address book"to make an existing Pine > .addressbook file you may have on a remote IMAP server accessible to Pine > running on a different host. > ======================================================================== Alas, you can't, can you. Which means - if you're anything like me - you'd have to key in your password, /even though/ the addressbook is a local file. I wonder if there's a collosally good reason why Pine can't read and write a remote addressbook locally. _ (_ / _ / ( E-mail pigeons nest in binary trees ) (__/__(/\_(/ http://www.cs.bgu.ac.il/~elad ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 12:45:37 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA18390 for ; Sun, 11 Oct 1998 12:45:35 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA11061; Sun, 11 Oct 1998 12:45:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA06396; Sun, 11 Oct 1998 12:42:39 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA47510 for ; Sun, 11 Oct 1998 12:39:27 -0700 Received: from goodnet.com (goodnet.com [207.98.129.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA30881 for ; Sun, 11 Oct 1998 12:39:27 -0700 Received: from localhost by goodnet.com with ESMTP id MAA05192 for ; Sun, 11 Oct 1998 12:42:27 -0700 (MST) Message-Id: Date: Sun, 11 Oct 1998 12:42:26 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Kathleen P. Daily-Herrman" To: Pine Discussion Forum Subject: NASCA Telnet.. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi.. I'm going to need to download this program so I can print from Pine Mail under Windows 95. I've look though the http://www.tucows.com site under telnet applications and didn't find it. Does anyone have the url for this program? Thank you for any assistance. much appreciated Kathleen ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 12:53:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA09842 for ; Sun, 11 Oct 1998 12:53:13 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA11134; Sun, 11 Oct 1998 12:53:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA14291; Sun, 11 Oct 1998 12:50:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA43216 for ; Sun, 11 Oct 1998 12:48:22 -0700 Received: from mailhost.cybermania.net.ma ([194.204.198.70]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA29833 for ; Sun, 11 Oct 1998 12:48:05 -0700 Received: from mailhost.cybermania.net.ma (tdaoud@mailhost.cybermania.net.ma [194.204.198.70]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id TAA09217; Sun, 11 Oct 1998 19:36:58 GMT Message-Id: Date: Sun, 11 Oct 1998 19:36:58 +0000 (WET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Kathleen P. Daily-Herrman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > find it. Does anyone have the url for > this program? ftp://ftp.cac.washington.edu/pine/pcpine/ Regards, _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 13:06:10 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id NAA18455 for ; Sun, 11 Oct 1998 13:06:09 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA24385; Sun, 11 Oct 1998 13:06:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA14762; Sun, 11 Oct 1998 13:02:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA58706 for ; Sun, 11 Oct 1998 12:59:35 -0700 Received: from zugzug.cfar.umd.edu (root@zugzug.cfar.umd.edu [128.8.132.82]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA30393 for ; Sun, 11 Oct 1998 12:59:34 -0700 Received: from cfar.umd.edu (adam@localhost [127.0.0.1]) by zugzug.cfar.umd.edu (8.9.1/8.9.1) with ESMTP id PAA14786; Sun, 11 Oct 1998 15:59:10 -0400 (EDT) Message-Id: <199810111959.PAA14786@zugzug.cfar.umd.edu> Date: Sun, 11 Oct 1998 15:59:09 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adam Sulmicki To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: Your message of "Sun, 11 Oct 1998 19:36:58 -0000." X-To: Tawfik Daoud X-Cc: Pine Discussion Forum , adam@cfar.umd.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Tawfik Daoud writes: ->On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: -> ->> find it. Does anyone have the url for ->> this program? -> ->ftp://ftp.cac.washington.edu/pine/pcpine/ I don't think he was looking for PC pine -- I would not think he wants to have his mail delivered to his box. For example he may not have const IP. (True, one still could use imap, assuming server supports it) The best solution would be of course to install Linux :) Adam From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 15:07:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA19385 for ; Sun, 11 Oct 1998 15:07:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA25833; Sun, 11 Oct 1998 15:07:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA17796; Sun, 11 Oct 1998 15:04:42 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA43012 for ; Sun, 11 Oct 1998 15:01:29 -0700 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA06373 for ; Sun, 11 Oct 1998 15:01:26 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id GAA11436; Mon, 12 Oct 1998 06:54:26 +0930 Message-Id: Date: Mon, 12 Oct 1998 06:54:25 +0930 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Kathleen P. Daily-Herrman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > > > > Hi.. > > > I'm going to need to download this program > so I can print from Pine Mail under > Windows 95. Really? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 15:37:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA03948 for ; Sun, 11 Oct 1998 15:37:08 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13083; Sun, 11 Oct 1998 15:37:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA11192; Sun, 11 Oct 1998 15:34:01 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA43740 for ; Sun, 11 Oct 1998 15:31:26 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA06799 for ; Sun, 11 Oct 1998 15:31:24 -0700 Received: from fireball.control-risks.de (port205.koeln.ndh.net [195.94.92.205]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id AAA13897 for ; Mon, 12 Oct 1998 00:31:20 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id XAA05199; Sun, 11 Oct 1998 23:14:07 +0200 Message-Id: <19981011231407.A5183@fireball.control-risks.de> Date: Sun, 11 Oct 1998 23:14:07 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: <199810111959.PAA14786@zugzug.cfar.umd.edu>; from Adam Sulmicki on Sun, Oct 11, 1998 at 03:59:09PM -0400 References: <199810111959.PAA14786@zugzug.cfar.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Adam Sulmicki (adam@cfar.umd.edu): > Tawfik Daoud writes: > ->On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > -> > ->> find it. Does anyone have the url for this program? > -> > ->ftp://ftp.cac.washington.edu/pine/pcpine/ > > I don't think he was looking for PC pine [...] > The best solution would be of course to install Linux :) Not necessarily. I'm currently putting together a presentation, and I couldn't do that with StarOffice for Linux because my boss doesn't have that on his laptop. Duhhh... So I do what every Wintendo-player should do: I use MIX (the MicroImages X-Server) to connect to my Linux server (guess what, a mail- and newsserver will most happily run on a 486DX30 with 8MB). My own server is actually a little better, because I use it as an intranetserver, proxy, and application server for XEmacs, LyX and the like for my fiancee (Mac) and me (dual boot Linux/Windog). Great stuff. Off topic? Sure. So: how do I change the darn from: line in pine? Just kidding. Have a nice one, Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 15:41:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA16469 for ; Sun, 11 Oct 1998 15:41:24 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13137; Sun, 11 Oct 1998 15:41:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA19176; Sun, 11 Oct 1998 15:40:00 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA28460 for ; Sun, 11 Oct 1998 15:37:27 -0700 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA07003 for ; Sun, 11 Oct 1998 15:37:25 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id HAA11539; Mon, 12 Oct 1998 07:30:24 +0930 Message-Id: Date: Mon, 12 Oct 1998 07:30:23 +0930 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: <199810111959.PAA14786@zugzug.cfar.umd.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Adam Sulmicki X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Adam Sulmicki wrote: > Tawfik Daoud writes: > ->On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > -> > ->> find it. Does anyone have the url for > ->> this program? > -> > ->ftp://ftp.cac.washington.edu/pine/pcpine/ > > I don't think he was looking for PC pine -- I would not think he wants > to have his mail delivered to his box. For example he may not have > const IP. (True, one still could use imap, assuming server > supports it) > > The best solution would be of course to install Linux :) One can only guess that she has terminal access to pine running remotely on a multiuser computer, and possibly that it's not accessible to her on a LAN nor on a PPP link. But I still don't understand why she can use NCSA Telnet but not W95 telnet, since she says (I think) that she is using W95. But whatever the case may be as to that, the pine host presumably has imapd. Tawfik Doud mailed a hint as to a _possibly_ better solution than the one she had in mind. Even if she needs to transfer files from the pine host to her Microsoft computer (or vice versa) to print them, she doesn't need telnet, but ftp or zmodem. NCSA Telnet is around, and with a bit of effort the URL could be located, but it's a curious request. Perhaps Kathleen can tell us more about her situation. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 15:49:51 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id PAA20190 for ; Sun, 11 Oct 1998 15:49:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13231; Sun, 11 Oct 1998 15:49:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA19429; Sun, 11 Oct 1998 15:48:57 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA58794 for ; Sun, 11 Oct 1998 15:46:17 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA06287 for ; Sun, 11 Oct 1998 15:46:16 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id QAA08655 for ; Sun, 11 Oct 1998 16:46:16 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id QAA09636 for ; Sun, 11 Oct 1998 16:43:44 -0600 (MDT) Message-Id: Date: Sun, 11 Oct 1998 16:40:20 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 Oct 1998, Michael Talbot-Wilson wrote: > One can only guess that she has terminal access to pine running > remotely on a multiuser computer, and possibly that it's not > accessible to her on a LAN nor on a PPP link. But I still don't > understand why she can use NCSA Telnet but not W95 telnet, since she > says (I think) that she is using W95. because the telnet that ships with windows is utterly and completely brain-dead. It can't even emulate VT100 correctly. FYI, NCSA telnet is probably at ncsa.uiuc.edu. However, CRT is one of the best terminal programs under windows (they even have a version now that supports secure connections via SSH and serial connections. www.vandyke.com. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 16:03:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA09461 for ; Sun, 11 Oct 1998 16:03:51 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA26424; Sun, 11 Oct 1998 16:03:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA11983; Sun, 11 Oct 1998 16:02:28 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA28606 for ; Sun, 11 Oct 1998 15:59:49 -0700 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA06995 for ; Sun, 11 Oct 1998 15:59:47 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id HAA11612; Mon, 12 Oct 1998 07:52:47 +0930 Message-Id: Date: Mon, 12 Oct 1998 07:52:46 +0930 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ian Hall-Beyer X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Ian Hall-Beyer wrote: > FYI, NCSA telnet is probably at ncsa.uiuc.edu. However, CRT is one of the Probably. But it would probably be better to get it from somewhere else where it has had some more recent development. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 16:06:40 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA13950 for ; Sun, 11 Oct 1998 16:06:39 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13418; Sun, 11 Oct 1998 16:06:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA19958; Sun, 11 Oct 1998 16:05:33 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA58646 for ; Sun, 11 Oct 1998 16:02:16 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA08328 for ; Sun, 11 Oct 1998 16:02:13 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id TAA29221 for ; Sun, 11 Oct 1998 19:02:11 -0400 (EDT) Received: from sosue.me.mtu.edu (sosue.me.mtu.edu [141.219.26.133]) by mtu.edu (8.8.8/8.8.8) with ESMTP id TAA03867 for ; Sun, 11 Oct 1998 19:02:10 -0400 (EDT) Received: from doeray.me.mtu.edu (doeray.me.mtu.edu [141.219.26.131]) by sosue.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with ESMTP id TAA25680 for ; Sun, 11 Oct 1998 19:02:09 -0400 (EDT) Message-Id: Date: Sun, 11 Oct 1998 19:02:07 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: edan@doeray.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Ian Hall-Beyer wrote: > FYI, NCSA telnet is probably at ncsa.uiuc.edu. However, CRT is one of the > best terminal programs under windows (they even have a version now that > supports secure connections via SSH and serial connections. > www.vandyke.com. To futher add to the off-topic discussion, TeraTerm Pro is a free (with source) terminal emulator for those times when you're forced to be on a M$ operating system. It also supports the ssh protocol. http://www.zip.com.au/~roca/ttssh.html It's perhaps not quite as slick as CRT, but it is totally free. To make this relevant to Pine discussion, I will add that I have used Pine with ttssh and it worked well. - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 16:36:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id QAA07560 for ; Sun, 11 Oct 1998 16:36:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13791; Sun, 11 Oct 1998 16:36:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA13629; Sun, 11 Oct 1998 16:34:42 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA58630 for ; Sun, 11 Oct 1998 16:32:06 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA09904 for ; Sun, 11 Oct 1998 16:32:06 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id RAA10206 for ; Sun, 11 Oct 1998 17:32:05 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id RAA18743 for ; Sun, 11 Oct 1998 17:29:34 -0600 (MDT) Message-Id: Date: Sun, 11 Oct 1998 17:26:10 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: NASCA Telnet.. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 11 Oct 1998, Edan Idzerda wrote: > To futher add to the off-topic discussion, TeraTerm Pro is a free (with > source) terminal emulator for those times when you're forced to be on > a M$ operating system. It also supports the ssh protocol. Excellent. Free source should be encouraged. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Sun, 11 Oct 1998 20:26:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id UAA17687 for ; Sun, 11 Oct 1998 20:26:26 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA29595; Sun, 11 Oct 1998 20:26:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA19180; Sun, 11 Oct 1998 20:24:51 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA49888 for ; Sun, 11 Oct 1998 20:22:32 -0700 Received: from europe.std.com (europe.std.com [199.172.62.20]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA23183 for ; Sun, 11 Oct 1998 20:22:31 -0700 Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id WAA27746; Sun, 11 Oct 1998 22:47:18 -0400 (EDT) Received: from localhost by world.std.com (TheWorld/Spike-2.0) id AA29829; Sun, 11 Oct 1998 22:47:10 -0400 Message-Id: Date: Sun, 11 Oct 1998 22:47:10 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: NASCA Telnet and anzio In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN if i follow... you need to print pine mail on a pc? should we assume pine is running on a unix host somewhere? i use anzio [ www.anzio.com ] and LOVE it. it allows for pass through printing as well as up and down load. 99% functional demo available; real copy is only $25 On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > I'm going to need to download this program > so I can print from Pine Mail under > Windows 95. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 06:09:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id GAA31250 for ; Mon, 12 Oct 1998 06:09:44 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA23692; Mon, 12 Oct 1998 06:09:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA25979; Mon, 12 Oct 1998 06:08:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA14950 for ; Mon, 12 Oct 1998 01:25:04 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA06558 for ; Mon, 12 Oct 1998 01:25:03 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id KAA24023 for ; Mon, 12 Oct 1998 10:24:57 +0200 (CEST) Message-Id: Date: Mon, 12 Oct 1998 10:23:47 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Remote Address Books (was Re: Apples and Oranges) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 9 Oct 1998, Chris Wood wrote: > On Fri, 9 Oct 1998, Jan Kalin wrote: > > > > > So you cannot direcly access a Unix local address book. What you can do is > > install an IMAP server on the Unix box (if it isn't already running), move > > Unix local address books to 'remote' address books actually residing on > > the Unix machine and have PCPine access the same remote address books. > > Is this assuming that the unix pine is accessing things via IMAP just as > pc-pine is? or... is this assuming unix pine is accessing things locally > and pc-pine is accessing things via IMAP? Both Pines have to access address books via IMAP. That's because the local and remote address books have different formats. So you cannot access the same information both locally and via IMAP. It might help you to think of mail folders (after all, Pine's remote address books are just that: special-format folders). You can access local folders locally and remote folders from wherever in the Internet you are. To see the same folder (or address book) you *have* to make it remote, even though it might physically reside on the same machine as one of the Pines you're using. Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 07:08:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA31603 for ; Mon, 12 Oct 1998 07:08:53 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA07554; Mon, 12 Oct 1998 07:08:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA28489; Mon, 12 Oct 1998 07:07:22 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA31042 for ; Mon, 12 Oct 1998 07:04:39 -0700 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA20062 for ; Mon, 12 Oct 1998 07:04:38 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRNGHR>; Mon, 12 Oct 1998 10:08:44 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394F3A@POISON> Date: Mon, 12 Oct 1998 10:08:44 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: Re: Local vs Remote addressbooks (Was: Apples and Oranges) MIME-Version: 1.0 Content-Type: text/plain X-To: "'elad@cs.bgu.ac.il'" X-Cc: "'Pine List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I wonder..... Is it possible to have two imapd programs, one which requires authentication and one that does not. use tcdp to decide if it's from the local machine then run the imapd that requires no authentication, other wise run the imapd that does require it. This way a local user wouldn't need to enter a password? Is the password prompt controlled by imapd or does pine always ask for it? George Gallen ggallen@slackinc.com On Fri, 9 Oct 1998, Elad Eyal wrote: > Good morning, > > > ======================================================================== > > Please note: Remote address books stored on an IMAP server are of an > > entirely different format (namely, a special-purpose "mail folder") than > > that of the local addressbook familiar to Pine users. Therefore, you > > cannot use "add a remote address book"to make an existing Pine > > .addressbook file you may have on a remote IMAP server accessible to Pine > > running on a different host. > > ======================================================================== > > Alas, you can't, can you. Which means - if you're anything like me - you'd > have to key in your password, /even though/ the addressbook is a local > file. I wonder if there's a collosally good reason why Pine can't read and > write a remote addressbook locally. > > > _ > (_ / _ / ( E-mail pigeons nest in binary trees ) > (__/__(/\_(/ http://www.cs.bgu.ac.il/~elad > > > > > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 07:29:51 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA31981 for ; Mon, 12 Oct 1998 07:29:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA07896; Mon, 12 Oct 1998 07:29:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA28944; Mon, 12 Oct 1998 07:28:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA53910 for ; Mon, 12 Oct 1998 07:25:36 -0700 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA22811 for ; Mon, 12 Oct 1998 07:25:35 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRNGJX>; Mon, 12 Oct 1998 10:29:41 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394F3E@POISON> Date: Mon, 12 Oct 1998 10:29:41 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: Local vs Remote addressbooks (Was: Apples and Oranges) MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN After sending this, I realized that tcpd might not work since there is only one option for running (once successfully through the wrapper), if you placed the imapd in the rejection area (/etc/hosts.deny or /etc/hosts.allow) then it probably wouldn't run correctly? I realize this part is off topic, but can tcpd (wrappers) be setup to run either of two options depending on success/failure? George -----Original Message----- From: George Gallen [mailto:ggallen@slackinc.com] Sent: Monday, October 12, 1998 10:09 AM To: Pine Discussion Forum Subject: Re: Local vs Remote addressbooks (Was: Apples and Oranges) I wonder..... Is it possible to have two imapd programs, one which requires authentication and one that does not. use tcdp to decide if it's from the local machine then run the imapd that requires no authentication, other wise run the imapd that does require it. This way a local user wouldn't need to enter a password? Is the password prompt controlled by imapd or does pine always ask for it? George Gallen ggallen@slackinc.com On Fri, 9 Oct 1998, Elad Eyal wrote: > Good morning, > > > ======================================================================== > > Please note: Remote address books stored on an IMAP server are of an > > entirely different format (namely, a special-purpose "mail folder") than > > that of the local addressbook familiar to Pine users. Therefore, you > > cannot use "add a remote address book"to make an existing Pine > > .addressbook file you may have on a remote IMAP server accessible to Pine > > running on a different host. > > ======================================================================== > > Alas, you can't, can you. Which means - if you're anything like me - you'd > have to key in your password, /even though/ the addressbook is a local > file. I wonder if there's a collosally good reason why Pine can't read and > write a remote addressbook locally. > > > _ > (_ / _ / ( E-mail pigeons nest in binary trees ) > (__/__(/\_(/ http://www.cs.bgu.ac.il/~elad > > > > > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 07:36:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA22838 for ; Mon, 12 Oct 1998 07:36:55 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25113; Mon, 12 Oct 1998 07:36:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA29314; Mon, 12 Oct 1998 07:35:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA58878 for ; Mon, 12 Oct 1998 07:33:17 -0700 Received: from goodnet.com (goodnet.com [207.98.129.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA22049 for ; Mon, 12 Oct 1998 07:33:16 -0700 Received: from localhost by goodnet.com with ESMTP id HAA26423; Mon, 12 Oct 1998 07:36:09 -0700 (MST) Message-Id: Date: Mon, 12 Oct 1998 07:36:07 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Kathleen P. Daily-Herrman" To: Pine Discussion Forum Subject: Re: NASCA Telnet and anzio In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff A Kinsey X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN yes..exactly...someone had mentioned NASCA telnet some time ago and I could'nt find it on tucows site.. I'll try it and some of the other packages suggested.. thank you for your assistance everyone.. Kathleen On Sun, 11 Oct 1998, Jeff A Kinsey wrote: > if i follow... you need to print pine mail on a pc? > > should we assume pine is running on a unix host somewhere? > > i use anzio [ www.anzio.com ] and LOVE it. it allows for pass > through printing as well as up and down load. 99% functional demo > available; real copy is only $25 > > On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > > > I'm going to need to download this program > > so I can print from Pine Mail under > > Windows 95. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 07:40:49 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA29750 for ; Mon, 12 Oct 1998 07:40:48 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25201; Mon, 12 Oct 1998 07:40:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA29427; Mon, 12 Oct 1998 07:38:42 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA58764 for ; Mon, 12 Oct 1998 07:33:35 -0700 Received: from ntcorp.dn.net (ntcorp.dn.net [207.226.172.79]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA22071 for ; Mon, 12 Oct 1998 07:33:35 -0700 Received: from localhost (fidelman@localhost) by ntcorp.dn.net (8.8.7/8.8.7) with ESMTP id KAA15459; Mon, 12 Oct 1998 10:31:20 -0400 (EDT) Message-Id: Date: Mon, 12 Oct 1998 10:31:20 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Miles Fidelman To: Pine Discussion Forum Subject: bug in handling Unix From headers - any workarounds? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: mfidelman@civicnet.org X-Sender: fidelman@ntcorp.dn.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've just discovered that Pine 4.05 seems to have a bug in its handling of >From headers during export operations. Here's an example: >From ccn@shore.net Mon Oct 12 00:15:36 1998 Date: Fri, 4 Sep 1998 11:45:56 -0400 (EDT) From: CCN To: rciville@civicnet.org Cc: mfidelman@civicnet.org Subject: changes to secure server note that the Unix From line, inserted during export, show the date/time of export, NOT the date/time of the original messages. This makes running a collection of messages through an archive program very difficult. In my case, I'm trying to run about a 1000 messages through majoromo's archive2.pl archiver - and they're all showing up in this month's archive file. Any liklihood of a near-term fix, or any workarounds? Thanks much, Miles Fidelman mfidelman@civicnet.org ************************************************************************** The Center for Civic Networking PO Box 600618 Miles R. Fidelman, President & Newtonville, MA 02460-0006 Director of Civic Networking Systems 617-558-3698 fax: 617-630-8946 mfidelman@civicnet.org http://civic.net/ccn.html Information Infrastructure: Public Spaces for the 21st Century Let's Start With: Internet Wall-Plugs Everywhere Say It Often, Say It Loud: "I Want My Internet!" ************************************************************************** From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 07:59:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id HAA13282 for ; Mon, 12 Oct 1998 07:59:11 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25581; Mon, 12 Oct 1998 07:59:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA08724; Mon, 12 Oct 1998 07:57:50 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA35924 for ; Mon, 12 Oct 1998 07:55:10 -0700 Received: from xena.acsu.buffalo.edu (qmailr@xena.acsu.buffalo.edu [128.205.7.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id HAA28146 for ; Mon, 12 Oct 1998 07:55:10 -0700 Received: (qmail 14685 invoked by uid 24350); 12 Oct 1998 14:55:08 -0000 Message-Id: Date: Mon, 12 Oct 1998 10:55:08 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jack P Freer To: Pine Discussion Forum Subject: PC-Pine 4.05 Error messages MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine-Info X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I've downloaded PC-Pine 4.05 and when I first open it, I get: [Error creating "C:\PROGRAM FILES" : file exists] Then, if I try to reconfigure it (setup->configure), I get: [Config file not changeable, can't change options or settings] I have downloaded this on other Win95 machines and it has worked fine. Any ideas? ----------- Jack Freer University at Buffalo ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 08:35:44 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id IAA32748 for ; Mon, 12 Oct 1998 08:35:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA09418; Mon, 12 Oct 1998 08:35:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA02506; Mon, 12 Oct 1998 08:34:23 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA23104 for ; Mon, 12 Oct 1998 08:31:28 -0700 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA28763 for ; Mon, 12 Oct 1998 08:31:27 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRNGSK>; Mon, 12 Oct 1998 11:35:34 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394F43@POISON> Date: Mon, 12 Oct 1998 11:35:34 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: NASCA Telnet and anzio MIME-Version: 1.0 Content-Type: text/plain X-To: "'Kathleen P. Daily-Herrman'" , Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN What I did, was setup my W95 printer as a remote printer for the unix system. I used a lpd daemon program running on the PC. Then just printed to the remote printer from unix. This of course assumes that you get your printer setup as a remote printer. I have the luxury(?) of being the unix admin so getting approval was not an issue. George Gallen ggallen@slackinc.com -----Original Message----- From: Kathleen P. Daily-Herrman [mailto:kdh@goodnet.com] Sent: Monday, October 12, 1998 10:36 AM To: Pine Discussion Forum Subject: Re: NASCA Telnet and anzio yes..exactly...someone had mentioned NASCA telnet some time ago and I could'nt find it on tucows site.. I'll try it and some of the other packages suggested.. thank you for your assistance everyone.. Kathleen On Sun, 11 Oct 1998, Jeff A Kinsey wrote: > if i follow... you need to print pine mail on a pc? > > should we assume pine is running on a unix host somewhere? > > i use anzio [ www.anzio.com ] and LOVE it. it allows for pass > through printing as well as up and down load. 99% functional demo > available; real copy is only $25 > > On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > > > I'm going to need to download this program > > so I can print from Pine Mail under > > Windows 95. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 09:29:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA29756 for ; Mon, 12 Oct 1998 09:29:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA11170; Mon, 12 Oct 1998 09:28:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA05311; Mon, 12 Oct 1998 09:26:09 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA49806 for ; Mon, 12 Oct 1998 09:24:04 -0700 Received: from nimbus.anzio.com (bezell@nimbus.anzio.com [204.201.253.34]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02380 for ; Mon, 12 Oct 1998 09:24:04 -0700 Received: from localhost (bezell@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id JAA01690; Mon, 12 Oct 1998 09:23:02 -0700 Message-Id: Date: Mon, 12 Oct 1998 09:23:02 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bobby Ezell To: Pine Discussion Forum Subject: RE: NASCA Telnet and anzio In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055394F43@POISON> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: George Gallen X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN One of the nice features built in to Pine for UNIX is its ability to support passthrough (or transparent) printing through the terminal session. Many emulation products support this nicely, such as for the vt and wyse terminal types (I tend to think our Anzio products do it the best). The nice thing with this is that the printing then becomes a "follow-me" type printing (if I want to print through Pine from the office, it prints to my local printer, if I want to print at home, it works there also). Within Pine UNIX its automatic, just go to Setup:Printer and select attached-to-ansi Bobby Ezell Rasmussen Software, Inc. On Mon, 12 Oct 1998, George Gallen wrote: > What I did, was setup my W95 printer as a remote printer > for the unix system. I used a lpd daemon program running on > the PC. Then just printed to the remote printer from unix. > > This of course assumes that you get your printer setup as > a remote printer. I have the luxury(?) of being the unix > admin so getting approval was not an issue. > > George Gallen > ggallen@slackinc.com > > -----Original Message----- > From: Kathleen P. Daily-Herrman [mailto:kdh@goodnet.com] > Sent: Monday, October 12, 1998 10:36 AM > To: Pine Discussion Forum > Subject: Re: NASCA Telnet and anzio > > > > > yes..exactly...someone had mentioned NASCA > telnet some time ago and I could'nt find > it on tucows site.. > > I'll try it and some of the other packages > suggested.. > > thank you for your assistance everyone.. > > Kathleen > > > On Sun, 11 Oct 1998, Jeff A Kinsey wrote: > > > if i follow... you need to print pine mail on a pc? > > > > should we assume pine is running on a unix host somewhere? > > > > i use anzio [ www.anzio.com ] and LOVE it. it allows for pass > > through printing as well as up and down load. 99% functional demo > > available; real copy is only $25 > > > > On Sun, 11 Oct 1998, Kathleen P. Daily-Herrman wrote: > > > > > I'm going to need to download this program > > > so I can print from Pine Mail under > > > Windows 95. > > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 09:41:27 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id JAA02352 for ; Mon, 12 Oct 1998 09:41:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA11635; Mon, 12 Oct 1998 09:41:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA14754; Mon, 12 Oct 1998 09:37:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA25984 for ; Mon, 12 Oct 1998 09:34:09 -0700 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA03713 for ; Mon, 12 Oct 1998 09:34:06 -0700 Received: from spike by webster (SMI-8.6/SMI-SVR4) id MAA00896; Mon, 12 Oct 1998 12:37:12 -0400 Message-Id: Date: Mon, 12 Oct 1998 12:35:56 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: Re: Telnet EMUs and printing In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bobby Ezell X-Cc: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 Oct 1998, Bobby Ezell wrote: >One of the nice features built in to Pine for UNIX is its ability to >support passthrough (or transparent) printing through the terminal >session. Many emulation products support this nicely, such as for the vt >and wyse terminal types (I tend to think our Anzio products do it the >best). The nice thing with this is that the printing then becomes a >"follow-me" type printing (if I want to print through Pine from the >office, it prints to my local printer, if I want to print at home, it >works there also). > >Within Pine UNIX its automatic, just go to Setup:Printer and select > attached-to-ansi > >Bobby Ezell >Rasmussen Software, Inc. I've found EWAN is very good at supporting the "attached-to-ansi" feature. The latest version should be available 24 hrs a day, 7 days a week from: http://www.lysator.liu.se/~zander/ewan.html If you like WWW ftp.lysator.liu.se /pub/msdos/windows If you prefer FTP Shawn Jeffries ujefsh81@vetri.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 10:58:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id KAA03754 for ; Mon, 12 Oct 1998 10:58:21 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA01184; Mon, 12 Oct 1998 10:58:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA21451; Mon, 12 Oct 1998 10:56:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA50742 for ; Mon, 12 Oct 1998 10:53:25 -0700 Received: from smtp.yourwebhost.com (smtp.yourwebhost.com [209.239.47.254]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA15858 for ; Mon, 12 Oct 1998 10:53:24 -0700 Received: from anna.yourwebhost.com (anna.yourwebhost.com [209.239.44.1] (may be forged)) by smtp.yourwebhost.com (8.8.7/8.8.4) with ESMTP id BAA16136 for ; Tue, 13 Oct 1998 01:53:43 -0400 Received: from anna.yourwebhost.com (mousaler.com [209.239.44.160]) by anna.yourwebhost.com (8.8.7/8.8.4) with SMTP id OAA17389 for ; Mon, 12 Oct 1998 14:54:00 -0400 Message-Id: Date: Mon, 12 Oct 1998 13:54:00 -0500 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "webmaster@mousaler.com" To: Pine Discussion Forum Subject: Changing the username to preferred name MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: armenia@anna.yourwebhost.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am trying to change my default username in Pine, similar to the way you can change "YOU EMAIL" in Netscape or any other windows mail software. Is it possible to do it in Unix Pine?? I was able to change the default full name, but not the username, which shows as the sender's email when I send email. Please help ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 11:17:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id LAA30275 for ; Mon, 12 Oct 1998 11:17:46 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA01778; Mon, 12 Oct 1998 11:17:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA15076; Mon, 12 Oct 1998 11:15:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA51414 for ; Mon, 12 Oct 1998 11:12:37 -0700 Received: from mailhost2.cac.washington.edu (mailhost2.cac.washington.edu [140.142.33.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA18043 for ; Mon, 12 Oct 1998 11:12:37 -0700 Received: from D-128-95-135-197.dhcp.washington.edu (D-128-95-135-197.dhcp.washington.edu [128.95.135.197]) by mailhost2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA19146; Mon, 12 Oct 1998 11:12:28 -0700 Message-Id: Date: Mon, 12 Oct 1998 11:14:01 -0700 (PDT) Reply-To: kanelson@cac.washington.edu Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kris Nelson To: Pine Discussion Forum Subject: Re: Changing the username to preferred name In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "webmaster@mousaler.com" X-Cc: Pine Discussion Forum X-X-Sender: kanelson@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 Oct 1998, webmaster@mousaler.com wrote: > > I am trying to change my default username in Pine, similar to the way you > can change "YOU EMAIL" in Netscape or any other windows mail software. Is > it possible to do it in Unix Pine?? > > I was able to change the default full name, but not the username, which > shows as the sender's email when I send email. Please see FAQ #4.10 at: http://www.washington.edu/pine/faq Regards, Kris -- Kristopher Nelson -- kanelson@cac.washington.edu University of Washington -- Computing & Communications From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 12:23:29 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05147 for ; Mon, 12 Oct 1998 12:23:28 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA17303; Mon, 12 Oct 1998 12:23:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA27565; Mon, 12 Oct 1998 12:21:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA34064 for ; Mon, 12 Oct 1998 12:18:41 -0700 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA32239 for ; Mon, 12 Oct 1998 12:18:38 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id EAA15014; Tue, 13 Oct 1998 04:11:32 +0930 Message-Id: Date: Tue, 13 Oct 1998 04:11:31 +0930 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: RE: NASCA Telnet and anzio In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055394F43@POISON> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: George Gallen X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 Oct 1998, George Gallen wrote: > What I did, was setup my W95 printer as a remote printer > for the unix system. I used a lpd daemon program running on > the PC. Then just printed to the remote printer from unix. Interesting. Does W95 come with a lpd daemon? If the original problem was a need for a Unix computer to use a printer attached to a W95 PC, I would suggest Samba (I think, ftp://samba.anu.edu.au). But that does need to be set up by the administrator of the Unix system. Both of these approaches would allow other users of the Unix system to print on the printer - in general, a good thing: why waste a resource? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 12:34:14 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05635 for ; Mon, 12 Oct 1998 12:34:14 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA17693; Mon, 12 Oct 1998 12:34:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA28279; Mon, 12 Oct 1998 12:30:20 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA36884 for ; Mon, 12 Oct 1998 12:27:31 -0700 Received: from news.mtu.edu (root@news.mtu.edu [141.219.70.11]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA29358 for ; Mon, 12 Oct 1998 12:27:29 -0700 Received: from mtu.edu (root@mtu.edu [141.219.70.1]) by news.mtu.edu (8.8.8/8.8.8) with ESMTP id PAA09332; Mon, 12 Oct 1998 15:27:17 -0400 (EDT) Received: from sosue.me.mtu.edu (sosue.me.mtu.edu [141.219.26.133]) by mtu.edu (8.8.8/8.8.8) with ESMTP id PAA25865; Mon, 12 Oct 1998 15:27:16 -0400 (EDT) Received: from doeray.me.mtu.edu (doeray.me.mtu.edu [141.219.26.131]) by sosue.me.mtu.edu (8.8.8/8.8.8/mturelay-1.2) with ESMTP id PAA09476; Mon, 12 Oct 1998 15:27:16 -0400 (EDT) Message-Id: Date: Mon, 12 Oct 1998 15:27:15 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Edan Idzerda To: Pine Discussion Forum Subject: RE: NASCA Telnet and anzio In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Talbot-Wilson X-Cc: Pine Discussion Forum X-Sender: edan@doeray.me.mtu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 13 Oct 1998, Michael Talbot-Wilson wrote: > Interesting. Does W95 come with a lpd daemon? Hell no! > If the original problem was a need for a Unix computer to use a > printer attached to a W95 PC, I would suggest Samba (I think, > ftp://samba.anu.edu.au). But that does need to be set up by the > administrator of the Unix system. Save the Samba maintainers internet fees and go to http://samba.anu.edu.au/samba and pick your closest mirror. You don't need root access to get Samba, compile it, and use the bundled "smbclient" to print to a Windows 95 printer. There is plenty of documentation--I'd explain it, but with my job right now you would *definitely* have to send me pizza if I did. - edan From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 12:36:55 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id MAA05761 for ; Mon, 12 Oct 1998 12:36:54 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA04196; Mon, 12 Oct 1998 12:36:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA20602; Mon, 12 Oct 1998 12:34:23 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA13096 for ; Mon, 12 Oct 1998 12:31:36 -0700 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA29961 for ; Mon, 12 Oct 1998 12:31:34 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id EAA15066; Tue, 13 Oct 1998 04:24:23 +0930 Message-Id: Date: Tue, 13 Oct 1998 04:24:23 +0930 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: RE: NASCA Telnet and anzio In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bobby Ezell X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 12 Oct 1998, Bobby Ezell wrote: > > One of the nice features built in to Pine for UNIX is its ability to > support passthrough (or transparent) printing through the terminal > session. Many emulation products support this nicely, such as for the vt Ah! NOW I understand... From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) for mailarch+pine-info; Mon, 12 Oct 1998 17:15:02 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.09) with ESMTP id RAA13021 for ; Mon, 12 Oct 1998 17:15:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA12884; Mon, 12 Oct 1998 17:14:55 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA15255; Mon, 12 Oct 1998 17:13:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA13190 for ; Mon, 12 Oct 1998 17:11:08 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA10423 for ; Mon, 12 Oct 1998 17:11:07 -0700 Received: from [132.198.236.112] (132.198.236.112) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.718E24A0@smtpgate.uvm.edu>; Mon, 12 Oct 1998 20:11:06 -0400 Message-Id: Date: Mon, 12 Oct 1998 20:11:00 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: PC-Pine 4.05 Error messages In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i am guessing you have pine installed in c:\program files directory? have you tried using c:\pine? i wouldn't know why it would work in program files on some computers and some not. Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 mailer http://www.washington.edu/pine On Mon, 12 Oct 1998, Jack P Freer wrote: > I've downloaded PC-Pine 4.05 and when I first open it, I get: > [Error creating "C:\PROGRAM FILES" : file exists] > > Then, if I try to reconfigure it (setup->configure), I get: > [Config file not changeable, can't change options or settings] > > I have downloaded this on other Win95 machines and it has worked > fine. Any ideas? > > ----------- > Jack Freer > > University at Buffalo > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 14 Oct 1998 07:39:00 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA20399 for ; Wed, 14 Oct 1998 07:38:59 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA27351; Wed, 14 Oct 1998 07:38:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA23832; Wed, 14 Oct 1998 07:36:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA38556 for ; Wed, 14 Oct 1998 07:33:18 -0700 Received: from neon.transmeta.com (neon-best.transmeta.com [206.184.214.10]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA28980 for ; Wed, 14 Oct 1998 07:33:18 -0700 Received: from deepthought.transmeta.com (mailhost.transmeta.com [10.1.1.15]) by neon.transmeta.com (8.9.1/8.9.1) with ESMTP id HAA31415 for ; Wed, 14 Oct 1998 07:30:07 -0700 Received: from marvin.transmeta.com (root@marvin.transmeta.com [10.1.27.210]) by deepthought.transmeta.com (8.8.8+spamcan/8.8.5) with ESMTP id HAA20300 for ; Wed, 14 Oct 1998 07:33:15 -0700 (PDT) Received: from localhost (localhost.transmeta.com [127.0.0.1]) by marvin.transmeta.com (8.8.5/8.7.3) with ESMTP id HAA14790 for ; Wed, 14 Oct 1998 07:33:15 -0700 Message-Id: Date: Wed, 14 Oct 1998 07:33:14 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jauder Ho To: Pine Discussion Forum Subject: Content-Transfer-Encoding: Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-BOFH-Subliminal-Message: Use vi not Emacs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN apparently when I send mail it does set the content-type but the Content-Transfer-Encoding: is not set for outbound mail which I guess should default to 7bit. this is with 4.05 --Jauder ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 14 Oct 1998 07:59:11 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA20337 for ; Wed, 14 Oct 1998 07:59:10 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA13333; Wed, 14 Oct 1998 07:59:04 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA26581; Wed, 14 Oct 1998 07:57:43 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA52316 for ; Wed, 14 Oct 1998 07:55:56 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA10559 for ; Wed, 14 Oct 1998 07:55:53 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Wed, 14 Oct 1998 22:55:44 +0800 Message-Id: <001701bdf782$a7bd4490$1511b381@edspc17.twntpe.cdc.com> Date: Wed, 14 Oct 1998 22:55:16 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Content-Transfer-Encoding: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Jauder Ho" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > apparently when I send mail it does set the content-type but the > Content-Transfer-Encoding: is not set for outbound mail which I guess > should default to 7bit. this is with 4.05 If you read the MIME RFCs you'd find that the absence of a C-T-E header implies 7bit. Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 00:13:52 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA03509 for ; Thu, 15 Oct 1998 00:13:49 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA08772; Thu, 15 Oct 1998 00:13:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA22119; Thu, 15 Oct 1998 00:12:56 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA20044 for ; Thu, 15 Oct 1998 00:10:41 -0700 Received: from lcjdap.soroscj.ro (lcjdap.soroscj.ro [193.226.84.253]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id AAA23108 for ; Thu, 15 Oct 1998 00:10:37 -0700 Received: (qmail 10135 invoked by uid 723); 15 Oct 1998 07:11:16 -0000 Message-Id: Date: Thu, 15 Oct 1998 10:11:16 +0300 (EEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: PINE list To: Pine Discussion Forum Subject: Pine 4.05 - deleting attachements MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I want to keep some e-mails that also contain big attachements, why can't, how can delete I if it can be done the attachements in pine 4.05? I can mark attachements with "D" but I can't actually expunge them. Roby ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 05:07:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA10607 for ; Thu, 15 Oct 1998 05:07:05 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA25492; Thu, 15 Oct 1998 05:06:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA13308; Thu, 15 Oct 1998 05:06:11 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA52478 for ; Thu, 15 Oct 1998 05:04:05 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA11133 for ; Thu, 15 Oct 1998 05:04:05 -0700 Received: from Chicago.ess.harris.com (chicago.ess.harris.com [130.41.63.112]) by ess.harris.com (8.8.6/8.8.6) with ESMTP id IAA17682; Thu, 15 Oct 1998 08:03:41 -0400 (EDT) Received: from Maxville.ESS.Harris.com by Chicago.ess.harris.com (8.8.8+Sun/SMI-SVR4) id IAA14847; Thu, 15 Oct 1998 08:03:33 -0400 (EDT) Received: from localhost by Maxville.ESS.Harris.com (SMI-8.6/SMI-SVR4) id IAA24620; Thu, 15 Oct 1998 08:03:30 -0400 Message-Id: Date: Thu, 15 Oct 1998 08:03:30 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Paul Halsema To: Pine Discussion Forum Subject: Re: Pine 4.05 - deleting attachements In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: phalsema@Maxville.ess.harris.com X-To: PINE list X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 15 Oct 1998, Roby wrote: > I want to keep some e-mails that also contain big attachements, > why can't, how can delete I if it can be done the attachements in pine 4.05? > I can mark attachements with "D" but I can't actually expunge them. Go back to the article window and save the article back to the same folder and then delete the original article. ---Paul From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 07:37:01 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA11577 for ; Thu, 15 Oct 1998 07:36:59 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA14708; Thu, 15 Oct 1998 07:36:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA19971; Thu, 15 Oct 1998 07:35:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA52054 for ; Thu, 15 Oct 1998 07:33:08 -0700 Received: from bcx01.co.boulder.co.us (swcxt@bcx01.co.boulder.co.us [161.98.128.4]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA05484 for ; Thu, 15 Oct 1998 07:33:08 -0700 Received: from localhost (swcxt@localhost) by bcx01.co.boulder.co.us (8.9.1a/8.9.1) with ESMTP id IAA197926 for ; Thu, 15 Oct 1998 08:33:06 -0600 Message-Id: Date: Thu, 15 Oct 1998 08:33:06 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shane Castle To: Pine Discussion Forum Subject: buglet in and fix for pico/display.c MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Problem: If the user's screen is odd-sized, such as 90 cols wide, the display initially shown by pico is displayed improperly. An implicit assumption was made in the code about the screen size that causes it to display the options across the bottom correctly only if the width is not evenly divisible by 6. If it is then an extra character occurs at the bottom right that screws up the subsequent painting of the characters at the top. Solution: Subtract one from the screen width before dividing by six; that way the extra character, if generated, will never be a problem. Patch: --- display.c.dist Fri Jun 19 11:19:53 1998 +++ display.c Wed Oct 14 12:59:36 1998 @@ -2350,7 +2350,7 @@ else nspace[index] = (index < 4) ? 3 : 4; - tspace = term.t_ncol/6; /* total space for each item */ + tspace = (term.t_ncol-1)/6; /* total space for each item */ index = 0; for(row = 0; row <= 1; row++){ linebuf[0] = '\0'; A final note: This buglet has been in every version of Pine I have ever seen. I've tried to get this fix in the code before but never succeeded. Maybe this time someone will put it in? Shane Castle | "Perfection, then, is finally achieved, not Boulder County Info Svcs | when there is nothing left to add, but when Boulder CO USA | there is nothing left to take away." | - Antoine de Saint-Exupery ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 09:39:10 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA08854 for ; Thu, 15 Oct 1998 09:39:09 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01078; Thu, 15 Oct 1998 09:39:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA06018; Thu, 15 Oct 1998 09:32:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA50514 for ; Thu, 15 Oct 1998 09:29:22 -0700 Received: from server.contad.unam.mx (server.contad.unam.mx [132.248.18.20]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA03183 for ; Thu, 15 Oct 1998 09:29:05 -0700 Received: from localhost by server.contad.unam.mx with SMTP (1.38.193.4/16.2) id AA17758; Thu, 15 Oct 1998 11:25:22 -0500 Message-Id: Date: Thu, 15 Oct 1998 11:25:21 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jorge Juarez Xospa To: Pine Discussion Forum Subject: Re: Pine 4.05 - deleting attachements In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: PINE list X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi Roby! The efect to expunge the attachments will be when yuo save in another folder, it could be the INBOX too. George On Thu, 15 Oct 1998, PINE list wrote: > > I want to keep some e-mails that also contain big attachements, > why can't, how can delete I if it can be done the attachements in pine 4.05? > I can mark attachements with "D" but I can't actually expunge them. > > Roby > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 14:38:44 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA21857 for ; Thu, 15 Oct 1998 14:38:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10459; Thu, 15 Oct 1998 14:38:34 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA10269; Thu, 15 Oct 1998 14:36:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA27174 for ; Thu, 15 Oct 1998 14:34:32 -0700 Received: from usc.edu (usc.edu [128.125.253.136]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA07249 for ; Thu, 15 Oct 1998 14:34:30 -0700 Received: from Law.USC.EDU (law.usc.edu [128.125.42.6]) by usc.edu (8.8.8/8.8.8/usc) with SMTP id OAA23276 for ; Thu, 15 Oct 1998 14:34:29 -0700 (PDT) Received: from faculty.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA06460; Thu, 15 Oct 1998 14:39:10 PDT Received: from l2122.usc.edu by faculty.Law.USC.EDU (4.1/SMI-4.1) id AA10064; Thu, 15 Oct 1998 14:41:47 PDT Message-Id: Date: Thu, 15 Oct 1998 14:32:38 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Robert Larmon To: Pine Discussion Forum Subject: importing/exporting messages to/from pine and Novell Groupwise Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: rlarmon@faculty-law.usc.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I'd be interested in anyone's experiences in importing/exporting messages to/from Pine and Groupwise (especially 5.5). I'm relatively new to file formats, so any helpful tips, URL's, faqs, utilities, etc. would be great. Thanks. Robert ``````````````````````````````````````````````````````````````````````` ` Robert Larmon ` ` PC Systems Analyst ` ` USC Law School Computing Services ` ` rlarmon@law.usc.edu ` ''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 20:38:55 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA13166 for ; Thu, 15 Oct 1998 20:38:53 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA07068; Thu, 15 Oct 1998 20:38:45 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA07971; Thu, 15 Oct 1998 20:37:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA20160 for ; Thu, 15 Oct 1998 20:35:42 -0700 Received: from cidc-cn.com.cn ([202.96.47.18]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA29619 for ; Thu, 15 Oct 1998 20:35:39 -0700 Received: from mailsvr.cidc (mailsvr.cidc [192.9.100.24]) by cidc-cn.com.cn (8.8.7/8.8.7) with ESMTP id LAA04619 for ; Fri, 16 Oct 1998 11:36:41 +0800 Received: from mail2 (mail2 [192.9.100.28]) by mailsvr.cidc (AIX4.2/UCB 8.7/8.7) with ESMTP id LAA15458 for ; Fri, 16 Oct 1998 11:35:38 -0500 (CDT) Received: (from weiym@localhost) by mail2 (8.7.1/8.7.1) id LAA01835 for pine-info@u.washington.edu; Fri, 16 Oct 1998 11:35:17 +0800 (EAT) Message-Id: <199810160335.LAA01835@mail2> Date: Fri, 16 Oct 1998 11:35:16 EAT Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Wei Yongming To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN To access message on a POP3 server, I defined a folder like this: {the hostname of pop3 server/pop3}my inbox name but I get a message "invalid remote specification", what should I do? This is Unix pine 3.90. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 22:30:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA17491 for ; Thu, 15 Oct 1998 22:30:15 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA19862; Thu, 15 Oct 1998 22:30:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA26181; Thu, 15 Oct 1998 22:29:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA35626 for ; Thu, 15 Oct 1998 22:27:24 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id WAA05520 for ; Thu, 15 Oct 1998 22:27:23 -0700 Received: from CROTH (132.198.237.130) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.1F23B240@smtpgate.uvm.edu>; Fri, 16 Oct 1998 1:27:21 -0400 Message-Id: Date: Fri, 16 Oct 1998 01:17:26 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: your mail In-Reply-To: <199810160335.LAA01835@mail2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN my answer to this question is a question. and that is, what version did pop support comeout in pine aaron On Fri, 16 Oct 1998, Wei Yongming wrote: > Date: Fri, 16 Oct 1998 11:35:16 EAT > From: Wei Yongming > To: Pine Discussion Forum > > To access message on a POP3 server, I defined a folder like this: > {the hostname of pop3 server/pop3}my inbox name > but I get a message "invalid remote specification", what should I do? > This is Unix pine 3.90. > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 15 Oct 1998 23:58:13 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA29003 for ; Thu, 15 Oct 1998 23:58:09 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA09645; Thu, 15 Oct 1998 23:57:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA01443; Thu, 15 Oct 1998 23:57:03 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA12092 for ; Thu, 15 Oct 1998 23:55:06 -0700 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA11216 for ; Thu, 15 Oct 1998 23:55:03 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id PAA09063 for ; Fri, 16 Oct 1998 15:48:06 +0930 Message-Id: Date: Fri, 16 Oct 1998 15:48:06 +0930 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: your mail (again) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have too often, recently, received mail with the subject "Re: your mail" which turns out to have nothing to do with any mail I ever sent. It seems to be a fault of Pine, specifically, that it automatically adds this subject to replies to cretins who send mail with no subject. It might seem a good idea, when the reply goes to the said idiot and no-one else, but it's a very bad approach in general, because the reply might go to the many subscribers of a mailing list, for only one of whom is the heading truthful. The others, if they saw a subject such as "Re:" or "Re: NO SUBJECT" would know it was a response to mail they didn't read before because it had no subject, and they would be able to make the same choice concerning the response. If the next version of Pine exhibits this broken behavior, I hope at least that it will be configurable in Setup, and off by default. I had a quick look but could find no way to touch this - it seems hard-wired. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 05:35:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA26609 for ; Fri, 16 Oct 1998 05:35:33 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA25122; Fri, 16 Oct 1998 05:35:20 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA16076; Fri, 16 Oct 1998 05:34:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA51996 for ; Fri, 16 Oct 1998 05:32:01 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA12546 for ; Fri, 16 Oct 1998 05:31:59 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 16 Oct 1998 20:31:50 +0800 Message-Id: <000501bdf900$de8e0ed0$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 16 Oct 1998 20:31:16 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: your mail (again) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Michael Talbot-Wilson" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Mike, To me, this seems like a rather small "style" issue. > I have too often, recently, received mail with the subject "Re: your > mail" which turns out to have nothing to do with any mail I ever > sent. I get some of these too. However, it seems (for me at least) easy to determine if the message has anything to do with something I wrote. If I am not explicitly addressed in the To: field it is probably not in response to "my" mail. This is especially true when I also don't personally know the sender. > It seems to be a fault of Pine, specifically, that it automatically > adds this subject to replies to cretins who send mail with no > subject. Pine has had this behavior for as long as I can recall. > It might seem a good idea, when the reply goes to the said idiot and > no-one else, but it's a very bad approach in general, because the > reply might go to the many subscribers of a mailing list, for only > one of whom is the heading truthful. Should user agents which put at in the message text at the beginning of a reply words like: "On June 17, 1998 You said: " also be taken to task? I've seen those too. (I've also been quick to determine if "I" did, in fact, say what comes after that statement.... :-) :-) ) > The others, if they saw a subject such as "Re:" or "Re: NO SUBJECT" > would know it was a response to mail they didn't read before because > it had no subject, and they would be able to make the same choice > concerning the response. > > If the next version of Pine exhibits this broken behavior, I hope at > least that it will be configurable in Setup, and off by default. I > had a quick look but could find no way to touch this - it seems > hard-wired. Sorry, I think the term "broken" is a bit harsh. Broken implies that a feature or function doesn't behave in the advertised manner or that a standard is violated such that it has a negative impact on other user agents. Knowing the developers of pine I am sure your suggestion is duly noted and will be placed into consideration. Regards, Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 06:23:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA03546 for ; Fri, 16 Oct 1998 06:23:48 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA14757; Fri, 16 Oct 1998 06:23:41 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA05506; Fri, 16 Oct 1998 06:22:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA12102 for ; Fri, 16 Oct 1998 06:20:29 -0700 Received: from dv.go.dlr.de (dv.go.dlr.de [129.247.91.3]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA15811 for ; Fri, 16 Oct 1998 06:20:24 -0700 Received: from Tschaikowsky.RZ.Go.DLR.De (tschaikowsky.rz.go.dlr.de [129.247.72.20]) by dv.go.dlr.de (8.9.1a/8.9.1) with ESMTP id PAA64844; Fri, 16 Oct 1998 15:18:43 +0200 Message-Id: Date: Fri, 16 Oct 1998 15:18:43 +0200 (CEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Andreas.Landhaeusser@dlr.de To: Pine Discussion Forum Subject: feature for pine 4.xx (was RE: your mail (again)) In-Reply-To: <000501bdf900$de8e0ed0$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Sender: rz5j@Tschaikowsky.RZ.Go.DLR.De X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 16 Oct 1998, Ed Greshko wrote: Hi all out there, if possible, pine should be configurable to NOT allowing to send a message without a subject. An even AI feature could be to check if the subject is a short desc of the composed mail, perhaps pine 99.0 . :-) But I think we should have to define an RFC to disallow Mail messages without a subject. But I don't think that this could be made mandantory for MUAs. > To me, this seems like a rather small "style" issue. And when user isn't allowed to send a message without a subject, one wouldn't get the RE: your mail subject. > I get some of these too. However, it seems (for me at least) easy to > determine if the message has anything to do with something I wrote. If I am > not explicitly addressed in the To: field it is probably not in response to > "my" mail. This is especially true when I also don't personally know the > sender. > > Pine has had this behavior for as long as I can recall. So please if one of the ppl in the pine development team could think at least of this as a configurable feature? > Knowing the developers of pine I am sure your suggestion is duly noted and > will be placed into consideration. Best regards Andreas -- Andreas R. Landhaeusser Deutsches Zentrum fuer Luft- und Raumfahrt e.V. (DLR) Bunsenstr. 10, D-37073 Goettingen, Germany, phone: +49 551 709 2379 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 06:25:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA04298 for ; Fri, 16 Oct 1998 06:25:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA14784; Fri, 16 Oct 1998 06:25:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA17781; Fri, 16 Oct 1998 06:24:23 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA41334 for ; Fri, 16 Oct 1998 06:21:05 -0700 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA15892 for ; Fri, 16 Oct 1998 06:21:02 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id WAA10789 for ; Fri, 16 Oct 1998 22:14:07 +0930 Message-Id: Date: Fri, 16 Oct 1998 22:14:06 +0930 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: RE: your mail (again) In-Reply-To: <000501bdf900$de8e0ed0$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 16 Oct 1998, Ed Greshko wrote: > I get some of these too. However, it seems (for me at least) easy to > determine if the message has anything to do with something I wrote. If I am > not explicitly addressed in the To: field it is probably not in response to > "my" mail. This is especially true when I also don't personally know the > sender. Ed, I don't understand. The mail is addressed to me. In the Pine index I see the sender's name, and the subject "Re: Your mail". I can't see the To: field until I select the mail item for reading and display the message. > Should user agents which put at in the message text at the beginning of a > reply words like: > > "On June 17, 1998 You said: " No. The point is that you can stay in the index and skip or delete mail that you don't have time to read. You don't see "You said" until you start to read it. But you are defeated if the subject is "Re: Your mail". You have to read it. At least until you can be sure that no-one can really have sent you mail with that subject and get your fancy delivery agent to black-hole all such mail - quite a bother. However, if the Pine mailing list was configured to flag in the subject all mail it forwarded, so that one saw "[pine] Re: Your mail" or something, then I would know the nature of the mail and would have no complaint. > Sorry, I think the term "broken" is a bit harsh. Broken implies that a > feature or function doesn't behave in the advertised manner or that a > standard is violated such that it has a negative impact on other user > agents. You are right, of course; "broken" was a mistake. So were "cretin" and "idiot". Regards, Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 07:11:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA04707 for ; Fri, 16 Oct 1998 07:11:53 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA15521; Fri, 16 Oct 1998 07:11:46 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA07550; Fri, 16 Oct 1998 07:10:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA41230 for ; Fri, 16 Oct 1998 07:08:29 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA07842 for ; Fri, 16 Oct 1998 07:08:27 -0700 Received: from fireball.control-risks.de (port254.koeln.ndh.net [195.94.92.254]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id QAA12258 for ; Fri, 16 Oct 1998 16:08:17 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id QAA01863; Fri, 16 Oct 1998 16:05:53 +0200 Message-Id: <19981016160551.A1809@fireball.control-risks.de> Date: Fri, 16 Oct 1998 16:05:51 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: your mail (again) In-Reply-To: ; from Michael Talbot-Wilson on Fri, Oct 16, 1998 at 10:14:06PM +0930 References: <000501bdf900$de8e0ed0$1511b381@edspc17.twntpe.cdc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Michael Talbot-Wilson (mtw@calypso.view.net.au): > On Fri, 16 Oct 1998, Ed Greshko wrote: > [confusing "re: your mail"] > Ed, I don't understand. The mail is addressed to me. In the Pine index I > see the sender's name, and the subject "Re: Your mail". I can't see the To: > field until I select the mail item for reading and display the message. Then go get the sources, patch what you don't like, recompile and stop whining. Now. > > Should user agents which put at in the message text at the beginning of a > > reply words like: > > > > "On June 17, 1998 You said: " > > No. The point is that you can stay in the index and skip or delete mail > that you don't have time to read. Yadda yadda yadda... > You don't see "You said" until you start to read it. That's because pine obviously sucks for you. Don't use it. Or write a patch. But please quit stating the obvious in a manner that makes me want to projectile-vomit, will you? TIA. > But you are defeated if the subject is "Re: Your mail". You have to read > it. At least until you can be sure that no-one can really have sent you > mail with that subject and get your fancy delivery agent to black-hole all > such mail - quite a bother. Honey, if you're not actually a lobotomized idiot, you're making a superb attempt at simulating one. Here's why: o you haven't read the documentation and what's in it re this particular "problem" o you're not using procmail or some other MDA (hint: mailing lists can easily be identified...) o you don't know that there are... errr... more powerful alternatives to pine that can easily do what you want > However, if the Pine mailing list was configured to flag in the subject all > mail it forwarded, so that one saw "[pine] Re: Your mail" or something, then > I would know the nature of the mail and would have no complaint. However, of pine allowed for shooting whining luuuusers, you'd be pretty dead by now. The "[crap]" thing is braindead. Period. So is your not using a mail filter. Maybe your whole sorry self is a mistake, dunno. Maybe it's just Friday... > > Sorry, I think the term "broken" is a bit harsh. Broken implies that a > > feature or function doesn't behave in the advertised manner or that a > > standard is violated such that it has a negative impact on other user > > agents. > > You are right, of course; "broken" was a mistake. So were "cretin" and > "idiot". They were not wrong, only addressing the wrong person. Mike. N'est-ce pas? Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 08:03:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA32488 for ; Fri, 16 Oct 1998 08:03:02 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA27268; Fri, 16 Oct 1998 08:02:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA21374; Fri, 16 Oct 1998 08:01:37 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA49718 for ; Fri, 16 Oct 1998 07:59:29 -0700 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA31383 for ; Fri, 16 Oct 1998 07:59:27 -0700 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id XAA11212 for ; Fri, 16 Oct 1998 23:52:32 +0930 Message-Id: Date: Fri, 16 Oct 1998 23:52:31 +0930 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: your mail (again) In-Reply-To: <19981016160551.A1809@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > o you're not using procmail or some other MDA (hint: mailing lists can As a matter of fact, I am. To follow on a bit from what I was saying before, it is extremely easy for some list management software to set a subject line prefix. E.g. majordomo has the 'subject_prefix' variable which can be set in the .config file. I understand that u.washington has its own list software, though, and it may not be quite so easy with that. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 08:20:32 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA05287 for ; Fri, 16 Oct 1998 08:20:31 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA16954; Fri, 16 Oct 1998 08:20:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA22007; Fri, 16 Oct 1998 08:19:06 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA49704 for ; Fri, 16 Oct 1998 08:17:11 -0700 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA06985 for ; Fri, 16 Oct 1998 08:17:09 -0700 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id LAA09603; Fri, 16 Oct 1998 11:16:50 -0400 (EDT) Message-Id: Date: Fri, 16 Oct 1998 11:16:49 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: your mail (again) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Talbot-Wilson X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 16 Oct 1998, Michael Talbot-Wilson wrote: > > o you're not using procmail or some other MDA (hint: mailing lists can > > As a matter of fact, I am. > > To follow on a bit from what I was saying before, it is extremely > easy for some list management software to set a subject line prefix. It also gets really ugly really fast imo. For the pine list you can filter on the X-To header.... ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 08:45:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA05370 for ; Fri, 16 Oct 1998 08:45:41 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA17642; Fri, 16 Oct 1998 08:45:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA14829; Fri, 16 Oct 1998 08:43:56 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA20216 for ; Fri, 16 Oct 1998 08:41:27 -0700 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA18050 for ; Fri, 16 Oct 1998 08:41:25 -0700 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id LAA09636 for ; Fri, 16 Oct 1998 11:41:20 -0400 (EDT) Message-Id: Date: Fri, 16 Oct 1998 11:41:20 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: your mail (again) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 16 Oct 1998, Darren Henderson wrote: > on the X-To header.... oops. or the X-Cc header depending on how it was sent apparently:) ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 10:36:08 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA07579 for ; Fri, 16 Oct 1998 10:36:07 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA21373; Fri, 16 Oct 1998 10:35:50 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA01735; Fri, 16 Oct 1998 10:33:49 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA35718 for ; Fri, 16 Oct 1998 10:31:11 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13138 for ; Fri, 16 Oct 1998 10:31:10 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id KAA05616; Fri, 16 Oct 1998 10:31:01 -0700 (PDT) Message-Id: Date: Fri, 16 Oct 1998 10:31:01 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: Procmailrc for Pine-info (was Re: your mail (again)) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Darren Henderson X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 16 Oct 1998, Darren Henderson wrote: > On Fri, 16 Oct 1998, Darren Henderson wrote: > > > on the X-To header.... > oops. or the X-Cc header depending on how it was sent apparently:) Here's the rule I use for filtering messages from pine-info into a pine-info mailbox. :0: * ^TO.*pine-info@u.washington.edu pine-info -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 12:50:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA01729 for ; Fri, 16 Oct 1998 12:50:49 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA25551; Fri, 16 Oct 1998 12:50:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA27339; Fri, 16 Oct 1998 12:48:36 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA16318 for ; Fri, 16 Oct 1998 12:46:38 -0700 Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA03943 for ; Fri, 16 Oct 1998 12:46:37 -0700 Received: from [212.228.155.84] (helo=A470.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.05demon1 #1) id 0zUFpb-0007VL-00 for pine-info@u.washington.edu; Fri, 16 Oct 1998 19:46:36 +0000 Received: (qmail 9524 invoked by uid 500); 16 Oct 1998 20:47:32 -0000 Message-Id: <19981016204731.A7238@A470.demon.co.uk> Date: Fri, 16 Oct 1998 20:47:31 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Wyn Rees To: Pine Discussion Forum Subject: macro to make toast Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-WWW: http://www.netlink.co.uk/cgi-merlin/lwgate X-PGP: finger merlin@netlink.co.uk for key X-PGP-Fingerprint: F8 79 5E 84 F0 20 A5 62 FA 2D E9 BD BE 06 7D 10 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm told Pine is REALLY well-specified... I need help. I usually download my mail very early in the morning. Toaster nearby. Is there a way to create some sort of macro in Pine so that I can press CNTL + T (for toast) to make the toast? Thnx (I'm hungry) -- Darren Rees merlin@netlink.co.uk 2000+ Berfau; fformat .zip .htm M$ Access CSV http://www.netlink.co.uk/users/merlin/berfau/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 16 Oct 1998 21:40:42 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA17470 for ; Fri, 16 Oct 1998 21:40:32 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA06892; Fri, 16 Oct 1998 21:40:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA14189; Fri, 16 Oct 1998 21:38:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA50234 for ; Fri, 16 Oct 1998 21:37:09 -0700 Received: from ashawna.eni.net (firewall-user@chastity.eni.net [206.135.49.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA18164 for ; Fri, 16 Oct 1998 21:37:08 -0700 Received: from localhost (drachen@localhost [127.0.0.1]) by ashawna.eni.net (8.8.7/8.8.7) with SMTP id VAA15654; Fri, 16 Oct 1998 21:32:18 -0700 Message-Id: Date: Fri, 16 Oct 1998 21:32:17 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Vinnie Chassot To: Pine Discussion Forum Subject: Re: macro to make toast In-Reply-To: <19981016204731.A7238@A470.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Darren Wyn Rees X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN well..lessee..alot of variables here, but if I assume you have a linux box, then you could write a little proggie to send appropriate signals out the parallel port to a little robotic arm that could then pick up a piece of bread, put it in the toaster, and push it down. in the editor ^T spelldchecks, so all you'd have to do is replace the spell check command with your proggie I think it'd work ;) Vinnie -- drachen@eni.net System Administrator Epoch Internet "It's more than just eye to eye learn the things I could never apply" -- Least Complicated On Fri, 16 Oct 1998, Darren Wyn Rees wrote: > Date: Fri, 16 Oct 1998 20:47:31 +0000 > From: Darren Wyn Rees > To: Pine Discussion Forum > Subject: macro to make toast > > I'm told Pine is REALLY well-specified... > > I need help. I usually download my mail very > early in the morning. Toaster nearby. > > Is there a way to create some sort of macro > in Pine so that I can press CNTL + T (for toast) > to make the toast? > > Thnx (I'm hungry) > -- > Darren Rees merlin@netlink.co.uk > > 2000+ Berfau; fformat .zip .htm M$ Access CSV > http://www.netlink.co.uk/users/merlin/berfau/ > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 17 Oct 1998 01:14:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA13971 for ; Sat, 17 Oct 1998 01:14:37 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA18981; Sat, 17 Oct 1998 01:14:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA29076; Sat, 17 Oct 1998 01:13:16 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA35996 for ; Sat, 17 Oct 1998 01:11:27 -0700 Received: from ariel.ucs.unimelb.EDU.AU (IDENT:joeh@ariel.ucs.unimelb.EDU.AU [128.250.20.3]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA00554 for ; Sat, 17 Oct 1998 01:11:24 -0700 Received: from localhost (joeh@localhost) by ariel.ucs.unimelb.EDU.AU (8.8.5/8.8.5) with SMTP id SAA02574; Sat, 17 Oct 1998 18:11:11 +1000 (AEST) Message-Id: Date: Sat, 17 Oct 1998 18:11:10 +1000 (AEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joe Haskian To: Pine Discussion Forum Subject: Re: macro to make toast In-Reply-To: <19981016204731.A7238@A470.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Darren Wyn Rees X-Cc: Pine Discussion Forum X-Sender: joeh@ariel.ucs.unimelb.EDU.AU X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Yes. Apparently I too was once confronted with a similar dilemna. An academic requested that I configure (PC) pine for her so that it can make her breakfast (not just toast mind you, she wanted eggs, sausages, coffee the lot!). After a little int. x86 asm. programming, I ran pine. I thought I had the job done, but there was one minor bug (when I fix this, I'll let you know). You see, when I hit "ctrl+B" (where "B" a macro that loads a .com program which would produce the entire breakfast package), I kept getting the error message "BREAKFAST.COM halted .... cereal port not detected". ^^^^^^ ----------------------------------------------------------------- PS I realize that this is a medium for discussion of legitimate pine technical issues, and I if anyone feels that this is being undermined by my reply, my deepest apologies. But I found Darren's email so amusing that I just had to put my bit in. Joe On Fri, 16 Oct 1998, Darren Wyn Rees wrote: > I'm told Pine is REALLY well-specified... > > I need help. I usually download my mail very > early in the morning. Toaster nearby. > > Is there a way to create some sort of macro > in Pine so that I can press CNTL + T (for toast) > to make the toast? > > Thnx (I'm hungry) > -- > Darren Rees merlin@netlink.co.uk > > 2000+ Berfau; fformat .zip .htm M$ Access CSV > http://www.netlink.co.uk/users/merlin/berfau/ > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > ************************************************* Joe Haskian * Systems Programmers Group * Information Technology Services * University of Melbourne * Parkville Vic. 3052 * Phone: (03) 9344-4855 * Fax: (03) 9347-4803 * Email: j.haskian@ITS.unimelb.edu.au * ************************************************* "As far as the laws of mathematics refer to reality, they are not certain; and as far as they are certain, they do not refer to reality". Albert Einstein From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 17 Oct 1998 10:52:12 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA19321 for ; Sat, 17 Oct 1998 10:52:11 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA26237; Sat, 17 Oct 1998 10:52:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA24348; Sat, 17 Oct 1998 10:50:01 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA49692 for ; Sat, 17 Oct 1998 10:45:43 -0700 Received: from admin.inetport.com (root@inetport.com [204.96.100.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13979 for ; Sat, 17 Oct 1998 10:45:42 -0700 Received: from expwncog (ip248.boston-xcom.ma.pub-ip.psi.net [38.26.199.248]) by admin.inetport.com (8.8.8/8.8.5) with SMTP id MAA15519 for ; Sat, 17 Oct 1998 12:45:46 -0500 (CDT) Message-Id: Date: Sat, 17 Oct 1998 13:43:17 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Jonathan E. D. Richmond" To: Pine Discussion Forum Subject: Use Public Transport! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine mailing list X-X-Sender: richmond@mail.inetport.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The breakfast bug problem can be solved by travelling to such projects on a universal cereal bus. ----- Jonathan E. D. Richmond (617) 864-6394 Fellow (617) 496-3194 Taubman Center for State and Local Government FAX: (617) 496-1722 Kennedy School of Government Harvard University Cambridge MA 02138 e-mail: Jonathan_Richmond@harvard.edu or richmond@alum.mit.edu WWW: http://the-tech.mit.edu/~richmond/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 17 Oct 1998 11:01:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA12552 for ; Sat, 17 Oct 1998 11:01:18 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA26338; Sat, 17 Oct 1998 11:01:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA21271; Sat, 17 Oct 1998 10:59:34 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA23928 for ; Sat, 17 Oct 1998 10:56:24 -0700 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA26470 for ; Sat, 17 Oct 1998 10:56:23 -0700 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id MAA15372 for ; Sat, 17 Oct 1998 12:56:21 -0500 Message-Id: Date: Sat, 17 Oct 1998 12:56:21 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Use Public Transport! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Jonathan E. D. Richmond" >Date: Sat, 17 Oct 1998 13:43:17 -0400 (Eastern Daylight Time) >The breakfast bug problem can be solved by travelling to such projects on >a universal cereal bus. Can I get a transfer with that? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 17 Oct 1998 11:19:43 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA29045 for ; Sat, 17 Oct 1998 11:19:42 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA26560; Sat, 17 Oct 1998 11:19:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA25270; Sat, 17 Oct 1998 11:16:30 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA51156 for ; Sat, 17 Oct 1998 11:13:15 -0700 Received: from pilsener.ucs.ualberta.ca (pilsener.ucs.ualberta.ca [129.128.5.19]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA15422 for ; Sat, 17 Oct 1998 11:13:10 -0700 Received: from gpu4.srv.ualberta.ca (gpu4.srv.ualberta.ca [129.128.98.18]) by pilsener.ucs.ualberta.ca (8.9.0/8.9.0) with ESMTP id MAA24092 for ; Sat, 17 Oct 1998 12:11:53 -0600 (MDT) Received: from localhost (maldridg@localhost) by gpu4.srv.ualberta.ca (8.8.5/8.8.5) with SMTP id MAA50192 for ; Sat, 17 Oct 1998 12:11:53 -0600 Message-Id: Date: Sat, 17 Oct 1998 12:11:52 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Lea To: Pine Discussion Forum Subject: Re: Use Public Transport! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Information List X-Sender: maldridg@gpu4.srv.ualberta.ca X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sat, 17 Oct 1998, Adam H. Kerman wrote: > >The breakfast bug problem can be solved by travelling to such projects on > >a universal cereal bus. > > Can I get a transfer with that? Probably. I'd rather have eggroll, though. Hey, is coffee.exe included in the breakfast package? Lea From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 17 Oct 1998 11:29:31 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28908 for ; Sat, 17 Oct 1998 11:29:30 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA26662; Sat, 17 Oct 1998 11:29:22 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA08090; Sat, 17 Oct 1998 11:27:26 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA47964 for ; Sat, 17 Oct 1998 11:24:16 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA15969 for ; Sat, 17 Oct 1998 11:24:16 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id MAA11087; Sat, 17 Oct 1998 12:24:15 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id MAA17931; Sat, 17 Oct 1998 12:21:36 -0600 (MDT) Message-Id: Date: Sat, 17 Oct 1998 12:17:48 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Use Public Transport! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Lea X-Cc: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sat, 17 Oct 1998, Lea wrote: > Hey, is coffee.exe included in the breakfast package? A friend of mine told me about a CORBA-compliant hot beverage dispenser, which was tied into a smart badge system... You'd walk into the break room, and you favorite cup of coffee would be waiting for you, piping hot. -Ian (yes, as far as I know, this is legit) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 18 Oct 1998 04:17:16 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA28349 for ; Sun, 18 Oct 1998 04:17:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA29194; Sun, 18 Oct 1998 04:17:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA25410; Sun, 18 Oct 1998 04:15:53 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA36424 for ; Sun, 18 Oct 1998 04:12:05 -0700 Received: from nimbus.rz.uni-konstanz.de (nimbus.rz.uni-konstanz.de [134.34.3.4]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA23526 for ; Sun, 18 Oct 1998 04:12:04 -0700 Received: from goodhope.terrania.city (actually stheno-155.dial-in.uni-konstanz.de) by nimbus.rz.uni-konstanz.de with Intranet SMTP (PP); Sun, 18 Oct 1998 13:11:43 +0200 Received: from localhost (jeff@localhost [127.0.0.1]) by goodhope.terrania.city (8.8.8/8.8.8/Debian/GNU) with ESMTP id NAA22532 for ; Sun, 18 Oct 1998 13:08:54 +0200 Message-Id: Date: Sun, 18 Oct 1998 13:08:54 +0200 (CEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joerg Friedrich To: Pine Discussion Forum Subject: auto-decrypting uuencoded data MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Mailing List X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Did anyone write a display-filter which automaticly decodes uuedata and saves the decoded file to a directory? -- Heute ist nicht alle Tage, ich komme wieder, keine Frage!!! Joerg ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 18 Oct 1998 04:20:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA07383 for ; Sun, 18 Oct 1998 04:20:19 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA29237; Sun, 18 Oct 1998 04:20:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA16301; Sun, 18 Oct 1998 04:19:12 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA49236 for ; Sun, 18 Oct 1998 04:12:06 -0700 Received: from nimbus.rz.uni-konstanz.de (nimbus.rz.uni-konstanz.de [134.34.3.4]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA23528 for ; Sun, 18 Oct 1998 04:12:05 -0700 Received: from goodhope.terrania.city (actually stheno-155.dial-in.uni-konstanz.de) by nimbus.rz.uni-konstanz.de with Intranet SMTP (PP); Sun, 18 Oct 1998 13:11:44 +0200 Received: from localhost (jeff@localhost [127.0.0.1]) by goodhope.terrania.city (8.8.8/8.8.8/Debian/GNU) with ESMTP id NAA22527 for ; Sun, 18 Oct 1998 13:06:35 +0200 Message-Id: Date: Sun, 18 Oct 1998 13:06:35 +0200 (CEST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Joerg Friedrich To: Pine Discussion Forum Subject: Displaying Attachments MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Mailing List X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is it possible, that Pine (Linux) can display pgp-signed mails which are sent like this: Details about Attachment #1 : Type : Application Subtype : PGP Encoding : QUOTED-PRINTABLE Parameters : FORMAT = mime X-ACTION = signclear X-ORIGINATOR = 326B28A1 Approx. Size : 2,279 bytes Display Method : Can't, Unknown Attachment Format -- Heute ist nicht alle Tage, ich komme wieder, keine Frage!!! Joerg ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 19 Oct 1998 15:44:39 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA24625 for ; Mon, 19 Oct 1998 15:44:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA06102; Mon, 19 Oct 1998 15:44:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA18497; Mon, 19 Oct 1998 15:42:25 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA25892 for ; Mon, 19 Oct 1998 15:39:10 -0700 Received: from mail1.csun.edu (mail1.csun.edu [130.166.1.23]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA17846 for ; Mon, 19 Oct 1998 15:39:09 -0700 Received: from itr04.csun.edu (s011n078.csun.edu [130.166.11.78]) by mail1.csun.edu (2.0.3/SMS 2.0.3) with SMTP id PAA86266 for ; Mon, 19 Oct 1998 15:41:59 -0700 Message-Id: Date: Mon, 19 Oct 1998 15:41:01 -0700 (Pacific Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ovanes Manucharyan To: Pine Discussion Forum Subject: Variables in pine.conf or .pinerc MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Authentication: none X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Is there a way I can insert environment variables into the pine.conf file for example, I'd like all my users to use IMAP, and want to configure it so that it enters their username for them, so the line in the config file would look as such. {host.domain:143/user=username} This works if I have username set to whatever I would like in the pinerc. When I try to do the following {host.domain:143/user=$LOGNAME} in the pine.conf file it doesn't work Am I doing something wrong? Sincerely, Ovanes Manucharyan ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 20 Oct 1998 07:31:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA21303 for ; Tue, 20 Oct 1998 07:31:19 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA21157; Tue, 20 Oct 1998 07:31:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA22097; Tue, 20 Oct 1998 07:29:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA56464 for ; Tue, 20 Oct 1998 07:25:39 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id HAA26489 for ; Tue, 20 Oct 1998 07:25:37 -0700 Received: from [132.198.177.59] (132.198.177.59) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.F9E16B80@smtpgate.uvm.edu>; Tue, 20 Oct 1998 10:25:36 -0400 Message-Id: Date: Tue, 20 Oct 1998 10:20:48 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: path of environment variables in PC-Pine MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: Pine Development Team X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i thought that the addressbook and signature would be searched for in the same directory as the pinerc directory. this is not working with my addressbook, and signature file. i am using the default names for these files. addrbook and pine.sig. the debug file is being placed in the same direcotry as the pinerc file, as it should. obviously, i can just change my settings, and it works. but i am just stating that the actual behavior of pc-pine is different from the theoretical behavior Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 E-Mailer____free_____http://www.washington.edu/pine ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 12:26:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA18393 for ; Wed, 21 Oct 1998 12:26:06 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA10010; Wed, 21 Oct 1998 12:26:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA07718; Wed, 21 Oct 1998 12:23:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA41172 for ; Wed, 21 Oct 1998 12:20:26 -0700 Received: from postoffice.npac.syr.edu (postoffice.npac.syr.edu [128.230.7.230]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA12140 for ; Wed, 21 Oct 1998 12:19:56 -0700 Received: from vega.npac.syr.edu.mwvbqpdhnk (vega.npac.syr.edu [128.230.8.146]) by postoffice.npac.syr.edu (8.7.5/8.7.1) with SMTP id PAA16871 for ; Wed, 21 Oct 1998 15:19:54 -0400 (EDT) Received: from localhost by vega.npac.syr.edu.mwvbqpdhnk (SMI-8.6/SMI-SVR4) id PAA24851; Wed, 21 Oct 1998 15:19:54 -0400 Message-Id: Date: Wed, 21 Oct 1998 15:19:53 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mark Natoli To: Pine Discussion Forum Subject: incoming-startup-rule MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I have installed pine 4.05 on solaris 2.6. I have created a /usr/local/lib/pine.conf file with only user-domain and inbox-path defined. The setting for incoming-startup-rule was default which should be first-unseen. However all users get the first message with this option. Even when it is explicitly set to first-unseen the first message appears. Why can't I get cursor to go to the first unseen message. TIA, Mark Mark Natoli Systems and Network Administrator Northeast Parallel Architectures Center, Syracuse University mnatoli@npac.syr.edu ph. 315.443.2010 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 12:38:15 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA24537 for ; Wed, 21 Oct 1998 12:38:14 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA10437; Wed, 21 Oct 1998 12:38:07 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA08482; Wed, 21 Oct 1998 12:33:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA40218 for ; Wed, 21 Oct 1998 12:32:09 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA05424 for ; Wed, 21 Oct 1998 12:32:08 -0700 Received: by gw.learjet.com; id OAA15920; Wed, 21 Oct 1998 14:32:07 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma015802; Wed, 21 Oct 98 14:31:25 -0500 Received: from unknown (hx02.learjet.com [172.18.126.91]) by hs8.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA08103 for ; Wed, 21 Oct 1998 14:31:24 -0500 (CDT) Received: from localhost by unknown (1.37.109.20) id AA248718283; Wed, 21 Oct 1998 14:31:23 -0500 Message-Id: Date: Wed, 21 Oct 1998 14:31:23 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff To: Pine Discussion Forum Subject: Compose including other messages? Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info List X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, all. I'm wondering if there is an easier way to include other e-mail messages in a composition. Ie: I'm replying to a certain email, but would like to quote part or all of a separate e-mail. Currently, I do this by postponing (^o) the current message, going to the other e-mail, saving it out to a file, then resuming the compose, and ^r inserting the file. If this option exists, could someone point me to it, and if it doesn't, would it be feeping creaturism (to quote L. Wall) to include it? Thanks! -jeff ---- Jeff Schaller schaller@learjet.com UNIX System Administrator Phone: (316) 946-7255 Learjet Inc Fax: (316) 946-2809 ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 13:38:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA26736 for ; Wed, 21 Oct 1998 13:38:40 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA12232; Wed, 21 Oct 1998 13:38:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA04787; Wed, 21 Oct 1998 13:36:01 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA40254 for ; Wed, 21 Oct 1998 13:34:29 -0700 Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA26078 for ; Wed, 21 Oct 1998 13:34:26 -0700 Received: from localhost (ehr@localhost) by oracle.dsuper.net (Delphi Sendmail 1.2/8.6.9) with SMTP id QAA31870 for ; Wed, 21 Oct 1998 16:40:13 -0400 (EDT) Message-Id: Date: Wed, 21 Oct 1998 16:40:12 -0400 (EDT) Reply-To: robibaro@supernet.ca Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Eric Robibaro To: Pine Discussion Forum Subject: hashed mail spool with pine 4.05 and imap 4.4 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Does anyone know if support for this is included in either? Has anyone added support for this in pine before? If not, what's the best ballpark figure for the effort of converting both (especially the number of files that must be checked) to support hash_spool=2 directory structures (/usr/spool/mail/e/h/ehr)? I've looked at the source and I noticed just how extensive they were for both products and since this is to be a production system (on an alpha) I want to minimize mistakes/forgotten code references Thanks in advance -- Eric Robibaro Member of Team NetOps Delphi Supernet inc. 1-800-super-mtl robibaro@supernet.ca ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 13:50:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA15883 for ; Wed, 21 Oct 1998 13:50:47 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA12618; Wed, 21 Oct 1998 13:50:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA05276; Wed, 21 Oct 1998 13:47:08 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA39680 for ; Wed, 21 Oct 1998 13:45:49 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id NAA14925 for ; Wed, 21 Oct 1998 13:45:45 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.3EB3A080@smtpgate.uvm.edu>; Wed, 21 Oct 1998 16:45:43 -0400 Message-Id: Date: Wed, 21 Oct 1998 16:46:11 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN the only other way is as follows: make sure all the messages you want to reply to our quote from are in the same mail folder. then hit reply on the message you want to include, and then hit ^R and hit ^W and insert a message, then say how many messages in the folder. as you can see this is just as annoying as your old way. so all i can say is, that is a good suggestion for the next version of pine. On Wed, 21 Oct 1998, Jeff wrote: > > Date: Wed, 21 Oct 1998 14:31:23 -0500 (CDT) > From: Jeff > To: Pine Discussion Forum > Subject: Compose including other messages? > > Hello, all. > > I'm wondering if there is an easier way to include other e-mail > messages in a composition. Ie: I'm replying to a certain email, but > would like to quote part or all of a separate e-mail. Currently, I do > this by postponing (^o) the current message, going to the other > e-mail, saving it out to a file, then resuming the compose, and ^r > inserting the file. If this option exists, could someone point me to > it, and if it doesn't, would it be feeping creaturism (to quote L. > Wall) to include it? > > Thanks! > > -jeff > > ---- > Jeff Schaller schaller@learjet.com > UNIX System Administrator Phone: (316) 946-7255 > Learjet Inc Fax: (316) 946-2809 > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 E-Mailer____free_____http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 14:13:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA27394 for ; Wed, 21 Oct 1998 14:13:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA13316; Wed, 21 Oct 1998 14:13:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA20104; Wed, 21 Oct 1998 14:10:40 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA34236 for ; Wed, 21 Oct 1998 14:09:11 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA18493 for ; Wed, 21 Oct 1998 14:09:10 -0700 Received: by gw.learjet.com; id QAA01313; Wed, 21 Oct 1998 16:09:09 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma001287; Wed, 21 Oct 98 16:08:52 -0500 Received: from unknown (hx02.learjet.com [172.18.126.91]) by hs8.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id QAA17748 for ; Wed, 21 Oct 1998 16:08:51 -0500 (CDT) Received: from localhost by unknown (1.37.109.20) id AA255554130; Wed, 21 Oct 1998 16:08:50 -0500 Message-Id: Date: Wed, 21 Oct 1998 16:08:50 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info List X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 21 Oct 1998, Aaron S. Hawley wrote: > the only other way is as follows: > > make sure all the messages you want to reply to our quote from are in the > same mail folder. then hit reply on the message you want to include, and > then hit ^R and hit ^W and insert a message, then say how many messages in > the folder. as you can see this is just as annoying as your old way. so > all i can say is, that is a good suggestion for the next version of pine. Ahh, right, right. I'd forgotten that last detail of being able to include messages from the current folder, but not from different ones. So the feature would be: expand the ^R ^W to allow one to pull emails from different folders. Thanks! ---- Jeff Schaller schaller@learjet.com UNIX System Administrator Phone: (316) 946-7255 Learjet Inc Fax: (316) 946-2809 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 15:03:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA16582 for ; Wed, 21 Oct 1998 15:03:26 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA14808; Wed, 21 Oct 1998 15:03:16 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA22846; Wed, 21 Oct 1998 15:01:18 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA59808 for ; Wed, 21 Oct 1998 14:59:46 -0700 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA18662 for ; Wed, 21 Oct 1998 14:59:45 -0700 Received: from Chicago.ess.harris.com (chicago.ess.harris.com [130.41.63.112]) by ess.harris.com (8.8.6/8.8.6) with ESMTP id RAA21344 for ; Wed, 21 Oct 1998 17:59:41 -0400 (EDT) Received: from Maxville.ESS.Harris.com by Chicago.ess.harris.com (8.8.8+Sun/SMI-SVR4) id RAA10819; Wed, 21 Oct 1998 17:59:41 -0400 (EDT) Received: from localhost by Maxville.ESS.Harris.com (SMI-8.6/SMI-SVR4) id RAA02754; Wed, 21 Oct 1998 17:59:41 -0400 Message-Id: Date: Wed, 21 Oct 1998 17:59:40 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Paul Halsema To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: phalsema@Maxville.ess.harris.com X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 21 Oct 1998, Jeff wrote: > On Wed, 21 Oct 1998, Aaron S. Hawley wrote: > > the only other way is as follows: > > > > make sure all the messages you want to reply to our quote from are in the > > same mail folder. then hit reply on the message you want to include, and > > then hit ^R and hit ^W and insert a message, then say how many messages in > > the folder. as you can see this is just as annoying as your old way. so > > all i can say is, that is a good suggestion for the next version of pine. > > Ahh, right, right. I'd forgotten that last detail of being able to > include messages from the current folder, but not from different ones. > So the feature would be: expand the ^R ^W to allow one to pull emails > from different folders. Two other options: 1) If messages are all in the same folder, then select the ones you want to include (:), then do Apply and Reply. 2) For messages in different folders do Aaron's ^R ^W suggestion, followed by ^O to postpone, Go to the other folder, resume composing the postponed message and then ^R ^W to include messages from that folder. It's not quite as awkward as it sounds and a little better than saving or exporting each file first/ ---Paul From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 15:32:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA19580 for ; Wed, 21 Oct 1998 15:32:55 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA15795; Wed, 21 Oct 1998 15:32:48 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA24609; Wed, 21 Oct 1998 15:31:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA29988 for ; Wed, 21 Oct 1998 15:28:57 -0700 Received: from nov.diac.com (diac.com [209.64.40.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA09837 for ; Wed, 21 Oct 1998 15:28:57 -0700 Received: from localhost (ekwall2@localhost) by nov.diac.com (8.8.8/8.8.8) with SMTP id WAA29111; Wed, 21 Oct 1998 22:28:31 GMT Message-Id: Date: Wed, 21 Oct 1998 16:28:31 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Ekwall To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Jeff X-Cc: Pine Discussion Forum X-Sender: ekwall2@november X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 21 Oct 1998, Jeff wrote: On Wed, 21 Oct 1998, Aaron S. Hawley wrote: > the only other way is as follows: > > make sure all the messages you want to reply to our quote from are in the > same mail folder. then hit reply on the message you want to include, and > then hit ^R and hit ^W and insert a message, then say how many messages in > the folder. as you can see this is just as annoying as your old way. so > all i can say is, that is a good suggestion for the next version of pine. Ahh, right, right. I'd forgotten that last detail of being able to include messages from the current folder, but not from different ones. So the feature would be: expand the ^R ^W to allow one to pull emails from different folders. Jeff Schaller schaller@learjet.com -------------- Hi all, That's an interesting feature, but strange in function to me. Why or what exactly was that ^W implimented for? - BULK MAILING?? or something?? And what's with the " enter number of messages " 2?, 200? ---> *.*? Looks like one would have to have a very clean folder and in order and seperated by date/time for inclusion's to make sense too. Just curious, as it works! I thought the first request was valid. Is a 'folder directory' with Include Which? a way to go on that? Thoughts? Thanks -=se=- ekwall2@diac.com p.s. Since ^W is whereis (search for string) in compose would instead of number to include be better an ascii "keyword" to include? so, anyfile containing the word "cats & dogs" are found and included? just a thought. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 18:07:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA29113 for ; Wed, 21 Oct 1998 18:07:49 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA19762; Wed, 21 Oct 1998 18:07:43 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA08656; Wed, 21 Oct 1998 18:05:35 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA42984 for ; Wed, 21 Oct 1998 18:03:49 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id SAA09208 for ; Wed, 21 Oct 1998 18:03:49 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.4BBD7250@smtpgate.uvm.edu>; Wed, 21 Oct 1998 21:03:47 -0400 Message-Id: Date: Wed, 21 Oct 1998 21:04:06 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN before jeff asked the question about including other messages, i had never used the feature of including other messages. and when i first used it i of course used ^R to include a files, then i thought I would get the option of going to files (^T) and then be shown my mail folders and have to select a folder, and then perhaps select a message or multiple messages. this is option of browsing your messages or files is used when you are saving a message to a folder, except of course you don't select messages. so i would think pine is capable, just for some reason it wasn't used there. and yes, i would also like to know why the hell you would want to choose a certain of number of messages after pressing ^W InsertMsg. cause it's a pain in the you now what to have to delete all the messages you wouldn't want. Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 E-Mailer____free_____http://www.washington.edu/pine On Wed, 21 Oct 1998, Steve Ekwall wrote: > Date: Wed, 21 Oct 1998 16:28:31 -0600 (MDT) > From: Steve Ekwall > To: Pine Discussion Forum > Subject: Re: Compose including other messages? > > On Wed, 21 Oct 1998, Jeff wrote: > On Wed, 21 Oct 1998, Aaron S. Hawley wrote: > > the only other way is as follows: > > > > make sure all the messages you want to reply to our quote from are in the > > same mail folder. then hit reply on the message you want to include, and > > then hit ^R and hit ^W and insert a message, then say how many messages in > > the folder. as you can see this is just as annoying as your old way. so > > all i can say is, that is a good suggestion for the next version of pine. > > Ahh, right, right. I'd forgotten that last detail of being able to > include messages from the current folder, but not from different ones. > So the feature would be: expand the ^R ^W to allow one to pull emails > from different folders. > Jeff Schaller schaller@learjet.com > > -------------- > Hi all, > > That's an interesting feature, but strange in function to me. Why or > what exactly was that ^W implimented for? - BULK MAILING?? or something?? > And > what's with the " enter number of messages " 2?, 200? ---> *.*? > Looks like one would have to have a very clean folder and in order and > seperated by date/time for inclusion's to make sense too. > Just curious, as it works! I thought the first request was valid. > Is a 'folder directory' with Include Which? a way to go on that? Thoughts? > > Thanks > -=se=- > ekwall2@diac.com > > p.s. Since ^W is whereis (search for string) in compose would instead of > number to include be better an ascii "keyword" to include? so, anyfile > containing the word "cats & dogs" are found and included? just a thought. > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 18:35:04 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA00392 for ; Wed, 21 Oct 1998 18:35:03 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA13960; Wed, 21 Oct 1998 18:34:56 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA17981; Wed, 21 Oct 1998 18:32:46 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA38240 for ; Wed, 21 Oct 1998 18:31:27 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id SAA32763 for ; Wed, 21 Oct 1998 18:31:27 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.2805EF50@smtpgate.uvm.edu>; Wed, 21 Oct 1998 21:31:25 -0400 Message-Id: Date: Wed, 21 Oct 1998 21:31:47 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: pc-pine working directory multiple users MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN if anybody out there is using pc-pine with multiple users. i suggest using different directory for each user in the c:\\ or whatever directory you have it your pine.exe file. then give the name of the directory as the first name of the person or there username. and then you can use the default names for all the configuration files, addressbooks, etc. then if you were to have a Windows (good 'ol 95 in my case) shortcut for the program, and then in the shortcut properties change 'Start In' to c:\\ then, from what i've experimented with, all the settings for files like the signature and addressbook, don't need to be changed to c:\\\ like pine.sig, or addrbook. i thought this was a real easy way to make multiple users. by just making a shortcut to pine giving the 'Start In' variable c:\\ then having a pinerc file with some common settings of the multiple users. for example at my school, the University of Vermont, everyone has the same smtp server, mail server, saved messages folder, etc. so having to plug in the values for each user is a pain. but keep values like features, username, personal id, etc, open for editing by that user, since they are user-specific. did everyone learn something new. hopefully i'm not just a loser pointing out the obvious. keep pining (ouch on the lingo attempt aaron) Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 E-Mailer____free_____http://www.washington.edu/pine ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 18:40:35 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA27524 for ; Wed, 21 Oct 1998 18:40:34 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA20300; Wed, 21 Oct 1998 18:40:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA02580; Wed, 21 Oct 1998 18:38:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA22762 for ; Wed, 21 Oct 1998 18:37:22 -0700 Received: from gw-us1new.philips.com (gw-us1new.philips.com [205.167.14.36]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA26455 for ; Wed, 21 Oct 1998 18:37:21 -0700 Received: from smtprelay-us1.philips.com (localhost.philips.com [127.0.0.1]) by gw-us1new.philips.com with ESMTP id VAA16936 for ; Wed, 21 Oct 1998 21:37:20 -0400 (EDT) (envelope-from Jeff.Goswick@abq.sc.philips.com) Received: from smtprelay-nam1.philips.com(130.140.196.208) by gw-us1new.philips.com via mwrap (4.0a) id xma016934; Wed, 21 Oct 98 21:37:20 -0400 Received: from smtphub.sv.sc.philips.com (smtphub.sv.sc.philips.com [130.140.45.86]) by smtprelay-us1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id VAA00904 for ; Wed, 21 Oct 1998 21:37:19 -0400 (EDT) Received: from smtphub.abq.sc.philips.com (smtphub.abq.sc.philips.com [130.140.3.9]) by smtphub.sv.sc.philips.com (8.8.5/8.8.5) with ESMTP id SAA21970 for ; Wed, 21 Oct 1998 18:37:17 -0700 (PDT) Received: from abqhp1.abq.sc.philips.com (abqhp1.abq.sc.philips.com [130.140.4.1]) by smtphub.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id TAA26845 for ; Wed, 21 Oct 1998 19:37:16 -0600 (MDT) Received: from abqhp39.abq.sc.philips.com (abqhp39.abq.sc.philips.com [130.140.4.39]) by abqhp1.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id VAA17767 for ; Wed, 21 Oct 1998 21:37:19 -0400 (EDT) Received: from localhost (goswick@localhost) by abqhp39.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id TAA13488 for ; Wed, 21 Oct 1998 19:36:04 -0600 (MDT) Message-Id: Date: Wed, 21 Oct 1998 19:36:04 -0600 (MDT) Reply-To: Jeff Goswick Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff Goswick To: Pine Discussion Forum Subject: Re: Compose including other messages? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: Jeff.Goswick@abq.sc.philips.com X-To: Pine Discussion Forum X-Authentication-Warning: abqhp39.abq.sc.philips.com: goswick owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The ^R,^W allows you to include 1 message from the current folder, not a series of mesages. The number that you enter is the Message Number, i.e. the number in the second column from the left on the message index screen. So to include 2 different messages in a new email, reply to the first, and while editing the text, hit ^R, then ^W, then enter the index number (current folder of course) of the other message you want to include. ^O (postpone), G (goto folder), then C (resume compose) is needed if the messages you want to include are in different folders It would be nice if you could browse the index, select multiple messages, browse folders, etc, but I personally wouldn't use that feature very much. Regards Jeff On Wed, 21 Oct 1998, Aaron S. Hawley wrote: > and yes, i would also like to know why the hell you > would want to choose a certain of number of messages after pressing ^W > InsertMsg. cause it's a pain in the you now what to have to delete all > the messages you wouldn't want. > > Aaron S. Hawley > ashawley@zoo.uvm.edu > 802.656.7396 > http://www.uvm.edu/~ashawley > University of Vermont > Home: Vergennes, VT, USA From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 21 Oct 1998 22:31:50 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA02387 for ; Wed, 21 Oct 1998 22:31:48 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA23669; Wed, 21 Oct 1998 22:31:42 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA10266; Wed, 21 Oct 1998 22:29:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA46376 for ; Wed, 21 Oct 1998 22:28:20 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id WAA08174 for ; Wed, 21 Oct 1998 22:28:20 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.3F672EE0@smtpgate.uvm.edu>; Thu, 22 Oct 1998 1:28:18 -0400 Message-Id: Date: Thu, 22 Oct 1998 01:28:21 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: pc-pine, windows, configuration stuff MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i'm that kid who is always talking about multiple users with pc-pine. cause lets face it is not as good as unix pines, etc. with multiple accounts. last time i was talking about putting each users configuration files in a seperate directory in your pine directory, and then changing a shortcut for a certain users 'Start In' variable in the Shortcut properties window. well, I've come across a problem in my own theory i made up. why is it that i can't put c:\Pine\aaron (my name) for my 'Start In' variable, and then pine will automatically find the pinerc file there? cause i have to put -p pinerc to tell pine where the pinerc file. which is funny because i'm essentially telling pine to do what it should do by default, which is look for pinerc in the same directory as pine.exe. i don't have to put -p c:\Pine\aaron\pinerc, or jut -p aaron\pinerc. is it because of the order Pine looks for the pinerc file, and then looks in the 'Start In' command. sorry but i don't know how pine works inside, and only so much about windows. but this doesn't seem to make sense. now i am i supposed to send a suggestion to the pine development team like this. Or are you guys listening in right now? Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, USA PC-Pine 4.05 E-Mailer http://www.washington.edu/pine fast,small,simple,complex,free ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 02:05:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA01091 for ; Thu, 22 Oct 1998 02:05:05 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA20297; Thu, 22 Oct 1998 02:04:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA21687; Thu, 22 Oct 1998 02:02:36 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA30702 for ; Thu, 22 Oct 1998 02:01:10 -0700 Received: from green.csi.cam.ac.uk (exim@green.csi.cam.ac.uk [131.111.8.57]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA20150 for ; Thu, 22 Oct 1998 02:01:10 -0700 Received: from quinag.csi.cam.ac.uk ([131.111.10.53] helo=cam.ac.uk) by green.csi.cam.ac.uk with smtp (Exim 2.05 #3) id 0zWGcD-0004VJ-00; Thu, 22 Oct 1998 10:01:05 +0100 Message-Id: Date: Thu, 22 Oct 1998 10:02:28 +0100 (BST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Barry Landy To: Pine Discussion Forum Subject: Re: incoming-startup-rule In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Mark Natoli X-Cc: Pine Discussion Forum X-X-Sender: bl10@imap.hermes.cam.ac.uk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 21 Oct 1998, Mark Natoli wrote: :>Hi, :> :> I have installed pine 4.05 on solaris 2.6. I have created a :>/usr/local/lib/pine.conf file with only user-domain and inbox-path :>defined. :> The setting for incoming-startup-rule was default which should be :>first-unseen. However all users get the first message with this option. :>Even when it is explicitly set to first-unseen the first message appears. :> Why can't I get cursor to go to the first unseen message. I had this prohblem too. It is caused by a backdated IMAP4 server. Install the latest version and this bug will vanish...! ---------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 1223 334600 Head of Systems and Development Direct line: +44 1223 334713 University of Cambridge Computing Service New Museums Site Email:bl10@cam.ac.uk Pembroke Street, Cambridge CB2 3QG From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 13:36:52 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA19707 for ; Thu, 22 Oct 1998 13:36:50 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA11649; Thu, 22 Oct 1998 13:36:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA10495; Thu, 22 Oct 1998 13:32:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA49440 for ; Thu, 22 Oct 1998 13:29:49 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA01984 for ; Thu, 22 Oct 1998 13:29:44 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id NAA01420; Thu, 22 Oct 1998 13:29:29 -0700 (PDT) Message-Id: Date: Thu, 22 Oct 1998 13:29:29 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: Re: hashed mail spool with pine 4.05 and imap 4.4 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: robibaro@supernet.ca X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 21 Oct 1998, Eric Robibaro wrote: > Does anyone know if support for this is included in either? > Has anyone added support for this in pine before? > If not, what's the best ballpark figure for the effort of converting both > (especially the number of files that must be checked) to support > hash_spool=2 directory structures (/usr/spool/mail/e/h/ehr)? > I've looked at the source and I noticed just how extensive they were for > both products and since this is to be a production system (on an alpha) I > want to minimize mistakes/forgotten code references This may not be an option for you but we use procmail as an MTA for sendmail to put mail in users' home directories. This a good solution for us since users don't need a quota for /var. We have info at http://www3.hmc.edu/docs/coolstuff about our sendmail and popper configurations. I think our imap is standard but I'll ask. -Mike -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 13:42:46 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA19893 for ; Thu, 22 Oct 1998 13:42:45 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA11828; Thu, 22 Oct 1998 13:42:39 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA05525; Thu, 22 Oct 1998 13:40:08 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA44770 for ; Thu, 22 Oct 1998 13:38:44 -0700 Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA03238 for ; Thu, 22 Oct 1998 13:38:39 -0700 Received: from localhost (ehr@localhost) by oracle.dsuper.net (Delphi Sendmail 1.2/8.6.9) with SMTP id QAA06959; Thu, 22 Oct 1998 16:44:08 -0400 (EDT) Message-Id: Date: Thu, 22 Oct 1998 16:44:07 -0400 (EDT) Reply-To: Eric Robibaro Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Eric Robibaro To: Pine Discussion Forum Subject: Re: hashed mail spool with pine 4.05 and imap 4.4 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Thomas Cope X-Cc: robibaro@supernet.ca, Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 22 Oct 1998, Michael Thomas Cope wrote: > From: Michael Thomas Cope > Subject: Re: hashed mail spool with pine 4.05 and imap 4.4 > Date: Thu, 22 Oct 1998 13:29:29 -0700 (PDT) > To: robibaro@supernet.ca > > On Wed, 21 Oct 1998, Eric Robibaro wrote: > > > Does anyone know if support for this is included in either? > > Has anyone added support for this in pine before? > > If not, what's the best ballpark figure for the effort of converting both > > (especially the number of files that must be checked) to support > > hash_spool=2 directory structures (/usr/spool/mail/e/h/ehr)? > > I've looked at the source and I noticed just how extensive they were for > > both products and since this is to be a production system (on an alpha) I > > want to minimize mistakes/forgotten code references > This may not be an option for you but we use procmail as an MTA for > sendmail to put mail in users' home directories. This a good solution for > us since users don't need a quota for /var. That isn't really the problem how do you get the info OUT? I've checked, seems your system puts the emails in the user's home directories, which isn't what we really want, thanks anyways > We have info at http://www3.hmc.edu/docs/coolstuff about our > sendmail and popper configurations. I think our imap is standard but I'll > ask. I'll look into those > -Mike > -- > Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 > E-mail: Michael_Cope@hmc.edu > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 13:51:05 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA20129 for ; Thu, 22 Oct 1998 13:51:04 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA06970; Thu, 22 Oct 1998 13:50:58 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA11804; Thu, 22 Oct 1998 13:49:14 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA13464 for ; Thu, 22 Oct 1998 13:47:53 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA04709 for ; Thu, 22 Oct 1998 13:47:48 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id NAA10286 for ; Thu, 22 Oct 1998 13:47:47 -0700 (PDT) Message-Id: Date: Thu, 22 Oct 1998 13:47:46 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: shared lib build of pine? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Has anyone done a shared library build of pine? We have a 800 user system and about 100-200 users are using pine at any one time. Many of them leave it on all the time and we don't really mind since the system load is minimal, however since each process is using 2-5M of resident memory, the memory load is significant. Our thought is that a shared library build would reduce the amount of redundant memory use. Has anyone done this or have suggestions? We are also buying more memory. -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 14:43:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA09360 for ; Thu, 22 Oct 1998 14:43:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA08664; Thu, 22 Oct 1998 14:43:32 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA29205; Thu, 22 Oct 1998 14:41:02 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA22884 for ; Thu, 22 Oct 1998 14:39:30 -0700 Received: from neon.transmeta.com (neon-best.transmeta.com [206.184.214.10]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA06010 for ; Thu, 22 Oct 1998 14:39:30 -0700 Received: from deepthought.transmeta.com (mailhost.transmeta.com [10.1.1.15]) by neon.transmeta.com (8.9.1/8.9.1) with ESMTP id OAA04712; Thu, 22 Oct 1998 14:35:48 -0700 Received: from yamato.transmeta.com (admin@yamato.transmeta.com [10.1.1.218]) by deepthought.transmeta.com (8.8.8+spamcan/8.8.5) with ESMTP id OAA21543; Thu, 22 Oct 1998 14:38:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by yamato.transmeta.com (8.8.5/8.7.3) with ESMTP id OAA00460; Thu, 22 Oct 1998 14:38:57 -0700 Message-Id: Date: Thu, 22 Oct 1998 14:38:56 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jauder Ho To: Pine Discussion Forum Subject: Re: hashed mail spool with pine 4.05 and imap 4.4 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Thomas Cope X-Cc: Pine Discussion Forum X-BOFH-Subliminal-Message: Use vi not Emacs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN it is not a problem with pine rather you have to adjust the imap source code. it is not that hard to do. I can send patches that adjust the concept of home dir to /var/imap/ it should be easy to move it to /var/imap/u/s/username. I haven't moved to that model yet because we are just over 200 people :) --Jauder On Thu, 22 Oct 1998, Michael Thomas Cope wrote: > On Wed, 21 Oct 1998, Eric Robibaro wrote: > > > Does anyone know if support for this is included in either? > > Has anyone added support for this in pine before? > > If not, what's the best ballpark figure for the effort of converting both > > (especially the number of files that must be checked) to support > > hash_spool=2 directory structures (/usr/spool/mail/e/h/ehr)? > > I've looked at the source and I noticed just how extensive they were for > > both products and since this is to be a production system (on an alpha) I > > want to minimize mistakes/forgotten code references > This may not be an option for you but we use procmail as an MTA for > sendmail to put mail in users' home directories. This a good solution for > us since users don't need a quota for /var. > We have info at http://www3.hmc.edu/docs/coolstuff about our > sendmail and popper configurations. I think our imap is standard but I'll > ask. > -Mike > -- > Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 > E-mail: Michael_Cope@hmc.edu > > > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 15:47:48 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA22654 for ; Thu, 22 Oct 1998 15:47:47 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA15138; Thu, 22 Oct 1998 15:47:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA26575; Thu, 22 Oct 1998 15:45:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA22840 for ; Thu, 22 Oct 1998 15:43:51 -0700 Received: from uxa.ecn.bgu.edu (uxa.ecn.bgu.edu [143.43.32.11]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA02766 for ; Thu, 22 Oct 1998 15:43:50 -0700 Received: from ecom4.ecnet.net (mfhmp@ecom4 [143.43.32.24]) by uxa.ecn.bgu.edu (8.8.2/8.8.2) with ESMTP id RAA25760 for ; Thu, 22 Oct 1998 17:43:49 -0500 (CDT) Received: from localhost (mfhmp@localhost) by ecom4.ecnet.net (8.8.8/8.8.8) with SMTP id RAA11099 for ; Thu, 22 Oct 1998 17:43:41 -0500 (CDT) Message-Id: Date: Thu, 22 Oct 1998 17:43:41 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Heather M. McMeekan" To: Pine Discussion Forum Subject: HELP!! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: ecom4.ecnet.net: mfhmp owned process doing -bs X-Sender: mfhmp@ecom4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I have a weird problem. For some reason, when I log into pine, it requires me to enter my user name AND password...so, when I log onto telnet, I must enter it twice...which gets to be a pain. I have tried everything I know to fix it, and apparently nobody here knows how to fix it for me. Can you help? Heather McMeekan "I don't want to get to the end of my life and find that I just lived the length of it. I want to have lived the width of it as well." -Diane Ackerman ********************************************** * Heather M. McMeekan, B.A., EMT-P * * 459 Stipes Hall * * Western Illinois University * * Macomb, Il. 61455 * * (309) 298-1093 * * http://www.wiu.edu/users/mfhmp/index.html * ********************************************** ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 16:16:56 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA22773 for ; Thu, 22 Oct 1998 16:16:54 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA15904; Thu, 22 Oct 1998 16:16:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA06134; Thu, 22 Oct 1998 16:15:13 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA30446 for ; Thu, 22 Oct 1998 16:13:48 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA18393 for ; Thu, 22 Oct 1998 16:13:34 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id QAA23873; Thu, 22 Oct 1998 16:12:55 -0700 (PDT) Message-Id: Date: Thu, 22 Oct 1998 16:12:55 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: Re: HELP!! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Heather M. McMeekan" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 22 Oct 1998, Heather M. McMeekan wrote: > > > Hello, > > I have a weird problem. For some reason, when I log into pine, it > requires me to enter my user name AND password...so, when I log onto > telnet, I must enter it twice...which gets to be a pain. Is this a new behavior? If so I would be very suspicious that somebody wants your password and has written a wrapper to ask for it. Use the command which pine to find out what gets executed when you call pine. If it's not /usr/bin/pine or /usr/local/bin/pine or /bin/pine contact your system administrator. If this is not the case, look at your ~/.pinerc file more ~/.pinerc and see if anything looks odd. Even if it doesn't try moving .pinerc to something else temporarily mv ~/.pinerc ~/pinerc and start pine. Pine with create a default .pinerc If this works without the password prompt, either configure Pine the way you had it before or see what the difference between .pinerc and pinerc is diff ~/.pinerc ~/pinerc identify the offending parameter, edit pinerc and move it back mv ~/pinerc ~/.pinerc -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 16:27:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA23064 for ; Thu, 22 Oct 1998 16:27:44 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA16187; Thu, 22 Oct 1998 16:27:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA28706; Thu, 22 Oct 1998 16:26:15 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA41152 for ; Thu, 22 Oct 1998 16:24:46 -0700 Received: from sass165.sandia.gov (mailgate.sandia.gov [132.175.109.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA19699 for ; Thu, 22 Oct 1998 16:24:45 -0700 Received: from sasg829.sandia.gov (sasg829.sandia.gov [134.253.226.190]) by sass165.sandia.gov (8.9.1a/8.9.1a) with ESMTP id RAA16861 for ; Thu, 22 Oct 1998 17:24:41 -0600 (MDT) Message-Id: Date: Thu, 22 Oct 1998 17:23:15 -0600 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Daniel Sands To: Pine Discussion Forum Subject: Re: HELP!! In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 22 Oct 1998, Michael Thomas Cope wrote: > On Thu, 22 Oct 1998, Heather M. McMeekan wrote: > > > > > > > Hello, > > > > I have a weird problem. For some reason, when I log into pine, it > > requires me to enter my user name AND password...so, when I log onto > > telnet, I must enter it twice...which gets to be a pain. > Is this a new behavior? If so I would be very suspicious that somebody > wants your password and has written a wrapper to ask for it. Use the > command She is probably using an IMAP server, which requires authentication before she can read her mail. And I know of no way around this. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 16:32:59 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA22473 for ; Thu, 22 Oct 1998 16:32:58 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA16324; Thu, 22 Oct 1998 16:32:51 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA28931; Thu, 22 Oct 1998 16:30:54 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA23010 for ; Thu, 22 Oct 1998 16:29:38 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA28257 for ; Thu, 22 Oct 1998 16:29:33 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 23 Oct 1998 07:29:25 +0800 Message-Id: <001a01bdfe13$c69047e0$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 23 Oct 1998 07:29:12 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: HELP!! In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Heather M. McMeekan" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Heather, > I have a weird problem. For some reason, when I log into pine, it > requires me to enter my user name AND password...so, when I log onto > telnet, I must enter it twice...which gets to be a pain. > > I have tried everything I know to fix it, and apparently nobody here knows > how to fix it for me. Can you help? I think you are saying your process is like this: 1. telnet to a specific host. 2. enter username & password. 3. type pine (or choose it from a menu). 4. enter username & password. If this is the case, then your pine is probably configured to contact an IMAP server on a different host than the one you connected to in step one. Thus, the need for additional authentication. First, for the telnet session, second for the IMAP session. If you confirm the scenario your administrators will have to configure the IMAP host to use rimap, which is configured in a manner similar to rlogin. I don't have the details at hand but can dig them up if need be. Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 17:29:32 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA24904 for ; Thu, 22 Oct 1998 17:29:31 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA17862; Thu, 22 Oct 1998 17:29:24 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA09771; Thu, 22 Oct 1998 17:27:12 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA22636 for ; Thu, 22 Oct 1998 17:24:49 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA26726 for ; Thu, 22 Oct 1998 17:24:48 -0700 Received: from ccunltd.cdc.net (pm10-56.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3A8JF96PC000OZS@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Thu, 22 Oct 1998 20:22:45 EST Message-Id: <01J3A8JFXBJ6000OZS@CSTCC.CC.TN.US> Date: Thu, 22 Oct 1998 20:30:33 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: Auto respond MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello, I need help. Is there any way that pine can allow you to automatically send out mail when you receive mail. For example, if Im out of town and I want my clients to know that I'm out of town and will respond to there email when I return, by a reply messages being sent out automatically. Does anyone understand what I'm asking for? Thanks Debora Debora E. Ervin Your Personal Travel Consultant/Coordinator C & C Unlimited Travel & Events 2288 Gunbarrel Road Suite 111-130 Chattanooga, TN 37421 Tel:(423)697-7775 Ext. 6003 Toll Free:(800)301-7299 Ext. 2 Fax:(423)622-8862 Visit our website at http://www.ccunltd.com Email: DErvin@ccunltd.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 18:20:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA25264 for ; Thu, 22 Oct 1998 18:20:26 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA18844; Thu, 22 Oct 1998 18:20:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA19903; Thu, 22 Oct 1998 18:17:50 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA34170 for ; Thu, 22 Oct 1998 18:16:32 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA21000 for ; Thu, 22 Oct 1998 18:16:31 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id VAA02897; Thu, 22 Oct 1998 21:16:33 -0400 (EDT) Message-Id: Date: Thu, 22 Oct 1998 21:16:33 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3A8JFXBJ6000OZS@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Debora Ervin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN man procmail man vacation On Thu, 22 Oct 1998, Debora Ervin wrote: > Hello, > > I need help. Is there any way that pine can allow you to automatically send > out mail when you receive mail. For example, if Im out of town and I want > my clients to know that I'm out of town and will respond to there email > when I return, by a reply messages being sent out automatically. > > Does anyone understand what I'm asking for? > > Thanks > Debora > Debora E. Ervin > Your Personal Travel Consultant/Coordinator > C & C Unlimited Travel & Events > 2288 Gunbarrel Road > Suite 111-130 > Chattanooga, TN 37421 > Tel:(423)697-7775 Ext. 6003 > Toll Free:(800)301-7299 Ext. 2 > Fax:(423)622-8862 > Visit our website at http://www.ccunltd.com > Email: DErvin@ccunltd.com > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 21:32:11 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA26655 for ; Thu, 22 Oct 1998 21:32:09 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA21386; Thu, 22 Oct 1998 21:32:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA16133; Thu, 22 Oct 1998 21:09:37 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA33550 for ; Thu, 22 Oct 1998 21:08:08 -0700 Received: from moose.uvm.edu (moose.uvm.edu [132.198.101.60]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA03734 for ; Thu, 22 Oct 1998 21:08:06 -0700 Received: from gnu.uvm.edu (gnu.uvm.edu [132.198.101.64]) by moose.uvm.edu (8.8.7/8.8.7) with ESMTP id AAA59840 for ; Fri, 23 Oct 1998 00:08:05 -0400 Received: from localhost (ashawley@localhost) by gnu.uvm.edu (8.8.7/8.8.7) with SMTP id AAA116724 for ; Fri, 23 Oct 1998 00:08:05 -0400 Message-Id: Date: Fri, 23 Oct 1998 00:08:05 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3A8JFXBJ6000OZS@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Authentication-Warning: gnu.uvm.edu: ashawley owned process doing -bs X-Sender: ashawley@gnu.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN haven't i heard this question once before? or maybe it's twelve times. Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley University of Vermont Home: Vergennes, VT, US Pine 3.96 E-Mailer on UVM Zoo Unix Cluster http://www.washington.edu/pine On Thu, 22 Oct 1998, Debora Ervin wrote: > Hello, > > I need help. Is there any way that pine can allow you to automatically send > out mail when you receive mail. For example, if Im out of town and I want > my clients to know that I'm out of town and will respond to there email > when I return, by a reply messages being sent out automatically. > > Does anyone understand what I'm asking for? > > Thanks > Debora > Debora E. Ervin > Your Personal Travel Consultant/Coordinator > C & C Unlimited Travel & Events > 2288 Gunbarrel Road > Suite 111-130 > Chattanooga, TN 37421 > Tel:(423)697-7775 Ext. 6003 > Toll Free:(800)301-7299 Ext. 2 > Fax:(423)622-8862 > Visit our website at http://www.ccunltd.com > Email: DErvin@ccunltd.com > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 21:47:14 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA26358 for ; Thu, 22 Oct 1998 21:47:10 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA21600; Thu, 22 Oct 1998 21:47:03 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA25537; Thu, 22 Oct 1998 21:45:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA38212 for ; Thu, 22 Oct 1998 21:44:05 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA06781 for ; Thu, 22 Oct 1998 21:44:04 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id AAA04054; Fri, 23 Oct 1998 00:44:08 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 00:44:08 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: guckes-flamewars@math.fu-berlin.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm stuck in a /really/ bad movie: "Attack of the way-too-fucking-long-sig-file!!" C'mon, ya bunch of losers. 4 lines. It's accepted. Be a dear, take all that useless info out. -- Ken Woods kwoodskens.com On Fri, 23 Oct 1998, Aaron S. Hawley wrote: (snip, bitch, bitch, bitch) > Aaron S. Hawley > ashawley@zoo.uvm.edu > 802.656.7396 > http://www.uvm.edu/~ashawley > University of Vermont > Home: Vergennes, VT, US > Pine 3.96 E-Mailer on UVM Zoo Unix Cluster > http://www.washington.edu/pine > > On Thu, 22 Oct 1998, Debora Ervin wrote: (snip, chick needs to man procmail) > > Debora E. Ervin > > Your Personal Travel Consultant/Coordinator > > C & C Unlimited Travel & Events > > 2288 Gunbarrel Road > > Suite 111-130 > > Chattanooga, TN 37421 > > Tel:(423)697-7775 Ext. 6003 > > Toll Free:(800)301-7299 Ext. 2 > > Fax:(423)622-8862 > > Visit our website at http://www.ccunltd.com > > Email: DErvin@ccunltd.com > > > > > > ----------------------------------------------------------------- > > For information about this mailing list, and its archives, see: > > http://www.washington.edu/pine/pine-info/ > > ----------------------------------------------------------------- > > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 21:50:36 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA27017 for ; Thu, 22 Oct 1998 21:50:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA21647; Thu, 22 Oct 1998 21:50:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA09217; Thu, 22 Oct 1998 21:49:10 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA22810 for ; Thu, 22 Oct 1998 21:47:49 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA07092 for ; Thu, 22 Oct 1998 21:47:49 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id AAA04119; Fri, 23 Oct 1998 00:47:53 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 00:47:53 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: guckes-flamewars@math.fu-berlin.de X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN And for christ's sake, sig-dashes. Love 'em, learn 'em, use them. On Fri, 23 Oct 1998, Ken Woods wrote: > > I'm stuck in a /really/ bad movie: > > "Attack of the way-too-fucking-long-sig-file!!" > > C'mon, ya bunch of losers. 4 lines. It's accepted. Be a dear, take all > that useless info out. > > -- > Ken Woods > kwoodskens.com > > On Fri, 23 Oct 1998, Aaron S. Hawley wrote: > > (snip, bitch, bitch, bitch) > > > Aaron S. Hawley > > ashawley@zoo.uvm.edu > > 802.656.7396 > > http://www.uvm.edu/~ashawley > > University of Vermont > > Home: Vergennes, VT, US > > Pine 3.96 E-Mailer on UVM Zoo Unix Cluster > > http://www.washington.edu/pine > > > > On Thu, 22 Oct 1998, Debora Ervin wrote: > > (snip, chick needs to man procmail) > > > > Debora E. Ervin > > > Your Personal Travel Consultant/Coordinator > > > C & C Unlimited Travel & Events > > > 2288 Gunbarrel Road > > > Suite 111-130 > > > Chattanooga, TN 37421 > > > Tel:(423)697-7775 Ext. 6003 > > > Toll Free:(800)301-7299 Ext. 2 > > > Fax:(423)622-8862 > > > Visit our website at http://www.ccunltd.com > > > Email: DErvin@ccunltd.com > > > > > > > > > ----------------------------------------------------------------- > > > For information about this mailing list, and its archives, see: > > > http://www.washington.edu/pine/pine-info/ > > > ----------------------------------------------------------------- > > > > > > > -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 22:32:06 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA27151 for ; Thu, 22 Oct 1998 22:32:02 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA22256; Thu, 22 Oct 1998 22:31:52 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA27153; Thu, 22 Oct 1998 22:29:50 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA37344 for ; Thu, 22 Oct 1998 22:28:20 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA16428 for ; Thu, 22 Oct 1998 22:28:17 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 23 Oct 1998 13:28:06 +0800 Message-Id: <001a01bdfe45$e2010c80$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 23 Oct 1998 13:27:53 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Ken Woods" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > And for christ's sake, sig-dashes. > Love 'em, learn 'em, use them. And, if you really want to get "picky", why not trim the useless fat out of your replies? :-) Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Thu, 22 Oct 1998 23:09:50 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA27529 for ; Thu, 22 Oct 1998 23:09:49 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA18430; Thu, 22 Oct 1998 23:09:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA19632; Thu, 22 Oct 1998 23:05:45 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA27310 for ; Thu, 22 Oct 1998 23:04:20 -0700 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA00437 for ; Thu, 22 Oct 1998 23:04:19 -0700 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id BAA26132 for ; Fri, 23 Oct 1998 01:04:17 -0500 Message-Id: Date: Fri, 23 Oct 1998 01:04:17 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <001a01bdfe45$e2010c80$1511b381@edspc17.twntpe.cdc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Ed Greshko >Date: Fri, 23 Oct 1998 13:27:53 +0800 >>And for christ's sake, sig-dashes. >>Love 'em, learn 'em, use them. >And, if you really want to get "picky", why not trim the useless fat out of >your replies? :-) As long as we are picking on each other, would all of you users of Microsoft products please mark your messages US-ASCII if you aren't sending any 8-bit characters? Or at least stop making Bill Gates rich till he complies with standards and best practices? Hm: New job? I didn't know you were an epidemiologist for the Centers for Disease Control? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 01:03:27 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA26875 for ; Fri, 23 Oct 1998 01:03:26 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA24039; Fri, 23 Oct 1998 01:03:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA14366; Fri, 23 Oct 1998 01:02:20 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA49628 for ; Fri, 23 Oct 1998 00:59:52 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA29251 for ; Fri, 23 Oct 1998 00:59:51 -0700 Received: from fireball.control-risks.de (port194.koeln.ndh.net [195.94.92.194]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id JAA13698 for ; Fri, 23 Oct 1998 09:59:47 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id KAA08241; Fri, 23 Oct 1998 10:00:09 +0200 Message-Id: <19981023100008.A7870@fireball.control-risks.de> Date: Fri, 23 Oct 1998 10:00:08 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: ; from Adam H. Kerman on Fri, Oct 23, 1998 at 01:04:17AM -0500 References: <001a01bdfe45$e2010c80$1511b381@edspc17.twntpe.cdc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Adam H. Kerman (ahk@chinet.chinet.com): Your reply string is too long. Luser. > >From: Ed Greshko > >>And for christ's sake, sig-dashes. Love 'em, learn 'em, use them. > > >And, if you really want to get "picky", why not trim the useless fat out of > >your replies? :-) > > As long as we are picking on each other, would all of you users of Microsoft > products please mark your messages US-ASCII if you aren't sending any 8-bit > characters? And the RFC for that would be? > Or at least stop making Bill Gates rich till he complies with > standards and best practices? How about making the NRA rich and solving the Gates problem once and for all? Ro"hahajustjoking"bin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 02:00:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA28000 for ; Fri, 23 Oct 1998 02:00:43 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA24776; Fri, 23 Oct 1998 02:00:31 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA22998; Fri, 23 Oct 1998 01:59:17 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA35602 for ; Fri, 23 Oct 1998 01:57:15 -0700 Received: from calvin.twntpe.cdc.com (ip129179-17-10.a.cdc.com [129.179.17.10]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA09590 for ; Fri, 23 Oct 1998 01:57:11 -0700 Received: from edspc17.twntpe.cdc.com by calvin.twntpe.cdc.com; Fri, 23 Oct 1998 16:57:00 +0800 Message-Id: <003c01bdfe63$109ffde0$1511b381@edspc17.twntpe.cdc.com> Date: Fri, 23 Oct 1998 16:56:47 +0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Ed Greshko" To: Pine Discussion Forum Subject: RE: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-To: "Adam H. Kerman" X-Cc: "Pine Discussion Forum" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Hm: New job? I didn't know you were an epidemiologist for the Centers for > Disease Control? You seem to be unaware of the usage of the Smiley Face ":-)" in an email message. That should clue you into the fact that my comment was not intended to pick on anyone. If it seemed that way to you, then I apologize. In any event, I was wrong. If someone has complaints or comments about an individual's style or email they should do it off-line and not on this or any other list. (Indeed, I am fully aware that I'm violating my on tenet with this message.) Also, common courtesy should tell people that yelling and swearing at others just isn't going to bring about the desired results. Neither will any kind of personal attacks. BTW, Robin is correct on the charset labeling issue. I will not respond to any additional messages concerning this "topic" on this list. So, please feel free to flame away and have the last word. Regards, Ed From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 03:01:54 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA22320 for ; Fri, 23 Oct 1998 03:01:50 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA20869; Fri, 23 Oct 1998 02:38:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA02382; Fri, 23 Oct 1998 02:36:49 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA30246 for ; Fri, 23 Oct 1998 02:34:55 -0700 Received: from nov.diac.com (diac.com [209.64.40.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA00519 for ; Fri, 23 Oct 1998 02:34:55 -0700 Received: from localhost (ekwall2@localhost) by nov.diac.com (8.8.8/8.8.8) with SMTP id JAA01587; Fri, 23 Oct 1998 09:34:21 GMT Message-Id: Date: Fri, 23 Oct 1998 03:34:21 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Ekwall To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023100008.A7870@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Sender: ekwall2@november X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Robin S. Socha wrote: -snip- Quoting Adam H. Kerman (ahk@chinet.chinet.com): Your reply string is too long. Luser. <-- is that Loser? german 2 english? (generic luu :) > >From: Ed Greshko -snip- > characters? And the RFC for that would be? > Or at least stop making Bill Gates rich till he complies with > standards and best practices? How about making the NRA rich and solving the Gates problem once and for all? Ro"hahajustjoking"bin -- Robin S. Socha ------------------------------ Hi Robin (nra might have use for the monie$ :) grin.. tried your www.kens.com/robin address, and we'd need a password, can I get one from you, If, Im _not_ an MS lover of bill gates and just recieved my first copy of redhat linux 5.0 (understood 5.1 is better)... send off line to avoid band-width and non-list clutter. thanks -=se=- steve ekwall mailto: ekwall2@diac.com p.s. another path to point me to if not?? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 04:29:25 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA01215 for ; Fri, 23 Oct 1998 04:29:23 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA26745; Fri, 23 Oct 1998 04:29:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA17031; Fri, 23 Oct 1998 04:27:34 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA41484 for ; Fri, 23 Oct 1998 04:25:39 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA27811 for ; Fri, 23 Oct 1998 04:25:38 -0700 Received: from fireball.control-risks.de (port254.koeln.ndh.net [195.94.92.254]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id NAA23820 for ; Fri, 23 Oct 1998 13:25:34 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id NAA10187; Fri, 23 Oct 1998 13:13:04 +0200 Message-Id: <19981023131303.A10086@fireball.control-risks.de> Date: Fri, 23 Oct 1998 13:13:03 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: ; from Steve Ekwall on Fri, Oct 23, 1998 at 03:34:21AM -0600 References: <19981023100008.A7870@fireball.control-risks.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Steve Ekwall (ekwall2@diac.com): > On Fri, 23 Oct 1998, Robin S. Socha wrote: >> Quoting Adam H. Kerman (ahk@chinet.chinet.com): >>>From: Ed Greshko DuDE, your mail was totally fscked up citationwise. I strongly recommend that thou readest thy fuckynge manual. >> Your reply string is too long. Luser. > ----- > is that Loser? german 2 english? (generic luu :) No, it's Korn Speak, ML-revised edition 5.3: luser /loo'zr/ /n./ A user; esp. one who is also a loser. This word was coined around 1975 at MIT. Under ITS, when you first walked up to a terminal at MIT and typed Control-Z to get the computer's attention, it printed out some status information, including how many people were already using the computer; it might print "14 users", for example. Someone thought it would be a great joke to patch the system to print "14 losers" instead. There ensued a great controversy, as some of the users didn't particularly want to be called losers to their faces every time they used the computer. For a while several hackers struggled covertly, each changing the message behind the back of the others; any time you logged into the computer it was even money whether it would say "users" or "losers". Finally, someone tried the compromise "lusers", and it stuck. Later one of the ITS machines supported luser as a request-for-help command. ITS died the death in mid-1990, except as a museum piece; the usage lives on, however, and the term `luser' is often seen in program comments. > tried your www.kens.com/robin address, and we'd need a password, can I > get one from you, Sure. It's to be found on . Or maybe you should try UID: "DeAHtiHS", Password: "BofH". > If, Im _not_ an MS lover of bill gates and just recieved my first copy of > redhat linux 5.0 (understood 5.1 is better)... 5.0? You should consider generously donating it to your local software museum (would look nice beside NT 5 and Win98). > send off line to avoid band-width and non-list clutter. Just like this mail, I presume? Great. I love this list. It's become just what we all dreamt of when we started whining "we want to disrupt the gateway to comp.mail.pine and have a list for complex technical problems" and the Pine Gods(tm) spoke unto us and said "yeah, right, here you go and stuff". > p.s. another path to point me to if not?? Sendero Luminoso? 42? Hell? Damn! It's FRIDAY again. Here's a tricky and probably pine-related question for my friends across the Atlantic: how come that you let loose an assorted collection of braindamaged power-lusers EACH AND EVERY FRIDAY? I mean, Friday sucks, anyway, so why make it even worse? *argl* Robin -- Robin S. Socha Cc: me and I'll chop your head off... From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 07:30:04 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA03869 for ; Fri, 23 Oct 1998 07:30:03 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA29831; Fri, 23 Oct 1998 07:29:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA07540; Fri, 23 Oct 1998 07:27:47 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA30342 for ; Fri, 23 Oct 1998 07:25:33 -0700 Received: from NiagaraNet.npiec.on.ca (NiagaraNet.npiec.on.ca [205.211.3.7]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25640 for ; Fri, 23 Oct 1998 07:25:32 -0700 Received: from nev.npiec.on.ca (nev.npiec.on.ca [205.211.3.2]) by NiagaraNet.npiec.on.ca (8.9.0/8.9.0) with ESMTP id KAA43922 for ; Fri, 23 Oct 1998 10:22:19 -0400 Received: from localhost (jwrussel@localhost) by nev.npiec.on.ca (8.9.0/8.9.0) with SMTP id KAA27650 for ; Fri, 23 Oct 1998 10:22:18 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 10:22:17 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "John Russell, VE3LL" To: Pine Discussion Forum Subject: signoff help MIME-Version: 1.0 Content-Type: MULTIPART/REPORT; REPORT-TYPE=delivery-status; BOUNDARY="KAA26903.909151781/nev.npiec.on.ca" Content-ID: X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --KAA26903.909151781/nev.npiec.on.ca Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: how do i unsub/signoff of this list. there is no closing banner with addresses of list-owner/cmd-proceesor/faq which would be more useful than today's traffic john VE3LL@RAC.CA --KAA26903.909151781/nev.npiec.on.ca-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 07:36:07 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA03820 for ; Fri, 23 Oct 1998 07:36:06 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA26062; Fri, 23 Oct 1998 07:36:00 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA20869; Fri, 23 Oct 1998 07:33:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA22746 for ; Fri, 23 Oct 1998 07:32:08 -0700 Received: from mailhost.cybermania.net.ma (root@[194.204.198.70]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA12245 for ; Fri, 23 Oct 1998 07:32:07 -0700 Received: from mailhost.cybermania.net.ma (tdaoud@mailhost.cybermania.net.ma [194.204.198.70]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id OAA32090; Fri, 23 Oct 1998 14:20:00 GMT Message-Id: Date: Fri, 23 Oct 1998 14:20:00 +0000 (WET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: Re: signoff help In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "John Russell, VE3LL" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, John Russell, VE3LL wrote: > how do i unsub/signoff of this list. To get more information on how to use this service, please send the command HELP in a line by itself in a mail message to listproc@u.washington.edu. To signoff from the list, email to listproc@u.washington.edu with the following request: signoff PINE-INFO or unsubscribe PINE-INFO Regards, _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:08:16 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA02544 for ; Fri, 23 Oct 1998 08:08:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA00659; Fri, 23 Oct 1998 08:08:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA14836; Fri, 23 Oct 1998 08:05:38 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA41622 for ; Fri, 23 Oct 1998 08:03:39 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA29601 for ; Fri, 23 Oct 1998 08:03:38 -0700 Received: from ccunltd.cdc.net (pm13-30.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3B37J9HS00011CA@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Fri, 23 Oct 1998 11:01:34 EST Message-Id: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> Date: Fri, 23 Oct 1998 11:08:56 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023131303.A10086@fireball.control-risks.de> References: <19981023100008.A7870@fireball.control-risks.de> MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: "Robin S. Socha" , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Look, I'm not sure what you guys are talking about in this discussion, but I'm sorry that it got tied up in my question. I'm new to this discussion group and I sorry if I offended someone by asking a questions that has been asked several times before. I thought this was the place to come if you had questions about using pine, which I'm very new to as well, and would like to use this program in a productive manner. I would like to Thank you Greg for all your help and patience with me. Also, all the others who where so helpful. And Aaron thank you for making the new people feel so welcome...... Debora From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:11:47 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA31279 for ; Fri, 23 Oct 1998 08:11:45 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA26813; Fri, 23 Oct 1998 08:11:38 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA15115; Fri, 23 Oct 1998 08:09:21 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA61640 for ; Fri, 23 Oct 1998 08:07:19 -0700 Received: from mailhost.cybermania.net.ma (root@[194.204.198.70]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA11620 for ; Fri, 23 Oct 1998 08:07:18 -0700 Received: from RESERVED02.cybermania.net.ma (RESERVED02.cybermania.net.ma [194.204.198.92]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id OAA32183; Fri, 23 Oct 1998 14:55:35 GMT Message-Id: Date: Fri, 23 Oct 1998 15:06:45 +0000 (Greenwich) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: Re: signoff help In-Reply-To: <001501bdfe93$af061160$1e09f4cf@ccunltd.cdc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: C & C Unlimited Travel & Events X-X-Sender: tdaoud@mailhost.cybermania.net.ma X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I thought contributing in Pine info list should help people in promoting their knowledge in using the Pine mailing software. But to exchange ads whenever a contribution is made (such as the one I received below), let me think of how major-domo or whatever mailing lists software, the pine developers are using, could stop this unsolicited activities?!? May be someone should sit behind the wheel and try to filter those emails or may be excluding mails having such big words like SPECIALS .. RESERVATION .. etc -Tawfik On Fri, 23 Oct 1998, C & C Unlimited Travel & Events wrote: > Hello, > > C&C Unlimited Travel & Events has received your recent email. > Thank you. We will handle your request accordingly. > > Visit our website: http://www.ccunltd.com > > *********************** > SPECIALS > *********************** > > CARNIVAL FunShip > "Winter Sale" > 2-for-1 > 3, 4, and 7 day cruises > Rates From Only $299 (Including port charges) > > Make Your Reservations Today!@ > > Debora Ervin > C&C Unlimited Travel & Events > 2288 Gunbarrel Road > Suite 111-130 > Chattanooga, TN 37421 > Toll Free: (800)301-7299 EX. 2 > Local: (423)697-7775 EX. 6003 > Fax: (423)622-8862 > Website: http://www.ccunltd.com > > "Your Personal Consultants to the World" > > _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:23:34 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA01827 for ; Fri, 23 Oct 1998 08:23:33 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA27120; Fri, 23 Oct 1998 08:23:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA10374; Fri, 23 Oct 1998 08:21:05 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA37298 for ; Fri, 23 Oct 1998 08:19:18 -0700 Received: from gluon.zag.si (gluon.zag.si [193.2.24.5]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA31414 for ; Fri, 23 Oct 1998 08:19:16 -0700 Received: from Charm.sckcen.be (Charm.sckcen.be [193.190.184.5]) by gluon.zag.si (8.8.6/8.8.6) with ESMTP id RAA02615 for ; Fri, 23 Oct 1998 17:19:12 +0200 (CEST) Message-Id: Date: Fri, 23 Oct 1998 17:17:54 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jan Kalin To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: jank@charm.sckcen.be X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Debora Ervin wrote: > Look, I'm not sure what you guys are talking about in this discussion, but > I'm sorry that it got tied up in my question. I'm new to this discussion > group and I sorry if I offended someone by asking a questions that has been > asked several times before. I thought this was the place to come if you had > questions about using pine, which I'm very new to as well, and would like > to use this program in a productive manner. > > I would like to Thank you Greg for all your help and patience with me. > Also, all the others who where so helpful. > > And Aaron thank you for making the new people feel so welcome...... > > Debora > I have an idea how we could reduce the chance of repeated questions. I don't remember exactly (it was some time ago) but when you register yourself in the pine-info mailing list you get a confirmation letter, right? Why not put the FAQ into the letter. Maybe not the whole FAQ, just the RFAQ (Really FAQ :) on this list, i.e., the ones that prompt 'Oh no, not again!' reactions. Cheers, Jan -- Jan Kalin (male, preferred languages: Slovene, English) contact information From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:24:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA04465 for ; Fri, 23 Oct 1998 08:24:44 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA01071; Fri, 23 Oct 1998 08:24:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA23377; Fri, 23 Oct 1998 08:22:52 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA36504 for ; Fri, 23 Oct 1998 08:20:45 -0700 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA19775 for ; Fri, 23 Oct 1998 08:20:45 -0700 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRNZ85>; Fri, 23 Oct 1998 11:24:41 -0400 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394FA9@POISON> Date: Fri, 23 Oct 1998 11:24:37 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: signoff help MIME-Version: 1.0 Content-Type: text/plain X-To: "'Tawfik Daoud'" X-Cc: "'Pine List'" X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I think the problem here is: Tawfik responded to someone else and that response also went to all on the list, which unfortunatly one of the list recipients is auto responding to the sender and thus is the reason why no one else would have received the "ad". Possibly solution would be that in order to remain on the list, to not have an auto responder on your email, unless it's an "out of office" type response George Gallen ggallen@slackinc.com -----Original Message----- From: Tawfik Daoud [mailto:tdaoud@cybermania.net.ma] Sent: Friday, October 23, 1998 11:07 AM To: Pine Discussion Forum Subject: Re: signoff help I thought contributing in Pine info list should help people in promoting their knowledge in using the Pine mailing software. But to exchange ads whenever a contribution is made (such as the one I received below), let me think of how major-domo or whatever mailing lists software, the pine developers are using, could stop this unsolicited activities?!? May be someone should sit behind the wheel and try to filter those emails or may be excluding mails having such big words like SPECIALS .. RESERVATION .. etc -Tawfik On Fri, 23 Oct 1998, C & C Unlimited Travel & Events wrote: > Hello, > > C&C Unlimited Travel & Events has received your recent email. > Thank you. We will handle your request accordingly. > > Visit our website: http://www.ccunltd.com > > *********************** > SPECIALS > *********************** > > CARNIVAL FunShip > "Winter Sale" > 2-for-1 > 3, 4, and 7 day cruises > Rates From Only $299 (Including port charges) > > Make Your Reservations Today!@ > > Debora Ervin > C&C Unlimited Travel & Events > 2288 Gunbarrel Road > Suite 111-130 > Chattanooga, TN 37421 > Toll Free: (800)301-7299 EX. 2 > Local: (423)697-7775 EX. 6003 > Fax: (423)622-8862 > Website: http://www.ccunltd.com > > "Your Personal Consultants to the World" > > _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:39:22 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA00245 for ; Fri, 23 Oct 1998 08:39:21 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA27554; Fri, 23 Oct 1998 08:39:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA02344; Fri, 23 Oct 1998 08:37:04 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA36414 for ; Fri, 23 Oct 1998 08:35:10 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA19136 for ; Fri, 23 Oct 1998 08:35:09 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id JAA06079 for ; Fri, 23 Oct 1998 09:35:08 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id JAA22720 for ; Fri, 23 Oct 1998 09:32:23 -0600 (MDT) Message-Id: Date: Fri, 23 Oct 1998 09:28:08 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: signoff help In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Tawfik Daoud wrote: > their knowledge in using the Pine mailing software. But to exchange ads > whenever a contribution is made (such as the one I received below), let me [Spam Snipped] Ummm... That didn't go to the list. You got that from some other source. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 08:44:47 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA04837 for ; Fri, 23 Oct 1998 08:44:46 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA01589; Fri, 23 Oct 1998 08:44:40 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA11655; Fri, 23 Oct 1998 08:41:32 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA45174 for ; Fri, 23 Oct 1998 08:39:53 -0700 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA22123 for ; Fri, 23 Oct 1998 08:39:53 -0700 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id JAA06686 for ; Fri, 23 Oct 1998 09:39:52 -0600 (MDT) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id JAA24736 for ; Fri, 23 Oct 1998 09:37:07 -0600 (MDT) Message-Id: Date: Fri, 23 Oct 1998 09:32:53 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: RE: signoff help In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055394FA9@POISON> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, George Gallen wrote: > Possibly solution would be that in order to remain > on the list, to not have an auto responder on your > email, unless it's an "out of office" type response I personally want to brutally bludgeon people that have autoresponders on when they go away for extended periods of time. I subscribe to many lists, and I must get 3 or 4 "Out of Office" messages ON LISTS every week. There is a very simple solution to that: 1) Sign off the list for the duration of your absence. Firstly, the list won't be nailed with a "I'm on vacation" message every time someone posts to it, and secondly, your inbox won't be so cluttered when you get back. 2) DON'T USE AN AUTORESPONDER. Most likely the people that send you important mail ALREADY KNOW that you're not there and won't try to email you. You can pretty much dismiss the rest of the mail you get as unimportant. Send it to /dev/null. Stuff like "there's a meeting today" isn't really pertinent to you while you're away, is it? My $0.02. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:16:08 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA05648 for ; Fri, 23 Oct 1998 09:16:06 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02557; Fri, 23 Oct 1998 09:15:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA19228; Fri, 23 Oct 1998 09:14:23 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA51978 for ; Fri, 23 Oct 1998 09:11:14 -0700 Received: from acacia.datacomm.com (ted@acacia.datacomm.com [205.147.65.193]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA26507 for ; Fri, 23 Oct 1998 09:11:13 -0700 Received: from localhost (ted@localhost) by acacia.datacomm.com (8.9.0/8.9.0) with ESMTP id JAA17333; Fri, 23 Oct 1998 09:05:49 -0700 Message-Id: Date: Fri, 23 Oct 1998 09:05:48 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ted Rolle To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Debora Ervin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Right on, Deb! We're an ego-centric bunch, aren't we? To suppose that you know what's been asked before. We get that way from living in our parent's basements and watching Star Trek reruns. On Fri, 23 Oct 1998, Debora Ervin wrote: > group and I sorry if I offended someone by asking a questions that has been From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:19:18 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29316 for ; Fri, 23 Oct 1998 09:19:17 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02670; Fri, 23 Oct 1998 09:19:05 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA14193; Fri, 23 Oct 1998 09:17:39 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA59924 for ; Fri, 23 Oct 1998 09:15:56 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA20462 for ; Fri, 23 Oct 1998 09:15:55 -0700 Received: from fireball.control-risks.de (port254.koeln.ndh.net [195.94.92.254]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id SAA29037 for ; Fri, 23 Oct 1998 18:15:52 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id SAA12542; Fri, 23 Oct 1998 18:15:36 +0200 Message-Id: <19981023181536.C12465@fireball.control-risks.de> Date: Fri, 23 Oct 1998 18:15:36 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: ; from Jan Kalin on Fri, Oct 23, 1998 at 05:17:54PM +0200 References: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Jan Kalin (jan.kalin@zag.si): > On Fri, 23 Oct 1998, Debora Ervin wrote: (endless miles of quotes) > I have an idea how we could reduce the chance of repeated questions. I > don't remember exactly (it was some time ago) but when you register > yourself in the pine-info mailing list you get a confirmation letter, > right? You're pretty clever... > Why not put the FAQ into the letter. Groovy. May I suggest adding the sources for XFree 3. They are quite entertaining on long winter nights. > Maybe not the whole FAQ, just the RFAQ (Really FAQ :) on this list, i.e., > the ones that prompt 'Oh no, not again!' reactions. Let me think... ummm... yeah! Great idea. Too bad you never read that first letter you were sent, isn't it? -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:22:26 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA10467 for ; Fri, 23 Oct 1998 09:22:24 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02756; Fri, 23 Oct 1998 09:22:14 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA05230; Fri, 23 Oct 1998 09:19:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA61474 for ; Fri, 23 Oct 1998 09:15:58 -0700 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA27247 for ; Fri, 23 Oct 1998 09:15:57 -0700 Received: from fireball.control-risks.de (port254.koeln.ndh.net [195.94.92.254]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id SAA29049 for ; Fri, 23 Oct 1998 18:15:53 +0200 (MET DST) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id SAA12537; Fri, 23 Oct 1998 18:09:26 +0200 Message-Id: <19981023180926.B12465@fireball.control-risks.de> Date: Fri, 23 Oct 1998 18:09:26 +0200 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US>; from Debora Ervin on Fri, Oct 23, 1998 at 11:08:56AM -0400 References: <19981023100008.A7870@fireball.control-risks.de> <19981023131303.A10086@fireball.control-risks.de> <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Debora Ervin (DErvin@ccunltd.com): > Look, I'm not sure what you guys are talking about in this discussion, Technical, you know, stuff and, like, netiquette and maybe even, ummm... pine? > but I'm sorry that it got tied up in my question. Ok. > I'm new to this discussion group It's a mailing list. What is commonly referred to by Wintendo lusers as a "discussion group" is actually the usenet newsgrop . Some time ago, it was agreed upon that this mailing list be the place for technical questions (of which yours is none at all). > and I sorry if I offended someone by asking a questions that has been asked > several times before. Nice try, but *we* have got used to this move over the years. The correct statement would have been: "I've read the Q&A, the users guide and some of the technical notes. Then I got myself Nancy McGough's filtering mail FAQ thankyouverymuch". See the difference? > I thought this was the place to come if you had questions about using pine, > which I'm very new to as well, and would like to use this program in a > productive manner. Good idea. Grab a copy of the documentation (which is good and easy to understand and *very* clear re: your "question") and you're halfway there. > And Aaron thank you for making the new people feel so welcome...... s/Aaron/Ken/g Ro"itsfridayagain..."bin -- Robin S. Socha I said DON'T FSCKING Cc: ME... From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:24:17 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA05149 for ; Fri, 23 Oct 1998 09:24:16 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02827; Fri, 23 Oct 1998 09:24:09 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA05412; Fri, 23 Oct 1998 09:22:42 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA61560 for ; Fri, 23 Oct 1998 09:20:47 -0700 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA21015 for ; Fri, 23 Oct 1998 09:20:46 -0700 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id LAA00461 for ; Fri, 23 Oct 1998 11:20:44 -0500 Message-Id: Date: Fri, 23 Oct 1998 11:20:44 -0500 (CDT) Reply-To: "Adam H. Kerman" Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023100008.A7870@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Robin S. Socha" >Date: Fri, 23 Oct 1998 10:00:08 +0200 >Quoting Adam H. Kerman (ahk@chinet.chinet.com): >Your reply string is too long. Luser. Phbbbbt. I like my reply string; people should include dates. >>As long as we are picking on each other, would all of you users of Microsoft >>products please mark your messages US-ASCII if you aren't sending any 8-bit >>characters? >And the RFC for that would be? It would be a "best practices" to indicate that a message contains no 8-bit characters when it really doesn't have any 8-bit characters. It's a concept like, oh, use of 2 dashes/blank to delimit a .sig. I can't believe you would defend Bill Gates. >>Or at least stop making Bill Gates rich till he complies with standards and >>best practices? >How about making the NRA rich and solving the Gates problem once and for all? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:35:57 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA06230 for ; Fri, 23 Oct 1998 09:35:56 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03180; Fri, 23 Oct 1998 09:35:44 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA15050; Fri, 23 Oct 1998 09:33:28 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA49528 for ; Fri, 23 Oct 1998 09:31:41 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29716 for ; Fri, 23 Oct 1998 09:31:40 -0700 Received: from ccunltd.cdc.net (pm13-30.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3B6B1U2DS0015MW@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Fri, 23 Oct 1998 12:29:35 EST Message-Id: <01J3B6B3E5C20015MW@CSTCC.CC.TN.US> Date: Fri, 23 Oct 1998 12:37:18 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023180926.B12465@fireball.control-risks.de> References: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: "Robin S. Socha" , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks Robin for all the valuable information. Man, u tech guys are way over my head. What Such Smart people u r. I'm very impressed Robin, but then again Im easily impressed, so that's not a big deal. This discussion forum....was listed as a pine discussion group...(which to me means, discussion about pine, thats anything about pine). I could wrong, be I dont remember seeing a statement saying, (new users not allowed). But again....thanks for that information....I'm beginning to like this group after all. Debora At 06:09 PM 10/23/98 +0200, Robin S. Socha wrote: >Quoting Debora Ervin (DErvin@ccunltd.com): > >> Look, I'm not sure what you guys are talking about in this discussion, > >Technical, you know, stuff and, like, netiquette and maybe even, ummm... pine? > >> but I'm sorry that it got tied up in my question. > >Ok. > >> I'm new to this discussion group > >It's a mailing list. What is commonly referred to by Wintendo lusers as a >"discussion group" is actually the usenet newsgrop . Some >time ago, it was agreed upon that this mailing list be the place for technical >questions (of which yours is none at all). > >> and I sorry if I offended someone by asking a questions that has been asked >> several times before. > >Nice try, but *we* have got used to this move over the years. The correct >statement would have been: "I've read the Q&A, the users guide and some of the >technical notes. Then I got myself Nancy McGough's filtering mail FAQ >thankyouverymuch". See the difference? > >> I thought this was the place to come if you had questions about using pine, >> which I'm very new to as well, and would like to use this program in a >> productive manner. > >Good idea. Grab a copy of the documentation (which is good and easy to >understand and *very* clear re: your "question") and you're halfway there. > >> And Aaron thank you for making the new people feel so welcome...... > >s/Aaron/Ken/g > >Ro"itsfridayagain..."bin > >-- >Robin S. Socha > >I said DON'T FSCKING Cc: ME... > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:42:12 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA06749 for ; Fri, 23 Oct 1998 09:42:10 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29561; Fri, 23 Oct 1998 09:42:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA06449; Fri, 23 Oct 1998 09:39:49 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA37284 for ; Fri, 23 Oct 1998 09:37:46 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA27162 for ; Fri, 23 Oct 1998 09:37:40 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.E1F6B500@smtpgate.uvm.edu>; Fri, 23 Oct 1998 12:37:23 -0400 Message-Id: Date: Fri, 23 Oct 1998 12:37:26 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Debora Ervin X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Look, I'm not sure what you guys are talking about in this discussion, but > I'm sorry that it got tied up in my question. I'm new to this discussion > group and I sorry if I offended someone by asking a questions that has been > asked several times before. I thought this was the place to come if you had > questions about using pine, which I'm very new to as well, and would like > to use this program in a productive manner. they also put information on the web with common and old questions about using pine. > I would like to Thank you Greg for all your help and patience with me. > Also, all the others who where so helpful. > > And Aaron thank you for making the new people feel so welcome...... > > Debora what i really don't get is why is it that you wanted to know how to automatic reply, but when i sent a message to you (or the discussion list did) your company sent an automatic reply. oh well love ya aaron From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:44:20 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA06053 for ; Fri, 23 Oct 1998 09:44:18 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03392; Fri, 23 Oct 1998 09:44:02 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA28672; Fri, 23 Oct 1998 09:42:35 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA60104 for ; Fri, 23 Oct 1998 09:40:31 -0700 Received: from gw.learjet.com (firewall-user@gw.learjet.com [192.206.89.4]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA31059 for ; Fri, 23 Oct 1998 09:40:28 -0700 Received: by gw.learjet.com; id LAA10355; Fri, 23 Oct 1998 11:40:27 -0500 (CDT) Received: from hs8.learjet.com(172.18.126.238) by gw.learjet.com via smap (4.1) id xma010322; Fri, 23 Oct 98 11:39:55 -0500 Received: from unknown (hx02.learjet.com [172.18.126.91]) by hs8.learjet.com (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id LAA13888 for ; Fri, 23 Oct 1998 11:39:54 -0500 (CDT) Received: from localhost by unknown (1.37.109.20) id AA126730793; Fri, 23 Oct 1998 11:39:53 -0500 Message-Id: Date: Fri, 23 Oct 1998 11:39:53 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Info List X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Adam H. Kerman wrote: > Phbbbbt. I like my reply string; people should include dates. Speaking of reply strings, is there a way to customize them in Pine? I didn't see it in 'Main - Setup - Config', or the "Pine Questions and Answers", or the "Pine Technical Notes" on the uwashington server. What I'm looking for is something like some news readers have where you can have Pine quote a string at the beginning of replies, such as: On , pounded furiously at the keyboard, thus producing: . I'm using version 3.94. ---- Jeff Schaller schaller@learjet.com UNIX System Administrator Phone: (316) 946-7255 Learjet Inc Fax: (316) 946-2809 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:46:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA04389 for ; Fri, 23 Oct 1998 09:46:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29723; Fri, 23 Oct 1998 09:46:36 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA15792; Fri, 23 Oct 1998 09:44:25 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA45864 for ; Fri, 23 Oct 1998 09:41:09 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA31174 for ; Fri, 23 Oct 1998 09:41:08 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.67C29190@smtpgate.uvm.edu>; Fri, 23 Oct 1998 12:41:07 -0400 Message-Id: Date: Fri, 23 Oct 1998 12:41:11 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: RE: signoff help In-Reply-To: <0089B6FA4F0DD211AD4E0001FA7E5055394FA9@POISON> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > I think the problem here is: > > Tawfik responded to someone else and that response > also went to all on the list, which unfortunatly > one of the list recipients is auto responding to > the sender and thus is the reason why no one else > would have received the "ad". > > Possibly solution would be that in order to remain > on the list, to not have an auto responder on your > email, unless it's an "out of office" type response > > George Gallen > ggallen@slackinc.com the greatest part i must add again is that the person sending the ad, witht he auto responder, wants to know how to use an autoresponder when she goes on vacation. i think the word here is irony. aaron again From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:52:03 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA28014 for ; Fri, 23 Oct 1998 09:52:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03762; Fri, 23 Oct 1998 09:51:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA21567; Fri, 23 Oct 1998 09:49:19 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA37282 for ; Fri, 23 Oct 1998 09:46:37 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA24665 for ; Fri, 23 Oct 1998 09:46:36 -0700 Received: from ccunltd.cdc.net (pm13-30.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3B6TK9SBK001B1X@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Fri, 23 Oct 1998 12:44:29 EST Message-Id: <01J3B6TLCD02001B1X@CSTCC.CC.TN.US> Date: Fri, 23 Oct 1998 12:52:14 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: References: <01J3B380AUAQ0011CA@CSTCC.CC.TN.US> MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: "Aaron S. Hawley" , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Well Aaron, for your information, I was using Outlook Express, but my system is not up 24 hours to download my email into outlook express, so that the auto reply would work. But as you know already, if I had it in pine, where my email actual is sent, then I would not have to worry about downloading it, in order for the auto reply to work. Does that clear up confusion for you? At 12:37 PM 10/23/98 -0400, Aaron S. Hawley wrote: > >> Look, I'm not sure what you guys are talking about in this discussion, but >> I'm sorry that it got tied up in my question. I'm new to this discussion >> group and I sorry if I offended someone by asking a questions that has been >> asked several times before. I thought this was the place to come if you had >> questions about using pine, which I'm very new to as well, and would like >> to use this program in a productive manner. > >they also put information on the web with common and old questions about >using pine. > >> I would like to Thank you Greg for all your help and patience with me. >> Also, all the others who where so helpful. >> >> And Aaron thank you for making the new people feel so welcome...... >> >> Debora > >what i really don't get is why is it that you wanted to know how to >automatic reply, but when i sent a message to you (or the discussion list >did) your company sent an automatic reply. > >oh well > >love ya >aaron > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 09:56:41 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA31181 for ; Fri, 23 Oct 1998 09:56:39 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03907; Fri, 23 Oct 1998 09:56:33 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA07567; Fri, 23 Oct 1998 09:54:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA60052 for ; Fri, 23 Oct 1998 09:52:45 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29778 for ; Fri, 23 Oct 1998 09:52:44 -0700 Received: from ccunltd.cdc.net (pm13-30.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3B70X847K0014SI@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Fri, 23 Oct 1998 12:50:34 EST Message-Id: <01J3B70Y7QYA0014SI@CSTCC.CC.TN.US> Date: Fri, 23 Oct 1998 12:58:11 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: RE: signoff help In-Reply-To: References: <0089B6FA4F0DD211AD4E0001FA7E5055394FA9@POISON> MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: "Aaron S. Hawley" , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Actually Aaron vacation is not what I was going to use the auto responder for, if you must know. I want to automatically respond to my clients only. This is why I was looking for a program that I could setup just to sent out to certain people and not to email one who sends me email.....as it seems to do at this time. As a business person, I like to use my resources wisely. And you guys are great....now where are these faq that everyone is talking about? Debora At 12:41 PM 10/23/98 -0400, Aaron S. Hawley wrote: >> I think the problem here is: >> >> Tawfik responded to someone else and that response >> also went to all on the list, which unfortunatly >> one of the list recipients is auto responding to >> the sender and thus is the reason why no one else >> would have received the "ad". >> >> Possibly solution would be that in order to remain >> on the list, to not have an auto responder on your >> email, unless it's an "out of office" type response >> >> George Gallen >> ggallen@slackinc.com > >the greatest part i must add again is that the person sending the ad, >witht he auto responder, wants to know how to use an autoresponder when >she goes on vacation. i think the word here is irony. > >aaron > >again > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:01:07 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA05657 for ; Fri, 23 Oct 1998 10:01:05 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03990; Fri, 23 Oct 1998 09:59:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA29855; Fri, 23 Oct 1998 09:58:13 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA22942 for ; Fri, 23 Oct 1998 09:56:32 -0700 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA25936 for ; Fri, 23 Oct 1998 09:56:31 -0700 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id LAA00983 for ; Fri, 23 Oct 1998 11:56:30 -0500 Message-Id: Date: Fri, 23 Oct 1998 11:56:30 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B6B3E5C20015MW@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Debora Ervin >Date: Fri, 23 Oct 1998 12:37:18 -0400 >This discussion forum....was listed as a pine discussion group...(which to >me means, discussion about pine, thats anything about pine). I could wrong, >be I dont remember seeing a statement saying, (new users not allowed). New users are most welcome. Discussion about pine is most welcome. But questions that are asked repeatedly are not. They drive out the discussion. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:08:19 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA32229 for ; Fri, 23 Oct 1998 10:08:18 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA04262; Fri, 23 Oct 1998 10:08:11 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA23118; Fri, 23 Oct 1998 10:05:34 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA36460 for ; Fri, 23 Oct 1998 10:03:14 -0700 Received: from mailhost.cybermania.net.ma ([194.204.198.70]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA12751 for ; Fri, 23 Oct 1998 10:02:03 -0700 Received: from RESERVED02.cybermania.net.ma (RESERVED02.cybermania.net.ma [194.204.198.92]) by mailhost.cybermania.net.ma (8.8.4/8.8.4) with ESMTP id QAA32546; Fri, 23 Oct 1998 16:50:07 GMT Message-Id: Date: Fri, 23 Oct 1998 17:01:18 +0000 (Greenwich) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Tawfik Daoud To: Pine Discussion Forum Subject: Re: signoff help In-Reply-To: <01J3B3VD3U8I0012W5@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Cc: Debora Ervin X-X-Sender: tdaoud@mailhost.cybermania.net.ma X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Debora, I am including your message below for clarification. Regards, On Fri, 23 Oct 1998, Debora Ervin wrote: > Hello Tawfik, > > Let me apologize for that advertisement. I'm using Outlook Express auto > reply and was unaware that it was sending replies to every email I receive. > I thought I had it setup to reply to only me clients. I have disabled this > feature, so it should not happen again. > > Again I apologize. > Debora > Debora E. Ervin _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:24:02 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA07060 for ; Fri, 23 Oct 1998 10:24:01 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA01086; Fri, 23 Oct 1998 10:23:54 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA24177; Fri, 23 Oct 1998 10:22:12 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA39738 for ; Fri, 23 Oct 1998 10:19:49 -0700 Received: from moose.uvm.edu (moose.uvm.edu [132.198.101.60]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA15354 for ; Fri, 23 Oct 1998 10:19:48 -0700 Received: from elk.uvm.edu (elk.uvm.edu [132.198.101.63]) by moose.uvm.edu (8.8.7/8.8.7) with ESMTP id NAA37486 for ; Fri, 23 Oct 1998 13:19:47 -0400 Received: from localhost (ashawley@localhost) by elk.uvm.edu (8.8.7/8.8.7) with SMTP id NAA98430 for ; Fri, 23 Oct 1998 13:19:46 -0400 Message-Id: Date: Fri, 23 Oct 1998 13:19:46 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: RE: signoff help In-Reply-To: <01J3B70Y7QYA0014SI@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Authentication-Warning: elk.uvm.edu: ashawley owned process doing -bs X-Sender: ashawley@elk.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN here's the faq deb http://www.washington.edu/pine/faq/ Aaron S. Hawley ashawley@zoo.uvm.edu 802.656.7396 http://www.uvm.edu/~ashawley Vergennes, VT, US Pine 3.96 E-Mailer on UVM Zoo Unix Cluster http://www.washington.edu/pine On Fri, 23 Oct 1998, Debora Ervin wrote: > Actually Aaron vacation is not what I was going to use the auto responder > for, if you must know. I want to automatically respond to my clients only. > This is why I was looking for a program that I could setup just to sent out > to certain people and not to email one who sends me email.....as it seems > to do at this time. As a business person, I like to use my resources > wisely. And you guys are great....now where are these faq that everyone is > talking about? > > Debora > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:30:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03421 for ; Fri, 23 Oct 1998 10:30:57 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA01275; Fri, 23 Oct 1998 10:30:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA19426; Fri, 23 Oct 1998 10:28:36 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA13402 for ; Fri, 23 Oct 1998 10:26:45 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA16662 for ; Fri, 23 Oct 1998 10:26:45 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id NAA07919 for ; Fri, 23 Oct 1998 13:26:47 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 13:26:47 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023180926.B12465@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Robin S. Socha wrote: > Debra "I'mtoocluelesstoman" wrote: > > And Aaron thank you for making the new people feel so welcome...... > s/Aaron/Ken/g Exactly. It's too bad the lusers don't read (ie, understand) what I write. -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:44:01 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA05744 for ; Fri, 23 Oct 1998 10:44:00 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA05163; Fri, 23 Oct 1998 10:43:53 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA03333; Fri, 23 Oct 1998 10:41:59 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA52192 for ; Fri, 23 Oct 1998 10:37:57 -0700 Received: from nimbus.anzio.com (ras@nimbus.anzio.com [204.201.253.34]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA32245 for ; Fri, 23 Oct 1998 10:37:56 -0700 Received: from localhost (ras@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id KAA13606 for ; Fri, 23 Oct 1998 10:37:43 -0700 Message-Id: Date: Fri, 23 Oct 1998 10:37:41 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bob Rasmussen To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Ken Woods wrote: > On Fri, 23 Oct 1998, Robin S. Socha wrote: > > Debra "I'mtoocluelesstoman" wrote: > > > And Aaron thank you for making the new people feel so welcome...... > > s/Aaron/Ken/g > > Exactly. > > It's too bad the lusers don't read (ie, understand) what I write. Or maybe you are too clueless to detect sarcasm. What? Flamers lacking in social skills? Couldn't be! (sarcasm) Regards, ....Bob Rasmussen, President, Rasmussen Software, Inc. personal e-mail: ras@anzio.com company e-mail: rsi@anzio.com or sales@anzio.com or support@anzio.com ftp://ftp.anzio.com voice: 503-624-0360 http://www.anzio.com fax: 503-624-0760 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 10:57:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA07548 for ; Fri, 23 Oct 1998 10:57:25 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02011; Fri, 23 Oct 1998 10:57:18 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA26575; Fri, 23 Oct 1998 10:55:54 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA46456 for ; Fri, 23 Oct 1998 10:52:14 -0700 Received: from acacia.datacomm.com (ted@acacia.datacomm.com [205.147.65.193]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA05213 for ; Fri, 23 Oct 1998 10:52:12 -0700 Received: from localhost (ted@localhost) by acacia.datacomm.com (8.9.0/8.9.0) with ESMTP id KAA17517; Fri, 23 Oct 1998 10:46:17 -0700 Message-Id: Date: Fri, 23 Oct 1998 10:46:16 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ted Rolle To: Pine Discussion Forum Subject: RE: signoff help In-Reply-To: <01J3B70Y7QYA0014SI@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Debora Ervin X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > for, if you must know. I want to automatically respond to my clients only. Are you using PC-pine? Under unix 'procmail' and/or/ 'sendmail' might do the trick. But they are not for the faint-of-heart. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 11:12:22 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA01305 for ; Fri, 23 Oct 1998 11:12:21 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA05943; Fri, 23 Oct 1998 11:12:15 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA22034; Fri, 23 Oct 1998 11:10:35 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA44592 for ; Fri, 23 Oct 1998 11:06:49 -0700 Received: from mailhost1.u.washington.edu (mailhost1.u.washington.edu [140.142.32.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA22954 for ; Fri, 23 Oct 1998 11:06:47 -0700 Received: from D-128-95-135-197.dhcp.washington.edu (D-128-95-135-197.dhcp.washington.edu [128.95.135.197]) by mailhost1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA16747 for ; Fri, 23 Oct 1998 11:06:45 -0700 Message-Id: Date: Fri, 23 Oct 1998 11:06:44 -0700 (PDT) Reply-To: kanelson@cac.washington.edu Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kris Nelson To: Pine Discussion Forum Subject: Pointer to the Pine FAQ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: kanelson@shivams.cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN The (official) Pine FAQ (i.e., list of Frequently Asked Questions), containing many tips and solutions, is available at the following URL: http://www.washington.edu/pine/faq Please read through it before writing to the pine-info mailing list or posting to comp.mail.pine, in case your question has already been answered. Remember as well that help on unsubscribing, etc. from pine-info is available by writing to listproc@u.washington.edu with HELP in the message text. Also, keep in mind that the Pine Information Center contains quite a bit of other useful information besides just the FAQ, such as current versions of Pine and PC-Pine. The URL is: http://www.washington.edu/pine (Keep in mind before asking us for help that the Pine Team receives no funding to provide support beyond the University of Washington. Other Pine users and your local computer support staff are your best resources.) Regards, Kris -- Kristopher Nelson -- kanelson@cac.washington.edu University of Washington -- Computing & Communications ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 11:23:17 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA03466 for ; Fri, 23 Oct 1998 11:23:15 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA02877; Fri, 23 Oct 1998 11:22:59 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA27835; Fri, 23 Oct 1998 11:21:23 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA59930 for ; Fri, 23 Oct 1998 11:17:42 -0700 Received: from grover.en.com (grover.en.com [204.89.181.10]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA12541 for ; Fri, 23 Oct 1998 11:17:41 -0700 Received: from bigbird (awyeah@bigbird [204.89.181.250]) by grover.en.com (8.8.8/8.8.8) with ESMTP id OAA13729 for ; Fri, 23 Oct 1998 14:16:38 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 14:14:22 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Dave To: Pine Discussion Forum Subject: Moved xxx bytes from /var/mail/..... (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: awyeah@bigbird X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When I'm at home, I use a client other than pine to access my mail... i like confidentiality, so it downloads it to my home computer and then deletes it. However, pine 4.05 does that thing where it moves the mail from the system mailbox (/var/mail/$LOGNAME) to somewhere in your home directory. How can I make it not do this? Dave ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dave Andrzejewski http://awyeah.diablo-2.com/ E-Mail: awyeah@en.com/00anddav@hawken.edu Whois: DA6239 ICQ UIN: 556410 AOL Instant Messager: SeCkZy Boi IRC Operator on the DALnet IRC network: /server sodre.dal.net 7000 Get my PGP Public Keys: http://awyeah.diablo-2.com/pgpkeys.html Hard work has a future payoff. Laziness pays off NOW. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBNjDHhMHnYhUtgdpwEQIdMQCgiYRM0xfIbKYBBFSbVYoo+4PkRLMAoO3b V3suGtRzNPcJ9RjpQCYlWFlD =FqYP -----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-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 11:46:38 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA09264 for ; Fri, 23 Oct 1998 11:46:37 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA03660; Fri, 23 Oct 1998 11:46:29 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA14440; Fri, 23 Oct 1998 11:44:26 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA37272 for ; Fri, 23 Oct 1998 11:40:34 -0700 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA15662 for ; Fri, 23 Oct 1998 11:40:33 -0700 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id OAA29428 for ; Fri, 23 Oct 1998 14:40:28 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 14:40:28 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <01J3B6B3E5C20015MW@CSTCC.CC.TN.US> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Debora Ervin wrote: > This discussion forum....was listed as a pine discussion group...(which to > me means, discussion about pine, thats anything about pine). I could wrong, > be I dont remember seeing a statement saying, (new users not allowed). The "mailing list" is for discussions about pine, thats the whole point really.... It could certainly be said better then it has been. People get tired of repeating it and reading it though... The fact is that if people even thought about it a little bit they would probably realize that pine is NOT likely to be an autoresponder. Other then the fact that pine deals with mail it has nothing in common with autoresponders. (of course I suppose you could always cobble somethign together with expect:) The rfaq idea really isnt that bad but it should be sent from the list as an introductory message to new subscribers. Just detail the hot button issues... * pine is not an autoresonder. dont ask about making it look like one * pine requires the mail spool directory to have 1777 for permissions etc etc...there really arent that many of them. Hit to the top 10 or so and that would probably help some. People frequently ask rather then reading a bit, this might head off a portion of those. Of course....ignoring these questions would also work... ;) ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 12:11:45 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA09096 for ; Fri, 23 Oct 1998 12:11:43 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA07664; Fri, 23 Oct 1998 12:11:37 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA07370; Fri, 23 Oct 1998 12:08:45 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA46464 for ; Fri, 23 Oct 1998 12:06:56 -0700 Received: from ALPHA2.CSTCC.CC.TN.US (ALPHA2.CSTCC.CC.TN.US [198.146.32.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA12199 for ; Fri, 23 Oct 1998 12:06:55 -0700 Received: from ccunltd.cdc.net (pm13-30.chattanooga.cdc.net) by CSTCC.CC.TN.US (PMDF V5.1-9 #D3068) with SMTP id <01J3BBPMM7KW001246@CSTCC.CC.TN.US> for pine-info@u.washington.edu; Fri, 23 Oct 1998 15:04:51 EST Message-Id: <01J3BBPNFEUQ001246@CSTCC.CC.TN.US> Date: Fri, 23 Oct 1998 15:12:39 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Debora Ervin To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: References: <01J3B6B3E5C20015MW@CSTCC.CC.TN.US> MIME-version: 1.0 Content-type: text/plain; charset="us-ascii" X-To: Darren Henderson , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN At 02:40 PM 10/23/98 -0400, Darren Henderson wrote: > >On Fri, 23 Oct 1998, Debora Ervin wrote: > >> This discussion forum....was listed as a pine discussion group...(which to >> me means, discussion about pine, thats anything about pine). I could wrong, >> be I dont remember seeing a statement saying, (new users not allowed). > >The "mailing list" is for discussions about pine, thats the whole point >really.... It could certainly be said better then it has been. People get >tired of repeating it and reading it though... The fact is that if people >even thought about it a little bit they would probably realize that pine >is NOT likely to be an autoresponder. Other then the fact that pine deals >with mail it has nothing in common with autoresponders. (of course I >suppose you could always cobble somethign together with expect:) > >The rfaq idea really isnt that bad but it should be sent from the list as >an introductory message to new subscribers. Just detail the hot button >issues... > >* pine is not an autoresonder. dont ask about making it look like one > >* pine requires the mail spool directory to have 1777 for permissions > >etc etc...there really arent that many of them. Hit to the top 10 or so >and that would probably help some. People frequently ask rather then >reading a bit, this might head off a portion of those. > >Of course....ignoring these questions would also work... ;) > > >______________________________________________________________________ >Darren Henderson darren@jasper.somtel.com > > Help fight junk e-mail, visit http://www.cauce.org/ > Thanks Darren, I was not looking for Pine to be an autoresponder....I need it to auto reply to my clients email only. Thanks From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 12:37:40 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA08471 for ; Fri, 23 Oct 1998 12:37:39 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA05290; Fri, 23 Oct 1998 12:37:28 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA08693; Fri, 23 Oct 1998 12:35:48 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA38222 for ; Fri, 23 Oct 1998 12:32:55 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA22846 for ; Fri, 23 Oct 1998 12:32:55 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id PAA08734 for ; Fri, 23 Oct 1998 15:32:57 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 15:32:57 -0400 (EDT) Reply-To: Ken Woods Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Adam H. Kerman wrote: > >From: Debora Ervin > >Date: Fri, 23 Oct 1998 12:37:18 -0400 > > >This discussion forum....was listed as a pine discussion group...(which to > >me means, discussion about pine, thats anything about pine). I could wrong, > >be I dont remember seeing a statement saying, (new users not allowed). > > New users are most welcome. Discussion about pine is most welcome. But > questions that are asked repeatedly are not. They drive out the discussion. lusers: umm...Frequently Asked Questions? FAQ??? http://www.washington.edu/pine/faq http://www.washington.edu/pine/QandA/index.html *sigh* -- Ken Woods kwoodskens.com And goddammnit, quit cc'ing me. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 13:42:57 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA10972 for ; Fri, 23 Oct 1998 13:42:56 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA07066; Fri, 23 Oct 1998 13:42:49 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA19323; Fri, 23 Oct 1998 13:39:04 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA13472 for ; Fri, 23 Oct 1998 13:32:53 -0700 Received: from kens.com (kens.com [209.70.169.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA30302 for ; Fri, 23 Oct 1998 13:32:52 -0700 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id QAA09085 for ; Fri, 23 Oct 1998 16:32:55 -0400 (EDT) Message-Id: Date: Fri, 23 Oct 1998 16:32:55 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Auto respond (fwd) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ---------- Forwarded message ---------- Date: Fri, 23 Oct 1998 22:28:44 +0200 From: A person that has a clue, who will remain anonymous. To: Those of us who have a clue. Subject: Re: Auto respond 90 seconds of editing gives you these sigs: Aaron S. Hawley ashawley@zoo.uvm.edu http://www.uvm.edu/~ashawley Home: Vergennes, VT, US // University of Vermont // 802.656.7396 Pine 3.96 E-Mailer on UVM Zoo Unix Cluster http://www.washington.edu/pine Debora E. Ervin DErvin@ccunltd.com Suite 111-130 // 2288 Gunbarrel Road // Chattanooga, TN 37421 FON (423)697-7775 Ext. 6003 Toll Free:(800)301-7299 Ext. 2 FAX (423)622-8862 Visit our website at http://www.ccunltd.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 14:10:37 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10529 for ; Fri, 23 Oct 1998 14:10:36 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA07867; Fri, 23 Oct 1998 14:10:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA20806; Fri, 23 Oct 1998 14:08:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA26496 for ; Fri, 23 Oct 1998 14:05:00 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id OAA28830 for ; Fri, 23 Oct 1998 14:04:59 -0700 Received: from [132.198.177.59] (132.198.177.59) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.41AF4140@smtpgate.uvm.edu>; Fri, 23 Oct 1998 17:04:55 -0400 Message-Id: Date: Fri, 23 Oct 1998 17:00:20 -0400 (EDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Auto respond (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Ken Woods X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN thanks ken i'll seriously use the new signature. question why is four lines the standard? Aaron S. Hawley ashawley@zoo.uvm.edu http://www.uvm.edu/~ashawley Home: Vergennes, VT, US // University of Vermont // 802.656.7396 Pc-Pine 4.05 E-Mailer http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 16:25:28 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA02591 for ; Fri, 23 Oct 1998 16:25:27 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13778; Fri, 23 Oct 1998 16:25:21 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA08230; Fri, 23 Oct 1998 16:24:19 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA25050 for ; Fri, 23 Oct 1998 16:21:41 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA18089 for ; Fri, 23 Oct 1998 16:21:27 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id QAA10660; Fri, 23 Oct 1998 16:21:18 -0700 (PDT) Message-Id: Date: Fri, 23 Oct 1998 16:21:18 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: Re: Moved xxx bytes from /var/mail/..... (fwd) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Dave X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Dave wrote: > However, pine 4.05 does that thing where it moves the mail from the system > mailbox (/var/mail/$LOGNAME) to somewhere in your home directory. How can > I make it not do this? This is a "feature" and can be disabled two ways. Either rename ~/mbox or edit your ~/.pinerc and change disable-these-drivers= to disable-these-drivers=mbox disable-these-drivers This variable is a list of mail drivers which will be disabled. The candidates for disabling are listed below. There may be more in the future if you compile Pine with a newer version of the c-client library. * mbox * mbx * mh * mmdf * mtx * mx * news * phile * tenex * unix The mbox driver enables the following behavior: if there is a file called mbox in your home directory, and if that file is either empty or in Unix mailbox format, then every time you open INBOX the mbox driver will automatically transfer mail from the system mail spool directory into the mbox file and delete it from the spool directory. If you disable the mbox driver, this will not happen. -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 16:42:23 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA11311 for ; Fri, 23 Oct 1998 16:42:21 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA11640; Fri, 23 Oct 1998 16:42:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA09094; Fri, 23 Oct 1998 16:40:51 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA46112 for ; Fri, 23 Oct 1998 16:38:21 -0700 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id QAA16627 for ; Fri, 23 Oct 1998 16:38:20 -0700 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.AE139E70@smtpgate.uvm.edu>; Fri, 23 Oct 1998 19:38:16 -0400 Message-Id: Date: Fri, 23 Oct 1998 19:38:24 -0400 (Eastern Daylight Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: ken! signature MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ken how is this for a signature. it's three lines, and dashes. and can i get away with the two lines at the bottom. i just want to fight back against like hotmail where at the bottom of the message they say hotmail, and then say the URl of hotmail. -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 16:44:34 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA06133 for ; Fri, 23 Oct 1998 16:44:32 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA14260; Fri, 23 Oct 1998 16:44:26 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA29821; Fri, 23 Oct 1998 16:43:24 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA22698 for ; Fri, 23 Oct 1998 16:40:22 -0700 Received: from cdc.net (server1.cdc.net [207.244.0.12]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id QAA16795 for ; Fri, 23 Oct 1998 16:40:22 -0700 Received: (qmail 10230 invoked from network); 23 Oct 1998 23:40:20 -0000 Received: from unknown (HELO ccunltd.cdc.net) (207.244.7.55) by server1.cdc.net with SMTP; 23 Oct 1998 23:40:20 -0000 Message-Id: <199810232340.QAA16795@mxu4.u.washington.edu> Date: Fri, 23 Oct 1998 19:46:04 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: DErvin@ccunltd.com To: Pine Discussion Forum Subject: Re: Auto respond (fwd) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-To: Ken Woods , Pine Discussion Forum X-Sender: ccunltd@mail.cdc.net X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Oh Ken you really are a sweetheart....thanks At 04:32 PM 10/23/98 -0400, Ken Woods wrote: > >---------- Forwarded message ---------- >Date: Fri, 23 Oct 1998 22:28:44 +0200 >From: A person that has a clue, who will remain anonymous. >To: Those of us who have a clue. >Subject: Re: Auto respond > >90 seconds of editing gives you these sigs: > >Aaron S. Hawley ashawley@zoo.uvm.edu http://www.uvm.edu/~ashawley >Home: Vergennes, VT, US // University of Vermont // 802.656.7396 >Pine 3.96 E-Mailer on UVM Zoo Unix Cluster http://www.washington.edu/pine > >Debora E. Ervin DErvin@ccunltd.com >Suite 111-130 // 2288 Gunbarrel Road // Chattanooga, TN 37421 >FON (423)697-7775 Ext. 6003 Toll Free:(800)301-7299 Ext. 2 >FAX (423)622-8862 Visit our website at http://www.ccunltd.com > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 17:11:35 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14170 for ; Fri, 23 Oct 1998 17:11:34 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA12386; Fri, 23 Oct 1998 17:11:27 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA23003; Fri, 23 Oct 1998 17:10:26 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA46098 for ; Fri, 23 Oct 1998 17:08:02 -0700 Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA04262 for ; Fri, 23 Oct 1998 17:07:59 -0700 Received: from [212.228.155.84] (helo=A470.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.05demon1 #1) id 0zWrFN-0007l1-00 for pine-info@u.washington.edu; Sat, 24 Oct 1998 00:07:58 +0000 Received: (qmail 8093 invoked by uid 500); 24 Oct 1998 01:09:02 -0000 Message-Id: <19981024010902.A7905@A470.demon.co.uk> Date: Sat, 24 Oct 1998 01:09:02 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Wyn Rees To: Pine Discussion Forum Subject: Re: ken! signature In-Reply-To: ; from Aaron S. Hawley on Fri, Oct 23, 1998 at 07:38:24PM -0400 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-PGP-812C54B1: F8 79 5E 84 F0 20 A5 62 FA 2D E9 BD BE 06 7D 10 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, Oct 23, 1998 at 07:38:24PM -0400, Aaron S. Hawley wrote: > like hotmail where at the bottom of the message they say hotmail, and then > say the URl of hotmail. I pass all my mail through a sed script. It zaps tonnes of unwanted ads, a la : /^Get Your Private, Free Email at http\:\/\/www\.hotmail\.com/d /^DO YOU YAHOO!?/d /^Get your free \@yahoo\.com address at http/d /^Get free e-mail and a permanent address at/d /^at http:\/\/www.eGroups.com -- Free Web-based e-mail groups/d Easy... no more Yahoo! ads. (I also add the trailer info for list, eg. the one for the Pine list). From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 17:14:24 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA14901 for ; Fri, 23 Oct 1998 17:14:23 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA12481; Fri, 23 Oct 1998 17:14:06 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA16121; Fri, 23 Oct 1998 17:12:56 -0700 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA46122 for ; Fri, 23 Oct 1998 17:08:51 -0700 Received: from nov.diac.com (diac.com [209.64.40.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA19532 for ; Fri, 23 Oct 1998 17:08:51 -0700 Received: from localhost (ekwall2@localhost) by nov.diac.com (8.8.8/8.8.8) with SMTP id AAA13511; Sat, 24 Oct 1998 00:08:19 GMT Message-Id: Date: Fri, 23 Oct 1998 18:08:18 -0600 (MDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Ekwall To: Pine Discussion Forum Subject: Re: signoff help In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Tawfik Daoud X-Cc: Pine Discussion Forum X-Sender: ekwall2@november X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi Tawfik(?) Before you leave, I think you might note, that that was a one-time autoreply from Debora who ask THE question, how can I make this work! * She appeared to be succesful! * So, the group, (most of it anyway) got her question answered (proof below - that's her auto-generated vacation file in .pine. and will be recieved only ONE time by this list, it was of course designed (written for her clients) if all the "man procmail" and "man vacation" features work. So, esstentially, that was a thank you from her that it worked as pine-lister's suggested. or at least "got it!:)" Best to you & yours (whatever business endeaver your in:) -=se=- steve (i can't afford the trips anyway :) ekwall back to Y2K fixings :) On Fri, 23 Oct 1998, Tawfik Daoud wrote: I thought contributing in Pine info list should help people in promoting their knowledge in using the Pine mailing software. But to exchange ads whenever a contribution is made (such as the one I received below), let me think of how major-domo or whatever mailing lists software, the pine developers are using, could stop this unsolicited activities?!? May be someone should sit behind the wheel and try to filter those emails or may be excluding mails having such big words like SPECIALS .. RESERVATION .. etc -Tawfik On Fri, 23 Oct 1998, C & C Unlimited Travel & Events wrote: > Hello, > > C&C Unlimited Travel & Events has received your recent email. > Thank you. We will handle your request accordingly. > > Visit our website: http://www.ccunltd.com > > *********************** > SPECIALS > *********************** > > CARNIVAL FunShip > "Winter Sale" > 2-for-1 > 3, 4, and 7 day cruises > Rates From Only $299 (Including port charges) > > Make Your Reservations Today!@ > > Debora Ervin > C&C Unlimited Travel & Events > 2288 Gunbarrel Road > Suite 111-130 > Chattanooga, TN 37421 > Toll Free: (800)301-7299 EX. 2 > Local: (423)697-7775 EX. 6003 > Fax: (423)622-8862 > Website: http://www.ccunltd.com > > "Your Personal Consultants to the World" > > _______________________________________ Tawfik H. Daoud Cyber Mania - Internet Service Provider 68, Avenue Mohamed V, 93000 Tetouan, Morocco Telephone: +212.9.704987 Fax: +212.9.965883 E-mail: tdaoud@cybermania.net.ma http://www.cybermania.net.ma From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 18:33:26 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA14583 for ; Fri, 23 Oct 1998 18:33:25 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA13668; Fri, 23 Oct 1998 18:33:19 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA13083; Fri, 23 Oct 1998 18:32:19 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA30320 for ; Fri, 23 Oct 1998 18:29:42 -0700 Received: from nov.diac.com (diac.com [209.64.40.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA10663 for ; Fri, 23 Oct 1998 18:29:41 -0700 Received: from localhost (ekwall2@localhost) by nov.diac.com (8.8.8/8.8.8) with SMTP id BAA26546; Sat, 24 Oct 1998 01:29:11 GMT Message-Id: Date: Fri, 23 Oct 1998 19:29:11 -0600 (MDT) Reply-To: Steve Ekwall Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Steve Ekwall To: Pine Discussion Forum Subject: Re: Auto respond In-Reply-To: <19981023131303.A10086@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Sender: ekwall2@november X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Robin S. Socha wrote: > tried your www.kens.com/robin address, and we'd need a password, can I Sure. It's to be found on . Or maybe you should try UID: "DeAHtiHS", Password: "BofH". > or. another path to point me to if not?? Sendero Luminoso? 42? Hell? Robin ------------------------------ Hi Ro(sorry it's frisday for u)bin Never mind, sorry I asked, actually got through anyway last night and got all the .professional*.english,.misc.interests.afterstep.xemacs htmls and will read-this weekend. hope to return a smarter lusor as you say. just thought we could learn a little more from you thanks anyway. -=se=- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 20:05:24 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA14630 for ; Fri, 23 Oct 1998 20:05:23 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA17393; Fri, 23 Oct 1998 20:05:17 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA27775; Fri, 23 Oct 1998 20:04:17 -0700 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA45376 for ; Fri, 23 Oct 1998 20:01:49 -0700 Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA03129 for ; Fri, 23 Oct 1998 20:01:49 -0700 Received: from luomat.peak.org (port-10-ts1-gnv.da.fdt.net [209.212.132.169]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA14709 for ; Fri, 23 Oct 1998 20:01:42 -0700 Message-Id: <199810240301.XAA13180@ocalhost> Date: Fri, 23 Oct 1998 23:01:36 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Is there anywhere I can get the original 3.96 source code? In-Reply-To: <199810240258.WAA13024@ocalhost> References: <199810240258.WAA13024@ocalhost> Content-Type: text/plain MIME-Version: 1.0 X-To: pine-info@cac.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN 3.96 is still my preferred version of PINE. I seem to have lost the source code (only have my patches to it). Does anyone have it somewhere that I could FTP it? Thanks TjL ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 20:20:38 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA16696 for ; Fri, 23 Oct 1998 20:20:36 -0700 (PDT) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA17599; Fri, 23 Oct 1998 20:20:30 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA15866; Fri, 23 Oct 1998 20:19:32 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA49424 for ; Fri, 23 Oct 1998 20:17:04 -0700 Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA17934 for ; Fri, 23 Oct 1998 20:17:03 -0700 Received: from localhost (mcope@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) with ESMTP id UAA00586; Fri, 23 Oct 1998 20:16:59 -0700 (PDT) Message-Id: Date: Fri, 23 Oct 1998 20:16:59 -0700 (PDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Thomas Cope To: Pine Discussion Forum Subject: Re: Is there anywhere I can get the original 3.96 source code? In-Reply-To: <199810240301.XAA13180@ocalhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 23 Oct 1998, Timothy J Luoma wrote: > > 3.96 is still my preferred version of PINE. > Does anyone have it somewhere that I could FTP it? ftp://ftp.cac.washington.edu/pine/old/ -- Michael Cope: Harvey Mudd College '00; Armand Hammer UWC '96 E-mail: Michael_Cope@hmc.edu From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Fri, 23 Oct 1998 20:28:20 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA16423 for ; Fri, 23 Oct 1998 20:28:19 -0700 (PDT) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA15060; Fri, 23 Oct 1998 20:28:13 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA22038; Fri, 23 Oct 1998 20:27:13 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA30222 for ; Fri, 23 Oct 1998 20:24:51 -0700 Received: from luomat.peak.org (port-16-ts2-gnv.da.fdt.net [209.212.132.47]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA18404 for ; Fri, 23 Oct 1998 20:24:44 -0700 Message-Id: <199810240324.XAA13577@ocalhost> Date: Fri, 23 Oct 1998 23:24:05 -0400 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Timothy J Luoma To: Pine Discussion Forum Subject: Re: Is there anywhere I can get the original 3.96 source code? In-Reply-To: References: Content-Type: text/plain MIME-Version: 1.0 X-To: Michael Thomas Cope X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN My apologies. I can't explain why I didn't see that directory. I was just there earlier tonight (d/l the 4.5 code) and the 'old' directory never even registered in my brain. TjL From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sat, 24 Oct 1998 11:33:33 -0700 (PDT) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA27309 for ; Sat, 24 Oct 1998 11:33:31 -0700 (PDT) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA27851; Sat, 24 Oct 1998 11:33:25 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA14731; Sat, 24 Oct 1998 11:31:29 -0700 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA23206 for ; Sat, 24 Oct 1998 11:28:59 -0700 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA03350 for ; Sat, 24 Oct 1998 11:28:58 -0700 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id NAA18408 for ; Sat, 24 Oct 1998 13:28:56 -0500 Message-Id: Date: Sat, 24 Oct 1998 13:28:56 -0500 (CDT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Aaron S. Hawley" >Date: Fri, 23 Oct 1998 17:00:20 -0400 (EDT) >thanks ken i'll seriously use the new signature. question why is four >lines the standard? >Aaron S. Hawley ashawley@zoo.uvm.edu http://www.uvm.edu/~ashawley >Home: Vergennes, VT, US // University of Vermont // 802.656.7396 >Pc-Pine 4.05 E-Mailer http://www.washington.edu/pine Sven (Ken just forwarded) forgot to emphasize use of the delimiter: "-- " [two hyphens followed by a space on a line above the .sig] It's not a standard; it's a convention. It has nothing to do with routing messages through machines. It has everything to do with trying the patience of those who would read your message. I haven't been receiving e-mail long enough to recall, so I cannot speak to this from experience. From what I have read, in the beginning Mail compliant with Internet (and predessors) standards was relayed through uucp. Typically, but not always, the headers survived intact. However, Mail was often gatewayed to other systems like BITNET and FidoNET that followed different protocols. All of these systems were like uucp: store and forward. Also, the original mailing list server, LISTSERV, was written in Europe to distribute messages over the US BITNET. The purpose was to consolidate the sending of identical messages as much as possible to better utilize the use of extremely expensive resources, namely trans-Atlantic communications. LISTSERV only identified the name of the mailing list at first, not the author of the message. For all these reasons, it became a practice to include the author's name in the .sig. Today, none of these reasons exist anymore, and information in the .sig is either redundant or unnecessary. The real reason authors include .sigs is vanity or advertising. However, you may put any text you like into the body of a Mail message. If you follow the convention of use of "-- " as a delimiter and include no more than four lines of text, no one at all will complain. Four lines of text is generally considered to be "within reason" and won't irritate anyone. The following arguments are made against .sigs in general, and my use of the word "you" isn't aimed specifically at Aaron's new .sig. Yes, there can be gateways that munge headers these days, but they are called "broken". Rather than have everyone assume that repeating one's name in the .sig is necessary, it is up to the users of those gateways to take steps to fix them. It's their problem, not the rest of us. The rest of the information people typically unnecessary. We don't need to your phone number. We don't care to reach you by wireless, whether pager or cellular, and we aren't going to send you a fax. We know your e-mail address, and that's how we'll contact you if we choose to. We know your name: It's in your From line. (It's not? Then put it there.) It's lovely that you have a Web page. Is anything on it relevant to the Subject of the thread? Then make reference to it much earlier in your message. Are any of your 15 affiliations relevant to the arguments you made in your message? Unlikely. If you actually published a paper, cite it. If we want to, we'll read it and make our own judgement. And as far as those quotes go, yes, it was witty when the original author said it. You are repeating it over and over again. It's now trite. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 00:01:58 -0700 (PDT) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA25723 for ; Sun, 25 Oct 1998 00:01:55 -0700 (PDT) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA03416; Sun, 25 Oct 1998 00:01:47 -0700 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA09753; Sat, 24 Oct 1998 23:54:20 -0700 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA15074 for ; Sat, 24 Oct 1998 23:51:07 -0700 Received: from moose.uvm.edu (moose.uvm.edu [132.198.101.60]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA25197 for ; Sat, 24 Oct 1998 23:51:05 -0700 Received: from elk.uvm.edu (elk.uvm.edu [132.198.101.63]) by moose.uvm.edu (8.8.7/8.8.7) with ESMTP id BAA60538; Sun, 25 Oct 1998 01:51:04 -0500 Received: from localhost (ashawley@localhost) by elk.uvm.edu (8.8.7/8.8.7) with SMTP id BAA74914; Sun, 25 Oct 1998 01:51:03 -0500 Message-Id: Date: Sun, 25 Oct 1998 01:51:03 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Authentication-Warning: elk.uvm.edu: ashawley owned process doing -bs X-Sender: ashawley@elk.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Thanks Adam for the Info on signature files. Now that wasn't so bad now was it Michael Ruder (he gave me crap for talking about signatures). but now i think i learned something, and isn't what this Pine Discussion Forum is all about learningin something about using Pine. And I would think signatures have to do with Pine. we all have to deal with other peoples signature so lets understand the ethics of signatures. That's just my take on it. although i can sympathize with peoples annoyance that we are making a huge discussions over signaturs. -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__Millis 428__802.656.7396 Pine 3.96 E-Mailer on Zoo Unix Cluster_______________________________ small,fast,simple,complex,free_________http://www.washington.edu/pine On Sat, 24 Oct 1998, Adam H. Kerman wrote: > Sven (Ken just forwarded) forgot to emphasize use of the delimiter: > "-- " [two hyphens followed by a space on a line above the .sig] > > It's not a standard; it's a convention. It has nothing to do with routing > messages through machines. It has everything to do with trying the patience of > those who would read your message. > > I haven't been receiving e-mail long enough to recall, so I cannot speak to > this from experience. From what I have read, in the beginning Mail compliant > with Internet (and predessors) standards was relayed through uucp. Typically, > but not always, the headers survived intact. > > However, Mail was often gatewayed to other systems like BITNET and FidoNET that > followed different protocols. All of these systems were like uucp: store and > forward. > > Also, the original mailing list server, LISTSERV, was written in Europe to > distribute messages over the US BITNET. The purpose was to consolidate the > sending of identical messages as much as possible to better utilize the use of > extremely expensive resources, namely trans-Atlantic communications. > > LISTSERV only identified the name of the mailing list at first, not the author > of the message. > > For all these reasons, it became a practice to include the author's name in the > .sig. Today, none of these reasons exist anymore, and information in the .sig > is either redundant or unnecessary. > > The real reason authors include .sigs is vanity or advertising. > > However, you may put any text you like into the body of a Mail message. If you > follow the convention of use of "-- " as a delimiter and include no more than > four lines of text, no one at all will complain. Four lines of text is > generally considered to be "within reason" and won't irritate anyone. > > The following arguments are made against .sigs in general, and my use of the > word "you" isn't aimed specifically at Aaron's new .sig. > > Yes, there can be gateways that munge headers these days, but they are called > "broken". Rather than have everyone assume that repeating one's name in the > .sig is necessary, it is up to the users of those gateways to take steps to fix > them. It's their problem, not the rest of us. > > The rest of the information people typically unnecessary. We don't need to your > phone number. We don't care to reach you by wireless, whether pager or > cellular, and we aren't going to send you a fax. > > We know your e-mail address, and that's how we'll contact you if we choose to. > We know your name: It's in your From line. (It's not? Then put it there.) > > It's lovely that you have a Web page. Is anything on it relevant to the Subject > of the thread? Then make reference to it much earlier in your message. > > Are any of your 15 affiliations relevant to the arguments you made in your > message? Unlikely. If you actually published a paper, cite it. If we want to, > we'll read it and make our own judgement. > > And as far as those quotes go, yes, it was witty when the original author said > it. You are repeating it over and over again. It's now trite. > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 06:51:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA08921 for ; Sun, 25 Oct 1998 06:51:10 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA11255; Sun, 25 Oct 1998 06:51:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA01247; Sun, 25 Oct 1998 06:50:01 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA46094 for ; Sun, 25 Oct 1998 06:47:27 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA05743 for ; Sun, 25 Oct 1998 06:47:26 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id IAA01665 for ; Sun, 25 Oct 1998 08:47:24 -0600 Message-Id: Date: Sun, 25 Oct 1998 08:47:24 -0600 (CST) Reply-To: "Adam H. Kerman" Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Please do not Cc the author when replying to his message on a mailing list or on a newsgroup. Please don't quote back the ENTIRE message. If you have a comment on a specific aspect of the message, quote that and delete everything else. >From: "Aaron S. Hawley" >Date: Sun, 25 Oct 1998 01:51:03 -0500 (EST) >Thanks Adam for the Info on signature files. Now that wasn't so bad now Aaron, I'll trust that you used "-- " including the trailing blank. But a gateway somewhere truncates trailing blanks, a common but broken practice. You've gotten your .sig down to 4 lines of text, which is fine. But I'd still urge you to remove the three blank lines. >-- >Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ >University of Vermont__Millis 428__802.656.7396 > > > >Pine 3.96 E-Mailer on Zoo Unix Cluster_______________________________ >small,fast,simple,complex,free_________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 08:47:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10629 for ; Sun, 25 Oct 1998 08:47:19 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA12407; Sun, 25 Oct 1998 08:47:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA16850; Sun, 25 Oct 1998 08:42:34 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA59726 for ; Sun, 25 Oct 1998 08:40:08 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA23118 for ; Sun, 25 Oct 1998 08:40:08 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id JAA06475 for ; Sun, 25 Oct 1998 09:40:07 -0700 (MST) Received: from [192.168.1.2] (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id JAA17985 for ; Sun, 25 Oct 1998 09:37:19 -0700 (MST) Message-Id: Date: Sun, 25 Oct 1998 09:32:55 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 25 Oct 1998, Adam H. Kerman wrote: > Please do not Cc the author when replying to his message on a mailing list or > on a newsgroup. Please don't quote back the ENTIRE message. If you have a Then in that case, it would probably be a good idea if the list administrators changed the list setup to add a "reply-to:" line to the headers. The way it's currently set up, if you do a reply in pine, You either have to reply directyl to the author, or to the author and cc: to the list. that, or go in and munge the addressees of the reply, which, quite frankly, is a royal pain in the butt. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 09:17:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA03822 for ; Sun, 25 Oct 1998 09:17:53 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA12835; Sun, 25 Oct 1998 09:17:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA17720; Sun, 25 Oct 1998 09:16:52 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA20754 for ; Sun, 25 Oct 1998 09:14:22 -0800 Received: from zugzug.cfar.UMD.EDU (root@zugzug.cfar.umd.edu [128.8.132.82]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA28221 for ; Sun, 25 Oct 1998 09:14:22 -0800 Received: from cfar.umd.edu by zugzug.cfar.UMD.EDU (8.8.5/UMIACS-0.9/04-05-88) id MAA15446; Sun, 25 Oct 1998 12:14:13 -0500 (EST) Message-Id: <199810251714.MAA15446@zugzug.cfar.UMD.EDU> Date: Sun, 25 Oct 1998 12:14:12 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Adam Sulmicki To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: Your message of "Sun, 25 Oct 1998 08:47:24 CST." X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum , adam@cfar.umd.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN "Adam H. Kerman" writes: ->Please don't quote back the ENTIRE message. If you have a comment on a ->specific aspect of the message, quote that and delete everything else. Yes. ->Please do not Cc the author when replying to his message on a mailing list or ->on a newsgroup. No. That's not that simple. For some ppl may it seems to good solution, but other's hate it. In fact a while ago on linux kernel mailing list they did try to implement Reply-To solution so that reply would go back only to list. However, after a lots of protest they backed off. The reason for this is that many ppl use mail filtering programs. For example in mine case, the mail for 'pine' goes to one folder and mail sent to me goes to different folder. Thus it is good to send both copies because : 1) I can maintain proper archive of both, 'personal' and 'pine' folders. 2) I know that someone send an email to me, and it deverves priority in responding. After all I get around 500 emails a day. Thus I may have time to read them all on given day. CCing me helps make sure it gets my attention. Adam From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 09:42:16 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA11085 for ; Sun, 25 Oct 1998 09:42:15 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA10757; Sun, 25 Oct 1998 09:42:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA10620; Sun, 25 Oct 1998 09:41:07 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA45228 for ; Sun, 25 Oct 1998 09:38:36 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29428 for ; Sun, 25 Oct 1998 09:38:35 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id LAA03508 for ; Sun, 25 Oct 1998 11:38:34 -0600 Message-Id: Date: Sun, 25 Oct 1998 11:38:34 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Cc'ing the author of a mailing list or News message (was: limits on .sig) In-Reply-To: <199810251714.MAA15446@zugzug.cfar.UMD.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Adam Sulmicki >Date: Sun, 25 Oct 1998 12:14:12 -0500 >"Adam H. Kerman" writes: >->Please do not Cc the author when replying to his message on a mailing list or >->on a newsgroup. >No. I just made a specific request. You may disagree with me that it shouldn't apply to replies you send to others. But you just deliberately Cc'd me against my wishes. I can only conclude that you are being deliberately irritating. >That's not that simple. For some ppl may it seems to good solution, >but other's hate it. In fact a while ago on linux kernel mailing list >they did try to implement Reply-To solution so that reply would go >back only to list. However, after a lots of protest they backed off. Having the list server set Reply-To is especially evil. That header is for the legitimate use of the author of a mail message. He may be writing a messgae from one account and asking that replies be sent to another account he uses. The list server SHOULD pass messages intact, except for adding Received headers and any necessary headers added by moderators. It should NEVER alter any headers set by the author. >The reason for this is that many ppl use mail filtering programs. For >example in mine case, the mail for 'pine' goes to one folder and >mail sent to me goes to different folder. You may filter incoming mail as you wish. I filter first by looking for replies to messages I sent, not caring if they were personal e-mail or via a mailing list. Or I look for Subjects containing threads I participated in. (Unlike in News, which tries to maintain threads with Message-IDs, Mail tends to discard earlier Message-IDs so that's not reliable.) Or I look for text unique to the thread. After that initial filtering, I look for header information (like Sender) which is unique to a mailing list I'm on. Nearly everything else is spam, even if personally addressed to me. >Thus it is good to send both copies because : >1) I can maintain proper archive of both, 'personal' and 'pine' folders. Lots of people save all incoming mail. Make a judgment when you first read it. If you don't think you'll ever need to look at it again, discard it. >2) I know that someone send an email to me, and it deverves priority >in responding. After all I get around 500 emails a day. Thus I may >have time to read them all on given day. CCing me helps make sure it >gets my attention. It sounds like instead you should set up an outgoing message filter to prevent you from subscribing to any more mailing lists you couldn't possibly read. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 09:44:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA06648 for ; Sun, 25 Oct 1998 09:44:46 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13140; Sun, 25 Oct 1998 09:44:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA10784; Sun, 25 Oct 1998 09:43:45 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA27338 for ; Sun, 25 Oct 1998 09:38:40 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA12809 for ; Sun, 25 Oct 1998 09:38:39 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id MAA19975 for ; Sun, 25 Oct 1998 12:38:41 -0500 (EST) Message-Id: Date: Sun, 25 Oct 1998 12:38:41 -0500 (EST) Reply-To: Ken Woods Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 25 Oct 1998, Ian Hall-Beyer wrote: > headers. The way it's currently set up, if you do a reply in pine, You > either have to reply directyl to the author, or to the author and cc: to > the list. that, or go in and munge the addressees of the reply, which, > quite frankly, is a royal pain in the butt. You certainly are a lazy asshole, aren't you??? Take the extra 3 seconds. Here's what you have to do. Up arrow Up arrow Up arrow Up arrow CTRL-k Downarrow CTRL-k up arrow CTRL-u Pretty simple, isn't it, you stupid bastard? Now, if you were GOOD, you could add a crtl sequence, and do that with one keystroke, like the rest of us do. However, you're not, so just do what I outlined above. obpine: ehh.....anybody ever compile pine so that it sends ROT13 by default???? Fun. -- Ken Woods kwoodskens.com Yes, I know I'm an asshole. So??? From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 11:09:36 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA11191 for ; Sun, 25 Oct 1998 11:09:35 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA11764; Sun, 25 Oct 1998 11:09:29 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA07128; Sun, 25 Oct 1998 11:08:09 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA40116 for ; Sun, 25 Oct 1998 11:05:28 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA01191 for ; Sun, 25 Oct 1998 11:05:27 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id NAA04429 for ; Sun, 25 Oct 1998 13:05:26 -0600 Message-Id: Date: Sun, 25 Oct 1998 13:05:26 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Setting Reply-To on list evil (was: limits on .sig) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Ian Hall-Beyer >Date: Sun, 25 Oct 1998 09:32:55 -0700 (MST) >On Sun, 25 Oct 1998, Adam H. Kerman wrote: >>Please do not Cc the author when replying to his message on a mailing list or >>on a newsgroup. >Then in that case, it would probably be a good idea if the list administrators >changed the list setup to add a "reply-to:" line to the headers. The way it's >currently set up, if you do a reply in pine, You either have to reply directyl >to the author, or to the author and cc: to the list. that, or go in and munge >the addressees of the reply I don't care for Pine's implementation of replies to messages from mailing lists either. But having the list server add or overwrite Reply-To is simply evil. An author is assumed to have a good reason when he set Reply-To, and the server should take pains to minimize the changes it makes to send the message to the list. pine is the tool we chose to use. Replying to a list is one of its limitations. As users, we must work with it. But it is wrong to expect list owners to overcome such definciencies, even the owner of pine-info. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 12:35:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA12357 for ; Sun, 25 Oct 1998 12:35:55 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA12842; Sun, 25 Oct 1998 12:35:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA23404; Sun, 25 Oct 1998 12:34:04 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA30386 for ; Sun, 25 Oct 1998 12:31:27 -0800 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA21770 for ; Sun, 25 Oct 1998 12:31:25 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id PAA06105 for ; Sun, 25 Oct 1998 15:31:19 -0500 (EST) Message-Id: Date: Sun, 25 Oct 1998 15:31:19 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil (was: limits on .sig) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 25 Oct 1998, Adam H. Kerman wrote: > I don't care for Pine's implementation of replies to messages from mailing > lists either. But having the list server add or overwrite Reply-To is simply > evil. An author is assumed to have a good reason when he set Reply-To, and the > server should take pains to minimize the changes it makes to send the message > to the list. I've seen this arguement in several places. Some people argue this with a religous zeal that is not to be believed. Look, its a matter of perspective. I send a message the the list the list sends a message to everyone else. I don't send the message to everyone else the list does. Since the list is now sending the message its legit for it to set the reply-to header as it sees fit. On a list that is meant to be a discussion list and not a contact list or an announcement list the reply too should always be set to the list imo. ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 12:50:52 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA31529 for ; Sun, 25 Oct 1998 12:50:51 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA15436; Sun, 25 Oct 1998 12:50:44 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA04096; Sun, 25 Oct 1998 12:48:24 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA27350 for ; Sun, 25 Oct 1998 12:45:58 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA05980 for ; Sun, 25 Oct 1998 12:45:57 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id OAA05430 for ; Sun, 25 Oct 1998 14:45:56 -0600 Message-Id: Date: Sun, 25 Oct 1998 14:45:56 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Darren Henderson >Date: Sun, 25 Oct 1998 15:31:19 -0500 (EST) >On Sun, 25 Oct 1998, Adam H. Kerman wrote: >>But having the list server add or overwrite Reply-To is simply evil. An >>author is assumed to have a good reason when he set Reply-To, and the server >>should take pains to minimize the changes it makes to send the message to the >>list. >I've seen this arguement in several places. Some people argue this with a >religous zeal that is not to be believed. >Look, its a matter of perspective. I send a message the the list the list >sends a message to everyone else. I don't send the message to everyone >else the list does. Since the list is now sending the message its legit >for it to set the reply-to header as it sees fit. Like people who argue in favor of servers munging messages, you are blind to the main point: The author of the message has the right to set Reply-To as he likes for his own purposes. The list owner is usurping that right by substituting his judgment. >On a list that is meant to be a discussion list and not a contact list or >an announcement list the reply too should always be set to the list imo. If you make a mistake in a reply, would you rather take a chance that you sent it to only one person or you sent a private message to all? Setting Reply-To is ALSO an attempt to substitute for the judgment of the person composing the reply. The list owner is saying, there should NEVER be any private replies. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 13:51:22 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA13233 for ; Sun, 25 Oct 1998 13:51:22 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA13756; Sun, 25 Oct 1998 13:51:15 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA05801; Sun, 25 Oct 1998 13:50:01 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA28254 for ; Sun, 25 Oct 1998 13:47:29 -0800 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA09265 for ; Sun, 25 Oct 1998 13:47:27 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id QAA06232 for ; Sun, 25 Oct 1998 16:47:21 -0500 (EST) Message-Id: Date: Sun, 25 Oct 1998 16:47:21 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > Like people who argue in favor of servers munging messages, you are blind to > the main point: The author of the message has the right to set Reply-To as he > likes for his own purposes. The list owner is usurping that right by > substituting his judgment. Nope, your using my list, you accept the terms of how that list works. I'm not stopping you from replying privately. I may be making you work a bit harder to do it but thats because its meant to be a discussion and not a place for setting up private contacts (if thats the nature of the list). I'm not blind to anything, I view the relationships differently then you is all. You're submitting something to a list to be broadcast. If the list is moderated it may or may not be accepted. Am I then usurping your right to speak? Lists frequently tack on footers on every message, are they coopting my editorial and speech rights when they do that? Of course not. If you belong to a list you are agreeing to accept the terms the list maintainer has choosen. You can ask them (hopefully outside the list, and hopefully politely) to change those terms. This really isnt a discussion thats appropriate to this list other then perhaps as an example of why it migth be nice if pine could some how attempt to devine the source of a message and explicitly ask: Reply to (L)ist, (A)uthor, or (B)oth or some such. > If you make a mistake in a reply, would you rather take a chance that you sent > it to only one person or you sent a private message to all? So everyone should have to do more to protect you from making a stupid mistak? Anyone who sends a message without double checking the receipient is asking for trouble. We can't protect everyone from everything. Personal responsibility ya know? > Setting Reply-To is ALSO an attempt to substitute for the judgment of the > person composing the reply. The list owner is saying, there should NEVER be any > private replies. Thats just silly. Just making it the tinyest bit harder for you to do it. You have to concuously take a discussion away from the list. I'm certainly not capbalbe of reaching out there and stopping you from sending to whoever you like to send too. It is expressing a preference that you reply to the list instead of privately and I see absolutely nothing wrong with that if its appropriate for the given list. ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 14:17:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA13407 for ; Sun, 25 Oct 1998 14:17:46 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA16473; Sun, 25 Oct 1998 14:17:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA12243; Sun, 25 Oct 1998 14:16:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA43186 for ; Sun, 25 Oct 1998 14:13:56 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA27673 for ; Sun, 25 Oct 1998 14:13:55 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id QAA06400 for ; Sun, 25 Oct 1998 16:13:53 -0600 Message-Id: Date: Sun, 25 Oct 1998 16:13:53 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Darren Henderson >Date: Sun, 25 Oct 1998 16:47:21 -0500 (EST) >>Like people who argue in favor of servers munging messages, you are blind to >>the main point: The author of the message has the right to set Reply-To as he >>likes for his own purposes. The list owner is usurping that right by >>substituting his judgment. >Nope, your using my list, you accept the terms of how that list works. I'm >not stopping you from replying privately. I may be making you work a bit >harder to do it but thats because its meant to be a discussion and not a >place for setting up private contacts (if thats the nature of the list). >I'm not blind to anything, This is my final try. If you miss the point again, I will assume that there is nothing I can do to open your eyes. Reply-To is a header designed to be used by the composer of a message. Only later was its use taken over by a few list owners who fail to acknowledge its original utility. Let's say, for my convenience, I have multiple mailboxes. Suppose I subscribe to a mailing list and must post to the list using a specific From. I participate on a thread that pertains to a subject I have a regular interest in. It could be business or a hobby. Normally, I correspond with people using a different From. So, I participate on the thread and set Reply-To to the mailbox to which I want personal replies directed to. I'd say that I have a legitimate use for setting Reply-To myself. If you were the list owner, you have decided that I may NOT set Reply-To. You instead substitute your own judgment and have the server munge it to the list posting address. You, the list owner, are doing something harmful. >I view the relationships differently then you is all. You're submitting >something to a list to be broadcast. If the list is moderated it may or may >not be accepted. Am I then usurping your right to speak? You have missed the point. You are so wide of the mark that the shot went around the bend into the next county. You are usurping MY right to ask people to send replies NOT to the address I must post from, but to another address at which I would prefer to receive them. >Lists frequently tack on footers on every message, are they coopting my >editorial and speech rights when they do that? Of course not. To some extent, they are. A list server can make necessary modifications to headers, like Sender. The purist would say Make minimal modifications! But no purist would EVER modify the body of a message. However, that is much less harmful than setting Reply-To. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 16:10:16 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA07830 for ; Sun, 25 Oct 1998 16:10:15 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA17729; Sun, 25 Oct 1998 16:10:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA00223; Sun, 25 Oct 1998 16:08:50 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA28644 for ; Sun, 25 Oct 1998 16:06:14 -0800 Received: from moose.uvm.edu (moose.uvm.edu [132.198.101.60]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA17222 for ; Sun, 25 Oct 1998 16:06:14 -0800 Received: from gnu.uvm.edu (gnu.uvm.edu [132.198.101.64]) by moose.uvm.edu (8.8.7/8.8.7) with ESMTP id TAA72160 for ; Sun, 25 Oct 1998 19:06:12 -0500 Received: from localhost (ashawley@localhost) by gnu.uvm.edu (8.8.7/8.8.7) with SMTP id TAA97194 for ; Sun, 25 Oct 1998 19:06:12 -0500 Message-Id: Date: Sun, 25 Oct 1998 19:06:12 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Authentication-Warning: gnu.uvm.edu: ashawley owned process doing -bs X-Sender: ashawley@gnu.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN what if i was to just Cc to the Pine-info duscussion list ould you guys be pissed? and not put in the To? not like i'm to lazy to do it the right way. but i've been doing it that way and i'm wondering if anyone was gving me crap for that at any time. -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__Millis 428__802.656.7396 Pine 3.96 E-Mailer on Zoo Unix Cluster_______________________________ small,fast,simple,complex,free_________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 18:26:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA14345 for ; Sun, 25 Oct 1998 18:26:30 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA16810; Sun, 25 Oct 1998 18:26:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA20991; Sun, 25 Oct 1998 18:25:16 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA39968 for ; Sun, 25 Oct 1998 18:22:28 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA25466 for ; Sun, 25 Oct 1998 18:22:26 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id UAA09214 for ; Sun, 25 Oct 1998 20:22:24 -0600 Message-Id: Date: Sun, 25 Oct 1998 20:22:24 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: "Aaron S. Hawley" >Date: Sun, 25 Oct 1998 19:06:12 -0500 (EST) >what if i was to just Cc to the Pine-info duscussion list ould you guys be >pissed? and not put in the To? not like i'm to lazy to do it the right >way. but i've been doing it that way and i'm wondering if anyone was >gving me crap for that at any time. That wouldn't break anything; go for it. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 19:58:42 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA15767 for ; Sun, 25 Oct 1998 19:58:41 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA20563; Sun, 25 Oct 1998 19:58:35 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA00431; Sun, 25 Oct 1998 19:56:56 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA38380 for ; Sun, 25 Oct 1998 19:54:57 -0800 Received: from mailcity.com (fes-new.whowhere.com [209.185.123.154]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id TAA28022 for ; Sun, 25 Oct 1998 19:54:56 -0800 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Sun Oct 25 19:54:48 1998 Message-Id: Date: Sun, 25 Oct 1998 19:54:48 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Neil Hauser" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sent-Mail: on X-Sender-Ip: 153.34.189.53 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN To List. I learned something from Mr. Adam. I think he receives one hunded per cent on his test. I am going to forward his post to my computer lab teacher. >From Neil. On Sun, 25 Oct 1998 01:51:03 Aaron S. Hawley wrote: >Thanks Adam for the Info on signature files. Now that wasn't so bad now >was it Michael Ruder (he gave me crap for talking about signatures). but >now i think i learned something, and isn't what this Pine Discussion Forum >is all about learningin something about using Pine. And I would think >signatures have to do with Pine. we all have to deal with other peoples >signature so lets understand the ethics of signatures. That's just my >take on it. although i can sympathize with peoples annoyance that we are >making a huge discussions over signaturs. > >-- >Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ >University of Vermont__Millis 428__802.656.7396 > > > >Pine 3.96 E-Mailer on Zoo Unix Cluster_______________________________ >small,fast,simple,complex,free_________http://www.washington.edu/pine > >On Sat, 24 Oct 1998, Adam H. Kerman wrote: > >> Sven (Ken just forwarded) forgot to emphasize use of the delimiter: >> "-- " [two hyphens followed by a space on a line above the .sig] >> >> It's not a standard; it's a convention. It has nothing to do with routing >> messages through machines. It has everything to do with trying the patience of >> those who would read your message. >> >> I haven't been receiving e-mail long enough to recall, so I cannot speak to >> this from experience. From what I have read, in the beginning Mail compliant >> with Internet (and predessors) standards was relayed through uucp. Typically, >> but not always, the headers survived intact. >> >> However, Mail was often gatewayed to other systems like BITNET and FidoNET that >> followed different protocols. All of these systems were like uucp: store and >> forward. >> >> Also, the original mailing list server, LISTSERV, was written in Europe to >> distribute messages over the US BITNET. The purpose was to consolidate the >> sending of identical messages as much as possible to better utilize the use of >> extremely expensive resources, namely trans-Atlantic communications. >> >> LISTSERV only identified the name of the mailing list at first, not the author >> of the message. >> >> For all these reasons, it became a practice to include the author's name in the >> .sig. Today, none of these reasons exist anymore, and information in the .sig >> is either redundant or unnecessary. >> >> The real reason authors include .sigs is vanity or advertising. >> >> However, you may put any text you like into the body of a Mail message. If you >> follow the convention of use of "-- " as a delimiter and include no more than >> four lines of text, no one at all will complain. Four lines of text is >> generally considered to be "within reason" and won't irritate anyone. >> >> The following arguments are made against .sigs in general, and my use of the >> word "you" isn't aimed specifically at Aaron's new .sig. >> >> Yes, there can be gateways that munge headers these days, but they are called >> "broken". Rather than have everyone assume that repeating one's name in the >> .sig is necessary, it is up to the users of those gateways to take steps to fix >> them. It's their problem, not the rest of us. >> >> The rest of the information people typically unnecessary. We don't need to your >> phone number. We don't care to reach you by wireless, whether pager or >> cellular, and we aren't going to send you a fax. >> >> We know your e-mail address, and that's how we'll contact you if we choose to. >> We know your name: It's in your From line. (It's not? Then put it there.) >> >> It's lovely that you have a Web page. Is anything on it relevant to the Subject >> of the thread? Then make reference to it much earlier in your message. >> >> Are any of your 15 affiliations relevant to the arguments you made in your >> message? Unlikely. If you actually published a paper, cite it. If we want to, >> we'll read it and make our own judgement. >> >> And as far as those quotes go, yes, it was witty when the original author said >> it. You are repeating it over and over again. It's now trite. >> >> >> ----------------------------------------------------------------- >> For information about this mailing list, and its archives, see: >> http://www.washington.edu/pine/pine-info/ >> ----------------------------------------------------------------- >> > > Get your FREE E-mail at http://mailcity.lycos.com Get your PERSONALIZED START PAGE at http://personal.lycos.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Sun, 25 Oct 1998 22:40:27 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA16799 for ; Sun, 25 Oct 1998 22:40:25 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA22572; Sun, 25 Oct 1998 22:40:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA11897; Sun, 25 Oct 1998 22:39:12 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA30282 for ; Sun, 25 Oct 1998 22:37:24 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA05473 for ; Sun, 25 Oct 1998 22:37:23 -0800 Received: from fireball.control-risks.de (port253.koeln.ndh.net [195.94.92.253]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id HAA03158 for ; Mon, 26 Oct 1998 07:37:19 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id SAA14587; Sun, 25 Oct 1998 18:31:38 +0100 Message-Id: <19981025183137.A14328@fireball.control-risks.de> Date: Sun, 25 Oct 1998 18:31:37 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: limits on .sig (was: Auto respond) In-Reply-To: ; from Ian Hall-Beyer on Sun, Oct 25, 1998 at 09:32:55AM -0700 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Ian Hall-Beyer (manuka@rmi.net): > On Sun, 25 Oct 1998, Adam H. Kerman wrote: > > Please do not Cc the author when replying to his message on a mailing list > > or on a newsgroup. Please don't quote back the ENTIRE message. If you have > > a > > Then in that case, it would probably be a good idea if the list > administrators changed the list setup to add a "reply-to:" line to the > headers. Not at all, and if you finally decided to do a little voluntary reading instead of your usual, revolting whining, you might even get a clue why. > The way it's currently set up, if you do a reply in pine, Then use Gnus or mutt, but stop whining. > You either have to reply directyl to the author, or to the author and cc: to > the list. that, or go in and munge the addressees of the reply, which, quite > frankly, is a royal pain in the butt. There it is again... listen, dude, your "this sucks and isn't userfriendly" 'tude seriously pisses me off. If you don't like the way pine behaves, don't use it or write a patch - apart from being a nice program, pine also happens to be a free program. If you're too stoopid to do either, please show a little decency towards the innocent people on this list (which, after all is for technical problems and not your, like, intellectual deficiencies and stuff, huh-huh...) and quit whining. Just do it. Shut up and get a clue. Now. Thankyouverymuch. Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 01:59:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA19680 for ; Mon, 26 Oct 1998 01:59:03 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA22040; Mon, 26 Oct 1998 01:58:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA15528; Mon, 26 Oct 1998 01:57:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA52116 for ; Mon, 26 Oct 1998 01:55:07 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA14507 for ; Mon, 26 Oct 1998 01:55:02 -0800 Received: from localhost (mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) with SMTP id UAA02440; Mon, 26 Oct 1998 20:24:06 +1030 Message-Id: Date: Mon, 26 Oct 1998 20:24:06 +1030 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Sun, 25 Oct 1998, Adam H. Kerman wrote: > Reply-To is a header designed to be used by the composer of a message. Only > later was its use taken over by a few list owners who fail to acknowledge its > original utility. Where is your proof that it was designed for the exclusive use of the author of the original message? > Let's say, for my convenience, I have multiple mailboxes. Suppose I subscribe > to a mailing list and must post to the list using a specific From. I > participate on a thread that pertains to a subject I have a regular interest > in. It could be business or a hobby. Normally, I correspond with people using a > different From. > > So, I participate on the thread and set Reply-To to the mailbox to which I want > personal replies directed to. > > I'd say that I have a legitimate use for setting Reply-To myself. If you were Yes, you have a legitimate use. That is a reasonable thing to want to do. It is also reasonable for a list owner to want to do something that conflicts with what you want. > the list owner, you have decided that I may NOT set Reply-To. You instead > substitute your own judgment and have the server munge it to the list posting > address. This is where you get paranoid. There is a very good reason for list servers to set the Reply-To to point to the list. It is very annoying when replies go to originators with cc: to the list. Every response is duplicated, if people do just the natural thing in replying. Lists of recipients consisting of everone who ever contributed to a thread are built up, and still there is a cc. to the list. People who have forgotten that they ever contributed continue to get double mailings, firstly from the author and secondly from the list. Pointing Reply-To to the list fixes the problem. Responses then go to a single address, that of the mailing list, and that is how a mailing list is meant to work. Mail reflected from a mailing list must have a 'From:' identifying the author, but for the mailing list to work, your MUA must be instructed ignore it, to not reply to the 'From:' address but to Reply To another one. That is what 'Reply-To:' is for, get it? > You, the list owner, are doing something harmful. It's really not a moral question, you know. The mailing list software came along and set the Reply-To, as always. You had already set a Reply-to and it was obliterated by the new setting. That is all. Your remaining claims are silly enough not to need any response. Accept the policy of the list owner, or unsubscribe. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 03:19:28 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA21111 for ; Mon, 26 Oct 1998 03:19:27 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA23054; Mon, 26 Oct 1998 03:19:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA27090; Mon, 26 Oct 1998 03:18:26 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA37052 for ; Mon, 26 Oct 1998 03:16:22 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA19961 for ; Mon, 26 Oct 1998 03:16:21 -0800 Received: from fireball.control-risks.de (port242.koeln.ndh.net [195.94.92.242]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id MAA21001 for ; Mon, 26 Oct 1998 12:16:18 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id HAA15316; Mon, 26 Oct 1998 07:47:21 +0100 Message-Id: <19981026074721.A14729@fireball.control-risks.de> Date: Mon, 26 Oct 1998 07:47:21 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Cc'ing the author of a mailing list or News message (was: limits on .sig) In-Reply-To: ; from Adam H. Kerman on Sun, Oct 25, 1998 at 11:38:34AM -0600 References: <199810251714.MAA15446@zugzug.cfar.UMD.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Adam H. Kerman (ahk@chinet.chinet.com): > From: Adam Sulmicki > >The reason for this is that many ppl use mail filtering programs. For > >example in mine case, the mail for 'pine' goes to one folder and > >mail sent to me goes to different folder. > > You may filter incoming mail as you wish. I filter first by looking for replies > to messages I sent, not caring if they were personal e-mail or via a mailing > list. Or I look for Subjects containing threads I participated in. (Unlike in > News, which tries to maintain threads with Message-IDs, Mail tends to discard > earlier Message-IDs so that's not reliable.) Or I look for text unique to the > thread. If you get that many messages, use procmail's weighted scoring techniques or use Gnus with adaptive scoring. I got higher scores for follow-up's (Gnus treats mail and news alike) to myself. EOT. Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 04:52:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA21493 for ; Mon, 26 Oct 1998 04:52:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA24327; Mon, 26 Oct 1998 04:51:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA28676; Mon, 26 Oct 1998 04:51:05 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA60894 for ; Mon, 26 Oct 1998 04:49:08 -0800 Received: from hd1.vsnl.net.in (hd1.vsnl.net.in [202.54.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA23078 for ; Mon, 26 Oct 1998 04:48:54 -0800 Received: from hd1 ([202.54.30.108]) by hd1.vsnl.net.in (8.8.8/8.8.8) with SMTP id SAA28969 for ; Mon, 26 Oct 1998 18:17:02 +0500 (GMT+0500) Message-Id: <002001be00df$ed37b2b0$2806a8c0@hd1.vsnl.net.in> Date: Mon, 26 Oct 1998 18:25:34 +0530 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Dalip" To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01BE010E.05875E00" X-To: X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_001D_01BE010E.05875E00 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable UNSUBSCRIBE ------=_NextPart_000_001D_01BE010E.05875E00 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
UNSUBSCRIBE
------=_NextPart_000_001D_01BE010E.05875E00-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 05:07:05 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA13633 for ; Mon, 26 Oct 1998 05:07:04 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA24523; Mon, 26 Oct 1998 05:06:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA05057; Mon, 26 Oct 1998 05:05:52 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA35768 for ; Mon, 26 Oct 1998 05:04:02 -0800 Received: from hd1.vsnl.net.in (hd1.vsnl.net.in [202.54.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA23694 for ; Mon, 26 Oct 1998 05:03:58 -0800 Received: from hd1 ([202.54.30.108]) by hd1.vsnl.net.in (8.8.8/8.8.8) with SMTP id SAA15756 for ; Mon, 26 Oct 1998 18:32:08 +0500 (GMT+0500) Message-Id: <003901be00e2$08c10930$2806a8c0@hd1.vsnl.net.in> Date: Mon, 26 Oct 1998 18:40:40 +0530 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Chandu" To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01BE0110.218632A0" X-To: X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0036_01BE0110.218632A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable UNSUBSCRIBE ------=_NextPart_000_0036_01BE0110.218632A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

UNSUBSCRIBE

------=_NextPart_000_0036_01BE0110.218632A0-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 09:20:50 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA27320 for ; Mon, 26 Oct 1998 09:20:48 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA29975; Mon, 26 Oct 1998 09:20:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA21759; Mon, 26 Oct 1998 09:17:15 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA16332 for ; Mon, 26 Oct 1998 09:14:54 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA15230 for ; Mon, 26 Oct 1998 09:14:53 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id LAA19527 for ; Mon, 26 Oct 1998 11:14:48 -0600 Message-Id: Date: Mon, 26 Oct 1998 11:14:48 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN What part of "Do no Cc the author of a message if you reply to a mailing list or on News" is unclear? >From: Michael Talbot-Wilson >Date: Mon, 26 Oct 1998 20:24:06 +1030 (CST) >On Sun, 25 Oct 1998, Adam H. Kerman wrote: >>Reply-To is a header designed to be used by the composer of a message. Only >>later was its use taken over by a few list owners who fail to acknowledge its >>original utility. >Where is your proof that it was designed for the exclusive use of >the author of the original message? RFC # 822 STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES August 13, 1982 4.4. ORIGINATOR FIELDS The standard allows only a subset of the combinations possi- ble with the From, Sender, Reply-To, Resent-From, Resent-Sender, and Resent-Reply-To fields. The limitation is intentional. 4.4.3. REPLY-TO / RESENT-REPLY-TO This field provides a general mechanism for indicating any mailbox(es) to which responses are to be sent. Three typical uses for this feature can be distinguished. In the first case, the author(s) may not have regular machine-based mail- boxes and therefore wish(es) to indicate an alternate machine address. In the second case, an author may wish additional persons to be made aware of, or responsible for, replies. A somewhat different use may be of some help to "text message teleconferencing" groups equipped with automatic distribution services: include the address of that service in the "Reply- To" field of all messages submitted to the teleconference; then participants can "reply" to conference submissions to guarantee the correct distribution of any submission of their own. 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO For systems which automatically generate address lists for replies to messages, the following recommendations are made: o If the "Reply-To" field exists, then the reply should go to the addresses indicated in that field and not to the address(es) indicated in the "From" field. That's been an absolutely clear recommendation since 1982. >> Let's say, for my convenience, I have multiple mailboxes. Suppose I subscribe >> to a mailing list and must post to the list using a specific From. I >> participate on a thread that pertains to a subject I have a regular interest >> in. It could be business or a hobby. Normally, I correspond with people using a >> different From. >> >> So, I participate on the thread and set Reply-To to the mailbox to which I want >> personal replies directed to. >> >> I'd say that I have a legitimate use for setting Reply-To myself. >Yes, you have a legitimate use. That is a reasonable thing to want to do. >It is also reasonable for a list owner to want to do something that >conflicts with what you want. And according to the recommendation in the RFC I just posted, the author's wishes should be honored. >>If you were the list owner, you have decided that I may NOT set Reply-To. You >>instead substitute your own judgment and have the server munge it to the list >>posting address. >This is where you get paranoid. There is a very good reason for list servers >to set the Reply-To to point to the list. It is very annoying when replies go >to originators with cc: to the list. YOU are the one who did that. Just because pine behaves in a certain way when Reply-To is not present, just because many of us disagree with pine's behavior, we accept that as a limitation of pine and work around it. It is outrageous to blame YOUR personal bad behavior on either the mail client or the mailing list owner. You find it too inconvenient to send the keystrokes necessary to avoid sending duplicate messages? Change mail clients. You cannot demand that the rest of the world change reasonable behavior to accomodate your unreasonable attitude. >Every response is duplicated, if people do just the natural thing in replying. The natural thing is to fart in public, eat with our hands, pick our noses, and altogether violate standards of civilization. Observance of etiquette keeps us from killing each other, also natural behavior. The Internet is a shared resource which you don't pay for. It has its own standards of conduct. No one wants to talk to you if you do "just the natural thing". While it is unnatural to demonstrate common courtesy, do it anyway. >Mail reflected from a mailing list must have a 'From:' identifying >the author, but for the mailing list to work, your MUA must be >instructed ignore it, to not reply to the 'From:' address but to >Reply To another one. That is what 'Reply-To:' is for, get it? That's been my point for several messages on this thread. It's tool for the author's use. >> You, the list owner, are doing something harmful. >It's really not a moral question, you know. The mailing list >software came along and set the Reply-To, as always. You had >already set a Reply-to and it was obliterated by the new setting. >That is all. It's a violation of a 16-year-old recommendation. Many of us think it was well- intended then and should continue to guide us today. >Your remaining claims are silly enough not to need any response. >Accept the policy of the list owner, or unsubscribe. Explain why that doesn't apply to you. The policy of the owner of pine-info is that Reply-To is not set. Numerous people, including me, have asked that duplicates of replies to the list not be sent to us. The list owner's policy, then, is that YOU should cut the line containing the author's address from your reply if you compose in pine. Through your actions, you have made it clear that you don't like that policy and flaunt it. I expect you to immediately unsubscribe from this mailing list. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 10:14:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA00375 for ; Mon, 26 Oct 1998 10:14:39 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA04249; Mon, 26 Oct 1998 10:14:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA20135; Mon, 26 Oct 1998 10:12:09 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA24000 for ; Mon, 26 Oct 1998 10:10:04 -0800 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA23281 for ; Mon, 26 Oct 1998 10:10:02 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id NAA07822 for ; Mon, 26 Oct 1998 13:09:57 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 13:09:57 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Adam H. Kerman wrote: > 4.4.3. REPLY-TO / RESENT-REPLY-TO > > This field provides a general mechanism for indicating any > mailbox(es) to which responses are to be sent. Three typical > uses for this feature can be distinguished. In the first > case, the author(s) may not have regular machine-based mail- > boxes and therefore wish(es) to indicate an alternate machine > address. In the second case, an author may wish additional > persons to be made aware of, or responsible for, replies. A > somewhat different use may be of some help to "text message > teleconferencing" groups equipped with automatic distribution > services: include the address of that service in the "Reply- > To" field of all messages submitted to the teleconference; > then participants can "reply" to conference submissions to > guarantee the correct distribution of any submission of their > own. Did you even read this? Just what do you think "text message teleconferencing" groups are? Give it a rest. I doubgt seriously that the list maintainers are even considiering the change. If they are then you can review your decision to paticipate. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 10:31:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22130 for ; Mon, 26 Oct 1998 10:31:02 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02451; Mon, 26 Oct 1998 10:30:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA26674; Mon, 26 Oct 1998 10:28:36 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA30610 for ; Mon, 26 Oct 1998 10:26:29 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA23052 for ; Mon, 26 Oct 1998 10:26:29 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id NAA25637 for ; Mon, 26 Oct 1998 13:26:30 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 13:26:30 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Dude, you need to shut the fuck up. You don't have a fucking clue as to what you're talking about. On Mon, 26 Oct 1998, Darren Henderson wrote: > On Mon, 26 Oct 1998, Adam H. Kerman wrote: > > > 4.4.3. REPLY-TO / RESENT-REPLY-TO > > > > This field provides a general mechanism for indicating any > > mailbox(es) to which responses are to be sent. Three typical > > uses for this feature can be distinguished. In the first > > case, the author(s) may not have regular machine-based mail- > > boxes and therefore wish(es) to indicate an alternate machine > > address. In the second case, an author may wish additional > > persons to be made aware of, or responsible for, replies. A > > somewhat different use may be of some help to "text message > > teleconferencing" groups equipped with automatic distribution > > services: include the address of that service in the "Reply- > > To" field of all messages submitted to the teleconference; > > then participants can "reply" to conference submissions to > > guarantee the correct distribution of any submission of their > > own. > > > Did you even read this? Just what do you think "text message > teleconferencing" groups are? Give it a rest. I doubgt seriously that the > list maintainers are even considiering the change. If they are then you > can review your decision to paticipate. > -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 11:13:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA23757 for ; Mon, 26 Oct 1998 11:13:19 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA06055; Mon, 26 Oct 1998 11:13:06 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA24317; Mon, 26 Oct 1998 11:10:04 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA38414 for ; Mon, 26 Oct 1998 11:08:08 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA31795 for ; Mon, 26 Oct 1998 11:08:06 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id NAA21471 for ; Mon, 26 Oct 1998 13:08:04 -0600 Message-Id: Date: Mon, 26 Oct 1998 13:08:04 -0600 (CST) Reply-To: "Adam H. Kerman" Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Darren Henderson >Date: Mon, 26 Oct 1998 13:09:57 -0500 (EST) >Did you even read this? Just what do you think "text message >teleconferencing" groups are? Give it a rest. This gentleman is aware that he has no point to make that contradicts my own arguments. He engaged in selective editing of the text I had posted. The excerpts from RFC822 in 4.4.3 and 4.4.4 must be read together to understand them. Mr. Henderson deliberately ignored and deleted the recommendations found in 4.4.4. Read them yourselves and form your own opinion. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 11:45:57 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA32621 for ; Mon, 26 Oct 1998 11:45:55 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04985; Mon, 26 Oct 1998 11:45:50 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA26447; Mon, 26 Oct 1998 11:43:32 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA50294 for ; Mon, 26 Oct 1998 11:41:24 -0800 Received: from jasper.somtel.com (jasper.somtel.com [206.139.114.254]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04588 for ; Mon, 26 Oct 1998 11:41:23 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id OAA07940 for ; Mon, 26 Oct 1998 14:41:09 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 14:41:09 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Oh please...selective quoting indeed. I quoted back too much if anything, quoting is meant to provide a reference pont, a guide to give an indication to what my comment was addressing. Recall what I stated a few days ago about this (Reply-to) being a religous issue with some people. Tis a pointless argument. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 11:50:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA31535 for ; Mon, 26 Oct 1998 11:50:24 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA05150; Mon, 26 Oct 1998 11:50:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA10137; Mon, 26 Oct 1998 11:45:59 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA45308 for ; Mon, 26 Oct 1998 11:44:10 -0800 Received: from dormouse.syr.edu (root@dormouse.syr.edu [128.230.4.155]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04975 for ; Mon, 26 Oct 1998 11:44:09 -0800 Received: from dormouse.syr.edu (gmalling@localhost [127.0.0.1]) by dormouse.syr.edu (8.9.1/8.9.1) with ESMTP id OAA23716 for ; Mon, 26 Oct 1998 14:44:06 -0500 (EST) Message-Id: <199810261944.OAA23716@dormouse.syr.edu> Date: Mon, 26 Oct 1998 14:44:04 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Glenn A. Malling" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: Your message of "Mon, 26 Oct 1998 13:08:04 CST." MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----- =_aaaaaaaaaa0" Content-ID: <23698.909430329.0@dormouse.syr.edu> X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ------- =_aaaaaaaaaa0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23698.909430329.1@dormouse.syr.edu> Why argue about what the author of RFC822 intended when he has stated his intentions in public? Note well that RFC822 pre-dates mailing list managers as Mr. Crocker acknowledges. Now whether I will let YOU control ME is a question of possible interest to psycologists or sociologists, certainly not a technical issue. ;-) You could also note that the mailing list manager used by this mailing list does not munge the Reply-to: so the complaint is against some mail user agent(s). The DRUMS mailing list archive is available via anonymous IMAP. There are quite a few people who decline to give such control to others. You can read them for yourselves should you be interested. {cyrus.andrew.cmu.edu:143/anonymous}archive.[] -- Glenn A. Malling Syracuse University Computing Services +1 (315) 443-4111 220 Machinery Hall Syracuse, New York 13244-1260 Postmaster for SUnix and LISTSERV. ------- =_aaaaaaaaaa0 Content-Type: message/rfc822 Return-Path: Received: from dormouse.syr.edu (gmalling@dormouse.syr.edu [128.230.4.155]) by mailbox.syr.edu (8.9.1/8.9.1) with ESMTP id OAA10510 for ; Mon, 26 Oct 1998 14:18:53 -0500 (EST) Received: from localhost (gmalling@localhost) by dormouse.syr.edu (8.9.1/8.9.1) with ESMTP id OAA23681 for ; Mon, 26 Oct 1998 14:18:51 -0500 (EST) X-Authentication-Warning: dormouse.syr.edu: gmalling owned process doing -bs X-Received: from CS.UTK.EDU (CS.UTK.EDU [128.169.94.1]) by mail1.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id DAA08094 for ; Fri, 26 Sep 1997 03:20:30 -0400 (EDT) X-Received: from localhost (daemon@localhost) by CS.UTK.EDU with SMTP (cf v2.9s-UTK) id DAA24680; Fri, 26 Sep 1997 03:17:42 -0400 (EDT) X-Received: by CS.UTK.EDU (bulk_mailer v1.7); Fri, 26 Sep 1997 03:16:03 -0400 X-Received: by CS.UTK.EDU (cf v2.9s-UTK) id DAA24601; Fri, 26 Sep 1997 03:16:02 -0400 (EDT) X-Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by CS.UTK.EDU with ESMTP (cf v2.9s-UTK) id DAA24591; Fri, 26 Sep 1997 03:15:59 -0400 (EDT) X-Received: from dcrocker-omni (d70.netgate.net [205.214.160.106]) by mail.proper.com (8.8.7/8.7.3) with SMTP id AAA19063 for ; Fri, 26 Sep 1997 00:13:45 -0700 (PDT) Message-Id: <3.0.3.32.19970926001456.033f985c@ng.netgate.net> X-Sender: dcrocker@ng.netgate.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 26 Sep 1997 00:14:56 -0700 To: Drums@cs.utk.edu From: Dave Crocker Subject: Re: Reply-to, etc. In-Reply-To: <8025651D.003A1037.00@motorcity2.lotus.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ReSent-Date: Mon, 26 Oct 1998 14:18:37 -0500 (EST) ReSent-From: Glenn Malling ReSent-To: gmalling@mailbox.syr.edu ReSent-Subject: Re: Reply-to, etc. ReSent-Message-ID: X-UIDL: 1899fc308a4b8da4333d61499a451102 Folks, The Reply-to conundrum is all the more perplexing for the relative simplicity of the issues: Originators dictate alternate addresses and mailing lists needing to override default recipient system behaviors. Perhaps the main source of confusion is a bit of revisionistic reading going on. Perhaps the other main source is the considerable paucity of user-to-user email protocol features, so that none of us is all that used to modeling things like Reply-to as a protocol. But please don't get distracted. Yes, this is the stuff of protocols, albeit end-user to end-user. It very much does dictate bits over the wire. RFC822 Intent: Most of the relevant text in RFC 822 is every bit as vague to today's readers have observed, except that the ambiguity is blown away by one paragraph in particular: > o If the "Reply-To" field exists, then the reply should > go to the addresses indicated in that field and not to > the address(es) indicated in the "From" field. So, for all the possible confusion about the earlier references about where replies should be sent, this one paragraph gives very specific direction. The use of 'should' is the cause of my using the word "revisionistic". Yes, today's specifications use the word 'should' as guidance rather than dictum. Sorry but we weren't that precise way back when. Nonetheless, the intent behind From/Reply-to is quite specific: The originator of the message is directing that any reply which would be sent to address(es) in the From field must go to the address(s) listed in Reply-to. Reply-to has nothing to do with addresses in cc or To. Sorry, no, the originator is not politely making a suggestion. The originator is saying that they do not want replies to go to From. They want them to go to Reply-To. Now a respondent is free to engage in whatever socially deviant behavior they might wish and one suspects that the protocol police will be no more forceful about dealing with the transgression than they have been about email sillinesses in the past, but please don't confuse the lack of enforcement with a lack of clarity in the originator's intent. All of this is made sadly worse by the group communication mess. Yes, this part of the system IS a mess. Perhaps the major problem is that we have no way to indicate that an address is a list rather than an individual. To the extent that we are trying to add a facility which clearly and cleanly directs that a reply intended for the entire set of addresses (From, To, CC) go to that one address, I suggest we consider a new header as several have suggested, though that won't solve the problem, really, given the distributed nature of list services. Still, it would be better than what we have today. List developers have been desperate to deal with legitimate problems and found that the Internet mail facilities did not give them the right tools, so they jumped into overloading Reply-to. They chose what was available but that does not make the choice right. The right choice is to leave Reply-to to its original intent and deal with the group override through a separate mechanism. d/ -------------------- Dave Crocker +1 408 246 8253 Brandenburg Consulting fax: +1 408 249 6205 675 Spruce Dr. dcrocker@brandenburg.com Sunnyvale, CA 94086 USA http://www.brandenburg.com Internet Mail Consortium info@imc.org, http://www.imc.org ------- =_aaaaaaaaaa0-- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 12:23:25 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA28807 for ; Mon, 26 Oct 1998 12:23:23 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA08570; Mon, 26 Oct 1998 12:23:09 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id MAA12257; Mon, 26 Oct 1998 12:20:35 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id MAA50862 for ; Mon, 26 Oct 1998 12:18:34 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id MAA09787 for ; Mon, 26 Oct 1998 12:18:32 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id OAA22624 for ; Mon, 26 Oct 1998 14:18:29 -0600 Message-Id: Date: Mon, 26 Oct 1998 14:18:29 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Darren Henderson >Date: Mon, 26 Oct 1998 14:41:09 -0500 (EST) >Oh please...selective quoting indeed. For anyone with an open mind, this is what he selectively deleted. As you can see, it was written with broadly enough that it still applies today. I interpret this to mean that if the author of the message has set Reply-To, then the list owner should not reset it to the list-posting address. I find this recommendation to be unambiguous. 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO For systems which automatically generate address lists for replies to messages, the following recommendations are made: o If the "Reply-To" field exists, then the reply should go to the addresses indicated in that field and not to the address(es) indicated in the "From" field. >I quoted back too much if anything, quoting is meant to provide a reference >pont, a guide to give an indication to what my comment was addressing. Since you failed to address this, your arguments are inadequate. >Recall what I stated a few days ago about this (Reply-to) being a religous >issue with some people. Tis a pointless argument. You've asked me to support my position; I've done so. You only supported your position by cheating. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 13:14:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA26839 for ; Mon, 26 Oct 1998 13:14:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA10088; Mon, 26 Oct 1998 13:14:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id NAA26578; Mon, 26 Oct 1998 13:11:12 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id NAA43214 for ; Mon, 26 Oct 1998 13:09:16 -0800 Received: from jasper.somtel.com (IDENT:darren@jasper.somtel.com [206.139.114.254]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id NAA14649 for ; Mon, 26 Oct 1998 13:09:15 -0800 Received: from localhost (darren@localhost) by jasper.somtel.com (8.8.5/8.6.12) with ESMTP id QAA08074 for ; Mon, 26 Oct 1998 16:09:10 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 16:09:09 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Darren Henderson To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Adam H. Kerman wrote: > You've asked me to support my position; I've done so. You only supported your > position by cheating. I have never asked you to support your position though other members of the list have I believe. As for the rest... I won't dignify that childish accusation with a response other then to say welcome you to my /dev/null... Procmail is a wonderful tool. ______________________________________________________________________ Darren Henderson darren@jasper.somtel.com Help fight junk e-mail, visit http://www.cauce.org/ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 14:22:58 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA03059 for ; Mon, 26 Oct 1998 14:22:57 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10024; Mon, 26 Oct 1998 14:22:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA07114; Mon, 26 Oct 1998 14:19:20 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA49436 for ; Mon, 26 Oct 1998 14:17:28 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id OAA12183 for ; Mon, 26 Oct 1998 14:17:27 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.808A5940@smtpgate.uvm.edu>; Mon, 26 Oct 1998 17:17:26 -0500 Message-Id: Date: Mon, 26 Oct 1998 17:17:30 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: conclusion MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN so have we come to a conclusion that the list does not have the right to change the reply-to value in the header. i don't understand quite all the lingo you debaters are using, and also it is hard for me to keep track of who said what. A -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 17:44:37 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA07239 for ; Mon, 26 Oct 1998 17:44:36 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA16183; Mon, 26 Oct 1998 17:44:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA29165; Mon, 26 Oct 1998 17:42:15 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA19498 for ; Mon, 26 Oct 1998 17:40:03 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA20803 for ; Mon, 26 Oct 1998 17:40:03 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id SAA14381 for ; Mon, 26 Oct 1998 18:40:02 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id SAA08867 for ; Mon, 26 Oct 1998 18:37:13 -0700 (MST) Message-Id: Date: Mon, 26 Oct 1998 19:32:40 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Ken Woods wrote: > Dude, you need to shut the [BLEEP] up. > You don't have a [BLEEP] clue as to what you're talking about. Ah, yes, I love the internet, where we can have adult discussions and really adult responses. Uh huh. Two words: GROW UP. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 17:46:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA07658 for ; Mon, 26 Oct 1998 17:46:07 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA17628; Mon, 26 Oct 1998 17:46:01 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA16795; Mon, 26 Oct 1998 17:44:44 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA54146 for ; Mon, 26 Oct 1998 17:42:49 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA20308 for ; Mon, 26 Oct 1998 17:42:49 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id SAA14554; Mon, 26 Oct 1998 18:42:48 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id SAA09898; Mon, 26 Oct 1998 18:39:58 -0700 (MST) Message-Id: Date: Mon, 26 Oct 1998 19:35:26 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Adam H. Kerman wrote: > I interpret this to mean that if the author of the message has set Reply-To, > then the list owner should not reset it to the list-posting address. I find > this recommendation to be unambiguous. > > 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO > > For systems which automatically generate address lists for > replies to messages, the following recommendations are made: > > o If the "Reply-To" field exists, then the reply should > go to the addresses indicated in that field and not to > the address(es) indicated in the "From" field. > Read again. All this is saying is that if there is a Reply-to field, that the client should direct the replies to it instead of what's in the from field. that is ALL that says. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 18:26:07 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA08473 for ; Mon, 26 Oct 1998 18:26:06 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA18331; Mon, 26 Oct 1998 18:26:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA24558; Mon, 26 Oct 1998 18:24:07 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA42992 for ; Mon, 26 Oct 1998 18:22:17 -0800 Received: from mailcity.com (fes-new.whowhere.com [209.185.123.154]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id SAA26176 for ; Mon, 26 Oct 1998 18:22:16 -0800 Received: from Unknown/Local ([?.?.?.?]) by mailcity.com; Mon Oct 26 18:21:57 1998 Message-Id: Date: Mon, 26 Oct 1998 18:21:57 -0700 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Neil Hauser" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Sent-Mail: on X-Expiredinmiddle: true X-Sender-Ip: 140.198.26.38 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ? What is the big deal? I thought you people, you guys were software engineers or developers. I used my mouse to click reply so I could copy the text below. I just changed the to address because the information documents say post to list and instruct to serv. I thought it was an exception to carbon copy an email. Can you email someone? I do not want anyone to leave the list because of this! Mr. Adam I agreed with everything you wrote. I thought you were a real expert in computer language. But that one sentence I expect you to.... I mean does it matter? How can anyone cheat a computer? Oh yeah I got another problem. The advert. The instructions say when instructing listproc print END before the free advert. But this email program site, mailcity, has Carnegie Mellon written all over it. I feel bad enough myself but I do not want to worry someone else about it. The Pine program is on a UNIX platform. It is a different version. I did not download the program. It is part of the school course. I just need the course credit. End of Message. On Mon, 26 Oct 1998 11:14:48 Adam H. Kerman wrote: >What part of "Do no Cc the author of a message if you reply to a mailing list >or on News" is unclear? > >>From: Michael Talbot-Wilson >>Date: Mon, 26 Oct 1998 20:24:06 +1030 (CST) > >>On Sun, 25 Oct 1998, Adam H. Kerman wrote: > >>>Reply-To is a header designed to be used by the composer of a message. Only >>>later was its use taken over by a few list owners who fail to acknowledge its >>>original utility. > >>Where is your proof that it was designed for the exclusive use of >>the author of the original message? > > RFC # 822 > > STANDARD FOR THE FORMAT OF > > ARPA INTERNET TEXT MESSAGES > > August 13, 1982 > > 4.4. ORIGINATOR FIELDS > > The standard allows only a subset of the combinations possi- > ble with the From, Sender, Reply-To, Resent-From, Resent-Sender, > and Resent-Reply-To fields. The limitation is intentional. > > 4.4.3. REPLY-TO / RESENT-REPLY-TO > > This field provides a general mechanism for indicating any > mailbox(es) to which responses are to be sent. Three typical > uses for this feature can be distinguished. In the first > case, the author(s) may not have regular machine-based mail- > boxes and therefore wish(es) to indicate an alternate machine > address. In the second case, an author may wish additional > persons to be made aware of, or responsible for, replies. A > somewhat different use may be of some help to "text message > teleconferencing" groups equipped with automatic distribution > services: include the address of that service in the "Reply- > To" field of all messages submitted to the teleconference; > then participants can "reply" to conference submissions to > guarantee the correct distribution of any submission of their > own. > > 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO > > For systems which automatically generate address lists for > replies to messages, the following recommendations are made: > > o If the "Reply-To" field exists, then the reply should > go to the addresses indicated in that field and not to > the address(es) indicated in the "From" field. > >That's been an absolutely clear recommendation since 1982. > >>> Let's say, for my convenience, I have multiple mailboxes. Suppose I subscribe >>> to a mailing list and must post to the list using a specific From. I >>> participate on a thread that pertains to a subject I have a regular interest >>> in. It could be business or a hobby. Normally, I correspond with people using a >>> different From. >>> >>> So, I participate on the thread and set Reply-To to the mailbox to which I want >>> personal replies directed to. >>> >>> I'd say that I have a legitimate use for setting Reply-To myself. > >>Yes, you have a legitimate use. That is a reasonable thing to want to do. > >>It is also reasonable for a list owner to want to do something that >>conflicts with what you want. > >And according to the recommendation in the RFC I just posted, the author's >wishes should be honored. > >>>If you were the list owner, you have decided that I may NOT set Reply-To. You >>>instead substitute your own judgment and have the server munge it to the list >>>posting address. > >>This is where you get paranoid. There is a very good reason for list servers >>to set the Reply-To to point to the list. It is very annoying when replies go >>to originators with cc: to the list. > >YOU are the one who did that. Just because pine behaves in a certain way when >Reply-To is not present, just because many of us disagree with pine's behavior, >we accept that as a limitation of pine and work around it. > >It is outrageous to blame YOUR personal bad behavior on either the mail client >or the mailing list owner. > >You find it too inconvenient to send the keystrokes necessary to avoid sending >duplicate messages? Change mail clients. You cannot demand that the rest of the >world change reasonable behavior to accomodate your unreasonable attitude. > >>Every response is duplicated, if people do just the natural thing in replying. > >The natural thing is to fart in public, eat with our hands, pick our noses, and >altogether violate standards of civilization. Observance of etiquette keeps us >from killing each other, also natural behavior. > >The Internet is a shared resource which you don't pay for. It has its own >standards of conduct. No one wants to talk to you if you do "just the natural >thing". While it is unnatural to demonstrate common courtesy, do it anyway. > >>Mail reflected from a mailing list must have a 'From:' identifying >>the author, but for the mailing list to work, your MUA must be >>instructed ignore it, to not reply to the 'From:' address but to >>Reply To another one. That is what 'Reply-To:' is for, get it? > >That's been my point for several messages on this thread. It's tool for the >author's use. > >>> You, the list owner, are doing something harmful. > >>It's really not a moral question, you know. The mailing list >>software came along and set the Reply-To, as always. You had >>already set a Reply-to and it was obliterated by the new setting. >>That is all. > >It's a violation of a 16-year-old recommendation. Many of us think it was well- >intended then and should continue to guide us today. > >>Your remaining claims are silly enough not to need any response. >>Accept the policy of the list owner, or unsubscribe. > >Explain why that doesn't apply to you. The policy of the owner of pine-info is >that Reply-To is not set. Numerous people, including me, have asked that >duplicates of replies to the list not be sent to us. > >The list owner's policy, then, is that YOU should cut the line containing the >author's address from your reply if you compose in pine. Through your actions, >you have made it clear that you don't like that policy and flaunt it. > >I expect you to immediately unsubscribe from this mailing list. > > Get your FREE E-mail at http://mailcity.lycos.com Get your PERSONALIZED START PAGE at http://personal.lycos.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 18:57:54 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA08201 for ; Mon, 26 Oct 1998 18:57:54 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA18782; Mon, 26 Oct 1998 18:57:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA14571; Mon, 26 Oct 1998 18:56:23 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA61444 for ; Mon, 26 Oct 1998 18:54:33 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA27598 for ; Mon, 26 Oct 1998 18:54:32 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id VAA28232 for ; Mon, 26 Oct 1998 21:54:36 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 21:54:36 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Ian Hall-Beyer wrote: > On Mon, 26 Oct 1998, Ken Woods wrote: > > > Dude, you need to shut the [BLEEP] up. > > You don't have a [BLEEP] clue as to what you're talking about. > > Ah, yes, I love the internet, where we can have adult discussions and > really adult responses. Uh huh. > > Two words: > > GROW UP. Five words: Fuck off, nobody asked you. -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 19:34:17 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA07711 for ; Mon, 26 Oct 1998 19:34:16 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA19215; Mon, 26 Oct 1998 19:34:10 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA26792; Mon, 26 Oct 1998 19:32:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA45434 for ; Mon, 26 Oct 1998 19:30:53 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA18024 for ; Mon, 26 Oct 1998 19:30:52 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id VAA28359 for ; Mon, 26 Oct 1998 21:30:51 -0600 Message-Id: Date: Mon, 26 Oct 1998 21:30:51 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Why is this such a difficult concept for everyone on this list? Don't Cc me! >From: Ian Hall-Beyer >Date: Mon, 26 Oct 1998 19:35:26 -0700 (MST) >On Mon, 26 Oct 1998, Adam H. Kerman wrote: >>I interpret this to mean that if the author of the message has set Reply-To, >>then the list owner should not reset it to the list-posting address. I find >>this recommendation to be unambiguous. >> 4.4.4. AUTOMATIC USE OF FROM / SENDER / REPLY-TO >> For systems which automatically generate address lists for >> replies to messages, the following recommendations are made: >> o If the "Reply-To" field exists, then the reply should >> go to the addresses indicated in that field and not to >> the address(es) indicated in the "From" field. >Read again. All this is saying is that if there is a Reply-to field, that >the client should direct the replies to it instead of what's in the from >field. that is ALL that says. If the author has set Reply-To, replies are directed to that address. So if the list owner overwrites it, it won't go to the address indicated in that field. That violates the recommendation. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 20:07:21 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA30126 for ; Mon, 26 Oct 1998 20:07:20 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA19630; Mon, 26 Oct 1998 20:07:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA22559; Mon, 26 Oct 1998 20:06:10 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA30210 for ; Mon, 26 Oct 1998 20:04:20 -0800 Received: from post5.inre.asu.edu (post5.inre.asu.edu [129.219.110.86]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA02684 for ; Mon, 26 Oct 1998 20:04:17 -0800 Received: from general4.asu.edu by asu.edu (PMDF V5.1-12 #24133) with ESMTP id <01J3FV5BAMY48WWVSI@asu.edu> for pine-info@u.washington.edu; Mon, 26 Oct 1998 21:04:15 MST Received: from localhost (localhost [127.0.0.1]) by general4.asu.edu (8.9.1/8.9.1) with SMTP id VAA25364 for ; Mon, 26 Oct 1998 21:04:14 -0700 (MST) Message-Id: Date: Mon, 26 Oct 1998 21:04:13 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: jvan@asu.edu To: Pine Discussion Forum Subject: I want a signature line MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Sender: jvanasu@general4.asu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, Can you tell me how to include a permanent signature line with my pine messages? I'd appreciate the info. I can't find it in the help text. for now, jvan ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 20:21:40 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA09180 for ; Mon, 26 Oct 1998 20:21:39 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA19870; Mon, 26 Oct 1998 20:21:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA17537; Mon, 26 Oct 1998 20:20:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA60484 for ; Mon, 26 Oct 1998 20:18:43 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA03936 for ; Mon, 26 Oct 1998 20:18:43 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id XAA28753 for ; Mon, 26 Oct 1998 23:18:47 -0500 (EST) Message-Id: Date: Mon, 26 Oct 1998 23:18:46 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998 jvan@asu.edu wrote: > Hi, > Can you tell me how to include a permanent signature line with my pine > messages? I'd appreciate the info. I can't find it in the help text. > for now, > jvan Did you even _try_ reading the FAQ??? http://www.washington.edu/pine/faq/custom.html#xtocid561245 -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 21:52:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA31053 for ; Mon, 26 Oct 1998 21:52:03 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA19597; Mon, 26 Oct 1998 21:51:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA02281; Mon, 26 Oct 1998 21:50:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA23330 for ; Mon, 26 Oct 1998 21:48:58 -0800 Received: from tilmax.tatainfotech.co.in (tilmax.tatainfotech.co.in [202.54.16.130]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA09987 for ; Mon, 26 Oct 1998 21:48:54 -0800 Received: from seepzmail.in.tatainfotech.com (163-122-3222.unisys.com [163.122.32.22]) by tilmax.tatainfotech.co.in (8.7.4/8.7.3) with SMTP id LAA14950 for ; Tue, 27 Oct 1998 11:02:31 +0530 Received: from seepzmail by seepzmail.in.tatainfotech.com (8.6.10/SMI-4.1) id FAA29518; Tue, 27 Oct 1998 05:44:15 GMT Message-Id: Date: Tue, 27 Oct 1998 11:14:14 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nayan Jain To: Pine Discussion Forum Subject: Underline / Reversing / Blinking .. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: nayan.jain@seepzmail X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi All, I have seen some people sending me mails in pine with some words underlined...(it was underlined the same way as we do it in MS-WORD) I want to know how this can be done ? I want to send a mail to someone with some words underlined...or in reverse video...so that when he opens his mail in pine(UNIX) he should get those words as underlined or blinking. Thanks in Advance Nayan...! "No bird soars too high if he soars with his own wings." -William Blake ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 23:07:55 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA00507 for ; Mon, 26 Oct 1998 23:07:54 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA22068; Mon, 26 Oct 1998 23:07:48 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA28857; Mon, 26 Oct 1998 23:06:31 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA19554 for ; Mon, 26 Oct 1998 23:04:38 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id XAA15755 for ; Mon, 26 Oct 1998 23:04:38 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.26422AE0@smtpgate.uvm.edu>; Tue, 27 Oct 1998 2:04:37 -0500 Message-Id: Date: Tue, 27 Oct 1998 02:04:52 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: Underline / Reversing / Blinking .. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN what! i didn't know this could be done! i use pc-pine. maybe that's why. -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine On Tue, 27 Oct 1998, Nayan Jain wrote: > Date: Tue, 27 Oct 1998 11:14:14 +0530 (IST) > From: Nayan Jain > To: Pine Discussion Forum > Subject: Underline / Reversing / Blinking .. > > Hi All, > > I have seen some people sending me mails in pine with some words > underlined...(it was underlined the same way as we do it in MS-WORD) > > I want to know how this can be done ? > > I want to send a mail to someone with some words underlined...or in > reverse video...so that when he opens his mail in pine(UNIX) he should get > those words as underlined or blinking. > > Thanks in Advance > Nayan...! > > "No bird soars too high if he soars with his own wings." > -William Blake > > > ----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ > ----------------------------------------------------------------- > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 23:12:04 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA11196 for ; Mon, 26 Oct 1998 23:12:03 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA20707; Mon, 26 Oct 1998 23:11:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA29050; Mon, 26 Oct 1998 23:11:06 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA40340 for ; Mon, 26 Oct 1998 23:09:21 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id XAA17791 for ; Mon, 26 Oct 1998 23:09:21 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.CED78420@smtpgate.uvm.edu>; Tue, 27 Oct 1998 2:09:20 -0500 Message-Id: Date: Tue, 27 Oct 1998 02:09:35 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN ken, you need a serious attitued adjustment. lighten up. i think you need a special someone in your life to take some stress off. cause your CPU just ain't doing the trick. On Mon, 26 Oct 1998, Ken Woods wrote: > > Hi, > > Can you tell me how to include a permanent signature line with my pine > > messages? I'd appreciate the info. I can't find it in the help text. > > for now, > > jvan > > Did you even _try_ reading the FAQ??? > > http://www.washington.edu/pine/faq/custom.html#xtocid561245 > > -- > Ken Woods > kwoodskens.com On Mon, 26 Oct 1998, Ken Woods wrote: > On Mon, 26 Oct 1998, Ian Hall-Beyer wrote: > > > On Mon, 26 Oct 1998, Ken Woods wrote: > > > > > Dude, you need to shut the [BLEEP] up. > > > You don't have a [BLEEP] clue as to what you're talking about. > > > > Ah, yes, I love the internet, where we can have adult discussions and > > really adult responses. Uh huh. > > > > Two words: > > > > GROW UP. > > Five words: > > Fuck off, nobody asked you. > > -- > Ken Woods > kwoodskens.com -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Mon, 26 Oct 1998 23:19:25 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA07935 for ; Mon, 26 Oct 1998 23:19:24 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA20841; Mon, 26 Oct 1998 23:19:18 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA29264; Mon, 26 Oct 1998 23:18:34 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA19606 for ; Mon, 26 Oct 1998 23:16:50 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA16766 for ; Mon, 26 Oct 1998 23:16:49 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id CAA29470 for ; Tue, 27 Oct 1998 02:16:49 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 02:16:49 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I just hate stupidity, and lazy people. Please realize that there is a difference between being uneducated, and being lazy and stupid. If you have a question, read the FAQ. If 100 people are telling you not to cc: them on messages, then don't. Simple. On Tue, 27 Oct 1998, Aaron S. Hawley wrote: > ken, you need a serious attitued adjustment. lighten up. i think you > need a special someone in your life to take some stress off. cause your > CPU just ain't doing the trick. > > On Mon, 26 Oct 1998, Ken Woods wrote: > > > > Hi, > > > Can you tell me how to include a permanent signature line with my pine > > > messages? I'd appreciate the info. I can't find it in the help text. > > > for now, > > > jvan > > > > Did you even _try_ reading the FAQ??? > > > > http://www.washington.edu/pine/faq/custom.html#xtocid561245 > > > > -- > > Ken Woods > > kwoodskens.com > > On Mon, 26 Oct 1998, Ken Woods wrote: > > > > > > On Mon, 26 Oct 1998, Ian Hall-Beyer wrote: > > > > > On Mon, 26 Oct 1998, Ken Woods wrote: > > > > > > > Dude, you need to shut the [BLEEP] up. > > > > You don't have a [BLEEP] clue as to what you're talking about. > > > > > > Ah, yes, I love the internet, where we can have adult discussions and > > > really adult responses. Uh huh. > > > > > > Two words: > > > > > > GROW UP. > > > > Five words: > > > > Fuck off, nobody asked you. > > > > -- > > Ken Woods > > kwoodskens.com > > > -- > Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ > University of Vermont__802.656.7396__Millis 428 > > PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free > ______________________________________http://www.washington.edu/pine > > -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 00:34:07 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA01670 for ; Tue, 27 Oct 1998 00:34:06 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA21637; Tue, 27 Oct 1998 00:33:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA25605; Tue, 27 Oct 1998 00:33:08 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA23432 for ; Tue, 27 Oct 1998 00:31:17 -0800 Received: from dosa.cisco.com (dosa.cisco.com [192.122.173.24]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA07551 for ; Tue, 27 Oct 1998 00:31:15 -0800 Received: from dosa.cisco.com (dosa.cisco.com [192.122.173.24]) by dosa.cisco.com (8.8.4-Cisco.1/8.6.5) with SMTP id OAA10448; Tue, 27 Oct 1998 14:02:04 +0530 (IST) Message-Id: Date: Tue, 27 Oct 1998 14:02:04 +0530 (IST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: titthoma@cisco.com To: Pine Discussion Forum Subject: please...don't send useless mails. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Aaron S. Hawley" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN hi, See ,What the hell are u guys doing out there? WE (I mean those who have subscribed to the list) simply don't like getting useless mails in our boxes. I think this is not a place for settling personal scores. Do it by sending personal mails, please..... if this tit for tat mail series is going to continue.. I think lot of us will think to sign off. Dear listmaster ...it's time to put some thought. tito thomas. ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* h c what does "it" mean t|o s|o in the sentence t|||m i|||. "What time is it?"? .:ti||||a@c||||com:. ~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 02:17:55 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA07917 for ; Tue, 27 Oct 1998 02:17:53 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA23032; Tue, 27 Oct 1998 02:17:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA27341; Tue, 27 Oct 1998 02:16:55 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA34006 for ; Tue, 27 Oct 1998 02:14:15 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA25175 for ; Tue, 27 Oct 1998 02:14:13 -0800 Received: from fireball.control-risks.de (port253.koeln.ndh.net [195.94.92.253]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id LAA23335 for ; Tue, 27 Oct 1998 11:14:10 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id JAA19092; Tue, 27 Oct 1998 09:28:31 +0100 Message-Id: <19981027092831.C18325@fireball.control-risks.de> Date: Tue, 27 Oct 1998 09:28:31 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: ; from Aaron S. Hawley on Tue, Oct 27, 1998 at 02:09:35AM -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Aaron S. Hawley (ashawley@zoo.uvm.edu): > On Mon, 26 Oct 1998, Ken Woods wrote: > > > Can you tell me how to include a permanent signature line with my pine > > > messages? I'd appreciate the info. I can't find it in the help text. > > > for now, > > > > Did you even _try_ reading the FAQ??? > > ken, you need a serious attitued adjustment. lighten up. i think you > need a special someone in your life to take some stress off. cause your > CPU just ain't doing the trick. Good morning, NT-luser, o your quotes are totally broken o your spelling is so seriously broken that this is not a spelling flame o you are so fscking clueless that you should spent a *lot* of time reading the basic documents on email o your whining luser attitude is a serious annoyance Here are the rules again: o this is a closed mailing list for technical problems o luser problems are to be dealt with in o new users are required to read the FAQ, the user guide and the online help to earn to right to whine And here are the first three commandments again: o thou shalt read thy fuckynge manual o thou shalt not whine o thou shalt not suck Got it? Now get out of my life. Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 02:19:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA14543 for ; Tue, 27 Oct 1998 02:19:37 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA23054; Tue, 27 Oct 1998 02:19:31 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA27400; Tue, 27 Oct 1998 02:18:47 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA44770 for ; Tue, 27 Oct 1998 02:14:16 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA26711 for ; Tue, 27 Oct 1998 02:14:15 -0800 Received: from fireball.control-risks.de (port253.koeln.ndh.net [195.94.92.253]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id LAA23342 for ; Tue, 27 Oct 1998 11:14:12 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id LAA19169; Tue, 27 Oct 1998 11:14:44 +0100 Message-Id: <19981027111443.D18325@fireball.control-risks.de> Date: Tue, 27 Oct 1998 11:14:43 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Underline / Reversing / Blinking .. In-Reply-To: ; from Aaron S. Hawley on Tue, Oct 27, 1998 at 02:04:52AM -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Aaron S. Hawley (ashawley@zoo.uvm.edu): > On Tue, 27 Oct 1998, Nayan Jain wrote: You fscked up your quotes again, idiot. And you didn't crop them, either, so everyone on the list has to suffer Mrs Jain's braindamaged crap again, this time after scrolling yours. Good job, NT luser, really... > > I have seen some people sending me mails in pine with some words > > underlined...(it was underlined the same way as we do it in MS-WORD) > > > > I want to know how this can be done ? No, you don't. Check the archives of this mailing list to find out why. You could send ansi escape sequences but it would be a very, very braindead idea. > > I want to send a mail to someone with some words underlined...or in > > reverse video...so that when he opens his mail in pine(UNIX) he should get > > those words as underlined or blinking. Wise up, honey, it's _not_ UNIX. One of these days, I'll find out just /what/ it is that makes things like you invoke this trademarked four-letter-word every time you think (?) something magical is happening. Anyway, it doesn't work with pine, but it does work with Gnus (which also displays smilies), but if you had been using mail for more than 53 minutes, you would *know* that in this paragraph, there is underlining, italicising, and boldfacing. Blinking is a sure sign of a deseased mind. > what! i didn't know this could be done! Guess what, tosser, this is just the tip of the iceberg of your ignorance. > i use pc-pine. We know. We also understand. We don't forgive, though. > maybe that's why. No, it's because you're an annoying, whining, clueless idiot. So, let me rephrase my hints for you Ken Style: READ THE FUCKING MANUAL READ THE FUCKING FAQ READ THE FUCKING ARCHIVE CHECK THE FUCKING LINKS [1] HTH, Robin Footnotes: [1] www.math.fu-berlin/~guckes/pine/#outbound -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 03:24:34 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA15955 for ; Tue, 27 Oct 1998 03:24:33 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA25180; Tue, 27 Oct 1998 03:24:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id DAA16029; Tue, 27 Oct 1998 03:23:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id DAA45450 for ; Tue, 27 Oct 1998 03:21:46 -0800 Received: from au.dk (au.dk [130.225.9.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id DAA27794 for ; Tue, 27 Oct 1998 03:21:43 -0800 Received: from localhost (etnojens@localhost) by au.dk (8.8.4/8.8.4) with SMTP id MAA17323 for ; Tue, 27 Oct 1998 12:18:47 +0100 (MET) Message-Id: Date: Tue, 27 Oct 1998 12:18:46 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jens Kjaerulff To: Pine Discussion Forum Subject: How to append to top of document? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: etnojens@au X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I hope this is the right place to ask: In Pine, when I export a mail to an existing file, it gets appended to the bottom of the document. How do I change this so that it get appended to the top instead? Please mail reply directly to: etnojens@au.dk Thank you for your help ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 04:09:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA14079 for ; Tue, 27 Oct 1998 04:09:22 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA24459; Tue, 27 Oct 1998 04:09:14 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA09985; Tue, 27 Oct 1998 04:07:49 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA19518 for ; Tue, 27 Oct 1998 04:05:57 -0800 Received: from pump2.york.ac.uk (pump2.york.ac.uk [144.32.128.12]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA16603 for ; Tue, 27 Oct 1998 04:05:55 -0800 Received: from pippin.york.ac.uk (pippin.york.ac.uk [144.32.128.9]) by pump2.york.ac.uk (8.8.7/8.8.7) with ESMTP id MAA25456; Tue, 27 Oct 1998 12:05:39 GMT Message-Id: <717707.3118478737@pippin.york.ac.uk> Date: Tue, 27 Oct 1998 12:05:37 +0000 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Mike Brudenell To: Pine Discussion Forum Subject: Re: How to append to top of document? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-To: Jens Kjaerulff X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Greetings - --On Tue, Oct 27, 1998 12:18 pm +0100 Jens Kjaerulff wrote: > I hope this is the right place to ask: Hmmmm.... strictly speaking you should be asking in the comp.mail.pine Usenet News group instead. As I recall that is where general user-level requests for help should go, whereas the Pine-Info mailing list is really more for discussion about problems administrators experience setting up or configuring Pine and discussion of bugs etc. Be warned that there seem to be some very bolshy people around on the Pine-Info list at present, so you may get a few less-than-pleasant replies. :-( > In Pine, when I export a mail to an existing file, it gets appended to the > bottom of the document. How do I change this so that it get appended to > the top instead? There isn't an easy way to do this. If you pause for a moment and consider an existing text file you should be able to see that adding text to the end of it (appending) is a very easy and cheap operation: * Open file for output, but DON'T truncate (empty) it; * Position write-pointer at end of data; * Write out new data; * Close file. In contrast prepending (put new material at the start of the file) or elsewhere in the file (inserting) is expensive, involving reading in the data already in the file, writing out the new material, then re-writing out the previous contents. It is also risk-prone: for example if you run out of disk space during an APPEND Pine can truncate the file back to its original size and its content is left intact (but without the new material, which it can warn you about). However if you are prepending/inserting then your quota might run out before the file's previous content is completely written out. The result would be a corrupted file which MIGHT have (some of) the new material, and would DEFINITELY have lost some of the materialthat used to be in there and you thought safe. (There are ways around this, but it involves using even more disk space to write a temporary copy of the file which is then renamed over the old one.) If you REALLY need to insert new stuff at the beginning of the file you can probably use Pine's Pipe command to achieve the effect. (But that, as they say, is left as an excercise for the reader. ;-) Cheers, Mike Brudenell -- The Computing Service, University of York, Heslington, York Yo10 5DD, UK Tel: +44-1904-433811 FAX: +44-1904-433740 http://www.york.ac.uk/~pmb1/ * Unsolicited commercial e-mail is NOT welcome at this e-mail address. * From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 04:48:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA18327 for ; Tue, 27 Oct 1998 04:48:00 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA26481; Tue, 27 Oct 1998 04:47:50 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA17699; Tue, 27 Oct 1998 04:46:38 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA45550 for ; Tue, 27 Oct 1998 04:45:06 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA31202 for ; Tue, 27 Oct 1998 04:45:04 -0800 Received: from fireball.control-risks.de (port237.koeln.ndh.net [195.94.92.237]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id NAA24149; Tue, 27 Oct 1998 13:44:53 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id MAA19823; Tue, 27 Oct 1998 12:41:20 +0100 Message-Id: <19981027124120.A19426@fireball.control-risks.de> Date: Tue, 27 Oct 1998 12:41:20 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: How to append to top of document? In-Reply-To: ; from Jens Kjaerulff on Tue, Oct 27, 1998 at 12:18:46PM +0100 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Cc: Jens Kjaerulff X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Jens Kjaerulff (etnojens@au.dk): > > I hope this is the right place to ask: > > In Pine, when I export a mail to an existing file, it gets appended to the > bottom of the document. How do I change this so that it get appended to > the top instead? That's not possible out of the box. You could use the custom print command to pipe the file into a temp file and then cat the file you want to append to into that temp file, then overwrite the existing file. Ummm... this is pretty braindamaged. Perl, anyone? Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 04:55:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA18133 for ; Tue, 27 Oct 1998 04:55:33 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA25104; Tue, 27 Oct 1998 04:55:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA00426; Tue, 27 Oct 1998 04:54:09 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA49492 for ; Tue, 27 Oct 1998 04:52:53 -0800 Received: from all-phase.com (cork.all-phase.com [208.136.204.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA31598 for ; Tue, 27 Oct 1998 04:52:52 -0800 Received: from all-phase.com (cork [192.168.142.2]) by all-phase.com (8.8.8+Sun/8.8.8) with SMTP id HAA06326 for ; Tue, 27 Oct 1998 07:44:14 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 07:55:49 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Candy Cyr - Br 4e Clerical <04eclcac@all-phase.com> To: Pine Discussion Forum Subject: unsubscribe MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 04eclcac@kirk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Please take me off the pine discussion forum. Thank You, Candy Cyr Br 4E - Lafayette ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 06:07:03 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA08154 for ; Tue, 27 Oct 1998 06:07:02 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA25982; Tue, 27 Oct 1998 06:06:56 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA02394; Tue, 27 Oct 1998 06:05:42 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA20210 for ; Tue, 27 Oct 1998 06:03:15 -0800 Received: from mg2.rockymtn.net (mailserv.rockymtn.net [166.93.205.12]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA22893 for ; Tue, 27 Oct 1998 06:03:14 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg2.rockymtn.net (8.8.7/8.8.7) with ESMTP id HAA22698 for ; Tue, 27 Oct 1998 07:03:14 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id HAA15686 for ; Tue, 27 Oct 1998 07:00:25 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 07:55:52 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Mon, 26 Oct 1998, Ken Woods wrote: > Fuck off, nobody asked you. Um, yes, you asked all of us. By posting your idiocy to a public discussion forum, you open yourself to any and all criticism, ridicule, and flames. If you don't like it, there's always the "unsubscribe" command. What are you, 13? And if you take it to private mail, rest assured that it will all go directly to /dev/null. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 06:09:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA16270 for ; Tue, 27 Oct 1998 06:09:08 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA26025; Tue, 27 Oct 1998 06:09:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA13165; Tue, 27 Oct 1998 06:07:54 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA31236 for ; Tue, 27 Oct 1998 06:05:36 -0800 Received: from mg2.rockymtn.net (mailserv.rockymtn.net [166.93.205.12]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA23057 for ; Tue, 27 Oct 1998 06:05:35 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg2.rockymtn.net (8.8.7/8.8.7) with ESMTP id HAA22829; Tue, 27 Oct 1998 07:05:35 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id HAA16227; Tue, 27 Oct 1998 07:02:33 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 07:58:00 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Underline / Reversing / Blinking .. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Nayan Jain X-Cc: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Nayan Jain wrote: > I want to know how this can be done ? HTML Mail is an abomination unto the face of the earth and unto the RFC. If you're going to do it, put it in an attachment where it won't assault my eyes. -Ian (Hmm, can procmail route HTML mail to /dev/null?) From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 06:18:47 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA13353 for ; Tue, 27 Oct 1998 06:18:46 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA27621; Tue, 27 Oct 1998 06:18:38 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA08501; Tue, 27 Oct 1998 06:17:21 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA45384 for ; Tue, 27 Oct 1998 06:15:31 -0800 Received: from hd1.vsnl.net.in (hd1.vsnl.net.in [202.54.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA23807 for ; Tue, 27 Oct 1998 06:15:28 -0800 Received: from hd1 ([202.54.68.76]) by hd1.vsnl.net.in (8.8.8/8.8.8) with SMTP id TAA27627 for ; Tue, 27 Oct 1998 19:43:21 +0500 (GMT+0500) Message-Id: <008501be01b5$29f59020$2806a8c0@hd1.vsnl.net.in> Date: Tue, 27 Oct 1998 19:51:46 +0530 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: chandu@goldstone.net To: Pine Discussion Forum Subject: UNSUBSCRIBE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0082_01BE01E3.3A812A20" X-To: X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This is a multi-part message in MIME format. ------=_NextPart_000_0082_01BE01E3.3A812A20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable UNSUBSCRIBE ------=_NextPart_000_0082_01BE01E3.3A812A20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

UNSUBSCRIBE

------=_NextPart_000_0082_01BE01E3.3A812A20-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 06:23:11 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA17219 for ; Tue, 27 Oct 1998 06:23:09 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA27724; Tue, 27 Oct 1998 06:23:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id GAA08774; Tue, 27 Oct 1998 06:21:46 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id GAA31438 for ; Tue, 27 Oct 1998 06:20:00 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id GAA04380 for ; Tue, 27 Oct 1998 06:19:59 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id IAA02735 for ; Tue, 27 Oct 1998 08:19:58 -0600 Message-Id: Date: Tue, 27 Oct 1998 08:19:58 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: please...don't send useless mails. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: titthoma@cisco.com >Date: Tue, 27 Oct 1998 14:02:04 +0530 (IST) >See ,What the hell are u guys doing out there? >WE (I mean those who have subscribed to the list) simply don't like >getting useless mails in our boxes. That's lovely. If you don't care for certain threads, purge them with your filter. You do use one, don't you? >if this tit for tat mail series is going to continue.. >I think lot of us will think to sign off. Go for it. You have ignored 100% of the discussion of the .sig issue. Yours is 8 lines long and not delimited with "-- ". >Dear listmaster ...it's time to put some thought. Clean up your own act first. >tito thomas. >~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* > h c >what does "it" mean t|o s|o > in the sentence t|||m i|||. > "What time is it?"? .:ti||||a@c||||com:. >~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~*~* From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 07:22:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA19165 for ; Tue, 27 Oct 1998 07:22:41 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA27179; Tue, 27 Oct 1998 07:22:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA15564; Tue, 27 Oct 1998 07:20:35 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA49534 for ; Tue, 27 Oct 1998 07:18:41 -0800 Received: from webster (webster.vetri.com [198.153.135.140]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id HAA10853 for ; Tue, 27 Oct 1998 07:18:40 -0800 Received: from spike by webster (SMI-8.6/SMI-SVR4) id KAA15985; Tue, 27 Oct 1998 10:21:50 -0500 Message-Id: Date: Tue, 27 Oct 1998 10:20:46 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Shawn Jeffries To: Pine Discussion Forum Subject: More on list ettiquette (was: I want a signature line) In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: ujefsh81@spike X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ken Woods wrote: >I just hate stupidity, and lazy people. > >Please realize that there is a difference between being uneducated, and >being lazy and stupid. > >If you have a question, read the FAQ. >If 100 people are telling you not to cc: them on messages, then don't. > >Simple. Ken, Most people aren't used to the extremely good help resources that pine affords in the Help menus or on the net in FAQ form. Most software is generally unsupported to any reasonable degree. It takes a lot less time to just answer an honest question with a simple answer, than it does starting an argument by insulting them. If you are seriously offended by people you percieve as either "stupid" or "lazy", then I suggest you not answer their questions at all, and leave it for someone else. It only takes a small amount of effort to refer the user to those help resources, and I am sure that many people would be happy to help. -- Shawn Jeffries ujefsh81@vetri.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 07:48:45 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA19969 for ; Tue, 27 Oct 1998 07:48:44 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA27704; Tue, 27 Oct 1998 07:48:37 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA12937; Tue, 27 Oct 1998 07:46:46 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA30552 for ; Tue, 27 Oct 1998 07:44:16 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA32687 for ; Tue, 27 Oct 1998 07:44:15 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id KAA01703 for ; Tue, 27 Oct 1998 10:44:16 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 10:44:16 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ian Hall-Beyer wrote: > discussion forum, you open yourself to any and all criticism, ridicule, > and flames. If you don't like it, there's always the "unsubscribe" > command. Never said that I didn't like it. Quite the contrary, acutally. I thrive on conflict, and intelligent debate. However, you have proven yourself to be an unworthy debate opponent. *PLONK* -- Ken Woods kwoodskens.com And my filter can /dev/null you, even if you do post messages to the list. You need to man procmail man procmailrc From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 07:51:33 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA08545 for ; Tue, 27 Oct 1998 07:51:32 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA29159; Tue, 27 Oct 1998 07:51:26 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA17731; Tue, 27 Oct 1998 07:49:12 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA33954 for ; Tue, 27 Oct 1998 07:46:08 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA13726 for ; Tue, 27 Oct 1998 07:46:08 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id KAA01771 for ; Tue, 27 Oct 1998 10:46:09 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 10:46:09 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Underline / Reversing / Blinking .. In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ian Hall-Beyer wrote: (snip) > -Ian (Hmm, can procmail route HTML mail to /dev/null?) man perl man procmail man procmailrc man egrep -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 08:30:31 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA10938 for ; Tue, 27 Oct 1998 08:30:30 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA00212; Tue, 27 Oct 1998 08:30:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id IAA26032; Tue, 27 Oct 1998 08:28:54 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id IAA43270 for ; Tue, 27 Oct 1998 08:26:38 -0800 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id IAA18914 for ; Tue, 27 Oct 1998 08:26:37 -0800 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPRN01X>; Tue, 27 Oct 1998 11:30:56 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394FC5@POISON> Date: Tue, 27 Oct 1998 11:30:53 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: More on list ettiquette (was: I want a signature line) MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I have found that PINE's help is indeed good....but It's like trying to find out what a word means in the dictionary, if you don't know how to spell it, it's not as easy to find it. Like pine, if you don't know where to look for the help you may never find the information you need. What might be better (of course I don't have the indepth knowlege of pine to do this) would be a basic outline of topics which then would say where/how to find the help for it. For instance a lot of questions I initially had were solved once I realized that you could get the help under configurations But a lot of the terms for configurations don't describe what they do, unless you read the help, which basically I spent a few hours, just clicking help on each configuration entry just to see what it did and do I need it. George Gallen ggallen@slackinc.com -----Original Message----- From: Shawn Jeffries [mailto:ujefsh81@vetri.com] Sent: Tuesday, October 27, 1998 10:21 AM To: Pine Discussion Forum Subject: More on list ettiquette (was: I want a signature line) On Tue, 27 Oct 1998, Ken Woods wrote: >I just hate stupidity, and lazy people. > >Please realize that there is a difference between being uneducated, and >being lazy and stupid. > >If you have a question, read the FAQ. >If 100 people are telling you not to cc: them on messages, then don't. > >Simple. Ken, Most people aren't used to the extremely good help resources that pine affords in the Help menus or on the net in FAQ form. Most software is generally unsupported to any reasonable degree. It takes a lot less time to just answer an honest question with a simple answer, than it does starting an argument by insulting them. If you are seriously offended by people you percieve as either "stupid" or "lazy", then I suggest you not answer their questions at all, and leave it for someone else. It only takes a small amount of effort to refer the user to those help resources, and I am sure that many people would be happy to help. -- Shawn Jeffries ujefsh81@vetri.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- -----Original Message----- From: Shawn Jeffries [mailto:ujefsh81@vetri.com] Sent: Tuesday, October 27, 1998 10:21 AM To: Pine Discussion Forum Subject: More on list ettiquette (was: I want a signature line) On Tue, 27 Oct 1998, Ken Woods wrote: >I just hate stupidity, and lazy people. > >Please realize that there is a difference between being uneducated, and >being lazy and stupid. > >If you have a question, read the FAQ. >If 100 people are telling you not to cc: them on messages, then don't. > >Simple. Ken, Most people aren't used to the extremely good help resources that pine affords in the Help menus or on the net in FAQ form. Most software is generally unsupported to any reasonable degree. It takes a lot less time to just answer an honest question with a simple answer, than it does starting an argument by insulting them. If you are seriously offended by people you percieve as either "stupid" or "lazy", then I suggest you not answer their questions at all, and leave it for someone else. It only takes a small amount of effort to refer the user to those help resources, and I am sure that many people would be happy to help. -- Shawn Jeffries ujefsh81@vetri.com ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 09:23:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA21046 for ; Tue, 27 Oct 1998 09:23:49 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01884; Tue, 27 Oct 1998 09:23:42 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA12341; Tue, 27 Oct 1998 09:21:42 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA58688 for ; Tue, 27 Oct 1998 09:20:15 -0800 Received: from post5.inre.asu.edu (post5.inre.asu.edu [129.219.110.86]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA27361 for ; Tue, 27 Oct 1998 09:20:14 -0800 Received: from general5.asu.edu by asu.edu (PMDF V5.1-12 #24133) with ESMTP id <01J3GMY2SKYU8Y62VL@asu.edu> for pine-info@u.washington.edu; Tue, 27 Oct 1998 10:20:10 MST Received: from localhost (localhost [127.0.0.1]) by general5.asu.edu (8.9.1/8.9.1) with SMTP id KAA00054; Tue, 27 Oct 1998 10:20:07 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 10:20:05 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: jvan@asu.edu To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: Ken Woods X-Cc: Pine Discussion Forum X-Sender: jvanasu@general5.asu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi ken and all, Ken, your sarcasm is unecessary and offensive. I didn't know there was a FAQ--now thanks to a return message with the net address I've found it, read it, and will create my signature line. I've been reading the messages on this list for only two days but I have noticed a lack of civility among the participants--I don't know if this is all in fun because you all know each other, or this is the general tone of the list--I hope not. I'm sure I'll become more savvy as I become more familiar with Pine. Ken, remember Thumper's admonition? for now, jvan On Mon, 26 Oct 1998, Ken Woods wrote: > On Mon, 26 Oct 1998 jvan@asu.edu wrote: > > > Hi, > > Can you tell me how to include a permanent signature line with my pine > > messages? I'd appreciate the info. I can't find it in the help text. > > for now, > > jvan > > Did you even _try_ reading the FAQ??? > > http://www.washington.edu/pine/faq/custom.html#xtocid561245 > > > > -- > Ken Woods > kwoodskens.com > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 09:38:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA13034 for ; Tue, 27 Oct 1998 09:38:15 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01518; Tue, 27 Oct 1998 09:38:02 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA19524; Tue, 27 Oct 1998 09:36:10 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA45520 for ; Tue, 27 Oct 1998 09:34:44 -0800 Received: from post5.inre.asu.edu (post5.inre.asu.edu [129.219.110.86]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA28667 for ; Tue, 27 Oct 1998 09:34:43 -0800 Received: from general5.asu.edu by asu.edu (PMDF V5.1-12 #24133) with ESMTP id <01J3GNG2EMY88Y63A2@asu.edu> for pine-info@u.washington.edu; Tue, 27 Oct 1998 10:34:39 MST Received: from localhost (localhost [127.0.0.1]) by general5.asu.edu (8.9.1/8.9.1) with SMTP id KAA02476; Tue, 27 Oct 1998 10:34:38 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 10:34:37 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: jvan@asu.edu To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: <19981027092831.C18325@fireball.control-risks.de> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Sender: jvanasu@general5.asu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Robin, thanks for forwarding the rules. I didn't know them. I was looking around in Pine trying to solve my own problem. I appreciate the info. and didn't know the nature of the list i was joining. Now I do. thanks, for now, jvan On Tue, 27 Oct 1998, Robin S. Socha wrote: > Quoting Aaron S. Hawley (ashawley@zoo.uvm.edu): > > On Mon, 26 Oct 1998, Ken Woods wrote: > > > > > Can you tell me how to include a permanent signature line with my pine > > > > messages? I'd appreciate the info. I can't find it in the help text. > > > > for now, > > > > > > Did you even _try_ reading the FAQ??? > > > > ken, you need a serious attitued adjustment. lighten up. i think you > > need a special someone in your life to take some stress off. cause your > > CPU just ain't doing the trick. > > Good morning, NT-luser, > > o your quotes are totally broken > o your spelling is so seriously broken that this is not a spelling > flame > o you are so fscking clueless that you should spent a *lot* of time > reading the basic documents on email > o your whining luser attitude is a serious annoyance > > Here are the rules again: > > o this is a closed mailing list for technical problems > o luser problems are to be dealt with in > o new users are required to read the FAQ, the user guide and the > online help to earn to right to whine > > And here are the first three commandments again: > > o thou shalt read thy fuckynge manual > o thou shalt not whine > o thou shalt not suck > > Got it? Now get out of my life. > > Robin > > -- > Robin S. Socha > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 09:41:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA14355 for ; Tue, 27 Oct 1998 09:41:31 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01644; Tue, 27 Oct 1998 09:41:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA24050; Tue, 27 Oct 1998 09:38:20 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA40122 for ; Tue, 27 Oct 1998 09:36:56 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA28953 for ; Tue, 27 Oct 1998 09:36:55 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id MAA02498 for ; Tue, 27 Oct 1998 12:36:57 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 12:36:57 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998 jvan@asu.edu wrote: > Ken, your sarcasm is unecessary and offensive. According to you. If you're offended, then unsubscribe. > I didn't know there was a FAQ--now thanks to a return message with the > net address I've found it, read it, and will create my signature line. Good. Don't ask any more questions that are in the FAQ. > I've been reading the messages on this list for only two days but I No you haven't. You cc'ed me on your message. Haven't you read the messages that are going back and forth about NOT cc'ing people on responses to the list??? > have noticed a lack of civility among the participants--I don't know if > this is all in fun because you all know each other, or this is the LOL... yeah. That's it. We all know and love each other. > general tone of the list--I hope not. I'm sure I'll become more savvy > as I become more familiar with Pine. Get used to the "terse" tone. It's here to stay. > Ken, remember Thumper's admonition? eh.....No??? -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 09:50:56 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA17242 for ; Tue, 27 Oct 1998 09:50:55 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01915; Tue, 27 Oct 1998 09:50:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA24883; Tue, 27 Oct 1998 09:48:03 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA19634 for ; Tue, 27 Oct 1998 09:46:38 -0800 Received: from fluke.com (mail.fluke.com [206.138.179.7]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA30326 for ; Tue, 27 Oct 1998 09:46:38 -0800 Received: by gateway2.fluke.com id <27841>; Tue, 27 Oct 1998 09:43:38 -0800 Message-Id: <98Oct27.094338pst.27841@gateway2.fluke.com> Date: Tue, 27 Oct 1998 09:46:28 -0800 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: David Dyck To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN jvan, Ken and a few others are the minority on pine-info list Back in July, Colin posted a suggestion to ignore them... Date: Sun, 26 Jul 1998 13:36:02 -0700 From: Colin J. Raven To: Pine Discussion Forum Subject: Re: Ken's strange approach If anyone has procmail set up, this is the perfect way to silently banish Ken, his rantings, profanity, and generally offensive behavior... :0: *^From:.*@kens.com /dev/null On Tue, 27 Oct 1998 jvan@asu.edu wrote: > Hi ken and all, > Ken, your sarcasm is unecessary and offensive. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 09:54:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA22864 for ; Tue, 27 Oct 1998 09:54:40 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA02012; Tue, 27 Oct 1998 09:54:32 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA14714; Tue, 27 Oct 1998 09:53:06 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA40096 for ; Tue, 27 Oct 1998 09:51:43 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA31125 for ; Tue, 27 Oct 1998 09:51:40 -0800 Received: from [132.198.177.59] (132.198.177.59) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.89EC97B0@smtpgate.uvm.edu>; Tue, 27 Oct 1998 12:51:39 -0500 Message-Id: Date: Tue, 27 Oct 1998 12:46:41 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ken Woods wrote: > On Tue, 27 Oct 1998 jvan@asu.edu wrote: > > Ken, your sarcasm is unecessary and offensive. > > According to you. > If you're offended, then unsubscribe. people shouldn't have to deal with it. i don't think when they subscribed for the mailing list they were aware dickhead ken was on. the whole point is to deal with pine. not you > > I've been reading the messages on this list for only two days but I > > No you haven't. > You cc'ed me on your message. > Haven't you read the messages that are going back and forth about NOT > cc'ing people on responses to the list??? the guy asked how to make a signature line, you tink he knows what Cc'ing is? > > have noticed a lack of civility among the participants--I don't know if > > this is all in fun because you all know each other, or this is the > > LOL... > yeah. > That's it. > We all know and love each other. i love you ken > -- > Ken Woods > kwoodskens.com Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 10:07:08 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA23142 for ; Tue, 27 Oct 1998 10:07:06 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02382; Tue, 27 Oct 1998 10:06:58 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA26243; Tue, 27 Oct 1998 10:05:42 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA60420 for ; Tue, 27 Oct 1998 10:04:21 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA01849 for ; Tue, 27 Oct 1998 10:04:20 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id NAA02691 for ; Tue, 27 Oct 1998 13:04:22 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 13:04:22 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Aaron S. Hawley wrote: > On Tue, 27 Oct 1998, Ken Woods wrote: > > On Tue, 27 Oct 1998 jvan@asu.edu wrote: > > > Ken, your sarcasm is unecessary and offensive. > > According to you. > > If you're offended, then unsubscribe. > people shouldn't have to deal with it. i don't think when they subscribed > for the mailing list they were aware dickhead ken was on. the whole point > is to deal with pine. not you I think everybody needs to check the archives. While my answers may be short and consise, they are correct, and with a bit of thought, one can deduce the solution. If you can't deal with my email, then set me up in your filter. Makes no difference to me. > > > I've been reading the messages on this list for only two days but I > > No you haven't. > > You cc'ed me on your message. > > Haven't you read the messages that are going back and forth about NOT > > cc'ing people on responses to the list??? > > the guy asked how to make a signature line, you tink he knows what Cc'ing > is? That's not my problem. He says he's been reading the list. It's obvious that he was not. > > > have noticed a lack of civility among the participants--I don't know if > > > this is all in fun because you all know each other, or this is the > > LOL... yeah. That's it. > > We all know and love each other. > i love you ken I love you too, Aaron. -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 10:22:38 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA19073 for ; Tue, 27 Oct 1998 10:22:36 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02833; Tue, 27 Oct 1998 10:22:28 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA16417; Tue, 27 Oct 1998 10:20:33 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA30406 for ; Tue, 27 Oct 1998 10:19:06 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id KAA04242 for ; Tue, 27 Oct 1998 10:19:01 -0800 Received: from [132.198.177.59] (132.198.177.59) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.5A776790@smtpgate.uvm.edu>; Tue, 27 Oct 1998 13:18:57 -0500 Message-Id: Date: Tue, 27 Oct 1998 13:14:00 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ken Woods wrote: > I think everybody needs to check the archives. > While my answers may be short and consise, they are correct, and with a > bit of thought, one can deduce the solution. If you can't deal with my > email, then set me up in your filter. Makes no difference to me. but if we were to set up a filter, how are we supposed to get messages where you do have those great answers, or you ask us a question (of course ken would never do that> > > the guy asked how to make a signature line, you tink he knows what Cc'ing > > is? > > That's not my problem. He says he's been reading the list. > It's obvious that he was not. maybe he did read the list but has no clue what Ccing. unless he read the message where some one typed out the exact commands necessary to not Cc (up arrow up arrow, ^K, etc.> > > > > have noticed a lack of civility among the participants--I don't know if > > > > this is all in fun because you all know each other, or this is the > > > LOL... yeah. That's it. > > > We all know and love each other. > > i love you ken > > I love you too, Aaron. i love you infinity (sp?) > > -- > Ken Woods > kwoodskens.com > > a -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 11:26:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA00151 for ; Tue, 27 Oct 1998 11:26:31 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04927; Tue, 27 Oct 1998 11:26:19 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA20517; Tue, 27 Oct 1998 11:24:37 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA10264 for ; Tue, 27 Oct 1998 11:21:27 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA12228 for ; Tue, 27 Oct 1998 11:21:25 -0800 Received: from fireball.control-risks.de (port235.koeln.ndh.net [195.94.92.235]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id UAA09042 for ; Tue, 27 Oct 1998 20:21:21 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id TAA21989; Tue, 27 Oct 1998 19:39:34 +0100 Message-Id: <19981027193934.F20900@fireball.control-risks.de> Date: Tue, 27 Oct 1998 19:39:34 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: I want a New World (tm) (was: I want a signature line) In-Reply-To: ; from Aaron S. Hawley on Tue, Oct 27, 1998 at 01:14:00PM -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Aaron S. Hawley (ashawley@zoo.uvm.edu): > On Tue, 27 Oct 1998, Ken Woods wrote: Good boy, you've learnt how to quote properly. (...) > > If you can't deal with my email, then set me up in your filter. Makes no > > difference to me. > > but if we were to set up a filter, how are we supposed to get messages > where you do have those great answers, or you ask us a question (of course > ken would never do that> Use Gnus or procmail's weighted scoring. Now, just where did I read that trick before? (the OP not reading the thread about Cc:'s) > maybe he did read the list but has no clue what Ccing. unless he read the > message where some one typed out the exact commands necessary to not Cc > (up arrow up arrow, ^K, etc.> My, my, are we superimposing our own braindeadness unto other people again, Aaron? Pine *is* self-explanatory on this point if you care to read the online help. If you choose not to, you're in the wrong place. Speaking of which: how come you're still here although you've been told a couple of times that this list is for the discussion of technical problems among admins? (disgusting display of bestiality snipped) > i love you infinity (sp?) You're making me sick, Aaron. And that "(sp?)" part should really go into the from line. Now go somewhere else, please. Robin -- Robin S. Socha ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 15:22:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA30396 for ; Tue, 27 Oct 1998 15:22:13 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA12087; Tue, 27 Oct 1998 15:22:07 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA22006; Tue, 27 Oct 1998 15:21:14 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA45952 for ; Tue, 27 Oct 1998 15:19:28 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA04500 for ; Tue, 27 Oct 1998 15:19:25 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id JAA05875; Wed, 28 Oct 1998 09:48:50 +1030 Message-Id: Date: Wed, 28 Oct 1998 09:48:50 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: A semi-moderated list? In-Reply-To: <008501be01b5$29f59020$2806a8c0@hd1.vsnl.net.in> MIME-Version: 1.0 Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="----=_NextPart_000_0082_01BE01E3.3A812A20" Content-ID: X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ------=_NextPart_000_0082_01BE01E3.3A812A20 Content-Type: TEXT/PLAIN; CHARSET=iso-8859-1 Content-ID: There have been many recent posts to this list that (to put it mildly) did not have a lot to do with administration of Pine sites. I suppose most of us have sent e-mail that was unnecessary or inappropriate in some way. But most of us, also, have some quality of character which causes us to be prepared to accept and digest a just rebuke. We may even have some sense of shame or remorse on reading a protest against or comment on what we have written. Some people lack that quality, and unfortunately some of them have subscribed themselves to this list and trashed it. They rudely tell people who don't like their manners, who don't like to read mail of the kind they send, to unsubscribe. It is no novelty that there are people who lack that quality. The book of Proverbs deals with them, and our prisons are full of them. Their behavior is characteristic, and it is not hard to identify them, and in most of the activities of life, to shun them. Coming to the Pine mailing list, the only way to shun them here is to unsubscribe from the list, and clearly that is happening. I would like to suggest, since the amount of legitimate mail to the list is rather small, that it could become a moderated list, at least for as long as it takes to get rid of these people. Another approach would be for the list owner to simply unsubscribe them. I don't think there is any law against that. But they could still mail to the list. Perhaps the list owner could filter out mail from certain addresses (e.g. with procmail) so that it is not passed on to subscribers. Thus the moderator would not need to make decisions on every mail, but only step in from time to time to add an address to a black list of those who can't subscribe themselves and whose mail to the list is not forwarded. I think it is clear that some such remedy is needed. --Mike ------=_NextPart_000_0082_01BE01E3.3A812A20-- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 15:58:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA22789 for ; Tue, 27 Oct 1998 15:58:18 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13135; Tue, 27 Oct 1998 15:58:12 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA18524; Tue, 27 Oct 1998 15:56:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA30314 for ; Tue, 27 Oct 1998 15:54:14 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA19108 for ; Tue, 27 Oct 1998 15:54:13 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id QAA10677; Tue, 27 Oct 1998 16:54:13 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id QAA08228; Tue, 27 Oct 1998 16:51:21 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 17:46:48 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: I want a signature line In-Reply-To: <98Oct27.094338pst.27841@gateway2.fluke.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: David Dyck X-Cc: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, David Dyck wrote: > jvan, > Ken and a few others are the minority on pine-info list Indeed. I've been lurking here since shortly after 4.0 came out, and have been generally happy with the list. There are indeed some exceptions to that rule, and it seems you may have stepped in the thick of a flamewar. Here's your asbestos suit. -Ian From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 16:00:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA30910 for ; Tue, 27 Oct 1998 16:00:19 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13188; Tue, 27 Oct 1998 16:00:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA18675; Tue, 27 Oct 1998 15:59:16 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA45990 for ; Tue, 27 Oct 1998 15:55:01 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA22012 for ; Tue, 27 Oct 1998 15:55:00 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id QAA10767 for ; Tue, 27 Oct 1998 16:55:00 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id QAA08610 for ; Tue, 27 Oct 1998 16:52:10 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 17:47:38 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ken Woods wrote: > And my filter can /dev/null you, even if you do post messages to the list. > You need to man procmail man procmailrc By all means, be my guest. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 16:01:42 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA28877 for ; Tue, 27 Oct 1998 16:01:41 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA13241; Tue, 27 Oct 1998 16:01:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA07702; Tue, 27 Oct 1998 16:00:42 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA45872 for ; Tue, 27 Oct 1998 15:58:01 -0800 Received: from mg1.rockymtn.net (mailserv.rockymtn.net [166.93.205.11]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA19672 for ; Tue, 27 Oct 1998 15:58:00 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg1.rockymtn.net (8.8.7/8.8.7) with ESMTP id QAA11123 for ; Tue, 27 Oct 1998 16:58:00 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id QAA09987 for ; Tue, 27 Oct 1998 16:55:10 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 17:50:38 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ken Woods wrote: > Quite the contrary, acutally. I thrive on conflict, and intelligent > debate. However, you have proven yourself to be an unworthy debate > opponent. Heehee... anybody else get a good laugh about this? For the record, reverting to profanity does not constitute intelligent debate. It indicates a lack of control, a lack of mastery of the language, and general pre-pubescent behaviour. Welcome to the killfile, hop you like it in there. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 17:19:30 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA26689 for ; Tue, 27 Oct 1998 17:19:29 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA15631; Tue, 27 Oct 1998 17:19:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA29818; Tue, 27 Oct 1998 17:18:25 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA44614 for ; Tue, 27 Oct 1998 17:16:43 -0800 Received: from gw-us1new.philips.com (gw-us1new.philips.com [205.167.14.36]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA00291 for ; Tue, 27 Oct 1998 17:16:42 -0800 Received: from smtprelay-us1.philips.com (localhost.philips.com [127.0.0.1]) by gw-us1new.philips.com with ESMTP id UAA20988 for ; Tue, 27 Oct 1998 20:16:41 -0500 (EST) (envelope-from Jeff.Goswick@abq.sc.philips.com) Received: from smtprelay-nam1.philips.com(130.140.196.208) by gw-us1new.philips.com via mwrap (4.0a) id xma020986; Tue, 27 Oct 98 20:16:41 -0500 Received: from smtphub.sv.sc.philips.com (smtphub.sv.sc.philips.com [130.140.45.86]) by smtprelay-us1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id UAA17303 for ; Tue, 27 Oct 1998 20:16:40 -0500 (EST) Received: from smtphub.abq.sc.philips.com (smtphub.abq.sc.philips.com [130.140.3.9]) by smtphub.sv.sc.philips.com (8.8.5/8.8.5) with ESMTP id RAA02000 for ; Tue, 27 Oct 1998 17:16:38 -0800 (PST) Received: from abqhp1.abq.sc.philips.com (abqhp1.abq.sc.philips.com [130.140.4.1]) by smtphub.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id SAA18302 for ; Tue, 27 Oct 1998 18:16:37 -0700 (MST) Received: from abqhp39.abq.sc.philips.com (abqhp39.abq.sc.philips.com [130.140.4.39]) by abqhp1.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id UAA28686 for ; Tue, 27 Oct 1998 20:16:48 -0500 (EST) Received: from localhost (goswick@localhost) by abqhp39.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id SAA05513 for ; Tue, 27 Oct 1998 18:15:20 -0700 (MST) Message-Id: Date: Tue, 27 Oct 1998 18:15:20 -0700 (MST) Reply-To: Jeff Goswick Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff Goswick To: Pine Discussion Forum Subject: url-viewer bug? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: Jeff.Goswick@abq.sc.philips.com X-To: Pine Discussion Forum X-Authentication-Warning: abqhp39.abq.sc.philips.com: goswick owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I seem to have found a bug in the execution of the url-viewer command. If the command line is too long, extra characters seem to be added to the very end of the line. I'm running Pine 4.05 on HP-UX 10.20. In my case, I was using the command: url-viewers : "/user/goswick/bin/netscape -noraise -remote 'openURL ( _URL_ , new-window)'" When I select a long url, and attempt to view it Pine returns almost immediately with "VIEWER command completed", but no netscape window. In debug mode 9, I see the following: Want_to read: RETURN (13) resume_busy_alarm Opening pipe: "/user/goswick/bin/netscape -noraise -remote 'openURL (http://ww w.newshound.com/NewsHound/FetchStory.html?day=3&hit_id=123531057 ,new-window )'{" (UT) PID: 5494, COMMAND: /user/goswick/bin/netscape -noraise -remote 'openURL (http ://www.newshound.com/NewsHound/FetchStory.html?day=3&hit_id=123531057 ,new-w indow)'{ new mail called (0 2 0) SIGCHLD raised q_status_message(VIEWER command completed) (long lines folded and indented 2 space characters) The "{" character is added by pine. It is not in the .pinerc or the URL. The additional character(s) is/are not always the same, and seem to depend on the length of the command + URL. Regards, Jeff ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 19:42:48 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA02417 for ; Tue, 27 Oct 1998 19:42:47 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA17457; Tue, 27 Oct 1998 19:42:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA26963; Tue, 27 Oct 1998 19:41:37 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA61444 for ; Tue, 27 Oct 1998 19:40:08 -0800 Received: from proxy4.ba.best.com (root@proxy4.ba.best.com [206.184.139.15]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA13146 for ; Tue, 27 Oct 1998 19:40:08 -0800 Received: from jdtiller.vip.best.com (jdtiller.vip.best.com [206.86.76.13]) by proxy4.ba.best.com (8.9.0/8.9.0/best.out) with ESMTP id TAA12016 for ; Tue, 27 Oct 1998 19:39:09 -0800 (PST) Message-Id: Date: Tue, 27 Oct 1998 19:33:42 -0800 (Pacific Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jason Tiller To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: jdtiller@shell3.ba.best.com X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, Michael, :) As a lurker, I haven't paid too terribly much attention to the recent flame-fest ("d" is an awfully useful key), but I do manage some big mailing lists that are sometimes subject to these types of problems, and moderation or some other type of "list-splitting" is a predictable suggested solution. (My list, Handbell-L, happens to be somewhat seasonal, so we can be guaranteed to get heavy, low S/N traffic at certain points of the year - the "August urge.") I tend to shy away from these suggestions, however - moderation is a *pain* (time-consuming, slow, debate-squelching, biased, etc.), and list-splitting reduces the information content of the original list. Yes, the result may be a higher S/N, but at what cost? On Wed, 28 Oct 1998, Michael Talbot-Wilson wrote: > Coming to the Pine mailing list, the only way to shun them here is > to unsubscribe from the list, and clearly that is happening. > [...] > Perhaps the list owner could filter out mail from certain addresses > (e.g. with procmail) so that it is not passed on to subscribers. Not necessarily. Pine-Info is managed by listproc 6.0c (right?), which is the same software we use for our handbell lists; listproc provides facilities to "shun" a user, as you put it, with a .ignore list that disallows them from interacting with the list manager (subscribing, sending mail, requesting subscriber lists, etc.). With Handbell-L at over five years old and probably 2,000+ subscribers (at various points!), I've only had to ignore one subscriber. I've found that a more effective tool is a personal message to the "offender" (I quote that because one person's "offensive" is another's "stimulating!") from the listowner that reinforces whatever written or unwritten guidelines bound users' interaction with the list. If that doesn't yield results - namely contrition or at least an understanding of why some behaviors are unacceptable - *then* the clubs can be pulled out. It's also been my experience that this type of problem is sporadic, with flare-ups occurring more frequently as the subscribership grows; still, with an involved listowner, these problems can be dealt with as they come up without too much pain. One thing I do ask on Handbell-L, however, is that if there is to be any clubbing, *I* be the heavy. My list is too big and too varied for everyone to act as a "list monitor" and try to chide other subscribers as they see fit - that's my job, and I feel that keeping the reins on other users' attempts at corrective actions helps keep the list as a whole more congenial. A listowner's duties include keeping the list on-topic and un-abusive, IMHO, and I feel that subscribers should keep that in mind. I'm not condoning inflammatory rhetoric, just trying to state my experience and how these issues could be addressed. --- ---Jason Tiller jdtiller@best.com Handbell-L Listowner Pine Appreciator From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Tue, 27 Oct 1998 20:51:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA02752 for ; Tue, 27 Oct 1998 20:51:06 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA18931; Tue, 27 Oct 1998 20:51:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA00282; Tue, 27 Oct 1998 20:50:07 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA45946 for ; Tue, 27 Oct 1998 20:48:41 -0800 Received: from kens.com (kens.com [209.70.169.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA22107 for ; Tue, 27 Oct 1998 20:48:40 -0800 Received: from kens.com (kens.com [209.70.169.2]) by kens.com (8.8.8/8.9.0) with SMTP id XAA10419 for ; Tue, 27 Oct 1998 23:48:44 -0500 (EST) Message-Id: Date: Tue, 27 Oct 1998 23:48:44 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ken Woods To: Pine Discussion Forum Subject: Re: Setting Reply-To on list evil In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Tue, 27 Oct 1998, Ian Hall-Beyer wrote: > On Tue, 27 Oct 1998, Ken Woods wrote: > > I thrive on conflict, and intelligent debate > > Heehee... anybody else get a good laugh about this? > For the record, reverting to profanity does not constitute intelligent > debate. It indicates a lack of control, a lack of mastery of the language, > and general pre-pubescent behaviour. Welcome to the killfile, hop you like > it in there. (A) Self control??? You're not dead yet, are you??? That's self control on my part. (B) OK, we could continue this in German if you'd like. How about French??? Spanish?? For that matter, while it could be technically challanging, it could be done in American Sign Language. I normally think in any one of the 5. How about you??? (C) See below, you stupid asshole. *sigh* This email is about goals. What's the goal?? You stupid assholes need to get a fucking clue. **************************** =OK, now, stop thinking about everything you have just read. Now, think about the emotion that it invoked; beit anger, job, aggravation, or whatever. Profanity, and antagonistic language, when used correctly, is a VERY valuable tool for stirring emotion. GOAL: An increase in strong emotions triggers the brain to engage. Once a bodys' brain has engaged, they (sometimes) start to think for themselves. Think, think, think. =Most of my responses are short and often are "man procmail", "man man" or "man perl". That pisses alot of people off. Oh well. GOAL: To make you people think about your problem before blindly posting a question to the list. If you know that my answer is going to be "man somethingthatyoualreadyknow", then think about that for a while. Maybe you will be able to START on a solution. If you check the archives, you'll find that I've never flamed, or ridiclued anyone who has attempted to solve their own problems in an intelligent, methodical manner. =Something that everybody needs to realize is the following: This list is not intended for Joe Blow to ask stupid questions. This list is intended to be utilized by admins, and HIGH level users, asking questions that are technical in nature. GOAL: Don't ask me how to set up a filter on this list. Use comp.mail.pine for things of that nature. However, be forewarned, unless you've ready Nancy's docs, the PINE FAQ, and done a web search on "mail filters", don't expect me to be nice. =Final Thoughts. =If you don't agree with me, and are about to compose a message telling me to "fuck off", please agree to do this: Wait 15 mins. Re-read this message. If you still feel that you have something that you need to say, then please do so. GOAL: To kill this pathetic "waahh, the people on the pine-info list are mean to everybody" thread. -- Ken Woods kwoodskens.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(9) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 00:02:10 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA01484 for ; Wed, 28 Oct 1998 00:02:06 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA21258; Wed, 28 Oct 1998 00:01:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA29281; Wed, 28 Oct 1998 00:01:08 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA15066 for ; Tue, 27 Oct 1998 23:59:33 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA01995 for ; Tue, 27 Oct 1998 23:59:31 -0800 Received: from fireball.control-risks.de (port200.koeln.ndh.net [195.94.92.200]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id IAA26219 for ; Wed, 28 Oct 1998 08:59:26 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id IAA22963; Wed, 28 Oct 1998 08:57:46 +0100 Message-Id: <19981028085746.I20900@fireball.control-risks.de> Date: Wed, 28 Oct 1998 08:57:46 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: ; from Michael Talbot-Wilson on Wed, Oct 28, 1998 at 09:48:50AM +1030 References: <008501be01b5$29f59020$2806a8c0@hd1.vsnl.net.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Michael Talbot-Wilson (mtw@calypso.view.net.au): > There have been many recent posts to this list that (to put it > mildly) did not have a lot to do with administration of Pine sites. That is correct. Basically, they went along the following lines: "how do I forge my from line?" "how do I add a signature?" "how do I filter mail?" "how do I underline...?" "why are reply-to's evil?" Now tell me, Michael, what do these questions have to do with "Pine sites"? > I suppose most of us have sent e-mail that was unnecessary or > inappropriate in some way. But most of us, also, have some quality > of character which causes us to be prepared to accept and digest a > just rebuke. We may even have some sense of shame or remorse on > reading a protest against or comment on what we have written. English not being my mother tongue, I presume that this novellette roughly means "if you fuck up, take the whipping like a man"? > Some people lack that quality, and unfortunately some of them have > subscribed themselves to this list and trashed it. They rudely tell > people who don't like their manners, who don't like to read mail of > the kind they send, to unsubscribe. The last person who was told to unsubscribe was this Aaron dude. Now, Michael, you're not really trying to justify Aaron's brave display of public stupidity, and his unnerving reluctance to read, are you? > It is no novelty that there are people who lack that quality. The > book of Proverbs deals with them, and our prisons are full of them. You remember the eye for an eye thing, too, do you, Michael? And American prisions don't bother me at all. To my knowledge, no German ever got jailed for telling a luser to unsub from a mailing list. > Their behavior is characteristic, and it is not hard to identify > them, and in most of the activities of life, to shun them. Yes, Michael, that is an excellent idea. Go back to your bookshelf, the one with Darwin, Rosenberg and Himmler in it. > Coming to the Pine mailing list, the only way to shun them here is > to unsubscribe from the list, and clearly that is happening. Let me rephrase that. You are saying: people are unsubscribing because of the unbearable amount of profane emails sent to this list. I say: if the list were put to its proper use, the profanity would stay where it belongs (ie Usenet). > I would like to suggest, since the amount of legitimate mail to the > list is rather small, that it could become a moderated list, at > least for as long as it takes to get rid of these people. Did you just volunteer for that job, Michael? Tell me, have you ever moderated a list? Are you even remotely aware of what a sucky job this is? And who else would volunteer? You see, there's Gnus, the mail and newsreader for XEmacs. It's got this nifty feature of doc groups. When you fire it up, it's got the FAQ on board, as well as a set of rules and guidelines for using it. Now, take a minute and *read* and tell me in which respect it is different from . Correct: there are far less lusers there, although it's a Usenet newsgroup. Is Gnus any more difficult to use than Pine? I don't really think so, although you probably need a fairly good understanding of Emacs to use it. Are Gnus users more intelligent than Pine users? Hardly likely - even I can use it. Is their attitude towards the tool different? I should think so. If you use Emacs, you're probably an advanced user and therefore prone to reading the docs thoroughly. If anything, I think it might be a good idea to make the Pine docs even more accessible by re-writing them in, say, linuxdoc and allow admins to convert them into every conceivable format. Even an intelligent use of CSS for the HTML docs might make make printing them out a lot more fun. If you were interested in that, I'd join. The online help is good, but I prefer hardcopies. If you want to convert the current help system into something more readable, go for it. > Another approach would be for the list owner to simply unsubscribe > them. I don't think there is any law against that. But they could > still mail to the list. They couldn't, but they could re-subscribe from another account most easily. > Perhaps the list owner could filter out mail from certain addresses > (e.g. with procmail) so that it is not passed on to subscribers. Now that is a great idea. Let's start with aol, compuserve and everything that says "edu". Gosh, what a quite little list that would be. Site banishes are lame, Michael, get over it. > Thus the moderator would not need to make decisions on every mail, > but only step in from time to time to add an address to a black list > of those who can't subscribe themselves and whose mail to the list > is not forwarded. I can see it clearly before me: the Pine Email Police Force, the Pico Vice Squad and the Pilot Task Force. And you, of course, still dressed in those funny clothes your big sister forces you to wear every time you've been a silly billy again. > I think it is clear that some such remedy is needed. Absolutely. Now, brothers and sisters, let us all rejoice in the Truth and Rigour and the Depth of Godwin's Law and sing: "Ja, mein Pine Fuehrer, we need eine Sonderloesung for der Scum of die Earth." Ro"thisthreadhasjustbeenkilled"bin +-Vv+ Io oI Digitally enhanced portrait I = I of Der Grosse Pineator I _ I +---+ From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:01:20 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA13507 for ; Wed, 28 Oct 1998 10:01:18 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA02590; Wed, 28 Oct 1998 10:00:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA19948; Wed, 28 Oct 1998 10:00:05 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA45330 for ; Wed, 28 Oct 1998 09:56:33 -0800 Received: from nimbus.anzio.com (ras@nimbus.anzio.com [204.201.253.34]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA14548 for ; Wed, 28 Oct 1998 09:56:33 -0800 Received: from localhost (ras@localhost) by nimbus.anzio.com (8.7.5/8.7.3) with SMTP id JAA21976; Wed, 28 Oct 1998 09:55:56 -0800 Message-Id: Date: Wed, 28 Oct 1998 09:55:55 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Bob Rasmussen To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Michael Talbot-Wilson X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm sure many who agree with Mr. Talbot-Wilson have refrained from commenting for fear of unleashing a more of the behavior about which he complains, or have left the list in frustration. Well I'll speak up. I agree completely. Just about every listserv, online forum, newsgroup, etc. which I have read, if not moderated in some fashion, soon sinks to the level of a sewer, with a few contributors who can't or won't conform to norms of social decency dominating the bandwidth, to the point that the list uses its usefulness. It is, of course, useless to try to convince them that they are not valued participants, or that they should use some manners. Other lists, which are moderated at least to the point of preventing abusive language, I find to be extremely productive. I community mentality develops, where people feel free to ask questions, and others feel free to respond. If there are others who would like to see this list moderated, I encourage you to speak up. Let's not allow the bad to drive out the good. Regards, ....Bob Rasmussen, President, Rasmussen Software, Inc. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:28:02 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA12436 for ; Wed, 28 Oct 1998 10:28:01 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03421; Wed, 28 Oct 1998 10:27:55 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA03698; Wed, 28 Oct 1998 10:25:50 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA20722 for ; Wed, 28 Oct 1998 10:23:51 -0800 Received: from europe.std.com (europe.std.com [199.172.62.20]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA16302 for ; Wed, 28 Oct 1998 10:23:50 -0800 Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id NAA01675; Wed, 28 Oct 1998 13:23:49 -0500 (EST) Received: from localhost by world.std.com (TheWorld/Spike-2.0) id AA29275; Wed, 28 Oct 1998 13:23:43 -0500 Message-Id: Date: Wed, 28 Oct 1998 13:23:42 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff A Kinsey To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i thought i would never say this: i vote to moderate. -jeff On Wed, 28 Oct 1998, Bob Rasmussen wrote: > If there are others who would like to see this list moderated, I encourage you > to speak up. Let's not allow the bad to drive out the good. -- "make no small plans - for they have no magic to stir man's souls" From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:40:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA18108 for ; Wed, 28 Oct 1998 10:40:31 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03327; Wed, 28 Oct 1998 10:40:23 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA22619; Wed, 28 Oct 1998 10:39:31 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA20620 for ; Wed, 28 Oct 1998 10:37:21 -0800 Received: from pilsener.ucs.ualberta.ca (pilsener.ucs.ualberta.ca [129.128.5.19]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA24617 for ; Wed, 28 Oct 1998 10:37:19 -0800 Received: from gpu2.srv.ualberta.ca (gpu2.srv.ualberta.ca [129.128.98.12]) by pilsener.ucs.ualberta.ca (8.9.1a/8.9.1) with ESMTP id LAA05676 for ; Wed, 28 Oct 1998 11:37:18 -0700 (MST) Received: from localhost (maldridg@localhost) by gpu2.srv.ualberta.ca (8.8.5/8.8.5) with SMTP id LAA42704 for ; Wed, 28 Oct 1998 11:37:18 -0700 Message-Id: Date: Wed, 28 Oct 1998 11:37:18 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Lea To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Information List X-Sender: maldridg@gpu2.srv.ualberta.ca X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN > On Wed, 28 Oct 1998, Bob Rasmussen wrote: > > > If there are others who would like to see this list moderated, I encourage you > > to speak up. Let's not allow the bad to drive out the good. I truly hate having to say this, but in my line of work (frontline computer consulting) I listen to enough verbal abuse as it is. I don't want to read abusive language in what's supposed to be a professional mailing list, and no, I'm not yet prepared to unsubscribe. The information exchange on this list over the past few years has been too valuable to me to simply dismiss it. I can understand Ken and Robin's frustrations - they are both highly technically competent - but to be honest, I don't think it's fair to assume that people asking a common question to which the answer is simple haven't done their homework. I've had personal experience working with complicated software for the first time where I really had no idea where the 'feature' I wanted was hidden...er...located, and the built-in help menus weren't any help because I didn't know what term the software used to reference this feature. So yeah, another vote for moderation. Every which way. Lea From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:53:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA21994 for ; Wed, 28 Oct 1998 10:53:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03673; Wed, 28 Oct 1998 10:53:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA23673; Wed, 28 Oct 1998 10:52:08 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA52760 for ; Wed, 28 Oct 1998 10:50:03 -0800 Received: from gw-us1new.philips.com (gw-us1new.philips.com [205.167.14.36]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22716 for ; Wed, 28 Oct 1998 10:50:02 -0800 Received: from smtprelay-us1.philips.com (localhost.philips.com [127.0.0.1]) by gw-us1new.philips.com with ESMTP id NAA00893 for ; Wed, 28 Oct 1998 13:50:00 -0500 (EST) (envelope-from Jeff.Goswick@abq.sc.philips.com) Received: from smtprelay-nam1.philips.com(130.140.196.208) by gw-us1new.philips.com via mwrap (4.0a) id xma000891; Wed, 28 Oct 98 13:50:00 -0500 Received: from smtphub.sv.sc.philips.com (smtphub.sv.sc.philips.com [130.140.45.86]) by smtprelay-us1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with ESMTP id NAA10970 for ; Wed, 28 Oct 1998 13:49:59 -0500 (EST) Received: from smtphub.abq.sc.philips.com (smtphub.abq.sc.philips.com [130.140.3.9]) by smtphub.sv.sc.philips.com (8.8.5/8.8.5) with ESMTP id KAA28618 for ; Wed, 28 Oct 1998 10:49:57 -0800 (PST) Received: from abqhp1.abq.sc.philips.com (abqhp1.abq.sc.philips.com [130.140.4.1]) by smtphub.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id LAA25961 for ; Wed, 28 Oct 1998 11:49:57 -0700 (MST) Received: from abqhp39.abq.sc.philips.com (abqhp39.abq.sc.philips.com [130.140.4.39]) by abqhp1.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id NAA00240 for ; Wed, 28 Oct 1998 13:50:10 -0500 (EST) Received: from localhost (goswick@localhost) by abqhp39.abq.sc.philips.com (8.8.5/8.8.5) with ESMTP id LAA08247 for ; Wed, 28 Oct 1998 11:48:40 -0700 (MST) Message-Id: Date: Wed, 28 Oct 1998 11:48:40 -0700 (MST) Reply-To: Jeff Goswick Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeff Goswick To: Pine Discussion Forum Subject: Re: url-viewer bug? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE X-Sender: Jeff.Goswick@abq.sc.philips.com X-To: Pine Discussion Forum X-Authentication-Warning: abqhp39.abq.sc.philips.com: goswick owned process doing -bs X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Nope, attempted with just escaping parenthesis (no embedded newline: Pine rejects the embedded newline in the .pinerc file, as well as in the setup screen, which seems appropriate to me). Now getting debug info: Want_to read: RETURN (13) resume_busy_alarm Opening pipe: "/user/goswick/bin/netscape -noraise -remote openURL\( "http: //www.newshound.com/NewsHound/FetchStory.html?day=3D4&hit_id=3D123634468"= , ne w-window\)=E2{" (UT) PID: 8099, COMMAND: /user/goswick/bin/netscape -noraise -remote openURL\( " http://www.newshound.com/NewsHound/FetchStory.html?day=3D4&hit_id=3D12363= 4468 ", new-window\)=E2{ new mail called (0 2 0) SIGCHLD raised q_status_message(VIEWER command completed) (Note: long lines wrapped at column 75, and indented 2 spaces) Again, extra characters are being added to the command. These characters are not necessarily ascii. Both my original setting, and Brett's suggestion w/o newline work if the UR= L + command is short (I don't know how short is short enough). Work around is to create a wrapper shell: #!/bin/csh -f # urlview wrapper script netscape -noraise -remote "openURL ( $1 , new-window)" & and use pine configuration: url-viewers: /user/goswick/bin/urlview Regards, Jeff On Tue, 27 Oct 1998, Brett Eldridge wrote: > On Tue, 27 Oct 1998, Jeff Goswick wrote: >=20 > > url-viewers : > > "/user/goswick/bin/netscape -noraise -remote 'openURL ( _URL_ , new-wi= ndow)'" >=20 > Try this instead: >=20 > "/user/goswick/bin/netscape -noraise -remote openURL\\(_URL_,\\=20 > new-window\\)" >=20 >=20 > - brett >=20 >=20 From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:55:10 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA21243 for ; Wed, 28 Oct 1998 10:55:09 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03727; Wed, 28 Oct 1998 10:55:03 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA05766; Wed, 28 Oct 1998 10:54:17 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA41596 for ; Wed, 28 Oct 1998 10:50:29 -0800 Received: from poison.slackinc.com (poison.slackinc.com [206.0.70.40]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22703 for ; Wed, 28 Oct 1998 10:50:28 -0800 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPR3B5K>; Wed, 28 Oct 1998 13:54:47 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394FE0@POISON> Date: Wed, 28 Oct 1998 13:54:46 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: A semi-moderated list? MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN -----Original Message----- From: Lea [mailto:Marianne.Aldridge@ualberta.ca] Sent: Wednesday, October 28, 1998 1:37 PM To: Pine Discussion Forum Subject: Re: A semi-moderated list? > On Wed, 28 Oct 1998, Bob Rasmussen wrote: > > > If there are others who would like to see this list moderated, I encourage you > > to speak up. Let's not allow the bad to drive out the good. I truly hate having to say this, but in my line of work (frontline computer consulting) I listen to enough verbal abuse as it is. I don't want to read abusive language in what's supposed to be a professional mailing list, and no, I'm not yet prepared to unsubscribe. The information exchange on this list over the past few years has been too valuable to me to simply dismiss it. I can understand Ken and Robin's frustrations - they are both highly technically competent - but to be honest, I don't think it's fair to assume that people asking a common question to which the answer is simple haven't done their homework. I've had personal experience working with complicated software for the first time where I really had no idea where the 'feature' I wanted was hidden...er...located, and the built-in help menus weren't any help because I didn't know what term the software used to reference this feature. So yeah, another vote for moderation. Every which way. Lea From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 10:57:31 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA22019 for ; Wed, 28 Oct 1998 10:57:30 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA03811; Wed, 28 Oct 1998 10:57:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id KAA06082; Wed, 28 Oct 1998 10:56:19 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id KAA30280 for ; Wed, 28 Oct 1998 10:54:03 -0800 Received: from poison.slackinc.com (smtp.slackinc.com [206.0.70.39]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id KAA27131 for ; Wed, 28 Oct 1998 10:54:02 -0800 Received: by POISON with Internet Mail Service (5.5.1960.3) id <4QPR3B5V>; Wed, 28 Oct 1998 13:58:21 -0500 Message-Id: <0089B6FA4F0DD211AD4E0001FA7E5055394FE1@POISON> Date: Wed, 28 Oct 1998 13:58:20 -0500 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: George Gallen To: Pine Discussion Forum Subject: RE: A semi-moderated list? MIME-Version: 1.0 Content-Type: text/plain X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN oops, first one went out as blank...I guess a moderated list would have stopped that from bugging anyone :) Either way, it doesn't make a big difference to me, I can hit the delete key pretty easy when it gets rediculous... Two problems with moderation: 1. Who will moderate it (like they already have much too much spare time) 2. How much time will that add to the posting? If someone needs answers quickly, even getting non helpful replies is ok, as long as you are also getting the helpful ones. and assuming the moderators are being objective, even sometimes the rediculous can be helpful, but the moderator may not see that. Personally, I favor unmoderated, but can live with moderated. George Gallen ggallen@slackinc.com -----Original Message----- From: Lea [mailto:Marianne.Aldridge@ualberta.ca] Sent: Wednesday, October 28, 1998 1:37 PM To: Pine Discussion Forum Subject: Re: A semi-moderated list? > On Wed, 28 Oct 1998, Bob Rasmussen wrote: > > > If there are others who would like to see this list moderated, I encourage you > > to speak up. Let's not allow the bad to drive out the good. I truly hate having to say this, but in my line of work (frontline computer consulting) I listen to enough verbal abuse as it is. I don't want to read abusive language in what's supposed to be a professional mailing list, and no, I'm not yet prepared to unsubscribe. The information exchange on this list over the past few years has been too valuable to me to simply dismiss it. I can understand Ken and Robin's frustrations - they are both highly technically competent - but to be honest, I don't think it's fair to assume that people asking a common question to which the answer is simple haven't done their homework. I've had personal experience working with complicated software for the first time where I really had no idea where the 'feature' I wanted was hidden...er...located, and the built-in help menus weren't any help because I didn't know what term the software used to reference this feature. So yeah, another vote for moderation. Every which way. Lea From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 11:07:50 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA20773 for ; Wed, 28 Oct 1998 11:07:49 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04607; Wed, 28 Oct 1998 11:07:40 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA12424; Wed, 28 Oct 1998 11:06:12 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA42910 for ; Wed, 28 Oct 1998 11:03:44 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA28708 for ; Wed, 28 Oct 1998 11:03:43 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id NAA05534 for ; Wed, 28 Oct 1998 13:03:37 -0600 Message-Id: Date: Wed, 28 Oct 1998 13:03:37 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Lea >Date: Wed, 28 Oct 1998 11:37:18 -0700 (MST) >I can understand Ken and Robin's frustrations - they are both highly >technically competent - but to be honest, I don't think it's fair to assume >that people asking a common question to which the answer is simple haven't >done their homework. I've had personal experience working with complicated >software for the first time where I really had no idea where the 'feature' I >wanted was hidden...er...located, and the built-in help menus weren't any help >because I didn't know what term the software used to reference this feature. >So yeah, another vote for moderation. Every which way. You are all missing the larger issue: Moderation is work, which none of you has volunteered to do. No one has yet defended any of the askers of inane questions. Can we all agree that questions which are easily answered in the FAQs or the Help text do not belong on this list? If so, the only question is the degree of contempt with which the askers of questions are treated. I've suggested this before: moderate only questions from new members till they get the idea. But SOMEONE in favor of moderation must volunteer to correspond with these violators. I propose a sliding scale: First time violation: Dear Lucas User, I completely understand that you don't understand this program. Nevertheless, it is a requirement of this mailing list that you lurk for a while (read only, don't post) to get a feel for the nature of the list. Before you ask a question, it is mandatory that you read the Help text "^g" and the FAQs. If you are still having trouble, you may correspond with me. After that, they get a best of Robin or Ken. If they still persist, well, a more personal response is in order. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 11:13:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA20648 for ; Wed, 28 Oct 1998 11:13:51 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA04388; Wed, 28 Oct 1998 11:13:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA07560; Wed, 28 Oct 1998 11:12:34 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA56532 for ; Wed, 28 Oct 1998 11:10:43 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA25923 for ; Wed, 28 Oct 1998 11:10:42 -0800 Received: from fireball.control-risks.de (port232.koeln.ndh.net [195.94.92.232]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id UAA08970 for ; Wed, 28 Oct 1998 20:10:36 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id UAA25389; Wed, 28 Oct 1998 20:11:22 +0100 Message-Id: <19981028201122.C24291@fireball.control-risks.de> Date: Wed, 28 Oct 1998 20:11:22 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: ; from Bob Rasmussen on Wed, Oct 28, 1998 at 09:55:55AM -0800 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Bob Rasmussen (ras@anzio.com) wants a moderated list: (...) > Just about every listserv, online forum, newsgroup, etc. which I have read, if > not moderated in some fashion, soon sinks to the level of a sewer, with a few > contributors who can't or won't conform to norms of social decency dominating > the bandwidth, to the point that the list uses its usefulness. Form follows function, Bob. A while ago, the Pine ML was gatewayed to comp.mail.pine. After a lengthy discussion, the Pine developers decided to separate the two, leaving the NG for luser problems and the ML for technical/administration problems. As far as the latter are concerned, there has been none of the behaviour you wordily deplore. As for luser questions: o new users are required to read the documentation available; if they don't, they're not in a position to complain o Pine has ample documentation, although the format is suboptimal; nonetheless, all information is there and in many regards in better shape than in many other programs around o not reading the documentation and instead asking the same VFAQ again and again and again is the opposite of the politeness you demand. It's arrogant, stupid and gerenally annoying. It's also rude towards the people who devoted their time to write excellent documentation for a free program > It is, of course, useless to try to convince them that they are not valued > participants, or that they should use some manners. I'll unsubscribe the very moment you, Bob, prove yourself more valuable than me. Honest. You asked for it - now go for it. > Other lists, which are moderated at least to the point of preventing abusive > language, I find to be extremely productive. Let me rephrase that: "abusive language destroys productivity", right? Tell me, Bob, when did you last read code? > I community mentality develops, where people feel free to ask questions, and > others feel free to respond. This seems to be a particularly Microsoftish/American idea. If I told you that you're not quite up to standard as far as sociology is concerned - would that be any different from calling you a whining lamer? I don't think so. E-communication tends to be best when it is concise and hard-hitting. Nice people with nice attitudes and a generally good aura make me sick. Not surprisingly, these are exactly the same people who a) ask VFAQs, b) don't have the slightes clue of the technology they're abusing and c) suck. Besides which, everyone gets the answer they deserve here, still. If I bumped into alt.sex.singles.with.severe.social.dysfunctions asking for Lamer Bob, I wouldn't expect an answer, either. Actually, I would, but that's a different story, I presume. > If there are others who would like to see this list moderated, I encourage you > to speak up. Oh, I forget. There's also the guys commonly referred to as Samaritans. They are hardly ever seen when it comes to technical discussions, they generally don't participate in voluntary work - but they parade the respective forum going "look, Ma, I'm a Big Boy now, and I want to become a politician with the moral integrity of our current president". God bless America - with people like you leading the crowd, it will certainly need that. > Let's not allow the bad to drive out the good. Ummm, Bob, rhetorics don't work this way. Neither are you and I "we", nor are you in a position to judge who's good or bad. Or are you? Is that you God? Have you turned into > ....Bob Rasmussen, President, Rasmussen Software, Inc. to put us all to shame? Naaaa - don't think so. Till then... ....Robin S. Socha, Jerk, Frustrated, Inc. -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 14:11:53 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA24925 for ; Wed, 28 Oct 1998 14:11:52 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10174; Wed, 28 Oct 1998 14:11:46 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA08689; Wed, 28 Oct 1998 14:10:24 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA50218 for ; Wed, 28 Oct 1998 14:07:31 -0800 Received: from mail.mankato.msus.edu (Mail.Mankato.MSUS.EDU [134.29.1.12]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA19742 for ; Wed, 28 Oct 1998 14:07:28 -0800 Received: from bs1.mankato.msus.edu (root@bs1.Mankato.MSUS.EDU [134.29.1.244]) by mail.mankato.msus.edu (8.9.1/8.9.1) with ESMTP id QAA23753 for ; Wed, 28 Oct 1998 16:07:24 -0600 (CST) Message-Id: <199810282207.QAA23753@mail.mankato.msus.edu> Date: Wed, 28 Oct 1998 16:07:21 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeffrey Hundstad To: Pine Discussion Forum Subject: Local folders 3.96 -> 4.05 MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I'm trying to migrate from pine 3.96 to 4.05. While 4.05 seems to work just fine for most things I can't get it to ``see'' my imap folders that were created with 3.96. Did I miss something in the Installation directions? This seems like user error (mine) but I don't really know where to look next. -- Jeffrey Hundstad PS I apologize of this question is asked every two days... but I just subscribed. ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 14:32:08 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA15883 for ; Wed, 28 Oct 1998 14:32:07 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA10839; Wed, 28 Oct 1998 14:31:47 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id OAA17774; Wed, 28 Oct 1998 14:29:56 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id OAA61356 for ; Wed, 28 Oct 1998 14:27:13 -0800 Received: from mail.mankato.msus.edu (Mail.Mankato.MSUS.EDU [134.29.1.12]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id OAA19832 for ; Wed, 28 Oct 1998 14:27:11 -0800 Received: from bs1.mankato.msus.edu (root@bs1.Mankato.MSUS.EDU [134.29.1.244]) by mail.mankato.msus.edu (8.9.1/8.9.1) with ESMTP id QAA28456; Wed, 28 Oct 1998 16:26:56 -0600 (CST) Message-Id: <199810282226.QAA28456@mail.mankato.msus.edu> Date: Wed, 28 Oct 1998 16:26:53 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Jeffrey Hundstad To: Pine Discussion Forum Subject: Re: Local folders 3.96 -> 4.05 In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-To: ashawley@zoo.uvm.edu, pine-info@u.washington.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I administrate the text based mail access at Minnesota State University, Mankato. MSU,M -> http://www.mankato.msus.edu/ Mine -> http://www.mankato.msus.edu/jeffrey/ On 28 Oct, Aaron S. Hawley wrote: > are you a network administrator, or just a single user of pine email? > > if just one user i would suggest asking this question to the newsgroup > comp.mail.pine because you are goign to catch hell for asking it here. > > so write an apology to this list before you catch hell from ken or robin. > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 15:24:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA17800 for ; Wed, 28 Oct 1998 15:24:31 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA12288; Wed, 28 Oct 1998 15:24:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA24023; Wed, 28 Oct 1998 15:23:33 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA27360 for ; Wed, 28 Oct 1998 15:20:38 -0800 Received: from post6.inre.asu.edu (post6.inre.asu.edu [129.219.110.87]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA29428 for ; Wed, 28 Oct 1998 15:20:37 -0800 Received: from general2.asu.edu by asu.edu (PMDF V5.1-12 #24133) with ESMTP id <01J3IDT9WW3Y8Y6AQT@asu.edu> for pine-info@u.washington.edu; Wed, 28 Oct 1998 16:20:33 MST Received: from localhost (localhost [127.0.0.1]) by general2.asu.edu (8.9.1/8.9.1) with SMTP id QAA28570; Wed, 28 Oct 1998 16:20:28 -0700 (MST) Message-Id: Date: Wed, 28 Oct 1998 16:20:27 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: jvan@asu.edu To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Sender: jvanasu@general2.asu.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi All, As I am a luser who wants to be a winner, and who asked one of the stupid questions that got some of you up and out of your chairs with vitriolic glee, I would like to apologize. I am SORRY. Mea culpa, 3X. (YES--I'm CC'ing all of you--on purpose! and I WILL NEVER do it again). I vote for Adam's message for folks like me who--stumbling through this world--chance upon the eden of this list thinking AHA! I have found a way to have my questions answered, not realizing--because it is not stated(at least not where I found the list and signed on to it--that the list is for Xtremely advanced users/administrators, not your average teacher who is teaching computer aided compositon classes (3) mostly via pine, and has only been using pine for four years, and has been too busy teaching the classes to have much time to figure out pines delicate (oh, so delicate,and subtle) nuances. The suggested message to first time offenders seems civil, and i would have respected it--even appreciated it. Maybe quick draw Ken could add it to his signature? for now, jvan On Wed, 28 Oct 1998, Adam H. Kerman wrote: > >From: Lea > >Date: Wed, 28 Oct 1998 11:37:18 -0700 (MST) > > >I can understand Ken and Robin's frustrations - they are both highly > >technically competent - but to be honest, I don't think it's fair to assume > >that people asking a common question to which the answer is simple haven't > >done their homework. I've had personal experience working with complicated > >software for the first time where I really had no idea where the 'feature' I > >wanted was hidden...er...located, and the built-in help menus weren't any help > >because I didn't know what term the software used to reference this feature. > > >So yeah, another vote for moderation. Every which way. > > You are all missing the larger issue: Moderation is work, which none of you has > volunteered to do. > > No one has yet defended any of the askers of inane questions. Can we all agree > that questions which are easily answered in the FAQs or the Help text do not > belong on this list? > > If so, the only question is the degree of contempt with which the askers of > questions are treated. > > I've suggested this before: moderate only questions from new members till they > get the idea. But SOMEONE in favor of moderation must volunteer to correspond > with these violators. > > I propose a sliding scale: > > First time violation: > > Dear Lucas User, > > I completely understand that you don't understand this program. Nevertheless, > it is a requirement of this mailing list that you lurk for a while (read only, > don't post) to get a feel for the nature of the list. Before you ask a > question, it is mandatory that you read the Help text "^g" and the FAQs. > If you are still having trouble, you may correspond with me. > > After that, they get a best of Robin or Ken. > > If they still persist, well, a more personal response is in order. > > From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 15:40:34 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA27767 for ; Wed, 28 Oct 1998 15:40:32 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA12835; Wed, 28 Oct 1998 15:40:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA21360; Wed, 28 Oct 1998 15:39:48 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA27136 for ; Wed, 28 Oct 1998 15:37:47 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA29745 for ; Wed, 28 Oct 1998 15:37:44 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id KAA12004; Thu, 29 Oct 1998 10:07:10 +1030 Message-Id: Date: Thu, 29 Oct 1998 10:07:10 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 28 Oct 1998, Adam H. Kerman wrote: > You are all missing the larger issue: Moderation is work, which none of you has Please keep your lines under 80 characters. > volunteered to do. Moderation would be a pain, for someone. But I addressed that, and someone else has mentioned the listserv 'ignore' facility. > No one has yet defended any of the askers of inane questions. Can we all agree All right. Since you apparently don't know, here is what you do about askers of inane questions. There are two standard approaches. You have a choice, you see. Here they are: (1) Ignore them. Do not mail them, and certainly don't mail the list. Remember, 'd' will delete thir mail. (2) Mail the person privately with a helpful reply. Certainly, don't mail the list to exhibit yourself and the wit of your reply. Those are the two standard methods. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 15:57:49 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA29169 for ; Wed, 28 Oct 1998 15:57:48 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13382; Wed, 28 Oct 1998 15:57:41 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA01006; Wed, 28 Oct 1998 15:57:00 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA31482 for ; Wed, 28 Oct 1998 15:55:13 -0800 Received: from seen.farley.org (root@farley.org [204.248.217.248]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA32116 for ; Wed, 28 Oct 1998 15:55:11 -0800 Received: from seen.farley.org ([192.168.1.2] ident=sean) by seen.farley.org with esmtp (Exim 1.92 #1) for pine-info@u.washington.edu id 0zYfQz-00017a-00; Wed, 28 Oct 1998 18:55:25 -0500 Message-Id: Date: Wed, 28 Oct 1998 18:55:25 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Sean Farley To: Pine Discussion Forum Subject: Postponed messages MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: sean@farley.org X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN I am running my own domain (farley.org) and use Exim as the MTA. One of Exim's features is allowing suffixes to a user name. For example, I can change my e-mail address to scf-pine@farley.org. In this case Exim would parse the .forward file for directions on what to do with the e-mail. I was writing an e-mail but since I needed to go do something else, I postponed it. After attempting to send it out when I got back, I was greeted with an error 550 sent back from Exim. Before sending the mail out I had changed the From: header to scf-pine@farley.org--still using the example. I have succeeded at changing the From: header before with out problems from Exim, so I was quite confused. After some testing, I discovered that Pine was changing the Reply-to: header on me if I postponed the message. If I do not postpone, it does not change the Reply-to:. I am assuming this is a bug. Am I correct in assuming that it should never change the Reply-to: if I change the From:? At least I hope this is the case since it would work better through Exim. Hint. Hint. :) For those who are surprised by Exim doing this, I have sender_verify set to true which would cause the 550 to be sent back to Pine. Sean -------------- scf@farley.org ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 15:59:52 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA31469 for ; Wed, 28 Oct 1998 15:59:51 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA13461; Wed, 28 Oct 1998 15:59:45 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id PAA14581; Wed, 28 Oct 1998 15:58:58 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id PAA35714 for ; Wed, 28 Oct 1998 15:56:31 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id PAA01949 for ; Wed, 28 Oct 1998 15:56:29 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id KAA12088; Thu, 29 Oct 1998 10:25:55 +1030 Message-Id: Date: Thu, 29 Oct 1998 10:25:55 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: <19981028201122.C24291@fireball.control-risks.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 28 Oct 1998, Robin S. Socha wrote: > o Pine has ample documentation, although the format is suboptimal; > nonetheless, all information is there and in many regards in better > shape than in many other programs around > o not reading the documentation and instead asking the same VFAQ again > and again and again is the opposite of the politeness you demand. > It's arrogant, stupid and gerenally annoying. It's also rude towards > the people who devoted their time to write excellent documentation > for a free program > Bob, when did you last read code? So, read all of the documentation, and read the code. If you don't, you uncap the sewer that is Robin S. Socha and it all sloshes out. Not just over the "offender" who failed to read all the documentation and the code, but over everyone. Robin, this mailing list is not called "pine-dev". Even if it were, sending abusive responses to it, to the list, would not be excusable. Keep it for private mail. There is no need to show off here. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 17:00:05 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA20903 for ; Wed, 28 Oct 1998 17:00:01 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA14871; Wed, 28 Oct 1998 16:59:52 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id QAA04114; Wed, 28 Oct 1998 16:59:02 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id QAA57200 for ; Wed, 28 Oct 1998 16:56:33 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id QAA09904 for ; Wed, 28 Oct 1998 16:56:32 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id SAA12517 for ; Wed, 28 Oct 1998 18:56:31 -0600 Message-Id: Date: Wed, 28 Oct 1998 18:56:31 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Michael Talbot-Wilson >Date: Thu, 29 Oct 1998 10:07:10 +1030 (CST) >Moderation would be a pain, for someone. What do you care? It's not your list. >But I addressed that, and someone else has mentioned the listserv 'ignore' >facility. . . . which will not prevent inane threads from beginning. As long as people like you defend the right to ask inane questions, I will defend the right of others to answer vitriolicly. It keeps us awake. Few will admit it, but you find the responses entertaining. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 18:44:20 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA30402 for ; Wed, 28 Oct 1998 18:44:19 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA17423; Wed, 28 Oct 1998 18:44:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA00825; Wed, 28 Oct 1998 18:43:43 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA49050 for ; Wed, 28 Oct 1998 18:41:18 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id SAA18860 for ; Wed, 28 Oct 1998 18:41:17 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.B0EACB70@smtpgate.uvm.edu>; Wed, 28 Oct 1998 21:41:16 -0500 Message-Id: Date: Wed, 28 Oct 1998 21:41:31 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Michael Talbot-Wilson wrote: > On Wed, 28 Oct 1998, Adam H. Kerman wrote: > > > No one has yet defended any of the askers of inane questions. Can we all agree > > All right. Since you apparently don't know, here is what you do > about askers of inane questions. There are two standard approaches. > You have a choice, you see. Here they are: > > (1) Ignore them. Do not mail them, and certainly don't mail the > list. Remember, 'd' will delete thir mail. > > (2) Mail the person privately with a helpful reply. Certainly, > don't mail the list to exhibit yourself and the wit of your reply. i like this philosophy. if your ken and robin and just want to be cocky, and mean, don't and use the 'd' key. by the way i don't think list moderation is the answer. i think this is the answer -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 19:19:12 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA00208 for ; Wed, 28 Oct 1998 19:19:11 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA17479; Wed, 28 Oct 1998 19:19:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA10781; Wed, 28 Oct 1998 19:18:31 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA47378 for ; Wed, 28 Oct 1998 19:16:39 -0800 Received: from hiway1.exit109.com (root@hiway1.exit109.com [208.225.64.3]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA26192 for ; Wed, 28 Oct 1998 19:16:39 -0800 Received: from locutus.compuwiz.com (root@ppp-1.rb5.exit109.com [208.225.65.71]) by hiway1.exit109.com (8.8.8/8.7.3) with ESMTP id WAA24738 for ; Wed, 28 Oct 1998 22:16:36 -0500 (EST) Received: from localhost (kfonda@localhost) by locutus.compuwiz.com (8.8.7/8.8.7) with ESMTP id WAA32058 for ; Wed, 28 Oct 1998 22:16:08 -0500 Message-Id: Date: Wed, 28 Oct 1998 22:16:07 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Kevin Fonda To: Pine Discussion Forum Subject: patch for Color MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Does any one know of a patch for unix pine to add some color. I'm looking for something like the pre 1.4 version of the Tin news reader. If it's not already availble, I'll make an attempt to add it myself when I get some time. P.S. - I did check the last few months of the list and the FAQ before posting. -- Kevin Fonda Email: kfonda@compuwiz.com 5 Main St. Phone: (732) 223-2013 Manasquan, NJ 08736 Fax : (732) 223-3431 LINUX, the choice of a GNU generation ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 23:00:32 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA02142 for ; Wed, 28 Oct 1998 23:00:31 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA20724; Wed, 28 Oct 1998 23:00:25 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA18591; Wed, 28 Oct 1998 22:59:54 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA23446 for ; Wed, 28 Oct 1998 22:57:24 -0800 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id WAA16181 for ; Wed, 28 Oct 1998 22:57:22 -0800 Received: from sushi.uni-bonn.de (131.220.225.118,17081) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Thu, 29 Oct 98 07:57:08 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id GAA03745; Thu, 29 Oct 1998 06:34:07 +0100 Message-Id: Date: 29 Oct 1998 06:34:07 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: patch for Color In-Reply-To: Kevin Fonda's message of "Wed, 28 Oct 1998 22:16:07 -0500 (EST)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Kevin Fonda writes: > Does any one know of a patch for unix pine to add some color. Check the link section of the pine website or take a look at Sven Guckes' *excellent* Pine pages, there's a link, too. Robin -- The One and Only Robin S. Socha Cc: me and I'll kill -9 you From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Wed, 28 Oct 1998 23:46:40 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA03399 for ; Wed, 28 Oct 1998 23:46:35 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA21301; Wed, 28 Oct 1998 23:46:27 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA03220; Wed, 28 Oct 1998 23:45:58 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA20200 for ; Wed, 28 Oct 1998 23:44:13 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id XAA19623 for ; Wed, 28 Oct 1998 23:44:12 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.01E5BEC0@smtpgate.uvm.edu>; Thu, 29 Oct 1998 2:44:11 -0500 Message-Id: Date: Thu, 29 Oct 1998 02:44:31 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: patch for Color In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 29 Oct 1998, Robin S. Socha wrote: > Date: 29 Oct 1998 06:34:07 +0100 > From: Robin S. Socha > To: Pine Discussion Forum > Subject: Re: patch for Color > Robin > > -- > The One and Only Robin S. Socha > > Cc: me and I'll kill -9 you can't believe Robin "the meany" made me laugh -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 01:53:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA29372 for ; Thu, 29 Oct 1998 01:53:11 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA22408; Thu, 29 Oct 1998 01:53:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id BAA22433; Thu, 29 Oct 1998 01:52:35 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id BAA32714 for ; Thu, 29 Oct 1998 01:50:43 -0800 Received: from green.csi.cam.ac.uk (green.csi.cam.ac.uk [131.111.8.57]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id BAA20024 for ; Thu, 29 Oct 1998 01:50:19 -0800 Received: from line52.slip.csx.cam.ac.uk ([131.111.99.152] helo=cam.ac.uk) by green.csi.cam.ac.uk with smtp (Exim 2.05 #3) id 0zYoiM-0003LM-00; Thu, 29 Oct 1998 09:49:59 +0000 Message-Id: Date: Thu, 29 Oct 1998 09:50:13 +0000 (GMT) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Barry Landy To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Bob Rasmussen X-Cc: Pine Discussion Forum X-X-Sender: bl10@imap.hermes.cam.ac.uk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 28 Oct 1998, Bob Rasmussen wrote: :>I'm sure many who agree with Mr. Talbot-Wilson have refrained from commenting :>for fear of unleashing a more of the behavior about which he complains, or :>have left the list in frustration. Well I'll speak up. I agree completely. :> :>Just about every listserv, online forum, newsgroup, etc. which I have read, if :>not moderated in some fashion, soon sinks to the level of a sewer, with a few :>contributors who can't or won't conform to norms of social decency dominating :>the bandwidth, to the point that the list uses its usefulness. It is, of :>course, useless to try to convince them that they are not valued participants, :>or that they should use some manners. :> :>Other lists, which are moderated at least to the point of preventing abusive :>language, I find to be extremely productive. I community mentality develops, :>where people feel free to ask questions, and others feel free to respond. :> :>If there are others who would like to see this list moderated, I encourage you :>to speak up. Let's not allow the bad to drive out the good. I dont mind the language that much, but what I regret is that this list has become useless for its intended purpose. (For those who dont know, serious technical queries about pine as opposed to newbie style ROTFM queries which should be on the newsgroup). ---------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 1223 334600 Head of Systems and Development Direct line: +44 1223 334713 University of Cambridge Computing Service New Museums Site Email:bl10@cam.ac.uk Pembroke Street, Cambridge CB2 3QG From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 04:53:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA09557 for ; Thu, 29 Oct 1998 04:53:40 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA25428; Thu, 29 Oct 1998 04:53:30 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id EAA19338; Thu, 29 Oct 1998 04:52:30 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id EAA49548 for ; Thu, 29 Oct 1998 04:50:29 -0800 Received: from all-phase.com (cork.all-phase.com [208.136.204.2]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id EAA26591 for ; Thu, 29 Oct 1998 04:50:29 -0800 Received: from all-phase.com (cork [192.168.142.2]) by all-phase.com (8.8.8+Sun/8.8.8) with SMTP id HAA24543 for ; Thu, 29 Oct 1998 07:41:48 -0500 (EST) Message-Id: Date: Thu, 29 Oct 1998 07:53:27 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Candy Cyr - Br 4e Clerical <04eclcac@all-phase.com> To: Pine Discussion Forum Subject: unsubscribe MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Sender: 04eclcac@kirk X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i want to unsubscribe to the pine discussion forum. please let me know what i need to do. i have tried just saying unsubscribe but i'm still on the list. Thank You, Candy Cyr Br 4E - Lafayette ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 07:49:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA04151 for ; Thu, 29 Oct 1998 07:49:19 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA27931; Thu, 29 Oct 1998 07:49:13 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA25678; Thu, 29 Oct 1998 07:48:36 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA49616 for ; Thu, 29 Oct 1998 07:46:30 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA09599 for ; Thu, 29 Oct 1998 07:46:28 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id JAA06702 for ; Thu, 29 Oct 1998 09:46:23 -0600 Message-Id: Date: Thu, 29 Oct 1998 09:46:23 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: unsubscribe In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Candy Cyr - Br 4e Clerical <04eclcac@all-phase.com> >Date: Thu, 29 Oct 1998 07:53:27 -0500 (EST) >i want to unsubscribe to the pine discussion forum. please let me know >what i need to do. i have tried just saying unsubscribe but i'm still on >the list. It's the wrong thing to do. Stop doing that! "unsubscribe" is a command. NEVER send commands to the list posting address. You see this link in the footer appended to every single message? Read it and follow the clear directions given. >----------------------------------------------------------------- > For information about this mailing list, and its archives, see: > http://www.washington.edu/pine/pine-info/ >----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 09:59:11 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA14809 for ; Thu, 29 Oct 1998 09:59:10 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id JAA01975; Thu, 29 Oct 1998 09:58:57 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id JAA08336; Thu, 29 Oct 1998 09:57:47 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA36378 for ; Thu, 29 Oct 1998 09:55:09 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id JAA27529 for ; Thu, 29 Oct 1998 09:55:06 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.59991130@smtpgate.uvm.edu>; Thu, 29 Oct 1998 12:55:05 -0500 Message-Id: Date: Thu, 29 Oct 1998 12:55:13 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Barry Landy X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Barry Landy wrote: > Date: Thu, 29 Oct 1998 09:50:13 +0000 (GMT) > From: Barry Landy > To: Pine Discussion Forum > Subject: Re: A semi-moderated list? > > I dont mind the language that much, but what I regret is that this list > has become useless for its intended purpose. (For those who dont know, > serious technical queries about pine as opposed to newbie style ROTFM > queries which should be on the newsgroup). you think real technical issues aren't going to be asked? they are. they've been submitted simultaneously with some pathetic FAQ's are asked. or does the last have to have a certain status? a -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 Home: Vergennes, VT, US(contrary to the popular belief of Canada) PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 17:28:24 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA23259 for ; Thu, 29 Oct 1998 17:28:23 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA15046; Thu, 29 Oct 1998 17:28:17 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA17961; Thu, 29 Oct 1998 17:27:23 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA49482 for ; Thu, 29 Oct 1998 17:24:56 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA30060 for ; Thu, 29 Oct 1998 17:24:53 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id LAA19025; Fri, 30 Oct 1998 11:54:02 +1030 Message-Id: Date: Fri, 30 Oct 1998 11:54:02 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Aaron S. Hawley" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Aaron S. Hawley wrote: > On Thu, 29 Oct 1998, Barry Landy wrote: > > > Date: Thu, 29 Oct 1998 09:50:13 +0000 (GMT) > > From: Barry Landy > > To: Pine Discussion Forum > > Subject: Re: A semi-moderated list? > > > > I dont mind the language that much, but what I regret is that this list > > has become useless for its intended purpose. (For those who dont know, > > serious technical queries about pine as opposed to newbie style ROTFM > > queries which should be on the newsgroup). > > you think real technical issues aren't going to be asked? they are. > they've been submitted simultaneously with some pathetic FAQ's are asked. > or does the last have to have a certain status? May I suggest a standard reply (for those wish to reply) to newbie-style queries: "Read the mail you were sent when you subscribed to this list." Yes, one would dearly like to say "sent, and ignored", or "Why didn't you read ...", make people clearly aware that it was offensive in them not to read it then, and they are stupid to ask now; but really, that is a temptation that I think is better resisted if the list is to serve its intended purpose. It becomes useless for that purpose more as a result of responses to FAQs than by the asking of them. So use your blowtorch, in private mail PLEASE, on anyone who sends an unnecessary or more amplified response to the list, either a flame or the actual answer. The suggested response could be sent to the list as a warning to others, if you think there is a need, and if that and the briefest quote is sent, no harm is done. Finally, as the person who mailed the comments that started this thread, let me say I didn't have the mauling of lamers in mind at all. I was thinking of another thread then current, which had reason (IMHO:) and a large majority on one side, and a singular fool who was immune to reasonable argument, and could not be silenced, on the other. In the course of his disgusting remarks, in a list with world-wide distribution, he insulted the nations who traditionally have eaten with the bare hand rather than with a knife and fork, and was too witless to know what he did. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 17:40:41 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA23331 for ; Thu, 29 Oct 1998 17:40:40 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA15281; Thu, 29 Oct 1998 17:40:34 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA00428; Thu, 29 Oct 1998 17:39:53 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA26800 for ; Thu, 29 Oct 1998 17:38:02 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA21081 for ; Thu, 29 Oct 1998 17:38:01 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.02FEBEB0@smtpgate.uvm.edu>; Thu, 29 Oct 1998 20:37:57 -0500 Message-Id: Date: Thu, 29 Oct 1998 20:38:14 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN i'm sorry mike but i can't take you seriously, because you fucking Cc'd me. have a good day. On Fri, 30 Oct 1998, Michael Talbot-Wilson wrote: > Date: Fri, 30 Oct 1998 11:54:02 +1030 (CST) > From: Michael Talbot-Wilson > To: Pine Discussion Forum > Subject: Re: A semi-moderated list? > > On Thu, 29 Oct 1998, Aaron S. Hawley wrote: > > > On Thu, 29 Oct 1998, Barry Landy wrote: > > > > > Date: Thu, 29 Oct 1998 09:50:13 +0000 (GMT) > > > From: Barry Landy > > > To: Pine Discussion Forum > > > Subject: Re: A semi-moderated list? > > > > > > I dont mind the language that much, but what I regret is that this list > > > has become useless for its intended purpose. (For those who dont know, > > > serious technical queries about pine as opposed to newbie style ROTFM > > > queries which should be on the newsgroup). > > > > you think real technical issues aren't going to be asked? they are. > > they've been submitted simultaneously with some pathetic FAQ's are asked. > > or does the last have to have a certain status? > > May I suggest a standard reply (for those wish to reply) to > newbie-style queries: "Read the mail you were sent when you > subscribed to this list." > > Yes, one would dearly like to say "sent, and ignored", or "Why > didn't you read ...", make people clearly aware that it was > offensive in them not to read it then, and they are stupid to ask > now; but really, that is a temptation that I think is better > resisted if the list is to serve its intended purpose. > > It becomes useless for that purpose more as a result of responses to > FAQs than by the asking of them. So use your blowtorch, in private > mail PLEASE, on anyone who sends an unnecessary or more amplified > response to the list, either a flame or the actual answer. > > The suggested response could be sent to the list as a warning to > others, if you think there is a need, and if that and the briefest > quote is sent, no harm is done. > > Finally, as the person who mailed the comments that started this > thread, let me say I didn't have the mauling of lamers in mind at > all. I was thinking of another thread then current, which had > reason (IMHO:) and a large majority on one side, and a singular fool > who was immune to reasonable argument, and could not be silenced, on > the other. In the course of his disgusting remarks, in a list with > world-wide distribution, he insulted the nations who traditionally > have eaten with the bare hand rather than with a knife and fork, and > was too witless to know what he did. > > --Mike > > > -- Aaron S. Hawley__ashawley@zoo.uvm.edu__http://www.uvm.edu/~ashawley/ University of Vermont__802.656.7396__Millis 428 Home: Vergennes, VT, USA (contrary to commmon belief of Canada) PC-Pine 4.05 E-Mailer_________________small,fast,simple,complex,free ______________________________________http://www.washington.edu/pine From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 17:56:33 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA23728 for ; Thu, 29 Oct 1998 17:56:32 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id RAA15513; Thu, 29 Oct 1998 17:56:24 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id RAA04995; Thu, 29 Oct 1998 17:55:47 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id RAA40588 for ; Thu, 29 Oct 1998 17:53:58 -0800 Received: from equake.geol.vt.edu (equake.geol.vt.edu [128.173.184.42]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id RAA22660 for ; Thu, 29 Oct 1998 17:53:57 -0800 Received: from localhost (snoke@localhost) by equake.geol.vt.edu (8.6.9/8.6.9) with SMTP id UAA12150 for ; Thu, 29 Oct 1998 20:53:56 -0500 Message-Id: Date: Thu, 29 Oct 1998 20:53:56 -0500 (EST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Arthur Snoke To: Pine Discussion Forum Subject: Cc: and Reply-To MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: snoke@equake X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Apologies if this point has been made, but ... I manage a few listservs, and some are "Discussion Lists" where the default for "Reply" is to the whole list, while others are "Announce Lists" where the default "Reply" is to the actual sender. It seems to me all this Cc: complaining would be solved if this list were handled as a "Discussion List" so that there would be little temptation to choose the "all recipients" option when replying. Or is it more normal for this list that the reply should just go to the original sender? ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 18:20:28 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA12253 for ; Thu, 29 Oct 1998 18:20:27 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA15285; Thu, 29 Oct 1998 18:20:21 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id SAA29357; Thu, 29 Oct 1998 18:19:37 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA24996 for ; Thu, 29 Oct 1998 18:17:45 -0800 Received: from calypso.view.net.au (mtw@calypso.view.net.au [203.30.237.210]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id SAA02552 for ; Thu, 29 Oct 1998 18:17:42 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id MAA19256; Fri, 30 Oct 1998 12:46:57 +1030 Message-Id: Date: Fri, 30 Oct 1998 12:46:57 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Arthur Snoke X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Arthur Snoke wrote: > Apologies if this point has been made, but ... > > I manage a few listservs, and some are "Discussion Lists" where the > default for "Reply" is to the whole list, while others are "Announce > Lists" where the default "Reply" is to the actual sender. It seems to me > all this Cc: complaining would be solved if this list were handled as a > "Discussion List" so that there would be little temptation to choose the > "all recipients" option when replying. Or is it more normal for this list > that the reply should just go to the original sender? For Majordomo, at least, that is a complete solution. Then, you don't even get the "all recipients" prompt. I assume that is true of listserv+pine also. But with very large lists I can understand that owners would want the default reply to the sender. Then (thinking of a million subscribers), even if a large majority of responses go to "all recipients", the small proportion that does not represents a significant mitigation of Net traffic and list server load. From the list owner's perspective, the Cc to the originator and contributers to the thread does not represent significant traffic. --Mike From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 19:32:15 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA23066 for ; Thu, 29 Oct 1998 19:32:14 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id TAA16903; Thu, 29 Oct 1998 19:32:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id TAA23260; Thu, 29 Oct 1998 19:31:38 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA60462 for ; Thu, 29 Oct 1998 19:29:44 -0800 Received: from smtpgate.uvm.edu (smtpgate.uvm.edu [132.198.101.121]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id TAA30873 for ; Thu, 29 Oct 1998 19:29:43 -0800 Received: from [132.198.237.137] (132.198.237.137) by smtpgate.uvm.edu (LSMTP for Windows NT v1.1a) with SMTP id <0.9F459EB0@smtpgate.uvm.edu>; Thu, 29 Oct 1998 22:29:42 -0500 Message-Id: Date: Thu, 29 Oct 1998 22:30:01 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Aaron S. Hawley" To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-X-Sender: ashawley@zoo.uvm.edu X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Fri, 30 Oct 1998, Michael Talbot-Wilson wrote: > Date: Fri, 30 Oct 1998 13:42:04 +1030 (CST) > From: Michael Talbot-Wilson > To: Aaron S. Hawley > Subject: Re: A semi-moderated list? > > > > > > > attack my civility. sounds like you can't defend your laziness. > > > > > > > > > > Nope. Always was lazy. That's why the software has to do it. > > > > > > > > > ring a ding ding. it doesn't do it though! > > > > > > Yes it does. Just a question of configuration. > > > > > but guess what, it's not configured that way right now > > Not my problem. your right it's my problem. cause i have to put up with your shit. and you talked about me being uncivil, when you practice the same shit. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 20:16:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA24954 for ; Thu, 29 Oct 1998 20:16:05 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA17479; Thu, 29 Oct 1998 20:15:59 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id UAA06329; Thu, 29 Oct 1998 20:14:54 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id UAA26694 for ; Thu, 29 Oct 1998 20:12:56 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id UAA01319 for ; Thu, 29 Oct 1998 20:12:55 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id WAA21499 for ; Thu, 29 Oct 1998 22:12:51 -0600 Message-Id: Date: Thu, 29 Oct 1998 22:12:51 -0600 (CST) Reply-To: "Adam H. Kerman" Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Michael Talbot-Wilson >Date: Fri, 30 Oct 1998 12:46:57 +1030 (CST) >On Thu, 29 Oct 1998, Arthur Snoke wrote: >>Apologies if this point has been made, but ... We had a thread about this 2 days ago. >>I manage a few listservs, and some are "Discussion Lists" where the >>default for "Reply" is to the whole list, while others are "Announce >>Lists" where the default "Reply" is to the actual sender. It seems to me >>all this Cc: complaining would be solved if this list were handled as a >>"Discussion List" so that there would be little temptation to choose the >>"all recipients" option when replying. Or is it more normal for this list >>that the reply should just go to the original sender? >For Majordomo, at least, that is a complete solution. Then, you >don't even get the "all recipients" prompt. I assume that is true >of listserv+pine also. You haven't the foggiest idea what you are talking about. Majordomo and LISTSERV are servers. (The platform this list uses is ListProc.) Receipients use clients like pine to reply. But pine isn't a client of the list server but of the mail server on his host or domain. That's several steps removed from the list server. A pine user sees prompts from pine that depend on whether his name was on To, Cc, or Bcc, and whether or not Reply-To was set to the list posting address. The list server is irrelevant. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 21:54:21 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA24827 for ; Thu, 29 Oct 1998 21:54:19 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA18713; Thu, 29 Oct 1998 21:54:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id VAA28400; Thu, 29 Oct 1998 21:53:26 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id VAA46372 for ; Thu, 29 Oct 1998 21:51:32 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id VAA20333 for ; Thu, 29 Oct 1998 21:51:29 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id QAA20357; Fri, 30 Oct 1998 16:20:47 +1030 Message-Id: Date: Fri, 30 Oct 1998 16:20:46 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: A semi-moderated list? In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Aaron S. Hawley" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Aaron S. Hawley wrote: > On Fri, 30 Oct 1998, Michael Talbot-Wilson wrote: > > > Date: Fri, 30 Oct 1998 13:42:04 +1030 (CST) > > From: Michael Talbot-Wilson > > To: Aaron S. Hawley > > Subject: Re: A semi-moderated list? > > > > > > > > > attack my civility. sounds like you can't defend your laziness. > > > > > > > > > > > > Nope. Always was lazy. That's why the software has to do it. > > > > > > > > > > > ring a ding ding. it doesn't do it though! > > > > > > > > Yes it does. Just a question of configuration. > > > > > > > but guess what, it's not configured that way right now > > > > Not my problem. > > your right it's my problem. cause i have to put up with your shit. and > you talked about me being uncivil, when you practice the same shit. You shouldn't have posted private mail on the list and you shouldn't have misrepresented me by selective quoting. If fact I thanked you, with some surprise, for an "almost civil reply". That is all I said on the subject. I meant that that mail item was far more civil than anything you had previously sent. A second point of misrepresentation or misunderstanding: I meant that configuration of the list server was a matter for the list owner. I didn't mean it was your problem. I meant it is something you need to take up with someone else, not with me. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 22:10:46 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA19193 for ; Thu, 29 Oct 1998 22:10:45 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA18359; Thu, 29 Oct 1998 22:10:39 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA10618; Thu, 29 Oct 1998 22:10:04 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA32570 for ; Thu, 29 Oct 1998 22:08:13 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA10195 for ; Thu, 29 Oct 1998 22:08:11 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id QAA20421; Fri, 30 Oct 1998 16:37:19 +1030 Message-Id: Date: Fri, 30 Oct 1998 16:37:19 +1030 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Adam H. Kerman" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Adam H. Kerman wrote: > >don't even get the "all recipients" prompt. I assume that is true > >of listserv+pine also. >... > Receipients use clients like pine to reply. But pine isn't a client of the list > server but of the mail server on his host or domain. That's several steps > removed from the list server. > > A pine user sees prompts from pine that depend on whether his name was on To, > Cc, or Bcc, and whether or not Reply-To was set to the list posting address. > The list server is irrelevant. I assumed that was so. I even said I assumed it was so. I made a more definite statement based on experience with Majordomo. Why do you take a microscope to the matter attempting to find an excuse to send one of your aggressive and unpleasant replies? Why do you send such muck to the _list_ for goodness sake? Trying to impress someone? If only you could see through someone else's eyes the impression of yourself that you convey by these anticks. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 22:32:06 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA25559 for ; Thu, 29 Oct 1998 22:31:56 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA19151; Thu, 29 Oct 1998 22:31:49 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA08499; Thu, 29 Oct 1998 22:31:14 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA60660 for ; Thu, 29 Oct 1998 22:29:30 -0800 Received: from IBM.rhrz.uni-bonn.de (ibm.rhrz.uni-bonn.de [131.220.236.2]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with SMTP id WAA23074 for ; Thu, 29 Oct 1998 22:29:29 -0800 Received: from sushi.uni-bonn.de (131.220.225.71,19004) by IBM.rhrz.uni-bonn.de (IBM/VM SMTP V2R2) with TCP; Fri, 30 Oct 98 07:29:12 MEZ Received: (from robin@localhost) by sushi.uni-bonn.de (8.8.8/8.8.8) id HAA11010; Fri, 30 Oct 1998 07:28:07 +0100 Message-Id: Date: 30 Oct 1998 07:28:07 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: Michael Talbot-Wilson's message of "Fri, 30 Oct 1998 12:46:57 +1030 (CST)" References: Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN * Michael Talbot-Wilson writes: > On Thu, 29 Oct 1998, Arthur Snoke wrote: [...] >> It seems to me all this Cc: complaining would be solved if this list >> were handled as a "Discussion List" so that there would be little >> temptation to choose the "all recipients" option when replying. Or >> is it more normal for this list that the reply should just go to the >> original sender? > For Majordomo, at least, that is a complete solution. Then, you > don't even get the "all recipients" prompt. I assume that is true > of listserv+pine also. [blabla] Don't use pine, use mutt: r reply reply to sender g group-reply reply to all recipients L list-reply reply to mailing list address or use Gnus (I've told it long ago not to Cc: mailing lists). IMO, pine is not well behaved in this respect, and this is particularly annoying when you use it as a newsreader. Apart from that, you still haven't understood what this discussion is about, have you? Robin -- The One and Only Robin S. Socha Cc: me and I'll kill -9 you From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 22:47:03 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA25621 for ; Thu, 29 Oct 1998 22:47:01 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA18817; Thu, 29 Oct 1998 22:46:54 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA08865; Thu, 29 Oct 1998 22:46:27 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA20616 for ; Thu, 29 Oct 1998 22:44:34 -0800 Received: from calypso.view.net.au (calypso.view.net.au [203.30.237.210]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA19541 for ; Thu, 29 Oct 1998 22:44:31 -0800 Received: (from mtw@localhost) by calypso.view.net.au (8.9.1/8.9.1) id RAA20564; Fri, 30 Oct 1998 17:13:41 +1030 Message-Id: Date: Fri, 30 Oct 1998 17:13:41 +1030 (CST) Reply-To: Michael Talbot-Wilson Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Michael Talbot-Wilson To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: "Robin S. Socha" X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 30 Oct 1998, Robin S. Socha wrote: > Don't use pine, use mutt: > r reply reply to sender > g group-reply reply to all recipients > L list-reply reply to mailing list address Yes. The problem with "Reply to all recipients?" is that the consequences of "No" are not entirely clear. You need to answer "Yes" to retain all the addresses, and then (if you remember) you need to manually delete and move addresses. I would rather put it like that, say it is an aspect of Pine that could IMO be improved, than abandon Pine for mutt. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Thu, 29 Oct 1998 23:17:18 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA11685 for ; Thu, 29 Oct 1998 23:17:17 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA19672; Thu, 29 Oct 1998 23:17:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id XAA09482; Thu, 29 Oct 1998 23:16:38 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id XAA46588 for ; Thu, 29 Oct 1998 23:14:46 -0800 Received: from chinet.com (IDENT:ahk@lagnaf-1.soho.enteract.com [216.80.30.1]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id XAA21722 for ; Thu, 29 Oct 1998 23:14:46 -0800 Received: from localhost (ahk@localhost) by chinet.com (8.8.7/8.8.7) with SMTP id BAA24929 for ; Fri, 30 Oct 1998 01:14:41 -0600 Message-Id: Date: Fri, 30 Oct 1998 01:14:41 -0600 (CST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Adam H. Kerman" To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Cc: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN >From: Michael Talbot-Wilson >Date: Fri, 30 Oct 1998 16:37:19 +1030 (CST) >I made a more definite statement based on experience with Majordomo. Then you should have known better. >Why do you take a microscope to the matter attempting to find an excuse to >send one of your aggressive and unpleasant replies? Why do you send such muck >to the _list_ for goodness sake? Apparently for the same reason that you deliberately Cc people when posting to the list. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 00:19:13 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA16983 for ; Fri, 30 Oct 1998 00:19:11 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA19940; Fri, 30 Oct 1998 00:19:05 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id AAA03084; Fri, 30 Oct 1998 00:18:25 -0800 Received: from mxu3.u.washington.edu (mxu3.u.washington.edu [140.142.33.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id AAA63202 for ; Fri, 30 Oct 1998 00:16:25 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu3.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id AAA29730 for ; Fri, 30 Oct 1998 00:16:24 -0800 Received: from fireball.control-risks.de (port204.koeln.ndh.net [195.94.92.204]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id JAA23217 for ; Fri, 30 Oct 1998 09:16:21 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id IAA31587; Fri, 30 Oct 1998 08:57:45 +0100 Message-Id: <19981030085745.B31460@fireball.control-risks.de> Date: Fri, 30 Oct 1998 08:57:45 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: ; from Michael Talbot-Wilson on Fri, Oct 30, 1998 at 05:13:41PM +1030 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Michael Talbot-Wilson (mtw@calypso.view.net.au): > On 30 Oct 1998, Robin S. Socha wrote: > > > Don't use pine, use mutt: > > r reply reply to sender > > g group-reply reply to all recipients > > L list-reply reply to mailing list address > > Yes. The problem with "Reply to all recipients?" is that the > consequences of "No" are not entirely clear. You need to answer > "Yes" to retain all the addresses, and then (if you remember) you > need to manually delete and move addresses. Which you didn't. I still hate Cc:s for mailing lists. I'm *on this list*. > I would rather put it like that, say it is an aspect of Pine that > could IMO be improved, than abandon Pine for mutt. There are quite a few things that could be improved in Pine (see Sven Guckes' website for a wishlist) and this one should be somewhere near the top. Maybe mutt's behaviour needs a little explaining: you define MLs in your muttrc and then you can reply to the List. Gnus is written in Lips and runs under XEmacs, so you have far more options to modify its behaviour. Personally, I've defined strict scoring rules, a different threading, a different from: address and reply behaviour and all mails are scanned for new addresses and URLs. My not-so-humble opinion again: if you read a lot of MLs or generally get a lot of mail, Pine isn't quite the most obvious choice for an MUA. Although mutt is harder to configure, it allows for a couple of neat tricks that only work with dirty hacks or not at all in Pine. Whatever... Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 02:22:09 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA29107 for ; Fri, 30 Oct 1998 02:22:07 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA21875; Fri, 30 Oct 1998 02:22:00 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id CAA16920; Fri, 30 Oct 1998 02:20:12 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id CAA60766 for ; Fri, 30 Oct 1998 02:18:13 -0800 Received: from mg2.rockymtn.net (mailserv.rockymtn.net [166.93.205.12]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id CAA23483 for ; Fri, 30 Oct 1998 02:18:12 -0800 Received: from rainbow.rmi.net (rainbow [166.93.8.14]) by mg2.rockymtn.net (8.8.7/8.8.7) with ESMTP id DAA26641 for ; Fri, 30 Oct 1998 03:18:11 -0700 (MST) Received: from janeway.geekpad.org (nerdherd.evilpeople.net [166.93.72.131]) by rainbow.rmi.net (8.8.7/8.8.5) with ESMTP id DAA18777 for ; Fri, 30 Oct 1998 03:15:18 -0700 (MST) Message-Id: Date: Fri, 30 Oct 1998 04:10:33 -0700 (MST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Ian Hall-Beyer To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: manuka@janeway.geekpad.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On 30 Oct 1998, Robin S. Socha wrote: > Don't use pine, use mutt: > Apart from that, you still haven't understood what this discussion is > about, have you? Obviously you haven't either. From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 05:59:17 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA24433 for ; Fri, 30 Oct 1998 05:59:16 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA24722; Fri, 30 Oct 1998 05:59:08 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id FAA22393; Fri, 30 Oct 1998 05:58:26 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id FAA58694 for ; Fri, 30 Oct 1998 05:56:16 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id FAA32511 for ; Fri, 30 Oct 1998 05:56:15 -0800 Received: from aleph.ii.com ("port 1234"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J3KQVROKKS000C66@mail1.new-york.net> for pine-info@u.washington.edu; Fri, 30 Oct 1998 08:56:03 -0500 (EDT) Message-Id: Date: Fri, 30 Oct 1998 08:55:52 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Sender: ii@mail1.new-york.net X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Thu, 29 Oct 1998, Adam H. Kerman wrote: > A pine user sees prompts from pine that depend on whether his name was on To, > Cc, or Bcc, and whether or not Reply-To was set to the list posting address. And whether or not reply-always-uses-reply-to is set in the pinerc. I do NOT set this feature because I like to get a heads up from Pine that Reply-To was set and then I decide whether I want to honor it or not. Here's how I decide how to reply to discussion group messages (mailing lists and newsgroups): If the message I'm responding to is fairly recent, e.g., within the last week or two, and either I think my response: * will be useful to some other people in the group, or * will let other people in the group know that the person's gotten an answer so they don't need to also respond Then, I reply to the discussion group ONLY. If the message I'm responding to is more than a week or two old, then I often will cc the author just in case they've stopped following the discussion (unless it's someone I know is still reading the group or it's someone I know hates to be cc'd). I also cc the person if he/she asked to be cc'd. When I cc a person I try to put a "posted & mailed" note at the bottom of the message so the person will know they're going to see this msg twice (if they're still reading the group). I think the key to all this is to educate people about how to participate in discussion groups and get people to look at (and think about) the To, Cc, Bcc, and Newsgroups headers before they fire off a message. Also, creating email clients that make it easy to choose where your response goes. Maybe Pine needs to change the "Reply to all recipients" prompt to be "Reply to all, some, or author only?" and then if "some" is chosen, present the user with a list of addresses that can be checked off with T (for To), C (for Cc), B (for Bcc), and N (for Newsgroups). Just an idea... -- Nancy McGough Infinite Ink http://www.ii.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 07:14:14 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA22411 for ; Fri, 30 Oct 1998 07:14:13 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25817; Fri, 30 Oct 1998 07:14:04 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA21917; Fri, 30 Oct 1998 07:12:08 -0800 Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA34638 for ; Fri, 30 Oct 1998 07:10:05 -0800 Received: from public.ndh.com (public.ndh.net [194.97.97.21]) by mxu2.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA05222 for ; Fri, 30 Oct 1998 07:10:04 -0800 Received: from fireball.control-risks.de (port244.koeln.ndh.net [195.94.92.244]) by public.ndh.com (8.8.7/8.8.0) with ESMTP id QAA22857 for ; Fri, 30 Oct 1998 16:09:59 +0100 (MET) Received: (from rss@localhost) by fireball.control-risks.de (8.8.7/8.8.7) id QAA02453; Fri, 30 Oct 1998 16:10:47 +0100 Message-Id: <19981030161046.B2152@fireball.control-risks.de> Date: Fri, 30 Oct 1998 16:10:46 +0100 Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: "Robin S. Socha" To: Pine Discussion Forum Subject: Re: Cc: and Reply-To In-Reply-To: ; from Nancy McGough on Fri, Oct 30, 1998 at 08:55:52AM -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-To: Pine Discussion Forum X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Quoting Nancy McGough (nm@NoAdsPlease.ii.com): > On Thu, 29 Oct 1998, Adam H. Kerman wrote: > > A pine user sees prompts from pine that depend on whether his name was on > > To, > > Cc, or Bcc, and whether or not Reply-To was set to the list posting > > address. [useful comments snipped] > I think the key to all this is to educate people about how to > participate in discussion groups and get people to look at (and think > about) the To, Cc, Bcc, and Newsgroups headers before they fire off a > message. Just to make sure, I checked the docs again, "Getting Started" in this case (for the record: PBhome.gif is missing in the tarball): |Replying to a Message | |To reply to a message that you have selected at the Folder Index screen or |that you are viewing: | |Press R (Reply). | |You are asked whether you want to include the original message in your reply. |Also, if the original message was sent to more than one person, you are asked |if you want to reply to all recipients. Think carefully before you answer-it |may be that you do not want your reply to be sent to more than just the author |of the message. It is always a good idea to check the list of addresses in |the To and Cc fields before you send a message to see who will receive it. I don't think this text is sufficiently clear. Some MLs, for example, have the reply-to hardcoded. This can lead to extremely embarrasing situations in which someone goes "hello, Robin, are you female? I'm a 17 year old stud..." and - apart from receiving a friendly 50MB thank-you-message - has made himself *big* fool in front of hundreds of people. And since you mention News, it should be mentioned that unmarked courtesy copies are extremely annoying. Using Gnus, I kill them off automatically, but it's still BAD to answer a private mail to see that the question has also been asked in the news. IIRC, Pine doesn't add this Cc-notice but it should IMO. Something like: (setq message-insert-courtesy-copy t ; Insert a courtesy message in mail ; copies of combined messages message-courtesy-message ; inserted at the start of a ; mailed copy of a posted message "Mailed and posted \n") > Also, creating email clients that make it easy to choose where your response > goes. Well, they do exist. As I said, both mutt and Gnus support this feature, and it's a Good Thing, too. > Maybe Pine needs to change the "Reply to all recipients" prompt to be > "Reply to all, some, or author only?" and then if "some" is chosen, present > the user with a list of addresses that can be checked off with T (for To), C > (for Cc), B (for Bcc), and N (for Newsgroups). Just an idea... Absolutely. When can we expect your patches }:-> Otherwise, maybe a less technical "walkthrough" or "hands on guide" for beginners might be a good idea. I remember someone having a website with an extremely disgusting cuddly wizard that was far more better suited for "getting started" without falling asleep, but I forget the URL. Maybe something like this could be included in the distribution. Dunno... Robin -- Robin S. Socha From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 07:48:41 -0800 (PST) Return-Path: Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA27851 for ; Fri, 30 Oct 1998 07:48:40 -0800 (PST) Received: from lists5.u.washington.edu (root@lists5.u.washington.edu [140.142.56.6]) by mx1.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA25771; Fri, 30 Oct 1998 07:48:33 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA22999; Fri, 30 Oct 1998 07:47:45 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA34708 for ; Fri, 30 Oct 1998 07:45:56 -0800 Received: from imap.ncsa.es (imap.ncsa.es [194.179.50.6]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA13917 for ; Fri, 30 Oct 1998 07:45:52 -0800 Received: from rdsi224-74.ncsa.es (rdsi224-74.ncsa.es [195.77.224.74]) by imap.ncsa.es (8.8.8/8.8.8) with ESMTP id QAA20483 for ; Fri, 30 Oct 1998 16:45:41 +0100 (CET) Message-Id: Date: =?iso-8859-1?Q?Fri=2C_30_Oct_1998_16=3A45=3A43_+0100_=28Hora?= =?iso-8859-1?Q?_est=E1ndar_romance=29?= Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Lluis Crespo To: Pine Discussion Forum Subject: help MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-X-Sender: crespo@imap.ncsa.es X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Messages index in my sentmail folder looks like this: N 23 xxx 88 To: Juan Vicent S (916) webmail. I think something is wrong in my date configuration, right? Thanks in advance for helping me. Lluis Crespo ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 07:54:23 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA22612 for ; Fri, 30 Oct 1998 07:54:22 -0800 (PST) Received: from lists4.u.washington.edu (root@lists4.u.washington.edu [140.142.56.2]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA26464; Fri, 30 Oct 1998 07:54:16 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id HAA26524; Fri, 30 Oct 1998 07:53:24 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id HAA09640 for ; Fri, 30 Oct 1998 07:51:43 -0800 Received: from out4.ibm.net (out4.ibm.net [165.87.194.239]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id HAA14484 for ; Fri, 30 Oct 1998 07:51:42 -0800 Received: from alpha.computers.org (ssdipola@slip139-92-33-94.lju.si.ibm.net [139.92.33.94]) by out4.ibm.net (8.8.5/8.6.9) with SMTP id PAA05324 for ; Fri, 30 Oct 1998 15:51:26 GMT Message-Id: Date: Fri, 30 Oct 1998 16:50:23 +0100 (MET) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Iztok Polanic To: Pine Discussion Forum Subject: problem in 3.96 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-To: Pine Discussion Forum X-Sender: ssdipola@alpha.computers.org X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hello !!! I don't know if this was corrected in 4.05 but I can't save attachemnts with emty lines between them. It sound's like if I'm using a 16 bit program and OS :) Bye. ////// xxxxxx ( o o ) xx xx /------------oOO-----O-----OOo------------\ xx xx | From: Iztok Polanic | xxxx | E-mail: Iztok.Polanic1@guest.arnes.si | xx xx | WWW: http://kotzi.home.ml.org | xx xx | http://www.intering.si | xx xx | ICQ: Kotzi => *12556824* | \-----------------------------------------/ ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ ----------------------------------------------------------------- From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Fri, 30 Oct 1998 11:39:29 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA05114 for ; Fri, 30 Oct 1998 11:39:28 -0800 (PST) Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA02621; Fri, 30 Oct 1998 11:39:11 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id LAA29311; Fri, 30 Oct 1998 11:37:56 -0800 Received: from mxu1.u.washington.edu (mxu1.u.washington.edu [140.142.32.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id LAA58092 for ; Fri, 30 Oct 1998 11:35:41 -0800 Received: from mail1.new-york.net (SYSTEM@mail1.new-york.net [165.254.2.54]) by mxu1.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id LAA15983 for ; Fri, 30 Oct 1998 11:35:40 -0800 Received: from aleph.ii.com ("port 1212"@aleph.ii.com) by mail1.new-york.net (PMDF V5.1-10 #22885) with ESMTP id <01J3L2QEVRQM000EQX@mail1.new-york.net> for pine-info@u.washington.edu; Fri, 30 Oct 1998 14:35:22 -0500 (EDT) Message-Id: Date: Fri, 30 Oct 1998 14:35:04 -0500 (Eastern Standard Time) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Nancy McGough To: Pine Discussion Forum Subject: Re: PC-Pine 4.05: Still new alternate editor problem In-Reply-To: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII X-Sender: ii@mail1.new-york.net X-To: Pine Discussion Forum X-Cc: Stephen Casner X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN On Wed, 23 Sep 1998, Stephen Casner wrote: > I was so hopeful, seeing a new release come out, then my hopes were > dashed; this problem isn't one of the ones that was fixed in 4.05: > > On Tue, 22 Sep 1998, Stephen Casner wrote: > > PC-Pine 4.04 fixed 4.03's problem of crashing when trying to invoke the > > alternate editor. However, 4.04 asks for the alternate editor command > > to be entered manually rather than using the contents of the "editor" > > variable if that variable contains any arguments in addition to the > > command executable name. I just got this to work in PC-Pine 4.05 by unsetting the pinerc editor variable and setting the EDITOR *environment* variable in my AUTOEXEC.BAT. It's weird that setting the pinerc editor variable doesn't work -- maybe pine gets confused with spaces in the path? FYI, when you set an environment variable, you don't use quotes, e.g., here's what I'm using: SET EDITOR=C:\Program Files\vim-5.3\gvim.exe I also tested it with an argument to see if it would solve Stephen's problem (and it did!). Here's the argument test I did: SET EDITOR=C:\Program Files\vim-5.3\gvim.exe +7 Both of these worked. Good luck, Nancy posted & mailed -- Nancy McGough Infinite Ink http://www.ii.com From pinedev@shiva0.cac.washington.edu Sun ??? 0 00:00:00 1970 +0000 Return-Path: Received: via tmail-4.1(10) (invoked by user mailnull) for mailarch+pine-info; Sat, 31 Oct 1998 22:32:00 -0800 (PST) Return-Path: Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by groupfs.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA29993 for ; Sat, 31 Oct 1998 22:31:58 -0800 (PST) Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by mx2.cac.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA00589; Sat, 31 Oct 1998 22:31:51 -0800 Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with SMTP id WAA05215; Sat, 31 Oct 1998 22:31:13 -0800 Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id WAA61328 for ; Sat, 31 Oct 1998 22:25:38 -0800 Received: from juno.astro.washington.edu (juno.astro.washington.edu [128.95.98.42]) by mxu4.u.washington.edu (8.9.1+UW98.09/8.9.1+UW98.09) with ESMTP id WAA06743 for ; Sat, 31 Oct 1998 22:25:38 -0800 Received: from localhost (reschke@localhost) by juno.astro.washington.edu (8.8.7/8.8.7) with SMTP id WAA18083 for ; Sat, 31 Oct 1998 22:25:37 -0800 Message-Id: Date: Sat, 31 Oct 1998 22:25:37 -0800 (PST) Sender: PINE-INFO-owner@u.washington.edu Precedence: bulk From: Chance Reschke To: Pine Discussion Forum Subject: Secure Pine IMAP Authentication? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Warning: juno.astro.washington.edu: reschke owned process doing -bs X-Sender: reschke@juno X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN Hi, I've been trying to eliminate clear text passwords from our network and had hoped IMAP mail readers could help in this effort. Unfortunately, it looks like Pine can only do IMAP "LOGIN" authentication, not the much more secure "AUTHENTICATE" method. Is this true? (I know about using rsh - That's not what I'm asking about). After looking at packet traces, it seems that the IMAP client in Netscape Communicator uses "AUTHENTICATE LOGIN" when authenticating a user's IMAP session with an IMAP4 server. This appears to prevent the username and password information from traversing the network in clear text. More packet traces reveal that Pine 3.96 appears to use "LOGIN" which passes everything as clear text. I had a quick look through the Pine sources, and couldn't find any reference to the more secure authentication mechanisms. Am I missing something? Thanks, Chance ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/pine/pine-info/ -----------------------------------------------------------------