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/ > ----------------------------------------------------------------- >