From owner-pine-info@cac.washington.edu Fri Oct 1 00:09:13 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19951; Fri, 1 Oct 93 00:09:13 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21863; Thu, 30 Sep 93 22:32:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from camembert.syd.deg.CSIRO.AU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21857; Thu, 30 Sep 93 22:32:12 -0700 Received: by camembert.syd.deg.csiro.au id AA06520 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 1 Oct 1993 15:30:36 +1000 Date: Fri, 1 Oct 1993 15:25:09 +1000 (EST) From: Jack Churchill Subject: Re: Extracting 'dead' attachments To: "Stephen F. Day [Med Ctr Comp Svcs]" Cc: NEIL J LONG , pine-info@cac.washington.edu, "Stephen F. Day [Med Ctr Comp Svcs]" In-Reply-To: <01H3JXUT48QS00081K@MEDUSA.UNM.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 30 Sep 1993, Stephen F. Day [Med Ctr Comp Svcs] wrote: > >Since the VAX mailer cannot forward MIME attachments nor can it read them I > >wondered if someone has a simple program to decode the extracted attachments. > >I guess there are a lot of people who have VAX/VMS accounts who will be facing > >a similar problem as MIME attachments increase in popularity and a VAX port > >of pine seems as far away as ever. > > Although VMS Mail (a *very* out-dated mail system that DEC should seriously > think about revamping!) cannot handle MIME, we have found that Innosoft's PMDF > MAIL product can. I am hoping that Innosoft might someday beef this product up > with a menu interface comparable to Elm or Pine or Gold Mail. I agree totally with your sentiments but one thing must be made clear for correctness. VMS mail does have an undocumented feature to send base64 encoded files. It works to a MIME mailer but unfortunately it doesn't work the other way, i.e., VMS mail won't recognise a MIME attachment (only from another VMS-mailed attachemnt). For some strange reason DEC desided to stall on the base64 feature about the time MIME started to become known and popular. As usual DEC does it first but no follow through. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Fri Oct 1 00:34:07 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20568; Fri, 1 Oct 93 00:34:07 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22595; Fri, 1 Oct 93 00:23:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22589; Fri, 1 Oct 93 00:23:14 -0700 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <06755-0@omega.qmw.ac.uk>; Fri, 1 Oct 1993 08:19:24 +0100 Date: Fri, 1 Oct 1993 08:17:42 +0100 (BST) From: Laurie Cuthbert Subject: pine 3.86 To: pine-info@cac.washington.edu Cc: A.P.Martin@qmw.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A suggestion for the next maintenance release - could we make the location of rimapd configureable in the "build" We like to keep locally installed stuff separate and hence install in /usr/local/sbin. At present we edit the source, but a configuration option would be tidier. Regards Laurie Cuthbert From owner-pine-info@cac.washington.edu Fri Oct 1 02:26:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23208; Fri, 1 Oct 93 02:26:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23407; Fri, 1 Oct 93 02:11:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dir.bris.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23401; Fri, 1 Oct 93 02:11:42 -0700 Received: from adm1.bristol.ac.uk by dir.bris.ac.uk with SMTP (PP) id <03145-0@dir.bris.ac.uk>; Fri, 1 Oct 1993 10:11:35 +0100 Date: Fri, 1 Oct 1993 10:05:35 +0100 (BST) From: Dave King Reply-To: Dave King Subject: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This morning (1st October) the usual "Delete old sent mail" question appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome the problem I used Pine 3.07 to satisfy Pine's requests for dealing with previous months' sent-mail files. I know you're running PTX at Washington, but are you running PTX 2.0.4 and had the same problem? Dave PS Other than that, Pine is fine! ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Email: Dave.King@uk.ac.Bristol (JANET) Email: Dave.King@Bristol.ac.uk (INTERNET) Tel: 0272 303961 (Direct Line) From owner-pine-info@cac.washington.edu Fri Oct 1 03:03:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23816; Fri, 1 Oct 93 03:03:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23567; Fri, 1 Oct 93 02:53:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from runix.runit.sintef.no by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23561; Fri, 1 Oct 93 02:53:49 -0700 Received: from runit.sintef.no by runix.runit.sintef.no id <21246-0@runix.runit.sintef.no>; Fri, 1 Oct 1993 10:53:31 +0100 Date: Fri, 1 Oct 1993 10:49:06 +0100 (MET) From: Steinar Haug Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: Dave King Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > This morning (1st October) the usual "Delete old sent mail" question > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > previous months' sent-mail files. > > I know you're running PTX at Washington, but are you running PTX 2.0.4 and > had the same problem? I had exactly the same problem today, running 3.85 on SunOS 4.1.3 machines. Seemed to hang forever. As an aside, I prefer to save old mail for a long time. It would be nice if Pine did *not* ask if I wanted to delete the old mail folder for *each and every* sent-mail-xxx-1993 folder I have! Is there any way to avoid these questions? Steinar Haug, system/networks administrator SINTEF RUNIT, University of Trondheim, NORWAY Email: Steinar.Haug@runit.sintef.no, Steinar.Haug@delab.sintef.no From owner-pine-info@cac.washington.edu Fri Oct 1 03:05:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23933; Fri, 1 Oct 93 03:05:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23346; Fri, 1 Oct 93 02:02:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23340; Fri, 1 Oct 93 02:02:25 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <06167-0@dummy1.dur.ac.uk>; Fri, 1 Oct 1993 10:02:14 +0100 Received: from draco.dur.ac.uk by vega.dur.ac.uk; Fri, 1 Oct 93 10:02:12 BST Date: Fri, 1 Oct 1993 09:43:10 +0100 (BST) From: Roger Gawley Subject: Re: newsgroup rather than mailing list ? To: Mike Ramey Cc: Pine-Info Email List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 30 Sep 1993, Mike Ramey wrote: > Would it be useful to conduct the pine-info discussion on a newsgroup > rather than via mailing list? (Heresy?) NO (sorry, I cannot find any bigger letters on my keyboard) Mail is available to all and fairly fast. News is available only to some and is variable but mostly slow. I might want to suggest to a > colleague that they look at a message (article) which I have deleted. > With the mailing list, it's gone; with a newsgroup, it's available > (at least for a while). -mr Have you heard of a program called mailbase? Written at the University of Newcastle upon Tyne (just down the road from me), it was conceived as a LISTSERV program for unix but is now much more. It functions as a mailing list expander but you can also archive the messages and read them using gopher. [Type gopher mailbase.ac.uk to see examples.] The program is free to UK eduactional establishment because of its funding. postmaster@mailbase.ac.uk could say what the position is for foreigners. From owner-pine-info@cac.washington.edu Fri Oct 1 04:24:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25645; Fri, 1 Oct 93 04:24:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24205; Fri, 1 Oct 93 04:09:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from rye.city.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24199; Fri, 1 Oct 93 04:08:59 -0700 Received: from hove.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <05614-0@Rye.city.ac.uk>; Fri, 1 Oct 1993 13:06:43 +0100 Date: Fri, 1 Oct 1993 12:07:07 +0100 (BST) From: "D.K.Brownlee" Subject: Re: newsgroup rather than mailing list ? To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Can we gateway it to a newsgroup, so that people who want to read it via news can, and the rest of us can stick with email? D.K.Brownlee@city.ac.uk. Network Analyst. Postmaster. Hostmaster. <_.-^-._> Telephone: (+44) 71 477 8000 Ext:3757. <_.-^-._> Snailmail: E308, City University, Northampton Sq, Islington, London ECIV 0HB. From owner-pine-info@cac.washington.edu Fri Oct 1 04:24:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25682; Fri, 1 Oct 93 04:24:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24262; Fri, 1 Oct 93 04:15:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bart.meiko.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24256; Fri, 1 Oct 93 04:15:15 -0700 Received: by bart.meiko.com id AA01388 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 1 Oct 1993 07:15:13 -0400 Date: Fri, 1 Oct 1993 06:51:26 -0400 (EDT) From: Mike Stok Subject: 3.85 delete old sent-mail slow? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It's the beginning of the month... and I am being asked about deleting my old mail by pine. With 3.85 this seems to take ages, moving the sent-mail to sent-mail-sep-1993 was OK, but it seems to take about 30+ seconds to digest my "n" answer to 'Remove sent-mail-???-1992', then even longer (maybe 90 sec) to *not* delete sent-mail-aug-1992, then another long period to deal with Sep 1992... It even seems to take a long time (a minute or more) to put up the No when I type "n" at the propmt. This is an annoyance to me 'cos I keep a couple of years of mail lurking around by default. For now I can kill pine, rename all the sent-mail-* folders to something else, re-start pine. It fit *my* working pattern if all pine did was to move the sent-mail and then not ask about deleting mail (another addition to the feature list?). I am running 3.85 (with both patches) under SunOS 4.1.3 on a Sun 4c. The CPU meter on the local machine and the remote machine both seem to be at about 0. Sorry if this is one of those problems that loads of people report as they get into work in the morning today :-) Still, loads of features about 3.85 are really excellent (tab completion of folder names, folder collections, saved-name-rule, ...). Thanks again. Mike -- The "usual disclaimers" apply. | Meiko Mike Stok | Reservoir Place Mike.Stok@meiko.waltham.ma.us | 1601 Trapelo Road Meiko tel: (617) 890 7676 | Waltham, MA 02154 From owner-pine-info@cac.washington.edu Fri Oct 1 05:20:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26560; Fri, 1 Oct 93 05:20:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24527; Fri, 1 Oct 93 05:10:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24521; Fri, 1 Oct 93 05:10:55 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA00388; Fri, 1 Oct 93 07:10:31 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA29408; Fri, 1 Oct 93 19:54:41 +0800 Date: Fri, 1 Oct 1993 19:53:30 +0800 (TPE) From: Ed Greshko Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: Steinar Haug Cc: Dave King , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Steinar Haug wrote: > > This morning (1st October) the usual "Delete old sent mail" question > > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > > previous months' sent-mail files. > > > > I know you're running PTX at Washington, but are you running PTX 2.0.4 and > > had the same problem? > > I had exactly the same problem today, running 3.85 on SunOS 4.1.3 machines. > Seemed to hang forever. > > As an aside, I prefer to save old mail for a long time. It would be nice > if Pine did *not* ask if I wanted to delete the old mail folder for *each > and every* sent-mail-xxx-1993 folder I have! Is there any way to avoid these > questions? I had NO problem with this on a MIPS platform. Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Fri Oct 1 05:32:41 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26715; Fri, 1 Oct 93 05:32:41 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08997; Fri, 1 Oct 93 05:19:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mhc.mtholyoke.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08991; Fri, 1 Oct 93 05:19:03 -0700 Received: by mhc.mtholyoke.edu (5.57/Ultrix4.2a_930410.01) id AA19881; Fri, 1 Oct 93 08:18:56 -0400 Date: Fri, 1 Oct 1993 08:15:18 -0400 (EDT) From: "Michael A. Crowley" Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: Steinar Haug Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Steinar Haug wrote: ..... > As an aside, I prefer to save old mail for a long time. It would be nice > if Pine did *not* ask if I wanted to delete the old mail folder for *each > and every* sent-mail-xxx-1993 folder I have! Is there any way to avoid these > questions? > Adding a digit in your .pinerc effectively stops it from ever asking the questions: -------------------------------------------------------------- # Date last time you were asked about deleting old sent-mail last-time-prune-questioned=392.8 -------------------------------------------------------------- mike From owner-pine-info@cac.washington.edu Fri Oct 1 05:35:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26836; Fri, 1 Oct 93 05:35:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09027; Fri, 1 Oct 93 05:27:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mhc.mtholyoke.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09021; Fri, 1 Oct 93 05:27:32 -0700 Received: by mhc.mtholyoke.edu (5.57/Ultrix4.2a_930410.01) id AA20310; Fri, 1 Oct 93 08:27:22 -0400 Date: Fri, 1 Oct 1993 08:20:26 -0400 (EDT) From: "Michael A. Crowley" Subject: Re: newsgroup rather than mailing list ? To: Roger Gawley Cc: Pine-Info Email List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Roger Gawley wrote: > > On Thu, 30 Sep 1993, Mike Ramey wrote: > > Would it be useful to conduct the pine-info discussion on a newsgroup > > rather than via mailing list? (Heresy?) > > NO (sorry, I cannot find any bigger letters on my keyboard) > > Mail is available to all and fairly fast. News is available only to some > and is variable but mostly slow. Mailing lists and news are not mutually exclusive and news, for some, has very rapid distribution. Many lists are sent into and out of news. I'm not sure which way I would end up preferring, but I wouldn't mind having the choice. mike From owner-pine-info@cac.washington.edu Fri Oct 1 06:38:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27870; Fri, 1 Oct 93 06:38:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25053; Fri, 1 Oct 93 06:28:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from danpost4.uni-c.dk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25047; Fri, 1 Oct 93 06:28:32 -0700 Received: from jan-o.uni-c.dk by danpost4.uni-c.dk with SMTP (PP) id <18468-0@danpost4.uni-c.dk>; Fri, 1 Oct 1993 14:27:06 +0100 Date: Fri, 1 Oct 1993 05:54:44 PDT From: Erik Lawaetz Reply-To: Erik Lawaetz Subject: ESC key in PC-pine To: pine-info@cac.washington.edu X-Sender: uniel@danpost4.uni-c.dk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I haven't been following the discussion on PC-pine thoroughly enough to know if this has been suggested already, but after about 10 minutes of usage I already miss something badly. The ability for the ESC key to take me back, e.g. from the addrbook to the main menu. All I get know is an annoyin beep. --Erik From owner-pine-info@cac.washington.edu Fri Oct 1 06:52:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28069; Fri, 1 Oct 93 06:52:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25199; Fri, 1 Oct 93 06:38:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from INFOODS.MIT.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25193; Fri, 1 Oct 93 06:38:35 -0700 Received: from INFOODS.UNU.EDU by INFOODS.UNU.EDU (PMDF V4.2-13 #2603) id <01H3LCK5VGK0000AL0@INFOODS.UNU.EDU>; Fri, 1 Oct 1993 09:37:06 EDT Date: Fri, 01 Oct 1993 09:37:06 -0400 (EDT) From: John C Klensin Subject: RE: MIME character sets, and an apology In-Reply-To: <01H3KDINY2DK9AN313@SIGURD.INNOSOFT.COM> To: NED@SIGURD.INNOSOFT.COM Cc: pine-info@CAC.WASHINGTON.EDU, agulbra@PVV.UNIT.NO Message-Id: <749482626.168726.KLENSIN@INFOODS.UNU.EDU> X-Envelope-To: pine-info@CAC.WASHINGTON.EDU Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Mail-System-Version: Thanks Ned, for that posting. One thing I probably should add to what I said yesterday. The current theory about what to do about the proliferation of MIME- defined character sets is to start issuing Applicability Statements at some point that identify things as, e.g., "good", "not-so-good", and "probably you shouldn't use this trash". Now IETF has been a lot better at talking about A/Ss than about doing them. And the feeling has been to let experience accumulate for some months before trying to get serious about this one. However, if someone has a theory on which such a document could be built, I'd be happy to see a draft proposal. In the meantime and thereafter, mail systems must be prepared to receive character set specifications they haven't heard of before and to handle them in a fairly graceful way. And the meaning of "graceful" is very much a matter of taste. --john From owner-pine-info@cac.washington.edu Fri Oct 1 07:58:32 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29201; Fri, 1 Oct 93 07:58:32 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09425; Fri, 1 Oct 93 07:20:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay1.UU.NET by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09419; Fri, 1 Oct 93 07:20:09 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA07867; Fri, 1 Oct 93 10:20:05 -0400 Received: from racerx.UUCP by uucp4.uu.net with UUCP/RMAIL (queueing-rmail) id 101833.25830; Fri, 1 Oct 1993 10:18:33 EDT Received: from ernie.noname by racerx (4.1/SMI-4.0) id AA09231; Fri, 1 Oct 93 09:01:28 CDT Received: by ernie.noname (4.1/SMI-4.1) id AA21761; Fri, 1 Oct 93 09:01:23 CDT Date: Fri, 1 Oct 1993 08:58:35 -0500 (CDT) From: Ken Hardy Subject: newsgroup rather than mailing list ? (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII >rather than via mailing list? (Heresy?) I might want to suggest to a >colleague that they look at a message (article) which I have deleted. >With the mailing list, it's gone; with a newsgroup, it's available >(at least for a while). -mr I have a couple of mailing lists that I have redirected to a file as well as to my inbox. Said file needs to be trimmed by hand, but not very often if you have the disk space (I trim sometimes only at the first of the year.) I don't know if you can do this (depends on your system & your privilege), but here is what I've done, e.g. I've subscribed to the firewalls mailing list as user "firewalls". Then I put these aliases into the aliases file on my mail gateway: firewalls: fwall_folks, fwall_file fwall_folks: ken,max fwall_file: /home/ken/security/firewall-list The mail to "firewalls" gets split to "fwall_folks" and "fwall_file". You can see that Ken & Max get the list in their inboxes, and the traffic goes to a file under my home directory as well. This file can be read as a mail folder. I encourage all users here to subscribe to lists in this way whether or not the redirection to a file is used; local readers can be added to and subtracted from the list without bothering the mailing list maintainer, and only 1 copy of each article needs to be sent & received. This is how I subcribe to the Pine mailing list (it doesn't go to a file.) Ken Hardy ken@bridge.com (racerx!ken) --__-_____--__-__--_--__-___-__-__-___---- From owner-pine-info@cac.washington.edu Fri Oct 1 08:16:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29811; Fri, 1 Oct 93 08:16:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25914; Fri, 1 Oct 93 07:43:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from geneva.ucs.indiana.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25908; Fri, 1 Oct 93 07:43:56 -0700 Received: from loris.cisab.indiana.edu by PO5.Indiana.Edu; id AA14617 (5.65c+jsm/2.5.1jsm); Fri, 1 Oct 1993 09:43:55 -0500 Received: by loris.cisab.indiana.edu (AIX 3.2/UCB 5.64/4.03) id AA20619; Fri, 1 Oct 1993 09:42:18 -0500 Date: Fri, 1 Oct 1993 09:39:58 -0500 (EST) From: Shan Duncan Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Dave King wrote: > Date: Fri, 1 Oct 1993 10:05:35 +0100 (BST) > From: Dave King > To: pine-info@cac.washington.edu > Subject: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) > > This morning (1st October) the usual "Delete old sent mail" question > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > previous months' sent-mail files. Same problem but running on a RS6000 530H and AIX 3.2.4 with each question taking longer and longer... Switched back to 3.07 and had no problems. ---------------------------------------------------------------------------- Dr. Shan Duncan duncan@loris.cisab.indiana.edu CISAB- Indiana University sdduncan@indiana.edu 402 N. Park Ave Bloomington, IN. 47405 (812) 855-5895 (812) 855-9663 (main office) (812) 855-0411 (FAX) ------------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Fri Oct 1 08:53:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01337; Fri, 1 Oct 93 08:53:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26918; Fri, 1 Oct 93 08:40:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from corona.med.utah.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26912; Fri, 1 Oct 93 08:40:12 -0700 Received: from comet.med.utah.edu by corona.med.utah.edu (4.1/SMI-4.0 [uucc-nhj/15FEB1991]) id AA15074; Fri, 1 Oct 93 09:40:00 MDT Received: by comet.med.utah.edu (5.57/Ultrix3.0-C) id AA07058; Fri, 1 Oct 93 09:39:59 -0600 Date: Fri, 1 Oct 1993 09:38:16 -0600 (MDT) From: "Paul G. Leo Jr." Subject: delete sent-mail under 3.85 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII i'm experiencing same problem regarding slowness in delete sendmail -- the platform is different though -- decstation 3000 running ultrix v4.2 pine's great!!!! Paul Leo e-mail paulleo@comet.med.utah.edu University of Utah Medical School paulleo@utahmed.bitnet Eccles Institute of Human Genetics Building 533 Room 2100 phone 801-585-3653 Salt Lake City, Utah 84106 fax 801-585-3910 From owner-pine-info@cac.washington.edu Fri Oct 1 08:56:07 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01484; Fri, 1 Oct 93 08:56:07 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26960; Fri, 1 Oct 93 08:41:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26954; Fri, 1 Oct 93 08:41:19 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <05262-0@susssys1.reading.ac.uk>; Fri, 1 Oct 1993 16:40:52 +0100 Date: Fri, 1 Oct 1993 16:38:12 +0100 (BST) From: Mike Roch Reply-To: Mike Roch Subject: inbox-path in /usr/local/lib/pine-conf To: pine-info@cac.washington.edu Cc: Neal Curran x8432 , Adrian Bassett x8432 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We have a Solaris machine and ~100 SunOS 4.1.n other machines. For the moment we're happy to run Pine in binary-compatibility mode on Solaris, but the mail spool is in /var/mail and not /var/spool/mail. The actual mailboxes (held on SunOS 4) are mounted by the Solaris machine at /var/mail. Our problem is how to allow users (who move from one machine to another) to see their mail. We don't really want to use IMAP; why make them "login again"? If they edit "inbox-path" to /var/mail/_username_ they're Ok until they switch machines. If we setup inbox-path in /usr/local/lib/pine-conf on the Solaris machine, we can't name each user's - we need to be able to say /var/spool/$USER or somesuch). If we link /var/spool/mail to /var/mail then Barry Cornelius reports locking problems.(See below) Advice please! Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AF Fax: 0734 753094 Date: Wed, 17 Mar 1993 18:47:01 +0000 (GMT) From: Barry Cornelius To: pine-info@edu.washington.cac Subject: Re: Pine and Solaris It is possible to run SunOS 4.1.x binaries with SunOS 5.1 (which is part of Solaris 2.1) if you use the Binary Compatibility Package. I have tried this with a SunOS 4.1.x binary of pine. Most aspects of pine will work. For example, this message was sent from a 4.1.2 binary running on a machine with SunOS 5.1. However, I found a problem with file locking. This problem occurs in two places: (1) if you use NFS to mount /var/spool/mail rather than use IMAP, then pine hangs on starting it up. For example, you can't get the mail index, and there is a lock on your mailbox; (2) if you use the g command to goto a folder, then pine hangs: there is a lock on the file containing the folder. From owner-pine-info@cac.washington.edu Fri Oct 1 09:16:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02282; Fri, 1 Oct 93 09:16:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27171; Fri, 1 Oct 93 08:51:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27165; Fri, 1 Oct 93 08:51:19 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15209; Fri, 1 Oct 93 08:50:45 -0700 Date: Fri, 1 Oct 1993 08:39:37 -0700 (PDT) From: David L Miller Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: Pekka Kytolaakso Cc: Mark Crispin , Joseph Brennan , pine-info@cac.washington.edu In-Reply-To: <9309302145.AA26818@tellus.csc.fi> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 30 Sep 1993, Pekka Kytolaakso wrote: > Your message dated: Thu, 30 Sep 1993 12:10:32 MST > > On Thu, 30 Sep 1993 13:17:43 -0400 (EDT), Joseph Brennan wrote: > > > Has someone got a fix for the Mac NCSA Telnet problem with ^J ? It's= been > > > making us crazy here. I actually modified Pico/Pine to avoid ^J as a > > > command but that'll be annoying to do with each release. If I can in= stall > > > a standard 3.85 I'd be happy. > >=20 > A way (hack :-) might be to add a configuration parameter (yes, one more) > like=20 >=20 > # fill-command defines the control chacter used to fill paragraphs > # the default value is 11 (^J), 0 means fill no in use=20 > fill-command=3D >=20 A much better solution would be to provide a general keyboard remapping=20 capability (and not much more work). > The problems with this are > =09- screen-menu shows ^J as fill (runtime change) > =09- help file has wrong key (must edit help-file) >=20 > Neither of these are serious because when a user changes this he should > now what the fill command is. >=20 > I just looked and found a problem with this. There are few free keys. I > think ^W and ^] are about the only unused ones. A way around this would m= e to > make some key (like ^X) a prefix-key and make some seldom-used > functions two-key commands. I can suggest several like spell (^X^S), > read (^X^R), postpone (^X^P), send (^X^C),... . If pressing the prefix > (^X) changes the menu at the bottom of the screen tit isn't much harder > to use that pine/pico now are (and most people need to know emacs anyway)= . >=20 ^W is search, ^] is frequently a telnet escape. One of the fundamental=20 principles of Pine is to not have any multi-key sequences. This leaves=20 us with very few keys left indeed :( > Pekka Kyt=F6laakso > --------------------------------------------------------------- > netmgr@tellus.csc.fi Centre for Scientific Computing > Pekka.Kytolaakso@csc.fi PL 40 SF-02101 Espoo FINLAND > Phone: +358 0 4571 Telefax: + 358 0 4572302 From owner-pine-info@cac.washington.edu Fri Oct 1 09:17:18 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02348; Fri, 1 Oct 93 09:17:18 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09945; Fri, 1 Oct 93 09:05:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sdac.harvard.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09939; Fri, 1 Oct 93 09:05:46 -0700 Received: by sdac.harvard.edu (5.57/Ultrix3.0-C) id AA10731; Fri, 1 Oct 93 12:05:08 -0400 Date: Fri, 1 Oct 1993 11:48:07 -0400 (EDT) From: Art Gaer Subject: Re: Delete old sent-mail problem (Pine 3.85 on ULTRIX 4.2A) To: Steinar Haug Cc: Dave King , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Steinar Haug wrote: > > This morning (1st October) the usual "Delete old sent mail" question > > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > > previous months' sent-mail files. > > > I had exactly the same problem today, running 3.85 on SunOS 4.1.3 machines. > Seemed to hang forever. > > As an aside, I prefer to save old mail for a long time. It would be nice > if Pine did *not* ask if I wanted to delete the old mail folder for *each > and every* sent-mail-xxx-1993 folder I have! Is there any way to avoid these > questions? > I also had the problem early this morning with it taking *forever* to accept my "no" for removing the old sent-mail folders. I think it literally took *minutes* to respond to each keypress. I never had any problem like this under Pine 3.05 and 3.07, perfectly normal response time when this question appeared. This is on a DEC RISC box running ULTRIX 4.2A. Note that I was trapped at 1:00 am when dialing in from home, because at the "Delete sent-mail-xxx-1993?" prompt neither Ctrl-C nor Ctrl-Z had any effect, these keypresses were just ignored, so I couldn't easily break out of the Pine process and rename the folders. Once I did rename the folders (to mail-xxx-1993) everything functioned normally. I agree that it would be a nice configuration option to have it not ask you about removing old sent-mail folders. I too keep my mail around for a long time, and it would be awfully nice to not have to hit Return 20 times on the first of every month. ---------------------------------------- Art Gaer Unix Systems Analyst gaer@sdac.harvard.edu (617) 432-2521 Statistical & Data Analysis Center, Dept. of Biostatistics Harvard University, School of Public Health From owner-pine-info@cac.washington.edu Fri Oct 1 09:20:49 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02556; Fri, 1 Oct 93 09:20:49 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27605; Fri, 1 Oct 93 09:10:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from watsun.cc.columbia.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27599; Fri, 1 Oct 93 09:10:13 -0700 Received: by watsun.cc.columbia.edu (5.59/FCB/jba) id AA16185; Fri, 1 Oct 93 12:10:11 EDT Date: Fri, 1 Oct 93 12:10:10 EDT From: Joe Brennan To: David L Miller Cc: Pekka Kytolaakso , Mark Crispin , pine-info@cac.washington.edu Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 In-Reply-To: Your message of Fri, 1 Oct 1993 08:39:37 -0700 (PDT) Message-Id: You have to change some other control-commands. I ended up killing spellcheck and using its letter for fill-para, since other "good" control letters are used up. I'm not happy with it but it makes Pine usable and that's what I want. It's a batch of changes since the actual command, menu, and help all have to be fixed, and ^J has to be made a synonym for ^M in several places. It's a Pine bug as far as I'm concerned. The rest of it is good enough to make it worthwhile to fix. We did skip 3.07 to avoid doing it though. Joseph Brennan Academic Information Systems Columbia University in the City of New York brennan@columbia.edu From owner-pine-info@cac.washington.edu Fri Oct 1 09:50:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03792; Fri, 1 Oct 93 09:50:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28063; Fri, 1 Oct 93 09:34:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28055; Fri, 1 Oct 93 09:33:55 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <14300-0@dummy1.dur.ac.uk>; Fri, 1 Oct 1993 17:32:20 +0100 Received: from deneb.dur.ac.uk by vega.dur.ac.uk; Fri, 1 Oct 93 17:32:18 BST Date: Fri, 1 Oct 1993 17:31:47 +0100 (BST) From: Barry Cornelius Reply-To: Barry Cornelius Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Mike Roch Cc: pine-info@cac.washington.edu, Neal Curran x8432 , Adrian Bassett x8432 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 1 Oct 1993, Mike Roch wrote: > [stuff deleted] > ... If we link > /var/spool/mail to /var/mail then Barry Cornelius reports locking > problems.(See below) Advice please! > > Mike > > ============================================================================== > Mike Roch, Computer Services Centre, Tel: 0734 318430 > The University, Whiteknights, Reading, RG6 2AF Fax: 0734 753094 > > Date: Wed, 17 Mar 1993 18:47:01 +0000 (GMT) > From: Barry Cornelius > To: pine-info@edu.washington.cac > Subject: Re: Pine and Solaris > > It is possible to run SunOS 4.1.x binaries with SunOS 5.1 (which is part > of Solaris 2.1) if you use the Binary Compatibility Package. I have tried > this with a SunOS 4.1.x binary of pine. Most aspects of pine will work. > For example, this message was sent from a 4.1.2 binary running on a > machine with SunOS 5.1. > > However, I found a problem with file locking. This problem occurs in two > places: > (1) if you use NFS to mount /var/spool/mail rather than use > IMAP, then pine hangs on starting it up. For example, you can't > get the mail index, and there is a lock on your mailbox; > (2) if you use the g command to goto a folder, then pine hangs: > there is a lock on the file containing the folder. Although I was certainly under the impression that there were file-locking problems using a 4.1.x binary with SunOS 5.1 back in March, at a later date (perhaps in May) I was unable to reproduce the problem. We have successfully used a 4.1.2 binary on a 5.2 system without any problems. I thought I had sent a message to the pine-info mailing list retracting my words, but I can't find it in my back numbers of this list. I'm sorry if I have misled anyone. -- Barry Cornelius Electronic mail: Barry.Cornelius@durham.ac.uk Post: Computing Service, University of Durham, Durham, DH1 3LE, England Phone: Durham (091 or +44 91) 374 4717, Secretary:374 2892, Fax:374 3741 From owner-pine-info@cac.washington.edu Fri Oct 1 09:55:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04062; Fri, 1 Oct 93 09:55:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28227; Fri, 1 Oct 93 09:40:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cliff.nalusda.gov by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28221; Fri, 1 Oct 93 09:40:53 -0700 Received: by cliff.nalusda.gov (4.1/SMI-4.1) id AA11148; Fri, 1 Oct 93 12:41:46 EDT Date: Fri, 1 Oct 1993 12:41:45 -0400 (EDT) From: Martha Feldman Subject: Re: Good Windows Terminal Emulator? To: "Jason R. Thorpe" Cc: Mike Stok , pine-info@cac.washington.edu In-Reply-To: Message-Id: We've recently switched to WINQVT/net version 3.6 here and printing is not functioning well at all. It's slow, keeps defaulting to a doublestike font, and inserts a separator page between each message printed. Perhaps these problems have been corrected in later versions. We've seen a version 3.93 on the net but haven't tried it yet. ***************************** Martha Feldman Information Systems Division National Agricultural Library Beltsville, Maryland Internet: mfeldman@nalusda.gov Phone: (301) 504-6813 Fax: (301) 504-7473 ******************************* On Thu, 30 Sep 1993, Jason R. Thorpe wrote: > On Thu, 30 Sep 1993, Mike Stok wrote: > > > I was wondering if there's a good termainal emulation package which runs > > under Windows on a PC which allows the ansi printing escapes to be used > > in an "intuitive" way. Currently a user of mine uses the Windows Term > > program, but can't seem to make printing work... > > Crosstalk for Windows works, as well as Procomm+ for Windows. If you're > looking for shareware, look for WinQVT. I've used all three and they all > work great... > > Later... > > ------------------------------------------------------------------------------ > Jason R. Thorpe | | 434 Weatherford Hall > OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 > Support Staff | | (503) 737-9533 > > From owner-pine-info@cac.washington.edu Fri Oct 1 10:05:03 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04539; Fri, 1 Oct 93 10:05:03 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10129; Fri, 1 Oct 93 09:47:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [128.193.164.25] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10123; Fri, 1 Oct 93 09:47:12 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA14612; Fri, 1 Oct 93 09:47:55 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA15496; Fri, 1 Oct 93 09:50:02 -0700 Date: Fri, 1 Oct 1993 09:48:59 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: Dave King Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Dave King wrote: > This morning (1st October) the usual "Delete old sent mail" question > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > previous months' sent-mail files. > > I know you're running PTX at Washington, but are you running PTX 2.0.4 and > had the same problem? We run PTX 2.0.3 on a fairly old S81...No such problem for us... Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Fri Oct 1 10:10:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04681; Fri, 1 Oct 93 10:10:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28514; Fri, 1 Oct 93 09:53:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28506; Fri, 1 Oct 93 09:53:03 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17004; Fri, 1 Oct 93 09:53:02 -0700 Date: Fri, 1 Oct 1993 09:22:08 -0700 (PDT) From: Michael Seibel Subject: Re: Delete old sent-mail problem (Pine 3.85 on ULTRIX 4.2A) To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1278806922-749494381:#15877" --0-1278806922-749494381:#15877 Content-Type: TEXT/PLAIN; charset=US-ASCII As many of you have discovered by now, there is a bug in pine 3.85 that can cause inordinate delays in the monthly sent-mail pruning. The bug has to do with a sleep intended to introduce a *brief* delay before over writing the message line with a new prompt. The bug has nothing to do with the actual pruning itself, and all folders are copied properly (if you have the patience to wait long enough). There are a couple of ways to work around the problem. As suggested here, fooling pine into not prompting by editing the .pinerc is one option. Setting the "last-time-prune-questioned" variable to "93.10" or deleting the date altogether should do it. This is the best fix if the "sent-mail" folder is part of a remote collection (i.e., the first folder-collection listed is remote). The other option, also suggested here, is to run an older pine version to handle the pruning. Attached is the diff for the fix that will be in the pine 3.86 maintenance release next week. It takes a much less "sophisticated" approach to figuring out any necessary delay. We'll also take a look at options for turning off the pruning in general. My sincerest apologies for any problems this has caused. Michael Seibel Networks and Distributed Computing mikes@cac.washington.edu University of Washington, Seattle (206) 543 - 0359 --0-1278806922-749494381:#15877 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="delay.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Delay bug patch KioqIHN0YXR1cy5jLm9sZAlGcmkgU2VwIDI0IDEyOjIxOjA1IDE5OTMKLS0t IHN0YXR1cy5jCUZyaSBPY3QgIDEgMDk6MzQ6NDIgMTk5MwoqKioqKioqKioq KioqKioKKioqIDU0OSw1NjggKioqKgogICAgICByZWdpc3RlciBpbnQgIGNo LCByZWFsX2xpbmU7CiAgICAgIGNoYXIgICAgICAgICAqcSwgKnAsICoqbGw7 CiAgICAgIGludCAgICAgICAgICAgY3Vyc29yX21vdmVkLCBtYXhfbGFiZWw7 Ci0gICAgIGxvbmcgICAgICAgICAgbm93LCBkaWZmLCBxdWV1ZV90aW1lOwog IAogICAgICAvKi0tLS0KICAgICAgICAgR2l2ZSB0aGUgdXNlciB0aW1lIHRv IHNlZSB0aGUgc3RhdHVzIG1lc3NhZ2UgdGhhdCB3YXMKICAgICAgICBqdXN0 IHB1dCB1cCBpZiB0aGVyZSB3YXMgb25lLgogICAgICAgIC0tLS0qLwohICAg ICBxdWV1ZV90aW1lID0gbWVzc2FnZXNfcXVldWVkKCk7CiEgICAgIGlmKHF1 ZXVlX3RpbWUgPiAwKSB7CiEgCS8qIG1lc3NhZ2UgaXMgc2hvd2luZyAqLwoh IAlub3cgPSB0aW1lKDApOwohIAlkaWZmID0gbm93IC0gKGRpc3BsYXllZF90 aW1lICsgcXVldWVfdGltZSk7CiEgCWlmKGRpZmYgPiAwKSAKISAJICAgIHNs ZWVwKGRpZmYpOwohICAgICB9IAogICAgICBuZWVkc19jbGVhcmluZyA9IDE7 CiAgCiAgICAgIG1hcmtfc3RhdHVzX2RpcnR5KCk7Ci0tLSA1NDksNTYyIC0t LS0KICAgICAgcmVnaXN0ZXIgaW50ICBjaCwgcmVhbF9saW5lOwogICAgICBj aGFyICAgICAgICAgKnEsICpwLCAqKmxsOwogICAgICBpbnQgICAgICAgICAg IGN1cnNvcl9tb3ZlZCwgbWF4X2xhYmVsOwogIAogICAgICAvKi0tLS0KICAg ICAgICAgR2l2ZSB0aGUgdXNlciB0aW1lIHRvIHNlZSB0aGUgc3RhdHVzIG1l c3NhZ2UgdGhhdCB3YXMKICAgICAgICBqdXN0IHB1dCB1cCBpZiB0aGVyZSB3 YXMgb25lLgogICAgICAgIC0tLS0qLwohICAgICBpZihtZXNzYWdlc19xdWV1 ZWQoKSkKISAgICAgICBzbGVlcCgzKTsKISAKICAgICAgbmVlZHNfY2xlYXJp bmcgPSAxOwogIAogICAgICBtYXJrX3N0YXR1c19kaXJ0eSgpOwo= --0-1278806922-749494381:#15877-- From owner-pine-info@cac.washington.edu Fri Oct 1 10:12:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04760; Fri, 1 Oct 93 10:12:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28634; Fri, 1 Oct 93 09:57:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28628; Fri, 1 Oct 93 09:57:02 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27224; Fri, 1 Oct 93 09:56:56 -0700 Date: Fri, 1 Oct 1993 09:52:58 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: Joe Brennan Cc: David L Miller , Pekka Kytolaakso , Mark Crispin , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 1 Oct 1993, Joe Brennan wrote: > It's a Pine bug as far as I'm concerned. The rest of it is good enough > to make it worthwhile to fix. We did skip 3.07 to avoid doing it > though. We disagree. It seems clear that the bug is in the NextStep telnetd. -teg From owner-pine-info@cac.washington.edu Fri Oct 1 10:13:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04847; Fri, 1 Oct 93 10:13:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10201; Fri, 1 Oct 93 09:57:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from earth.eecs.uic.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10195; Fri, 1 Oct 93 09:57:33 -0700 Received: from mal.eecs.uic.edu by earth.eecs.uic.edu with SMTP id AA11063 (5.64+/IDA-1.3.4 for pine-info@cac.washington.edu); Fri, 1 Oct 93 11:57:04 -0500 Received: by mal.eecs.uic.edu (920330.SGI/890607.SGI) (for @earth.eecs.uic.edu:pine-info@cac.washington.edu) id AA11129; Fri, 1 Oct 93 11:57:42 -0500 Date: Fri, 1 Oct 1993 11:55:57 -0500 (CDT) From: Sanjay Gowda Subject: Re: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Shan Duncan wrote: > On Fri, 1 Oct 1993, Dave King wrote: > > > Date: Fri, 1 Oct 1993 10:05:35 +0100 (BST) > > From: Dave King > > To: pine-info@cac.washington.edu > > Subject: Delete old sent-mail problem (Pine 3.85 on DYNIX PTX 2.0.4) > > > > This morning (1st October) the usual "Delete old sent mail" question > > appeared to take a l-o-n-g time to do it's job, i.e. hang. To overcome > > the problem I used Pine 3.07 to satisfy Pine's requests for dealing with > > previous months' sent-mail files. > > > > Same problem but running on a RS6000 530H and AIX 3.2.4 with each > question taking longer and longer... > > Switched back to 3.07 and had no problems. > > > > ---------------------------------------------------------------------------- > Dr. Shan Duncan duncan@loris.cisab.indiana.edu > CISAB- Indiana University sdduncan@indiana.edu > 402 N. Park Ave > Bloomington, IN. 47405 > (812) 855-5895 (812) 855-9663 (main office) (812) 855-0411 (FAX) > ------------------------------------------------------------------------------ > Same problem here. I am running pine 3.85 on an SGI Personal IRIS running IRIX 4.0.5. Sanjay From owner-pine-info@cac.washington.edu Fri Oct 1 10:16:15 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05093; Fri, 1 Oct 93 10:16:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10239; Fri, 1 Oct 93 10:02:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10233; Fri, 1 Oct 93 10:02:28 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA13977; Fri, 1 Oct 93 09:56:48 -0700 Date: Fri, 1 Oct 1993 09:51:49 -0700 (PDT) From: Mark Crispin Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Barry Cornelius Cc: Mike Roch , pine-info@cac.washington.edu, Neal Curran x8432 , Adrian Bassett x8432 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to add a note of caution. Granted, I'm ``Mr. IMAP'' so you may need to take this with more than the usual grain of salt (a 20 ton boulder of salt, some may say...). But, I think that using NFS as a means of remote access to mail is, in general, a horrible idea. There is a reason that I invented IMAP. The problems range from performance, to scaling, to being able to enforce locks across the network. The extra password problem can be solved by use of the rimap mechanism, and we *will* be supporting Kerberos, perhaps sooner rather than later. We've tried our best to make NFS access work, due to the demand for it, but there are known sharp edges that will get you if you aren't careful. From owner-pine-info@cac.washington.edu Fri Oct 1 10:21:25 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05376; Fri, 1 Oct 93 10:21:25 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10307; Fri, 1 Oct 93 10:08:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [128.193.164.25] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10301; Fri, 1 Oct 93 10:08:15 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA15041; Fri, 1 Oct 93 10:08:51 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA15513; Fri, 1 Oct 93 10:11:00 -0700 Date: Fri, 1 Oct 1993 10:10:38 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Good Windows Terminal Emulator? To: Martha Feldman Cc: Mike Stok , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Martha Feldman wrote: > We've recently switched to WINQVT/net version 3.6 here and printing is not > functioning well at all. It's slow, keeps defaulting to a doublestike > font, and inserts a separator page between each message printed. Perhaps > these problems have been corrected in later versions. We've seen a version > 3.93 on the net but haven't tried it yet. I was using an old version of QVT (dialup)... > > ***************************** > Martha Feldman > Information Systems Division > National Agricultural Library > Beltsville, Maryland > Internet: mfeldman@nalusda.gov > Phone: (301) 504-6813 > Fax: (301) 504-7473 > ******************************* > > > On Thu, 30 Sep 1993, Jason R. Thorpe wrote: > > > On Thu, 30 Sep 1993, Mike Stok wrote: > > > > > I was wondering if there's a good termainal emulation package which runs > > > under Windows on a PC which allows the ansi printing escapes to be used > > > in an "intuitive" way. Currently a user of mine uses the Windows Term > > > program, but can't seem to make printing work... > > > > Crosstalk for Windows works, as well as Procomm+ for Windows. If you're > > looking for shareware, look for WinQVT. I've used all three and they all > > work great... > > > > Later... > > > > ------------------------------------------------------------------------------ > > Jason R. Thorpe | | 434 Weatherford Hall > > OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 > > Support Staff | | (503) 737-9533 > > > > > ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Fri Oct 1 10:25:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05592; Fri, 1 Oct 93 10:25:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10325; Fri, 1 Oct 93 10:10:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [128.193.164.25] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10319; Fri, 1 Oct 93 10:10:57 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA15112; Fri, 1 Oct 93 10:11:38 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA15518; Fri, 1 Oct 93 10:13:46 -0700 Date: Fri, 1 Oct 1993 10:12:14 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Mike Roch Cc: pine-info@cac.washington.edu, Neal Curran x8432 , Adrian Bassett x8432 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 1 Oct 1993, Mike Roch wrote: > We have a Solaris machine and ~100 SunOS 4.1.n other machines. > > For the moment we're happy to run Pine in binary-compatibility mode on > Solaris, but the mail spool is in /var/mail and not /var/spool/mail. > > The actual mailboxes (held on SunOS 4) are mounted by the Solaris machine > at /var/mail. Our problem is how to allow users (who move from one machine > to another) to see their mail. We don't really want to use IMAP; why make > them "login again"? If they edit "inbox-path" to /var/mail/_username_ ^^^^^^^^^^^^^ Not necessary if you use the pre-auth feature (rimapd). It's described in the tech-notes. Each user must have a .rhosts in their home directory with the appropriate entries... Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Fri Oct 1 10:29:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05789; Fri, 1 Oct 93 10:29:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29027; Fri, 1 Oct 93 10:17:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from convex.csc.fi by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29021; Fri, 1 Oct 93 10:16:58 -0700 Received: from tellus.csc.fi by csc.fi with SMTP id AA17045 (5.65c8+/IDA-1.4.4); Fri, 1 Oct 1993 19:16:58 +0200 Received: from localhost.csc.fi by tellus.csc.fi (4.1/SMI-4.1) id AA04944; Fri, 1 Oct 93 19:15:43 +0200 Message-Id: <9310011715.AA04944@tellus.csc.fi> To: Terry Gray Cc: Joe Brennan , David L Miller , Mark Crispin , pine-info@cac.washington.edu Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 In-Reply-To: Your message of "Fri, 01 Oct 1993 09:52:58 MST." Date: Fri, 01 Oct 1993 19:15:42 +0200 From: Pekka Kytolaakso Your message dated: Fri, 01 Oct 1993 09:52:58 MST > > On Fri, 1 Oct 1993, Joe Brennan wrote: > > > It's a Pine bug as far as I'm concerned. The rest of it is good enough > > to make it worthwhile to fix. We did skip 3.07 to avoid doing it > > though. > > We disagree. It seems clear that the bug is in the NextStep telnetd. > > -teg Next telnetd isn't the only problem. Did you see my mail about SGI xwsh? Pekka Kyt|laakso --------------------------------------------------------------- netmgr@tellus.csc.fi Centre for Scientific Computing Pekka.Kytolaakso@csc.fi PL 40 SF-02101 Espoo FINLAND Phone: +358 0 4571 Telefax: + 358 0 4572302 From owner-pine-info@cac.washington.edu Fri Oct 1 16:20:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20421; Fri, 1 Oct 93 16:20:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12536; Fri, 1 Oct 93 16:08:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12522; Fri, 1 Oct 93 16:06:23 -0700 Received: by digi.syd.deg.csiro.au id AA11328 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sat, 2 Oct 1993 09:02:00 +1000 Date: Sat, 2 Oct 1993 08:56:50 +1000 (EST) From: Jack Churchill Reply-To: Jack Churchill Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Mark Crispin Cc: Barry Cornelius , Mike Roch , pine-info@cac.washington.edu, Neal Curran x8432 , Adrian Bassett x8432 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 1 Oct 1993, Mark Crispin wrote: > I would like to add a note of caution. Granted, I'm ``Mr. IMAP'' so you > may need to take this with more than the usual grain of salt (a 20 ton > boulder of salt, some may say...). But, I think that using NFS as a means > of remote access to mail is, in general, a horrible idea. There is a > reason that I invented IMAP. > > The problems range from performance, to scaling, to being able to enforce > locks across the network. > > The extra password problem can be solved by use of the rimap mechanism, > and we *will* be supporting Kerberos, perhaps sooner rather than later. > > We've tried our best to make NFS access work, due to the demand for it, > but there are known sharp edges that will get you if you aren't careful. I agree that IMAP is better in most cases but for tightly coupled systems on a local LAN I still prefer NFS. I don't know much about rimap but sounds like it's the best of both worlds. I've been using the NFS approach with the recommended tricks like: /usr/var/spool/mail@server:/usr/var/spool/mail:rw:0:0:nfs:bg,hard,intr:noac: for many months now and haven't had any problems as long as we don't try to access the inbox from more than one machine at the same time. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Fri Oct 1 21:05:59 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25643; Fri, 1 Oct 93 21:05:59 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13760; Fri, 1 Oct 93 20:54:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13754; Fri, 1 Oct 93 20:54:27 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA27088; Fri, 1 Oct 1993 22:58:06 -0500 Date: Fri, 1 Oct 1993 22:56:28 -0500 (CDT) From: "Robert A. Hayden" Subject: Mailing to News To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I apologize for mailing to the list. Earlier this week someone posted the address of a site where you can email to news. Could some kind soul drop me a message with that information again? An itchy delete finger hosed it by accident. Thanks {[> Robert A. Hayden ____ <[} Question Authority {[> \ /__ <]} -=-=- {[> aq650@slc4.INS.CWRU.Edu \/ / <]} Finger for PGP 2.3a Public Key {[> hayden@krypton.mankato.msus.edu \/ <]} # include -=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Sat Oct 2 01:50:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29274; Sat, 2 Oct 93 01:50:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11512; Sat, 2 Oct 93 01:40:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from daisy.ee.und.ac.za by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11506; Sat, 2 Oct 93 01:40:12 -0700 Received: by daisy.ee.und.ac.za (/\==/\ Smail3.1.22.1 #22+apb920812.178) id m0oj2UN-0000MyC; Sat, 2 Oct 1993 10:38:51 +0200 (SAST) Date: Sat, 2 Oct 1993 10:19:39 -0200 () From: Alan Barrett Subject: MIME character sets To: Ned Freed Cc: pine-info@cac.washington.edu, klensin@infoods.mit.edu In-Reply-To: <01H3KALQ0HKW8WWAKL@INNOSOFT.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii I should know better than to disagree with Ned Freed and John Klensin about this, but... My reading of RFC-1340 (Assigned Numbers) does not support the view that all the character sets from RFC-1345 are registered for use with MIME. Unfortunately, the sections in RFC-1340 are not numbered, but nevertheless there appear to be clear boundaries between major and minor sections: The major sections have headings in ALL CAPS, and are listed in the table of contents, while the minor sections have headings in Mixed Case and are not listed in the table of contents. One of the major sections is headed MIME TYPES, and begins on page 77. The introduction to this section refers to the authority granted to IANA by RFC-1341 (MIME). One of the sub-sections lists the registered MIME character sets, and there are only ten of them: US-ASCII and ISO-8859-x. An entirely separate major section is headed CHARACTER SETS, and begins on page 79. There is no comment about the status of these character sets, nor the reason why they are listed in RFC-1340. There are some cross-references from the "MIME TYPES"/"Character Sets" subsection to the "CHARACTER SETS" section, but I interpret these as beiong purely informational. Perhaps a clarification should be sought from the IANA regarding its intent. --apb Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa RFC822: barrett@ee.und.ac.za From owner-pine-info@cac.washington.edu Sat Oct 2 05:49:28 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02810; Sat, 2 Oct 93 05:49:28 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15507; Sat, 2 Oct 93 05:37:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [156.12.23.1] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15501; Sat, 2 Oct 93 05:37:13 -0700 Received: by acad.csv.kutztown.edu.csv.kutztown.edu (5.61/1.35) id AA09351; Sat, 2 Oct 93 08:37:18 -0400 Date: Sat, 2 Oct 1993 08:36:24 -0400 (EDT) From: "James D. Gillmore" Subject: Re: Mailing to News To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII try pine [newsgroup]@cs.utexas.edu ______________________________________________________________________________ Jim Gillmore E-mail gillmore@acad.csv.kutztown.edu Manager Network Services VOICE 215.683.4199 Kutztown University of PA FAX 215.683.4634 LMS Annex Room 105 HOME 717.865.5820 Holidays & Weekends 717.567.3931 I started out with nothing Through hard work and perseverance Have managed to hold on to most of it. ______________________________________________________________________________ From owner-pine-info@cac.washington.edu Sat Oct 2 10:20:30 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05407; Sat, 2 Oct 93 10:20:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14173; Sat, 2 Oct 93 10:05:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from THOR.INNOSOFT.COM by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14153; Sat, 2 Oct 93 10:04:59 -0700 Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-14 #1234) id <01H3MSF066288WWAKL@INNOSOFT.COM>; Sat, 2 Oct 1993 10:04:18 PST Date: Sat, 02 Oct 1993 09:52:00 -0800 (PST) From: Ned Freed Subject: Re: MIME character sets In-Reply-To: Your message dated "Sat, 02 Oct 1993 10:19:39 -0200" To: Alan Barrett Cc: Ned Freed , pine-info@cac.washington.edu, klensin@infoods.mit.edu Message-Id: <01H3MSZ4FSPW8WWAKL@INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Content-Transfer-Encoding: 7BIT > My reading of RFC-1340 (Assigned Numbers) does not support the view that > all the character sets from RFC-1345 are registered for use with MIME. > Unfortunately, the sections in RFC-1340 are not numbered, but nevertheless > there appear to be clear boundaries between major and minor sections: The > major sections have headings in ALL CAPS, and are listed in the table of > contents, while the minor sections have headings in Mixed Case and are not > listed in the table of contents. > One of the major sections is headed MIME TYPES, and begins on page 77. The > introduction to this section refers to the authority granted to IANA by > RFC-1341 (MIME). One of the sub-sections lists the registered MIME > character sets, and there are only ten of them: US-ASCII and ISO-8859-x. > An entirely separate major section is headed CHARACTER SETS, and begins on > page 79. There is no comment about the status of these character sets, > nor the reason why they are listed in RFC-1340. And this is the problem. What's the purpose of listing character sets in the assigned numbers RFC? There is only one such purpose -- registration for use with MIME. In order to justify your position you have to explain what purpose this list has if it isn't for MIME use. Thus far nobody has come up with an acceptable explanation for this registry list if it isn't for MIME use. And please don't try to argue that the character sets are not registered. The entire purpose of this RFC is to register things. > There are some cross-references from the "MIME TYPES"/"Character Sets" > subsection to the "CHARACTER SETS" section, but I interpret these as > beiong purely informational. Perhaps a clarification should be sought > from the IANA regarding its intent. I believe this has already been done, and the answer was that the character sets have been registered for MIME use. Much as I might like to believe in your interpretation (and Mark Crispin has sent me comparable material in private mail), I just cannot buy it. I can only reiterate the points John has already made. The IETF-822 Working Group set up a registration process that is open to everyone. This is irrefutable -- see the language in RFC1341 or RFC1521. Keld applied for registration of all the character sets in RFC1345. This is also known to be true. Lacking any mandate to perform any kind of checking or filterng and only requiring minimal documentation as a prerequisite, IANA registered these character sets. And the act of registering by definition carries with it the right to use them in MIME. And even if I were to buy into your interpretation, you cannot possibly make a case that proves my interpretation is invalid. This would be true even if RFC1340 did not exist. Keld published his RFC and requested that these character sets be registered for MIME use. I am aware of absolutely nothing that would allow IANA to refuse such a request. As such, characterizing use of RFC1345 character sets remains unacceptable. Ned From owner-pine-info@cac.washington.edu Sat Oct 2 12:58:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07041; Sat, 2 Oct 93 12:58:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16785; Sat, 2 Oct 93 12:47:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from chinook.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16779; Sat, 2 Oct 93 12:47:39 -0700 Received: by halcyon.com id AA01370 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sat, 2 Oct 1993 12:47:35 -0700 Date: Sat, 2 Oct 1993 12:47:07 -0700 (PDT) From: "Jon 'wait...what?' Gross" Subject: unsubscribe To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII unsubscribe From owner-pine-info@cac.washington.edu Sun Oct 3 16:30:19 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24310; Sun, 3 Oct 93 16:30:19 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21842; Sun, 3 Oct 93 16:17:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay1.UU.NET by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21836; Sun, 3 Oct 93 16:17:41 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA18519; Sun, 3 Oct 93 19:17:39 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA23154; Sun, 3 Oct 93 17:18:07 MDT X-Disclaimer: Nyx is a public access Unix system run by the University of Denver. The University has neither control over nor responsibility for the opinions or correct identity of users. Date: Sun, 3 Oct 1993 17:16:05 -0600 (MDT) From: Jeffrey Wolff Subject: Distribution List To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I hate to send this out via the reflector, but I have sent mail to pine-request twice to be removed from the mailing list and have gotten no response. This list is generating far too much traffic for me and would probably be a lot better if moved to a newsgroup or at very least have all messages cced to a newsgroup. Whoever needs to see this, PLEASE remove me from this mailing list. -- Jeffrey M. Wolff jwolff@nyx.cs.du.edu George Mason University From owner-pine-info@cac.washington.edu Sun Oct 3 17:10:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24863; Sun, 3 Oct 93 17:10:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22913; Sun, 3 Oct 93 16:59:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22907; Sun, 3 Oct 93 16:59:49 -0700 Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13567; Sun, 3 Oct 93 16:59:17 -0700 Date: Sun, 3 Oct 1993 16:47:06 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Jack Churchill Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sat, 2 Oct 1993, Jack Churchill wrote: > I agree that IMAP is better in most cases but for tightly coupled systems > on a local LAN I still prefer NFS. Jack, Could you elaborate on why you prefer NFS in the local cluster case? We've had very good success with IMAP even in our NFS-linked clusters, where the advantages Mark cited (performance, scaling, more robust locking) seem equally useful. -teg From owner-pine-info@cac.washington.edu Sun Oct 3 18:10:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25603; Sun, 3 Oct 93 18:10:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22124; Sun, 3 Oct 93 18:00:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22118; Sun, 3 Oct 93 18:00:42 -0700 Received: by digi.syd.deg.csiro.au id AA13579 (5.65c/IDA-1.4.4); Mon, 4 Oct 1993 11:03:20 +1000 Date: Mon, 4 Oct 1993 10:55:54 +1000 (EST) From: Jack Churchill Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Terry Gray Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 3 Oct 1993, Terry Gray wrote: > On Sat, 2 Oct 1993, Jack Churchill wrote: > > > I agree that IMAP is better in most cases but for tightly coupled systems > > on a local LAN I still prefer NFS. > > Jack, > Could you elaborate on why you prefer NFS in the local cluster case? > > We've had very good success with IMAP even in our NFS-linked clusters, > where the advantages Mark cited (performance, scaling, more robust > locking) seem equally useful. When I first installed pine I didn't like the imap method since the users had to type their passwords each time the wanted to use pine. They might as well telnet to the server. Telnet's more secure too since there's no .rhost file to worry about as is the case with rimap (I think). I didn't realize there was the rimap method at the time but now I will try it when I have time. For now the NFS-served imbox and folders works well so I and the users have no complaints. Rimap will scale better but for now we only have a few unix workstations to worry about. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Sun Oct 3 21:34:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28229; Sun, 3 Oct 93 21:34:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24309; Sun, 3 Oct 93 21:17:28 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from SIGURD.INNOSOFT.COM by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24303; Sun, 3 Oct 93 21:17:26 -0700 Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V4.3-0 #1234) id <01H3OUHET0C09AMSLX@SIGURD.INNOSOFT.COM>; Sun, 3 Oct 1993 21:17:00 PDT Date: Sun, 03 Oct 1993 21:10:41 -0700 (PDT) From: Ned Freed Subject: RE: MIME character sets, and an apology In-Reply-To: Your message dated "Fri, 01 Oct 1993 09:37:06 -0400 (EDT)" <749482626.168726.KLENSIN@INFOODS.UNU.EDU> To: John C Klensin Cc: NED@SIGURD.INNOSOFT.COM, pine-info@CAC.WASHINGTON.EDU, agulbra@PVV.UNIT.NO Message-Id: <01H3OURI8ALO9AMSLX@SIGURD.INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > Thanks Ned, for that posting. One thing I probably should add to what > I said yesterday. > The current theory about what to do about the proliferation of MIME- > defined character sets is to start issuing Applicability Statements at > some point that identify things as, e.g., "good", "not-so-good", and > "probably you shouldn't use this trash". Now IETF has been a lot better > at talking about A/Ss than about doing them. And the feeling has been > to let experience accumulate for some months before trying to get serious > about this one. I've been calling these things profiles. (A legacy of ANSI committee-speak? I don't know where I came up with the term.) I stand corrected and will start using the term "applicability statement" instead. > However, if someone has a theory on which such a document could be built, > I'd be happy to see a draft proposal. Hmm. Well, this would probably end up as a matter for ietf-charsets, and I'm still smarting from my last scuffle in that venue. So I think I'll plead "too busy for me to do all by myself" for the time being, and see if we cannot come up with a design team to formulate at least the skeleton of such a document. Thanks for your note. Ned From owner-pine-info@cac.washington.edu Sun Oct 3 22:18:08 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28823; Sun, 3 Oct 93 22:18:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24636; Sun, 3 Oct 93 22:09:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from discus.technion.ac.il by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24630; Sun, 3 Oct 93 22:09:07 -0700 Received: from localhost (oved@localhost) by discus.technion.ac.il (8.5/8.5) id HAA21249; Mon, 4 Oct 1993 07:08:47 +0200 Date: Mon, 4 Oct 1993 07:00:07 +0200 (EET) From: Oved Ben-Aroya Subject: Re: Automatic fill of user's real name in compose To: Tom Adams Cc: Pine Distribution List , adams@smc.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 28 Sep 1993, Tom Adams wrote: > When typing in a local user name in the To: (or Cc:) field followed by > carrage-return, Pine will retype the line with only the fully qualified > domain name and NOT include the user's real name obtained from the passwd's > gcos-field. > For example: > To: adams ==> To: adams@smc.com > Since my machine does not have a fully qualified domain name in the > hosts file, the pine variable "user-domain" was set to "smc.com". > > I noticed that if the "user-domain" is set to "". Then the user's > real name is included BUT I DO NOT GET THE FULL DOMAIN NAME (only > the local machine name that I am on). > For example: > To: adams ==> To: Tom Adams > > What I really would like is both the local user's real name and > a fully qualified domain name (without the local machine name) > and not touch my /etc/hosts file. > For example: > To: adams ==> To: Tom Adams Tom, Address manipulation is the job of the MTA (e.g., sendmail), not of the MUA (pine). > > (I assume the above is what is normally expected when the machine > is fully qualified in the /etc/hosts file.) It is, usually, a good idea to have fully qualified names. > > How do I set up pine's local variables to do this? > > _______________________________________________________________ > Tom Adams Telephone: 516-435-6083 > Standard Microsystems Corporation > 35 Marcus Boulevard UUCP: uunet!smc!adams > Hauppauge, NY 11788 Internet: adams@smc.com > > > From owner-pine-info@cac.washington.edu Mon Oct 4 10:04:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12831; Mon, 4 Oct 93 10:04:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00280; Mon, 4 Oct 93 09:36:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00272; Mon, 4 Oct 93 09:36:45 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA29185; Mon, 4 Oct 93 09:36:04 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA09598; Mon, 4 Oct 93 09:36:02 PDT Received: from hal by develop.Law.USC.EDU (4.1/SMI-4.1) id AA18185; Mon, 4 Oct 93 09:36:01 PDT Date: Mon, 4 Oct 1993 09:24:47 -0700 (PDT) From: Elmar Kurgpold Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Jack Churchill Cc: Terry Gray , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have heard many warnings that NFS is not the best way to read mail. However, we once had 100 Suns NFS mounting /var/spool/mail from various places and I don't remember a single problem in 2 years. I did experience an "unexplained" catastrophe last year where I lost about 500 messages out of the middle of my mail file. (and no, it wasn't user error ;-) Of course, I was not using pine at the time, but this shows you that it could happen. Your car can get broken into as well, but the chances of that happening depend on where you park it, and nobody can say how much damage will occur. ------------------------------------- | Elmar Kurgpold | | Network Administrator | | University of Southern California | | The Law Center | | ekurgpol@Law.USC.EDU | | (213)740-2571 FAX: (213)740-5502 | ------------------------------------- On Mon, 4 Oct 1993, Jack Churchill wrote: > On Sun, 3 Oct 1993, Terry Gray wrote: > > > On Sat, 2 Oct 1993, Jack Churchill wrote: > > > > > I agree that IMAP is better in most cases but for tightly coupled systems > > > on a local LAN I still prefer NFS. > > > > Jack, > > Could you elaborate on why you prefer NFS in the local cluster case? > > > > We've had very good success with IMAP even in our NFS-linked clusters, > > where the advantages Mark cited (performance, scaling, more robust > > locking) seem equally useful. > > When I first installed pine I didn't like the imap method since the users > had to type their passwords each time the wanted to use pine. They might > as well telnet to the server. Telnet's more secure too since there's no > .rhost file to worry about as is the case with rimap (I think). I didn't > realize there was the rimap method at the time but now I will try it when > I have time. For now the NFS-served imbox and folders works well so I > and the users have no complaints. Rimap will scale better but for now we > only have a few unix workstations to worry about. > > Jack N. Churchill | Jack.Churchill@dem.csiro.au > CSIRO Division of Exploration and Mining | churchill@decus.com.au > PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 > Australia | Fax: +61 2 887 8921 > From owner-pine-info@cac.washington.edu Mon Oct 4 12:28:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19981; Mon, 4 Oct 93 12:28:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26480; Mon, 4 Oct 93 11:49:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hermes.acs.ryerson.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26474; Mon, 4 Oct 93 11:49:32 -0700 Received: by hermes.acs.ryerson.ca (AIX 3.2/UCB 5.64/4.03) id AA60543; Mon, 4 Oct 1993 14:48:31 -0400 Date: Mon, 4 Oct 1993 14:45:31 -500 (EDT) From: Paul Ribeiro Subject: Re: inbox-path in /usr/local/lib/pine-conf To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have just started seeing some problems with NFS /var/spool/mail under AIX, there are times when the servers don't seem to be able to establish a proper lock and it just sits there.....waiting and waiting...sometimes the cows come home before rpc.lockd stops complaining.. I guess it's time to install imapd /P From owner-pine-info@cac.washington.edu Mon Oct 4 12:53:52 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20753; Mon, 4 Oct 93 12:53:52 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26788; Mon, 4 Oct 93 12:37:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26782; Mon, 4 Oct 93 12:37:31 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA18002; Mon, 4 Oct 93 12:37:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA11075; Mon, 4 Oct 93 12:37:09 -0700 Date: Mon, 4 Oct 1993 12:33:34 -0700 (PDT) From: Mark Crispin Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Paul Ribeiro Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 4 Oct 1993 14:45:31 -500 (EDT), Paul Ribeiro wrote: > We have just started seeing some problems with NFS /var/spool/mail > under AIX, there are times when the servers don't seem to be able > to establish a proper lock and it just sits there.....waiting and > waiting...sometimes the cows come home before rpc.lockd stops > complaining.. Yes, rpc.lockd is famous for not working reliably. I've heard of many sad stories about people who trusted it, and now trust it no more. Unfortunately, it works most of the time, often enough that people are misled into trusting it. > I guess it's time to install imapd Good idea! ;-) From owner-pine-info@cac.washington.edu Mon Oct 4 13:07:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21516; Mon, 4 Oct 93 13:07:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26859; Mon, 4 Oct 93 12:51:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26844; Mon, 4 Oct 93 12:51:00 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA18008; Mon, 4 Oct 93 12:50:46 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA11115; Mon, 4 Oct 93 12:50:32 -0700 Date: Mon, 4 Oct 1993 12:37:44 -0700 (PDT) From: Mark Crispin Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Elmar Kurgpold Cc: Jack Churchill , Terry Gray , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Elmar - You are probably correct in your observation that you've used NFS for mail reading for 2+ years without encountering many problems (you did lose 500+ messages once...). Basically, it all hinges upon avoidance of certain behaviors that would get you into trouble. To a lesser extent, it also relies upon certain mechanisms (.lock files, rpc.lockd) working properly and not encountering one of their failure cases. If your user community is relatively sophisticated, and if the overall size of the cluster is relatively small, and if the available bandwidth is always guaranteed to be high, mail access via NFS should work out alright most of the time. IMAP was designed to handle those cases where one or more of those assumptions is not true. At UW, none of those assumptions are true. I'm not going to tell you that you should switch from NFS to IMAP; I'm just trying to keep people informed of the tradeoffs so they can make an intelligent decision. NFS does have the advantage of being able to leverage off an existing infrastructure without having to build an IMAP infrastructure; to my mind this is an unimportant advantage, but it is real nonetheless. -- Mark -- From owner-pine-info@cac.washington.edu Mon Oct 4 14:16:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23999; Mon, 4 Oct 93 14:16:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05568; Mon, 4 Oct 93 13:41:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05562; Mon, 4 Oct 93 13:41:11 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA10756; Mon, 4 Oct 93 13:41:08 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA10057; Mon, 4 Oct 93 13:41:07 PDT Received: from hal by develop.Law.USC.EDU (4.1/SMI-4.1) id AA18803; Mon, 4 Oct 93 13:41:06 PDT Date: Mon, 4 Oct 1993 13:33:26 -0700 (PDT) From: Elmar Kurgpold Reply-To: Elmar Kurgpold Subject: Re: inbox-path in /usr/local/lib/pine-conf To: Mark Crispin Cc: Jack Churchill , Terry Gray , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII OK Mr. IMAP! I've already switched! I was supporting your opinion. Elmar On Mon, 4 Oct 1993, Mark Crispin wrote: > Elmar - > > You are probably correct in your observation that you've used NFS for > mail reading for 2+ years without encountering many problems (you did lose > 500+ messages once...). Basically, it all hinges upon avoidance of certain > behaviors that would get you into trouble. To a lesser extent, it also relies > upon certain mechanisms (.lock files, rpc.lockd) working properly and not > encountering one of their failure cases. > > If your user community is relatively sophisticated, and if the overall > size of the cluster is relatively small, and if the available bandwidth is > always guaranteed to be high, mail access via NFS should work out alright most > of the time. > > IMAP was designed to handle those cases where one or more of those > assumptions is not true. At UW, none of those assumptions are true. > > I'm not going to tell you that you should switch from NFS to IMAP; I'm > just trying to keep people informed of the tradeoffs so they can make an > intelligent decision. NFS does have the advantage of being able to leverage > off an existing infrastructure without having to build an IMAP infrastructure; > to my mind this is an unimportant advantage, but it is real nonetheless. > > -- Mark -- > From owner-pine-info@cac.washington.edu Mon Oct 4 14:52:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25226; Mon, 4 Oct 93 14:52:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06433; Mon, 4 Oct 93 14:32:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tiberius.safb.af.mil by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06421; Mon, 4 Oct 93 14:32:34 -0700 Received: by tiberius.safb.af.mil (4.1/SMI-4.1) id AA12703; Mon, 4 Oct 93 16:33:13 CDT Date: Mon, 4 Oct 1993 16:23:42 -0500 (CDT) From: John Daum x6835 or 618-632-2456 Reply-To: John Daum x6835 or 618-632-2456 Subject: Pine 3.07 on SGI 4D/320 Unix System To: Pine Help List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We have users who put 80 addresses in the To: field. Two questions related to this: 1. One user complains of Pine dumping him back to the Unix prompt if that user tries to edit the addressee list.... If he sends it, all is okay. Any ideas??? 2. Another user at the end of a 1200 baud line in an overseas location is the recipient of Email with 80 plus lines on the front of the message all dedicated to the To: field. Is there any way to keep the addressees spread across the 70+ character line?? OR is there a way to set THAT user up so that the addressees either do not show or they show at the end of the message?? Thanks, John Daum daumj@tiberius.safb.af.mil From owner-pine-info@cac.washington.edu Mon Oct 4 16:24:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28517; Mon, 4 Oct 93 16:24:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07288; Mon, 4 Oct 93 15:13:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07280; Mon, 4 Oct 93 15:12:58 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00923; Mon, 4 Oct 93 15:12:50 -0700 Date: Mon, 4 Oct 1993 15:07:16 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.07 on SGI 4D/320 Unix System To: John Daum x6835 or 618-632-2456 Cc: Pine Help List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 4 Oct 1993, John Daum x6835 or 618-632-2456 wrote: > > We have users who put 80 addresses in the To: field. Two questions > related to this: > > 1. One user complains of Pine dumping him back to the Unix prompt if > that user tries to edit the addressee list.... If he sends it, all is okay. > Any ideas??? > This is a bug that will be fixed in Pine 3.86 which will be out later this week. It will be ftpable from ftp.cac.washington.edu in the /mail directory. > 2. Another user at the end of a 1200 baud line in an overseas location is > the recipient of Email with 80 plus lines on the front of the message all > dedicated to the To: field. > Is there any way to keep the addressees spread across the 70+ character line?? > OR is there a way to set THAT user up so that the addressees > either do not show or they show at the end of the message?? > If you put the addresses in the Bcc: field rather than the To: field, they will not show up on the other end. In Pine 3.07, set feature-level=old-growth in your .pinerc. In Pine 3.85, set enable-full-headers in the feature-list. > Thanks, > John Daum > daumj@tiberius.safb.af.mil > > > > > From owner-pine-info@cac.washington.edu Mon Oct 4 17:23:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00992; Mon, 4 Oct 93 17:23:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09666; Mon, 4 Oct 93 17:03:28 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09658; Mon, 4 Oct 93 17:03:26 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02856; Mon, 4 Oct 93 17:03:25 -0700 Date: Mon, 4 Oct 1993 16:56:33 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.07 on SGI 4D/320 Unix System To: John Daum x6835 or 618-632-2456 , Pine Help List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 4 Oct 1993, David L Miller wrote: > > 2. Another user at the end of a 1200 baud line in an overseas location is > > the recipient of Email with 80 plus lines on the front of the message all > > dedicated to the To: field. > > Is there any way to keep the addressees spread across the 70+ character line?? > > OR is there a way to set THAT user up so that the addressees > > either do not show or they show at the end of the message?? > > > If you put the addresses in the Bcc: field rather than the To: field, > they will not show up on the other end. In Pine 3.07, set > feature-level=old-growth in your .pinerc. In Pine 3.85, set > enable-full-headers in the feature-list. > Oops, disregard that last part. Full-headers has to do with viewing messages rather than composing messages. When you are composing a message and the cursor is in the headers, the '^R' command will turn on Rich Headers. Use the Bcc: field and none of the other recipients will recieve the full list of recipients. An even better way to send messages to alot of people is to use a mailing list manager... Sorry about the mis-information. --DLM From owner-pine-info@cac.washington.edu Mon Oct 4 21:25:51 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05181; Mon, 4 Oct 93 21:25:51 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12311; Mon, 4 Oct 93 21:12:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from chinook.halcyon.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12305; Mon, 4 Oct 93 21:12:07 -0700 Received: by halcyon.com id AA18692 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 4 Oct 1993 21:12:02 -0700 Date: Mon, 4 Oct 1993 21:11:14 -0700 (PDT) From: "Jon 'wait...what?' Gross" Subject: How do you unsubscribe? To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Exactly what the title is - how do you unsubscribe from this list? If someone just watches - please unsubscribe me. Thanks. ---------- Brought to you by jon gross and the letter S. jong@halcyon.com From owner-pine-info@cac.washington.edu Mon Oct 4 22:30:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06524; Mon, 4 Oct 93 22:30:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12555; Mon, 4 Oct 93 21:48:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12549; Mon, 4 Oct 93 21:48:56 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05190; Mon, 4 Oct 93 21:47:40 -0700 Date: Mon, 4 Oct 1993 21:33:05 -0700 (PDT) From: Terry Gray Subject: Re: How do you unsubscribe? To: "Jon 'wait...what?' Gross" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 4 Oct 1993, Jon 'wait...what?' Gross wrote: > Exactly what the title is - how do you unsubscribe from this > list? If someone just watches - please unsubscribe me. Thanks. Jon, The rule for all conventional Internet mailing lists (where "conventional" means "not LISTSERV, Majordomo, or ListProc...") is to send a message to an address formed by appending "-request" to the left-hand-part of the list address. Therefore, in this case, a message to "pine-info-request@cac.washington.edu" would be the correct protocol. In the case of pine-info, which uses the Majordomo list manager, an even better option --albeit one you wouldn't reasonably know about-- would be to send a msg to "majordomo@cac.washington.edu" with one line in the body: "unsubscribe pine-info" -teg p.s. Apologies to everyone else on the list, but the number of administrative requests sent to the whole list suggests that periodic reposting of this info might be appropriate. From owner-pine-info@cac.washington.edu Tue Oct 5 09:50:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22177; Tue, 5 Oct 93 09:50:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19453; Tue, 5 Oct 93 09:28:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19447; Tue, 5 Oct 93 09:28:51 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA22551 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Tue, 5 Oct 93 11:28:49 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA09569; Tue, 5 Oct 93 11:28:48 CDT Date: Tue, 5 Oct 1993 11:25:48 -0500 (CDT) From: Matt Simmons Subject: Read-only mode To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Starting pine, ^Zing it to go do something else, and then forgetting about the ^Z'd process until you try to start up pine again, and then having to wait for it to try to talk to the other process only to find that it can't and that both are RO and having to kill both is rather annoying.... Could pine be fixed so that if it opens up and notices that another pine is running, it asks if it can make the other one RO? This would save a lot of grief... From owner-pine-info@cac.washington.edu Tue Oct 5 13:43:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02888; Tue, 5 Oct 93 13:43:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24294; Tue, 5 Oct 93 13:17:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24288; Tue, 5 Oct 93 13:17:41 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24032; Tue, 5 Oct 93 13:17:38 -0700 Date: Tue, 5 Oct 1993 13:12:25 -0700 (PDT) From: Terry Gray Subject: mailing list vs. newsgroup To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My views: -Both mailing lists and newsgroups have their places. -Having both, with bidirectional cross-posting seems desirable. -All of you will be happier if the UW team focuses on code-cutting rather than list management... So this seems like a good direction to go, but someone else would need to volunteer to do it. -teg From owner-pine-info@cac.washington.edu Tue Oct 5 15:32:53 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07839; Tue, 5 Oct 93 15:32:53 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04234; Tue, 5 Oct 93 15:07:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ramsey.cs.laurentian.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04228; Tue, 5 Oct 93 15:07:10 -0700 Received: by ramsey.cs.laurentian.ca (5.65/DEC-Ultrix/4.3) id AA17333; Tue, 5 Oct 1993 18:06:43 -0400 Received: by thunderbird.auc.laurentian.ca (5.4.2/200.1.1.4) id AA15420; Tue, 5 Oct 1993 18:04:19 -0400 Date: Tue, 5 Oct 1993 18:04:19 -0400 From: trainor@thunderbird.auc.laurentian.ca (James Trainor) Message-Id: <9310052204.AA15420@thunderbird.auc.laurentian.ca> To: pine-info@CAC.washington.edu Subject: ports to DG/UX I have succesfully(sic) ported(i think) pine3.07 to DG/UX rev 5.4.2 More to follow. From owner-pine-info@cac.washington.edu Tue Oct 5 16:40:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10980; Tue, 5 Oct 93 16:40:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29057; Tue, 5 Oct 93 16:27:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29049; Tue, 5 Oct 93 16:27:02 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22949; Tue, 5 Oct 93 16:26:41 -0700 Date: Tue, 5 Oct 1993 16:25:11 -0700 (PDT) From: David L Miller Subject: Re: ports to DG/UX To: James Trainor Cc: pine-info@CAC.washington.edu In-Reply-To: <9310052204.AA15420@thunderbird.auc.laurentian.ca> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Great! Now, are you ready to start work on porting Pine 3.86? ;) |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 5 Oct 1993, James Trainor wrote: > I have succesfully(sic) ported(i think) pine3.07 to DG/UX rev 5.4.2 > More to follow. From owner-pine-info@cac.washington.edu Tue Oct 5 17:59:35 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13622; Tue, 5 Oct 93 17:59:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05053; Tue, 5 Oct 93 17:48:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ramsey.cs.laurentian.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05047; Tue, 5 Oct 93 17:48:52 -0700 Received: by ramsey.cs.laurentian.ca (5.65/DEC-Ultrix/4.3) id AA21211; Tue, 5 Oct 1993 20:48:44 -0400 Received: by thunderbird.auc.laurentian.ca (5.4.2/200.1.1.4) id AA18255; Tue, 5 Oct 1993 20:46:33 -0400 Date: Tue, 5 Oct 1993 20:46:33 -0400 From: trainor@thunderbird.auc.laurentian.ca (James Trainor) Message-Id: <9310060046.AA18255@thunderbird.auc.laurentian.ca> To: David L Miller Cc: pine-info@CAC.washington.edu Subject: Re: ports to DG/UX still have a few bugs to work out for function key mappings. don't know when i'll have time for 3.86. are ther substantial advantages over 3.07??? From owner-pine-info@cac.washington.edu Tue Oct 5 21:08:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16889; Tue, 5 Oct 93 21:08:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02682; Tue, 5 Oct 93 20:57:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02676; Tue, 5 Oct 93 20:57:07 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA04476 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Tue, 5 Oct 93 22:57:05 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA27854; Tue, 5 Oct 93 22:57:04 CDT Date: Tue, 5 Oct 1993 22:51:07 -0500 (CDT) From: Matt Simmons Subject: svr4 port of 3.85 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII pine 3.85 will not compile for me under svr4... It gets through everything up till pine when it's trying to compile addrbook.c... I get this: "/usr/include/stdlib.h", line 66: identifier redeclared: system "/usr/include/unistd.h", line 154: identifier redeclared: rename "./../c-client/osdep.h", line 108: warning: identifier redeclared: gethostid "addrbook.c", line 200: warning: semantics of ">" change in ANSI C; use explicit cast "addrbook.c", line 204: warning: semantics of ">" change in ANSI C; use explicit cast then it doesn't spew out addrbook.o... what's going on? From owner-pine-info@cac.washington.edu Tue Oct 5 23:08:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18638; Tue, 5 Oct 93 23:08:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06217; Tue, 5 Oct 93 22:55:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06211; Tue, 5 Oct 93 22:55:24 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA21186; Tue, 5 Oct 93 22:55:14 -0700 Date: Tue, 5 Oct 1993 22:47:47 -0700 (PDT) From: Mark Crispin Subject: re: Read-only mode To: Matt Simmons Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 5 Oct 1993 11:25:48 -0500 (CDT), Matt Simmons wrote: > Starting pine, ^Zing it to go do something else, and then > forgetting about the ^Z'd process until you try to start up pine again, > and then having to wait for it to try to talk to the other process only > to find that it can't and that both are RO and having to kill both is > rather annoying.... Could pine be fixed so that if it opens up and > notices that another pine is running, it asks if it can make the other > one RO? This would save a lot of grief... We agree that this is annoying, but none of the various alternatives which we have considered have been any better. We'll look into this further, but for the time being the best thing is to avoid suspending Pine and forgetting about it! -- Mark -- From owner-pine-info@cac.washington.edu Wed Oct 6 01:46:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21764; Wed, 6 Oct 93 01:46:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04736; Wed, 6 Oct 93 01:39:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04730; Wed, 6 Oct 93 01:39:08 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <04452-0@dummy1.dur.ac.uk>; Wed, 6 Oct 1993 09:38:47 +0100 Received: from draco.dur.ac.uk by vega.dur.ac.uk; Wed, 6 Oct 93 09:38:42 BST Date: Wed, 6 Oct 1993 09:29:25 +0100 (BST) From: Roger Gawley Subject: Re: mailing list vs. newsgroup To: Terry Gray Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The danger I see in all this back-and-forth posting is be that discussion would get even more desynchronised than it is now. I still think you should take a look at mailbase. On Tue, 5 Oct 1993, Terry Gray wrote: > > My views: > > -Both mailing lists and newsgroups have their places. > -Having both, with bidirectional cross-posting seems desirable. > -All of you will be happier if the UW team focuses on code-cutting > rather than list management... > > So this seems like a good direction to go, but someone else would need to > volunteer to do it. > > -teg > > > From owner-pine-info@cac.washington.edu Wed Oct 6 05:10:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26082; Wed, 6 Oct 93 05:10:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07608; Wed, 6 Oct 93 05:02:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uafhp.uark.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07602; Wed, 6 Oct 93 05:02:44 -0700 Received: from comp.uark.edu by uafhp.uark.edu with SMTP (1.37.109.4/15.6) id AA11877; Wed, 6 Oct 93 07:01:21 -0500 Received: by (5.0/SMI-SVR4) id AA23592; Wed, 6 Oct 93 07:01:39 CDT Date: Wed, 6 Oct 1993 06:55:02 -0500 (CDT) From: Ken Schriner Subject: Re: mailing list vs. newsgroup To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 868 > > My views: > > > > -Both mailing lists and newsgroups have their places. As the manager of several lists and reader of several newsgroups, I agree. > > -Having both, with bidirectional cross-posting seems desirable. Toolb-l (which manage) is posted also to a newsgroup (as a digest). Cross posting is not doable. BEER-L is another list which is posted to a newsgroup with no cross posting. I don't know of any list/newsgroup that has cross posting. Let me know if you do. > > -All of you will be happier if the UW team focuses on code-cutting > > rather than list management... I think they are doing a fine job of both :-) > > So this seems like a good direction to go, but someone else would need to > > volunteer to do it. Ken Schriner ks06054@uafsysb University of Arkansas kschrine@comp.uark.edu From owner-pine-info@cac.washington.edu Wed Oct 6 05:58:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26747; Wed, 6 Oct 93 05:58:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07769; Wed, 6 Oct 93 05:50:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from log.css.itd.umich.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07763; Wed, 6 Oct 93 05:50:11 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA09464; Wed, 6 Oct 93 08:50:01 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA26275; Wed, 6 Oct 93 08:50:01 -0400 Date: Wed, 6 Oct 1993 08:47:58 -0400 (EDT) From: Alex Tang Subject: re: Read-only mode To: Mark Crispin Cc: Matt Simmons , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 5 Oct 1993, Mark Crispin wrote: > We agree that this is annoying, but none of the various alternatives which we > have considered have been any better. We'll look into this further, but for > the time being the best thing is to avoid suspending Pine and forgetting about > it! I also wrote about this...I was wondering if it's possible to get the second pine session to see if the first is sleeping. If so, then make the second pine session read only automatically and not try to grab the lock. just wondering.... ...alex... Alex Tang --- ALTITUDE@UMICH.EDU...USERW00Y@UMICHUM.BITNET -----------+ U of M, SNRE: Student and Computer Consultant II, PGP on req.| ITD/CSS Consultant, Short asian with long hair :) or finger | From owner-pine-info@cac.washington.edu Wed Oct 6 07:12:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28370; Wed, 6 Oct 93 07:12:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06995; Wed, 6 Oct 93 06:59:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06989; Wed, 6 Oct 93 06:59:43 -0700 Message-Id: <9310061359.AA06989@mx1.cac.washington.edu> Received: from UWAVM.U.WASHINGTON.EDU by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with BSMTP id 0544; Wed, 06 Oct 93 06:59:10 PDT Received: from ETSU.EAST-TENN-ST.EDU by UWAVM.U.WASHINGTON.EDU (Mailer R2.10 ptf008) with BSMTP id 1003; Wed, 06 Oct 93 06:59:09 PDT Received: from ETSU (NJE origin CMS2@ETSU) by ETSU.EAST-TENN-ST.EDU (LMail V1.1d/1.7f) with BSMTP id 9283; Wed, 6 Oct 1993 09:58:29 -0400 Date: Wed, 06 Oct 93 09:52:16 EDT From: Bill Williams Organization: East Tennessee State University Subject: PIne3.85 on RS/6000 AIX 3.2.3 To: pine-info@cac.washington.edu I built the Pine 3.85 on a RS/6K AIX 3.2.3 machine using 'build_a32' and the thing built without complaint! Congrats to all you a32 port-ers. Now the bad news: When I TelNet in (using FTP's TCP/IP Software on my PC) with vt220 emulation, Pine/Pico complains that "vt220 is not a known terminal"! Other utilities, vi and less, have no problems recognizing the vt220 so what's the problem here? Many activities get me kicked out with a "signal abort" and a coredump. Immediately reproducable is: pine 'L' -- List folders ...death by signal abort. Any clues? I have been running only in 'test' mode -- from where I built Pine3.85 -- and have *not* moved the files to the appropriate /usr/local/... areas. --------------------------------------- Bill Williams -- ETSU Systems Support East Tennessee (615) 929-6853 State University From owner-pine-info@cac.washington.edu Wed Oct 6 07:36:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28980; Wed, 6 Oct 93 07:36:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08156; Wed, 6 Oct 93 07:27:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mcmail.CIS.McMaster.CA by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08150; Wed, 6 Oct 93 07:26:54 -0700 Received: by mcmail.cis.mcmaster.ca id AA00527 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 6 Oct 1993 10:27:51 -0400 Date: Wed, 6 Oct 1993 10:17:44 -0400 (EDT) From: Muriel McKay Subject: re: Read-only mode To: Mark Crispin Cc: Matt Simmons , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John Benjamins at McMaster renamed pine to pine.exe and then wrote this script which he called pine . This checks for an existing pine process and if it finds one asks very nicely if it should be killed (mcmail is the name of our mail machine.) This works on SGI - Irix 4.0.5 . I'm sure I have one for sun 4.1.2 . I'll look and post later if anyone wants. Muriel McKay, Analyst, Desktop Computing Support. CIS. ABB132 ext. 23630 McMaster University . Hamilton Ontario, Canada. -------------------------------------------------------------------------- #!/usr/bin/perl -P- # -*-Perl-*- # Set up variables $Answer = not; $Continue = not; $Kill = no; $User = $ENV{'USER'} || $ENV{'LOGNAME'} || (getpwuid($<))[0]; $LockFile = "/tmp/\.\\usr\\mail\\".$User; $RealPine = "/usr/local/pine/bin/pine.exe"; open(TTYIN, "/dev/tty") || die "can't write /dev/tty: $!"; select(TTYOUT); $| = 1; select(STDOUT); # Handle signals $SIG{'INT'} = 'IGNORE'; $SIG{'TERM'} = 'IGNORE'; $SIG{'TSTP'} = 'IGNORE'; $SIG{'HUP'} = 'cleanup'; sub ignore { print "\nUnknown command\n\n"; } sub cleanup { system "stty", 'icanon'; system "stty", 'isig'; system "stty", 'echo'; system "stty", 'eol', '^@'; } # system "stty", '-icanon'; system "stty", '-isig'; system "stty", '-echo'; system "stty", 'eol', '^A'; # Look for the pine lock file in /tmp if ( -f "$LockFile" ) { while ( $Answer eq 'not' ) { print TTYOUT "\ You have another copy of pine running. This may be the result of rebooting \ your PC while you were logged in to mcmail. In any case, do you want to kill \ the other session and start a new one? [y/n]: "; read(TTYIN, $Answer, 1); if ($Answer =~ /^y/i) { print TTYOUT "\n"; $Kill="yes"; } elsif ($Answer =~ /^n/i) { while ($Continue eq 'not') { print "\n\ ******** WARNING ******** WARNING ******** WARNING ******** WARNING ********\ \ Pine will now start in READ ONLY mode. This means you will not be able to change your inbox folder. Are you sure you want to do this? [y/n]: "; read(TTYIN, $Continue, 1); print TTYOUT "\n"; if ($Continue =~ /^y/i) { &cleanup; exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; } elsif ($Continue =~ /^n/i) { &cleanup ; exit; } elsif ($Continue =~ /^q/i) { &cleanup ; exit; } else { print TTYOUT "\nPlease answer with y or n only please\n"; $Continue="not"; } } } elsif ($Answer =~ /^q/i) { &cleanup ; print "\n" ; exit; } else { print TTYOUT "\n\nPlease answer with y or n only please\n\n"; $Answer="not"; } } } # Kill the old one? if ( $Kill eq "yes" ) { system '/etc/fuser', '-k', $LockFile; } &cleanup; # If we get here, we want to start the real Pine executable exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; From owner-pine-info@cac.washington.edu Wed Oct 6 07:45:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29212; Wed, 6 Oct 93 07:45:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07405; Wed, 6 Oct 93 07:36:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07399; Wed, 6 Oct 93 07:36:28 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01297; Wed, 6 Oct 93 07:36:24 -0700 Date: Wed, 6 Oct 1993 07:35:06 -0700 (PDT) From: Terry Gray Subject: Re: mailing list vs. newsgroup To: Ken Schriner Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 6 Oct 1993, Ken Schriner wrote: > > > -Having both, with bidirectional cross-posting seems desirable. > > Toolb-l (which manage) is posted also to a newsgroup (as a digest). Cross > posting is not doable. BEER-L is another list which is posted to a > newsgroup with no cross posting. I don't know of any list/newsgroup that > has cross posting. Let me know if you do. I *thought* that comp.mail.mime was cross-posted, but I could easily be mistaken on that. -teg From owner-pine-info@cac.washington.edu Wed Oct 6 08:01:57 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29605; Wed, 6 Oct 93 08:01:57 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07592; Wed, 6 Oct 93 07:49:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stein.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07586; Wed, 6 Oct 93 07:49:48 -0700 Received: by stein1.u.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04151; Wed, 6 Oct 93 07:49:48 -0700 X-Sender: mramey@stein1.u.washington.edu Date: Wed, 6 Oct 1993 07:47:48 -0700 (PDT) From: Mike Ramey Subject: Re: mailing list vs. newsgroup To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I believe that VIRUS-L and comp.virus are bidirectionally linked. -mr On Wed, 6 Oct 1993, Ken Schriner wrote: > Toolb-l (which manage) is posted also to a newsgroup (as a digest). Cross > posting is not doable. BEER-L is another list which is posted to a > newsgroup with no cross posting. I don't know of any list/newsgroup that > has cross posting. Let me know if you do. From owner-pine-info@cac.washington.edu Wed Oct 6 08:03:02 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29678; Wed, 6 Oct 93 08:03:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08299; Wed, 6 Oct 93 07:51:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mcmail.CIS.McMaster.CA by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08277; Wed, 6 Oct 93 07:50:56 -0700 Received: by mcmail.cis.mcmaster.ca id AA04474 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 6 Oct 1993 10:51:59 -0400 Date: Wed, 6 Oct 1993 10:49:25 -0400 (EDT) From: Muriel McKay Subject: sun 4.1.2 kill dup pine process script To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Following is script for SUN os 4.1.2 (this one was a collaboration between John Benjamins and Dave Chajdiak )which will check for existing pine process and kill it on request . Hope this helps . Muriel McKay , Analyst , Dsktop Computing Support Computing and Information Services, ABB 132 . Ext. 23630 . McMaster University , Hamilton , Ontario, Canada -------------------------------------------------------------------------- #!/usr/local/bin/perl -P- # -*-Perl-*- # Set up variables $Answer = not; $Continue = not; $Kill = no; $User = $ENV{'USER'} || $ENV{'LOGNAME'} || (getpwuid($<))[0]; $LockFile = "/tmp/\.\\usr\\spool\\mail\\".$User; $RealPine = "/usr/local/pine/bin/pine.exe"; open(TTYIN, "/dev/tty") || die "can't write /dev/tty: $!"; select(TTYOUT); $| = 1; select(STDOUT); # Handle signals $SIG{'INT'} = 'IGNORE'; $SIG{'TERM'} = 'IGNORE'; $SIG{'TSTP'} = 'IGNORE'; $SIG{'HUP'} = 'cleanup'; sub ignore { print "\nUnknown command\n\n"; } sub cleanup { system "stty -cbreak echo /dev/tty 2>&1"; } # system "stty cbreak -echo /dev/tty 2>&1"; # Look for the pine lock file in /tmp if ( -f "$LockFile" ) { while ( $Answer eq 'not' ) { print TTYOUT "\ You have another copy of pine running. This may be the result of rebooting \ your PC while you were logged in to offsv1. In any case, do you want to kill \ the other session and start a new one? [y/n]: "; read(TTYIN, $Answer, 1); if ($Answer =~ /^y/i) { print TTYOUT "\n"; $Kill="yes"; } elsif ($Answer =~ /^n/i) { while ($Continue eq 'not') { print "\n\ ******** WARNING ******** WARNING ******** WARNING ******** WARNING ********\ \ Pine will now start in READ ONLY mode. This means you will not be able to change your inbox folder. Are you sure you want to do this? [y/n]: "; read(TTYIN, $Continue, 1); print TTYOUT "\n"; if ($Continue =~ /^y/i) { &cleanup; exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; } elsif ($Continue =~ /^n/i) { &cleanup ; exit; } elsif ($Continue =~ /^q/i) { &cleanup ; exit; } else { print TTYOUT "\nPlease answer with y or n only please\n"; $Continue="not"; } } } elsif ($Answer =~ /^q/i) { &cleanup ; print "\n" ; exit; } else { print TTYOUT "\n\nPlease answer with y or n only please\n\n"; $Answer="not"; } } } # Kill the old one? if ( $Kill eq "yes" ) { system "/usr/kvm/fuser -k $RealPine >/dev/null 2>&1"; } &cleanup; # If we get here, we want to start the real Pine executable exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; From owner-pine-info@cac.washington.edu Wed Oct 6 08:33:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01205; Wed, 6 Oct 93 08:33:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08108; Wed, 6 Oct 93 08:16:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from rye.city.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08100; Wed, 6 Oct 93 08:16:46 -0700 Received: from euston.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <17270-0@Rye.city.ac.uk>; Wed, 6 Oct 1993 17:13:49 +0100 Date: Wed, 6 Oct 1993 16:14:06 +0100 (BST) From: "D.K.Brownlee" Subject: re: Suspended pine problems To: Pine-Info Maillist Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Would it be possible to interceprt SIGTSTP & then just SIGCONT the parent process & continue running (or similar), and then pick up the SIGCONT from the patent later & reattach to the tty? David D.K.Brownlee@city.ac.uk. Network Analyst. Postmaster. Hostmaster. <_.-^-._> Telephone: (+44) 71 477 8000 Ext:3757. <_.-^-._> Snailmail: E308, City University, Northampton Sq, Islington, London ECIV 0HB. ---------- Forwarded message ---------- Date: Tue, 5 Oct 1993 22:47:47 -0700 (PDT) From: Mark Crispin To: Matt Simmons Cc: pine-info@cac.washington.edu Subject: re: Read-only mode On Tue, 5 Oct 1993 11:25:48 -0500 (CDT), Matt Simmons wrote: > Starting pine, ^Zing it to go do something else, and then > forgetting about the ^Z'd process until you try to start up pine again, > and then having to wait for it to try to talk to the other process only > to find that it can't and that both are RO and having to kill both is > rather annoying.... Could pine be fixed so that if it opens up and > notices that another pine is running, it asks if it can make the other > one RO? This would save a lot of grief... We agree that this is annoying, but none of the various alternatives which we have considered have been any better. We'll look into this further, but for the time being the best thing is to avoid suspending Pine and forgetting about it! -- Mark -- From owner-pine-info@cac.washington.edu Wed Oct 6 08:41:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01553; Wed, 6 Oct 93 08:41:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08174; Wed, 6 Oct 93 08:19:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from blas.cis.McMaster.CA by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08164; Wed, 6 Oct 93 08:19:16 -0700 Received: by blas.cis.mcmaster.ca id AA24283 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 6 Oct 1993 11:18:34 -0400 Message-Id: <199310061518.AA24283@blas.cis.mcmaster.ca> From: johnb@blas.cis.mcmaster.ca (John Benjamins) Date: Wed, 6 Oct 1993 11:18:34 -0400 In-Reply-To: Mark Crispin "re: Read-only mode" (Oct 5, 10:47pm) X-Department: Computing and Information Services, McMaster University X-Disclaimer: These are MY opinions, not CIS' or McMaster University's X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Mark Crispin , Matt Simmons Subject: re: Read-only mode Cc: pine-info@cac.washington.edu Mark Crispin, On Oct 5, 10:47pm, you wrote: } Subject: re: Read-only mode } On Tue, 5 Oct 1993 11:25:48 -0500 (CDT), Matt Simmons wrote: } > Starting pine, ^Zing it to go do something else, and then } > forgetting about the ^Z'd process until you try to start up pine again, } > and then having to wait for it to try to talk to the other process only } > to find that it can't and that both are RO and having to kill both is } > rather annoying.... Could pine be fixed so that if it opens up and } > notices that another pine is running, it asks if it can make the other } > one RO? This would save a lot of grief... } } We agree that this is annoying, but none of the various alternatives which we } have considered have been any better. We'll look into this further, but for } the time being the best thing is to avoid suspending Pine and forgetting about } it! } }-- End of excerpt of Oct 5, 10:47pm what we do here is run a perl script called pine. it checks for a file like /tmp/.\usr\spool\mail\loginname. if this exists it uses fuser (system V only, sorry) to kill the process that has the file open. it then exec's the REAL pine binary called pine.x. well actually it has a couple of prompts in it, to make it more friendly. if it finds the lock file, it says that you already have a pine session running. it then gives you the option of killing the original session and starting a new one, or starting pine in read-only mode. this has worked very well for us. we had to do this because many people here use a terminal emulator on their pc's to login to the mailhost and read their mail with pine. unfortunately sometimes the pc's will hang, get rebooted, etc. these leave pine sessions running on the mailhost, so the next time they login they are in read-only mode. this script gets around having to explain how to run ps/grep/kill to get around the problem. sounds like it would help for this case as well. i'll include the script here (from an sgi, needs tweaking to work on sunos, etc.). hope this helps. #!/usr/bin/perl -P- # -*-Perl-*- # Set up variables $Answer = not; $Continue = not; $Kill = no; $User = $ENV{'USER'} || $ENV{'LOGNAME'} || (getpwuid($<))[0]; $LockFile = "/tmp/\.\\usr\\mail\\".$User; $RealPine = "/usr/local/pine/bin/pine.exe"; open(TTYIN, "/dev/tty") || die "can't write /dev/tty: $!"; select(TTYOUT); $| = 1; select(STDOUT); # Handle signals $SIG{'INT'} = 'IGNORE'; $SIG{'TERM'} = 'IGNORE'; $SIG{'TSTP'} = 'IGNORE';$SIG{'HUP'} = 'cleanup'; sub ignore { print "\nUnknown command\n\n"; } sub cleanup { system "stty", 'icanon'; system "stty", 'isig'; system "stty", 'echo'; system "stty", 'eol', '^@'; } # system "stty", '-icanon'; system "stty", '-isig'; system "stty", '-echo'; system "stty", 'eol', '^A'; # Look for the pine lock file in /tmp if ( -f "$LockFile" ) { while ( $Answer eq 'not' ) { print TTYOUT "\ You have another copy of pine running. This may be the result of rebooting \ your PC while you were logged in to mcmail. In any case, do you want to kill \ the other session and start a new one? [y/n]: "; read(TTYIN, $Answer, 1); if ($Answer =~ /^y/i) { print TTYOUT "\n"; $Kill="yes"; } elsif ($Answer =~ /^n/i) { while ($Continue eq 'not') { print "\n\ ******** WARNING ******** WARNING ******** WARNING ******** WARNING ********\ \ Pine will now start in READ ONLY mode. This means you will not be able to change your inbox folder. Are you sure you want to do this? [y/n]: "; read(TTYIN, $Continue, 1); print TTYOUT "\n"; if ($Continue =~ /^y/i) { &cleanup; exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; } elsif ($Continue =~ /^n/i) { &cleanup ; exit; } elsif ($Continue =~ /^q/i) { &cleanup ; exit; } else { print TTYOUT "\nPlease answer with y or n only please\n"; $Continue="not"; } } } elsif ($Answer =~ /^q/i) { &cleanup ; print "\n" ; exit; } else { print TTYOUT "\n\nPlease answer with y or n only please\n\n"; $Answer="not"; } } } # Kill the old one? if ( $Kill eq "yes" ) { system '/etc/fuser', '-k', $LockFile; } &cleanup; # If we get here, we want to start the real Pine executable exec $RealPine, @ARGV; die "Can't run $RealPine: $!"; -- // E. John Benjamins -- // Calvin: "Verbing weirds language." \\ Hobbes: "Maybe we can eventually make language a complete impediment \\ to understanding." From owner-pine-info@cac.washington.edu Wed Oct 6 09:00:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02157; Wed, 6 Oct 93 09:00:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08788; Wed, 6 Oct 93 08:40:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08782; Wed, 6 Oct 93 08:40:56 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA15071 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Wed, 6 Oct 93 10:40:51 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA10407; Wed, 6 Oct 93 10:40:50 CDT Date: Wed, 6 Oct 1993 10:40:10 -0500 (CDT) From: Matt Simmons Subject: Re: sun 4.1.2 kill dup pine process script To: Muriel McKay Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 6 Oct 1993, Muriel McKay wrote: > Following is script for SUN os 4.1.2 (this one was a collaboration between > John Benjamins and Dave Chajdiak )which will check for existing pine > process and kill it on request . Hope this helps . > > Muriel McKay , > Analyst , Dsktop Computing Support > Computing and Information Services, > ABB 132 . Ext. 23630 . McMaster University , Hamilton , Ontario, Canada > -------------------------------------------------------------------------- > This is a wonderful, great script, there's only one slight problem... It doesn't kill the old pine process.... From owner-pine-info@cac.washington.edu Wed Oct 6 09:32:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03399; Wed, 6 Oct 93 09:32:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08915; Wed, 6 Oct 93 09:17:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from herman.cs.uoguelph.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08909; Wed, 6 Oct 93 09:16:47 -0700 Received: from shoe.cs.uoguelph.ca by herman.cs.uoguelph.ca with SMTP (1.37.109.4/16.2) id AA28178; Wed, 6 Oct 93 12:13:37 -0400 Received: by shoe.cs.uoguelph.ca (1.37.109.4/16.2) id AA25886; Wed, 6 Oct 93 12:16:55 -0400 Date: Wed, 6 Oct 1993 12:07:17 -0400 (EDT) From: Jim Lennie Subject: Enhancements for next release To: Pine-Info Maillist Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have a couple of suggestions for the next release. 1) Can the "^R Rich Hdr" function in the composer be expanded to include "Acknowledgement-To:"? 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn off all the confirmation [y/n] messages? From owner-pine-info@cac.washington.edu Wed Oct 6 10:00:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05419; Wed, 6 Oct 93 10:00:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09995; Wed, 6 Oct 93 09:30:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09984; Wed, 6 Oct 93 09:30:00 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA01222; Wed, 6 Oct 93 09:29:52 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA13412; Wed, 6 Oct 93 09:29:50 PDT Received: from hal by develop.Law.USC.EDU (4.1/SMI-4.1) id AA21182; Wed, 6 Oct 93 09:29:49 PDT Date: Wed, 6 Oct 1993 09:13:39 -0700 (PDT) From: Elmar Kurgpold Subject: Re: mailing list vs. newsgroup To: Terry Gray Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII How about keeping the mailing list going, and archiving the mail on a gopher server? I think that gopher is accessible to more people than is news. Anyone that watches the sun-managers list will know that any message that has the word "summary" in the subject header is automatically archived on a gopher server, so that all the answer-less questions are not saved. There is usually much less traffic on pine-info, so I am not sure that we would need to filter out any messages, or if we did how it would be determined. The next question is, "Who maintains the gopher server?" If I had more time on my hands, I'd volunteer to do it myself because I've been offered free access to a campus gopher server with reportedly "gobs of disk space". ------------------------------------- | Elmar Kurgpold | | Network Administrator | | University of Southern California | | The Law Center | | ekurgpol@Law.USC.EDU | | (213)740-2571 FAX: (213)740-5502 | ------------------------------------- From owner-pine-info@cac.washington.edu Wed Oct 6 10:04:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05754; Wed, 6 Oct 93 10:04:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10392; Wed, 6 Oct 93 09:47:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gateway.welch.jhu.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10386; Wed, 6 Oct 93 09:47:05 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA05676; Wed, 6 Oct 93 12:44:58 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA21892; Wed, 6 Oct 93 12:45:13 EDT Date: Wed, 6 Oct 1993 12:44:06 -0400 (EST) From: Keith Christopher Subject: Re: Enhancements for next release To: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 487 Can the non implemented features be removed ? How do I stop Pine from writing to sent-mail ? Keith Christopher Welch Medical Library Unix System Adminstrator On Wed, 6 Oct 1993, Jim Lennie wrote: > I have a couple of suggestions for the next release. > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > "Acknowledgement-To:"? > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > off all the confirmation [y/n] messages? > From owner-pine-info@cac.washington.edu Wed Oct 6 10:07:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05931; Wed, 6 Oct 93 10:07:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10544; Wed, 6 Oct 93 09:52:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10538; Wed, 6 Oct 93 09:52:05 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03480; Wed, 6 Oct 93 09:51:34 -0700 Date: Wed, 6 Oct 1993 09:43:08 -0700 (PDT) From: David L Miller Subject: Re: Enhancements for next release To: Jim Lennie Cc: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There will be extensions to the headers available in future versions of Pine. The "Acknowledgement-To:" header is not part of any standards I am aware of though... There will be a couple more options in Pine 3.86 to reduce confirmations. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 6 Oct 1993, Jim Lennie wrote: > I have a couple of suggestions for the next release. > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > "Acknowledgement-To:"? > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > off all the confirmation [y/n] messages? > From owner-pine-info@cac.washington.edu Wed Oct 6 10:35:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07940; Wed, 6 Oct 93 10:35:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11175; Wed, 6 Oct 93 10:18:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11169; Wed, 6 Oct 93 10:18:29 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04388; Wed, 6 Oct 93 10:18:23 -0700 Date: Wed, 6 Oct 1993 10:15:25 -0700 (PDT) From: David L Miller Subject: Re: Enhancements for next release To: Keith Christopher Cc: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Well, we have thought about taking out the non-implemented features, but have not done it. To stop writing sent-mail, set default-fcc="" in your .pinerc. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 6 Oct 1993, Keith Christopher wrote: > Can the non implemented features be removed ? > How do I stop Pine from writing to sent-mail ? > > > Keith Christopher > Welch Medical Library > Unix System Adminstrator > > > On Wed, 6 Oct 1993, Jim Lennie wrote: > > > I have a couple of suggestions for the next release. > > > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > > "Acknowledgement-To:"? > > > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > > off all the confirmation [y/n] messages? > > > > > From owner-pine-info@cac.washington.edu Wed Oct 6 10:59:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09016; Wed, 6 Oct 93 10:59:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11987; Wed, 6 Oct 93 10:48:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11977; Wed, 6 Oct 93 10:48:32 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05294; Wed, 6 Oct 93 10:48:23 -0700 Date: Wed, 6 Oct 1993 10:41:59 -0700 (PDT) From: Terry Gray Subject: Re: Enhancements for next release To: Keith Christopher Cc: David L Miller , Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 6 Oct 1993, David L Miller wrote: > > Can the non implemented features be removed ? > Well, we have thought about taking out the non-implemented features, but > have not done it. Yes, taking them out would be almost as much work as finishing them! :) Note that most of them are individually enabled in the .pinerc, although included in the "old-growth" package. So one could cause all of these: # enable-unix-pipe-cmd (included in old-growth set) # enable-bounce-cmd (included in old-growth set) # enable-apply-cmd (included in old-growth set) # enable-flag-cmd (included in old-growth set) # enable-zoom-cmd (included in old-growth set) to disappear from the keymaps by not setting "feature-list=old-growth" and explicitly listing just the things you want. Apply and Zoom will take awhile yet, but pipe, bounce, and flag should definitely make it into the next non-maintenance release... -teg From owner-pine-info@cac.washington.edu Wed Oct 6 12:49:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13282; Wed, 6 Oct 93 12:49:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14465; Wed, 6 Oct 93 12:36:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gateway.welch.jhu.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14453; Wed, 6 Oct 93 12:36:03 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA22391; Wed, 6 Oct 93 15:33:56 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA22683; Wed, 6 Oct 93 15:34:11 EDT Date: Wed, 6 Oct 1993 15:32:14 -0400 (EST) From: Keith Christopher Subject: Re: Enhancements for next release To: David L Miller Cc: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1532 Thanks for the info. Well I got Pine3.85 to compile under Solaris2.2 using GCC2.4.5, the flags in the makefile.sol should be set to : -traditional (removing the -ansi and -DANSI) I also user the os-sv4.h and .c files for the os dep. I thought you might want to include a HOW-to compile under Sol2.2 with GCC in there somewhere, I can be a contact if you like. Keith Christopher Welch Medical Library Unix System Adminstrator On Wed, 6 Oct 1993, David L Miller wrote: > > Well, we have thought about taking out the non-implemented features, but > have not done it. > > To stop writing sent-mail, set default-fcc="" in your .pinerc. > > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 > |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) > University of Washington, Networks & Distributed Computing > 4545 15th Ave NE, Seattle WA 98105, USA > > On Wed, 6 Oct 1993, Keith Christopher wrote: > > > Can the non implemented features be removed ? > > How do I stop Pine from writing to sent-mail ? > > > > > > Keith Christopher > > Welch Medical Library > > Unix System Adminstrator > > > > > > On Wed, 6 Oct 1993, Jim Lennie wrote: > > > > > I have a couple of suggestions for the next release. > > > > > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > > > "Acknowledgement-To:"? > > > > > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > > > off all the confirmation [y/n] messages? > > > > > > > > > > From owner-pine-info@cac.washington.edu Wed Oct 6 13:01:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13749; Wed, 6 Oct 93 13:01:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14648; Wed, 6 Oct 93 12:45:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ETSU.east-tenn-st.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14640; Wed, 6 Oct 93 12:45:50 -0700 Message-Id: <9310061945.AA14640@mx1.cac.washington.edu> Received: from ETSU by ETSU.EAST-TENN-ST.EDU (IBM VM SMTP V2R2) with BSMTP id 1311; Wed, 06 Oct 93 15:44:40 EDT Date: Wed, 06 Oct 93 15:36:25 EDT From: Bill Williams Organization: East Tennessee State University Subject: Re: PIne3.85 on RS/6000 AIX 3.2.3 To: pine-info@cac.washington.edu In-Reply-To: Your message of Wed, 6 Oct 1993 10:14:45 -0400 (EDT) On Wed, 6 Oct 1993 10:14:45 -0400 (EDT) Tim Cheney said: >On Wed, 6 Oct 1993, Bill Williams wrote: >> I built the Pine 3.85 on a RS/6K AIX 3.2.3 machine using 'build_a32' and >> the thing built without complaint! Congrats to all you a32 port-ers. >> >> Now the bad news: >> When I TelNet in (using FTP's TCP/IP Software on my PC) with vt220 >> emulation, Pine/Pico complains that "vt220 is not a known terminal"! >> Other utilities, vi and less, have no problems recognizing the vt220 so >> what's the problem here? >Recompile using terminfo. Did it, and it fixed that problem! Thanks for the tip. For other RS/6K AIX 3.2.3 users, the changes are to: pine/makefile.a32 and pico/makefile.a32 change modules: tcap to tinfo (:%s/tcap/tinfo/g) change library: termcap to curses (:%s/termcap/curses/g) and re-make for a32. >> Many activities get me kicked out with a "signal abort" and a coredump. >> Immediately reproducable is: >> pine >> 'L' -- List folders >> ...death by signal abort. >> >I had this problem compiling on 3.2.3, but I compiled under 3.2.4 on >another machine and the problem went away. Like the bottom of a fireplace: grate! Just for any wizard who loves these things, here's an edited version of a .pine-debug file: ---------------------------------------------------------------------- Debug output of the Pine program (at debug level 2). Version 3.85 Wed Oct 6 15:19:16 1993 reading_pinerc "/usr/local/lib/pine.conf" Open failed: No such file or directory reading_pinerc "/u/brw/.pinerc" Read 6612 characters ...STUFF DELETED.... Userid: brw Fullname: "Bill Williams -- ETSU Systems Support" User domain name being used "" Local Domain name being used "east-tenn-st.edu" Host name being used "sched25.east-tenn-st.edu" Mail Domain name being used "sched25.east-tenn-st.edu" new win size -----<24 80>------ Terminal type: vt100 Context mail/[] type: LOCAL Address book opened with 4 items ---- COMPOSE SCREEN (not in pico yet) ---- === send called === new win size -----<24 80>------ about to end_tty_driver Pine Panic: Received abort signal ---------------------------------------------------------------------- All these .pine-debug? files show death on the same thing: about to end_tty_driver Pine Panic: Received abort signal ---------- B.R.Wms From owner-pine-info@cac.washington.edu Wed Oct 6 13:35:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14988; Wed, 6 Oct 93 13:35:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15416; Wed, 6 Oct 93 13:17:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15408; Wed, 6 Oct 93 13:17:49 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09219; Wed, 6 Oct 93 13:17:38 -0700 Date: Wed, 6 Oct 1993 13:13:34 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: Attachment Viewing To: Paul Tarr Cc: pine-info@cac.washington.edu, Paul Tarr In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This is the way Pine was designed. When you have a multipart message, there is really nothing in the format of a message to distinguish the body of a message from the attachments. Pine happens to make the body of the message the first part, but there is nothing in the standards that say that has to be the case. Thanks for the good words, I'm glad you are finding Pine useful. --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 30 Sep 1993, Paul Tarr wrote: > I notice that when I use pine 3.85 to view attachments that the > first attachment is always the main body of the mail message. Actual > attachments are always the second or greater attachment. Is this the > intent of the pine design or a bug? > > Bye the way - thanks for pine. My son told me about it and it is > great! I am medically limited to working at home and without pine my life > would be much more difficult. > From owner-pine-info@cac.washington.edu Wed Oct 6 15:16:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18269; Wed, 6 Oct 93 15:16:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17072; Wed, 6 Oct 93 14:59:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17066; Wed, 6 Oct 93 14:59:44 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10472; Wed, 6 Oct 93 14:59:40 -0700 Date: Wed, 6 Oct 1993 14:59:16 -0700 (PDT) From: David L Miller Subject: Re: Enhancements for next release To: Keith Christopher Cc: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks for the information. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 6 Oct 1993, Keith Christopher wrote: > Thanks for the info. > > Well I got Pine3.85 to compile under Solaris2.2 using GCC2.4.5, the flags > in the makefile.sol should be set to : > > -traditional (removing the -ansi and -DANSI) > I also user the os-sv4.h and .c files for the os dep. > > I thought you might want to include a HOW-to compile under Sol2.2 with GCC > in there somewhere, I can be a contact if you like. > > > Keith Christopher > Welch Medical Library > Unix System Adminstrator > > > On Wed, 6 Oct 1993, David L Miller wrote: > > > > > Well, we have thought about taking out the non-implemented features, but > > have not done it. > > > > To stop writing sent-mail, set default-fcc="" in your .pinerc. > > > > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 > > |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) > > University of Washington, Networks & Distributed Computing > > 4545 15th Ave NE, Seattle WA 98105, USA > > > > On Wed, 6 Oct 1993, Keith Christopher wrote: > > > > > Can the non implemented features be removed ? > > > How do I stop Pine from writing to sent-mail ? > > > > > > > > > Keith Christopher > > > Welch Medical Library > > > Unix System Adminstrator > > > > > > > > > On Wed, 6 Oct 1993, Jim Lennie wrote: > > > > > > > I have a couple of suggestions for the next release. > > > > > > > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > > > > "Acknowledgement-To:"? > > > > > > > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > > > > off all the confirmation [y/n] messages? > > > > > > > > > > > > > > > > > > From owner-pine-info@cac.washington.edu Wed Oct 6 15:36:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19266; Wed, 6 Oct 93 15:36:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17446; Wed, 6 Oct 93 15:15:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17440; Wed, 6 Oct 93 15:15:14 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10829; Wed, 6 Oct 93 15:15:05 -0700 Date: Wed, 6 Oct 1993 15:04:16 -0700 (PDT) From: David L Miller Subject: Re: ESC key in PC-pine To: Erik Lawaetz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We made a conscious decision to not give Pine a concept of where "back" is. One of the principles of Pine is that hitting a particular key will do the same thing every time, regardless of the past sequence of commands. Using the ESC key is also a problem because of the need to distinguish the ESC key from an escape sequence. Programs like 'vi' try to get around this by using a timer, but that is very unreliable over slow or heavily used connections. This leads to surprise, which violates another of our major principles. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 1 Oct 1993, Erik Lawaetz wrote: > I haven't been following the discussion on PC-pine thoroughly enough to > know if this has been suggested already, but after about 10 minutes of > usage I already miss something badly. The ability for the ESC key to take > me back, e.g. from the addrbook to the main menu. All I get know is an > annoyin beep. > > --Erik > > From owner-pine-info@cac.washington.edu Wed Oct 6 18:46:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26087; Wed, 6 Oct 93 18:46:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21609; Wed, 6 Oct 93 18:27:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gateway.welch.jhu.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21598; Wed, 6 Oct 93 18:27:01 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA09556; Wed, 6 Oct 93 21:24:55 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA23072; Wed, 6 Oct 93 21:25:09 EDT Date: Wed, 6 Oct 1993 21:23:51 -0400 (EDT) From: Keith Christopher Subject: Re: Enhancements for next release To: David L Miller Cc: Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2382 Question, what's the scoop on the file gmon.out ? how do I stop this file from being generated ? On Wed, 6 Oct 1993, David L Miller wrote: > > Thanks for the information. > > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 > |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) > University of Washington, Networks & Distributed Computing > 4545 15th Ave NE, Seattle WA 98105, USA > > On Wed, 6 Oct 1993, Keith Christopher wrote: > > > Thanks for the info. > > > > Well I got Pine3.85 to compile under Solaris2.2 using GCC2.4.5, the flags > > in the makefile.sol should be set to : > > This should read in the makefile.sol in the pine dir. > > -traditional (removing the -ansi and -DANSI) > > I also user the os-sv4.h and .c files for the os dep. > > > > I thought you might want to include a HOW-to compile under Sol2.2 with GCC > > in there somewhere, I can be a contact if you like. > > > > > > Keith Christopher > > Welch Medical Library > > Unix System Adminstrator > > > > > > On Wed, 6 Oct 1993, David L Miller wrote: > > > > > > > > Well, we have thought about taking out the non-implemented features, but > > > have not done it. > > > > > > To stop writing sent-mail, set default-fcc="" in your .pinerc. > > > > > > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 > > > |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) > > > University of Washington, Networks & Distributed Computing > > > 4545 15th Ave NE, Seattle WA 98105, USA > > > > > > On Wed, 6 Oct 1993, Keith Christopher wrote: > > > > > > > Can the non implemented features be removed ? > > > > How do I stop Pine from writing to sent-mail ? > > > > > > > > > > > > Keith Christopher > > > > Welch Medical Library > > > > Unix System Adminstrator > > > > > > > > > > > > On Wed, 6 Oct 1993, Jim Lennie wrote: > > > > > > > > > I have a couple of suggestions for the next release. > > > > > > > > > > 1) Can the "^R Rich Hdr" function in the composer be expanded to include > > > > > "Acknowledgement-To:"? > > > > > > > > > > 2) Can we add "no-confirm" to the feature list? "no-confirm" would turn > > > > > off all the confirmation [y/n] messages? > > > > > > > > > > > > > > > > > > > > > > > > > > > > Keith Christopher Welch Medical Library Unix System Adminstrator From owner-pine-info@cac.washington.edu Wed Oct 6 23:15:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29818; Wed, 6 Oct 93 23:15:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23554; Wed, 6 Oct 93 23:05:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23548; Wed, 6 Oct 93 23:05:28 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00392; Wed, 6 Oct 93 23:05:25 -0700 Date: Wed, 6 Oct 1993 23:04:12 -0700 (PDT) From: Steve Hubert Subject: Re: Enhancements for next release To: Keith Christopher Cc: David L Miller , Pine-Info Maillist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sounds like you've got profiling turned on. That would usually get turned on by having something like -p or -p in the CFLAGS when you compiled. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 6 Oct 1993, Keith Christopher wrote: > > Question, what's the scoop on the file gmon.out ? how do I stop this file > from being generated ? From owner-pine-info@cac.washington.edu Thu Oct 7 02:20:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03621; Thu, 7 Oct 93 02:20:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24654; Thu, 7 Oct 93 02:11:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24648; Thu, 7 Oct 93 02:11:53 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <23662-0@dummy1.dur.ac.uk>; Thu, 7 Oct 1993 10:11:45 +0100 Received: from draco.dur.ac.uk by vega.dur.ac.uk; Thu, 7 Oct 93 10:11:42 BST Date: Thu, 7 Oct 1993 10:08:02 +0100 (BST) From: Roger Gawley Subject: Re: mailing list vs. newsgroup To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 6 Oct 1993, Elmar Kurgpold wrote: > How about keeping the mailing list going, and archiving the mail on a gopher > server? I think that gopher is accessible to more people than is news. > I agree 100% that gopher is accessible to more people than is news. [Of course, if you used the mailbase programs, you would have a gopher server there.] Now I will stop saying this because we seem to be spending more time on how to deliver the message than on discussing pine! From owner-pine-info@cac.washington.edu Thu Oct 7 04:23:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06145; Thu, 7 Oct 93 04:23:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25448; Thu, 7 Oct 93 04:14:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bart.meiko.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25442; Thu, 7 Oct 93 04:14:20 -0700 Received: by bart.meiko.com id AA06982 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 7 Oct 1993 07:14:17 -0400 Date: Thu, 7 Oct 1993 07:13:32 -0400 (EDT) From: Mike Stok Reply-To: Mike Stok Subject: cut text "vanishes" between messages To: pine-info@cac.washington.edu Cc: David Alden Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII One of my users has just noticed that the way in which cut text is handled between 3.07 and 3.85 is different. He used to be able to combine the contents of more than one message by, for example: starting to forward , go into the body, cut the exciting lines. cancel the forward of reply to , go into its body, uncut the lines which were cut from This allowed him to quote from a number of messages even from a VT100 or similar terminal where the luxury of a window system provided cut & paste facility wasn't provided. Is there any chance of the "old" behaviour slipping back into 3.86, or is there some workaround that I have missed? Thanks, Mike -- The "usual disclaimers" apply. | Meiko Mike Stok | Reservoir Place Mike.Stok@meiko.waltham.ma.us | 1601 Trapelo Road Meiko tel: (617) 890 7676 | Waltham, MA 02154 From owner-pine-info@cac.washington.edu Thu Oct 7 09:05:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11642; Thu, 7 Oct 93 09:05:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28226; Thu, 7 Oct 93 08:45:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ACF4.NYU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28220; Thu, 7 Oct 93 08:45:38 -0700 Received: by acf4.NYU.EDU (5.65/DEC-Ultrix/4.3) id AA10679; Thu, 7 Oct 1993 11:44:18 -0400 Date: Thu, 7 Oct 1993 11:39:18 -0400 (EDT) From: "Yigal M. Rechtman" Subject: Pine on CTIX 5.2.25 (Unix V) To: pinelist Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ok, so I have the code for pine 3.07 (I'd rather this then 3.85, just BECAUSE it has less fetures-- les problems...) and I am trying to compile it on a really low machine, A CTIX (Convergent Tech Unix) S/80 which is the equivallent to Unisys's System/80. I can't seem to find a platform that would be compatiable although I saw in pine-ports some that may be, but could not find their makefile. Does anyone havve any experince with it? We are trying to donate two of these machine to a small college to have them starting with some email capabilites, to join the cyberspace world. So : any ideas? Suggestions? MATERIALS (I will ftp, if possible to get it!) Thanks, Yigal. ______________________________________________________________ | Yigal Rechtman,303 Beverly Rd,Brooklyn,NY,11218 USA | | | | The Most Beautiful Piece Of Art Is | | Your Own Name In PRINT. | | YIGAL M. RECHTMAN | | ymr6189@acf4.nyu.edu | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Thu Oct 7 09:07:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11801; Thu, 7 Oct 93 09:07:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28278; Thu, 7 Oct 93 08:48:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from danpost4.uni-c.dk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28270; Thu, 7 Oct 93 08:48:43 -0700 Received: from danpost4.uni-c.dk by danpost4.uni-c.dk with SMTP (PP) id <11773-0@danpost4.uni-c.dk>; Thu, 7 Oct 1993 16:47:11 +0100 Date: Thu, 7 Oct 1993 16:42:56 +0100 (MET) From: Erik Lawaetz Subject: pine 3.85 cannot handle source routes To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I tried mailing to 2 addresses of the format: @vm.uni-c.dk:user@node which is a fully legal way of mailing to EARN and BITNET users (vm.uni-c.dk being my local gateway). However PINE wouldn't accept it, claiming there to be "Junk at end of address". In this case I'll claim the "junk" to be in pine instead. --Erik From owner-pine-info@cac.washington.edu Thu Oct 7 10:06:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14310; Thu, 7 Oct 93 10:06:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29337; Thu, 7 Oct 93 09:32:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29327; Thu, 7 Oct 93 09:32:09 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21911; Thu, 7 Oct 93 09:31:59 -0700 Date: Thu, 7 Oct 1993 09:22:40 -0700 (PDT) From: David L Miller Subject: Re: Pine on CTIX 5.2.25 (Unix V) To: "Yigal M. Rechtman" Cc: pinelist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My first suggestion would be to get Pine 3.85. Even though it has more features, we have done _alot_ of work to make it easier to port to new platforms. In 3.07 we barely had any SYSV support. Now we have several SYSV variants running. A CTIX port may still not be easy, but we are in a position to better help you with 3.85. Alternatively, there is a person working on a port of Pine to the UnixPC (SVR2). If you like, we can get you in contact with him. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 7 Oct 1993, Yigal M. Rechtman wrote: > Ok, so I have the code for pine 3.07 (I'd rather this then 3.85, just > BECAUSE it has less fetures-- les problems...) and I am trying to compile > it on a really low machine, A CTIX (Convergent Tech Unix) S/80 which is the > equivallent to Unisys's System/80. I can't seem to find a platform that > would be compatiable although I saw in pine-ports some that may be, but > could not find their makefile. Does anyone havve any experince with it? > > We are trying to donate two of these machine to a small college to have them > starting with some email capabilites, to join the cyberspace world. > So : any ideas? Suggestions? MATERIALS (I will ftp, if possible to get it!) > > Thanks, Yigal. > > ______________________________________________________________ > | Yigal Rechtman,303 Beverly Rd,Brooklyn,NY,11218 USA | > | | > | The Most Beautiful Piece Of Art Is | > | Your Own Name In PRINT. | > | YIGAL M. RECHTMAN | > | ymr6189@acf4.nyu.edu | > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > From owner-pine-info@cac.washington.edu Thu Oct 7 10:09:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14421; Thu, 7 Oct 93 10:09:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29275; Thu, 7 Oct 93 09:30:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29269; Thu, 7 Oct 93 09:30:50 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07408; Thu, 7 Oct 93 09:30:44 -0700 Date: Thu, 7 Oct 1993 09:22:04 -0700 (PDT) From: Terry Gray Subject: Re: Pine on CTIX 5.2.25 (Unix V) To: "Yigal M. Rechtman" Cc: pinelist In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yigal, We would *strongly* urge you to upgrade to Pine 3.86, which will be released tonight or tomorrow... 3.86 has important bug fixes compared to 3.07, including improvements in MIME attachment typing that will affect everyone who receives *your* messages with attachments, and will also limit your ability to participate in the Internet remote printing (fax gateway) experiment. Almost all of the new features in Pine 3.85/3.86 are optional and must be explicitly turned on. (And some of them are even believed to be useful :) Finally, 3.85/3.86 is emminently more portable than 3.07, so it should be much easier to get it running on CTIX. Please reconsider your decision to promulgate 3.07. -teg On Thu, 7 Oct 1993, Yigal M. Rechtman wrote: > Ok, so I have the code for pine 3.07 (I'd rather this then 3.85, just > BECAUSE it has less fetures-- les problems...) and I am trying to compile > it on a really low machine, A CTIX (Convergent Tech Unix) S/80 which is the > equivallent to Unisys's System/80. I can't seem to find a platform that > would be compatiable although I saw in pine-ports some that may be, but > could not find their makefile. Does anyone havve any experince with it? > > We are trying to donate two of these machine to a small college to have them > starting with some email capabilites, to join the cyberspace world. > So : any ideas? Suggestions? MATERIALS (I will ftp, if possible to get it!) > > Thanks, Yigal. > > ______________________________________________________________ > | Yigal Rechtman,303 Beverly Rd,Brooklyn,NY,11218 USA | > | | > | The Most Beautiful Piece Of Art Is | > | Your Own Name In PRINT. | > | YIGAL M. RECHTMAN | > | ymr6189@acf4.nyu.edu | > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > From owner-pine-info@cac.washington.edu Thu Oct 7 10:13:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14634; Thu, 7 Oct 93 10:13:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29714; Thu, 7 Oct 93 09:47:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29706; Thu, 7 Oct 93 09:47:22 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22368; Thu, 7 Oct 93 09:47:18 -0700 Date: Thu, 7 Oct 1993 09:46:15 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.85 bug (already =) ) To: Matt Simmons Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have found and corrected this problem for the upcoming Pine 3.86 release. If all goes well, we should start the build process this afternoon. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 23 Sep 1993, Matt Simmons wrote: > Whenever I try to delete a name from the address book, it says error > writing addressbook, permission denied or something to that effect. > After I tried that 2-3 times, it said received abort signal and died... > > Devoted _n______________________________________________ _________________ > Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| > Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | > Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| > =========\ Walt Disney World Monorail System || > LCA _____\________________________________________________||_________________ > __/ This highway's in perfect shape. Quick! Thank god I'm not a > _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) > > > From owner-pine-info@cac.washington.edu Thu Oct 7 10:26:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15348; Thu, 7 Oct 93 10:26:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00209; Thu, 7 Oct 93 10:03:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00203; Thu, 7 Oct 93 10:03:02 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23336; Thu, 7 Oct 93 10:02:38 -0700 Date: Thu, 7 Oct 1993 10:01:34 -0700 (PDT) From: David L Miller Subject: Re: pine 3.85 problems in hpux. To: Hannu Martikka Cc: pine-info@cac.washington.edu In-Reply-To: <199309291603.AA11969@cc.lut.fi> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This problem has been fixed in Pine 3.86. We hope to have it out late today! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 29 Sep 1993, Hannu Martikka wrote: > > I have small problem with pine in hpux. > In /usr/local/lib/pine.conf I have following line: > folder-collections=Mail/[] > > 'Folder list' uses correctly Mail-directory, but if I look system > configuration with pine -conf here is what pine says: > folder-collections=@, > > I'm using pine in hp9000/7xx machines. > In SunOS 4.1.3 it seems to work. > > -- > Regards from Goodi > ______________________________________________________________________________ > Internet: Hannu.Martikka@lut.fi / \ > Bitnet : GOODGULF@FINFILES // \\ \-\-\-\-\-\-\ oh5lhh > Hannu Martikka,Skinnarilankatu /// \\\ | on 70cm > 28 F17, 53850 Lappeenranta,SF /// | \\\_____________|________________________ > Home Tel. +358-(9)53-251446 | :) Lappeenranta University Of Technology | > ------------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Thu Oct 7 10:42:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16276; Thu, 7 Oct 93 10:42:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00812; Thu, 7 Oct 93 10:25:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00803; Thu, 7 Oct 93 10:25:38 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23844; Thu, 7 Oct 93 10:25:08 -0700 Date: Thu, 7 Oct 1993 10:23:35 -0700 (PDT) From: David L Miller Subject: Re: ports to DG/UX To: James Trainor Cc: pine-info@CAC.washington.edu In-Reply-To: <9310060046.AA18255@thunderbird.auc.laurentian.ca> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We just got a report that Porting 3.86 to DG/UX was "hardly worth calling a port". He was using our SVR4 port as a baseline. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 5 Oct 1993, James Trainor wrote: > still have a few bugs to work out for function key mappings. > don't know when i'll have time for 3.86. > are ther substantial advantages over 3.07??? From owner-pine-info@cac.washington.edu Thu Oct 7 11:19:12 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18389; Thu, 7 Oct 93 11:19:12 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16438; Thu, 7 Oct 93 10:48:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ucsd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16432; Thu, 7 Oct 93 10:48:44 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA15905 sendmail 5.67/UCSD-2.2-sun via SMTP Thu, 7 Oct 93 10:48:39 -0700 for pine-info@cac.washington.edu Received: from weber.ucsd.edu (localhost [127.0.0.1]) by weber.ucsd.edu (8.6/UCSDGENERIC.4c) with ESMTP id KAA14150 to ; Thu, 7 Oct 1993 10:48:38 -0700 Message-Id: <199310071748.KAA14150@weber.ucsd.edu> To: pine-info@cac.washington.edu Subject: Re: pine 3.85 cannot handle source routes In-Reply-To: Your message of "Thu, 07 Oct 1993 16:42:56 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 07 Oct 1993 10:48:37 -0700 From: "Michael J. Corrigan" I agree - pine should not force addresses to be in a certain format. -Mike Corrigan I tried mailing to 2 addresses of the format: @vm.uni-c.dk:user@node which is a fully legal way of mailing to EARN and BITNET users (vm.uni-c.dk being my local gateway). However PINE wouldn't accept it, claiming there to be "Junk at end of address". In this case I'll claim the "junk" to be in pine instead. --Erik From owner-pine-info@cac.washington.edu Thu Oct 7 11:25:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18916; Thu, 7 Oct 93 11:25:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01456; Thu, 7 Oct 93 10:48:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from paradiso.umd.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01446; Thu, 7 Oct 93 10:47:58 -0700 Received: from localhost by paradiso.umd.edu (8.5/16.2) id NAA06239; Thu, 7 Oct 1993 13:48:07 -0400 From: Rocky Giannini Message-Id: <199310071748.NAA06239@paradiso.umd.edu> Subject: Pine Reply Bug? To: pine-info@cac.washington.edu Date: Thu, 7 Oct 1993 13:48:07 -0400 (EDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1093 When Pine 3.85 was first released, I posted a message stating that we were consistently getting core dumps when replying to messages from certain sites. We have since narrowed the problem down. It appears that pine was having trouble replying to messages that did not have a Message-Id header. Message-Id header generation was (by default) turned off in our sendmail.cf. It appears that pine generates it's own Message-Id header so that if a pine user received a message sent with pine the reply command worked fine. However messages generated with any other mailer (mail, mailx, elm etc...) caused pine to dump core when the reply command was issued. We have since cleared up this problem by uncommenting the line "H?M?Message-Id: <$t.$i@$j>" in our sendmail.cf file. Now all messages that pass through our system get a Message-Id, but I'm wondering if this is a bug in the latest version of pine, or if our system was configured incorrectly to begin with. We have never had problems with any other mailers or previous versions of pine. -- Rocky Giannini UMUC Unix and VMS Systems From owner-pine-info@cac.washington.edu Thu Oct 7 11:49:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20599; Thu, 7 Oct 93 11:49:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02434; Thu, 7 Oct 93 11:26:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from kamba.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02428; Thu, 7 Oct 93 11:26:47 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA10964; Thu, 7 Oct 93 11:26:40 PDT Date: Thu, 7 Oct 1993 11:25:52 -0700 (PDT) From: Steve Hubert Subject: Re: pine 3.85 cannot handle source routes To: Erik Lawaetz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Source routes are actually required to be in brackets. I think if you use brackets it will work. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Thu, 7 Oct 1993, Erik Lawaetz wrote: > I tried mailing to 2 addresses of the format: > > @vm.uni-c.dk:user@node > > which is a fully legal way of mailing to EARN and BITNET users > (vm.uni-c.dk being my local gateway). > > However PINE wouldn't accept it, claiming there to be "Junk at end of > address". In this case I'll claim the "junk" to be in pine instead. > > --Erik > > From owner-pine-info@cac.washington.edu Thu Oct 7 11:55:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21652; Thu, 7 Oct 93 11:55:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02527; Thu, 7 Oct 93 11:30:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from kamba.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02517; Thu, 7 Oct 93 11:30:00 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA10971; Thu, 7 Oct 93 11:29:55 PDT Date: Thu, 7 Oct 1993 11:29:37 -0700 (PDT) From: Steve Hubert Subject: Re: Pine Reply Bug? To: Rocky Giannini Cc: pine-info@cac.washington.edu In-Reply-To: <199310071748.NAA06239@paradiso.umd.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This has been fixed for 3.86. Thanks. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Thu, 7 Oct 1993, Rocky Giannini wrote: > When Pine 3.85 was first released, I posted a message stating that we > were consistently getting core dumps when replying to messages from certain > sites. > > We have since narrowed the problem down. It appears that pine was having > trouble replying to messages that did not have a Message-Id header. > Message-Id header generation was (by default) turned off in our sendmail.cf. > It appears that pine generates it's own Message-Id header so that if > a pine user received a message sent with pine the reply command worked fine. > However messages generated with any other mailer (mail, mailx, elm > etc...) caused pine to dump core when the reply command was issued. > > We have since cleared up this problem by uncommenting the line > "H?M?Message-Id: <$t.$i@$j>" in our sendmail.cf file. Now all messages > that pass through our system get a Message-Id, but I'm wondering if > this is a bug in the latest version of pine, or if our system was configured > incorrectly to begin with. We have never had problems with any other mailers > or previous versions of pine. > > -- > Rocky Giannini > UMUC Unix and VMS Systems > From owner-pine-info@cac.washington.edu Thu Oct 7 12:02:30 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22096; Thu, 7 Oct 93 12:02:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02897; Thu, 7 Oct 93 11:43:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02889; Thu, 7 Oct 93 11:43:22 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25869; Thu, 7 Oct 93 11:43:12 -0700 Date: Thu, 7 Oct 1993 11:41:23 -0700 (PDT) From: David L Miller Subject: Re: Pine Reply Bug? To: Rocky Giannini Cc: pine-info@cac.washington.edu In-Reply-To: <199310071748.NAA06239@paradiso.umd.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is fixed in Pine 3.86. Unless a major bug shows up in the next few minutes, we will begin packaging this afternoon... |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 7 Oct 1993, Rocky Giannini wrote: > When Pine 3.85 was first released, I posted a message stating that we > were consistently getting core dumps when replying to messages from certain > sites. > > We have since narrowed the problem down. It appears that pine was having > trouble replying to messages that did not have a Message-Id header. > Message-Id header generation was (by default) turned off in our sendmail.cf. > It appears that pine generates it's own Message-Id header so that if > a pine user received a message sent with pine the reply command worked fine. > However messages generated with any other mailer (mail, mailx, elm > etc...) caused pine to dump core when the reply command was issued. > > We have since cleared up this problem by uncommenting the line > "H?M?Message-Id: <$t.$i@$j>" in our sendmail.cf file. Now all messages > that pass through our system get a Message-Id, but I'm wondering if > this is a bug in the latest version of pine, or if our system was configured > incorrectly to begin with. We have never had problems with any other mailers > or previous versions of pine. > > -- > Rocky Giannini > UMUC Unix and VMS Systems From owner-pine-info@cac.washington.edu Thu Oct 7 12:04:54 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22406; Thu, 7 Oct 93 12:04:54 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16763; Thu, 7 Oct 93 11:36:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16757; Thu, 7 Oct 93 11:36:20 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA23113; Thu, 7 Oct 93 11:35:53 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA06002; Thu, 7 Oct 93 11:35:36 -0700 Date: Thu, 7 Oct 1993 11:19:14 -0700 (PDT) From: Mark Crispin Subject: re: pine 3.85 cannot handle source routes To: Erik Lawaetz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 7 Oct 1993 16:42:56 +0100 (MET), Erik Lawaetz wrote: > I tried mailing to 2 addresses of the format: > > @vm.uni-c.dk:user@node > > which is a fully legal way of mailing to EARN and BITNET users > (vm.uni-c.dk being my local gateway). > > However PINE wouldn't accept it, claiming there to be "Junk at end of > address". In this case I'll claim the "junk" to be in pine instead. Please review RFC 822 and RFC 1123. The correct syntax is <@vm.uni-c.dk:user@node> and that works just fine. If you investigate the other address formats that Pine attempts to parse, including some very common bogons, you'll see why the brokets are required; too many ambiguities otherwise. However, I question why you are using RFC 822 source routing addresses at all. These have been deprecated, because ``node'' is required to be a valid entity in the Domain Name System. So, you have to use something like the infamous %- hack, e.g. user%node@vm.uni-c.dk, to get around this. Sigh. I was one of the individuals, 10+ years ago, who pressured (rather LOUDLY) for source routing in RFC 822, after the Powers That Be of the time banned the RFC 733 multiple-@ syntax (which looked like ``user at node at uni- c-vm''). When RFC 822 was issued, I went to implement source routes and immediately ran up against the ``must be a valid name in the host table (later DNS)'' rule. The %-hack was a 2AM fix for the problem. [Not that the %-hack was without problems; it was responsible for the entire OS development group at a major computer vendor being unable to log in the next day...] :-) From owner-pine-info@cac.washington.edu Thu Oct 7 12:24:48 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23093; Thu, 7 Oct 93 12:24:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03503; Thu, 7 Oct 93 12:06:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ucdavis.ucdavis.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03491; Thu, 7 Oct 93 12:06:54 -0700 Received: from neyman.ucdavis.edu by ucdavis.ucdavis.edu (4.1/UCD2.05) id AA05874; Thu, 7 Oct 93 11:56:26 PDT Received: by neyman.ucdavis.edu (5.57/UCD2.03) id AA06267; Thu, 7 Oct 93 11:53:01 -0700 Date: Thu, 7 Oct 1993 11:43:36 -0700 (PDT) From: Larry Tai Subject: Reply To All Recipients Problem To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We are running Pine 3.07 on DECStations 5000s under Ultrix 4.3a. We seem to be having a problem with the "Reply TO All Recipients?" feature. The "Reply To All Recipients? (y/n)" prompt always comes on even when the original message was sent to only one recipient. Can some one shed some light on this? Thanks in advance. --------- US-Mail: Larry Tai, 2120A Wickson, Statistical Laboratory UC Davis, Davis, Ca. 95616 E-Mail: larry@wald.ucdavis.edu or lptai@ucdavis.edu Tel: (916)-752-6085 From owner-pine-info@cac.washington.edu Thu Oct 7 12:27:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23164; Thu, 7 Oct 93 12:27:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03349; Thu, 7 Oct 93 12:01:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03335; Thu, 7 Oct 93 12:01:39 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <06891-0@dummy1.dur.ac.uk>; Thu, 7 Oct 1993 19:59:21 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Thu, 7 Oct 93 19:59:19 BST Date: Thu, 7 Oct 1993 19:51:32 +0100 (BST) From: Barry Cornelius Subject: Re: Pine Reply Bug? To: Rocky Giannini Cc: pine-info@cac.washington.edu In-Reply-To: <199310071748.NAA06239@paradiso.umd.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 7 Oct 1993, Rocky Giannini wrote: > When Pine 3.85 was first released, I posted a message stating that we > were consistently getting core dumps when replying to messages from certain > sites. > We have since narrowed the problem down. It appears that pine was having > trouble replying to messages that did not have a Message-Id header. > [stuff deleted] I have noticed this too. If you reply to a message with no Message-ID line, with 3.85 compiled for HP-UX 8.07, Pine will generate the following line in the reply: In-Reply-To: With SunOS 4.1.x, Pine 3.85 will generate the following line in the reply: In-Reply-To: (null) However, with SunOS 5.2, Pine 3.85 will crash if an attempt is made to reply to a message that has no Message-ID line. The problem lies in the function generate_reply_to in the file pine/reply.c. This function attempts to use sprintf on a pointer which I believe is NULL when replying to a message with no Message-ID line. The following patch solves the problem. With this patch, the In-Reply-To line is not generated (when replying to a message with no Message-ID line). *** /users/pine/pine3.85.930923/pine/reply.c Thu Sep 23 04:52:07 1993 --- /users/pine/pine3.85.930927/pine/reply.c Fri Oct 1 18:29:27 1993 *************** *** 1270,1275 **** --- 1270,1279 ---- if (env == NULL) return(NULL); + /* BJC 931001B: added the next two lines + */ + if (env->message_id == NULL) + return(NULL); else { sprintf(buffer, "%.100s", env->message_id); } I have reported this to pine-bugs@cac.washington.edu, and Michael Seibel replied saying that this bug will be repaired in 3.86. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Thu Oct 7 13:02:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24348; Thu, 7 Oct 93 13:02:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04305; Thu, 7 Oct 93 12:49:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04299; Thu, 7 Oct 93 12:49:57 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27047; Thu, 7 Oct 93 12:48:20 -0700 Date: Thu, 7 Oct 1993 12:42:21 -0700 (PDT) From: David L Miller Subject: Re: Reply To All Recipients Problem To: Larry Tai Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine 3.07 had some difficulties with the matching algorithm when comparing the recipients of the message with the sender of the reply. If you reply to a message directed only to you and answer yes to "Reply To All Recipients? (y/n)", you should see your name in the cc: header. This problem is fixed in Pine 3.85. Unless something crops up in the next few minutes, we will start packaging Pine 3.86 this afternoon. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 7 Oct 1993, Larry Tai wrote: > > We are running Pine 3.07 on DECStations 5000s under Ultrix 4.3a. We seem to > be having a problem with the "Reply TO All Recipients?" feature. > > The "Reply To All Recipients? (y/n)" prompt always comes on even when the > original message was sent to only one recipient. Can some one shed some > light on this? > > Thanks in advance. > > --------- > US-Mail: Larry Tai, 2120A Wickson, Statistical Laboratory > UC Davis, Davis, Ca. 95616 > E-Mail: larry@wald.ucdavis.edu or lptai@ucdavis.edu > Tel: (916)-752-6085 > From owner-pine-info@cac.washington.edu Thu Oct 7 13:26:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25261; Thu, 7 Oct 93 13:26:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04783; Thu, 7 Oct 93 13:12:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pitt.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04777; Thu, 7 Oct 93 13:12:37 -0700 Received: by pitt.edu id AA05004 (5.65c/IDA-1.4.4.5 for pine-info@cac.washington.edu); Thu, 7 Oct 1993 16:12:34 -0400 Received: via switchmail; Thu, 7 Oct 1993 16:12:31 -0400 (EDT) Received: from emerald.cis.pitt.edu via qmail ID ; Thu, 7 Oct 1993 16:11:50 -0400 (EDT) Received: from emerald.cis.pitt.edu via qmail ID ; Thu, 7 Oct 1993 16:11:41 -0400 (EDT) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.emerald.cis.pitt.edu.pmax.ul4 via MS.5.6.emerald.cis.pitt.edu.pmax_ul4; Thu, 7 Oct 1993 16:11:40 -0400 (EDT) Message-Id: Date: Thu, 7 Oct 1993 16:11:40 -0400 (EDT) From: James Ralston Crawford Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: Pine Info Subject: Pine "From:" header bug (was Re: Pine Reply Bug?) In-Reply-To: <199310071748.NAA06239@paradiso.umd.edu> References: <199310071748.NAA06239@paradiso.umd.edu> Excerpts from dl.pine-info: 7-Oct-93 Pine Reply Bug? Rocky Giannini@paradiso. (1093*) > When Pine 3.85 was first released, I posted a message stating that we > were consistently getting core dumps when replying to messages from > certain sites. We have since narrowed the problem down. It appears > that pine was having trouble replying to messages that did not have a > Message-Id header. Speaking of which, has the bug in Pine which causes it to crash on a message without a From: header been fixed? This bug is present in version 3.03... -- James Ralston Crawford \ qralston+@pitt.edu \ Systems and Networks [CIS] University of Pittsburgh \ 600 Epsilon Drive \ Pittsburgh PA 15238-2887 "Computer, you and I need to have a little talk." - O'Brien, ST:DS9 From owner-pine-info@cac.washington.edu Thu Oct 7 13:49:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26084; Thu, 7 Oct 93 13:49:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04954; Thu, 7 Oct 93 13:28:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04946; Thu, 7 Oct 93 13:27:56 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27860; Thu, 7 Oct 93 13:27:48 -0700 Date: Thu, 7 Oct 1993 13:27:33 -0700 (PDT) From: David L Miller Subject: Re: Pine "From:" header bug (was Re: Pine Reply Bug?) To: James Ralston Crawford Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, that is fixed. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 7 Oct 1993, James Ralston Crawford wrote: > Excerpts from dl.pine-info: 7-Oct-93 Pine Reply Bug? Rocky > Giannini@paradiso. (1093*) > > > When Pine 3.85 was first released, I posted a message stating that we > > were consistently getting core dumps when replying to messages from > > certain sites. We have since narrowed the problem down. It appears > > that pine was having trouble replying to messages that did not have a > > Message-Id header. > > Speaking of which, has the bug in Pine which causes it to crash on a > message without a From: header been fixed? This bug is present in > version 3.03... > > -- > James Ralston Crawford \ qralston+@pitt.edu \ Systems and Networks [CIS] > University of Pittsburgh \ 600 Epsilon Drive \ Pittsburgh PA 15238-2887 > "Computer, you and I need to have a little talk." - O'Brien, ST:DS9 From owner-pine-info@cac.washington.edu Thu Oct 7 15:07:27 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28917; Thu, 7 Oct 93 15:07:27 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06508; Thu, 7 Oct 93 14:43:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06502; Thu, 7 Oct 93 14:43:16 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00214; Thu, 7 Oct 93 14:43:12 -0700 Date: Thu, 7 Oct 1993 14:40:14 -0700 (PDT) From: David L Miller Subject: Re: saved messages marked as NEW/folder lock To: Alex Tang Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Your first problem is on the list for the future, but it will not make it into the Pine 3.86 maintenance release. One way to look at it is that the message is new to this folder... Your second problem is more difficult and has recieved some attention in other postings on pine-info in the last few days, so I won't go into it again. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 28 Sep 1993, Alex Tang wrote: > Hi. I've got 2 questions...first with pine 3.85, when I save messages to > folders, they get re-marked as new...even if it was read and/or answered > before i saved it. Is this a bug or a feature? > > Second I thought that pine would get the folder lock from another pine > process. When I run pine, then suspend it, then run pine again, it chews > on the lock process for a while, then it says that it's read only, and > the original session gets the write access taken away....hence 2 pine > sessions with no write capaability. > > just wondering.... > > ...alex... > > Alex Tang -- ALTITUDE@UMICH.EDU...USERW00Y@UMICHUM.BITNET > U of M, SNRE: Student and Computer Consultant II, > ITD/CSS Consultant, Short asian with long hair :) > "Think young grasshopper...but remember...you must think in C." > > From owner-pine-info@cac.washington.edu Thu Oct 7 20:15:57 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07769; Thu, 7 Oct 93 20:15:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07056; Thu, 7 Oct 93 19:38:20 -0700 Received: by ListDist v0.2 for /usr/local/lib/pine-announce.cf Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07048; Thu, 7 Oct 93 19:38:19 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11236; Thu, 7 Oct 93 19:38:14 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05914; Thu, 7 Oct 93 19:38:12 -0700 Reply-To: Michael Seibel Message-Id: Date: Thu, 7 Oct 1993 19:15:42 -0700 (PDT) From: Michael Seibel To: Pine Announcement Distribution Subject: Pine 3.86 released X-Owner: pine-announce-request@cac.washington.edu X-To: Pine Announce Distribution Version 3.86 of Pine and PC-Pine is now available. The release also includes new versions of Pico and IMAPd. STATUS... This is primarily a maintenance release, although there are actually a couple of new features (and therefore a chance of a few new bugs). In a few cases, we changed Pine's behavior back to the way it was before 3.85, based on feedback from you. There are some important bug fixes, so we encourage everyone to upgrade to 3.86 as soon as possible. You should update your IMAPd as well. Pine's method of discovering remote folders has been changed (to avoid an unfortunate conflict with other IMAP clients that make use of a hidden .mailboxlist file) but will be somewhat slower *unless* using the new IMAPd. There are other IMAPd fixes as well. The list of changes/fixes is appended... and is quite long, considering that 3.85 is only two weeks old! HOW TO GET IT... --> Via anonymous FTP ftp pine.cac.washington.edu user: anonymous passwd: your email address binary cd mail get pine.tar.Z <-- full distribution, including Pico and IMAPd get pcpine_f.zip <-- version for FTP PC/TCP get pcpine_n.zip <-- version for Novell LWP get pcpine_s.zip <-- version for Sun PC/NFS get pcpine_p.zip <-- version for Packet Driver quit There will also be precompiled binaries available for certain platforms. These will have names like pine-bin.ultrix. --> Via PC-Pine PC-Pine users can also obtain new versions via the "Update" option under the Main Menu "Setup" command. From the Folder Index of the Update Server, just select and View the msg containing the version you need, then View/Save the attached Zip file. Note: it is still true that, because attachment encoding/decoding has not *yet* been performance-tuned, using Update and Save will be slower than FTP, but it may be more convenient. RELEASE NOTES (Changes since 3.85)... -Revert to having GOTO enabled by default. -Revert to allowing open folders to be deleted. -Revert to former meaning of -i command line flag. -Add command line flag -I for initial keystroke list (replaces -i overload). -Make personal feature list add to global feature list instead of replace. -Allow negation of previously-enabled features by prefixing "no-". -Add "by-from" name rule; change "by-sender" to use Sender: field -Add "expunge-without-confirm" feature. -Add "auto-move-read-msgs" feature. -Change "save-by-X" rules to strip routing data from offered foldername. -Change Pine to use FIND ALL, to avoid conflict with .mailboxlist. -Change IMAPd's FIND ALL behavior to not check file type. -Change Tenex-format mailbox extensions from .txt to .TxT. -Change composer to only put one blank between .sig and included text. -Change pine to expand tabs on fixed, 8-char boundaries. -Change address book nickname display length to match input limit. -Change inline-text encoding rule to use quoted-printable more often. -Change NewVersion message to indicate it only shows once, etc. -Change wording of monthly pruning message. -Change Ctl-K message to appear less frequently. -Fix: Delete in/after spell-check may trash msg or crash Pine. -Fix: crash resulting from M->S->? key sequence. -Fix: crash resulting from null To: field. -Fix: crash resulting from "::" in From: header. -Fix: crash resulting from replying to above. -Fix: for long headers (address lists longer than a screen). -Fix: [Mark Set] message should vanish after ^K. -Fix: "No attachments" msg in Postpone is too long to fit. -Fix: Ext. help inclusion confusion (insert page breaks as file is read). -Fix: Low-speed fixes that broke in Pico 2.0. -Fix: Select/Goto should return to previous folder when open fails. -Fix: Spaces at beginning of filenames are now ignored in Save/Export. -Fix: put domain literal brackets around X-Sender when necessary. -Fix: Can't save to INBOX if "inbox" is implicit in inbox-path. -Fix Pico so lines w/tabs display correctly when characters deleted. -Fix negative network number in bracketed host numbers for DOS SMTP clients. -Fix Tenex driver to never cause a kiss-of-death to be sent or received. -Fix: Some global config options not transferred/displayed correctly? -Fix: Use "default state" when returning to INBOX, instead of wrong msg #. -Make PC-Pine more graceful when out of memory during a Send. -Suppress From: (Sender Unknown) in included headers for -nr mode -Improve performance of TAB and Del-skips-del on large folders. -Improve failure case when .addressbook or .pinerc can't be re-written. -IMAPd ignores kiss-of-death if current mailbox is not bezerk, mmdf, or mbox -Use XHDR in NNTP client drivers to work around a missing LISTGROUP command. -Internal FIND/FIND ALL redesign (no user or Pine-visible changes) -Create separate VAX ULtrix (VUL) port. -Rsh program name and pathname now set in c-client makefile for each port. -Modify some ports to be only makefiles (and perhaps os_???.h files). -Suppress Tenex driver new-mail snarf if it can't get RW access to spool. As always, thanks for your interest in pine! The Pine Team From owner-pine-info@cac.washington.edu Fri Oct 8 01:39:45 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13229; Fri, 8 Oct 93 01:39:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12419; Fri, 8 Oct 93 01:08:18 -0700 Received: by ListDist v0.2 for /usr/local/lib/pine-announce.cf Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12413; Fri, 8 Oct 93 01:08:17 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13610; Fri, 8 Oct 93 01:08:17 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08301; Fri, 8 Oct 93 01:08:12 -0700 Reply-To: Terry Gray Message-Id: Date: Fri, 8 Oct 1993 00:58:30 -0700 (PDT) From: Terry Gray To: Pine Announcement Distribution Subject: 3.86 oops... X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu A bug capable of causing Unix Pine to crash has been found (already). It will occur if your FCC is a path name, e.g. ~/sent-mail The file /mail/patches-for-3.86.tar on ftp.cac.washington.edu contains the fix. Thanks to Leland Woodbury for the quick bug report and fix! -teg From owner-pine-info@cac.washington.edu Fri Oct 8 02:36:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14567; Fri, 8 Oct 93 02:36:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14016; Fri, 8 Oct 93 02:17:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from danpost4.uni-c.dk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14010; Fri, 8 Oct 93 02:17:25 -0700 Received: from danpost4.uni-c.dk by danpost4.uni-c.dk with SMTP (PP) id <15289-0@danpost4.uni-c.dk>; Fri, 8 Oct 1993 10:03:56 +0100 Date: Fri, 8 Oct 1993 09:14:26 +0100 (MET) From: Erik Lawaetz Subject: re: pine 3.85 cannot handle source routes To: Mark Crispin Cc: Erik Lawaetz , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Please review RFC 822 and RFC 1123. The correct syntax is > <@vm.uni-c.dk:user@node> > and that works just fine. If you investigate the other address formats that > Pine attempts to parse, including some very common bogons, you'll see why the > brokets are required; too many ambiguities otherwise. Are you seriously suggesting that I should tell my users: "Oh yes, btw for some addresses you might need to put it in <>s" ? I don't posses your intimate knowledge of RFC 822 nor 1123, which I assume is the host requiremtns rfc, but from a user's perspective I'd rather have PINE accepting the address. The UAs I've used previously generously did this, and to the best of my knowledge did not create any problems. > However, I question why you are using RFC 822 source routing addresses at all. > These have been deprecated, because ``node'' is required to be a valid entity > in the Domain Name System. So, you have to use something like the infamous %- > hack, e.g. user%node@vm.uni-c.dk, to get around this. Looks like my weekend will be spent rereading 822 and reading 1123? ;-) --Erik From owner-pine-info@cac.washington.edu Fri Oct 8 02:37:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14624; Fri, 8 Oct 93 02:37:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14028; Fri, 8 Oct 93 02:18:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from danpost4.uni-c.dk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14022; Fri, 8 Oct 93 02:18:16 -0700 Received: from danpost4.uni-c.dk by danpost4.uni-c.dk with SMTP (PP) id <15404-0@danpost4.uni-c.dk>; Fri, 8 Oct 1993 10:16:44 +0100 Date: Fri, 8 Oct 1993 10:11:17 +0100 (MET) From: Erik Lawaetz Subject: Re: Reply To All Recipients Problem To: David L Miller Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Pine 3.07 had some difficulties with the matching algorithm when > comparing the recipients of the message with the sender of the reply. If > you reply to a message directed only to you and answer yes to "Reply To > All Recipients? (y/n)", you should see your name in the cc: header. One additional feature available in elm would be very helpful. In my elmrc file I had: # alternative addresses that I could receive mail from (usually a # forwarding mailbox) and don't want to have listed... alternatives =erik.lawaetz@uni-c.dk uniel@danpost.uni-c.dk uniel@danpost2.uni-c.dk uniel@uts.uni-c.dk postmaster@danpost4.uni-c.dk which helped persuade elm not to include these addresses in replies to all recipients. --Erik From owner-pine-info@cac.washington.edu Fri Oct 8 03:48:50 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16001; Fri, 8 Oct 93 03:48:50 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21193; Fri, 8 Oct 93 03:22:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21187; Fri, 8 Oct 93 03:22:24 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA24909; Fri, 8 Oct 93 03:22:17 -0700 Date: Fri, 8 Oct 1993 03:19:25 -0700 (PDT) From: Mark Crispin Reply-To: Mark Crispin Subject: re: pine 3.85 cannot handle source routes To: Erik Lawaetz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 8 Oct 1993, Erik Lawaetz wrote: > Are you seriously suggesting that I should tell my users: "Oh yes, btw > for some addresses you might need to put it in <>s" ? Unfortunately, yes. There are ambiguities that occur otherwise. > I don't posses your intimate knowledge of RFC 822 nor 1123, which I > assume is the host requiremtns rfc, but from a user's perspective I'd > rather have PINE accepting the address. The UAs I've used previously > generously did this, and to the best of my knowledge did not create any > problems. How did the other UAs solve the parsing ambiguities? To be more specific about the problem with source routes, the host requirements RFC (RFC 1123) explicitly depreciates them (paragraphs 5.2.6, 5.2.19). Technically, Pine is in violation of the Host Requirements by permitting their use at all. We would have no defense to the ``protocol police'' if someone received a message with one that was generated by Pine and complained. Host Requirements specifies that some means of mail relaying that does not involve the use of RFC 822 source routing be used instead, e.g. user%node@uni-c.dk (the so-called %-hack) instead of <@uni-c.dk:user@node> This recommended way (RFC 1123 paragraph 5.2.16) is three characters shorter and arguably easier to understand! So, we're between a rock and a hard place. We're not supposed to permit the user to use source routes, there's an officially blessed alternative, and there's a possibility that it might break something else if source routes were permitted outside of the angle brackets. Would it be possible to use the ``% hack'' instead? From owner-pine-info@cac.washington.edu Fri Oct 8 08:12:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21531; Fri, 8 Oct 93 08:12:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16711; Fri, 8 Oct 93 07:51:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pp.dundee.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16705; Fri, 8 Oct 93 07:51:11 -0700 Received: from dux.dundee.ac.uk by pp.dundee.ac.uk with SMTP (PP) id <26039-0@pp.dundee.ac.uk>; Fri, 8 Oct 1993 15:33:37 +0100 Received: by dux.dundee.ac.uk (5.0/SMI-SVR4-S2000) id AA21860; Fri, 8 Oct 93 15:49:14 BST Date: Fri, 8 Oct 1993 15:41:02 +0100 (BST) From: "K.M. Lovell Information Technology Services ext 4" Subject: Pine 3.86 core dump with solaris 2.2 - ok with 3.85 To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 604 I have compiled pine 3.86 with the patch-for-3.86.tar fix but get a segmentation core dump when I run it - No output comes out. This is on a Sparc 2000 running Solaris 2.2. I found pine 3.85 compiled under Solaris 2.2 ok and ran ok. I am compiling using Sun's c compiler with -Xs option in addition to your supplied options. -------------------------------------------------------------- From: K.M.Lovell , Information Technology Services, University of Dundee, Park Place , Dundee DD1 4HN , UK Email: kmlovell@dux.dundee.ac.uk Tel : +44 382 307136 Fax : +44 382 28649 From owner-pine-info@cac.washington.edu Fri Oct 8 11:00:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28181; Fri, 8 Oct 93 11:00:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20178; Fri, 8 Oct 93 10:36:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20166; Fri, 8 Oct 93 10:36:35 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <18858-0@dummy1.dur.ac.uk>; Fri, 8 Oct 1993 18:36:29 +0100 Date: Fri, 8 Oct 1993 18:29:00 +0100 (BST) From: Barry Cornelius Subject: Re: Reply To All Recipients Problem To: Erik Lawaetz Cc: David L Miller , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 8 Oct 1993, Erik Lawaetz wrote: > > Pine 3.07 had some difficulties with the matching algorithm when > > comparing the recipients of the message with the sender of the reply. If > > you reply to a message directed only to you and answer yes to "Reply To > > All Recipients? (y/n)", you should see your name in the cc: header. > > One additional feature available in elm would be very helpful. > In my elmrc file I had: > # alternative addresses that I could receive mail from (usually a # > forwarding mailbox) and don't want to have listed... > alternatives =erik.lawaetz@uni-c.dk uniel@danpost.uni-c.dk > uniel@danpost2.uni-c.dk uniel@uts.uni-c.dk > postmaster@danpost4.uni-c.dk > which helped persuade elm not to include these addresses in replies to all > recipients. I have never sent the Pine people any wish list for Pine. However, this is one that I have been meaning to send them for the last 4 months: it is the one that would top our wish list. Whenever you release a new version of Pine, I modify the code so that it understands the mailnames that are used at the University of Durham. For example, although my username is dcl0bjc and this message is being sent from vega.dur.ac.uk, my e-mail address is Barry.Cornelius@durham.ac.uk. So, I want to be able to include something in my .pinerc that will tell Pine that messages addressed to the address Barry.Cornelius@durham.ac.uk and Barry.Cornelius@dur.ac.uk are references to me. Is this the issue addressed by the "alternatives" variable of elm? If so, could we please, please, please have it in one of the next non-maintenance releases of Pine. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Fri Oct 8 11:40:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00350; Fri, 8 Oct 93 11:40:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20865; Fri, 8 Oct 93 11:12:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20859; Fri, 8 Oct 93 11:12:45 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18772; Fri, 8 Oct 93 11:12:32 -0700 Date: Fri, 8 Oct 1993 11:10:20 -0700 (PDT) From: Steve Hubert Subject: Re: Reply To All Recipients Problem To: Barry Cornelius Cc: Erik Lawaetz , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The alternatives variable sounds like something we could do. (We have to evaluate the idea and think about it and blah, blah, blah first, of course.) To the best of my recollection, you are the first two people who've ever requested such a feature, but now that you mention it, it does seem like a feature that many mailers have. Thanks for the suggestion. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Fri Oct 8 13:37:10 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04985; Fri, 8 Oct 93 13:37:10 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23159; Fri, 8 Oct 93 13:08:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23148; Fri, 8 Oct 93 13:08:06 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <20903-0@dummy1.dur.ac.uk>; Fri, 8 Oct 1993 21:07:59 +0100 Received: from altair (altair.dur.ac.uk) by vega.dur.ac.uk; Fri, 8 Oct 93 21:07:57 BST Date: Fri, 8 Oct 1993 21:01:52 +0100 (BST) From: Barry Cornelius Reply-To: Barry Cornelius Subject: Re: Pine 3.86 core dump with solaris 2.2 - ok with 3.85 To: "K.M. Lovell Information Technology Services ext 4" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Length: 1061 On Fri, 8 Oct 1993, K.M. Lovell Information Technology Services ext 4 wrote: > I have compiled pine 3.86 with the patch-for-3.86.tar fix but > get a segmentation core dump when I run it - No output comes out. > This is on a Sparc 2000 running Solaris 2.2. > I found pine 3.85 compiled under Solaris 2.2 ok and ran ok. > I am compiling using Sun's c compiler with -Xs option in addition to your > supplied options. Like you, I have compiled Pine 3.86 with the patches-for-3.86.tar fix on a SunOS 5.2 (Solaris 2.2) machine. I compiled it using: /opt/SUNWspro/bin/cc -Xs ... I run it on the same SunOS 5.2 machine using an IMAPd daemon running on a SunOS 4.1.3 machine. I have not seen the segmentation core dump problem that you mention. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Fri Oct 8 14:19:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06608; Fri, 8 Oct 93 14:19:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24179; Fri, 8 Oct 93 13:54:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from unlinfo.unl.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24172; Fri, 8 Oct 93 13:53:52 -0700 Received: from unlinfo2.unl.edu by unlinfo.unl.edu (4.1/SMI-4.1) id AA27671; Fri, 8 Oct 93 15:48:15 CDT Received: by unlinfo2.unl.edu (4.1/SMI-4.1) id AA27322; Fri, 8 Oct 93 15:47:00 CDT Date: Fri, 8 Oct 1993 15:37:14 -0500 (CDT) From: Paul H Kramer Subject: How to set up pine read news only? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII At our university, a person sees a full-screen menu after s/he logs in. Two of the items on the menu are worded M)ail and N)etwork News. If the person presses M then pine is launched and if N is pressed then nn is launched. If I substitute pine for nn, how can I keep pine from going into the INBOX. I want pine when launched as a news reader to only look at USENET newsgroups. I don't want the person to be able to switch into their personal mailboxes when they originally started pine as a news reader. Second unrelated question, does anybody have a written document that they would be willing to share with me that explains why pine would be a better mail agent than elm for general users. I need something that I can present that would make people see the light and switch to pine. Paul -- Paul H Kramer Computing Resource Center (402) 472-5427 Room 120, 501 Building pkramer@unl.edu University of Nebraska-Lincoln From owner-pine-info@cac.washington.edu Fri Oct 8 14:19:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06617; Fri, 8 Oct 93 14:19:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24005; Fri, 8 Oct 93 13:43:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23993; Fri, 8 Oct 93 13:43:31 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23550; Fri, 8 Oct 93 13:43:09 -0700 Date: Fri, 8 Oct 1993 13:41:07 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.86 core dump with solaris 2.2 - ok with 3.85 To: Barry Cornelius Cc: "K.M. Lovell Information Technology Services ext 4" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Check to make sure that you have something listed in the feature-list variable in your .pinerc. An empty feature-list triggers a bug on Solaris. This will be fixed in Pine 3.87. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 8 Oct 1993, Barry Cornelius wrote: > On Fri, 8 Oct 1993, K.M. Lovell Information Technology Services ext 4 wrote: > > > I have compiled pine 3.86 with the patch-for-3.86.tar fix but > > get a segmentation core dump when I run it - No output comes out. > > This is on a Sparc 2000 running Solaris 2.2. > > I found pine 3.85 compiled under Solaris 2.2 ok and ran ok. > > I am compiling using Sun's c compiler with -Xs option in addition to your > > supplied options. > > Like you, I have compiled Pine 3.86 with the patches-for-3.86.tar fix on a > SunOS 5.2 (Solaris 2.2) machine. I compiled it using: > > /opt/SUNWspro/bin/cc -Xs ... > > I run it on the same SunOS 5.2 machine using an IMAPd daemon running on a > SunOS 4.1.3 machine. I have not seen the segmentation core dump problem > that you mention. > > -- > Barry Cornelius Durham (091 or +44 91) 374 4717 > Information Technology Service, IT Service Office: 374 2892 > University of Durham, Durham. Fax: 374 3741 > DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk > > > > From owner-pine-info@cac.washington.edu Fri Oct 8 14:58:49 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08236; Fri, 8 Oct 93 14:58:49 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24915; Fri, 8 Oct 93 14:38:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24909; Fri, 8 Oct 93 14:38:11 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25815; Fri, 8 Oct 93 14:38:09 -0700 Date: Fri, 8 Oct 1993 14:37:26 -0700 (PDT) From: Steve Hubert Subject: Re: Pine 3.86 core dump with solaris 2.2 - ok with 3.85 To: David L Miller Cc: Barry Cornelius , "K.M. Lovell Information Technology Services ext 4" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII And a feature of no-something is allowed in 3.86 and would effectively be a no-op. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Fri, 8 Oct 1993, David L Miller wrote: > > Check to make sure that you have something listed in the feature-list > variable in your .pinerc. An empty feature-list triggers a bug on > Solaris. This will be fixed in Pine 3.87. From owner-pine-info@cac.washington.edu Fri Oct 8 15:04:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08600; Fri, 8 Oct 93 15:04:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24510; Fri, 8 Oct 93 14:42:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ua.d.umn.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24504; Fri, 8 Oct 93 14:41:54 -0700 Received: from jness.d.umn.edu by ua.d.umn.edu with SMTP id AA17380 (5.65c/IDA-1.4.4 for ); Fri, 8 Oct 1993 16:41:47 -0500 Date: Fri, 8 Oct 93 16:41:46 -0600 From: Joel Ness To: pine-info@cac.washington.edu Subject: Re: How to set up pine read news only? Message-Id: In-Reply-To: Your message of Fri, 8 Oct 1993 15:37:14 -0500 (CDT) Content-Type: TEXT/plain; charset=US-ASCII > At our university, a person sees a full-screen menu > after s/he logs in. Two of the items on the menu are > worded M)ail and N)etwork News. If the person presses > M then pine is launched and if N is pressed then nn is > launched. If I substitute pine for nn, how can I keep > pine from going into the INBOX. I want pine when > launched as a news reader to only look at USENET > newsgroups. I don't want the person to be able to > switch into their personal mailboxes when they > originally started pine as a news reader. > > Second unrelated question, does anybody have a written > document that they would be willing to share with me > that explains why pine would be a better mail agent > than elm for general users. I need something that I > can present that would make people see the light and > switch to pine. > > Paul > -- > Paul H Kramer Computing Resource Center > (402) 472-5427 Room 120, 501 Building > pkramer@unl.edu University of Nebraska-Lincoln This is mostly a "me too" kind of reply in that we are also very interested in other folk's experiences with using Pine as an interface to news. Our interest is because we want to make it easier to electronically distribute general announcements and information on campus. We don't want to distribute the same email message to many hundreds of mail boxes (inefficient and, to some folk, annoying). News groups are the ideal vehicle, but the learning curve for most Unix mail interfaces would prevent most folks from reading news the conventional way. Eventually, people can use Mac and PC based news readers (and mail programs) with nicer interfaces. But for now most use some type of vt100 access to our central systems. If most of our folk are already logging in and running Pine to read mail, they'd have no problems using the same Pine interface to read announcements. We've started playing around with 3.85 and have found that we can have .pinerc file point to specific newsgroups and, using the initial keystroke options, start Pine right into an index screen of that mail group. What we'd like to know is what options/problems other folks have discovered for similar types of services. Ideally, we'd like to present people with a front end menu of commonly used Unix applications such as mail, announcements, scheduling, and file management. Choosing mail gives you Pine, choosing announcements gives you Pine pointed at a newsgroup (we assume we'd have to have this use a different .pinerc for this). Anyone else trying similar things yet? _________________________ Joel Ness UMD Information Services jness@ua.d.umn.edu (218) 726-8841 From owner-pine-info@cac.washington.edu Fri Oct 8 15:06:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08706; Fri, 8 Oct 93 15:06:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25153; Fri, 8 Oct 93 14:48:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25143; Fri, 8 Oct 93 14:48:32 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26038; Fri, 8 Oct 93 14:48:21 -0700 Date: Fri, 8 Oct 1993 14:48:16 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: How to set up pine read news only? To: Paul H Kramer Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Are you sure you want to do this with the current version of Pine? The current version of Pine can only read news. It cannot subscribe, unsubscribe or post messages. You still need another newsreader, like nn, to manage your subscriptions. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 8 Oct 1993, Paul H Kramer wrote: > At our university, a person sees a full-screen menu after s/he logs in. > Two of the items on the menu are worded M)ail and N)etwork News. If the > person presses M then pine is launched and if N is pressed then nn is > launched. If I substitute pine for nn, how can I keep pine from going > into the INBOX. I want pine when launched as a news reader to only look > at USENET newsgroups. I don't want the person to be able to switch into > their personal mailboxes when they originally started pine as a news reader. > > Second unrelated question, does anybody have a written document that they > would be willing to share with me that explains why pine would be a > better mail agent than elm for general users. I need something that I > can present that would make people see the light and switch to pine. > > Paul > -- > Paul H Kramer Computing Resource Center > (402) 472-5427 Room 120, 501 Building > pkramer@unl.edu University of Nebraska-Lincoln > > From owner-pine-info@cac.washington.edu Fri Oct 8 14:56:45 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08166; Fri, 8 Oct 93 14:56:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06945; Fri, 8 Oct 93 14:29:01 -0700 Received: by ListDist v0.2 for /usr/local/lib/pine-announce.cf Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06905; Fri, 8 Oct 93 14:28:17 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24711; Fri, 8 Oct 93 14:27:53 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25490; Fri, 8 Oct 93 14:27:32 -0700 Reply-To: Terry Gray Message-Id: Date: Fri, 8 Oct 1993 14:22:17 -0700 (PDT) From: Terry Gray To: Pine Announcement Distribution Subject: Pine 3.87 coming asap X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu The status of Pine 3.86 is that 3.87 (a "maintenance release maintenance release") will be coming very soon; hopefully within six hours. We still think we fixed more bugs in 3.86 than we introduced :), but there are several nasties that slipped by. For sure the following will be fixed: Leland Woodbury: crash caused by out-of-context FCC (Bezerk_open) Keith Christopher: Solaris crash when there is no feature-list Grant Weber: crash with [No Message Text Available] message Dan Larsen: crash on folder Rename We are also trying to verify whether or not some of the other Solaris problems are manifestations of one of those bugs. Apologies for the difficulties, and many thanks both to those who helped us find the bugs, and those who are being patient with them! -teg From owner-pine-info@cac.washington.edu Fri Oct 8 16:15:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11172; Fri, 8 Oct 93 16:15:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26333; Fri, 8 Oct 93 15:46:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26327; Fri, 8 Oct 93 15:46:51 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27267; Fri, 8 Oct 93 15:46:48 -0700 Date: Fri, 8 Oct 1993 15:15:32 -0700 (PDT) From: David L Miller Subject: Re: How to set up pine read news only? To: Joel Ness Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 8 Oct 1993, Joel Ness wrote: > > At our university, a person sees a full-screen menu > > after s/he logs in. Two of the items on the menu are > > worded M)ail and N)etwork News. If the person presses > > M then pine is launched and if N is pressed then nn is > > launched. If I substitute pine for nn, how can I keep > > pine from going into the INBOX. I want pine when > > launched as a news reader to only look at USENET > > newsgroups. I don't want the person to be able to > > switch into their personal mailboxes when they > > originally started pine as a news reader. > > You could launch pine with the '-nr' option. This puts it into a special anonymous mode specifically for newsreading. You could also use the '-p' or '-P' option to use an alternative to .pinerc or /usr/local/lib/pine.conf, respectively. > > Second unrelated question, does anybody have a written > > document that they would be willing to share with me > > that explains why pine would be a better mail agent > > than elm for general users. I need something that I > > can present that would make people see the light and > > switch to pine. > > Hmmm... About the best sales pitch we have found is a demo. There is a special demo account, pinedemo@demo.cac.washington.edu, that anyone can use to get a feel for Pine. > > Paul > > -- > > Paul H Kramer Computing Resource Center > > (402) 472-5427 Room 120, 501 Building > > pkramer@unl.edu University of Nebraska-Lincoln > > This is mostly a "me too" kind of reply in that we are also very interested in > other folk's experiences with using Pine as an interface to news. > Pine's news interface is at a very early stage of development right now. This is a very high priority topic for future releases though... > Our interest is because we want to make it easier to electronically distribute > general announcements and information on campus. We don't want to distribute the > same email message to many hundreds of mail boxes (inefficient and, to some > folk, annoying). News groups are the ideal vehicle, but the learning curve for > most Unix mail interfaces would prevent most folks from reading news the > conventional way. Eventually, people can use Mac and PC based news readers (and > mail programs) with nicer interfaces. But for now most use some type of vt100 > access to our central systems. > > If most of our folk are already logging in and running Pine to read mail, they'd > have no problems using the same Pine interface to read announcements. We've > started playing around with 3.85 and have found that we can have .pinerc file > point to specific newsgroups and, using the initial keystroke options, start > Pine right into an index screen of that mail group. > > What we'd like to know is what options/problems other folks have discovered for > similar types of services. Ideally, we'd like to present people with a front end > menu of commonly used Unix applications such as mail, announcements, scheduling, > and file management. Choosing mail gives you Pine, choosing announcements gives > you Pine pointed at a newsgroup (we assume we'd have to have this use a > different .pinerc for this). > Calendar and scheduling functions are on the list of requested features for Pine. I don't know when/if we will get to them, but they are on there. > Anyone else trying similar things yet? > _________________________ > Joel Ness > UMD Information Services > jness@ua.d.umn.edu > (218) 726-8841 > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA From owner-pine-info@cac.washington.edu Fri Oct 8 17:17:55 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13112; Fri, 8 Oct 93 17:17:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27611; Fri, 8 Oct 93 16:55:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from herald.usask.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27605; Fri, 8 Oct 93 16:55:18 -0700 Received: by herald.usask.ca (5.65/DEC-Ultrix/4.3) id AA28953; Fri, 8 Oct 1993 17:55:10 -0600 for pine-info@cac.washington.edu Date: Fri, 8 Oct 1993 17:50:12 -0600 (CST) From: Peter Scott U Sask Library Systems Dept Subject: Re: How to set up pine read news only? To: David L Miller Cc: Paul H Kramer , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 8 Oct 1993, David L Miller wrote: > Are you sure you want to do this with the current version of Pine? The > current version of Pine can only read news. It cannot subscribe, > unsubscribe or post messages. You still need another newsreader, like > nn, to manage your subscriptions. I've just made my subscribed newsgroups available via Pine. If I want to reply to a message I hit R for reply, delete the To:, and address it to: "newsgroup"@cs.utexas.edu, which then forwards my reply to all sites getting Usenet. The only thing to remember is to add dashes instead of periods to a newsgroup's name: i.e. alt-bbs-internet@cs.utexas.edu From owner-pine-info@cac.washington.edu Fri Oct 8 17:30:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13380; Fri, 8 Oct 93 17:30:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27847; Fri, 8 Oct 93 17:05:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27827; Fri, 8 Oct 93 17:04:59 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29209; Fri, 8 Oct 93 17:04:47 -0700 Date: Fri, 8 Oct 1993 17:03:54 -0700 (PDT) From: Steve Hubert Subject: Re: How to set up pine read news only? To: David L Miller Cc: Joel Ness , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > You could launch pine with the '-nr' option. This puts it into a special > anonymous mode specifically for newsreading. You could also use the '-p' > or '-P' option to use an alternative to .pinerc or > /usr/local/lib/pine.conf, respectively. Careful with this. This is mostly intended as a UW flag and is in a state of flux. Steve From owner-pine-info@cac.washington.edu Fri Oct 8 19:00:07 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15325; Fri, 8 Oct 93 19:00:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14882; Fri, 8 Oct 93 18:38:00 -0700 Received: by ListDist v0.2 for /usr/local/lib/pine-announce.cf Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14876; Fri, 8 Oct 93 18:37:58 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28756; Fri, 8 Oct 93 18:37:55 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00810; Fri, 8 Oct 93 18:37:54 -0700 Reply-To: Michael Seibel Message-Id: Date: Fri, 8 Oct 1993 18:31:25 -0700 (PDT) From: Michael Seibel To: Pine Announcement Distribution Subject: Pine and PC-Pine 3.87 now available X-Owner: pine-announce-request@cac.washington.edu X-To: Pine Announcement Distribution This version fixes several particularly unpleasant bugs found in Pine versions 3.86 and earlier. The bug fix list is fairly short, but should make Pine quite a bit more stable and a little easier to use. The list includes the following reported bugs: -crash in bezerk_open caused by out-of-context FCC (Leland Woodbury) -crash on Solaris with missing feature list (Keith Christopher) -crash with [No Message Text Available] message (Grant Weber) -crash on folder Rename (Dan Larsen) -crash with "Bad msgno in mail_fetchstructure" (Les Pennington) -need one more NL before included text if NO sig file (Jeannine Senechal) -makefile.sgi repairs (Mike Brudenell) Thanks to all (including those not listed above!) who helped by reporting and tracking down these bugs. Apologies for any problems or inconvenience they may have caused! The Pine Team From owner-pine-info@cac.washington.edu Sat Oct 9 03:59:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22904; Sat, 9 Oct 93 03:59:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02139; Sat, 9 Oct 93 03:50:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pp.dundee.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02133; Sat, 9 Oct 93 03:50:42 -0700 Received: from dux.dundee.ac.uk by pp.dundee.ac.uk with SMTP (PP) id <28307-0@pp.dundee.ac.uk>; Sat, 9 Oct 1993 11:33:20 +0100 Received: by dux.dundee.ac.uk (5.0/SMI-SVR4-S2000) id AA01452; Sat, 9 Oct 93 11:49:03 BST Date: Sat, 9 Oct 1993 11:45:12 +0100 (BST) From: "K.M. Lovell Information Technology Services ext 4" Subject: Re: Pine 3.86 core dump with solaris 2.2 - ok with 3.85 To: Steve Hubert Cc: David L Miller , Barry Cornelius , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 835 -------------------------------------------------------------- From: K.M.Lovell , Information Technology Services, University of Dundee, Park Place , Dundee DD1 4HN , UK Email: kmlovell@dux.dundee.ac.uk Tel : +44 382 307136 Fax : +44 382 28649 On Fri, 8 Oct 1993, Steve Hubert wrote: > And a feature of no-something is allowed in 3.86 and would effectively be > a no-op. > > On Fri, 8 Oct 1993, David L Miller wrote: > > > > > Check to make sure that you have something listed in the feature-list > > variable in your .pinerc. An empty feature-list triggers a bug on > > Solaris. This will be fixed in Pine 3.87. > Yes. It was indeed the lack of a feature list in .pinerc that caused the problem. After I set the right hand side to no- I was able to use pine 3.86 without a problem. Thank you From owner-pine-info@cac.washington.edu Sat Oct 9 09:49:52 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26628; Sat, 9 Oct 93 09:49:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04167; Sat, 9 Oct 93 09:42:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04161; Sat, 9 Oct 93 09:42:35 -0700 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <07278-0@omega.qmw.ac.uk>; Sat, 9 Oct 1993 17:38:09 +0100 Date: Sat, 9 Oct 1993 17:40:28 +0100 (BST) From: Laurie Cuthbert Subject: Re: Reply To All Recipients Problem To: Steve Hubert Cc: Barry Cornelius , Erik Lawaetz , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would support this idea - Internally to the dept my mail is generated as laurie@elec.qmw.ac.uk, but changed to L.G.Cuthbert@qmw.ac.uk at the site mailer. Replying to external mail therefore always includes my own name on the list when I choose the "all recipients" option with pine. Regards Laurie Cuthbert On Fri, 8 Oct 1993, Steve Hubert wrote: > The alternatives variable sounds like something we could do. (We have to > evaluate the idea and think about it and blah, blah, blah first, of > course.) To the best of my recollection, you are the first two people > who've ever requested such a feature, but now that you mention it, it > does seem like a feature that many mailers have. Thanks for the suggestion. > > Steve Hubert > Networks and Distributed Computing, Univ. of Washington, Seattle > > > From owner-pine-info@cac.washington.edu Sun Oct 10 03:47:17 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10249; Sun, 10 Oct 93 03:47:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10227; Sun, 10 Oct 93 03:37:28 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from discus.technion.ac.il by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10221; Sun, 10 Oct 93 03:37:12 -0700 Received: from localhost (oved@localhost) by discus.technion.ac.il (8.5/8.5) id MAA26653; Sun, 10 Oct 1993 12:37:05 +0200 Date: Sun, 10 Oct 1993 12:23:35 +0200 (EET) From: Oved Ben-Aroya Subject: Re: Reply To All Recipients Problem - "alternatives" variable To: Steve Hubert Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 8 Oct 1993, Steve Hubert wrote: > The alternatives variable sounds like something we could do. (We have to > evaluate the idea and think about it and blah, blah, blah first, of > course.) To the best of my recollection, you are the first two people > who've ever requested such a feature, but now that you mention it, it > does seem like a feature that many mailers have. Thanks for the suggestion. BSD mail, elm and mush all have this variable. > > Steve Hubert > Networks and Distributed Computing, Univ. of Washington, Seattle > > -- \Oved From owner-pine-info@cac.washington.edu Mon Oct 11 01:41:45 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26537; Mon, 11 Oct 93 01:41:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07112; Mon, 11 Oct 93 01:23:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07104; Mon, 11 Oct 93 01:23:40 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #88) id m0omIXa-00003JC; Mon, 11 Oct 93 09:23 BST Date: Mon, 11 Oct 1993 09:22:34 +0100 (BST) From: Philip Hazel Subject: Re: Reply To All Recipients Problem To: Laurie Cuthbert Cc: Steve Hubert , Barry Cornelius , Erik Lawaetz , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I would support this idea - So would I! It's one of the few Elm features I miss in Pine. Regards, Philip > > The alternatives variable sounds like something we could do. (We have to > > evaluate the idea and think about it and blah, blah, blah first, of > > course.) To the best of my recollection, you are the first two people > > who've ever requested such a feature, but now that you mention it, it > > does seem like a feature that many mailers have. Thanks for the suggestion. -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Mon Oct 11 02:01:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27102; Mon, 11 Oct 93 02:01:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18072; Mon, 11 Oct 93 01:49:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dxmint.cern.ch by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18066; Mon, 11 Oct 93 01:49:28 -0700 Received: from dxcoms.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA06194; Mon, 11 Oct 1993 09:49:25 +0100 Received: by dxcoms.cern.ch (5.65/DEC-Ultrix/4.3) id AA00805; Mon, 11 Oct 1993 09:49:24 +0100 From: dimou@dxcoms.cern.ch (M. Dimou-Zacharova) Message-Id: <9310110849.AA00805@dxcoms.cern.ch> Subject: Re: Reply To All Recipients Problem To: hubert@cac.washington.edu (Steve Hubert) Date: Mon, 11 Oct 1993 09:49:23 +0100 (MET) Cc: Barry.Cornelius@durham.ac.uk, Erik.Lawaetz@uni-c.dk, pine-info@cac.washington.edu In-Reply-To: from "Steve Hubert" at Oct 8, 93 11:10:20 am Reply-To: Maria.Dimou@cern.ch X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1526 > > The alternatives variable sounds like something we could do. (We have to > evaluate the idea and think about it and blah, blah, blah first, of > course.) To the best of my recollection, you are the first two people > who've ever requested such a feature, but now that you mention it, it > does seem like a feature that many mailers have. Thanks for the suggestion. > > Steve Hubert > Networks and Distributed Computing, Univ. of Washington, Seattle > If I may say I had sent a similar request last July where I wrote: >>To: pine-bugs@cac.washington.edu >>Date: Fri, 9 Jul 1993 12:15:55 +0200 (MET DST) >>Reply-To: maria.dimou@cern.ch >> >>I really like the 'use-only-domain-name' feature. This however can make >>the username@domainonly unrepliable if the directory service which resolves >>such addresses is based on personalname@domainonly. >>e.g. for user Brian Carpenter with computer registered username 'brian' >>the address brian@dxcern.cern.ch is valid >>as well as the address carpenter@cern.ch but not brian@cern.ch. I had gotten the following answer by David Miller then but I still beg for a solution to this problem because my users are really agressive on this: >>The use-only-domain feature really assumes that the username is >>consistent across the domain. Pine 4.0 will probably allow you to add a >>reply-to header, but other than that, I don't know any way to resolve >>your problem at the Pine level. Thanks very much in advance for considering this -maria From owner-pine-info@cac.washington.edu Mon Oct 11 06:27:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01471; Mon, 11 Oct 93 06:27:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19624; Mon, 11 Oct 93 06:10:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19618; Mon, 11 Oct 93 06:10:43 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA02575; Mon, 11 Oct 93 08:10:42 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA18803; Mon, 11 Oct 93 21:07:47 +0800 Date: Mon, 11 Oct 1993 20:58:08 +0800 (TPE) From: Ed Greshko Subject: pine release methods To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, When pine went from 3.07 to 3.85 it was released as a compressed tar file of over 2M bytes. When 3.86 was released it also came out as a compressed tar of about the same length. I'm assuming that when 3.87 is released it will be much the same. Well, I'm not in the USA and my connection is an expensive X.25 connection. So, for incremental releases, I'm wondering if pine updates can't be released as diffs that can be used as input to the "patches" utility? This would make the "free" software I obtain much less expensive. I can't believe I'm the only person in such a situation. Regards, Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Mon Oct 11 07:31:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02527; Mon, 11 Oct 93 07:31:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20136; Mon, 11 Oct 93 07:10:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20130; Mon, 11 Oct 93 07:10:41 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA02743; Mon, 11 Oct 93 09:10:39 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA18969; Mon, 11 Oct 93 21:43:08 +0800 Date: Mon, 11 Oct 1993 21:41:10 +0800 (TPE) From: Ed Greshko Subject: Simple quick question.... To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII ...that I should know the answer.... How does one change the location of the system wide config file from /usr/local/lib/pine.conf to something else? Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Mon Oct 11 09:59:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07674; Mon, 11 Oct 93 09:59:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23190; Mon, 11 Oct 93 09:42:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23182; Mon, 11 Oct 93 09:41:57 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01892; Mon, 11 Oct 93 09:41:36 -0700 Date: Mon, 11 Oct 1993 09:40:09 -0700 (PDT) From: Steve Hubert Subject: Re: Simple quick question.... To: Ed Greshko Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There is a macro SYSTEM_PINERC in the pine/osdep/os-xxx.h file that is set to the name of the file (if you want to change it for everyone). If you are talking about just changing it for a single user there is a -P command line arg to do that. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Mon, 11 Oct 1993, Ed Greshko wrote: > > ...that I should know the answer.... > > How does one change the location of the system wide config file > from /usr/local/lib/pine.conf to something else? > > Edward M. Greshko Control Data Taiwan > Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 > FAX : +886-2-712-9197 Taipei, Taiwan R.O.C > > From owner-pine-info@cac.washington.edu Mon Oct 11 10:04:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07840; Mon, 11 Oct 93 10:04:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22724; Mon, 11 Oct 93 09:21:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from epoch.geol.scarolina.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22688; Mon, 11 Oct 93 09:20:46 -0700 Received: from tbone.biol.scarolina.edu by epoch.geol.scarolina.edu (4.1/1.34) id AA05564; Mon, 11 Oct 93 12:21:58 EDT Received: by tbone.biol.scarolina.edu (4.1/SMI-4.1T3-2) id AA28930; Mon, 11 Oct 93 12:20:36 EDT Date: Mon, 11 Oct 93 12:20:36 EDT From: dean2@tbone.biol.scarolina.edu (Dean Pentcheff) Message-Id: <9310111620.AA28930@tbone.biol.scarolina.edu> To: pine-info@cac.washington.edu Subject: Pine weirdness Looking for help in (I hope) the right place... I've got a bizarre problem with the new(er) versions of Pine. It cropped up with both post-3.07 versions I've tried (most recently with 3.87), so I've reverted to 3.07 (which works fine). My system is a Sun IPC running SunOS 4.1.1. I compiled using gcc 2.3.3 (by changing the CC=cc to CC=gcc in the build script). It makes no difference whether the DEBUG option is used or disabled. I compile pine, install it, and change its permissions and ownership to: -rwxr-xr-x 1 root staff 2187264 Oct 10 17:18 /usr/local/bin/pine When I run it, all is well. Fine. But if any other user tries it, it fails. For example, the user "server" tries it (in real life this is a pseudo-user for a mailing list manager): [tbone]% pine Bug in Pine detected: "Received abort signal". Exiting pine. Arithmetic exception [tbone]% The debug file produced is appended at the end. Any ideas on what's up? Thanks! -Dean -- N. Dean Pentcheff Biological Sciences, Univ. of South Carolina, Columbia SC 29208 (803-777-8998) Internet addresses: pentcheff@pascal.acm.org or dean2@tbone.biol.scarolina.edu ===== Sample DEBUG File ===== Debug output of the Pine program (at debug level 2). Version 3.87 Sun Oct 10 17:23:17 1993 reading_pinerc "/usr/local/lib/pine.conf" Read 6080 characters pinerc : /usr/local/l : folder-collections : "Mail Mail" pinerc : /usr/local/l : default-fcc : "outgoing" pinerc : /usr/local/l : mail-directory : "Mail" pinerc : /usr/local/l : feature-list : "old-growth" pinerc : /usr/local/l : editor : "vi" pinerc : /usr/local/l : image-viewer : "echo 'Click right mouse button on image for image menu' ; xv" pinerc : /usr/local/l : bugs-nickname : "mail-bugs" pinerc : /usr/local/l : bugs-fullname : "For any mail system problems" pinerc : /usr/local/l : bugs-address : "root@tbone.biol.scarolina.edu" reading_pinerc "/home/server/.pinerc" Read 7772 characters pinerc : /home/server : last-version-used : "3.87" personal-name : user-id : user-domain : smtp-server : inbox-path : inbox inbox incoming-folders : folder-collection : Mail Mail Mail Mail news-collections : default-fcc : outgoing outgoing mail-directory : Mail Mail read-message-fold : signature-file : .signature .signature address-book : .addressbook .addressbook feature-list : old-growth old-growth initial-keystroke : saved-msg-name-ru : default-folder default-folder sort-key : arrival arrival character-set : editor : vi vi image-viewer : echo 'Click right echo 'Click right use-only-domain-n : no no printer : attached-to-ansi attached-to-ansi personal-print-co : standard-printer : lpr lpr last-time-prune-q : last-version-used : 3.87 3.87 bugs-nickname : mail-bugs mail-bugs bugs-fullname : For any mail syste For any mail syste bugs-address : root@tbone.biol.sc root@tbone.biol.sc elm-style-save : no no header-in-reply : no no feature-level : sapling sapling old-style-reply : no no compose-mime : show-all-characte : save-by-sender : no no Userid: server Fullname: "Listserv Server" User domain name being used "" Local Domain name being used "biol.scarolina.edu" Host name being used "tbone.biol.scarolina.edu" Mail Domain name being used "tbone.biol.scarolina.edu" new win size -----<38 80>------ Terminal type: xterm About to open folder "INBOX" inbox: "INBOX" about to end_tty_driver Pine Panic: Received abort signal From owner-pine-info@cac.washington.edu Mon Oct 11 12:55:34 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14341; Mon, 11 Oct 93 12:55:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10015; Mon, 11 Oct 93 12:38:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from vanbc.wimsey.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09997; Mon, 11 Oct 93 12:36:45 -0700 Received: by vanbc.wimsey.com (Smail3.1.28.1) id m0omT2W-00015WC; Mon, 11 Oct 93 12:36 PDT Message-Id: From: sl@wimsey.com (Stuart Lynne) Subject: SCO Pine? To: pine-info@cac.washington.edu Date: Mon, 11 Oct 1993 12:36:16 -0700 (PDT) X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 552 Anyone out there doing any work on Pine port for SCO? The latest has makefiles etc to get through c-client, imapd and pico. But nothing for pine. I hacked up enough to get pine compiling and running. Would like to compare notes. -- Stuart Lynne ............ UNIX Facsimile Software 800-457-4736 604-936-8649(voice) 604-937-4768(fax) 604-937-5311(pep) 604-937-7411(v32b) PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z From owner-pine-info@cac.washington.edu Mon Oct 11 14:03:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16664; Mon, 11 Oct 93 14:03:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10391; Mon, 11 Oct 93 13:46:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ramsey.cs.laurentian.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10385; Mon, 11 Oct 93 13:46:38 -0700 Received: by ramsey.cs.laurentian.ca (5.65/DEC-Ultrix/4.3) id AA23850; Mon, 11 Oct 1993 16:46:26 -0400 Received: by thunderbird.auc.laurentian.ca (5.4.2/200.1.1.4) id AA11115; Mon, 11 Oct 1993 16:44:37 -0400 Date: Mon, 11 Oct 1993 16:40:59 -0400 (EDT) From: James Trainor Subject: DG/UX To: pine-info@cac.washington.edu Cc: Project Assistant Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have no ported pine3.87 to run on DG/UX. If anyone else has done similar work i would like to compare notes. Thanks David for the srv4 hint, you were correct that the amount of work involved could hardly be called a port. The 3.07 port i did was based on the ptx port. -jEt- From owner-pine-info@cac.washington.edu Tue Oct 12 02:27:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03354; Tue, 12 Oct 93 02:27:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08126; Tue, 12 Oct 93 02:12:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun2.nsfnet-relay.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08120; Tue, 12 Oct 93 02:12:08 -0700 Via: uk.ac.sheffield; Tue, 12 Oct 1993 10:10:08 +0100 Received: from sunc.sheffield.ac.uk by pp.shef.ac.uk with SMTP (PP) id <25602-0@pp.shef.ac.uk>; Tue, 12 Oct 1993 10:08:42 +0100 From: Chris Martin Date: Tue, 12 Oct 93 10:09:27 BST Message-Id: <21189.9310120909@sunc.sheffield.ac.uk> Received: from ss3.ac.uk by sunc.sheffield.ac.uk; Tue, 12 Oct 93 10:09:27 BST Received: by ss3.ac.uk (4.1/SMI-4.1) id AA12035; Tue, 12 Oct 93 10:09:26 BST To: pine-info@cac.washington.edu Subject: Compilation error for v3.87 on SGI IRIX 5.0.1 build says: make args are "CC=cc" Making c-client library and mtest rm -f osdep.h ln os_sgi.h osdep.h cc -O -cckr -Wf,-XNh2000 -Dconst= -c mtest.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c mail.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c bezerk.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c tenex2.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c mbox.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c mh.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c imap2.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c news.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c nntpclient.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c phile.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c dummy.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c smtp.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c nntp.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c rfc822.c cc -O -cckr -Wf,-XNh2000 -Dconst= -c misc.c cc -O -cckr -Wf,-XNh2000 -Dconst= -DRSH=\"rsh\" -DRSHPATH=\"/usr/bsd/rsh \" -c os_sgi.c cfe: Error: os_sgi.c, line 90: '_tzname' undefined; reoccurrences will not be re To correct this I added #include to the list of includes in (pine)/imap/non-ANSI/c-client/os_sgi.c and changed _tzname to tzname. The diffs are: *** os_sgi.c Tue Oct 12 09:52:43 1993 --- os_sgi.c-orig Mon Oct 4 04:29:26 1993 *************** *** 52,58 **** #include "osdep.h" #include - #include #include #include #include --- 52,57 ---- *************** *** 88,94 **** sprintf (date,"%s, %d %s %d %02d:%02d:%02d %+03d%02d (%s)", days[t->tm_wday],t->tm_mday,months[t->tm_mon],t->tm_year+1900, t->tm_hour,t->tm_min,t->tm_sec,zone/60,abs(zone)%60, ! tzname[t->tm_isdst ? 1 : 0]); } /* Get a block of free storage --- 87,93 ---- sprintf (date,"%s, %d %s %d %02d:%02d:%02d %+03d%02d (%s)", days[t->tm_wday],t->tm_mday,months[t->tm_mon],t->tm_year+1900, t->tm_hour,t->tm_min,t->tm_sec,zone/60,abs(zone)%60, ! _tzname[t->tm_isdst ? 1 : 0]); } /* Get a block of free storage =========================================================================== From owner-pine-info@cac.washington.edu Tue Oct 12 03:03:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04010; Tue, 12 Oct 93 03:03:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08289; Tue, 12 Oct 93 02:44:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun2.nsfnet-relay.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08283; Tue, 12 Oct 93 02:44:03 -0700 Via: uk.ac.sheffield; Tue, 12 Oct 1993 10:39:27 +0100 Received: from sunc.sheffield.ac.uk by pp.shef.ac.uk with SMTP (PP) id <26287-0@pp.shef.ac.uk>; Tue, 12 Oct 1993 10:34:40 +0100 From: Chris Martin Date: Tue, 12 Oct 93 10:35:30 BST Message-Id: <23973.9310120935@sunc.sheffield.ac.uk> Received: from ss3.ac.uk by sunc.sheffield.ac.uk; Tue, 12 Oct 93 10:35:30 BST Received: by ss3.ac.uk (4.1/SMI-4.1) id AA12101; Tue, 12 Oct 93 10:35:29 BST To: pine-info@cac.washington.edu Subject: Segmentation fault on pine 3.87 under SGI IRIX 5.0.1 After fixing the compilation error as in my previous mail, pine now develops a segmentation fault when run. I'm sorry, I don't now how to use the SGI tools to examine a dump ... There is the following message in the build log: Making Pine. echo "char datestamp[]="\"`date`\"";" > date.c cc -c -cckr -DSGI -O -o date.o date.c cc -cckr -DSGI -O -o pine addrbook.o addrutil.o adrbklib.o args.o con text.o filter.o folder.o help.o helptext.o imap.o init.o mailcmd.o mailindx.o mailview.o newmail.o other.o pine.o print.o reply.o screen.o send.o signals.o s tatus.o strings.o ttyin.o ttyout.o os.o date.o ../pico/libpico.a ../c-client/c-c lient.a -ltermlib -lsun ld: termname: common but defined as text in a shared object I hope this helps. From owner-pine-info@cac.washington.edu Tue Oct 12 08:22:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10172; Tue, 12 Oct 93 08:22:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10964; Tue, 12 Oct 93 07:56:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from psi.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10958; Tue, 12 Oct 93 07:56:35 -0700 Received: from uu4.psi.com by psi.com (4.1/2.1-PSI/PSINet) id AA04102; Tue, 12 Oct 93 10:56:28 EDT Received: by uu4.psi.com (5.65b/4.0.071791-PSI/PSINet) via UUCP; id AA26320 for ; Tue, 12 Oct 93 10:43:44 -0400 Date: Mon, 11 Oct 1993 16:07:33 -0700 (PDT) From: "Andy C. McNiece" Subject: Use of alternate speller To: pine-info%cac.washington.edu@psi.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I am attempting to use ispell as an alternate speller. Could someone provide me with the syntax to use. Simply defining ispell as the speller in osdep.h is not working correctly. Upon invoking the spell checker from within pico, the screen fills with the ispell help message. From owner-pine-info@cac.washington.edu Tue Oct 12 08:48:17 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11213; Tue, 12 Oct 93 08:48:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11351; Tue, 12 Oct 93 08:15:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ib.rl.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11341; Tue, 12 Oct 93 08:15:28 -0700 Received: from letterbox.rl.ac.uk by ib.rl.ac.uk (IBM VM SMTP V2R1) with TCP; Tue, 12 Oct 93 16:14:58 BST Received: from adam2.bnsc.rl.ac.uk by letterbox.rl.ac.uk with SMTP (PP) id <04120-0@letterbox.rl.ac.uk>; Tue, 12 Oct 1993 16:15:49 +0100 Received: by adam2.bnsc.rl.ac.uk (5.57/Ultrix3.0-C) id AA24131; Tue, 12 Oct 93 16:15:01 +0100 Date: Tue, 12 Oct 1993 15:39:05 +0100 (BST) From: Starlink Software Librarian Subject: Pine 3.85/3.87 problem with Solaris To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have built Pine 3.85, (3.86) and 3.87 for our multi-host-type system, and mostly it works quite well. We have the following setup: 3 x DECstation/Ultrix 4.2a 1 x DECstation/Ultrix 4.3 1 x Sun Sparc/SunOS 4.1.2 2 x Sun Sparc/Solaris 2.2 1 x DEC Alpha/OSF 1.2 2 x HP 9000/HPUX 8.07 Mail lives on the Sun running SunOS 4.1.2. It exports its /var/spool/mail to the other machines in the group management domain. The other machines mount the directory over their own mail directory usinh the NFS automounter. The sun has the following in its /etc/exports: /var/spool/mail -rw=client1:client2:etc (giving the names of our village of machines.) All the user accounts reside mainly on disks NFS automounted around the system, chiefly on disks attached to the DECstations. The problem is this: For the Solaris machines, the user cannot access any of his mail folders, including INBOX. Pine locks up and refuses to do anything; kill -9 being the only way to dispatch pine AND its parent shell. The lock occurs immediately the access is tried: viewing folders or at send time after composing and mailing a message. The message itself is mailed and arrive ok at the other end (a VAX). Pine appears to sleep and not wake up. Only one user is able to use Pine on Solaris and his home directory is on a disk served by one of the Solaris machines. The rest of us are stuck, resorting to the other machines for mail work. Has anyone seen this sort of behaviour? I can supply debug logs and system call logs. >From reading the pine-info list, I gather using imap may be the only way out, but I'd rather not let Pine get too complicated and inflict imap on our users when we have such a tightly coupled system. We have ~1600 users at ~25 sites around the UK waiting for Pine and most or the sites using similarly coupled systems, I'm hopefull that this is a local system problem. Cheers, Martin. -- --------------------------------------------------------------------------- Martin Bly, | Internet: ussc@star.rl.ac.uk Starlink Software Librarian | Janet: ussc@uk.ac.rl.star Starlink, RAL, Chilton, DIDCOT | DECNET: RLVAD::USSC (19457) OXON, OX11 0QX, United Kingdom. | Tel: +44 (0)235 445363 --------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Tue Oct 12 09:22:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12675; Tue, 12 Oct 93 09:22:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12085; Tue, 12 Oct 93 08:50:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12077; Tue, 12 Oct 93 08:50:14 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18701; Tue, 12 Oct 93 08:49:52 -0700 Date: Tue, 12 Oct 1993 08:44:05 -0700 (PDT) From: David L Miller Subject: Re: Text as attachment is Base64-encoded? To: Ng Pheng Siong Cc: pine-info@cac.washington.edu In-Reply-To: <9310120220.AA12103@mx2.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, this is the correct behavior. We base this on the requirement that an extracted attachment be identical to the original. Only BASE64 encoding guarantees this. Some would argue that Quoted Printable would be better for text, but it does not *guarantee* complete preservation of an attachment. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 12 Oct 1993, Ng Pheng Siong wrote: > Sorry if this is old hat - I've only begun using Pine since 3.85. > > When I send a text file as an attachment, it says content type is > text/plain; charset=us-ascii, but then the next line says content > transfer encoding is base64. And the text file is encoded. > > Is it correct behaviour? > > Cheers. > > - PS > -- > Ng Pheng Siong * ngps@np.ac.sg * npngps@solomon.technet.sg > Computer Centre, Ngee Ann Polytechnic, Singapore From owner-pine-info@cac.washington.edu Tue Oct 12 10:38:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16668; Tue, 12 Oct 93 10:38:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15732; Tue, 12 Oct 93 10:02:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from chinook.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15723; Tue, 12 Oct 93 10:02:33 -0700 Received: by halcyon.com id AA02205 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Tue, 12 Oct 1993 10:02:30 -0700 From: Ralph Sims Message-Id: <199310121702.AA02205@halcyon.com> Subject: Unreadable messages. (fwd) To: pine-info@cac.washington.edu Date: Tue, 12 Oct 1993 10:02:26 -0700 (PDT) X-Mailer: ELM [version 2.4 PL13] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1898 Forwarded message: >From dpalm Mon Oct 11 22:38:02 1993 Date: Tue, 12 Oct 1993 05:38:02 -0700 (PDT) From: Douglas Palm Subject: Unreadable messages. (fwd) To: Ralph Sims Cc: Network Operator Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ralph, Ever since the PINE mail agent was updated I've had problems with BASE64 coding. Please see the attached reply from our Bangkok office. The problem is the same for Compuserve users and Internet users alike. What is BASE64 and how can I get PINE to work as it did before the upgrade? P.S. I've already reported this to the NOC with no reply. ---------- Forwarded message ---------- Date: 10 Oct 93 00:36:59 EDT From: Tony Stewart <100236.3461@compuserve.com> To: "Doug Palm (PATH)" Subject: Unreadable messages from you. Doug, Your last three messages have been unreadable. I cannot decode them with any of my utilities. I suspect that your MIME mailer is using an application specific encoding scheme. Here are the first few lines of your last message. Try using standard UUENCODE or ascii. Date: Sat, 2 Oct 1993 21:08:40 -0700 (PDT) From: Douglas Palm Subject: Re: 8lb Baby Girl To: Tony Stewart <100236.3461@compuserve.com> In-Reply-To: <931001231235_100236.3461_CHE70-1@CompuServe.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: BASE64 QnJpZWFubmEgTHltYW4gUGFsbS4NCkJvcm4gNjoxMiBhLm0uIFBULCBTZXB0 ZW1iZXIgMzAsIDE5OTMuDQpXdDogOGxicyAxLzIgb3ouICBMbjogMjAiDQoK V2UncmUgYWxsIGRvaW5nIHdlbGwgaGVyZSBhdCBob21lLiAgSSdsbCBiZSBi YWNrIGluIGFjdGlvbiBuZXh0IHdlZWsgYnV0IAp3aWxsIHRyeSB0byBtYWlu dGFpbiBteSBtYWlsYm94IHdoZW4gcG9zc2libGUgKGEgbG9zaW5nIGJhdHRs From owner-pine-info@cac.washington.edu Tue Oct 12 10:41:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16788; Tue, 12 Oct 93 10:41:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15800; Tue, 12 Oct 93 10:12:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from log.css.itd.umich.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15794; Tue, 12 Oct 93 10:12:14 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA10999; Tue, 12 Oct 93 13:12:08 -0400 Date: Tue, 12 Oct 1993 13:07:12 -0400 (EDT) From: Mike Kuniavsky Subject: Re: Use of alternate speller To: "Andy C. McNiece" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 11 Oct 1993, Andy C. McNiece wrote: > I am attempting to use ispell as an alternate speller. Could someone > provide me with the syntax to use. Simply defining ispell as the speller > in osdep.h is not working correctly. Upon invoking the spell checker > from within pico, the screen fills with the ispell help message. Although I wish there was a cleaner way to do this (feature suggestion?! ;-) I've found the defining ispell as the alternate editor in either individual .pinercs or in the global pine.conf works quite nicely. It would be nice if an alternate speller could be defined, so one could have both it and an alternate editor, but the current system works fine for most people. Mike Kuniavsky ITD/US UNIX Support mikek@umich.edu (313)764-1178 From owner-pine-info@cac.washington.edu Tue Oct 12 10:53:54 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17250; Tue, 12 Oct 93 10:53:54 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15823; Tue, 12 Oct 93 10:17:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15817; Tue, 12 Oct 93 10:16:45 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA05627 (5.65b/CWI-3.3); Tue, 12 Oct 1993 18:16:39 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05316; Tue, 12 Oct 93 17:04:20 GMT (MET) Message-Id: <9310121704.AA05316@wilg.bull.nl> To: pine-info@cac.washington.edu Subject: Printer setup screen declared twice (pine.c / other.c) Date: Tue, 12 Oct 93 18:04:18 MET From: Jos Vos Because I didn't like the text in the printer setup screen (only talking about "lpr" and "PRINTER", and not about "lp" and "LPDEST"), I looked in the code. There I saw the "redraw_printer_select()" function declared twice: in pine/pine.c and pine/other.c. The one in other.c contained the text I'ld like to have. But .... is the function from other.c ever called? I *always* get the text from pine.c. And... I didn't get a link error.... I'm confused. -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Tue Oct 12 11:07:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18012; Tue, 12 Oct 93 11:07:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14555; Tue, 12 Oct 93 10:38:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from psi.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14545; Tue, 12 Oct 93 10:37:50 -0700 Received: from instruction.CS.ORST.EDU ([128.193.164.25]) by psi.com (4.1/2.1-PSI/PSINet) id AA07432; Tue, 12 Oct 93 13:37:34 EDT Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA11021; Tue, 12 Oct 93 10:38:18 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA24796; Tue, 12 Oct 93 10:40:21 -0700 Date: Tue, 12 Oct 1993 10:39:40 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Use of alternate speller To: "Andy C. McNiece" Cc: pine-info%cac.washington.edu@psi.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 11 Oct 1993, Andy C. McNiece wrote: > > I am attempting to use ispell as an alternate speller. Could someone > provide me with the syntax to use. Simply defining ispell as the speller > in osdep.h is not working correctly. Upon invoking the spell checker > from within pico, the screen fills with the ispell help message. > > I believe when trn (Threaded Read News) invokes ispell, it uses: ispell -x But I'm not sure...Does this help? Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Tue Oct 12 12:01:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20261; Tue, 12 Oct 93 12:01:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15693; Tue, 12 Oct 93 11:31:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nexus.yorku.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15687; Tue, 12 Oct 93 11:31:43 -0700 Received: from vortex.yorku.ca ([130.63.232.15]) by nexus.yorku.ca with SMTP id <9225>; Tue, 12 Oct 1993 14:31:32 -0400 Received: by vortex.yorku.ca (4.1/SMI-4.1) id AA08959; Tue, 12 Oct 93 14:36:34 EDT Date: Tue, 12 Oct 1993 14:35:03 -0400 From: Ian Lumb Subject: Re: Use of alternate speller To: PINE INFO In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > It would be nice if an alternate speller could be defined, so one could > have both it and an alternate editor, but the current system works fine > for most people. I would also like to see an alternate speller added as a feature, as I quite often use an alternate editor which I do want to give up for a spell checker. Ian. -- Ian Lumb Internet: Earth & Atmospheric Science, York University North York, Ontario M3J 1P3, CANADA Voice: (416) 736-5245; Fax: (416) 736-5817 From owner-pine-info@cac.washington.edu Tue Oct 12 14:01:57 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24083; Tue, 12 Oct 93 14:01:57 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18074; Tue, 12 Oct 93 13:41:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18067; Tue, 12 Oct 93 13:41:36 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24862; Tue, 12 Oct 93 13:41:19 -0700 Date: Tue, 12 Oct 1993 13:38:49 -0700 (PDT) From: David L Miller Subject: Re: Use of alternate speller To: Ian Lumb Cc: PINE INFO In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can define an alternate spelling checker by setting the SPELL environment variable. Note that whatever you define here must take the text input on stdin and write out a list of misspelled words on stdout. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 12 Oct 1993, Ian Lumb wrote: > > It would be nice if an alternate speller could be defined, so one could > > have both it and an alternate editor, but the current system works fine > > for most people. > > I would also like to see an alternate speller added as a feature, as I > quite often use an alternate editor which I do want to give up for a > spell checker. > > Ian. > > > > -- > Ian Lumb Internet: > Earth & Atmospheric Science, York University > North York, Ontario M3J 1P3, CANADA > Voice: (416) 736-5245; Fax: (416) 736-5817 > > From owner-pine-info@cac.washington.edu Wed Oct 13 03:59:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13197; Wed, 13 Oct 93 03:59:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25880; Wed, 13 Oct 93 00:46:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25868; Wed, 13 Oct 93 00:45:25 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <19667-0@dummy1.dur.ac.uk>; Wed, 13 Oct 1993 08:45:06 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Wed, 13 Oct 93 08:45:05 BST Date: Wed, 13 Oct 1993 08:29:58 +0100 (BST) From: Barry Cornelius Subject: Re: Unreadable messages. (fwd) To: Ralph Sims Cc: pine-info@cac.washington.edu In-Reply-To: <199310121702.AA02205@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 12 Oct 1993, Ralph Sims wrote: > Forwarded message: > From: Douglas Palm > Ralph, > Ever since the PINE mail agent was updated I've had problems with BASE64 > coding. Please see the attached reply from our Bangkok office. The > problem is the same for Compuserve users and Internet users alike. What > is BASE64 and how can I get PINE to work as it did before the upgrade? > [stuff deleted] I have notcied that, for some messages, with full headers switched on, the BASE64 "gibberish" comes out, whereas with full headers off, "normal text" comes out. To prove that I was able to read the BASE64 gibberish in your message, I put the message with Subject field "Re; 8lb Baby Girl" into a folder, switched full headers off, and found that the baby girl was born at 6.12am on September 30th. [Congratulations!] I have also noticed that the presence of lines ending with carriage-return following by line-feed instead of just line-feed causes the message to be classified as BASE64 in the Unix version of Pine. I dunno if that helps. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Wed Oct 13 14:21:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01925; Wed, 13 Oct 93 14:21:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05923; Wed, 13 Oct 93 13:58:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05917; Wed, 13 Oct 93 13:58:11 -0700 Message-Id: <9310132058.AA05917@mx1.cac.washington.edu> Received: from UWAVM.U.WASHINGTON.EDU by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with BSMTP id 8452; Wed, 13 Oct 93 13:57:34 PDT Received: from ETSU.EAST-TENN-ST.EDU by UWAVM.U.WASHINGTON.EDU (Mailer R2.10 ptf008) with BSMTP id 1040; Wed, 13 Oct 93 13:57:33 PDT Received: from ETSU (NJE origin CMS2@ETSU) by ETSU.EAST-TENN-ST.EDU (LMail V1.1d/1.7f) with BSMTP id 5416; Wed, 13 Oct 1993 16:56:54 -0400 Date: Wed, 13 Oct 93 16:47:33 EDT From: Bill Williams Organization: East Tennessee State University Subject: Pine 3.87 on AIX 3.2.3 To: pine-info@cac.washington.edu, pine-bugs@cac.washington.edu I had build pine3.85 on a RS/6000 AIX 3.2.3 with the following mods to the makefile.a32: pine/makefile.a32 and pico/makefile.a32 change modules: tcap to tinfo (:%s/tcap/tinfo/g) change library: termcap to curses (:%s/termcap/curses/g) and it built just fine! I just got 3.87, made the same changes and it will *not* build -- can't find 'tigetstr()' anywhere. This was a problem I had when I tried to build 3.07 way back there and because of it I abandoned pine because I did not have time to pursue the solution. Obviously, somewhere in 3.85 it was solved but is now gone again!? Any clues? Suggestions? I could got the pine-bin.aix32, but it doesn't know vt220 or probably any other vt above 100 on this system -- they go for the terminfo approach and don't waste a lot of effort on termcap so those entries are rather sparse compared to the terminfo database. Also, I want to build without the debug option -- I get a .pine-debug? created for each invocation. I would *really* like to get this sucker to build. --------------------------------------- Bill Williams -- ETSU Systems Support East Tennessee (615) 929-6853 State University From owner-pine-info@cac.washington.edu Thu Oct 14 14:19:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08701; Thu, 14 Oct 93 14:19:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24840; Thu, 14 Oct 93 14:03:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24830; Thu, 14 Oct 93 14:03:36 -0700 Message-Id: <9310142103.AA24830@mx1.cac.washington.edu> Received: from UWAVM.U.WASHINGTON.EDU by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with BSMTP id 6810; Thu, 14 Oct 93 14:03:00 PDT Received: from ETSU.EAST-TENN-ST.EDU by UWAVM.U.WASHINGTON.EDU (Mailer R2.10 ptf008) with BSMTP id 9472; Thu, 14 Oct 93 14:02:59 PDT Received: from etsu.east-tenn-st.edu (NJE origin CMS2@ETSU) by ETSU.EAST-TENN-ST.EDU (LMail V1.1d/1.7f) with BSMTP id 9788; Thu, 14 Oct 1993 17:02:22 -0400 Date: Thu, 14 Oct 93 16:49:40 EDT From: Bill Williams Organization: East Tennessee State University Subject: pine3.86 on AIX 3.2.3 To: pine-info@cac.washington.edu, pine-bugs@cac.washington.edu In-Reply-To: Your message of Thu, 14 Oct 1993 08:58:21 -0400 (EDT) On Thu, 14 Oct 1993 08:58:21 -0400 (EDT) Paul Ribeiro, said: >Sorry, my previous note was premature. I did make the tcap to tinfo change >and when it refused to build, I put back tcap and re-built it and it still >didn't work. However I forgot to remove the old *.o files before the rebuild >Once I removed the *.o files then dir the rebuild with >LIBS= -lcurses -ltermcap -lc >and left tcap.c it built fine and I now have a working pine/pico that >works on vt220's and vt320's(ms-kermit) Bingo! Thanks, Paul. I have it built, but now I'm back to the problem I had with 3.85 wherein... On Wed, 6 Oct 1993 10:14:45 -0400 (EDT) Tim Cheney said: >On Wed, 6 Oct 1993, I wrote: >> Many activities get me kicked out with a "signal abort" and a coredump. >> Immediately reproducable is: >> pine >> 'L' -- List folders >> ...death by signal abort with messages: >> Bug in Pine detected: "Received abort signal". >> Exiting pine. >> IOT/Abort trap(coredump) >> >I had this problem compiling on 3.2.3, but I compiled under 3.2.4 on >another machine and the problem went away. I don't happen to have a 3.4.2 System -- any fixes or suggestions for my nasty 3.2.3 System? --------------------------------------- Bill Williams -- ETSU Systems Support East Tennessee (615) 929-6853 State University From owner-pine-info@cac.washington.edu Thu Oct 14 14:35:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09568; Thu, 14 Oct 93 14:35:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25302; Thu, 14 Oct 93 14:23:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25296; Thu, 14 Oct 93 14:23:51 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09249; Thu, 14 Oct 93 14:23:41 -0700 Date: Thu, 14 Oct 1993 14:22:09 -0700 (PDT) From: David L Miller Subject: Re: pine3.86 on AIX 3.2.3 To: Bill Williams Cc: pine-info@cac.washington.edu, pine-bugs@cac.washington.edu In-Reply-To: <9310142103.AA24830@mx1.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This sounds suspiciously like one of several bugs that were fixed in Pine 3.87. Could you try 3.87 and send me one of the core files if it still happens? |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 14 Oct 1993, Bill Williams wrote: > On Thu, 14 Oct 1993 08:58:21 -0400 (EDT) Paul Ribeiro, > said: > >Sorry, my previous note was premature. I did make the tcap to tinfo change > >and when it refused to build, I put back tcap and re-built it and it still > >didn't work. However I forgot to remove the old *.o files before the rebuild > >Once I removed the *.o files then dir the rebuild with > >LIBS= -lcurses -ltermcap -lc > >and left tcap.c it built fine and I now have a working pine/pico that > >works on vt220's and vt320's(ms-kermit) > > Bingo! Thanks, Paul. > > I have it built, but now I'm back to the problem I had with 3.85 > wherein... > On Wed, 6 Oct 1993 10:14:45 -0400 (EDT) Tim Cheney said: > >On Wed, 6 Oct 1993, I wrote: > >> Many activities get me kicked out with a "signal abort" and a coredump. > >> Immediately reproducable is: > >> pine > >> 'L' -- List folders > >> ...death by signal abort with messages: > >> Bug in Pine detected: "Received abort signal". > >> Exiting pine. > >> IOT/Abort trap(coredump) > >> > >I had this problem compiling on 3.2.3, but I compiled under 3.2.4 on > >another machine and the problem went away. > > I don't happen to have a 3.4.2 System -- any fixes or suggestions for my > nasty 3.2.3 System? > > --------------------------------------- > Bill Williams -- ETSU Systems Support > East > Tennessee (615) 929-6853 > State > University From owner-pine-info@cac.washington.edu Thu Oct 14 15:20:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11248; Thu, 14 Oct 93 15:20:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26270; Thu, 14 Oct 93 15:06:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26262; Thu, 14 Oct 93 15:06:33 -0700 Message-Id: <9310142206.AA26262@mx1.cac.washington.edu> Received: from UWAVM.U.WASHINGTON.EDU by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with BSMTP id 7286; Thu, 14 Oct 93 15:05:58 PDT Received: from ETSU.EAST-TENN-ST.EDU by UWAVM.U.WASHINGTON.EDU (Mailer R2.10 ptf008) with BSMTP id 1046; Thu, 14 Oct 93 15:05:57 PDT Received: from etsu.east-tenn-st.edu (NJE origin CMS2@ETSU) by ETSU.EAST-TENN-ST.EDU (LMail V1.1d/1.7f) with BSMTP id 0113; Thu, 14 Oct 1993 18:05:16 -0400 Date: Thu, 14 Oct 93 18:02:49 EDT From: Bill Williams Organization: East Tennessee State University Subject: Re: pine3.86 on AIX 3.2.3 -- Oops: It's 3.87 To: pine-info@cac.washington.edu, pine-bugs@cac.washington.edu In-Reply-To: Your message of Thu, 14 Oct 93 16:49:40 EDT I mistyped my subject line -- should have been Pine 3.87 instead of Pine 3.86 when.. On Thu, 14 Oct 93 16:49:40 EDT I said: >>> Many activities get me kicked out with a "signal abort" and a coredump. >>> Immediately reproducable is: >>> pine >>> 'L' -- List folders >>> ...death by signal abort with messages: >>> Bug in Pine detected: "Received abort signal". >>> Exiting pine. >>> IOT/Abort trap(coredump) >>> >>I had this problem compiling on 3.2.3, but I compiled under 3.2.4 on >>another machine and the problem went away. > >I don't happen to have a 3.4.2 System -- any fixes or suggestions for my >nasty 3.2.3 System? > > --------------------------------------- > Bill Williams -- ETSU Systems Support > East > Tennessee (615) 929-6853 > State > University From owner-pine-info@cac.washington.edu Fri Oct 15 04:02:07 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00773; Fri, 15 Oct 93 04:02:07 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04316; Fri, 15 Oct 93 03:46:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04310; Fri, 15 Oct 93 03:46:03 -0700 Received: from quinag.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <04696-0@ppsw2.cam.ac.uk>; Fri, 15 Oct 1993 11:45:43 +0100 Date: Fri, 15 Oct 1993 11:39:37 BST From: Barry Landy Subject: Re: Reply-To: To: Pine Info X-Sender: bl10@cus.cam.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We had correspondence recently about the lack of Reply-To: in Pine. One of my users, missing the feature, has pointed us to the relevant text in RFC-822, which would seem to end the debate. If the RFC says it should be there, then the feature ought to be provided, and the only variable left is a decision about priorities. 4.4.3. REPLY-TO / RESENT-REPLY-TO This field provides a general mechanism for indicating any mailbox(es) to which responses are to be sent. Three typical uses for this feature can be distinguished. In the first case, the author(s) may not have regular machine-based mail- boxes and therefore wish(es) to indicate an alternate machine address. In the second case, an author may wish additional persons to be made aware of, or responsible for, replies. A somewhat different use may be of some help to "text message teleconferencing" groups equipped with automatic distribution services: include the address of that service in the "Reply- To" field of all messages submitted to the teleconference; then participants can "reply" to conference submissions to guarantee the correct distribution of any submission of their own. Note: The "Return-Path" field is added by the mail transport service, at the time of final deliver. It is intended to identify a path back to the orginator of the mes- sage. The "Reply-To" field is added by the message originator and is intended to direct replies. ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Fri Oct 15 04:10:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01359; Fri, 15 Oct 93 04:10:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04330; Fri, 15 Oct 93 03:50:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from danpost4.uni-c.dk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04324; Fri, 15 Oct 93 03:50:30 -0700 Received: from danpost4.uni-c.dk by danpost4.uni-c.dk with SMTP (PP) id <12782-0@danpost4.uni-c.dk>; Fri, 15 Oct 1993 11:49:02 +0100 Date: Fri, 15 Oct 1993 11:38:44 +0100 (MET) From: Erik Lawaetz Subject: 2 items for the wish list To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 1. I like to filter my mail into multiple incoming folders. Contrary to elm, pine keeps the empty folders, and consequently one cannot tell by the mere existance of a folder if new mail has arrived, and one has to enter the folders. EAN for instance has the ability to show how many messages a folder contains, and how many are unread/new. I know this requires checking out the folders, and maybe it will slow down things too much? 2. When I do cut and paste in "brokenwindows" (OW 2.0) from one shelltool window to the one running pine I'd like keep the structure of the data I cut from the other window. pico however insists on making it a pretty text. Any way out? Should I just RTFM? --Erik From owner-pine-info@cac.washington.edu Fri Oct 15 09:05:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07761; Fri, 15 Oct 93 09:05:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07799; Fri, 15 Oct 93 08:47:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07793; Fri, 15 Oct 93 08:47:10 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21148; Fri, 15 Oct 93 08:47:04 -0700 Date: Fri, 15 Oct 1993 08:39:24 -0700 (PDT) From: David L Miller Subject: Re: 2 items for the wish list To: Erik Lawaetz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 15 Oct 1993, Erik Lawaetz wrote: > 1. I like to filter my mail into multiple incoming folders. > Contrary to elm, pine keeps the empty folders, and consequently > one cannot tell by the mere existance of a folder if new mail has > arrived, and one has to enter the folders. > EAN for instance has the ability to show how many messages a folder > contains, and how many are unread/new. > I know this requires checking out the folders, and maybe it will slow > down things too much? > The biggest problem with keeping track of all the incoming folders is that you have to keep them open, and with the default berkeley format folders, that means keeping them in memory. In addition there is the extra overhead of checking each one for new mail. We would like to display a count, or at least an indication of new mail, but have not yet figured out a good way to do so. > 2. When I do cut and paste in "brokenwindows" (OW 2.0) from one shelltool > window to the one running pine I'd like keep the structure of the data > I cut from the other window. pico however insists on making it a > pretty text. Any way out? Should I just RTFM? > Pico has no way to tell that a "paste" operation is anything other than a sequence of characters. Consequentially, word wrap occurs just as if you were typing. > --Erik > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA From owner-pine-info@cac.washington.edu Fri Oct 15 09:52:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09377; Fri, 15 Oct 93 09:52:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08935; Fri, 15 Oct 93 09:33:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08929; Fri, 15 Oct 93 09:33:29 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09948; Fri, 15 Oct 93 09:33:24 -0700 Date: Fri, 15 Oct 1993 09:25:27 -0700 (PDT) From: Terry Gray Subject: Re: Reply-To: To: Barry Landy Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Barry, In general I tend to think of RFC822 descriptions as "if you are going to have field xyz, this is how it should be done." Example: there is no requirement that every message have a CC: field; 822 specifies what they should look like if they do exist. However, this debate is academic: as we've said before, "Reply-To:" is definitely coming. I can't say exactly when yet, but "pretty soon"... -teg On Fri, 15 Oct 1993, Barry Landy wrote: > We had correspondence recently about the lack of Reply-To: in Pine. One > of my users, missing the feature, has pointed us to the relevant text in > RFC-822, which would seem to end the debate. If the RFC says it should be > there, then the feature ought to be provided, and the only variable left > is a decision about priorities. > > > 4.4.3. REPLY-TO / RESENT-REPLY-TO > > This field provides a general mechanism for indicating any > mailbox(es) to which responses are to be sent. Three typical > uses for this feature can be distinguished. In the first > case, the author(s) may not have regular machine-based mail- > boxes and therefore wish(es) to indicate an alternate machine > address. In the second case, an author may wish additional > persons to be made aware of, or responsible for, replies. A > somewhat different use may be of some help to "text message > teleconferencing" groups equipped with automatic distribution > services: include the address of that service in the "Reply- > To" field of all messages submitted to the teleconference; > then participants can "reply" to conference submissions to > guarantee the correct distribution of any submission of their > own. > > Note: The "Return-Path" field is added by the mail transport > service, at the time of final deliver. It is intended > to identify a path back to the orginator of the mes- > sage. The "Reply-To" field is added by the message > originator and is intended to direct replies. > > > ======================================================================= > Barry Landy, Head of Systems and Development, > University of Cambridge Computing Service > Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 > > > > From owner-pine-info@cac.washington.edu Fri Oct 15 10:00:57 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09679; Fri, 15 Oct 93 10:00:57 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09155; Fri, 15 Oct 93 09:45:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from INDIV-GW.CENT.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09149; Fri, 15 Oct 93 09:45:37 -0700 Received: by individual.com (5.65c/Spike-2.1) id AA21426; Fri, 15 Oct 1993 12:42:12 -0400 Date: Fri, 15 Oct 1993 12:36:14 -0400 (EDT) From: Adam J Weitzman Subject: Headers To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII While some people are asking for "Reply-To:" and other headers, a question comes to mind: since RFC-822 essentially allows you any darn header you please in an email message, why not have a facility that allows the user to do just that, put in any header they want? While I'm here, I would also really like the ability to move to the bottom of a long message I am reading and to do a search inside a message I am reading. Things for the wish list. - Adam J Weitzman INDIVIDUAL, Inc. weitzman@individual.com From owner-pine-info@cac.washington.edu Fri Oct 15 11:12:43 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12523; Fri, 15 Oct 93 11:12:43 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06186; Fri, 15 Oct 93 10:52:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay2.UU.NET by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06176; Fri, 15 Oct 93 10:51:22 -0700 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09299; Fri, 15 Oct 93 13:50:10 -0400 Received: from racerx.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 134831.14081; Fri, 15 Oct 1993 13:48:31 EDT Received: from ernie.noname by racerx (4.1/SMI-4.0) id AA12383; Fri, 15 Oct 93 12:36:15 CDT Date: Fri, 15 Oct 93 12:36:15 CDT From: ken@bridge.COM (Ken Hardy) Message-Id: <9310151736.AA12383@racerx> To: pine-info@cac.washington.edu Subject: Re: Headers Reply-To: pine-info@cac.washington.edu Adam J Weitzman writes: >since RFC-822 essentially allows you any darn header you please in an >email message, why not have a facility that allows the user to do just >that, put in any header they want? Although I maintain Pine for those users who need/prefer it, I use Sun's mailtool myself, and it has just such a facility -- I used it to add the "Reply-To" header on this message so that any responses should go to the list automagically. Do the authors of Pine use only Pine? It's a great application, but they're wearing blinders if they don't survey what's being done by other applications in the same field. (They're probably well informed, and it's just a matter of reaching a consensus of what's worth doing and what's not.) Letting the user add any header desired keeps the Rich Headers option from getting too big and avoids the shortcomings of petrifying a list what headers can be added. Some applications (like the anon.penet.fi anonymous mail server) use "X-*" headers of their own design. I think it's worth serious consideration. -- Ken Hardy ken@bridge.com (racerx!ken) --__-_____--__-__--_--__-___-__-__-___---- From owner-pine-info@cac.washington.edu Fri Oct 15 12:19:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14762; Fri, 15 Oct 93 12:19:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11597; Fri, 15 Oct 93 11:42:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11591; Fri, 15 Oct 93 11:42:06 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14227; Fri, 15 Oct 93 11:41:37 -0700 Date: Fri, 15 Oct 1993 11:17:58 -0700 (PDT) From: Terry Gray Subject: Re: Headers To: Ken Hardy Cc: pine-info@cac.washington.edu In-Reply-To: <9310151736.AA12383@racerx> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 15 Oct 1993, Ken Hardy wrote: > Adam J Weitzman writes: > > >since RFC-822 essentially allows you any darn header you please in an > >email message, why not have a facility that allows the user to do just > >that, put in any header they want? I personally lean toward a laissez faire approach to headers, but be advised that not everyone agrees that this would be desirable. In the past, some mail agent authors have been flamed for permitting arbitrary headers because of their potential for perceived "abuse". Alas, we have at least our share of mischief makers. > Although I maintain Pine for those users who need/prefer it, I use > Sun's mailtool myself, and it has just such a facility -- I used it to > add the "Reply-To" header on this message so that any responses should > go to the list automagically. Yes, but this is a good example of what I would consider *mis*use of the Reply-To: field. LISTSERV's are often configured this way, and it has caused enormous embarrassment to individuals who thought they were replying to an author, only to find their msg in thousands of mailboxes. Fortunately, Pine gives you the option of ignoring the reply-to field, so that you get to *choose* where your response goes. > Do the authors of Pine use only Pine? It's a great application, but > they're wearing blinders if they don't survey what's being done by > other applications in the same field. (They're probably well informed, > and it's just a matter of reaching a consensus of what's worth doing > and what's not.) The pine team *tries* to keep up on current events, but we always appreciate efforts to educate us... There is a consensus issue, but there is even more a *time* issue. This is only one of *many* enhancement requests. > Letting the user add any header desired keeps the Rich Headers option > from getting too big and avoids the shortcomings of petrifying a list > what headers can be added. Some applications (like the anon.penet.fi > anonymous mail server) use "X-*" headers of their own design. I think > it's worth serious consideration. Rest assured that it is getting serious consideration. But also keep in mind who is funding this project. In the 3+ years that Pine has been around, I believe that virtually all the requests for additional header support have come from other sites. With possibly very few exceptions, their absence has not been noticed by our constituency. Having said that, I will state one more time, just to be really clear: we will be providing additional header support in a future release. Whether to permit arbitrary user-defined headers is not yet decided, for the reason mentioned above, but Reply-To will certainly be there one way or another. -teg From owner-pine-info@cac.washington.edu Sat Oct 16 03:29:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05819; Sat, 16 Oct 93 03:29:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22250; Sat, 16 Oct 93 03:11:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22242; Sat, 16 Oct 93 03:11:27 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA12134; Sat, 16 Oct 93 05:11:24 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA29155; Sat, 16 Oct 93 17:46:48 +0800 Date: Sat, 16 Oct 1993 16:33:44 +0800 (TPE) From: Ed Greshko Subject: Re: Headers To: Terry Gray Cc: Ken Hardy , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 15 Oct 1993, Terry Gray wrote: > On Fri, 15 Oct 1993, Ken Hardy wrote: > > > Adam J Weitzman writes: > > > > >since RFC-822 essentially allows you any darn header you please in an > > >email message, why not have a facility that allows the user to do just > > >that, put in any header they want? > > I personally lean toward a laissez faire approach to headers, but be > advised that not everyone agrees that this would be desirable. In the > past, some mail agent authors have been flamed for permitting arbitrary > headers because of their potential for perceived "abuse". Alas, we have > at least our share of mischief makers. I don't think it is so much a "preceived abuse" but a risk to interoperability. As an example... It doesn't matter whether or not you compile MIME support into elm, elm will always generate a "Content" header. A certain application at our site was checking for "Content" header to determine if the message was MIME so it could further process the message. The application failed since the message was not really MIME compliant. Granted, the application should have been checking for the "Mime-Version" header instead of the "Content" header.....maybe....since without the "Mime-Version" header the "Content" is not defined and therefore should not appear in a message. I believe that RFC-822 is quite clear in its intentions and definitions. If you are going to implement the headers defined in 822 (and its extensions) you must do so as defined. If you wish to use headers not defined in the RFCs then you need to preceed it with an X. The reasoning is clear, in that later RFCs may define a header that you have chosen to use and you may end up "breaking" compliant UAs. Remember too that RFC-822 and its extentions only tell you how you must implement the defined headers. It doesn't say you have to implement them all. > > Although I maintain Pine for those users who need/prefer it, I use > > Sun's mailtool myself, and it has just such a facility -- I used it to > > add the "Reply-To" header on this message so that any responses should > > go to the list automagically. > > Yes, but this is a good example of what I would consider *mis*use of the > Reply-To: field. LISTSERV's are often configured this way, and it has > caused enormous embarrassment to individuals who thought they were > replying to an author, only to find their msg in thousands of mailboxes. > Fortunately, Pine gives you the option of ignoring the reply-to field, so > that you get to *choose* where your response goes. I like the fact that pine gives you the choice...but I can do without it since I'm a more experienced email user. For the less educated email user it presents a dilema. "When do I say yes? When do I say no? If I say no can I be sure my reply will get there?" I would say leave the decision of adding the "Reply-To:" field with the sender. If it causes "enormous embarrassment" it will not be the end of the world and the user will learn a few things from it. Not the least of which would be to be more careful of what is said in email. > > Do the authors of Pine use only Pine? It's a great application, but > > they're wearing blinders if they don't survey what's being done by > > other applications in the same field. (They're probably well informed, > > and it's just a matter of reaching a consensus of what's worth doing > > and what's not.) > > The pine team *tries* to keep up on current events, but we always > appreciate efforts to educate us... > > There is a consensus issue, but there is even more a *time* issue. This is > only one of *many* enhancement requests. I'm very sure the Pine authors are up-to-date on what is happening in the world of email. As far as I know, there is no UA in existence that implements all of the possible features in all of the possible combinations in all of the possible ways that everyone will like. (Just be happy they don't have to decide on what features of X.400 they should implement.) I for one am thankful that there isn't enough time to implement all of the "*many* enhancement requests". To do so would drive Pine to the level of complexity it seeks to avoid. > > Letting the user add any header desired keeps the Rich Headers option > > from getting too big and avoids the shortcomings of petrifying a list > > what headers can be added. Some applications (like the anon.penet.fi > > anonymous mail server) use "X-*" headers of their own design. I think > > it's worth serious consideration. > > Rest assured that it is getting serious consideration. But also keep in > mind who is funding this project. In the 3+ years that Pine has been > around, I believe that virtually all the requests for additional header > support have come from other sites. With possibly very few exceptions, > their absence has not been noticed by our constituency. "X-*" headers of their own design" only make sense if they convey information that the receiving UA understands and can make use of. While I see some justification for them I also see the potention for misue much like the *huge* .sigs I've had to endure. Should the authors of Pine decide to allow them I hope they also make it optional to display them. That said, I'd vote for minimum additions to the "Rich Headers" field and the ability to include a file of user defined headers on which Pine would enforce the "X-*" convention. > Having said that, I will state one more time, just to be really clear: > we will be providing additional header support in a future release. > Whether to permit arbitrary user-defined headers is not yet decided, > for the reason mentioned above, but Reply-To will certainly be there one > way or another. Thank you for considering it. If I wore one, I'd take my hat off to the Pine Team for being as sensitive as they are to indivduals outside of their community. And even if they decide against adding this feature there are at least 2 alternatives...move to another UA or start hacking. I, for one, would rather hack than switch. :-) :-) Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Sat Oct 16 07:56:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08907; Sat, 16 Oct 93 07:56:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23795; Sat, 16 Oct 93 07:43:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23789; Sat, 16 Oct 93 07:43:19 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04132; Sat, 16 Oct 93 07:43:14 -0700 Date: Sat, 16 Oct 1993 07:40:07 -0700 (PDT) From: Terry Gray Subject: Re: Pine 3.86 not including contributed code To: Maria.Dimou@cern.ch Cc: pine-bugs@cac.washington.edu, pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 13 Oct 1993, M. Dimou-Zacharova wrote: > I sent the following message last friday and got no answer so far. > I got pine 3.87 in the mean time and saw that the lock-in-home-dir > option was still not considered insteresting. > Please, don't think that I am 'agressive' on this matter. I just > want to confirm you got my message and find out your opinion. > I have thousands of users at CERN who access mail via afs , want to have > several pine and simultaneous elm sessions from different hosts and > the default locking in /tmp doesn't help in such cases. > Thanks for considering these thoughts Maria, My apologies for our not responding sooner... as you can imagine, things have been fairly hectic lately. Attached is a message that Steve Hubert sent to you and Markus on 21 Jul indicating that we probably wouldn't include the contributed changes for locking in home directories, and inviting further discussion --which was not forthcoming. You mentioned in your original msg that "this feature of allowing locking in the user's home directory (if defined) is harmless and very useful." We discussed the locking situation further at our weekly development meeting yesterday, and concluded that while locking in /tmp *is* a problem in your environment (where a single /tmp is not globally available on all machines), the proposed solution is not completely harmless, which is why we are still a bit reluctant to encourage lockfiles in home directories. The problem is with the shared mailbox case. Pine and imapd locks mediate access not only between a single MUA and the delivery agent (which agent presumably *can* be taught to find the lock file in the user's home dir), but they *also* mediate access among concurrent sessions, of possibly different users. In the multiple user case, a process running on behalf of one user has no knowledge of who else might be accessing the mailbox, so would be unable to know where to look for the lock file. If you are using tenex or mbox drivers, it's even worse, since access to both the inbox and the spool file has to be mediated. If you don't allow (or at least don't advertise the possibility of) shared mailboxes, this shared case may be of small consequence to you, but we are finding it increasingly useful and popular, so you can understand why we are concerned about giving the home directory lock approach a stamp of approval, even if only via an IFDEF. We believe that the ideal model is to organize things so that *all* the processes that directly manipulate a particular mailbox are actually running on the same machine. That doesn't mean running Pine on a file server, of course, but it does mean running IMAPd on whichever machine the mail is actually delivered to. I realize this suggestion is not 100% helpful if the delivery agent has been modified to accommodate non-IMAP clients by looking for lockfiles in home directories. So the choices seem to be: 1. Use /tmp for lockfiles, with all processes directly manipulating a mailbox running on the same machine. Pro: solves all locking problems even for multiuser shared mailboxes. Con: implies using only IMAP clients, or having a shared /tmp 2. Use NFS or AFS -mounted mailboxes with lockfiles in $HOME Pro: allows for concurrent non-IMAP and IMAP access to mailbox Con: precludes multiuser shared mailbox access, even in pure IMAP case (and in the NFS case, there are other problems.) 3. Postulate a "global" /tmp alternative, e.g. /gtmp Pro: allows for imap and non-imap access, and shared multi-user access. Con: highly non-standard; requires changes to all mail programs used. 4. See if it is feasible for the delivery agent to look in both places for lockfiles... on the assumption that users will not be trying to run elm and pine *simultaneously*. (This also assumes using Pine in IMAP mode, but I can't think of any reason *not* to do that...) 5. Try to think of a clever solution using links... Comments? Other suggestions? -teg ---------- Forwarded message ---------- Date: Wed, 21 Jul 1993 15:21:43 -0700 (PDT) From: Steve Hubert To: Markus Baertschi Cc: Sheryl Erez , pine-bugs@cac.washington.edu, dimou@dxcoms.cern.ch Subject: Re: Pine port to AIX 3.2 Markus, Pine has changed quite a bit between our last release and the current development source, so it is a little tough to integrate ports. We do have an AIX 3.2 system to work on and have a version that compiles and runs there. Perhaps when we are just a little bit more stable (couple weeks maybe?) you would be interested in testing on your AIX system. If so, we could send you an alpha-version to try to compile and run there. I don't believe we will include your LOCK_IN_HOME change in the source, however. If you wish to try to convince us of that write back and we'll discuss it! Thanks. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Sun Oct 17 13:34:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29047; Sun, 17 Oct 93 13:34:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02709; Sun, 17 Oct 93 13:24:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cerebrum.impaqt.drexel.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02703; Sun, 17 Oct 93 13:24:09 -0700 Received: by impaqt.drexel.edu (4.1/SMI-4.1) id AA11014; Sun, 17 Oct 93 16:22:53 EDT Date: Sun, 17 Oct 93 16:22:53 EDT From: meystel@cerebrum.impaqt.drexel.edu (Meystel) Message-Id: <9310172022.AA11014@impaqt.drexel.edu> To: pine-info@cac.washington.edu Subject: pine.conf Hi, I just compiled pine and I need to install pine.info and pine.conf files in the /usr/local/lib directory, but I can't find sample pine.conf or pine.info anywhere in the 3.87 distribution hierarchy. Could someone please point me in the right direction? Otherwise, the pine.debugX files keep getting bigger and bigger in each user's directory.... Thank you. ----- Michael A. Meystel Systems & Network Administration IMPACT Center, College of Engineering Drexel University, Philadelphia, PA USA + 1 215 895 5807 / meystel@impact.drexel.edu From owner-pine-info@cac.washington.edu Sun Oct 17 14:42:49 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29808; Sun, 17 Oct 93 14:42:49 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03051; Sun, 17 Oct 93 14:33:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03045; Sun, 17 Oct 93 14:33:10 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20830; Sun, 17 Oct 93 14:32:58 -0700 Date: Sun, 17 Oct 1993 14:30:48 -0700 (PDT) From: David L Miller Subject: Re: pine.conf To: Meystel Cc: pine-info@cac.washington.edu In-Reply-To: <9310172022.AA11014@impaqt.drexel.edu> Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-351460413-750893577:#20678" --0-351460413-750893577:#20678 Content-Type: TEXT/PLAIN; charset=US-ASCII You can get a default pine.conf by running "pine -conf". The pine.info file is simply a text file with whatever local information you want in it. I will attach a sample from one of our systems. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Sun, 17 Oct 1993, Meystel wrote: > Hi, > > I just compiled pine and I need to install pine.info and pine.conf > files in the /usr/local/lib directory, but I can't find sample > pine.conf or pine.info anywhere in the 3.87 distribution hierarchy. > Could someone please point me in the right direction? Otherwise, > the pine.debugX files keep getting bigger and bigger in each user's > directory.... > > Thank you. > > > ----- > > Michael A. Meystel > Systems & Network Administration > IMPACT Center, College of Engineering > Drexel University, Philadelphia, PA USA > + 1 215 895 5807 / meystel@impact.drexel.edu > > --0-351460413-750893577:#20678 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="pine.conf" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: IyAgICAgIC91c3IvbG9jYWwvbGliL3BpbmUuY29uZiAtLSBzeXN0ZW0gd2lk ZSBwaW5lIGNvbmZpZ3VyYXRpb24KIwojICBWYWx1ZXMgaGVyZSBhZmZlY3Qg YWxsIHBpbmUgdXNlcnMgdW5sZXNzIHRoZXkndmUgb3ZlcmlkZGVuIHRoZSB2 YWx1ZXMKIyAgaW4gdGhlaXIgLnBpbmVyYyBmaWxlcy4gIEEgYmxhbmsgY29w eSBvZiB0aGlzIGZpbGUgbWF5IGJlIG9idGFpbmVkCiMgIGJ5IHJ1bm5pbmcg InBpbmUgLWNvbmYiLiBJdCB3aWxsIGJlIHByaW50ZWQgb24gdGhlIHN0YW5k YXJkIG91dHB1dC4KIwojICBGb3IgYSB2YXJpYWJsZSB0byBiZSB1bnNldCBp dCdzIHZhbHVlIG11c3QgYmUgYmxhbmsuCiMgIFRvIHNldCBhIHZhcmlibGUg dG8gdGhlIGVtcHR5IHN0cmluZyBpdCdzIHZhbHVlIHNob3VsZCBiZSAiIi4K IyAgU3dpdGNoIHZhcmlhYmxlcyBhcmUgZWl0aGVyIHNldCB0byAieWVzIiBv ciAibm8iLgojCiMgIChUaGVzZSBjb21tZW50cyBhcmUgYXV0b21hdGljYWxs eSBpbnNlcnRlZC4pCgojIHVzZXItZG9tYWluIHNwZWNpZmllcyB0aGUgZG9t YWluIHBhcnQgb2YgeW91ciByZXR1cm4gYWRkcmVzcyBvbiBvdXRnb2luZwoj IGVtYWlsIGFuZCBpcyBhbHNvIHVzZWQgYXMgdGhlIGRlZmF1bHQgZG9tYWlu IGZvciBlbWFpbCBjb21wb3NlZCB0byBhCiMgbG9jYWwgdXNlci4gIElmIHVu c2V0LCBVbml4IFBpbmUgd2lsbCBvYnRhaW4gdGhlIGRvbWFpbiBmcm9tIHRo ZSBzeXN0ZW0uCnVzZXItZG9tYWluPQoKIyBMaXN0IG9mIFNNVFAgc2VydmVy cyBmb3Igc2VuZGluZyBtYWlsLiBZb3UgbXVzdCBoYXZlIGFuIFNNVFAgc2Vy dmVyCiMgZm9yIHVzZSB3aXRoIFBDLVBpbmUuICBFeGFtcGxlOiBzbXRwLXNl cnZlcj1tYWlsaG9zdC51Lndhc2hpbmd0b24uZWR1CiMgSWYgYmxhbmsgb24g VW5peCwgc2VuZG1haWwgd2lsbCBiZSB1c2VkLgpzbXRwLXNlcnZlcj0KCiMg aW5ib3gtcGF0aCBzcGVjaWZpZXMgdGhlIG5hbWUvcGF0aC9sb2NhdGlvbiBv ZiB5b3VyIElOQk9YLiAgRXhhbXBsZToKIyBpbmJveC1wYXRoPXtjYXJzb24u dS53YXNoaW5ndG9uLmVkdX1pbmJveCAoSU5CT1ggb24gYSByZW1vdGUgY29t cHV0ZXIpCiMgTm9ybWFsIFVuaXggZGVmYXVsdCBpcyB0aGUgbG9jYWwgSU5C T1ggKHVzdWFsbHkgL3VzZXIvc3Bvb2wvbWFpbC8kVVNFUikKaW5ib3gtcGF0 aD17c2hpdmFtcy5jYWMud2FzaGluZ3Rvbi5lZHV9aW5ib3gKCiMgaW5jb21p bmctZm9sZGVycyBhcmUgdGhvc2Ugb3RoZXIgdGhhbiBJTkJPWCB0aGF0IHJl Y2VpdmUgbmV3IG1lc3NhZ2VzLgojIEZvbGRlciBzeW50YXg6IG9wdG5sLWxh YmVsIHtvcHRubC1pbWFwLWhvc3RuYW1lfWZvbGRlci1wYXRoCiMgVXNlIG9u bHkgaWYgeW91IGZpbHRlciBpbmNvbWluZyBlbWFpbCBpbnRvIG11bHRpcGxl IGZpbGVzIG9yIHJlY2VpdmUKIyBlbWFpbCBvbiBzZXZlcmFsIGRpZmZlcmVu dCBtYWNoaW5lcy4KIyBFeGFtcGxlOgojIGluY29taW5nLWZvbGRlcnM9Q29u c3VsdGluZyAgICAgICB7Y2Fyc29uLnUud2FzaGluZ3Rvbi5lZHV9ZmlsdGVy L3RvLWhlbHAsCiMgICAgICAgICAgICAgICAgICBXaWRnZXQtUHJvamVjdCAg IHtjYXJzb24udS53YXNoaW5ndG9uLmVkdX1maWx0ZXIvdG8td2lkZ2V0LAoj ICAgICAgICAgICAgICAgICAgT2xkLVN0dWRlbnQtQWNjdCB7aW1hcC5iZXJr ZWxleS5lZHV9aW5ib3gKaW5jb21pbmctZm9sZGVycz0KCiMgZm9sZGVyLWNv bGxlY3Rpb25zIHNwZWNpZmllcyBhIGxpc3Qgb2YgZm9sZGVyIGNvbGxlY3Rp b25zIHdoZXJlaW4gc2F2ZWQKIyBtZXNzYWdlcyBhcmUgc3RvcmVkLiBUaGUg Zmlyc3QgY29sbGVjdGlvbiBpcyB0aGUgZGVmYXVsdCBmb3Igc2F2ZXMuCiMg Q29sbGVjdGlvbiBzeW50YXg6IG9wdG5sLWxhYmVsIHtvcHRubC1pbWFwLWhv c3RuYW1lfW9wdG5sLWRpcmVjdG9yeS1wYXRoW10KIyBFeGFtcGxlOgojIGZv bGRlci1jb2xsZWN0aW9ucz1TYXZlZC1FbWFpbCAgICB7Zm9vLmJhci5lZHV9 bWFpbC9bXSwKIyAgICAgICAgICAgICAgICAgICAgV2lkZ2V0LVByb2plY3Qg d2lkZ2V0L1tdLCAgPC0tIFZhbGlkIG9ubHkgaW4gVW5peCBQaW5lCiMgICAg ICAgICAgICAgICAgICAgIExvY2FsLVBDICAgICAgIG1haWxcW10gICAgIDwt LSBWYWxpZCBvbmx5IGluIFBDLVBpbmUKZm9sZGVyLWNvbGxlY3Rpb25zPQoK IyBuZXdzLWNvbGxlY3Rpb25zIHNwZWNpZmllcyBvbmUgb3IgbW9yZSBjb2xs ZWN0aW9ucyBvZiBuZXdzIGdyb3Vwcy4KIyBOZXdzIGNvbGxlY3Rpb24gc3lu dGF4OiBvcHRubC1sYWJlbCAqe25ld3MtaG9zdC9wcm90b2NvbH1bXQojIEV4 YW1wbGU6CiMgbmV3cy1jb2xsZWN0aW9ucz1TdWJzY3JpYmVkLUdyb3VwcyAq e25ld3MudS53YXNoaW5ndG9uLmVkdS9ubnRwfVtdCm5ld3MtY29sbGVjdGlv bnM9CgojIGRlZmF1bHQtZmNjIHNwZWNpZmllcyB3aGVyZSBhIGNvcHkgb2Yg b3V0Z29pbmcgbWFpbCBpcyBzYXZlZC4gIElmIHRoaXMgaXMKIyBub3QgYSBw YXRoIG5hbWUsIGl0IHdpbGwgYmUgaW4gdGhlIHRoZSBkZWZhdWx0IGNvbGxl Y3Rpb24gZm9yIHNhdmVzLgojIFVuaXggUGluZSBkZWZhdWx0IGlzIG5vcm1h bGx5ICJzZW50LW1haWwiIGluIHRoZSBkZWZhdWx0IGZvbGRlciBjb2xsZWN0 aW9uLgojIFBDLVBpbmUgZGVmYXVsdCBpcyAiU0VOVE1BSUwiIChzdG9yZWQg YXMgU0VOVE1BSUwuTVRYKQojIEV4YW1wbGUgb2YgcmVtb3RlIGNhc2U6IHtj YXJzb24udS53YXNoaW5ndG9uLmVkdX1zZW50LW1haWwKIyBUbyBzdXBwcmVz cyBzYXZpbmcgb2Ygb3V0Z29pbmcgbWFpbCwgc2V0OiBkZWZhdWx0LWZjYz0i IgpkZWZhdWx0LWZjYz0KCiMgbWFpbC1kaXJlY3RvcnkgaXMgd2hlcmUgcG9z dHBvbmVkICYgaW50ZXJydXB0ZWQgbXNncyBhcmUgaGVsZCB0ZW1wb3Jhcmls eS4KbWFpbC1kaXJlY3Rvcnk9CgojIHJlYWQtbWVzc2FnZS1mb2xkZXIgc3Bl Y2lmaWVzIHdoZXJlIGFscmVhZHktcmVhZCBtZXNzYWdlcyB3aWxsIGJlIHN0 b3JlZC4KIyBJZiBzZXQsIHlvdSB3aWxsIGJlIGFza2VkIHdoZW4geW91IHF1 aXQgUGluZSBpZiB5b3Ugd2FudCByZWFkIG1lc3NhZ2VzCiMgdG8gYmUgbW92 ZWQgdG8gdGhpcyBmb2xkZXIgYW5kIGRlbGV0ZWQgZnJvbSB5b3VyIElOQk9Y LgpyZWFkLW1lc3NhZ2UtZm9sZGVyPQoKIyBzaWduYXR1cmUtZmlsZSBzcGVj aWZpZXMgdGhlIG5hbWUgb3IgcGF0aCBvZiBhIGZpbGUgY29udGFpbmluZyB0 ZXh0IHRoYXQKIyB3aWxsIGF1dG9tYXRpY2FsbHkgYmUgaW5zZXJ0ZWQgaW4g b3V0Z29pbmcgbWFpbC4Kc2lnbmF0dXJlLWZpbGU9CgojIGFkZHJlc3MtYm9v ayBzcGVjaWZpZXMgdGhlIGZpbGVuYW1lIG9yIHBhdGggbmFtZSBvZiBQaW5l J3MgYWRkcmVzc2Jvb2suCiMgVW5peCBQaW5lIGRlZmF1bHQgaXMgbm9ybWFs bHkgfi8uYWRkcmVzc2Jvb2sKIyBQQy1QaW5lIGRlZmF1bHQgaXMgXFBJTkVc QUREUkJPT0sKYWRkcmVzcy1ib29rPQoKIyBmZWF0dXJlLWxpc3Q9IGNvbW1h LXNlcGFyYXRlZCBsaXN0IG9mIGZlYXR1cmVzIGZyb20gdGhlIGZvbGxvd2lu ZyBzZXQ6CiMgTm90ZTogdGhlIHZhbHVlICJvbGQtZ3Jvd3RoIiBpcyBzaG9y dGhhbmQgZm9yIHRoZSBpbmRpY2F0ZWQgZmVhdHVyZXMuLi4KIyBlbmFibGUt ZnVsbC1oZWFkZXItY21kICAgICAgICAoaW5jbHVkZWQgaW4gb2xkLWdyb3d0 aCBzZXQpCiMgZW5hYmxlLXVuaXgtcGlwZS1jbWQgICAgICAgICAgKGluY2x1 ZGVkIGluIG9sZC1ncm93dGggc2V0KQojIGVuYWJsZS1ib3VuY2UtY21kICAg ICAgICAgICAgIChpbmNsdWRlZCBpbiBvbGQtZ3Jvd3RoIHNldCkKIyBlbmFi bGUtYWx0ZXJuYXRlLWVkaXRvci1jbWQgICAoaW5jbHVkZWQgaW4gb2xkLWdy b3d0aCBzZXQpCiMgZW5hYmxlLXN1c3BlbmQgICAgICAgICAgICAgICAgKGlu Y2x1ZGVkIGluIG9sZC1ncm93dGggc2V0KQojIGVuYWJsZS10YWItY29tcGxl dGlvbiAgICAgICAgIChpbmNsdWRlZCBpbiBvbGQtZ3Jvd3RoIHNldCkKIyBl bmFibGUtanVtcC1zaG9ydGN1dCAgICAgICAgICAoaW5jbHVkZWQgaW4gb2xk LWdyb3d0aCBzZXQpCiMgcXVpdC13aXRob3V0LWNvbmZpcm0gICAgICAgICAg KGluY2x1ZGVkIGluIG9sZC1ncm93dGggc2V0KQojIGVuYWJsZS1nb3RvLWNt ZCAgICAgICAgICAgICAgIChpbmNsdWRlZCBpbiBvbGQtZ3Jvd3RoIHNldCkK IyBlbmFibGUtYXBwbHktY21kICAgICAgICAgICAgICAoaW5jbHVkZWQgaW4g b2xkLWdyb3d0aCBzZXQpCiMgZW5hYmxlLWZsYWctY21kICAgICAgICAgICAg ICAgKGluY2x1ZGVkIGluIG9sZC1ncm93dGggc2V0KQojIGVuYWJsZS16b29t LWNtZCAgICAgICAgICAgICAgIChpbmNsdWRlZCBpbiBvbGQtZ3Jvd3RoIHNl dCkKIyBleHBhbmRlZC12aWV3LW9mLWZvbGRlcnMKIyB1c2UtZnVuY3Rpb24t a2V5cwojIGluY2x1ZGUtaGVhZGVyLWluLXJlcGx5CiMgc2lnbmF0dXJlLWF0 LWJvdHRvbQojIGRlbGV0ZS1za2lwcy1kZWxldGVkCiMgZS5nLgojIGZlYXR1 cmUtbGlzdD0gb2xkLWdyb3d0aCwgc2lnbmF0dXJlLWF0LWJvdHRvbQpmZWF0 dXJlLWxpc3Q9ZW5hYmxlLWdvdG8tY21kCgojIFBpbmUgZXhlY3V0ZXMgdGhl c2Uga2V5cyB1cG9uIHN0YXJ0dXAgKGUuZy4gdG8gdmlldyBtc2cgMTM6IGks aiwxLDMsQ1IsdikKaW5pdGlhbC1rZXlzdHJva2UtbGlzdD0KCiMgc2F2ZWQt bXNnLW5hbWUtcnVsZT0gZGV0ZXJtaW5lcyBkZWZhdWx0IGZvbGRlciBuYW1l IGZvciBTYXZlcy4uLgojIENob29zZSBvbmU6IGRlZmF1bHQtZm9sZGVyLCBi eS1zZW5kZXIsIGJ5LXJlY2lwaWVudCwgbGFzdC1mb2xkZXItdXNlZAojIE5v cm1hbCBkZWZhdWx0IGlzICJkZWZhdWx0LWZvbGRlciIsIHdoaWNoIG9uIFVu aXggbWVhbnMgInNhdmVkLW1lc3NhZ2VzIgojIGFuZCBpbiBQQy1QaW5lIG1l YW5zICJTQVZFTUFJTCIKc2F2ZWQtbXNnLW5hbWUtcnVsZT0KCiMgc29ydC1r ZXk9IG9yZGVyIGluIHdoaWNoIG1lc3NhZ2VzIHdpbGwgYmUgcHJlc2VudGVk Li4uCiMgQ2hvb3NlIG9uZTogc3ViamVjdCwgZnJvbSwgYXJyaXZhbCwgZGF0 ZSwgc2l6ZS4KIyBOb3JtYWwgZGVmYXVsdCBpcyAiYXJyaXZhbCIKc29ydC1r ZXk9CgojIGNoYXJhY3Rlci1zZXQgc2hvdWxkIHJlZmxlY3QgdGhlIGNhcGFi aWxpdGllcyBvZiB0aGUgZGlzcGxheSB5b3UgaGF2ZS4KIyBOb3JtYWwgZGVm YXVsdCBpcyBVUy1BU0NJSS4gIFR5cGljYWwgYWx0ZXJuYXRpdmVzIGluY2x1 ZGUgSVNPLTg4NTkteCwKIyB3aGVyZSB4IGlzIGEgbnVtYmVyIGJldHdlZW4g MSBhbmQgOS4KY2hhcmFjdGVyLXNldD0KCiMgZWRpdG9yIHNwZWNpZmllcyB0 aGUgcHJvZ3JhbSBpbnZva2VkIGJ5IF5fIGluIHRoZSBDb21wb3Nlci4KIyBU aGlzIGlzIG5vcm1hbGx5IGFuIGFsdGVybmF0aXZlIHRvIFBpbmUncyBpbnRl cm5hbCBjb21wb3NlciAoUGljbykKZWRpdG9yPQoKIyBQcm9ncmFtIHRvIHZp ZXcgaW1hZ2VzIGlmIGZvcm1hdCBzdWNoIGFzIEdJRiBhbmQgVElGRgppbWFn ZS12aWV3ZXI9L3Vzci9sb2NhbC9iaW4vWDExUjQuZGlyL2Jpbi8uYmluL3hs b2FkaW1hZ2UgLWNvbG9ycyAxMjgKCiMgVXNlZCBpZiAidXNlci1kb21haW4i IG5vdCBzZXQuICBTdHJpcHMgaG9zdG5hbWUgZnJvbSB1c2VyJ3MgcmV0dXJu IGFkZHJlc3MuCiMgTm90IGFwcGxpY2FibGUgZm9yIFBDLVBpbmUKdXNlLW9u bHktZG9tYWluLW5hbWU9eWVzCgojIFlvdXIgcHJpbnRlciBzZWxlY3Rpb24K cHJpbnRlcj0KCiMgVGhlIHN5c3RlbSB3aWRlIHN0YW5kYXJkIHByaW50ZXIK c3RhbmRhcmQtcHJpbnRlcj0KCiMgTmlja25hbWUgb2YgYnVncyBlbnRyeSB0 byBiZSBhdXRvbWF0aWNhbGx5IHBsYWNlZCBpbiBhbGwgYWRkcmVzcyBib29r cwpidWdzLW5pY2tuYW1lPXBpbmUtYnVncwoKIyBGdWxsIG5hbWUgb2YgYnVn cyBlbnRyeSB0byBiZSBhdXRvbWF0aWNhbGx5IHBsYWNlZCBpbiBhbGwgYWRk cmVzcyBib29rcwpidWdzLWZ1bGxuYW1lPVBpbmUgTWlzc2lvbiBDb250cm9s IHtidWcgcmVwb3J0c30KCiMgRW1haWwgYWRkcmVzcyBvZiBidWdzIGVudHJ5 IHRvIGJlIGF1dG9tYXRpY2FsbHkgcGxhY2VkIGluIGFsbCBhZGRyZXNzIGJv b2tzCmJ1Z3MtYWRkcmVzcz1waW5lLWJ1Z3NAY2FjLndhc2hpbmd0b24uZWR1 Cgo= --0-351460413-750893577:#20678-- From owner-pine-info@cac.washington.edu Sun Oct 17 15:00:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00157; Sun, 17 Oct 93 15:00:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17606; Sun, 17 Oct 93 14:51:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [128.193.164.25] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17600; Sun, 17 Oct 93 14:51:23 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA22690; Sun, 17 Oct 93 14:52:00 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA24269; Sun, 17 Oct 93 14:54:20 -0700 Date: Sun, 17 Oct 1993 14:53:16 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: pine.conf To: Meystel Cc: pine-info@cac.washington.edu In-Reply-To: <9310172022.AA11014@impaqt.drexel.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 17 Oct 1993, Meystel wrote: > Hi, > > I just compiled pine and I need to install pine.info and pine.conf > files in the /usr/local/lib directory, but I can't find sample > pine.conf or pine.info anywhere in the 3.87 distribution hierarchy. > Could someone please point me in the right direction? Otherwise, > the pine.debugX files keep getting bigger and bigger in each user's > directory.... To my knowledge, you create pine.info yourself... As for pine.conf, there is an option for pine to generate a fresh .pinerc...It's in the man pages...Then copy this to pine.conf and edit it to your liking... Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Sun Oct 17 19:09:30 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03386; Sun, 17 Oct 93 19:09:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18475; Sun, 17 Oct 93 18:57:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from waldorf.cc.wwu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18469; Sun, 17 Oct 93 18:57:14 -0700 Received: by waldorf.cc.wwu.edu (5.65/WWU-M1.0/UW-NDC Revision: 2.26 ) id AA17695; Sun, 17 Oct 1993 18:58:09 -0700 Date: Sun, 17 Oct 1993 18:57:09 -0700 (PDT) From: "Iain Davidson.HD/OUR" Subject: WIN-PINE: Is there Pine for Windows? To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Instead of running in a DOS box. IS there a version of Pine for windows? thanks, -iain "Info-glutton" :-P iain@wwu.edu or uw-beaver!wwu.edu!henson!iain !Sdrawkcab em DAER! <.sruoy otni em ypoc, suriv erutangis dedocne weN:GNINRAW> From owner-pine-info@cac.washington.edu Sun Oct 17 19:22:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03541; Sun, 17 Oct 93 19:22:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05027; Sun, 17 Oct 93 19:11:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05021; Sun, 17 Oct 93 19:11:02 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29853; Sun, 17 Oct 93 19:10:57 -0700 Date: Sun, 17 Oct 1993 19:10:31 -0700 (PDT) From: Terry Gray Subject: Re: WIN-PINE: Is there Pine for Windows? To: "Iain Davidson.HD/OUR" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Instead of running in a DOS box. IS there a version of Pine for windows? Not at this time... -teg From owner-pine-info@cac.washington.edu Mon Oct 18 09:10:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17993; Mon, 18 Oct 93 09:10:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10952; Mon, 18 Oct 93 08:40:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10945; Mon, 18 Oct 93 08:40:41 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA16354 (5.65b/CWI-3.3); Mon, 18 Oct 1993 16:40:31 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA15735; Mon, 18 Oct 93 15:09:18 GMT (MET) Message-Id: <9310181509.AA15735@wilg.bull.nl> To: pine-info@cac.washington.edu Subject: Problem with .lock mailbox locking Date: Mon, 18 Oct 93 16:09:16 MET From: Jos Vos I noticed the following behaviour: When I make my pine (on System V.3) setgid mail, it creates a lockfile for the INBOX (/usr/spool/mail/jos.lock on our system). In a non-setgid (non-setuid) mode, pine seems not to create a .lock file (it can't, because it doesn't have the right to write in /usr/spool/mail), but it doesn't complain! Any explanation for this behaviour? -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Mon Oct 18 12:47:46 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25942; Mon, 18 Oct 93 12:47:46 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22962; Mon, 18 Oct 93 12:34:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22956; Mon, 18 Oct 93 12:34:06 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03040; Mon, 18 Oct 93 12:33:57 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23348; Mon, 18 Oct 93 12:33:47 -0700 Date: Mon, 18 Oct 1993 11:57:01 -0700 (PDT) From: Mark Crispin Subject: re: Problem with .lock mailbox locking To: Jos Vos Cc: pine-info@cac.washington.edu In-Reply-To: <9310181509.AA15735@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 18 Oct 93 16:09:16 MET, Jos Vos wrote: > I noticed the following behaviour: > > When I make my pine (on System V.3) setgid mail, it creates a lockfile > for the INBOX (/usr/spool/mail/jos.lock on our system). > > In a non-setgid (non-setuid) mode, pine seems not to create a .lock > file (it can't, because it doesn't have the right to write in > /usr/spool/mail), but it doesn't complain! > > Any explanation for this behaviour? Yes, there is an explanation. Pine is not designed to run privileged, and some sites (as a matter of policy) protect their /usr/spool/mail directories so unprivileged processes can't create .lock files. Pine uses two forms of locking: .lock files and the flock() call. Both of these are used by various versions of /bin/mail (which is what sendmail uses for mail delivery). Since Pine has no way of knowing which form of locking mail delivery uses, it tries both. Both forms have problems. Because there are sites which deliberately, prevent the creation of .lock files, Pine can only hope that /bin/mail uses flock() locking. Otherwise, the site's policy really is ``you can't have unprivileged programs accessing mail files.'' On such a site, either you make Pine run privileged (and run the risk with doing that), or take the risk of not having effective locking, or you run Pine on another system. :-( Unfortunately, flock() (or lockf() on SysV) isn't a panacea either. It's terribly annoying for Pine to issue zillions of error messages (we know; our local computer center has the above policy) when there is nothing wrong and flock() is covering Pine's rear. Hence Pine's silence on this condition. To summarize: Pine *tries* to do .lock file locking, and always does flock() (or the SysV equivalent) locking. The only other thing to do is to have some build configuration parameter in the c-client library set what kind of locking to use. There is a problem with this. In my experience, 98% of all the people who build Pine haven't a clue of how to answer such a question, and the consequences of answering it wrong are even worse than the current status quo. We would appreciate suggestions of how to handle this any better. We don't think it is safe to make locking configurable; Pine should try all forms. We can hope that .lock file creation failure means ``don't use .lock files on this system'', based on the assumption that the only other interpretation is ``only sysadmins can write/install mail programs on this system.'' We'd lock to hear of any ``magic bullets'' that'll solve these problems! From owner-pine-info@cac.washington.edu Mon Oct 18 13:08:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26856; Mon, 18 Oct 93 13:08:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23075; Mon, 18 Oct 93 12:51:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pima.dtcc.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23069; Mon, 18 Oct 93 12:51:47 -0700 Received: by pima.dtcc.edu (5.4.2/5.40/1.0) id AA18128; Mon, 18 Oct 1993 15:51:38 -0400 Date: Mon, 18 Oct 1993 15:51:38 -0400 From: weave@pima.dtcc.edu (Ken Weaverling) Message-Id: <9310181951.AA18128@pima.dtcc.edu> In-Reply-To: Mark Crispin "re: Problem with .lock mailbox locking" (Oct 18, 11:57) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Mark Crispin , Jos Vos Subject: re: Problem with .lock mailbox locking Cc: pine-info@cac.washington.edu >>>---> On Oct 18, 11:57, Mark Crispin wrote: > > Because there are sites which deliberately, prevent the creation of .lock > files, Pine can only hope that /bin/mail uses flock() locking. Otherwise, the > site's policy really is ``you can't have unprivileged programs accessing mail > files.'' On such a site, either you make Pine run privileged (and run the > risk with doing that), or take the risk of not having effective locking, or > you run Pine on another system. :-( Hmmm, so what is the risk of setting pine setgid to mail then? > We would appreciate suggestions of how to handle this any better. We don't > think it is safe to make locking configurable; Pine should try all forms. That's understandable, but at least put a note in the docs that say if you want .lock locking, pine must be installed setgid to mail. Then those of us that do know can make an intelligent decision. -- Ken Weaverling weave@dtcc.edu Manager of Computer Services Stanton/Wilmington Campuses of Delaware Technical & Community College From owner-pine-info@cac.washington.edu Mon Oct 18 13:55:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28275; Mon, 18 Oct 93 13:55:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23411; Mon, 18 Oct 93 13:40:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23405; Mon, 18 Oct 93 13:40:00 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03092; Mon, 18 Oct 93 13:39:49 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23562; Mon, 18 Oct 93 13:39:40 -0700 Date: Mon, 18 Oct 1993 13:34:03 -0700 (PDT) From: Mark Crispin Subject: re: Problem with .lock mailbox locking To: Ken Weaverling Cc: Jos Vos , pine-info@cac.washington.edu In-Reply-To: <9310181951.AA18128@pima.dtcc.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 18 Oct 1993 15:51:38 -0400, Ken Weaverling wrote: > Hmmm, so what is the risk of setting pine setgid to mail then? Pine does nothing to prevent abuse of being setgid to mail. A setuid/setgid program is supposed to check itself to make sure that system integrity is not being compromised. Pine was not designed to run with privileges. > That's understandable, but at least put a note in the docs that say if > you want .lock locking, pine must be installed setgid to mail. Then those > of us that do know can make an intelligent decision. Some note should go into the documentation about what's going on, but I don't think that *recommending* that Pine be setgid is doing anyone any favors. Personally, I feel that protecting /usr/spool/mail is needless, not to mention obnoxious; why should a system manager take it upon himself to forbid J. Random User from writing (or using) his own mail program? But thanks for the suggestion, there *should* be some documentation. From owner-pine-info@cac.washington.edu Mon Oct 18 14:00:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28359; Mon, 18 Oct 93 14:00:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17101; Mon, 18 Oct 93 13:47:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pima.dtcc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17095; Mon, 18 Oct 93 13:47:31 -0700 Received: by pima.dtcc.edu (5.4.2/5.40/1.0) id AA18675; Mon, 18 Oct 1993 16:47:21 -0400 Date: Mon, 18 Oct 1993 16:47:21 -0400 From: weave@pima.dtcc.edu (Ken Weaverling) Message-Id: <9310182047.AA18675@pima.dtcc.edu> In-Reply-To: Mark Crispin "re: Problem with .lock mailbox locking" (Oct 18, 13:34) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Mark Crispin Subject: re: Problem with .lock mailbox locking Cc: Jos Vos , pine-info@cac.washington.edu >>>---> On Oct 18, 13:34, Mark Crispin wrote: > Personally, I feel that protecting /usr/spool/mail is needless, not to mention > obnoxious; why should a system manager take it upon himself to forbid J. > Random User from writing (or using) his own mail program? OK, I am curious now, (honest!) Are you saying that the mail spool should be 777 (or at least with the sticky bit set on)? Then if so, what is to prevent users from copying whatever files they want up to the mail spool, or someone creating a mailbox of a user that hasn't had mail delivered to them yet, chmod'ing it to 664 and then chown'ing it to that user? (Sys V allows chown by users) -- Ken Weaverling weave@dtcc.edu Manager of Computer Services Stanton/Wilmington Campuses of Delaware Technical & Community College From owner-pine-info@cac.washington.edu Mon Oct 18 15:03:22 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00674; Mon, 18 Oct 93 15:03:22 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23873; Mon, 18 Oct 93 14:47:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23867; Mon, 18 Oct 93 14:47:14 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03178; Mon, 18 Oct 93 14:47:03 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23773; Mon, 18 Oct 93 14:46:53 -0700 Date: Mon, 18 Oct 1993 13:54:39 -0700 (PDT) From: Mark Crispin Subject: re: Problem with .lock mailbox locking To: Ken Weaverling Cc: Jos Vos , pine-info@cac.washington.edu In-Reply-To: <9310182047.AA18675@pima.dtcc.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 18 Oct 1993 16:47:21 -0400, Ken Weaverling wrote: > Are you saying that the mail spool should be 777 (or at least with the > sticky bit set on)? Then if so, what is to prevent users from copying > whatever files they want up to the mail spool, or someone creating > a mailbox of a user that hasn't had mail delivered to them yet, > chmod'ing it to 664 and then chown'ing it to that user? (Sys V allows > chown by users) This is my personal opinion ONLY!!! Here's an alternative strategy: 1) Create mail files for all users, and fix any system programs which presume to delete empty mail files. [Pine does not delete empty mail files.] 2) Consider disabling chown() for users. Unprivileged chown() has several other security/denial-of-service implications, which is why BSD disabled it. If necessary, have a setuid ``safe-chown'' program that makes extra checks before doing the operation (but note that BSD users have rarely complained about its absence). 3) Make sure that your mail delivery program does not permit links to mail files, improper ownership, improper protection (600 only), etc. Have a periodic task ensure that mail files are ``proper'' and that all users have mail files (creating if necessary). Possibly also flag mail files which are caught in ``bad'' state and drop an alert to the user. 4) Put in traps to catch people who try this stunt, and bop them on the head when you catch 'em. A few well-publicized examples do wonders... 5) Educate your users about the possibilities of forged mail, and that they should cast a skeptical eye at any mail that looks ``wrong''. Maybe also educate them about not deleting their mail files. 6) Create a non-adversarial relationship with your users. It seems to me that sites that are the most concerned with preventing users from doing something that *may* be bad are the ones which end up with users who are always trying to ``beat the system''. These 6 measures will do more towards achieving a reliable mail infrastructure whose integrity is high than so-called ``magic bullets'' such as directory protections. It does require more work, which is why many sites seek out the magic bullets. But, in my opinion, the time invested in doing this is more than paid back in the long run. From owner-pine-info@cac.washington.edu Tue Oct 19 04:00:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16051; Tue, 19 Oct 93 04:00:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27108; Tue, 19 Oct 93 03:14:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cc.lut.fi by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27102; Tue, 19 Oct 93 03:14:37 -0700 Received: by cc.lut.fi (5.65c/IDA-1.4.4/Kim-2.2) id AA10374; Tue, 19 Oct 1993 12:14:25 +0200 Date: Tue, 19 Oct 1993 12:14:25 +0200 From: Hannu Martikka Message-Id: <199310191014.AA10374@cc.lut.fi> To: pine-info@cac.washington.edu Subject: re: Problem with .lock mailbox locking In-Reply-To: <9310181951.AA18128@pima.dtcc.edu>; from Ken Weaverling on 18 October 1993 15:51:38 -0400 References: <9310181951.AA18128@pima.dtcc.edu> Mailer: VM 5.35 (beta) / GNU Emacs 19.19.2 Reply-To: Hannu Martikka Organization: Lappeenranta University of Technology, Finland >>>>> "Ken" == Ken Weaverling writes: ---> On Oct 18, 11:57, Mark Crispin wrote: Ken> Hmmm, so what is the risk of setting pine setgid to mail then? In our system all the INBOX folders are rw for owner and mail-group (660). Also the /usr/spool/mail is writeble only for mail-group. If we set sgid for pine, then anyone can read any INBOX-file. :( ie. you can read other users mail... Elm works fine and it is sgid mail. Could it be possible to change pine to work correctly with sgid set? -- Regards from Goodi ______________________________________________________________________________ Internet: Hannu.Martikka@lut.fi / \ Bitnet : GOODGULF@FINFILES // \\ \-\-\-\-\-\-\ oh5lhh Hannu Martikka,Skinnarilankatu /// \\\ | on 70cm 28 F17, 53850 Lappeenranta,SF /// | \\\_____________|________________________ Home Tel. +358-(9)53-251446 | :) Lappeenranta University Of Technology | ------------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Tue Oct 19 07:06:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18934; Tue, 19 Oct 93 07:06:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28021; Tue, 19 Oct 93 06:52:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28015; Tue, 19 Oct 93 06:52:36 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25103 (5.65b/CWI-3.3); Tue, 19 Oct 1993 14:52:20 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA21470; Tue, 19 Oct 93 13:32:49 GMT (MET) Message-Id: <9310191332.AA21470@wilg.bull.nl> To: weave@pima.dtcc.edu (Ken Weaverling) Cc: Mark Crispin , pine-info@cac.washington.edu Subject: Re: Problem with .lock mailbox locking In-Reply-To: Your message of "Mon, 18 Oct 93 16:47:21 MET." <9310182047.AA18675@pima.dtcc.edu> Date: Tue, 19 Oct 93 14:32:47 MET From: Jos Vos > >>>---> On Oct 18, 13:34, Mark Crispin wrote: > > Personally, I feel that protecting /usr/spool/mail is needless, not to ment ion > > obnoxious; why should a system manager take it upon himself to forbid J. > > Random User from writing (or using) his own mail program? > > OK, I am curious now, (honest!) > > Are you saying that the mail spool should be 777 (or at least with the > sticky bit set on)? Then if so, what is to prevent users from copying > whatever files they want up to the mail spool, or someone creating > a mailbox of a user that hasn't had mail delivered to them yet, > chmod'ing it to 664 and then chown'ing it to that user? (Sys V allows > chown by users) Yes, and: I don't want my mailbox being deleted by other users! -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Tue Oct 19 07:07:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18966; Tue, 19 Oct 93 07:07:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28222; Tue, 19 Oct 93 06:52:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28216; Tue, 19 Oct 93 06:52:23 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25108 (5.65b/CWI-3.3); Tue, 19 Oct 1993 14:52:21 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA21429; Tue, 19 Oct 93 13:29:42 GMT (MET) Message-Id: <9310191329.AA21429@wilg.bull.nl> To: Mark Crispin Cc: pine-info@cac.washington.edu Subject: Re: Problem with .lock mailbox locking In-Reply-To: Your message of "Mon, 18 Oct 93 11:57:01 MET." Date: Tue, 19 Oct 93 14:29:40 MET From: Jos Vos > To summarize: Pine *tries* to do .lock file locking, and always does flock() > (or the SysV equivalent) locking. Unfortunately, *trying* to lock means existing .lock files are not honoured, isn't it? So, when mail is just delivered to your INBOX, Pine doesn't matter :-( -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Tue Oct 19 07:08:23 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18996; Tue, 19 Oct 93 07:08:23 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28230; Tue, 19 Oct 93 06:52:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28224; Tue, 19 Oct 93 06:52:37 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25098 (5.65b/CWI-3.3); Tue, 19 Oct 1993 14:52:20 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA21454; Tue, 19 Oct 93 13:31:28 GMT (MET) Message-Id: <9310191331.AA21454@wilg.bull.nl> To: weave@pima.dtcc.edu (Ken Weaverling) Cc: Mark Crispin , pine-info@cac.washington.edu Subject: Re: Problem with .lock mailbox locking In-Reply-To: Your message of "Mon, 18 Oct 93 15:51:38 MET." <9310181951.AA18128@pima.dtcc.edu> Date: Tue, 19 Oct 93 14:31:27 MET From: Jos Vos > > files.'' On such a site, either you make Pine run privileged (and run the > > risk with doing that), or take the risk of not having effective locking, or > > you run Pine on another system. :-( > > Hmmm, so what is the risk of setting pine setgid to mail then? > > > We would appreciate suggestions of how to handle this any better. We don't > > think it is safe to make locking configurable; Pine should try all forms. > > That's understandable, but at least put a note in the docs that say if > you want .lock locking, pine must be installed setgid to mail. Then those > of us that do know can make an intelligent decision. I assume that making Pine setgid mail does not solve the problem. When a lock exists, it'll just ignore it anyway. Or am I wrong (I didn't dig into the coding details yet)? -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Tue Oct 19 08:44:35 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21000; Tue, 19 Oct 93 08:44:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28484; Tue, 19 Oct 93 08:24:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28478; Tue, 19 Oct 93 08:24:48 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05358; Tue, 19 Oct 93 08:24:37 -0700 Date: Tue, 19 Oct 1993 08:21:00 -0700 (PDT) From: Mark Crispin Subject: Re: Problem with .lock mailbox locking To: Jos Vos Cc: pine-info@cac.washington.edu In-Reply-To: <9310191329.AA21429@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 19 Oct 93 14:29:40 MET, Jos Vos wrote: > Unfortunately, *trying* to lock means existing .lock files are > not honoured, isn't it? > So, when mail is just delivered to your INBOX, Pine doesn't matter :-( No. The decision to give up on .lock file locking happens at a very specific point; that is, when an attempt is make to create a .lock file and the operating system returns a ``protection violation'' (EACCES) error. In ALL other cases, .lock file locking is enforced. This includes the case when there is an existing .lock file. In other words, Pine will not tromp upon some other program which has the file locked. But, if Pine is unable to make the .lock file, some othe program may tromp upon Pine. From owner-pine-info@cac.washington.edu Tue Oct 19 09:28:30 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22477; Tue, 19 Oct 93 09:28:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28791; Tue, 19 Oct 93 09:11:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from deneb.mc.duke.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28785; Tue, 19 Oct 93 09:11:18 -0700 Received: by deneb.mc.duke.edu (5.65/DEC-Ultrix/4.3) id AA12412; Tue, 19 Oct 1993 12:09:57 -0400 Date: Tue, 19 Oct 1993 12:08:00 -0400 (EDT) From: "James D. Dryfoos" Subject: Problem displaying a mime part with Pine 3.85 on Ultrix. To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have received the following mail for which Pine will not display the second part: Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H4ANPTDBWW001DXP@mc.duke.edu>; Tue, 19 Oct 1993 11:54:16 EST Date: Tue, 19 Oct 1993 11:54:16 -0500 (EST) From: PMDF Mail Server Subject: Undeliverable RFC822 mail: temporarily unable to deliver To: postmaster@mc.duke.edu, DRYFO001@mc.duke.edu Message-Id: <01H4ANRCVGSA001DXP@mc.duke.edu> Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID 0Qx4SUbncDMWrmGe5IL8gg)" --Boundary (ID 0Qx4SUbncDMWrmGe5IL8gg) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Your message could not be delivered to: WIGGI001@hermes1.mc.duke.edu Your message has been enqueued and undeliverable for 1 hour. The mail system will continue to try to deliver your message for an additional 287 hours. --Boundary (ID 0Qx4SUbncDMWrmGe5IL8gg) Content-type: MESSAGE/SAMPLE Received: from deneb.mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H4AKCA6BB4001CDL@mc.duke.edu>; Tue, 19 Oct 1993 10:15:50 EST Received: by deneb.mc.duke.edu (5.65/DEC-Ultrix/4.3) id AA12145; Tue, 19 Oct 1993 10:07:53 -0400 Date: Tue, 19 Oct 1993 10:07:36 -0400 (EDT) From: "James D. Dryfoos" Subject: Phone number? To: wiggi001@mc.duke.edu Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT What is your phone number here in Fu? ======================================================================= James D. Dryfoos | dryfo001@mc.duke.edu Duke University Medical Center | dryfo001@dukemc.bitnet 2200 West Main Street | Suite 450 Room 36A | (919) 286-6391 - office Durham, NC 27705 Earth | (919) 286-6369 - fax ======================================================================= From owner-pine-info@cac.washington.edu Tue Oct 19 09:29:21 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22519; Tue, 19 Oct 93 09:29:21 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28803; Tue, 19 Oct 93 09:13:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from deneb.mc.duke.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28797; Tue, 19 Oct 93 09:13:02 -0700 Received: by deneb.mc.duke.edu (5.65/DEC-Ultrix/4.3) id AA12418; Tue, 19 Oct 1993 12:11:39 -0400 Date: Tue, 19 Oct 1993 12:11:22 -0400 (EDT) From: "James D. Dryfoos" Reply-To: "James D. Dryfoos" Subject: What I see (part 2 of previous message). To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Here is what I do see in Pine: Date: Tue, 19 Oct 1993 11:54:38 -0500 (EST) From: PMDF Mail Server To: postmaster@mc.duke.edu, DRYFO001@mc.duke.edu Subject: Undeliverable RFC822 mail: temporarily unable to deliver Parts/attachments: 1 Shown 7 lines Text 2 Shown 1 KB Message ---------------------------------------- Your message could not be delivered to: GENTR001@hermes1.mc.duke.edu Your message has been enqueued and undeliverable for 1 hour. The mail system will continue to try to deliver your message for an additional 287 hours. ----- Part 2 "Included Message" ----- From owner-pine-info@cac.washington.edu Tue Oct 19 21:46:10 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12435; Tue, 19 Oct 93 21:46:10 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12237; Tue, 19 Oct 93 21:32:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12231; Tue, 19 Oct 93 21:32:44 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA08272 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Tue, 19 Oct 93 23:32:36 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA21067; Tue, 19 Oct 93 23:32:35 CDT Date: Tue, 19 Oct 1993 23:29:36 -0500 (CDT) From: Matt Simmons Subject: Pine NNTP newsreading To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Does pine check periodically for new news like it does for new mail? Can it be set to? Could it be set to check the currently active newsgroup for new news? Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Wed Oct 20 03:18:11 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18413; Wed, 20 Oct 93 03:18:11 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04229; Wed, 20 Oct 93 03:02:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04223; Wed, 20 Oct 93 03:02:24 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA24837 (5.65b/CWI-3.3); Wed, 20 Oct 1993 11:02:22 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA26692; Wed, 20 Oct 93 09:46:08 GMT (MET) Message-Id: <9310200946.AA26692@wilg.bull.nl> To: pine-info@cac.washington.edu Subject: Pine being setgid mail (was: .lock mailbox locking) Date: Wed, 20 Oct 93 10:46:06 MET From: Jos Vos Some good and some bad news. The good news is that making "pine" setgid mail (on System V systems) makes .lock mailbox locking work fine. Although it ignores failing .lock mailbox locking when the access is prohibited (i.e., when pine is not setgid mail and the mail directory is 775, is it should be), it honours existing .lock files and it creates its own .lock file if necessary. Now the bad news. When pine is setgid mail, I can read evertbody's mailbox. I did this by creating a symlink in my $HOME/mail directory to another user's mailbox. This is a *serious* security problem: System V mail locking is based on .lock files, basically, and this *should* work properly. -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Wed Oct 20 07:26:02 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22859; Wed, 20 Oct 93 07:26:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05216; Wed, 20 Oct 93 07:05:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pima.dtcc.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05210; Wed, 20 Oct 93 07:05:04 -0700 Received: by pima.dtcc.edu (5.4.2/5.40/1.0) id AA24946; Wed, 20 Oct 1993 10:05:00 -0400 Date: Wed, 20 Oct 1993 09:45:24 -0400 (EDT) From: Ken Weaverling Subject: Pine NNTP newsreading To: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Some problems with 3.87 and NNTP news-reading. The command 'mode reader' should be issued after connecting to NNTP port in case the host running the remote news reader also happens to feed the local host. This is peculiar to INN sites, and it is not a common occurance even at INN sites. (If another site is feeding your local site, you would normally read from your normal site, not the remote site.) However, I am in the process of migating from one system to another and attempting to move users slowly, so this situation currently exists. It shouldn't be hard to add, and just ignore any error message from a non INN site. What I get now is 'Group not implemented error' Another issue. I defined in the global pine-info file... news-collections=Local-News *[dtcc.*] When I expand the folder, it does list the local groups, but when I select a group, all of the messages in the index say [No Message Text Available]. However, if I change it to be news-collections=Local-News *[] It works fine or news-collections=Local-News *{news.dtcc.edu/nntp}[dtcc.*] it also works fine. NOTE: I want to break up the news stuff into the top level groups because if they are all in one, then it takes forever to expand the folder. Ken Weaverling weave@dtcc.edu Manager of Computer Services Stanton/Wilmington Campuses of Delaware Technical & Community College From owner-pine-info@cac.washington.edu Wed Oct 20 07:38:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23169; Wed, 20 Oct 93 07:38:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16466; Wed, 20 Oct 93 07:18:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pima.dtcc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16460; Wed, 20 Oct 93 07:18:45 -0700 Received: by pima.dtcc.edu (5.4.2/5.40/1.0) id AA25088; Wed, 20 Oct 1993 10:18:43 -0400 Date: Wed, 20 Oct 1993 10:14:32 -0400 (EDT) From: Ken Weaverling Subject: Keyboard locking in 3.87 To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Unfortunately, I personally wish the login password was still used for keyboard locking instead of asking the user to type the password in. I have already had someone forget the password they used. I guess this is to eventually make it compatible with DOS platform, but I hate bringing this to the lowest common denominator. At least, if you have to have users enter the password, have them do it twice to check for typos. (Of course, maybe they will just enter it once and leave, which will basically make the computer not secure if it is left prompting for confirmation of password.) I also miss the screen showing disk space used, mail space used, and quota information. I did modify the sources to show percentage of quota used when they start up pine, instead of just displaying when they go above the soft limit. (This is all on DG/UX, which can have a hard quota (cpd) but no idea of a soft quota anyway). Ken Weaverling weave@dtcc.edu Manager of Computer Services Stanton/Wilmington Campuses of Delaware Technical & Community College From owner-pine-info@cac.washington.edu Wed Oct 20 09:56:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28285; Wed, 20 Oct 93 09:56:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19187; Wed, 20 Oct 93 09:32:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19181; Wed, 20 Oct 93 09:32:54 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA27542; Wed, 20 Oct 93 09:32:44 PDT Received: from hal.usc.edu by Law.USC.EDU (4.1/SMI-4.1) id AA03012; Wed, 20 Oct 93 09:32:42 PDT Received: by hal.usc.edu (4.1/SMI-4.1) id AA21958; Wed, 20 Oct 93 09:32:41 PDT Date: Wed, 20 Oct 1993 09:24:08 -0700 (PDT) From: Elmar Kurgpold Subject: Re: Keyboard locking in 3.87 To: Ken Weaverling Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 20 Oct 1993, Ken Weaverling wrote: > Unfortunately, I personally wish the login password was still used for > keyboard locking instead of asking the user to type the password in. I > have already had someone forget the password they used. I guess this is > to eventually make it compatible with DOS platform, but I hate bringing > this to the lowest common denominator. I have to agree with this. What I have been doing when a user forgets her or his temporary password is killing their pine process so they can start another one. It seems to be the safest thing to do in our situation, but our sysadmins aren't on call after hours. > > At least, if you have to have users enter the password, have them do it > twice to check for typos. (Of course, maybe they will just enter it once > and leave, which will basically make the computer not secure if it is left > prompting for confirmation of password.) > If you don't use the login password, typing the password twice is the de facto standard, no matter how annoying it might be. ------------------------------------- | Elmar Kurgpold | | Network Administrator | | University of Southern California | | The Law Center | | ekurgpol@Law.USC.EDU | | (213)740-2571 FAX: (213)740-5502 | ------------------------------------- From owner-pine-info@cac.washington.edu Wed Oct 20 14:02:42 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06772; Wed, 20 Oct 93 14:02:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07397; Wed, 20 Oct 93 13:47:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07391; Wed, 20 Oct 93 13:47:09 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07409; Wed, 20 Oct 93 13:47:00 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03370; Wed, 20 Oct 93 13:46:53 -0700 Date: Wed, 20 Oct 1993 13:45:37 -0700 (PDT) From: Mark Crispin Subject: re: Problem displaying a mime part with Pine 3.85 on Ultrix. To: "James D. Dryfoos" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Thank you for making us aware of the problem with body parts of type MESSAGE/SAMPLE (and its official successor, MESSAGE/RFC822-FRAGMENT) not displaying in Pine. This problem will be fixed in a future release of Pine. From owner-pine-info@cac.washington.edu Wed Oct 20 14:25:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07761; Wed, 20 Oct 93 14:25:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07503; Wed, 20 Oct 93 14:07:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07497; Wed, 20 Oct 93 14:07:01 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07427; Wed, 20 Oct 93 14:06:54 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03434; Wed, 20 Oct 93 14:06:43 -0700 Date: Wed, 20 Oct 1993 13:47:51 -0700 (PDT) From: Mark Crispin Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: Jos Vos Cc: pine-info@cac.washington.edu In-Reply-To: <9310200946.AA26692@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Pine is not intended to run with any setuid and setgid privileges. Nor is imapd. It is questionable that an improvment to system security is made by creating a requirement that all mail-reading programs run with privileges. It is even more questionable that security is enhanced by granting privileges to software other than that provided by your vendor. The infamous bug with the ``move-mail'' program, used by the cracker in ``The Cuukoo's Egg'', suggests the great danger of requiring privileges in order to enable fundamental user tasks such as mail reading. It should be noted that move-mail itself was designed to be a ``safe'' privileged program to do a particular task that required privileges so the main program did not need any privileges. Pine has always supported .lock files. This are one of the fundamental aspects of locking in the mbox format. The problem is that an unprivileged program is not allowed to create .lock files on your system, because of the bad protection you have placed on the /usr/spool/mail directory. A separate message outlined an alternative strategy for dealing with the problem of a mischeivous user being able to create a mail file for someone else. Although this strategy is more complex, I urge you to give it serious consideration. Please also consider the great danger of having to give many mail programs privileged access. I will suggest to my co-workers about the possibility of making Pine and imapd safe to run with setgid privileges. It would be a great deal of work to make these programs privilege-safe, and the problem can be solved by an alternative configuration on your system. So I can't make any promises. If you have any further questions, please do not hesitate to ask. From owner-pine-info@cac.washington.edu Wed Oct 20 14:55:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08643; Wed, 20 Oct 93 14:55:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07713; Wed, 20 Oct 93 14:42:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07707; Wed, 20 Oct 93 14:42:46 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07449; Wed, 20 Oct 93 14:42:39 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03530; Wed, 20 Oct 93 14:42:32 -0700 Date: Wed, 20 Oct 1993 14:11:07 -0700 (PDT) From: Mark Crispin Subject: re: Pine NNTP newsreading To: Matt Simmons Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 19 Oct 1993 23:29:36 -0500 (CDT), Matt Simmons wrote: > Does pine check periodically for new news like it does for new mail? Can > it be set to? Could it be set to check the currently active newsgroup > for new news? Hi. At the present time, Pine does not check for new news. It can be done, although there are certain technical difficulties, in the IMAP and local news case. I don't think it can be done in the NNTP case without re-selecting the newsgroup (this is why the NNTP version of rn doesn't offer this). We will consider this as a new feature to implement in a future version of Pine. From owner-pine-info@cac.washington.edu Wed Oct 20 20:15:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20111; Wed, 20 Oct 93 20:15:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09412; Wed, 20 Oct 93 20:03:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09405; Wed, 20 Oct 93 20:03:52 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA08330; Wed, 20 Oct 93 20:03:45 -0700 Date: Wed, 20 Oct 1993 19:58:55 -0700 (PDT) From: Mark Crispin Subject: re: Pine NNTP newsreading To: Ken Weaverling Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 20 Oct 1993 09:45:24 -0400 (EDT), Ken Weaverling wrote: > The command 'mode reader' should be issued after connecting to NNTP port This change will be in Pine 3.88. Thank you for reporting this. > I defined in the global pine-info file... > news-collections=Local-News *[dtcc.*] > When I expand the folder, it does list the local groups, but when I select > a group, all of the messages in the index say [No Message Text Available]. > However, if I change it to be > news-collections=Local-News *[] > It works fine or > news-collections=Local-News *{news.dtcc.edu/nntp}[dtcc.*] > it also works fine. We are still investigating this problem. Am I correct in believing that on the local machine, you have a /usr/spool/news directory tree and a /usr/lib/news/active file? Is the local machine also the NNTP server? From owner-pine-info@cac.washington.edu Wed Oct 20 22:03:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22511; Wed, 20 Oct 93 22:03:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09908; Wed, 20 Oct 93 21:51:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hopi.dtcc.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09902; Wed, 20 Oct 93 21:51:46 -0700 Received: by hopi.dtcc.edu (5.4R2.01/200.1.1.4) id AA15631; Thu, 21 Oct 1993 00:51:43 -0400 Date: Thu, 21 Oct 1993 00:48:37 -0400 (EDT) From: Ken Weaverling Subject: re: Pine NNTP newsreading To: Mark Crispin Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 20 Oct 1993, Mark Crispin wrote: > > I defined in the global pine-info file... > > news-collections=Local-News *[dtcc.*] > > When I expand the folder, it does list the local groups, but when I select > > a group, all of the messages in the index say [No Message Text Available]. > > However, if I change it to be > > news-collections=Local-News *[] > > It works fine or > > news-collections=Local-News *{news.dtcc.edu/nntp}[dtcc.*] > > it also works fine. > > We are still investigating this problem. Am I correct in believing that on > the local machine, you have a /usr/spool/news directory tree and a > /usr/lib/news/active file? Is the local machine also the NNTP server? No, it wasn't, but I symlinked it and no difference. Besids, I can almost guarantee that I altered defines in the code to point to the right place. More weirdness, With just... news-collections=Local-News *[] some groups with small number of articles has the empty text message, and then those with more articles could have the same article duplicated for ~40 messages, then another set of ~40 duplicates. And yes, the local machine is also the NNTP server. If I set it up for nntp access, it works fine. From owner-pine-info@cac.washington.edu Wed Oct 20 22:21:03 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22891; Wed, 20 Oct 93 22:21:03 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10006; Wed, 20 Oct 93 22:11:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10000; Wed, 20 Oct 93 22:11:32 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA08641; Wed, 20 Oct 93 22:11:25 -0700 Date: Wed, 20 Oct 1993 22:09:13 -0700 (PDT) From: Mark Crispin Subject: re: Pine NNTP newsreading To: Ken Weaverling Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This is *seriously* wierd. Can you give me access to your machine and definite instructions on how to reproduce it? Is there any possibility that you might have made a mistake in your alteration of the defines in the code? This looks very much to me as being symptomatic of it not accessing the news spool files properly. From owner-pine-info@cac.washington.edu Thu Oct 21 02:18:09 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27586; Thu, 21 Oct 93 02:18:09 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10919; Thu, 21 Oct 93 02:10:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cheviot.ncl.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10913; Thu, 21 Oct 93 02:10:10 -0700 Received: from (scawdell.ncl.ac.uk) by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 ) with SMTP; Thu, 21 Oct 1993 10:10:00 +0100 Date: Thu, 21 Oct 1993 09:41:20 +0100 (BST) From: "A. Hilborne" Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: Mark Crispin Cc: Jos Vos , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have read your three messages on this subject. I must say I was initially surprised that pine doesn't run setgid. I must be one among many who can't really contemplate using your "alternative strategy." Mail is only one of many services here and we can't put that much effort into something which only improves, rather than fixes matters. Nor do we want a situation in which we have to continually create ~ 5,000 (mainly empty) mailboxes in our spool area! You suggest disabling chown. To do this effectively would mean a kernel change. You suggest we should endeavour to create a non-adversarial relationship with our users: I wholeheartedly agree here, but university students _will_ sometimes try to break security, whatever we do. We are fortunate: both our main system types (HP-UX and SunOS) support the alternative meaning of the sticky bit on directories, so we are partially protected from abuses of a rwxrwxrwx mail spool. We still aren't fully protected against users who create "false" mailboxes on behalf of others. What to do? Given an adequate modern Unix which will allow a setuid-program to switch back and forth between identities there is no need for such a program to "check itself to make sure that system integrity is not being compromised," except inside the "security box" in the program. Everywhere else the program runs with normal user privileges. Some additional care also needs to be taken with system resources (such as file descriptors) which are acquired inside the security box but used outside of it. Clearly such a restructuring of Pine would be a lot of work, but the result needn't be much more dangerous running setgid than Pine is now. -- Andrew M. Hilborne Andrew.Hilborne@newcastle.ac.uk Computing Service Tel: +44 91 222 8226 (direct) University of Newcastle upon Tyne, UK. +44 91 222 8039 (Comp Service office) From owner-pine-info@cac.washington.edu Thu Oct 21 04:26:44 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00230; Thu, 21 Oct 93 04:26:44 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11531; Thu, 21 Oct 93 04:17:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11521; Thu, 21 Oct 93 04:17:31 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA08941; Thu, 21 Oct 93 04:16:51 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA05882; Thu, 21 Oct 93 04:16:04 -0700 Date: Thu, 21 Oct 1993 03:00:49 -0700 (PDT) From: Mark Crispin Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: "A. Hilborne" Cc: Jos Vos , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The fact is, making your /usr/spool/mail directory protected 775 does *not* ``fix matters''. It breaks matters in two related ways: 1) Unprivileged programs can not be mail readers. So, if someone has a neat idea for the Ultimate Mail Reader, he cannot write it on your system, because your system's policy prevents it. If he sees a new nifty mail program on the net, he can't just FTP it to his directory and run it, because only programs that the system manager approves can be mailers. 2) All mail readers must be privileged, and the slightest oversight in ANY single mail reader compromises your entire system. How many more horror stories do there have to be about the setuid program that allowed you to spawn a root shell with !, before people realize how serious a problem this is? I hardly call this an ``improvement'', much less a ``fix''. It creates adversarial relationships and provides multiple stress points that can be tested for weaknesses. I have discussed the question of making Pine be set[gu]id safe with my co- workers, and I'll bring it up with our boss. No decision has been made. If done, it is going to be a tremendous amount of work, now and in the future. We have a very long ``to-do'' list of feature enhancements and bugs to be fixed. Should we divert our limited resources for several months (or longer) towards an effort that adds no user function and is unnecessary with better site management? Would offering a /bin/mail substitute (you would edit your sendmail.cf to run it instead of /bin/mail) that protects against mail being delivered to false mailboxes be a satisfactory alternate? We can offer this in a finite amount of time. This would fix the problem without requiring that mail readers run with privileges. Regards, -- Mark -- From owner-pine-info@cac.washington.edu Thu Oct 21 05:35:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01375; Thu, 21 Oct 93 05:35:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11739; Thu, 21 Oct 93 05:27:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sws1.CTD.ORNL.GOV by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11733; Thu, 21 Oct 93 05:27:23 -0700 Received: from localhost (s4i@localhost) by sws1.ctd.ornl.gov (8.6.2/8.6.2) id IAA08422 for pine-info@cac.washington.edu; Thu, 21 Oct 1993 08:27:20 -0400 Date: Thu, 21 Oct 1993 08:27:20 -0400 From: Jim Simmons Message-Id: <199310211227.IAA08422@sws1.ctd.ornl.gov> To: pine-info@cac.washington.edu Subject: (fwd) Problems with 3.87 on a Sun Newsgroups: ornl.mail.pine-info I've seen a couple of problems with pine 3.87 on a Sun Sparc 10 (running SunOS 4.1.3). First, it appears that when you save a message to another folder, the saved message gets marked as New, even though you've already read it. This is not the way it worked in 3.07. Is this normal? Also, we've been having trouble with users who apparently loose their connection (they're calling in through modems) and their pine process doesn't disappear. Sometimes it not only doesn't disappear, but apparently goes into a loop using up as much CPU time as it can get. Any ideas what may be happening? Thanks, Jim (s4i@ornl.gov) From owner-pine-info@cac.washington.edu Thu Oct 21 06:32:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02011; Thu, 21 Oct 93 06:32:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11947; Thu, 21 Oct 93 06:20:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11941; Thu, 21 Oct 93 06:20:41 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #101) id m0opzwW-000036C; Thu, 21 Oct 93 14:20 BST Message-Id: Subject: We have problems with 3.87 (Sun) too To: pine-info@cac.washington.edu Date: Thu, 21 Oct 1993 14:20:39 +0100 (BST) From: kmj1000@cus.cam.ac.uk (Kate M Jeary) X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 738 specifically, pine processes started up over dialup don't always exit cleanly. This was true of 3.85 as well; my machines are 10/51s running SunOs 4.1.3, similar to the previous message. They loop; each one puts on an average of 1 load point (a nuisance on these systems) until eventually killed either by me or other checks I run. The last time I saw this was with the occasional X11R4 process; X11R5 doesn't in general. It's a nuisance. I haven't yet noted the 'new' problem. I suspect that will be true as well. -- Internet: K.M.Jeary@ucs.cam.ac.uk University Computing Service, JANET: K.M.Jeary@uk.ac.cam.ucs Computer Laboratory, Pembroke St, Phone: +44 223 334447 Cambridge CB2 3QG, England. From owner-pine-info@cac.washington.edu Thu Oct 21 07:01:53 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02396; Thu, 21 Oct 93 07:01:53 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12054; Thu, 21 Oct 93 06:49:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cc.lut.fi by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12048; Thu, 21 Oct 93 06:49:32 -0700 Received: by cc.lut.fi (5.65c/IDA-1.4.4/Kim-2.2) id AA13340; Thu, 21 Oct 1993 15:49:13 +0200 Date: Thu, 21 Oct 1993 15:49:13 +0200 From: Hannu Martikka Message-Id: <199310211349.AA13340@cc.lut.fi> To: pine-info@cac.washington.edu Subject: re: Pine being setgid mail (was: .lock mailbox locking) In-Reply-To: ; from Mark Crispin on 21 October 1993 03:00:49 -0700 References: Mailer: VM 5.35 (beta) / GNU Emacs 19.19.2 Reply-To: Hannu Martikka Organization: Lappeenranta University of Technology, Finland Could it be possible to use some small external program from pine to handle locking? -- Regards from Goodi ______________________________________________________________________________ Internet: Hannu.Martikka@lut.fi / \ Bitnet : GOODGULF@FINFILES // \\ \-\-\-\-\-\-\ oh5lhh Hannu Martikka,Skinnarilankatu /// \\\ | on 70cm 28 F17, 53850 Lappeenranta,SF /// | \\\_____________|________________________ Home Tel. +358-(9)53-251446 | :) Lappeenranta University Of Technology | ------------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Thu Oct 21 07:04:08 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02505; Thu, 21 Oct 93 07:04:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07229; Thu, 21 Oct 93 06:48:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07221; Thu, 21 Oct 93 06:48:20 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <25038-0@dummy1.dur.ac.uk>; Thu, 21 Oct 1993 14:47:40 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Thu, 21 Oct 93 14:47:35 BST Date: Thu, 21 Oct 1993 14:36:57 +0100 (BST) From: Barry Cornelius Subject: Re: (fwd) Problems with 3.87 on a Sun To: Jim Simmons Cc: pine-info@cac.washington.edu In-Reply-To: <199310211227.IAA08422@sws1.ctd.ornl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 21 Oct 1993, Jim Simmons wrote: > Also, we've been having trouble with users who apparently loose their > connection (they're calling in through modems) and their pine process doesn't > disappear. Sometimes it not only doesn't disappear, but apparently goes into > a loop using up as much CPU time as it can get. Any ideas what may be > happening? We also have been having problems with Pine causing processes gobbling up cpu time. This is with Pine 3.85 running on a SunOS 4.1.3 computer (called vega). I noticed 3 process like this a few weeks ago, one last Sunday and 3 today. When this first occurred on 1st October, I reported it to pine-bugs@cac.washington.edu. I haven't managed to track down where the problem lies. However, it seems to occur when Pine is trying to write to the screen when the person running Pine has logged out by some means. It then seems to get into a closed loop (aka infinite loop). I have put the output from SunOS's trace command for one of the runaway processes below. The lines given below are repeatedly output. vega# trace -p 4413 Process 4413 attached - interrupt to quit setitimer (0, 0xefffed28, 0xefffed18) = 0 getpid () = 4413 kill (4413, 1) = - SIGHUP (1) sigcleanup () = 0 setitimer (0, 0xefffed28, 0xefffed18) = 0 write (1, "\33[7m\33[m\7\33[22;1H\33[K", 18) = -1 EIO (I/O error) write (1, "\33[7mA directory is selected, ent".., 95) = -1 EIO (I/O error) sigblock (0) = 0 sigstack (0, 0xefffed2c) = 0 setitimer (0, 0xefffed28, 0xefffed18) = 0 getpid () = 4413 ... -- Barry Cornelius Electronic mail: Barry.Cornelius@durham.ac.uk Post: Computing Service, University of Durham, Durham, DH1 3LE, England Phone: Durham (091 or +44 91) 374 4717, Secretary:374 2892, Fax:374 3741 From owner-pine-info@cac.washington.edu Thu Oct 21 08:27:23 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04118; Thu, 21 Oct 93 08:27:23 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08104; Thu, 21 Oct 93 08:07:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from runix.runit.sintef.no by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08083; Thu, 21 Oct 93 08:05:51 -0700 Received: from runit.sintef.no by runix.runit.sintef.no id <19521-0@runix.runit.sintef.no>; Thu, 21 Oct 1993 16:03:38 +0100 Date: Thu, 21 Oct 1993 15:58:26 +0100 (MET) From: Steinar Haug Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: "A. Hilborne" Cc: Mark Crispin , Jos Vos , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > You suggest disabling chown. To do this effectively would mean a kernel > change. You write later that your main systems are HP-UX and SunOS. You certainly don't need a kernel change for these systems! - For SunOS 4.1.x, chown to another user is *not* allowed, ie it follows the BSD standard, not the System V standard. - For HP-UX, chown to another user is by default allowed. It can easily be turned off by creating /etc/privgroup which contains *one* line: -n CHOWN If you want programs which are setgid to mail (eg. /bin/rmail) to be able to do chown, you need: -n CHOWN mail CHOWN In both cases, extremely easy. Steinar Haug, system/networks administrator SINTEF RUNIT, University of Trondheim, NORWAY Email: Steinar.Haug@runit.sintef.no, Steinar.Haug@delab.sintef.no From owner-pine-info@cac.washington.edu Thu Oct 21 08:55:07 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05152; Thu, 21 Oct 93 08:55:07 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08560; Thu, 21 Oct 93 08:35:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pitt.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08550; Thu, 21 Oct 93 08:35:13 -0700 Received: by pitt.edu id AA04585 (5.65c/IDA-1.4.4.5 for pine-info@cac.washington.edu); Thu, 21 Oct 1993 11:35:11 -0400 Received: via switchmail; Thu, 21 Oct 1993 11:35:11 -0400 (EDT) Received: from aquamarine.cis.pitt.edu via qmail ID ; Thu, 21 Oct 1993 11:33:59 -0400 (EDT) Received: from aquamarine.cis.pitt.edu via qmail ID ; Thu, 21 Oct 1993 11:33:54 -0400 (EDT) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.aquamarine.cis.pitt.edu.sun4c.411 via MS.5.6.aquamarine.cis.pitt.edu.sun4_41; Thu, 21 Oct 1993 11:33:54 -0400 (EDT) Message-Id: Date: Thu, 21 Oct 1993 11:33:54 -0400 (EDT) From: "Jeffrey J. Carpenter" Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: pine-info@cac.washington.edu Subject: Problem with sending mail in OLD version of pine Hi, I am in the process of building the new version of pine, but right now we are still running 3.03 (I know, we need to upgrade it). We have seen an occasional problem where when someone sends a message, the text of the message is replaced with the name of the smtp server. Our smtp server is smtp.pitt.edu, so the message would be something like: To: blah From: la la la Subject: test Date: ... smtp.pitt.edu The debug file from a session where this type of message was delivered looks normal. We cannot reliably reproduce this. Is this something that was previously reported and fixed? jeff From owner-pine-info@cac.washington.edu Thu Oct 21 09:25:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06304; Thu, 21 Oct 93 09:25:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09269; Thu, 21 Oct 93 09:08:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09263; Thu, 21 Oct 93 09:07:58 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06501; Thu, 21 Oct 93 09:07:48 -0700 Date: Thu, 21 Oct 1993 09:03:41 -0700 (PDT) From: David L Miller Subject: Re: (fwd) Problems with 3.87 on a Sun To: Jim Simmons Cc: pine-info@cac.washington.edu In-Reply-To: <199310211227.IAA08422@sws1.ctd.ornl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Both of these are known problems. The saved message problem will be fixed in an upcoming release, but it is not a trivial change. The looping problem on disconnection will be fixed in the upcoming Pine 3.88 maintenance release. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 21 Oct 1993, Jim Simmons wrote: > I've seen a couple of problems with pine 3.87 on a Sun Sparc 10 (running > SunOS 4.1.3). > > First, it appears that when you save a message to another folder, the > saved message gets marked as New, even though you've already read it. This > is not the way it worked in 3.07. Is this normal? > > Also, we've been having trouble with users who apparently loose their > connection (they're calling in through modems) and their pine process doesn't > disappear. Sometimes it not only doesn't disappear, but apparently goes into > a loop using up as much CPU time as it can get. Any ideas what may be > happening? > > Thanks, > > Jim (s4i@ornl.gov) From owner-pine-info@cac.washington.edu Thu Oct 21 09:26:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06340; Thu, 21 Oct 93 09:26:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09345; Thu, 21 Oct 93 09:11:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nexus.yorku.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09339; Thu, 21 Oct 93 09:11:13 -0700 Received: from vortex.yorku.ca ([130.63.232.15]) by nexus.yorku.ca with SMTP id <9222>; Thu, 21 Oct 1993 12:11:06 -0400 Received: by vortex.yorku.ca (4.1/SMI-4.1) id AA19885; Thu, 21 Oct 93 12:10:14 EDT Date: Thu, 21 Oct 1993 11:59:47 -0400 From: Ian Lumb Subject: Re: (fwd) Problems with 3.87 on a Sun To: PINE INFO Cc: UNICAAT Unix Team In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We've also noticed the same problem here on a Sun 10/30 running SunOS 4.1.3. I hesitated in posting a message to this discussion group, as I _thought_ that the problem may have been specific to our users connecting to our Sun host via Novell ethernet. Ian. -- Ian Lumb Internet: Earth & Atmospheric Science, York University North York, Ontario M3J 1P3, CANADA Voice: (416) 736-5245; Fax: (416) 736-5817 From owner-pine-info@cac.washington.edu Thu Oct 21 09:50:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07307; Thu, 21 Oct 93 09:50:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09673; Thu, 21 Oct 93 09:25:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09659; Thu, 21 Oct 93 09:25:14 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA22892 (5.65b/CWI-3.3); Thu, 21 Oct 1993 17:25:06 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05511; Thu, 21 Oct 93 16:14:47 GMT (MET) Message-Id: <9310211614.AA05511@wilg.bull.nl> To: Mark Crispin Cc: pine-info@cac.washington.edu Subject: Re: Pine being setgid mail (was: .lock mailbox locking) In-Reply-To: Your message of "Wed, 20 Oct 93 13:47:51 MET." Date: Thu, 21 Oct 93 17:14:45 MET From: Jos Vos > I will suggest to my co-workers about the possibility of making Pine and > imapd safe to run with setgid privileges. It would be a great deal of work t > make these programs privilege-safe, and the problem can be solved by an > alternative configuration on your system. So I can't make any promises. I've made a quick hack to temporarily solve the problem: - Pine (and other programs opening folders) run setgid mail, being compiled with SETGID_HACK set. - In main() the first thing to do is to save the effective gid, and do a setgid(getgid()) (disable the setgid stuff). - In the lock and unlock functions I temporarily restore the saved effective gid when performing the actual locking/unlocking actions. - This means that, except for the small pieces of code doing the (un)locking, pine runs with the real gid, and opening another person's mailbox is impossible. - All the stuff still works as before when not running setgid mail. Then the effective gid is the same as the real gid, so all setgid() actions are in fact a no-op. - I've tested it here with pine, and it seems to work fine. I didn't test it with imapd, because I don't use it (yet). - I consider it an unelegant hack, but it works. I invite everybody to make comments (and test everything thoroughly), so that we can suggest it as a standard solution to the Pine development team. ------CUT HERE------ *** pine/pine.c- Wed Oct 20 15:28:04 1993 --- pine/pine.c Wed Oct 20 15:16:09 1993 *************** *** 62,68 **** --- 62,72 ---- struct pine *ps_global; /* sort of THE global variable */ int timeout = NEW_MAIL_TIME; /* referenced in weemacs */ + #ifdef SETGID_HACK + gid_t egid; + #endif + /*---------------------------------------------------------------------- General use big buffer. It is used in the following places: compose_mail: while parsing header of postponed message *************** *** 214,219 **** --- 218,230 ---- char int_mail[MAXPATH+1]; #ifdef DYN char stdiobuf[64]; + #endif + + #ifdef SETGID_HACK + /* Save effective group ID (probably the group ID of "mail") */ + egid = getegid(); + /* Replace the effective group ID with the real group ID */ + (void) setgid(getgid()); #endif /*---------------------------------------------------------------------- *** imap/ANSI/c-client/bezerk.c- Thu Oct 21 16:19:57 1993 --- imap/ANSI/c-client/bezerk.c Thu Oct 21 16:21:24 1993 *************** *** 60,65 **** --- 60,69 ---- #include "rfc822.h" #include "misc.h" #include "dummy.h" + + #ifdef SETGID_HACK + extern gid_t egid; + #endif /* Berkeley mail routines */ *************** *** 1116,1121 **** --- 1120,1130 ---- char tmp[MAILTMPLEN]; struct timeval tp; struct stat sb; + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for locking */ + (void) setgid(egid); + #endif /* build lock filename */ strcat (bezerk_file (lock,file),".lock"); do { /* until OK or out of tries */ *************** *** 1187,1192 **** --- 1196,1206 ---- sleep (1); /* wait 1 second before next try */ } } while (i-- && ld < 0 && *lock); + + #ifdef SETGID_HACK + /* Disable effective group ID (locking is done now) */ + (void) setgid(getgid()); + #endif /* open file */ if ((fd = open (file,flags,mode)) >= 0) flock (fd,op); else { /* open failed */ *************** *** 1220,1227 **** --- 1234,1250 ---- } flock (fd,LOCK_UN); /* release flock'ers */ close (fd); /* close the file */ + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for unlocking */ + (void) setgid(egid); + #endif /* flush the lock file if any */ if (lock && *lock) unlink (lock); + #ifdef SETGID_HACK + /* Disable effective group ID (unlocking is done now) */ + (void) setgid(getgid()); + #endif } /* Berkeley mail parse and lock mailbox *** imap/ANSI/c-client/mmdf.c- Wed Oct 20 14:24:16 1993 --- imap/ANSI/c-client/mmdf.c Wed Oct 20 14:41:14 1993 *************** *** 50,55 **** --- 50,59 ---- #include "rfc822.h" #include "misc.h" #include "dummy.h" + + #ifdef SETGID_HACK + extern gid_t egid; + #endif /* MMDF mail routines */ *************** *** 1077,1082 **** --- 1081,1091 ---- char tmp[MAILTMPLEN]; struct timeval tp; struct stat sb; + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for locking */ + (void) setgid(egid); + #endif /* build lock filename */ strcat (mmdf_file (lock,file),".lock"); do { /* until OK or out of tries */ *************** *** 1148,1153 **** --- 1157,1167 ---- sleep (1); /* wait 1 second before next try */ } } while (i-- && ld < 0 && *lock); + + #ifdef SETGID_HACK + /* Disable effective group ID (locking is done now) */ + (void) setgid(getgid()); + #endif /* open file */ if ((fd = open (file,flags,mode)) >= 0) flock (fd,op); else { /* open failed */ *************** *** 1181,1188 **** --- 1195,1211 ---- } flock (fd,LOCK_UN); /* release flock'ers */ close (fd); /* close the file */ + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for unlocking */ + (void) setgid(egid); + #endif /* flush the lock file if any */ if (lock && *lock) unlink (lock); + #ifdef SETGID_HACK + /* Disable effective group ID (unlocking is done now) */ + (void) setgid(getgid()); + #endif } /* MMDF mail parse and lock mailbox *** imap/ANSI/c-client/mtest.c- Wed Oct 20 15:10:13 1993 --- imap/ANSI/c-client/mtest.c Wed Oct 20 15:17:44 1993 *************** *** 77,82 **** --- 77,86 ---- NIL }; + #ifdef SETGID_HACK + gid_t egid; + #endif + void main (); void mm (MAILSTREAM *stream,long debug); void header (MAILSTREAM *stream,long msgno); *************** *** 102,107 **** --- 106,119 ---- char *suffix; struct passwd *pwd; struct hostent *host_name; + + #ifdef SETGID_HACK + /* Save effective group ID (probably the group ID of "mail") */ + egid = getegid(); + /* Replace the effective group ID with the real group ID */ + (void) setgid(getgid()); + #endif + gethostname (tmp,MAILTMPLEN); /* get local name */ /* get it in full form */ curhst = (host_name = gethostbyname (tmp)) ? *** imap/ANSI/imapd/imapd.c- Wed Oct 20 15:17:59 1993 --- imap/ANSI/imapd/imapd.c Wed Oct 20 15:19:02 1993 *************** *** 110,116 **** --- 110,120 ---- extern DRIVER bezerkdriver,tenexdriver,imapdriver,newsdriver,nntpdriver, philedriver,dummydriver; + #ifdef SETGID_HACK + gid_t egid; + #endif + /* Function prototypes */ void main (int argc,char *argv[]); *************** *** 145,150 **** --- 149,162 ---- char *s,*t,*u,*v,tmp[MAILTMPLEN]; struct hostent *hst; void (*f) () = NIL; + + #ifdef SETGID_HACK + /* Save effective group ID (probably the group ID of "mail") */ + egid = getegid(); + /* Replace the effective group ID with the real group ID */ + (void) setgid(getgid()); + #endif + mail_link (&tenexdriver); /* install the Tenex mail driver */ mail_link (&bezerkdriver); /* install the Berkeley mail driver */ mail_link (&imapdriver); /* install the IMAP driver */ *** imap/non-ANSI/c-client/bezerk.c- Wed Oct 20 14:29:06 1993 --- imap/non-ANSI/c-client/bezerk.c Wed Oct 20 14:35:33 1993 *************** *** 60,65 **** --- 60,69 ---- #include "rfc822.h" #include "misc.h" #include "dummy.h" + + #ifdef SETGID_HACK + extern gid_t egid; + #endif /* Berkeley mail routines */ *************** *** 1201,1206 **** --- 1205,1215 ---- char tmp[MAILTMPLEN]; struct timeval tp; struct stat sb; + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for locking */ + (void) setgid(egid); + #endif /* build lock filename */ strcat (bezerk_file (lock,file),".lock"); do { /* until OK or out of tries */ *************** *** 1272,1277 **** --- 1281,1291 ---- sleep (1); /* wait 1 second before next try */ } } while (i-- && ld < 0 && *lock); + + #ifdef SETGID_HACK + /* Disable effective group ID (locking is done now) */ + (void) setgid(getgid()); + #endif /* open file */ if ((fd = open (file,flags,mode)) >= 0) flock (fd,op); else { /* open failed */ *************** *** 1308,1315 **** --- 1322,1338 ---- } flock (fd,LOCK_UN); /* release flock'ers */ close (fd); /* close the file */ + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for unlocking */ + (void) setgid(egid); + #endif /* flush the lock file if any */ if (lock && *lock) unlink (lock); + #ifdef SETGID_HACK + /* Disable effective group ID (unlocking is done now) */ + (void) setgid(getgid()); + #endif } /* Berkeley mail parse and lock mailbox *** imap/non-ANSI/c-client/mmdf.c- Wed Oct 20 14:29:12 1993 --- imap/non-ANSI/c-client/mmdf.c Wed Oct 20 14:35:57 1993 *************** *** 50,55 **** --- 50,59 ---- #include "rfc822.h" #include "misc.h" #include "dummy.h" + + #ifdef SETGID_HACK + extern gid_t egid; + #endif /* MMDF mail routines */ *************** *** 1158,1163 **** --- 1162,1172 ---- char tmp[MAILTMPLEN]; struct timeval tp; struct stat sb; + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for locking */ + (void) setgid(egid); + #endif /* build lock filename */ strcat (mmdf_file (lock,file),".lock"); do { /* until OK or out of tries */ *************** *** 1229,1234 **** --- 1238,1248 ---- sleep (1); /* wait 1 second before next try */ } } while (i-- && ld < 0 && *lock); + + #ifdef SETGID_HACK + /* Disable effective group ID (locking is done now) */ + (void) setgid(getgid()); + #endif /* open file */ if ((fd = open (file,flags,mode)) >= 0) flock (fd,op); else { /* open failed */ *************** *** 1265,1272 **** --- 1279,1295 ---- } flock (fd,LOCK_UN); /* release flock'ers */ close (fd); /* close the file */ + + #ifdef SETGID_HACK + /* Restore effective group ID (probably group "mail") for unlocking */ + (void) setgid(egid); + #endif /* flush the lock file if any */ if (lock && *lock) unlink (lock); + #ifdef SETGID_HACK + /* Disable effective group ID (unlocking is done now) */ + (void) setgid(getgid()); + #endif } /* MMDF mail parse and lock mailbox *** imap/non-ANSI/c-client/mtest.c- Wed Oct 20 15:26:32 1993 --- imap/non-ANSI/c-client/mtest.c Wed Oct 20 15:19:55 1993 *************** *** 77,82 **** --- 77,86 ---- NIL }; + #ifdef SETGID_HACK + gid_t egid; + #endif + void main (); void mm (); void header (); *************** *** 102,107 **** --- 106,119 ---- char *suffix; struct passwd *pwd; struct hostent *host_name; + + #ifdef SETGID_HACK + /* Save effective group ID (probably the group ID of "mail") */ + egid = getegid(); + /* Replace the effective group ID with the real group ID */ + (void) setgid(getgid()); + #endif + gethostname (tmp,MAILTMPLEN); /* get local name */ /* get it in full form */ curhst = (host_name = gethostbyname (tmp)) ? *** imap/non-ANSI/imapd/imapd.c- Wed Oct 20 15:20:26 1993 --- imap/non-ANSI/imapd/imapd.c Wed Oct 20 15:21:30 1993 *************** *** 110,116 **** --- 110,120 ---- extern DRIVER bezerkdriver,tenexdriver,imapdriver,newsdriver,nntpdriver, philedriver,dummydriver; + #ifdef SETGID_HACK + gid_t egid; + #endif + /* Function prototypes */ void main (); *************** *** 147,152 **** --- 151,164 ---- char *s,*t,*u,*v,tmp[MAILTMPLEN]; struct hostent *hst; void (*f) () = NIL; + + #ifdef SETGID_HACK + /* Save effective group ID (probably the group ID of "mail") */ + egid = getegid(); + /* Replace the effective group ID with the real group ID */ + (void) setgid(getgid()); + #endif + mail_link (&tenexdriver); /* install the Tenex mail driver */ mail_link (&bezerkdriver); /* install the Berkeley mail driver */ mail_link (&imapdriver); /* install the IMAP driver */ ------CUT HERE------ -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Thu Oct 21 10:24:56 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08475; Thu, 21 Oct 93 10:24:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13289; Thu, 21 Oct 93 10:08:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13281; Thu, 21 Oct 93 10:08:08 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25960 (5.65b/CWI-3.3); Thu, 21 Oct 1993 18:08:06 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05685; Thu, 21 Oct 93 16:24:59 GMT (MET) Message-Id: <9310211624.AA05685@wilg.bull.nl> To: Pine Info Subject: Patch for disabling the Update function Date: Thu, 21 Oct 93 17:24:57 MET From: Jos Vos Because I wanted to disable the Update function that (IMHO) may confuse our users (and does not work here), I've made the following patch to be able to disable it at compile time (macro: DISABLE_UPDATE). I'ld like to have it be included in future releases of Pine. ------CUT HERE------ *** pine/pine.c.org Tue Oct 12 15:49:30 1993 --- pine/pine.c Tue Oct 12 15:53:57 1993 *************** *** 663,669 **** --- 663,673 ---- {" %s ADDRESS BOOK - Update address book", OPF10, 'A', ADDRESS_KEY}, {"", UNUSED, UNUSED, UNUSED}, + #ifndef DISABLE_UPDATE {" %s SETUP - Configure or update Pine", + #else + {" %s SETUP - Configure Pine", + #endif OPF9, 'S',SETUP_KEY}, {"", UNUSED, UNUSED, UNUSED}, {" %s QUIT - Exit the Pine program", *************** *** 1205,1211 **** --- 1209,1217 ---- char *setup_names[] = {"Printer", "Newpassword", "Options", + #ifndef DISABLE_UPDATE "Update", + #endif "Exit", NULL}; /*---------------------------------------------------------------------- *************** *** 1223,1232 **** --- 1229,1246 ---- HelpType help; (void)strcpy(prompt, + #ifndef DISABLE_UPDATE "SETUP (Printer,Newpassword,Options,Update,[Exit]; type PNOU or E): "); + #else + "SETUP (Printer,Newpassword,Options,[Exit]; type PNO or E): "); + #endif help = h_mini_setup; + #ifndef DISABLE_UPDATE s = radio_buttons(prompt, ql, 0, "pnoue", setup_names, 'e', 'x', help, 0); + #else + s = radio_buttons(prompt, ql, 0, "pnoe", setup_names, 'e', 'x', help, 0); + #endif /* ^C */ if(s == 'x') { Writechar('\007', 0); *************** *** 1255,1260 **** --- 1269,1275 ---- * much, we can always turn pine.cac into a multi-address name which * randomizes. */ + #ifndef DISABLE_UPDATE #define UPDATE_FOLDER "*{pine.cac.washington.edu/anonymous}updates" /*----- UPDATE -----*/ case 'u': *************** *** 1262,1267 **** --- 1277,1283 ---- if(do_broach_folder(UPDATE_FOLDER, NULL) > 0) ps_global->next_screen = mail_index_screen; break; + #endif /*----- SET OPTIONS -----*/ case 'o': ------CUT HERE------ -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Thu Oct 21 10:26:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08506; Thu, 21 Oct 93 10:26:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10619; Thu, 21 Oct 93 10:08:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10612; Thu, 21 Oct 93 10:08:13 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25977 (5.65b/CWI-3.3); Thu, 21 Oct 1993 18:08:11 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05588; Thu, 21 Oct 93 16:20:59 GMT (MET) Message-Id: <9310211620.AA05588@wilg.bull.nl> To: Pine Info Subject: Patch for Pine documentation and groff Date: Thu, 21 Oct 93 17:20:57 MET From: Jos Vos The following patch I made to the pico manual page, because I had trouble formatting it with groff (groff can handle macro names longer than 2 characters). Please consider to include it in the next release of Pine. ------CUT HERE------ *** doc/pico.1.org Tue Oct 12 14:26:00 1993 --- doc/pico.1 Tue Oct 12 14:27:09 1993 *************** *** 48,76 **** .PP More specific help is available in \fIpico\fR's online help. .SH Options ! .IP\fB-f\fR Use function keys for commands. This option supported only in conjunction with UW Enhanced NCSA telnet. ! .IP\fB+\fIn\fB\fR Causes \fIpico\fR to be started with the cursor located \fIn\fR lines into the file. (Note: no space between "+" sign and number) ! .IP\fB-n\fIn\fB\fR The \-n\fIn\fR option enables new mail notification. The \fIn\fR argument is optional, and specifies how often, in seconds, your mailbox is checked for new mail. For example, \-n60 causes \fIpico\fR to check for new mail once every minute. The default interval is 180 seconds, while the minimum allowed is 30. (Note: no space between "+" sign and number) ! .IP\fB-t\fR Enable "tool" mode. Intended for when \fIpico\fR is used as the editor within other tools (e.g., Elm, Pnews). \fIPico\fR will not prompt for save on exit, and will not rename the buffer during the "Write Out" command. ! .IP\fB-v\fR View the file only, disallowing any editing. ! .IP\fB-w\fR Disable word wrap (thus allow editing of long lines). ! .IP\fB-z\fR Enable ^Z suspension of \fIpico\fR. .PP Lastly, when a running \fIpico\fR is disconnected (i.e., receipt of a --- 48,76 ---- .PP More specific help is available in \fIpico\fR's online help. .SH Options ! .IP \fB-f\fR Use function keys for commands. This option supported only in conjunction with UW Enhanced NCSA telnet. ! .IP \fB+\fIn\fB\fR Causes \fIpico\fR to be started with the cursor located \fIn\fR lines into the file. (Note: no space between "+" sign and number) ! .IP \fB-n\fIn\fB\fR The \-n\fIn\fR option enables new mail notification. The \fIn\fR argument is optional, and specifies how often, in seconds, your mailbox is checked for new mail. For example, \-n60 causes \fIpico\fR to check for new mail once every minute. The default interval is 180 seconds, while the minimum allowed is 30. (Note: no space between "+" sign and number) ! .IP \fB-t\fR Enable "tool" mode. Intended for when \fIpico\fR is used as the editor within other tools (e.g., Elm, Pnews). \fIPico\fR will not prompt for save on exit, and will not rename the buffer during the "Write Out" command. ! .IP \fB-v\fR View the file only, disallowing any editing. ! .IP \fB-w\fR Disable word wrap (thus allow editing of long lines). ! .IP \fB-z\fR Enable ^Z suspension of \fIpico\fR. .PP Lastly, when a running \fIpico\fR is disconnected (i.e., receipt of a ------CUT HERE------ -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Thu Oct 21 10:26:27 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08530; Thu, 21 Oct 93 10:26:27 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10720; Thu, 21 Oct 93 10:12:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from jhunix.hcf.jhu.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10714; Thu, 21 Oct 93 10:12:15 -0700 Received: from jhunix.hcf.jhu.edu ([128.220.2.5]) by jhunix.hcf.jhu.edu with SMTP id <72502-3>; Thu, 21 Oct 1993 13:11:57 -0400 Date: Thu, 21 Oct 1993 13:06:19 -0400 From: Andy Poling Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: Mark Crispin Cc: "A. Hilborne" , Jos Vos , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 21 Oct 1993, Mark Crispin wrote: > We have a very long ``to-do'' list of feature enhancements and bugs to be > fixed. Should we divert our limited resources for several months (or longer) > towards an effort that adds no user function and is unnecessary with better > site management? Definitely not... pleez. > Would offering a /bin/mail substitute (you would edit your sendmail.cf to run > it instead of /bin/mail) that protects against mail being delivered to false > mailboxes be a satisfactory alternate? We can offer this in a finite amount > of time. This would fix the problem without requiring that mail readers run > with privileges. Unfortunately this is not a solution. You are making a common mistake in assuming that everyone is running sendmail. There are at least two other MTA packages that are as good as, or better then, sendmail (e.g. MMDF and ZMAILER). Some sites (like us) handle too large a volume of mail to use sendmail. I say let the system administrator worry about it - this is not a new problem. I think your time is much better spent on improving the interface and user-visible functionality of your MUA. -Andy Andy Poling Internet: andy@jhunix.hcf.jhu.edu UNIX Systems Programmer Bitnet: ANDY@JHUNIX Homewood Academic Computing Voice: (410)516-8096 Johns Hopkins University UUCP: uunet!mimsy!aplcen!jhunix!andy From owner-pine-info@cac.washington.edu Thu Oct 21 10:28:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08599; Thu, 21 Oct 93 10:28:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10630; Thu, 21 Oct 93 10:08:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10622; Thu, 21 Oct 93 10:08:28 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25972 (5.65b/CWI-3.3); Thu, 21 Oct 1993 18:08:09 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05803; Thu, 21 Oct 93 16:36:06 GMT (MET) Message-Id: <9310211636.AA05803@wilg.bull.nl> To: Pine Info Subject: Misleading text in addrbook.c Date: Thu, 21 Oct 93 17:36:04 MET From: Jos Vos When adding a new entry in the addres book, you get the text New full name (last, first) : I think it's better to let the text be: New full name (First Last) : Because we don't really want a "," in the registered full name. ------CUT HERE------ *** pine/addrbook.c- Thu Oct 21 16:32:23 1993 --- pine/addrbook.c Thu Oct 21 16:36:07 1993 *************** *** 1748,1754 **** oe_append = 0; do { char *q; ! prompt = "New full name (last, first) : "; rc = optionally_enter(new_name, command_line, 0, MAX_FULLNAME, oe_append, 0, prompt, NULL, help, 0); oe_append = 1; --- 1748,1754 ---- oe_append = 0; do { char *q; ! prompt = "New full name (First Last) : "; rc = optionally_enter(new_name, command_line, 0, MAX_FULLNAME, oe_append, 0, prompt, NULL, help, 0); oe_append = 1; ------CUT HERE------ -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Thu Oct 21 10:29:42 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08650; Thu, 21 Oct 93 10:29:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13295; Thu, 21 Oct 93 10:08:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13283; Thu, 21 Oct 93 10:08:10 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA25967 (5.65b/CWI-3.3); Thu, 21 Oct 1993 18:08:08 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA05750; Thu, 21 Oct 93 16:32:43 GMT (MET) Message-Id: <9310211632.AA05750@wilg.bull.nl> To: Pine Info Subject: Patch for Printer setup screen Date: Thu, 21 Oct 93 17:32:42 MET From: Jos Vos In the file other.c and pine.c two functionally equivalent (static) functions redraw_printer_select() exist. The text included in other.c was more generic (it contained also references to "lp" and "LPDEST", thus being more appropriate for System V systems). So I made the following patch to make the text in pine.c equal to that in other.c. Please include this patch in the next official release. ------CUT HERE----- *** pine/pine.c.orig Tue Oct 12 16:48:52 1993 --- pine/pine.c Wed Oct 20 10:26:50 1993 *************** *** 1430,1437 **** rc = set_variable(V_PERSONAL_PRINT_COMMAND, custom_command); } if(rc == 0) ! q_status_message1(0,1,3, "Printer set to \"%s\"; configuration saved", ! ps_global->VAR_PRINTER); } } --- 1430,1438 ---- rc = set_variable(V_PERSONAL_PRINT_COMMAND, custom_command); } if(rc == 0) ! q_status_message1(0, 1, 3, ! "Printer set to \"%s\"; configuration saved", ! ps_global->VAR_PRINTER); } } *************** *** 1468,1475 **** l++; PutLine0(l++, 3, "2. Standard UNIX print command"); PutLine0(l++,6, ! "Using this option may require setting your \"PRINTER\" environment"); ! PutLine0(l++, 6, "variable using the standard UNIX utilities."); PutLine0(l, 10 , "Command: "); if(ps_global->VAR_STANDARD_PRINTER != NULL && strcmp(ps_global->VAR_PRINTER, ps_global->VAR_STANDARD_PRINTER) == 0) { --- 1469,1477 ---- l++; PutLine0(l++, 3, "2. Standard UNIX print command"); PutLine0(l++,6, ! "Using this option may require setting your \"PRINTER\" or \"LPDEST\""); ! PutLine0(l++, 6, ! "environment variable using the standard UNIX utilities."); PutLine0(l, 10 , "Command: "); if(ps_global->VAR_STANDARD_PRINTER != NULL && strcmp(ps_global->VAR_PRINTER, ps_global->VAR_STANDARD_PRINTER) == 0) { *************** *** 1488,1498 **** PutLine0(l++, 6, "The text to be printed will be piped into the command given here. Some"); PutLine0(l++, 6, ! "examples are: \"prt\", \"lpr\", or \"enscript\". The command may be given"); PutLine0(l++, 6, "with options, for example \"enscript -2 -r\" or \"lpr -Plpacc170\". The"); PutLine0(l++, 6, ! "commands and options on your system may be different these examples."); PutLine0(l, 10, "Command: "); if(!matched_printer) StartInverse(); --- 1490,1500 ---- PutLine0(l++, 6, "The text to be printed will be piped into the command given here. Some"); PutLine0(l++, 6, ! "examples are: \"prt\", \"lpr\", \"lp\", or \"enscript\". The command may be given"); PutLine0(l++, 6, "with options, for example \"enscript -2 -r\" or \"lpr -Plpacc170\". The"); PutLine0(l++, 6, ! "commands and options on your system may be different from these examples."); PutLine0(l, 10, "Command: "); if(!matched_printer) StartInverse(); ------CUT HERE----- -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Thu Oct 21 10:31:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08727; Thu, 21 Oct 93 10:31:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13344; Thu, 21 Oct 93 10:19:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13338; Thu, 21 Oct 93 10:19:08 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA21560; Thu, 21 Oct 1993 12:22:15 -0500 Date: Thu, 21 Oct 1993 12:19:51 -0500 (CDT) From: "Robert A. Hayden" Subject: Thought for next version To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I got to thinking of somethign that might be nice to have in a future version of pine: filename completion. Where I'm finding this would be helpful is when I'm reading in a file into a piece of mail. In bash, you can just press TAB and it will complete the filename for you. This would be most helpful to have when you have long filenames (or worse, confusing filenames). Just a thought, anyways. {[> Robert A. Hayden ____ <[} Question Authority {[> \ /__ <]} -=-=- {[> aq650@slc4.INS.CWRU.Edu \/ / <]} Finger for PGP 2.3a Public Key {[> hayden@krypton.mankato.msus.edu \/ <]} Finger for Geek Code Info -=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Thu Oct 21 12:17:30 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12151; Thu, 21 Oct 93 12:17:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12867; Thu, 21 Oct 93 12:00:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12861; Thu, 21 Oct 93 12:00:17 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10639; Thu, 21 Oct 93 12:00:09 -0700 Date: Thu, 21 Oct 1993 11:58:54 -0700 (PDT) From: David L Miller Subject: Re: Thought for next version To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine 3.87 already supports TAB for filename completion. You can activate this by adding enable-tab-completion to the feature-list in your .pinerc. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 21 Oct 1993, Robert A. Hayden wrote: > I got to thinking of somethign that might be nice to have in a future > version of pine: filename completion. > > Where I'm finding this would be helpful is when I'm reading in a file > into a piece of mail. In bash, you can just press TAB and it will > complete the filename for you. This would be most helpful to have when > you have long filenames (or worse, confusing filenames). > > Just a thought, anyways. > > {[> Robert A. Hayden ____ <[} Question Authority > {[> \ /__ <]} -=-=- > {[> aq650@slc4.INS.CWRU.Edu \/ / <]} Finger for PGP 2.3a Public Key > {[> hayden@krypton.mankato.msus.edu \/ <]} Finger for Geek Code Info > -=-=-=-=-=- > (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ > n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) > > From owner-pine-info@cac.washington.edu Thu Oct 21 12:54:43 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13136; Thu, 21 Oct 93 12:54:43 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14244; Thu, 21 Oct 93 12:40:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14238; Thu, 21 Oct 93 12:40:25 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA09169; Thu, 21 Oct 93 12:40:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA07210; Thu, 21 Oct 93 12:40:09 -0700 Date: Thu, 21 Oct 1993 12:07:38 -0700 (PDT) From: Mark Crispin Subject: re: (fwd) Problems with 3.87 on a Sun To: Jim Simmons Cc: pine-info@cac.washington.edu In-Reply-To: <199310211227.IAA08422@sws1.ctd.ornl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 21 Oct 1993 08:27:20 -0400, Jim Simmons wrote: > First, it appears that when you save a message to another folder, the > saved message gets marked as New, even though you've already read it. This > is not the way it worked in 3.07. Is this normal? This is a known problem, caused by a design change which permits saving of messages to remote folders via IMAP. Formerly, Pine had internal code to implement saving; now it uses a generic library routine. The problem was that IMAP didn't have a way to support flag preservation, so in the name of consistency flags were never preserved. This problem has been resolved. It is near the top of my high priority list of things to do. Unfortunately, it is a ``missing feature'', not a ``bug'', and so it will probably not make it into Pine 3.88. We have high hopes for it being in Pine 3.89 or Pine 3.90. > Also, we've been having trouble with users who apparently loose their > connection (they're calling in through modems) and their pine process > doesn't > disappear. Sometimes it not only doesn't disappear, but apparently goes > into > a loop using up as much CPU time as it can get. Any ideas what may be > happening? We believe that this problem will be fixed in Pine 3.88. From owner-pine-info@cac.washington.edu Thu Oct 21 14:12:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14947; Thu, 21 Oct 93 14:12:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14733; Thu, 21 Oct 93 13:52:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pg2-srv.wam.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14727; Thu, 21 Oct 93 13:52:15 -0700 Received: from next00cville.wam.umd.edu by pg2-srv.wam.umd.edu with SMTP id AA02873 (5.65c/IDA-1.4.4 for ); Thu, 21 Oct 1993 16:45:31 -0400 Received: by next00cville.wam.umd.edu id AA02929 (5.65c/IDA-1.4.4); Thu, 21 Oct 1993 16:45:03 -0400 Date: Thu, 21 Oct 1993 16:40:12 -0400 (EDT) From: Highway 'Nakoruru' YAH! Subject: Re: Misleading text in addrbook.c To: Jos Vos Cc: Pine Info In-Reply-To: <9310211636.AA05803@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I don't think it matters to have in the address book menu (first last) instead of (last, first). The only difference is that you have to manually type in the comma. --------------------- [ National Service Fraternity ] ---------------------- UU UU MM MM DDDDDD highway@wam.umd.edu EEEEEEE MM MM UU UU MMM MMM DD DD "the snuggly, cuddly care bear" EE MMM MMM UU UU MM M MM DD DD 124 Englefield Drive EEEEE MM M MM UU UU MM MM DD DD Gaithersburg, MD 20878 EE MM MM UUUUUUU MM MM DDDDDD (301) 948-5174 EEEEEEE MM MM University of Maryland Internet: highway@wam.umd.edu Epsilon Mu College Park Bitnet: tcwu@umdd.bitnet Alpha Phi Omega ----------------- [ In Leadership, Friendship & Service ] ------------------ {What is your name?} (Jean-Luc Picard.) {What is your quest?} (To seek out new life and civilization.) {What is the average warp speed of a bird of prey?} (Klingon or Romulan?) {What? I don't know that??!?! AIIIIEEEEEEEEE!!!!} From owner-pine-info@cac.washington.edu Thu Oct 21 14:30:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15345; Thu, 21 Oct 93 14:30:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14847; Thu, 21 Oct 93 14:12:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pg2-srv.wam.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14841; Thu, 21 Oct 93 14:12:40 -0700 Received: from next00cville.wam.umd.edu by pg2-srv.wam.umd.edu with SMTP id AA02906 (5.65c/IDA-1.4.4 for ); Thu, 21 Oct 1993 16:46:50 -0400 Received: by next00cville.wam.umd.edu id AA02935 (5.65c/IDA-1.4.4); Thu, 21 Oct 1993 16:46:29 -0400 Date: Thu, 21 Oct 1993 16:45:16 -0400 (EDT) From: Highway 'Nakoruru' YAH! Subject: Re: Misleading text in addrbook.c To: Jos Vos Cc: Pine Info In-Reply-To: <9310211636.AA05803@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 21 Oct 1993, Jos Vos wrote: > When adding a new entry in the addres book, you get the text > > New full name (last, first) : > > I think it's better to let the text be: > > New full name (First Last) : > > Because we don't really want a "," in the registered full name. Also, "," doesn't show up ie: New full name (last, first) : Doe, John cause when you type the nickname in the To: field, it comes out as: To: John Doe From owner-pine-info@cac.washington.edu Thu Oct 21 21:31:25 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25537; Thu, 21 Oct 93 21:31:25 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17025; Thu, 21 Oct 93 21:19:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pg2-srv.wam.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17019; Thu, 21 Oct 93 21:19:01 -0700 Received: from rac6.wam.umd.edu by pg2-srv.wam.umd.edu with SMTP id AA27360 (5.65c/IDA-1.4.4 for ); Fri, 22 Oct 1993 00:18:59 -0400 Received: by rac6.wam.umd.edu id AA23199 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 22 Oct 1993 00:18:57 -0400 Date: Fri, 22 Oct 1993 00:15:20 -0400 (EDT) From: Highway 'Nakoruru' YAH! Subject: Question: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Why is it that when I save my incoming file to another folder, the author for the email is changed to my account name? Before, in the old version, I would save mail in one file and type: from -f ~/mail/ it would list the mail items with the proper address it came from, but with the new version, it changes all the email address of where it's from to my userid. from -f ~/mail/ From highway@wam.umd.edu Thu Oct 21 22:02:21 1993 From highway@wam.umd.edu Thu Oct 21 22:10:52 1993 From highway@wam.umd.edu Thu Oct 21 23:22:11 1993 Like that... how do I fix that or how do I change settings? --------------------- [ National Service Fraternity ] ---------------------- UU UU MM MM DDDDDD highway@wam.umd.edu EEEEEEE MM MM UU UU MMM MMM DD DD "the snuggly, cuddly care bear" EE MMM MMM UU UU MM M MM DD DD 124 Englefield Drive EEEEE MM M MM UU UU MM MM DD DD Gaithersburg, MD 20878 EE MM MM UUUUUUU MM MM DDDDDD (301) 948-5174 EEEEEEE MM MM University of Maryland Internet: highway@wam.umd.edu Epsilon Mu College Park Bitnet: tcwu@umdd.bitnet Alpha Phi Omega ----------------- [ In Leadership, Friendship & Service ] ------------------ {What is your name?} (Jean-Luc Picard.) {What is your quest?} (To seek out new life and civilization.) {What is the average warp speed of a bird of prey?} (Klingon or Romulan?) {What? I don't know that??!?! AIIIIEEEEEEEEE!!!!} From owner-pine-info@cac.washington.edu Thu Oct 21 23:02:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26573; Thu, 21 Oct 93 23:02:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17263; Thu, 21 Oct 93 22:21:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17257; Thu, 21 Oct 93 22:21:15 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA10482; Thu, 21 Oct 93 22:21:04 -0700 Date: Thu, 21 Oct 1993 22:17:18 -0700 (PDT) From: Mark Crispin Subject: re: Pine being setgid mail (was: .lock mailbox locking) To: Hannu Martikka Cc: pine-info@cac.washington.edu In-Reply-To: <199310211349.AA13340@cc.lut.fi> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 21 Oct 1993 15:49:13 +0200, Hannu Martikka wrote: > Could it be possible to use some small external program from pine to > handle locking? That was considered many years ago. One problem with doing this is that Pine is no longer self-contained; you now have to install two programs. Plus, this doesn't help the case where Pine is user-installed and maintained, since presumably that external program will run with set[gu]id privileges and most system managers don't allow random programs to be privileged. From owner-pine-info@cac.washington.edu Fri Oct 22 02:17:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00353; Fri, 22 Oct 93 02:17:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22729; Fri, 22 Oct 93 01:35:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22723; Fri, 22 Oct 93 01:35:24 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA05506 (5.65b/CWI-3.3); Fri, 22 Oct 1993 09:35:14 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA12098; Fri, 22 Oct 93 08:23:51 GMT (MET) Message-Id: <9310220823.AA12098@wilg.bull.nl> To: Highway 'Nakoruru' YAH! Cc: Pine Info Subject: Re: Misleading text in addrbook.c In-Reply-To: Your message of "Thu, 21 Oct 93 16:45:16 MET." Date: Fri, 22 Oct 93 09:23:49 MET From: Jos Vos > > When adding a new entry in the addres book, you get the text > > New full name (last, first) : > > I think it's better to let the text be: > > New full name (First Last) : > > Because we don't really want a "," in the registered full name. > Also, "," doesn't show up ie: > New full name (last, first) : Doe, John > cause when you type the nickname in the To: field, it comes out as: > To: John Doe Sorry! I really thought I'd seen a "," appearing somewhere (maybe that was in 3.07, which I looked at quickly before moving to 3.87). It's still questionable whether it makes sense to ask someone to type in a name in the format "last, first". Is that a natural way in the U.S.? Here the "first last" format is more natural (in France the format "LAST first" seems to be the default :-)). -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Fri Oct 22 02:19:02 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00403; Fri, 22 Oct 93 02:19:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17981; Fri, 22 Oct 93 01:35:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17975; Fri, 22 Oct 93 01:35:37 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA10789; Fri, 22 Oct 93 01:35:31 -0700 Date: Fri, 22 Oct 1993 00:30:15 -0700 (PDT) From: Mark Crispin Subject: re: Question: To: Highway 'Nakoruru' YAH! Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The so-called ``author for the email'' -- more specifically, the token that follows the word ``From '' in an mbox-format header -- is really the ``return address'' of whatever delivery agent wrote that message. It may have nothing to do with the actual sender of the message. Pine does not use this field, nor do other mailbox formats have this field at all. Possibly, we could in a future copy this field in copying from one mbox- format mailbox to another, but in all other cases (including those involving IMAP) it is simply impossible. I don't think that inconsistent behavior is doing users any favors. In a sense, it is you who wrote that message into the other folder, not the agent who wrote it originally into your INBOX. In mailer architectures where there may be multiple INBOXes, this can be a significant difference. The date in the ``From '' header isn't copied either. This is intentional, due to the requirement in IMAP that the internaldates be strictly ascending. Arguably, it is a bug in the Unix ``from'' program that it reports this data and not the address in the RFC-822 ``From:'' header line. The from program's usage dates back from 1970's pre-ARPAnet UNIX, where the mbox ``From '' header was the only header and a ``network'' was UUCP and 1200-baud phone lines. -- Mark -- From owner-pine-info@cac.washington.edu Fri Oct 22 03:34:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02061; Fri, 22 Oct 93 03:34:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23141; Fri, 22 Oct 93 02:48:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pp2.shef.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23135; Fri, 22 Oct 93 02:48:42 -0700 Received: from sunc.sheffield.ac.uk (actually sunc.shef.ac.uk) by pp2.shef.ac.uk with SMTP (PP); Fri, 22 Oct 1993 10:49:36 +0100 From: Chris Martin Date: Fri, 22 Oct 93 10:48:09 BST Message-Id: <12884.9310220948@sunc.sheffield.ac.uk> Received: from ss3.ac.uk by sunc.sheffield.ac.uk; Fri, 22 Oct 93 10:48:09 BST Received: by ss3.ac.uk (4.1/SMI-4.1) id AA05710; Fri, 22 Oct 93 10:48:08 BST To: pine-info@cac.washington.edu Subject: Re: Compilation error for v3.87 on SGI IRIX 5.0.1 Because I couldn't get pine v3.87 to run on on our Challenge XL under IRIX 5.0.1 I recompiled pine3.07 -- which failed to compile with the same error message. Ahah! I then recompiled it on our 4D/420 under IRIX 4.0.5 and compiled and ran like the champion it is -- so did v3.87! The compilation problem comes from /usr/include/time.h which (C compiler v3.10) has extern char * _tzname[]; while version 3.16 has extern char *tzname[2]; It has apparently taken the good folks at Silicon Graphics 6 patches to break another piece of software! From owner-pine-info@cac.washington.edu Fri Oct 22 03:35:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02110; Fri, 22 Oct 93 03:35:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23179; Fri, 22 Oct 93 02:52:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23173; Fri, 22 Oct 93 02:52:11 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA04242 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Fri, 22 Oct 93 04:52:09 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA10221; Fri, 22 Oct 93 04:52:08 CDT Date: Fri, 22 Oct 1993 04:49:27 -0500 (CDT) From: Matt Simmons Subject: Selection bar To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII One of the users here uses pine indirectly through a dialin... He goes from the dialin through ISN through another machine to his. Thus pine is clueless as to the fact that he's calling in at a very slow baud rate and needs the '-->' instead of the selection bar... How does one tell pine to use the -->? This is probably a very stupid question with a very simple answer, but it's 4:51 in the am... Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Fri Oct 22 08:05:10 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06361; Fri, 22 Oct 93 08:05:10 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25702; Fri, 22 Oct 93 07:50:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from utdallas.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25696; Fri, 22 Oct 93 07:50:13 -0700 Received: from infoserv.utdallas.edu by utdallas.edu (ZMailer 2.1.3 #231) with BLIMP id <74082>; Fri, 22 Oct 1993 09:50:08 -0500 Subject: I want Elm's outgoing mail folder feature in PINE From: Billy Barron To: pine-info@cac.washington.edu Date: Fri, 22 Oct 1993 09:49:59 -0500 Cc: susie@utdallas.edu, shane@utdallas.edu (Shane Davis) X-Mailer: ELM [version 2.3 PL11] Message-Id: <93Oct22.095008cdt.74082@utdallas.edu> Is there any way to get PINE to do what Elm does with outgoing mail? That is to have it saved under the username of the person you are sending to. If not, could it be added in a future release? -- Billy Barron, Network Services Manager, Univ of Texas at Dallas billy@utdallas.edu From owner-pine-info@cac.washington.edu Fri Oct 22 08:51:53 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07943; Fri, 22 Oct 93 08:51:53 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19703; Fri, 22 Oct 93 08:33:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dartvax.dartmouth.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19697; Fri, 22 Oct 93 08:33:03 -0700 Received: from at-sn-148.dartmouth.edu by dartvax.dartmouth.edu (5.65+D5/4.5HUB) id AA01853; Fri, 22 Oct 93 11:32:54 -0400 Received: from janus.coat.com by coat.coat.com (4.1/SMI-4.0) id AA15194; Fri, 22 Oct 93 11:28:47 EDT Received: by janus.coat.com (4.1/SMI-4.1) id AA12910; Fri, 22 Oct 93 11:28:49 EDT Message-Id: <9310221528.AA12910@janus.coat.com> From: andyb@janus.coat.com (Andy Behrens) Date: Fri, 22 Oct 1993 11:28:48 -0400 Organization: Burlington Coat Factory Reply-To: Andy.Behrens@coat.com X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Matt Simmons , pine-info@cac.washington.edu Subject: Re: Selection bar > One of the users here uses pine indirectly through a dialin... He goes > from the dialin through ISN through another machine to his. Thus pine is > clueless as to the fact that he's calling in at a very slow baud rate and > needs the '-->' instead of the selection bar... How does one tell pine to > use the -->? If he's running on a Unix system and logs on to it through 'rlogin' or 'telnet', he could type 'stty 1200', 'stty 2400', etc. This would *not* be a good idea if he connected to his system through a character port, because it would actually change the port speed. But if he was connecting through a network port, the 'stty' speed would just serve to advise Pine that he's running at low speed. Andy -- Practice random kindness and senseless acts of beauty. (Anne Herbert) Andy Behrens Burlington Coat Factory, Schoolhouse Lane, Etna, N.H. 03750 (603) 643-2800 From owner-pine-info@cac.washington.edu Fri Oct 22 09:09:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08782; Fri, 22 Oct 93 09:09:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26924; Fri, 22 Oct 93 08:52:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26918; Fri, 22 Oct 93 08:52:32 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25415; Fri, 22 Oct 93 08:52:19 -0700 Date: Fri, 22 Oct 1993 08:49:11 -0700 (PDT) From: David L Miller Subject: Re: Misleading text in addrbook.c To: Jos Vos Cc: Highway 'Nakoruru' YAH! , Pine Info In-Reply-To: <9310220823.AA12098@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The reason we use "Last, First" is that we sort the addressbook by the full name field. This format makes it easy to get the entries in order by last name. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 22 Oct 1993, Jos Vos wrote: > > > When adding a new entry in the addres book, you get the text > > > New full name (last, first) : > > > I think it's better to let the text be: > > > New full name (First Last) : > > > Because we don't really want a "," in the registered full name. > > > Also, "," doesn't show up ie: > > New full name (last, first) : Doe, John > > cause when you type the nickname in the To: field, it comes out as: > > To: John Doe > > Sorry! I really thought I'd seen a "," appearing somewhere (maybe > that was in 3.07, which I looked at quickly before moving to 3.87). > > It's still questionable whether it makes sense to ask someone to > type in a name in the format "last, first". Is that a natural way > in the U.S.? Here the "first last" format is more natural > (in France the format "LAST first" seems to be the default :-)). > > -- > -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) > -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Fri Oct 22 12:21:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20257; Fri, 22 Oct 93 12:21:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01377; Fri, 22 Oct 93 12:04:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ACF4.NYU.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01371; Fri, 22 Oct 93 12:04:49 -0700 Received: by acf4.NYU.EDU (5.65/DEC-Ultrix/4.3) id AA22301; Fri, 22 Oct 1993 15:03:05 -0400 Date: Fri, 22 Oct 1993 15:00:01 -0400 (EDT) From: "Yigal M. Rechtman 1st" Subject: Genie/Prodigi/??: where to get info To: roots Cc: pinelist Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello felows: My mother-in-law is a liberarian (education, children's books) and would like to join the cyberworld. I am looking for a good service and think Genie/Prodigi would be one. Where can I find their info? Also, Do you know of any services with trial periods? Thanks! Yigal BTW: Any other suggestions are welcome! -Yigal From owner-pine-info@cac.washington.edu Fri Oct 22 13:56:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24556; Fri, 22 Oct 93 13:56:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21819; Fri, 22 Oct 93 13:42:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from redvax1.dgsca.unam.mx by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21809; Fri, 22 Oct 93 13:42:01 -0700 Received: by redvax1.dgsca.unam.mx (5.57/Ultrix3.0-C) id AA21065; Fri, 22 Oct 93 14:39:27 -0500 Date: Fri, 22 Oct 1993 14:32:01 -0500 (CDT) From: "Isaias Callejas Mancilla." Reply-To: "Isaias Callejas Mancilla." Subject: BBOARD... To: The PINE List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi dear PINE List : Why I can't connect to UPDATE server??, in the past it did work fine; when I select the option SETUP and select the option UPDATE, I have got the message : "connecting to update server" later.. [*{pine.cac.washington.edu/anonymous}updates : ftp.cac.washington.edu IMAP2bis] later.. "BBOARD failed: No such bboard : updates" What happen??... Thank's in advance... /####### E. Isaias Callejas M. /# /############ Grupo de Administradores del Equipo Microvax 3400 /## /############## Coordinacion de Servicios de Computo ### /## ### Computo Academico ### ### ### Universidad Nacional Autonoma de Mexico ### ########## ### ### ### ### ================================================= ### ##/ ### ##############/ ##/ Internet : isma@redvax1.dgsca.unam.mx ############/ #/ Bitnet : isma@redvax1.bitnet #######/ From owner-pine-info@cac.washington.edu Fri Oct 22 18:59:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05918; Fri, 22 Oct 93 18:59:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09134; Fri, 22 Oct 93 18:48:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09128; Fri, 22 Oct 93 18:48:19 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12542; Fri, 22 Oct 93 18:47:53 -0700 Date: Fri, 22 Oct 1993 18:46:14 -0700 (PDT) From: Terry Gray Subject: Re: BBOARD... To: "Isaias Callejas Mancilla." Cc: The PINE List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Isaias, A thousand pardons... We moved the update service to a different machine and didn't get all the necessary files copied. I'll let you know as soon as this is corrected. -teg On Fri, 22 Oct 1993, Isaias Callejas Mancilla. wrote: > Hi dear PINE List : > Why I can't connect to UPDATE server??, in the past it did work fine; > when I select the option SETUP and select the option UPDATE, I have got > the message : > "connecting to update server" > later.. > > [*{pine.cac.washington.edu/anonymous}updates : ftp.cac.washington.edu IMAP2bis] > > later.. > > "BBOARD failed: No such bboard : updates" > > What happen??... > Thank's in advance... > > > /####### E. Isaias Callejas M. > /# /############ Grupo de Administradores del Equipo Microvax 3400 > /## /############## Coordinacion de Servicios de Computo > ### /## ### Computo Academico > ### ### ### Universidad Nacional Autonoma de Mexico > ### ########## ### > ### ### ### ================================================= > ### ##/ ### > ##############/ ##/ Internet : isma@redvax1.dgsca.unam.mx > ############/ #/ Bitnet : isma@redvax1.bitnet > #######/ > > > > > > > > From owner-pine-info@cac.washington.edu Sat Oct 23 00:40:16 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10316; Sat, 23 Oct 93 00:40:16 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24665; Sat, 23 Oct 93 00:29:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24659; Sat, 23 Oct 93 00:29:19 -0700 Received: by digi.syd.deg.csiro.au id AA24102 (5.65c/IDA-1.4.4 for pine mailing list ); Sat, 23 Oct 1993 17:32:32 +1000 Date: Sat, 23 Oct 1993 17:24:12 +1000 (EST) From: Jack Churchill Subject: inboxes To: pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Some time ago there was a discussion on ideas to discourage users leaving their read mail in the inbox. Would you leave your real mail in your letter box after reading it? As a low priority, since I know the pine team are busy with other more important things, is it possible to have the option to force all read mail to be moved automatically to the "saved-messages" folder? Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Sat Oct 23 01:32:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11363; Sat, 23 Oct 93 01:32:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11773; Sat, 23 Oct 93 01:22:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11767; Sat, 23 Oct 93 01:22:46 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16721; Sat, 23 Oct 93 01:22:39 -0700 Date: Sat, 23 Oct 1993 01:21:11 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: inboxes To: Jack Churchill Cc: pine mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Pine 3.87 has an option to specify a read-messages-folder, to which mail is moved after it is read. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Sat, 23 Oct 1993, Jack Churchill wrote: > Some time ago there was a discussion on ideas to discourage users leaving > their read mail in the inbox. Would you leave your real mail in your > letter box after reading it? As a low priority, since I know the pine > team are busy with other more important things, is it possible to have the > option to force all read mail to be moved automatically to the > "saved-messages" folder? > > Jack N. Churchill | Jack.Churchill@dem.csiro.au > CSIRO Division of Exploration and Mining | churchill@decus.com.au > PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 > Australia | Fax: +61 2 887 8921 > From owner-pine-info@cac.washington.edu Sat Oct 23 08:13:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16296; Sat, 23 Oct 93 08:13:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13923; Sat, 23 Oct 93 08:05:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13917; Sat, 23 Oct 93 08:05:18 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20836; Sat, 23 Oct 93 08:05:03 -0700 Date: Sat, 23 Oct 1993 08:04:00 -0700 (PDT) From: Terry Gray Subject: Re: BBOARD... To: "Isaias Callejas Mancilla." Cc: The PINE List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The Pine Update service is now functional again. Let us know if you have any further difficulty. -teg From owner-pine-info@cac.washington.edu Sat Oct 23 10:03:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17674; Sat, 23 Oct 93 10:03:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14726; Sat, 23 Oct 93 09:55:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14720; Sat, 23 Oct 93 09:55:18 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22099; Sat, 23 Oct 93 09:55:07 -0700 Date: Sat, 23 Oct 1993 09:51:41 -0700 (PDT) From: Mark Crispin Subject: Re: Compilation error for v3.87 on SGI IRIX 5.0.1 To: Chris Martin Cc: pine-info@cac.washington.edu In-Reply-To: <12884.9310220948@sunc.sheffield.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ah yes. The newest c-client in the IMAP 3.1 toolkit has this change for the renamed tzname variable, courtesy of Angel Li. You can try substituting it for the one that is in Pine 3.87. Note that the SGI port is now an ANSI port instead of a non-ANSI one, so perhaps someting in the Pine makefile also needs to be changed. A pox on vendors who can't maintain source code compatibility from one release to the next! ;-) From owner-pine-info@cac.washington.edu Sat Oct 23 10:23:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17885; Sat, 23 Oct 93 10:23:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14881; Sat, 23 Oct 93 10:17:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from world.std.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14875; Sat, 23 Oct 93 10:17:12 -0700 Received: from localhost by world.std.com (5.65c/Spike-2.0) id AA26945; Sat, 23 Oct 1993 13:17:11 -0400 Message-Id: <199310231717.AA26945@world.std.com> To: pine-info@cac.washington.edu Subject: Attached text always BASE64 encoded? Date: Sat, 23 Oct 1993 13:17:10 -0400 From: Joe Ilacqua I've just put up 3.87 (from 3.01). Some of my users are complaining that attached text files are being encoded in BASE64 and this seems be the case. I realize the 3.01 use BASE64 if it found any 8 bit charaters or very long lines, but that is not the case here. If there any way to change this behavior? ->Spike From owner-pine-info@cac.washington.edu Sat Oct 23 10:53:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18232; Sat, 23 Oct 93 10:53:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15058; Sat, 23 Oct 93 10:45:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15052; Sat, 23 Oct 93 10:45:01 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22664; Sat, 23 Oct 93 10:44:57 -0700 Date: Sat, 23 Oct 1993 10:25:42 -0700 (PDT) From: Terry Gray Subject: Re: Attached text always BASE64 encoded? To: Joe Ilacqua Cc: pine-info@cac.washington.edu In-Reply-To: <199310231717.AA26945@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 23 Oct 1993, Joe Ilacqua wrote: > I've just put up 3.87 (from 3.01). Some of my users are > complaining that attached text files are being encoded in BASE64 and > this seems be the case. I realize the 3.01 use BASE64 if it found any > 8 bit charaters or very long lines, but that is not the case here. If > there any way to change this behavior? Spike, This change was a very conscious decision; and hence is a feature, not a bug :) We thought very hard about this one, so let me share the rationale. Pine provides two ways of sending text files: 1. By *inclusion*, using the ^R function in the composer 2. By *attachment*, using ^J or the attchmnt header line. Text *inclusion* should be used if the recipient does not have MIME support. Text *attachment* should be used if the recipient *does* have MIME support. But why change the *attachment* behavior for text files? Because we *strongly* believe that any MIME attachment should arrive intact, without modification of any kind. The only way we have to guarantee the integrity of the attachment is to Base64 encode it. (Q-P encoding is not sufficient.) Using MIME attachments should be as safe as doing a file transfer. Once we learned that q-p encoding was not sufficient in all cases to prevent modification of the text attachment during transit through gateways or delivery, we were not willing to jeopardize the reputation of MIME in general and Pine in particular by using the more "readable" encoding, especially given that the ^R alternative was always available when absolute integrity was not needed. Note that this problem completely disappears when your correspondents upgrade to MIME-aware mailers, as we hope they will soon, so that they can fully participate in the Internet mail world. -teg From owner-pine-info@cac.washington.edu Sat Oct 23 11:42:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18837; Sat, 23 Oct 93 11:42:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26991; Sat, 23 Oct 93 11:33:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from world.std.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26985; Sat, 23 Oct 93 11:33:31 -0700 Received: by world.std.com (5.65c/Spike-2.0) id AA08465; Sat, 23 Oct 1993 14:33:30 -0400 Date: Sat, 23 Oct 1993 14:33:30 -0400 From: bzs@world.std.com (Barry Shein) Message-Id: <199310231833.AA08465@world.std.com> To: gray@cac.washington.edu Cc: spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: Terry Gray's message of Sat, 23 Oct 1993 10:25:42 -0700 (PDT) Subject: Attached text always BASE64 encoded? Thanks for the response, now to offer (possibly) some help... We're experiencing that reported wild looping when someone hangs up on Pine (3.87), I used Sun's trace to see what it's looping on (this only reports syscalls, but perhaps that's useful) and here's what it looks like: write (1, "\33[22;1H\33[K", 10) = -1 EIO (I/O error) write (1, "\33[22;29H\33[7m[ \7Unknown command: ".., 39) = -1 EIO (I/O error) write (1, "\33[6;18H", 7) = -1 EIO (I/O error) sigblock (0) = 0 sigstack (0, 0xf7ffead4) = 0 setitimer (0, 0xf7ffead0, 0xf7ffeac0) = 0 getpid () = 20467 kill (20467, 1) = - SIGHUP (1) sigcleanup () = 0 setitimer (0, 0xf7ffead0, 0xf7ffeac0) = 0 gettimeofday (0xf7ffeae8, 0) = 0 write (1, "\33[22;1H\33[K", 10) = -1 EIO (I/O error) write (1, "\33[22;29H\33[7m[ \7Unknown command: ".., 39) = -1 EIO (I/O error) write (1, "\33[6;18H", 7) = -1 EIO (I/O error) Perhaps one easy fix is that someone, somewhere needs to check for that error return on the write()? Also, not that it is trying to kill() itself with a SIGHUP. Anyhow, perhaps that's helpful. -Barry Shein Software Tool & Die | bzs@world.std.com | uunet!world!bzs Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD From owner-pine-info@cac.washington.edu Sat Oct 23 11:43:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18861; Sat, 23 Oct 93 11:43:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15378; Sat, 23 Oct 93 11:36:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from coho.halcyon.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15372; Sat, 23 Oct 93 11:36:13 -0700 Received: by halcyon.com id AA04274 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sat, 23 Oct 1993 11:36:10 -0700 From: Ralph Sims Message-Id: <199310231836.AA04274@halcyon.com> Subject: Re: Attached text always BASE64 encoded? To: gray@cac.washington.edu (Terry Gray) Date: Sat, 23 Oct 1993 11:36:08 -0700 (PDT) Cc: spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: from "Terry Gray" at Oct 23, 93 10:25:42 am X-Mailer: ELM [version 2.4 PL13] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1832 > On Sat, 23 Oct 1993, Joe Ilacqua wrote: > > I've just put up 3.87 (from 3.01). Some of my users are > > complaining that attached text files are being encoded in BASE64 and > > this seems be the case. I realize the 3.01 use BASE64 if it found any > > 8 bit charaters or very long lines, but that is not the case here. If > > there any way to change this behavior? [ good discussion deleted ] > Note that this problem completely disappears when your correspondents > upgrade to MIME-aware mailers, as we hope they will soon, so that they > can fully participate in the Internet mail world. However, pine is designed for folks that have little awareness of unix/ms-dos tricks. If a pine user uploads a file prepared with an ms-dos editor that leaves a a ctrl-z EOF, or a ctrl-m at the end of each line, pine makes the determination that this is a binary file, suitable for BASE64 encoding. This was documented by one of our users, Doug Palm, and brought to the development team's attention. It was indicated by Dave Miller (I think) that the 'feature' will be re-designed in the upcoming 3.88 maintenance release, in order to ease the pain. We should not assume that pine's users know how to strip these control characters from uploaded files, or use zip/unzip to remove them, in order to make them 'true' ascii files, compliant to unix format. While this may have been planned as a 'feature', it is rapidly becoming an adminstrative/helpdesk headache. Messages posted with pine traverse many networks, including CompuServe, which is arguably one of the largest single mail systems around; CIS's mail interfaces do not provide for MIME attachments, it appears. While the rest of the world ramps up to MIME, pine is producing messages that can't be using the recipient's {traditional,only available} mail reader. From owner-pine-info@cac.washington.edu Sat Oct 23 11:51:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19052; Sat, 23 Oct 93 11:51:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15441; Sat, 23 Oct 93 11:42:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15435; Sat, 23 Oct 93 11:42:55 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23328; Sat, 23 Oct 93 11:42:52 -0700 Date: Sat, 23 Oct 1993 11:35:35 -0700 (PDT) From: Terry Gray Subject: Re: SIGHUP loop (was Attached text always BASE64 encoded?) To: Barry Shein Cc: spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: <199310231833.AA08465@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks Barry! This SIGHUP looping bug is one of several reasons why a pine 3.88 (mtce release) will appear much sooner than we planned :( Probably before the end of next week... -teg From owner-pine-info@cac.washington.edu Sat Oct 23 12:01:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19156; Sat, 23 Oct 93 12:01:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15500; Sat, 23 Oct 93 11:53:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15494; Sat, 23 Oct 93 11:53:51 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23435; Sat, 23 Oct 93 11:53:47 -0700 Date: Sat, 23 Oct 1993 11:43:23 -0700 (PDT) From: Terry Gray Subject: Re: Attached text always BASE64 encoded? To: Ralph Sims Cc: spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: <199310231836.AA04274@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ralph, The question of when to encode *in-line* text, as opposed to *attachments* is definitely distinct, and 3.87 appears to be too aggressive in when it encodes in-line text. I personally feel very strongly that Pine is doing the right thing in always encoding *attachments*, but I do not feel that Pine should be imposing MIME-ness on everyone else for *in-line* text. I need to talk with the team about exactly what will be done, but your (and Doug's) input on this was received loud and clear. -teg On Sat, 23 Oct 1993, Ralph Sims wrote: > > On Sat, 23 Oct 1993, Joe Ilacqua wrote: > > > > I've just put up 3.87 (from 3.01). Some of my users are > > > complaining that attached text files are being encoded in BASE64 and > > > this seems be the case. I realize the 3.01 use BASE64 if it found any > > > 8 bit charaters or very long lines, but that is not the case here. If > > > there any way to change this behavior? > > [ good discussion deleted ] > > > Note that this problem completely disappears when your correspondents > > upgrade to MIME-aware mailers, as we hope they will soon, so that they > > can fully participate in the Internet mail world. > > However, pine is designed for folks that have little awareness of > unix/ms-dos tricks. If a pine user uploads a file prepared with an > ms-dos editor that leaves a a ctrl-z EOF, or a ctrl-m at the end of > each line, pine makes the determination that this is a binary file, > suitable for BASE64 encoding. This was documented by one of our users, > Doug Palm, and brought to the development team's attention. It was > indicated by Dave Miller (I think) that the 'feature' will be > re-designed in the upcoming 3.88 maintenance release, in order to ease > the pain. > > We should not assume that pine's users know how to strip these control > characters from uploaded files, or use zip/unzip to remove them, in > order to make them 'true' ascii files, compliant to unix format. While > this may have been planned as a 'feature', it is rapidly becoming an > adminstrative/helpdesk headache. Messages posted with pine traverse > many networks, including CompuServe, which is arguably one of the > largest single mail systems around; CIS's mail interfaces do not > provide for MIME attachments, it appears. While the rest of the world > ramps up to MIME, pine is producing messages that can't be using the > recipient's {traditional,only available} mail reader. > > From owner-pine-info@cac.washington.edu Sat Oct 23 15:21:03 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21932; Sat, 23 Oct 93 15:21:03 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27751; Sat, 23 Oct 93 15:05:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mhc.mtholyoke.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27745; Sat, 23 Oct 93 15:05:44 -0700 Received: by mhc.mtholyoke.edu (5.57/Ultrix4.2a_930410.01) id AA20764; Sat, 23 Oct 93 18:05:16 -0400 Date: Sat, 23 Oct 1993 18:00:53 -0400 (EDT) From: "Michael A. Crowley" Subject: Re: inboxes To: Jack Churchill Cc: pine mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 23 Oct 1993, Jack Churchill wrote: > Some time ago there was a discussion on ideas to discourage users leaving > their read mail in the inbox. Would you leave your real mail in your > letter box after reading it? As a low priority, since I know the pine > team are busy with other more important things, is it possible to have the > option to force all read mail to be moved automatically to the > "saved-messages" folder? > > Jack N. Churchill | Jack.Churchill@dem.csiro.au As an option that could be set either by the user or manager, that would be like one Berkeley mail has had that saved messages to "mbox". As a style, however, it can result in people reading mail, not deleting that mail, and forgetting about it because it goes to another folder. Leaving it in the system inbox can encourage people to specifically delete or save messages, and I believe that more messages are thus appropriately deleted. Mike From owner-pine-info@cac.washington.edu Sat Oct 23 16:34:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22704; Sat, 23 Oct 93 16:34:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17180; Sat, 23 Oct 93 16:26:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17174; Sat, 23 Oct 93 16:26:35 -0700 Received: by digi.syd.deg.csiro.au id AA24903 (5.65c/IDA-1.4.4 for pine mailing list ); Sun, 24 Oct 1993 09:29:13 +1000 Date: Sun, 24 Oct 1993 09:04:38 +1000 (EST) From: Jack Churchill Subject: Re: inboxes To: "Michael A. Crowley" Cc: pine mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 23 Oct 1993, Michael A. Crowley wrote: > As an option that could be set either by the user or manager, that > would be like one Berkeley mail has had that saved messages to "mbox". > As a style, however, it can result in people reading mail, not deleting > that mail, and forgetting about it because it goes to another folder. > Leaving it in the system inbox can encourage people to specifically > delete or save messages, and I believe that more messages are thus > appropriately deleted. Yes, I had discussions which went along the same kind of reasoning about the limitations of having read mail moved to another folder. I suppose we can't have everything but I still like to handle the inbox like real mail, anyone who wants to read their real mail has to remove it from their mail box at home or the office, read it and file it away (includes the rubbish bin). Unfortunately, a lot of people don't follow your (and my) nice habbit of regularly cleaning up the inbox. What better way is there to force people to clean out their mail than if they reach their disk quota limit if their read mail is automatically moved to another folder? The same happens to me if I don't file away my real mail for more than a week - my desk starts to look like a rubbish tip and I can't do any work. Also, I prefer just one person to suffer disk quota problems than all of them suffer disk space problems as is the current situation if the /var/spool/mail area gets filled with bloated inboxes. I have in mind to install a cron jobs that will check everyones "read-messages" folder, their quotas and other things and send a reminder message about cleaning out their folder(s) before a dangerous level is reached. If they want to leave any of their mail after the cleanup in the "read-messages" folder instead of filing them into appropriate folders then that's their decision. That sought of duplicates the "saved-messages" folder. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Sat Oct 23 18:40:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24159; Sat, 23 Oct 93 18:40:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17839; Sat, 23 Oct 93 18:30:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17833; Sat, 23 Oct 93 18:30:51 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28111; Sat, 23 Oct 93 18:30:42 -0700 Date: Sat, 23 Oct 1993 18:30:25 -0700 (PDT) From: Terry Gray Subject: Re: I want Elm's outgoing mail folder feature in PINE To: Billy Barron Cc: pine-info@cac.washington.edu, susie@utdallas.edu, Shane Davis In-Reply-To: <93Oct22.095008cdt.74082@utdallas.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It's on the list! -teg On Fri, 22 Oct 1993, Billy Barron wrote: > Is there any way to get PINE to do what Elm does with outgoing mail? > That is to have it saved under the username of the person you are > sending to. > > If not, could it be added in a future release? > > -- > Billy Barron, Network Services Manager, Univ of Texas at Dallas > billy@utdallas.edu > From owner-pine-info@cac.washington.edu Sat Oct 23 21:39:14 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26049; Sat, 23 Oct 93 21:39:14 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29033; Sat, 23 Oct 93 21:29:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from coho.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29027; Sat, 23 Oct 93 21:29:53 -0700 Received: by halcyon.com id AA07629 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sat, 23 Oct 1993 21:29:49 -0700 From: Ralph Sims Message-Id: <199310240429.AA07629@halcyon.com> Subject: Re: Attached text always BASE64 encoded? To: gray@cac.washington.edu (Terry Gray) Date: Sat, 23 Oct 1993 21:29:47 -0700 (PDT) Cc: ralphs@halcyon.com, spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: from "Terry Gray" at Oct 23, 93 11:43:23 am X-Mailer: ELM [version 2.4 PL13] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 526 > I personally feel very strongly that Pine is doing the right thing in > always encoding *attachments*, but I do not feel that Pine should be > imposing MIME-ness on everyone else for *in-line* text. Perhaps a suggestion: when text is yanked in with a CTRL-R, then process it as-is--do not invoke encoding. If text is sent as an attachment, then use whatever encoding scheme prevails. Or, when text is yanked in, ask if this should be encoded or processed as-is. I can see times where both features would be useful. From owner-pine-info@cac.washington.edu Sat Oct 23 21:49:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26185; Sat, 23 Oct 93 21:49:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18818; Sat, 23 Oct 93 21:42:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18812; Sat, 23 Oct 93 21:42:21 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00279; Sat, 23 Oct 93 21:42:14 -0700 Date: Sat, 23 Oct 1993 21:33:31 -0700 (PDT) From: Terry Gray Subject: Re: inline text encoding (was Attached text always BASE64 encoded?) To: Ralph Sims Cc: ralphs@halcyon.com, spike@world.std.com, pine-info@cac.washington.edu In-Reply-To: <199310240429.AA07629@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ralph, There probably doesn't want to be any distinction between what is typed in directly and what is included via ^R... the question is what conditions should trigger q-p or b64 encoding of the inline text. We don't want Pine to be overly obnoxious to non-MIME users, but at the same time we want to fulfil the requirements of the MIME RFCs, and make sure that Pine does the right thing for our non-US-ASCII friends. We have been using an algorithmic approach to triggering the inline encoding, but the algorithm needs refinement. Stay tuned... -teg On Sat, 23 Oct 1993, Ralph Sims wrote: > > I personally feel very strongly that Pine is doing the right thing in > > always encoding *attachments*, but I do not feel that Pine should be > > imposing MIME-ness on everyone else for *in-line* text. > > Perhaps a suggestion: when text is yanked in with a CTRL-R, then > process it as-is--do not invoke encoding. If text is sent as an > attachment, then use whatever encoding scheme prevails. Or, when text > is yanked in, ask if this should be encoded or processed as-is. I can > see times where both features would be useful. > From owner-pine-info@cac.washington.edu Sun Oct 24 08:24:15 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03620; Sun, 24 Oct 93 08:24:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01327; Sun, 24 Oct 93 08:11:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01321; Sun, 24 Oct 93 08:11:10 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA15961 (5.65b/CWI-3.3); Sun, 24 Oct 1993 16:11:06 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA27680; Sun, 24 Oct 93 15:09:53 GMT (MET) Message-Id: <9310241509.AA27680@wilg.bull.nl> To: Pine Info Subject: How to disable the addition of '@hostname' to addresses? Date: Sun, 24 Oct 93 16:09:52 MET From: Jos Vos Pine automatically appends an '@' followed by my local hostname to outgoing addresses without an '@'. Is there a simple way to disable this (or to hack the code for this purpose? In my opinion this is a function of the mail transport agent (sendmail in our case), not of the mail user agent. Especially, the "rewriting" of hosta!hostb!user to hosta!hostb!user@myhost I don't like, because this type of addresses often confuses some mailers (I know it's officially correct). -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Sun Oct 24 12:48:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06483; Sun, 24 Oct 93 12:48:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02138; Sun, 24 Oct 93 12:36:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02132; Sun, 24 Oct 93 12:36:56 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01064; Sun, 24 Oct 93 12:36:47 -0700 Date: Sun, 24 Oct 1993 12:33:09 -0700 (PDT) From: Mark Crispin Subject: Re: How to disable the addition of '@hostname' to addresses? To: Jos Vos Cc: Pine Info In-Reply-To: <9310241509.AA27680@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jos - Pine is a RFC-822 syntax mailer. It is not intended to be a UUCP-syntax mailer. Since Pine runs on DOS configurations as well, it has to take on the responsibility of building proper RFC 822 format headers. If you run sendmail, you can configure your UUCP routing to use RFC-822 syntax using the Domain Name System, or you can configure sendmail to convert RFC-822 syntax to UUCP syntax. Regards, -- Mark -- From owner-pine-info@cac.washington.edu Sun Oct 24 23:58:11 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13775; Sun, 24 Oct 93 23:58:11 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04543; Sun, 24 Oct 93 23:50:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04537; Sun, 24 Oct 93 23:50:16 -0700 Received: by mail.swip.net (5.65c8-/1.2) id AA25123; Mon, 25 Oct 1993 07:50:12 +0100 Received: by abalon.se (4.1/SMI-4.1) id AA22737; Mon, 25 Oct 93 07:44:39 +0100 Date: Mon, 25 Oct 93 07:44:39 +0100 From: clindh@abalon.se (Christer Lindh) Message-Id: <9310250644.AA22737@abalon.se> To: pine-info@cac.washington.edu Subject: input/output character mapping in Unix-Pine Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit A long time ago I wished for input/output character mapping for Pine (back then it was UNIX only). Now I see that you have put it in, but unfortunately for PC only!! With a slight generalization of this it becomes usable for UNIX as well. Example; we would use it for users that have old terminals with ISO 646-SE, the swedish 7bit charset where "{}|[]\" are replaced by our national characters. I want to map these users input/output to/from ISO 8859-1 else they can't read mails using 8859/1 and what they write will become incomprehensible when viewed on a 8bit terminal. (It'll look like a C-program...) It seems I could use the PC-mapping stuff if it became enabled for UNIX as well. And why are the maps named by two env variables and not by entries in the pinerc-file like all other options? -- :: clindh@abalon.se :: o/ :: :: :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. :: :: (MIME compliant) :: /!> :: Love it or leave it. :: :: * All disclaimers apply * :: ! climb! :: :: From owner-pine-info@cac.washington.edu Sun Oct 24 23:58:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13806; Sun, 24 Oct 93 23:58:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27824; Sun, 24 Oct 93 23:48:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27818; Sun, 24 Oct 93 23:48:27 -0700 Received: by mail.swip.net (5.65c8-/1.2) id AA24878; Mon, 25 Oct 1993 07:48:23 +0100 Received: by abalon.se (4.1/SMI-4.1) id AA22515; Mon, 25 Oct 93 07:28:51 +0100 Date: Mon, 25 Oct 93 07:28:51 +0100 From: clindh@abalon.se (Christer Lindh) Message-Id: <9310250628.AA22515@abalon.se> To: pine-info@cac.washington.edu Subject: Re: inline text encoding (was Attached text always BASE64 encoded?) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > We don't want Pine to be overly obnoxious to non-MIME users, but at > the same time we want to fulfil the requirements of the MIME RFCs, > and make sure that Pine does the right thing for our non-US-ASCII > friends. It does the right thing when the receiver has MIME, but with the advance of 8bit SMTP there's no need to QP-encode. BTW, most SMTPs in Sweden are already hacked to pass 8 bits... So it would be nice if it was possible to turn the QP feature off, preferably per composed mail or at least in the rc-file. Put in "Content-Transfer-Encoding: 8bit" instead if QP is not used. 99% of my contacts does not have MIME-capabale readers yet. They are mostly users and have not a slightest idea on how to install metamail" nor Pine. They get terribly confused by all this =E5 stuff... Especially the line-breaking! (they are sort of used to see all kinds of weird characters instead of our national characters...) So, in short; Pine should offer all these nice MIMEifications, they come to great use in-house and between MIME-compliant mailers but as most of the email world doesn't do MIME yet, please make the encoding stuff more configurable. -- :: clindh@abalon.se :: o/ :: :: :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. :: :: (MIME compliant) :: /!> :: Love it or leave it. :: :: * All disclaimers apply * :: ! climb! :: :: From owner-pine-info@cac.washington.edu Mon Oct 25 00:08:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14010; Mon, 25 Oct 93 00:08:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27884; Sun, 24 Oct 93 23:58:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27876; Sun, 24 Oct 93 23:58:20 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA05370 (5.65b/CWI-3.3); Mon, 25 Oct 1993 07:58:17 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA01332; Mon, 25 Oct 93 06:56:58 GMT (MET) Message-Id: <9310250656.AA01332@wilg.bull.nl> To: Mark Crispin Cc: Pine Info Subject: Re: How to disable the addition of '@hostname' to addresses? In-Reply-To: Your message of "Sun, 24 Oct 93 12:33:09 MET." Date: Mon, 25 Oct 93 07:56:56 MET From: Jos Vos > Pine is a RFC-822 syntax mailer. It is not intended to be a UUCP-syntax > mailer. Since Pine runs on DOS configurations as well, it has to take on > the responsibility of building proper RFC 822 format headers. > > If you run sendmail, you can configure your UUCP routing to use RFC-822 > syntax using the Domain Name System, or you can configure sendmail to > convert RFC-822 syntax to UUCP syntax. We have Sendmail running, using UUCP to the outside world and SMTP in our internal network. And our Sendmail *does* use domain addresses as much as possible. But: that's just the reason that I don't want Pine to mungle headers. Our Sendmail takes its own decisions to change headers. -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Mon Oct 25 00:29:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14230; Mon, 25 Oct 93 00:29:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04668; Mon, 25 Oct 93 00:20:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04662; Mon, 25 Oct 93 00:20:38 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00947; Mon, 25 Oct 93 00:20:32 -0700 Date: Mon, 25 Oct 1993 00:06:13 -0700 (PDT) From: Mark Crispin Reply-To: Mark Crispin Subject: Re: How to disable the addition of '@hostname' to addresses? To: Jos Vos Cc: Pine Info In-Reply-To: <9310250656.AA01332@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I don't think you understand what is going on inside Pine. Pine does not ``mungle'' headers. Pine accepts input and parses it into a structured representation of that particular field. While doing so, it does services such as address book lookup, etc. When the message it sent, it generates a header from that structured representation. The original input is not used at all. This structured representation includes a ``hostname'' subfield in the case of an address field. This is not an optional field. It gets filled in with the local domain if it is not specified. The alternative is to give you an error message if you don't specify a hostname; I don't think anyone wants that! There have been many problems caused by mail programs which fail to set up fully-qualified e-mail addresses prior to sending the mail. The Internet e-mail development mailing list archives are filled with horror stories of such dating from at least 1977. The potential for user confusion and technical problems with incomplete e-mail addresses is *enormous*. What you are really asking is not ``make Pine not mungle headers''. In actuality, you are saying ``make Pine use exactly what the user typed in instead of generating proper Internet format, and trust that sendmail will mungle the headers to be valid.'' Please consider moving your UUCP network towards using the domain name system via MX records instead of UUCP routing syntax. This is a more robust system and is better supported by modern e-mail tools such as Pine. I do not see any means that we can make the hostname field optional in addresses without inflicting 16+ years' worth of documented horrors on novice users. From owner-pine-info@cac.washington.edu Mon Oct 25 01:10:50 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15472; Mon, 25 Oct 93 01:10:50 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04874; Mon, 25 Oct 93 00:59:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.NL.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04864; Mon, 25 Oct 93 00:59:19 -0700 Received: from nlbull by sun4nl.NL.net via EUnet id AA07348 (5.65b/CWI-3.3); Mon, 25 Oct 1993 08:59:16 +0100 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA01573; Mon, 25 Oct 93 07:56:55 GMT (MET) Message-Id: <9310250756.AA01573@wilg.bull.nl> To: Mark Crispin Cc: Pine Info Subject: Re: How to disable the addition of '@hostname' to addresses? In-Reply-To: Your message of "Mon, 25 Oct 93 00:06:13 MET." Date: Mon, 25 Oct 93 08:56:53 MET From: Jos Vos > What you are really asking is not ``make Pine not mungle headers''. In > actuality, you are saying ``make Pine use exactly what the user typed in > instead of generating proper Internet format, and trust that sendmail > will mungle the headers to be valid.'' Yes, that's exactly what I'm asking. Sendmail is much better occupied for that job than any mail user agent. > Please consider moving your UUCP network towards using the domain name > system via MX records instead of UUCP routing syntax. This is a more > robust system and is better supported by modern e-mail tools such as Pine. We *do* use domain addresses for almost all destinations (even UUCP hosts). But in some cases people use, for whatever reason, use an UUCP-path. -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Mon Oct 25 02:00:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16546; Mon, 25 Oct 93 02:00:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28682; Mon, 25 Oct 93 01:49:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28676; Mon, 25 Oct 93 01:49:20 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA29801 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Mon, 25 Oct 93 03:49:18 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA14123; Mon, 25 Oct 93 03:49:17 CDT Date: Mon, 25 Oct 1993 03:47:42 -0500 (CDT) From: Matt Simmons Subject: YAFR (Yet another feature request) To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When one receives mail from a list (i.e. mail not sent directly to one... there's a cool sentence for ya...) is it possible that pine could ask one whether it should grab (when one uses the TakeAddr command) the address of the sender or the address of the To: line? This would be cool for saving the addresses of mailing lists... Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Mon Oct 25 02:42:59 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17506; Mon, 25 Oct 93 02:42:59 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05276; Mon, 25 Oct 93 02:31:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ibm4.ruf.uni-freiburg.de by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05270; Mon, 25 Oct 93 02:31:10 -0700 Received: by ibm4.ruf.uni-freiburg.de (AIX 3.2/UCB 5.64/4.03) id AA31628; Mon, 25 Oct 1993 10:31:01 +0100 Date: Mon, 25 Oct 1993 10:29:34 +0100 (MEZ) From: Guenter Mueller Subject: Bug Report (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, If I use pine with aixterm window size 108x57 the header line will be written to line 0 and the content of the window is garbagged. (The cursor is not where it should be!) If I use ctrl-l the correct content will be displayed, but if I fill in text in the the header region it is again garbagged. Resizing the window to 107x57 or 109x57 will give correct contents and no garbage! Isn't it funny that only a x-size of 108 characters will have an effect and I have set my default size to just 108 characters? Kind Regards Guenter Guenter Mueller gmueller@ibm4.ruf.uni-freiburg.de Phone: +49 761 203 -4622 University of Freiburg - Computing Center FAX: -4643 >>>>>>>>>>>>>>>>> New Phone and FAX Numbers since 10.10.93 <<<<<<<<<<<<<<<<<< From owner-pine-info@cac.washington.edu Mon Oct 25 09:15:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24927; Mon, 25 Oct 93 09:15:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02830; Mon, 25 Oct 93 08:49:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ees1a0.engr.ccny.cuny.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02824; Mon, 25 Oct 93 08:49:05 -0700 Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1) id AA08402; Mon, 25 Oct 93 11:49:01 EDT Date: Mon, 25 Oct 1993 11:38:10 -0400 (EDT) From: Dan Schlitt Subject: Re: How to disable the addition of '@hostname' to addresses? To: Mark Crispin Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mark is exactly right about using fully qualified domain names in the headers generated by Pine. It would be nice if all MUAs did the same. Please don't change it. Mixed bang and @ addresses are a bad thing because they are ambiguous in meaning. Users probably should not be generating full bang paths either. The topology of the uucp network tends to change more rapidly than most people's knowledge of it. If one needs to use bang paths for delivery then the MTA should generate them and not the user. There have long been MTAs that can both handle domain style addresses to uucp sites and generate the correct bang path for delivery from the uucp maps. People who use uucp should use that software and not burden programs like Pine with those problems. /dan Dan Schlitt School of Engineering Computer Systems dan@ee-mail.engr.ccny.cuny.edu City College of New York (212)650-6760 New York, NY 10031 From owner-pine-info@cac.washington.edu Mon Oct 25 09:28:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26449; Mon, 25 Oct 93 09:28:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03667; Mon, 25 Oct 93 09:16:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03655; Mon, 25 Oct 93 09:15:55 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA09178; Mon, 25 Oct 93 11:15:37 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA07214; Tue, 26 Oct 93 00:11:50 +0800 Date: Mon, 25 Oct 1993 23:51:17 +0800 (TPE) From: Ed Greshko Subject: Re: How to disable the addition of '@hostname' to addresses? To: Jos Vos Cc: Mark Crispin , Pine Info In-Reply-To: <9310250756.AA01573@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Oct 1993, Jos Vos wrote: > > What you are really asking is not ``make Pine not mungle headers''. In > > actuality, you are saying ``make Pine use exactly what the user typed in > > instead of generating proper Internet format, and trust that sendmail > > will mungle the headers to be valid.'' > > Yes, that's exactly what I'm asking. > Sendmail is much better occupied for that job than any mail user agent. I must say that I fully agree with Mark. Even to this day I see broken mailers and broken sendmails were mail shows up on my doorstep in the form user@hostname...and they are no where close to being in my domain. You are making a bad assumption about sendmail since I think you are also assuming that everyone knows how to properly configure it to follow the rules. I can add to the "horror" stories that prove it bad a bad assumption. For pine to be the mailer it wants to be, i.e. the mailer of choice for the non-techincal, it needs to make inteligent decisions based upon standards. I personally find that to be commended. Not only that...it helps to reduce the "mistakes" made by even the most techie mail user. Within our local network we use SMTP, IMAP, POP2, POP3 and UUCP[B as protocols. For ease of making routing decisions and getting everything to interoperate...we don't fool around we simply use fully qualified domain names all of the time. The only thing we have is a "fire wall" that strips off the host part from all mail escaping our domain. If you want a mailer to do as you requested....try /bin/mail :-) Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Mon Oct 25 09:48:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28325; Mon, 25 Oct 93 09:48:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04116; Mon, 25 Oct 93 09:33:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun2.nsfnet-relay.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04110; Mon, 25 Oct 93 09:33:40 -0700 Via: uk.co.ggr; Mon, 25 Oct 1993 16:17:19 +0000 Received: from localhost by uk0x08.ggr.co.uk; Mon, 25 Oct 1993 16:18:30 GMT Received: from mx1.cac.washington.edu by ben.britain.eu.net via EUnet with SMTP (PP) id ; Mon, 25 Oct 1993 16:15:21 +0000 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02830; Mon, 25 Oct 93 08:49:10 -0700 Original-Sender: owner-pine-info@cac.washington.edu Received: from ees1a0.engr.ccny.cuny.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02824; Mon, 25 Oct 93 08:49:05 -0700 Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1) id AA08402; Mon, 25 Oct 93 11:49:01 EDT Date: Mon, 25 Oct 1993 11:38:10 -0400 (EDT) From: Dan Schlitt Subject: Re: How to disable the addition of '@hostname' to addresses? To: Mark Crispin Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mark is exactly right about using fully qualified domain names in the headers generated by Pine. It would be nice if all MUAs did the same. Please don't change it. Mixed bang and @ addresses are a bad thing because they are ambiguous in meaning. Users probably should not be generating full bang paths either. The topology of the uucp network tends to change more rapidly than most people's knowledge of it. If one needs to use bang paths for delivery then the MTA should generate them and not the user. There have long been MTAs that can both handle domain style addresses to uucp sites and generate the correct bang path for delivery from the uucp maps. People who use uucp should use that software and not burden programs like Pine with those problems. /dan Dan Schlitt School of Engineering Computer Systems dan@ee-mail.engr.ccny.cuny.edu City College of New York (212)650-6760 New York, NY 10031 From owner-pine-info@cac.washington.edu Mon Oct 25 10:53:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00441; Mon, 25 Oct 93 10:53:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05551; Mon, 25 Oct 93 10:37:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05545; Mon, 25 Oct 93 10:37:07 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10061; Mon, 25 Oct 93 10:37:02 -0700 Date: Mon, 25 Oct 1993 10:34:50 -0700 (PDT) From: David L Miller Subject: Re: YAFR (Yet another feature request) To: Matt Simmons Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have several planned enhancements for the TakeAddr command. This is a very reasonable one to add to the list. Thanks for the suggestion! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 25 Oct 1993, Matt Simmons wrote: > When one receives mail from a list (i.e. mail not sent directly to one... > there's a cool sentence for ya...) is it possible that pine could ask > one whether it should grab (when one uses the TakeAddr command) the > address of the sender or the address of the To: line? This would be cool > for saving the addresses of mailing lists... > > Devoted _n______________________________________________ _________________ > Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| > Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | > Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| > =========\ Walt Disney World Monorail System || > LCA _____\________________________________________________||_________________ > __/ This highway's in perfect shape. Quick! Thank god I'm not a > _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) > > > From owner-pine-info@cac.washington.edu Mon Oct 25 12:03:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03144; Mon, 25 Oct 93 12:03:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06781; Mon, 25 Oct 93 11:37:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tiberius.safb.af.mil by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06775; Mon, 25 Oct 93 11:37:28 -0700 Received: by tiberius.safb.af.mil (4.1/SMI-4.1) id AA19242; Mon, 25 Oct 93 13:38:08 CDT Date: Mon, 25 Oct 1993 13:28:53 -0500 (CDT) From: "John Daum... 618-256-6835" Subject: Wanted: three versions of BASE64.... To: Pine Help List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Since many existing mail programs support only uuEncode/uuDecode (CCMAIL, DaaVinci) AND since pine sends attachments as BASE64, could you provide the a source for BASE64 on MS WINDOWS, DOS, and for the MACintosh - thus allowing those poor unfortunates the ability to decode pine's BASE64 attachments??? Thanks, John E. Daum aka: <<<< 618-256-6835 or 618-632-2456 via ms bell OR o0-0o daumj@tiberius.safb.af.mil on the Internet --ooO-(_)-Ooo--- From owner-pine-info@cac.washington.edu Mon Oct 25 13:49:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06851; Mon, 25 Oct 93 13:49:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08874; Mon, 25 Oct 93 13:32:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08868; Mon, 25 Oct 93 13:32:38 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04834; Mon, 25 Oct 93 13:32:31 -0700 Date: Mon, 25 Oct 1993 13:30:28 -0700 (PDT) From: Terry Gray Subject: Re: Wanted: three versions of BASE64.... To: "John Daum... 618-256-6835" Cc: Pine Help List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Oct 1993, John Daum... 618-256-6835 wrote: > Since many existing mail programs support only uuEncode/uuDecode (CCMAIL, > DaaVinci) AND since pine sends attachments as BASE64, could you provide > the a source for BASE64 on MS WINDOWS, DOS, and for the MACintosh - thus > allowing those poor unfortunates the ability to decode pine's BASE64 > attachments??? The following announcement may be of general interest... -teg ---------- Forwarded message ---------- Date: Sat, 25 SEP 1993 11:09:50 -0400 From: John Gardiner Myers Subject: Announcing mpack Chris Newman and I are pleased to announce the release of mpack 1.0 Mpack and munpack are utilities for encoding and decoding (respectively) binary files in MIME (Multipurpose Internet Mail Extensions) format mail messages. In short, they are the MIME equivalent of uuencode and uudecode. For compabibility with older forms of transferring binary files, the munpack program can also decode messages in split-uuencoded format. Mpack/munpack are minimally MIME-conformant and support the Content-MD5: header. Source for unix, pc, and mac systems may be obtained either from comp.sources.reviewed or by anonymous FTP to export.acs.cmu.edu:pub/mpack/mpack-1.0-src.tar.Z Compiled executables for pc and mac systems are available by anonymos FTP to export.cs.cmu.edu:pub/mpack/mpack-1.0-pc.tar.Z and mpack-1.0-mac.hqx, respectively. From owner-pine-info@cac.washington.edu Mon Oct 25 18:03:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16152; Mon, 25 Oct 93 18:03:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13981; Mon, 25 Oct 93 17:23:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13975; Mon, 25 Oct 93 17:23:32 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA10552; Mon, 25 Oct 93 19:23:16 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA08563; Tue, 26 Oct 93 07:59:18 +0800 Date: Tue, 26 Oct 1993 07:52:47 +0800 (TPE) From: Ed Greshko Subject: Re: Wanted: three versions of BASE64.... To: Terry Gray Cc: "John Daum... 618-256-6835" , Pine Help List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Oct 1993, Terry Gray wrote: > > On Mon, 25 Oct 1993, John Daum... 618-256-6835 wrote: > > > Since many existing mail programs support only uuEncode/uuDecode (CCMAIL, > > DaaVinci) AND since pine sends attachments as BASE64, could you provide > > the a source for BASE64 on MS WINDOWS, DOS, and for the MACintosh - thus > > allowing those poor unfortunates the ability to decode pine's BASE64 > > attachments??? > > The following announcement may be of general interest... > > -teg > > ---------- Forwarded message ---------- > Date: Sat, 25 SEP 1993 11:09:50 -0400 > From: John Gardiner Myers > Subject: Announcing mpack > > Chris Newman and I are pleased to announce the release of mpack 1.0 > > Mpack and munpack are utilities for encoding and decoding > (respectively) binary files in MIME (Multipurpose Internet Mail > Extensions) format mail messages. In short, they are the MIME > equivalent of uuencode and uudecode. For compabibility with older > forms of transferring binary files, the munpack program can also > decode messages in split-uuencoded format. > > Mpack/munpack are minimally MIME-conformant and support the > Content-MD5: header. > > Source for unix, pc, and mac systems may be obtained either from > comp.sources.reviewed or by anonymous FTP to > export.acs.cmu.edu:pub/mpack/mpack-1.0-src.tar.Z Compiled > executables for pc and mac systems are available by anonymos FTP to > export.cs.cmu.edu:pub/mpack/mpack-1.0-pc.tar.Z and mpack-1.0-mac.hqx, > respectively. What may also be of interest is an SMTP-MIME Gateway to cc:Mail that is scheduled for release soon. You may write me for details if this is of interest. Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Mon Oct 25 21:44:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20059; Mon, 25 Oct 93 21:44:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16800; Mon, 25 Oct 93 21:29:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16794; Mon, 25 Oct 93 21:29:47 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA26012; Mon, 25 Oct 1993 23:33:42 -0500 Date: Mon, 25 Oct 1993 23:32:52 -0500 (CDT) From: "Robert A. Hayden" Subject: error To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I just got the following error and was booted. I have no clue what it is and I wasn't doing anything except reading a message and got more mail. *shrug* ------- Bug in Pine detected: "Bad msgno in mail_fetchstructure". ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> Veteran of the Bermuda Triangle \/ Finger for PGP 2.3a Public Key <=> Expeditionary Force -- 1993-1951 -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Mon Oct 25 22:07:51 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20472; Mon, 25 Oct 93 22:07:51 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11336; Mon, 25 Oct 93 21:54:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11330; Mon, 25 Oct 93 21:54:52 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02448; Mon, 25 Oct 93 21:54:47 -0700 Date: Mon, 25 Oct 1993 21:49:56 -0700 (PDT) From: Mark Crispin Subject: re: error To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 25 Oct 1993 23:32:52 -0500 (CDT), Robert A. Hayden wrote: > I just got the following error and was booted. I have no clue what it is > and I wasn't doing anything except reading a message and got more mail. > Bug in Pine detected: "Bad msgno in mail_fetchstructure". Thank you for your bug report, and please accept our apologies for the difficulty you encountered. Without additional information (such as a core dump) we cannot investigate the cause of this crash further. The message reported that an internal consistency check in a library called by Pine failed; however by itself that doesn't help us much. However, we believe that we have identified a bug in Pine which caused this error. This problem should be fixed in Pine 3.88. We expect to release Pine 3.88 in the very near future. If it happens to you again and you get a core dump, please let us know (and if possible forward the dump to us). Thank you for your continued interest in Pine. Regards, -- Mark -- From owner-pine-info@cac.washington.edu Mon Oct 25 22:38:56 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21097; Mon, 25 Oct 93 22:38:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17522; Mon, 25 Oct 93 22:27:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17516; Mon, 25 Oct 93 22:26:57 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA26884; Tue, 26 Oct 1993 00:30:52 -0500 Date: Tue, 26 Oct 1993 00:28:25 -0500 (CDT) From: "Robert A. Hayden" Subject: Re: error To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Oct 1993, Terry Gray wrote: > On Mon, 25 Oct 1993, Robert A. Hayden wrote: > > > > Bug in Pine detected: "Bad msgno in mail_fetchstructure". > Robert, > Do you still have the "core" file? > If so, could you send it to "pine-bugs@cac.washington.edu" as an > attachment, or otherwise make it available? Sorry, my apologies to everyone. There was no core dump. It simply quit pine, leaving no process existing. Sorry I couldn't be more helpful. I was just leaving the system and I wanted to quickly post the error message before I forgot it. ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> Veteran of the Bermuda Triangle \/ Finger for PGP 2.3a Public Key <=> Expeditionary Force -- 1993-1951 -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Tue Oct 26 09:54:00 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA26450; Tue, 26 Oct 93 09:54:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14435; Tue, 26 Oct 93 09:36:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cosmail1.CTD.ORNL.GOV by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14429; Tue, 26 Oct 93 09:36:34 -0700 Received: from [128.219.128.57] by cosmail1.ctd.ornl.gov (8.5/1.34) id MAA20209; Tue, 26 Oct 1993 12:36:28 -0400 Message-Id: <199310261636.MAA20209@cosmail1.ctd.ornl.gov> X-Sender: jnm@cosmail1 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 26 Oct 1993 12:36:31 -0500 To: pine-info@cac.washington.edu From: jnm@ORNL.GOV (Jamey Maze) Subject: un-hiding headers in nested message (?) Cc: gilesdc@cosmail1.ctd.ornl.gov, doh@cosmail1.ctd.ornl.gov, sui@cosmail1.ctd.ornl.gov Probably a FAQ. If so, sorry... When I forward a message from ALL-IN-1 through PMDF to a UNIX machine, it looks like what you see below. The problem is that Pine (3.85) hides the "Sender" header when displaying the attachment. But without the Sender header, users can't easily see who originated the forwarded message. How can you un-hide headers in Pine? -Thanks! >From MAZEJN%A1%OAX@mr.ctd.ornl.gov Tue Oct 26 12:09:31 1993 >Subject: Fwd: Re: some such >To: jnm@cos1.priv.ornl.gov, jnm@cosmail1.ctd.ornl.gov >MIME-version: 1.0 >Content-type: MULTIPART/MIXED; BOUNDARY="Boundary (ID E1fgfHVGfOMtVcCUvnoCZw)" >Posting-date: Tue, 26 Oct 1993 11:13:00 -0400 (EDT) > >--Boundary (ID E1fgfHVGfOMtVcCUvnoCZw) >Content-type: TEXT/PLAIN; CHARSET=US-ASCII > > forwarded message follows > >--Boundary (ID E1fgfHVGfOMtVcCUvnoCZw) >MIME-version: 1.0 >Content-type: MESSAGE/RFC822 > >Date: Wed, 20 Oct 1993 23:05:00 -0400 (EDT) >Subject: Re: some such... >Sender: Vivian M Baylor >To: rnb%stc06.ctd.ornl.gov%umcgate@mr.ctd.ornl.gov >Cc: "Maze, James N" >MIME-version: 1.0 >Content-type: TEXT/PLAIN; CHARSET=US-ASCII >Posting-date: Wed, 20 Oct 1993 23:12:00 -0400 (EDT) > >... > >--Boundary (ID E1fgfHVGfOMtVcCUvnoCZw)-- -- Jamey Maze Computing and Telecommunications Services E-Mail: JNM Phone: 4-6355 Fax: 6-4992 "How far you go in life depends on your being tender with the young, compassionate with the aged, sympathetic of the striving, and tolerant of the weak and the strong because someday in life you will have been all of these." - George Washington Carver From owner-pine-info@cac.washington.edu Tue Oct 26 10:15:17 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA27035; Tue, 26 Oct 93 10:15:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24614; Tue, 26 Oct 93 10:01:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24608; Tue, 26 Oct 93 10:01:32 -0700 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <07619-0@omega.qmw.ac.uk>; Tue, 26 Oct 1993 16:55:27 +0000 Date: Tue, 26 Oct 1993 16:52:14 +0000 (GMT) From: Laurie Cuthbert Subject: imapd process not dying To: pine-info@cac.washington.edu Cc: A.P.Martin@qmw.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I seem to recall having seen some messages about this before but as we were not having the trouble then I did not save them. Apologies if this has been answered. We are running the imapd that was bundled with pine 3.87 on a Sun ELC with SunOS 4.1.2. We had not noticed any problems with this until today when I noticed that I often logged in to see the message "You have mail" when it should have been telling me I had new mail. On investigation I saw that an imapd process I had started hours earlier was still running. The reason this had not been noticed before was that I normally keep a window open all day, but today I was working from home and coming over a modem (so naturally only staying logged on when necessary). Can someone please let me know whether this has now been fixed or do we have to wait until pine 3.88 A more worrying sympton is that I also had mail completely disappear. I logged on to see the elm "frm" command reporting I had one message - I was doing something else (not running pine) and then ran "frm" again - this time to see no messages! Again I discovered there was an impad process running from a previous session. I seem to recall that there had been problems with Sun sendmail and imapd earlier but I thought these had been fixed. By the way, I also pulled the latest imap.tar.Z - the compilation for the sun build fails with: "mtx.c", line 706: SEEK_SET undefined Regards Laurie Cuthbert From owner-pine-info@cac.washington.edu Tue Oct 26 10:45:16 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA27901; Tue, 26 Oct 93 10:45:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25161; Tue, 26 Oct 93 10:31:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dukemc.mc.duke.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25155; Tue, 26 Oct 93 10:31:18 -0700 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H4KIEI15WW0009F0@mc.duke.edu>; Tue, 26 Oct 1993 13:37:54 EST Date: Tue, 26 Oct 1993 13:35:46 -0500 (EST) From: James Dryfoos- Postmaster Subject: Wastebasket option? To: pine-info@cac.washington.edu Message-Id: <01H4KJF94HXG0009F0@mc.duke.edu> Organization: Duke University Medical Center, Durham NC, USA Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I am used to several email systems that use a wastbasket for deleted messages. This wastebasket holds deleted messages for either a period of time (specified) or until manually purged. The wastebasket is just a folder which one can go back to and reread a deleted message. I like this feature and have not found this in Pine. Have I just missed it? If not, I would like to suggest it is a future option. -- Jim From owner-pine-info@cac.washington.edu Tue Oct 26 13:44:34 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03952; Tue, 26 Oct 93 13:44:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15963; Tue, 26 Oct 93 13:30:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15957; Tue, 26 Oct 93 13:30:19 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03145; Tue, 26 Oct 93 13:30:10 -0700 Date: Tue, 26 Oct 1993 13:25:49 -0700 (PDT) From: Mark Crispin Subject: re: imapd process not dying To: Laurie Cuthbert Cc: pine-info@cac.washington.edu, A.P.Martin@qmw.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 26 Oct 1993 16:52:14 +0000 (GMT), Laurie Cuthbert wrote: > We are running the imapd that was bundled with pine 3.87 on a Sun ELC > with SunOS 4.1.2. We had not noticed any problems with this until today > when I noticed that I often logged in to see the message "You have mail" > when it should have been telling me I had new mail. On investigation I > saw that an imapd process I had started hours earlier was still running. > The reason this had not been noticed before was that I normally keep a > window open all day, but today I was working from home and coming over a > modem (so naturally only staying logged on when necessary). This seems to be consistant with what happens when you have a living Pine reading your mail. Normally, imapd commits suicide within 30 minutes of the Pine end vanishing (assuming an explicit logout wasn't done). > A more worrying sympton is that I also had mail completely disappear. I > logged on to see the elm "frm" command reporting I had one message - I > was doing something else (not running pine) and then ran "frm" again - > this time to see no messages! Again I discovered there was an impad > process running from a previous session. I seem to recall that there had > been problems with Sun sendmail and imapd earlier but I thought these had > been fixed. Are you sure the message really disappeared, as opposed to merely no longer being marked as new? Are you sure that that ``imapd process running from a previous session'' isn't talking to a living Pine that is checkpointing? Did you check your /usr/spool/mqueue/syslog file (or wherever sendmail logs are kept) to see if there are any unaccounted-for messages that were delivered to. Please check out these possibilities. > By the way, I also pulled the latest imap.tar.Z - the compilation for the > sun build fails with: > > "mtx.c", line 706: SEEK_SET undefined Please change the SEEK_SET reference in mtx.c to L_SET. This will be fixed in the next version of imap.tar.Z. Sorry for the inconvenience. -- Mark -- From owner-pine-info@cac.washington.edu Tue Oct 26 14:26:01 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04888; Tue, 26 Oct 93 14:26:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29861; Tue, 26 Oct 93 14:08:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29853; Tue, 26 Oct 93 14:08:28 -0700 Received: by digi.syd.deg.csiro.au id AA06197 (5.65c/IDA-1.4.4 for pine mailing list ); Wed, 27 Oct 1993 07:11:38 +1000 Date: Wed, 27 Oct 1993 07:06:44 +1000 (EST) From: Jack Churchill Subject: pine/pico file inclusion To: pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A nice feature found in some other editors is the ability to use wild cards when specifying the filename at the ^R (read file) option. A screen similar to the ^T (to files) option should then appear for selection unless there's only one file that matches anyway. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Tue Oct 26 16:52:17 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08808; Tue, 26 Oct 93 16:52:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02931; Tue, 26 Oct 93 16:30:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02925; Tue, 26 Oct 93 16:30:47 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA11730 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Tue, 26 Oct 93 18:30:46 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA21725; Tue, 26 Oct 93 18:30:45 CDT Date: Tue, 26 Oct 1993 18:30:05 -0500 (CDT) From: Matt Simmons Subject: Re: How to disable the addition of '@hostname' to addresses? To: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 26 Oct 1993, Mark Crispin wrote: > On Tue, 26 Oct 1993 12:19:37 -0500 (CDT), Matt Simmons wrote: > > Could you compile a set with debugging off? Pine takes 8 megs to compile > > and I have to do it in /tmp a 4 in the morning so my sysadmins don't > > scream at me for filling up tmp.. > Suggest it to pine@cac.washington.edu; I don't make that decision... ;-) We're talking about the precompiled binaries on ftp.cac.washington.edu here... Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Tue Oct 26 19:12:19 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10963; Tue, 26 Oct 93 19:12:19 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17783; Tue, 26 Oct 93 18:51:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stonewall.sph.umich.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17777; Tue, 26 Oct 93 18:51:11 -0700 Received: from appomattox.sph.umich.edu by sph.umich.edu (5.67/2.2) id AA20883; Tue, 26 Oct 93 21:49:42 -0400 Date: Tue, 26 Oct 1993 21:43:01 -0400 (EDT) From: Jim Kenyon Subject: Need for rshd access from PINE To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It appears that PINE tries to contact the rshd on the imapd host even if the "passwordless" access feature of PINE is not being used. I noticed this when I commented out rshd in inetd.conf on my mailhub (a bit of firewalling) -- connections to the server took about a minute to complete (from the "Opening INBOX" message to the userid prompt) with rshd disabled. Connections establish in about 2 seconds with rshd enabled. Why is PINE (if it is) trying to talk to rshd even when not doing rsh authentication? -jk Jim Kenyon -- jkenyon@umich.edu Systems Research Programmer II, School of Public Health From owner-pine-info@cac.washington.edu Tue Oct 26 19:32:25 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11194; Tue, 26 Oct 93 19:32:25 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17876; Tue, 26 Oct 93 19:18:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17870; Tue, 26 Oct 93 19:18:03 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03851; Tue, 26 Oct 93 19:18:00 -0700 Date: Tue, 26 Oct 1993 19:13:53 -0700 (PDT) From: Mark Crispin Subject: Re: Need for rshd access from PINE To: Jim Kenyon Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 26 Oct 1993, Jim Kenyon wrote: > It appears that PINE tries to contact the rshd on the imapd host even if > the "passwordless" access feature of PINE is not being used. I noticed > this when I commented out rshd in inetd.conf on my mailhub (a bit of > firewalling) -- connections to the server took about a minute to complete > (from the "Opening INBOX" message to the userid prompt) with rshd > disabled. Connections establish in about 2 seconds with rshd enabled. > Why is PINE (if it is) trying to talk to rshd even when not doing rsh > authentication? There is no way for Pine to know whether or not it is using rsh based authentication unless it tries it. It sounds to me that your rsh client is timing out rather than getting a connection refused error. From owner-pine-info@cac.washington.edu Wed Oct 27 10:22:44 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA26447; Wed, 27 Oct 93 10:22:44 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21753; Wed, 27 Oct 93 09:56:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from emoryu1.cc.emory.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21749; Wed, 27 Oct 93 09:56:13 -0700 Received: by emoryu1.cc.emory.edu (5.65/Emory_cc.3.4.12) via MAILPROG id AA00495 ; Wed, 27 Oct 93 12:56:08 -0400 Return-Path: usmf@unix.cc.emory.edu Date: Wed, 27 Oct 1993 12:55:20 -0400 (EDT) From: Mahbuba Ferdousi Subject: Ascii printing in Pine To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! I have a question on Pine. we are trying to print from a Mac using Telnet 2.5 and an Imagewriter attached to it directly to the Phone line. I used the option in Pine "attached to ansii" and tried to print, it tells me it is printing, but nothing comes out. Print selection works. Do you have any suggestions for me?? Are other people able to print?? Also do you know if Pine for RS6000 is here? Thanks a lot in advance, Mahbuba From owner-pine-info@cac.washington.edu Wed Oct 27 11:43:40 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28900; Wed, 27 Oct 93 11:43:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16431; Wed, 27 Oct 93 11:24:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nethost.multnomah.lib.or.us by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16425; Wed, 27 Oct 93 11:24:50 -0700 Received: by nethost.multnomah.lib.or.us (4.1/1.34) id AA22925; Wed, 27 Oct 93 11:24:32 PDT Date: Wed, 27 Oct 1993 11:22:45 -0700 (PDT) From: Brian Williams Subject: Re: Ascii printing in Pine To: Mahbuba Ferdousi Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I dial in occasionally from my Mac at home using Microphone and print to a laserwriter with no probs. I think it is your software. Brian Williams Automation Manager Multnomah County Library 801 SW 10th Portland, OR 97205 (503)248-5227 (v) (503)248-5226 (f) brianw@nethost.multnomah.lib.or.us On Wed, 27 Oct 1993, Mahbuba Ferdousi wrote: > > Hi! > > I have a question on Pine. we are trying to print from a Mac using Telnet > 2.5 and an Imagewriter attached to it directly to the Phone line. I used > the option in Pine "attached to ansii" and tried to print, it tells me it > is printing, but nothing comes out. Print selection works. Do you have any > suggestions for me?? Are other people able to print?? > From owner-pine-info@cac.washington.edu Wed Oct 27 11:47:56 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29061; Wed, 27 Oct 93 11:47:56 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16624; Wed, 27 Oct 93 11:31:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from saturn.hrz.tu-chemnitz.de by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16598; Wed, 27 Oct 93 11:30:32 -0700 Received: from hrz.tu-chemnitz.de by saturn.hrz.tu-chemnitz.de via Local Delivery channel id <12132-0@saturn.hrz.tu-chemnitz.de>; Wed, 27 Oct 1993 19:29:12 +0100 Date: Wed, 27 Oct 1993 19:21:51 +0100 (MET) From: Frank Richter Subject: No default command in Message View Screen To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I just upgraded from pine 3.07 to 3.87 (for our campus wide File Server for Sun4, Solaris, Ultrix, RS6000, HP 9000 (700+800) and NeXt). And I'm happy about the new features, our users as well, hopefully :-) One little thing I detected which disturbs me: [No default command in Message View Screen] -- when I press RETURN while viewing a message. Could this be changed? Regards, Frank -------------------------------------------------------------------------- Frank Richter Computing Services, Technical University Chemnitz, Germany Email: Frank.Richter@hrz.tu-chemnitz.de (MIME welcome) | see X.500 entry Tel: +49 (0)371 668-361 <---{{ NEW !! From owner-pine-info@cac.washington.edu Wed Oct 27 11:52:49 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29158; Wed, 27 Oct 93 11:52:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22480; Wed, 27 Oct 93 11:34:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22473; Wed, 27 Oct 93 11:34:50 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA05697; Wed, 27 Oct 1993 13:38:45 -0500 Date: Wed, 27 Oct 1993 13:32:27 -0500 (CDT) From: "Robert A. Hayden" Subject: Pine and PGP To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I posted a discussion of this a while back, but I believe it got buried under the flood of mail accompanying the 3.85 relase of the Pine package. I'm wondering about possibilities of encorporating abilities into Pine that will allow you to utilize the security features of PGP. Most specifically would be the ability to add a digital signature to your outgoing mail (pgp -s filename), and perhaps later the ability to check the 'To:' field and match those names to your public keyring. In theory, I don't think it would be that difficult to do. Simple that before the file is sent on its way, the headers should be stripped and then the signature would be added, then reattached to the headers and sent out. It's an operation that could take place invisibly to the user. Right now, the only way to sign a message is to create it outside of Pine, sign it, and then read it in, which is really cumbersome for spur of the moment creation of messages. I appreciate your time. ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> Veteran of the Bermuda Triangle \/ Finger for PGP 2.3a Public Key <=> Expeditionary Force -- 1993-1951 -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Wed Oct 27 12:15:25 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00120; Wed, 27 Oct 93 12:15:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17344; Wed, 27 Oct 93 12:00:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ua.d.umn.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17338; Wed, 27 Oct 93 12:00:43 -0700 Received: from kbaa65-85.d.umn.edu by ua.d.umn.edu with SMTP id AA18271 (5.65c/IDA-1.4.4 for ); Wed, 27 Oct 1993 14:00:39 -0500 Date: Wed, 27 Oct 93 14:01:57 -0600 From: Joel Ness To: pine-info@cac.washington.edu Subject: Re: Ascii printing in Pine Message-Id: In-Reply-To: Your message of Wed, 27 Oct 1993 11:22:45 -0700 (PDT) Content-Type: TEXT/plain; charset=US-ASCII Local printing requires that your communication program be able to handle the excape sequences that Pine sends and then route the text to a printer. The Pine docs say that this is possible on the Mac with some comm programs (I think they mention VersaTerm, and it looks like Microphone works, too). I know that Telnet won't work. Telnet does allow you to select text on the screen and then print the selection. Unfortunately, Pine does it's scrolling in a way that doesn't let Telnet capture text that has "scrolled past". Thus you can't scroll back through your Telnet window and select more than one screenful of your message (for printing or copying). This is one of the few advantages of elm and the reason some of our users haven't switched to Pine. I don't think this lack of scrollback capture is a Pine "bug", I think it's just related to how tightly integrated the interface is. > I dial in occasionally from my Mac at home using > Microphone and print to a laserwriter with no probs. I > think it is your software. > > Brian Williams Automation Manager > Multnomah County Library 801 SW 10th Portland, OR > 97205 > (503)248-5227 (v) (503)248-5226 (f) > brianw@nethost.multnomah.lib.or.us > > > > On Wed, 27 Oct 1993, Mahbuba Ferdousi wrote: > > > > > Hi! > > > > I have a question on Pine. we are trying to print from > a Mac using Telnet > > 2.5 and an Imagewriter attached to it directly to the > Phone line. I used > > the option in Pine "attached to ansii" and tried to > print, it tells me it > > is printing, but nothing comes out. Print selection > works. Do you have any > > suggestions for me?? Are other people able to print?? > > _________________________ Joel Ness UMD Information Services jness@ua.d.umn.edu (218) 726-8841 From owner-pine-info@cac.washington.edu Wed Oct 27 14:10:17 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02983; Wed, 27 Oct 93 14:10:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19671; Wed, 27 Oct 93 13:55:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tiberius.safb.af.mil by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19665; Wed, 27 Oct 93 13:55:47 -0700 Received: by tiberius.safb.af.mil (4.1/SMI-4.1) id AA23892; Wed, 27 Oct 93 15:56:38 CDT Date: Wed, 27 Oct 1993 15:35:19 -0500 (CDT) From: "John Daum... 618-256-6835" Subject: HELP Restoring Email into the spool or a folder To: Pine Help List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there an easy way to get PINE to recognize these Email messages??? I have a user who accidently invoked an older mail package that stored each of 80 some odd messages as individual files with a different order to each of the "From:" "To:" etc... for example: Return-Path: Received: id AA12548; Mon, 25 Oct 93 10:27:44 -0400 Message-Id: X-Sender: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: To: From: Subject: Status: O X-Status: Return-Path: Date: From: To: Subject: Return-Path: mckenney@smiley.mitre.org To: Subject: Reply-To: Date: From: Thanks.... John E. Daum 618-256-6835 or 618-632-2456 via ms bell OR daumj@tiberius.safb.af.mil via the Internet From owner-pine-info@cac.washington.edu Wed Oct 27 14:48:34 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04082; Wed, 27 Oct 93 14:48:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20019; Wed, 27 Oct 93 14:12:56 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ua.d.umn.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20001; Wed, 27 Oct 93 14:12:52 -0700 Received: from jness.d.umn.edu by ua.d.umn.edu with SMTP id AA03046 (5.65c/IDA-1.4.4 for ); Wed, 27 Oct 1993 16:12:48 -0500 Date: Wed, 27 Oct 93 16:12:47 -0600 From: Joel Ness To: "Andrew Sweger" Subject: Re: Ascii printing in Pine Cc: pine-info@cac.washington.edu Message-Id: In-Reply-To: Your message <9310271931.AA05864@hanna.cac.washington.edu> of 27 Oct 1993 12:30:39 -0800 Content-Type: TEXT/plain; charset=US-ASCII > NCSA Telnet v2.5x for the Macintosh DOES understand the > ASCII printing escape sequences. When you select Print > ('Y') from pine, you should get the normal print dialog > box. If you Cancel the print dialog, you should get the > option to spool the job for later printing. > > / Andrew B. Sweger > absweger@u.washington.edu // Manager, Computer Support > Group > \\ Department of Family Medicine, HQ-30 (206) > 543-2461 > // UNIVERSITY OF WASHINGTON > / Seattle, WA 98195 (206) > 685-0610 (FAX) Hmm, that would be great. I've got the latest NCSA Telnet and it still doesn't seem to work (LaserWriter driver 8.0 and a LaserWriter). The printer config screen in Pine says the following: 1. Printer attached to IBM PC or compatible, MacIntosh This may not work with all attached printers, and will depend on the terminal emulation/communications software in use. It is known to work with Versaterm Pro on Macs, and WRQ Reflections on PC's and with the latest UW version of NCSA telnet for either, and probably Kermit too. Command: attached-to-ansi Does UW have some further modified versions of Telnet for the Mac? I know that Telnet 2.6 is in the works from NCSA, but I don't believe it's released yet. _________________________ Joel Ness UMD Information Services jness@ua.d.umn.edu (218) 726-8841 From owner-pine-info@cac.washington.edu Wed Oct 27 15:37:00 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA05926; Wed, 27 Oct 93 15:37:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23924; Wed, 27 Oct 93 15:07:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from jade.saintmarys.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23918; Wed, 27 Oct 93 15:07:06 -0700 Received: by jade.saintmarys.edu (1.37.109.4/16.2) id AA22824; Wed, 27 Oct 93 17:09:26 -0500 Date: Wed, 27 Oct 1993 16:37:04 -0500 (EST) From: Dan Mandell Reply-To: Dan Mandell Subject: Suggestion for "Export" To: "pine-info@cac.washington.edu" Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII When users export to a file, if the file exists, they are asked about appending. If the user does not wish to append, most programs will request a new name be supplied. We have had users who when they indicated they did not want to append thought that the original file was overwritten (replaced) by the new message. In fact nothing has happened. If they had the option to supply a name instead of simply returning them to their document, they could then supply a different name. -- ===================================== Dan Mandell, Computer Services, Saint Mary's College Internet: dmandell@saintmarys.edu "Always promise a little less than you can deliver" : Montaigne From owner-pine-info@cac.washington.edu Wed Oct 27 16:00:51 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06681; Wed, 27 Oct 93 16:00:51 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17999; Wed, 27 Oct 93 12:31:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hanna.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17993; Wed, 27 Oct 93 12:31:22 -0700 Received: from family.fammed.washington.edu by hanna.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05864; Wed, 27 Oct 93 12:31:13 -0700 Message-Id: <9310271931.AA05864@hanna.cac.washington.edu> Date: 27 Oct 1993 12:30:39 -0800 From: "Andrew Sweger" Subject: RE: Ascii printing in Pine Return-Receipt-To: "Andrew Sweger" To: "Joel Ness" Cc: "pine-info" NCSA Telnet v2.5x for the Macintosh DOES understand the ASCII printing escape sequences. When you select Print ('Y') from pine, you should get the normal print dialog box. If you Cancel the print dialog, you should get the option to spool the job for later printing. / Andrew B. Sweger absweger@u.washington.edu // Manager, Computer Support Group \\ Department of Family Medicine, HQ-30 (206) 543-2461 // UNIVERSITY OF WASHINGTON / Seattle, WA 98195 (206) 685-0610 (FAX) _______________________________________________________________________________ To: pine-info@cac.washington.edu From: Joel Ness on Wed, Oct 27, 1993 12:20 PM Subject: Re: Ascii printing in Pine Local printing requires that your communication program be able to handle the excape sequences that Pine sends and then route the text to a printer. The Pine docs say that this is possible on the Mac with some comm programs (I think they mention VersaTerm, and it looks like Microphone works, too). I know that Telnet won't work. Telnet does allow you to select text on the screen and then print the selection. Unfortunately, Pine does it's scrolling in a way that doesn't let Telnet capture text that has "scrolled past". Thus you can't scroll back through your Telnet window and select more than one screenful of your message (for printing or copying). This is one of the few advantages of elm and the reason some of our users haven't switched to Pine. I don't think this lack of scrollback capture is a Pine "bug", I think it's just related to how tightly integrated the interface is. > I dial in occasionally from my Mac at home using > Microphone and print to a laserwriter with no probs. I > think it is your software. > > Brian Williams Automation Manager > Multnomah County Library 801 SW 10th Portland, OR > 97205 > (503)248-5227 (v) (503)248-5226 (f) > brianw@nethost.multnomah.lib.or.us > > > > On Wed, 27 Oct 1993, Mahbuba Ferdousi wrote: > > > > > Hi! > > > > I have a question on Pine. we are trying to print from > a Mac using Telnet > > 2.5 and an Imagewriter attached to it directly to the > Phone line. I used > > the option in Pine "attached to ansii" and tried to > print, it tells me it > > is printing, but nothing comes out. Print selection > works. Do you have any > > suggestions for me?? Are other people able to print?? > > _________________________ Joel Ness UMD Information Services jness@ua.d.umn.edu (218) 726-8841 From owner-pine-info@cac.washington.edu Wed Oct 27 17:47:24 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10071; Wed, 27 Oct 93 17:47:24 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24849; Wed, 27 Oct 93 17:35:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cs.uwp.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24843; Wed, 27 Oct 93 17:35:44 -0700 Received: by cs.uwp.edu id AA14461 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 27 Oct 1993 19:35:40 -0500 Date: Wed, 27 Oct 1993 19:34:22 -0500 (CDT) From: Don Piele Subject: remove name To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please remove my name from the pine list. Thank you. Don Piele piele@cs.uwp.edu From owner-pine-info@cac.washington.edu Wed Oct 27 22:31:22 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13638; Wed, 27 Oct 93 22:31:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27322; Wed, 27 Oct 93 22:19:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27316; Wed, 27 Oct 93 22:19:00 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10436; Wed, 27 Oct 93 22:18:53 -0700 Date: Wed, 27 Oct 1993 22:15:23 -0700 (PDT) From: Terry Gray Subject: Re: No default command in Message View Screen To: Frank Richter Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Frank, We held off having a default action for Message Text until we had a chance to come up with a spiffier "attachment selection" interface. There *will* be a default action as soon as this is available. -teg On Wed, 27 Oct 1993, Frank Richter wrote: > > I just upgraded from pine 3.07 to 3.87 (for our campus wide File > Server for Sun4, Solaris, Ultrix, RS6000, HP 9000 (700+800) and NeXt). > > And I'm happy about the new features, our users as well, hopefully :-) > > One little thing I detected which disturbs me: > > [No default command in Message View Screen] -- when I press RETURN while > viewing a message. > > Could this be changed? > > Regards, > Frank > -------------------------------------------------------------------------- > Frank Richter Computing Services, Technical University Chemnitz, Germany > Email: Frank.Richter@hrz.tu-chemnitz.de (MIME welcome) | see X.500 entry > Tel: +49 (0)371 668-361 <---{{ NEW !! > > > From owner-pine-info@cac.washington.edu Thu Oct 28 07:29:38 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20668; Thu, 28 Oct 93 07:29:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01896; Thu, 28 Oct 93 07:10:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dukemc.mc.duke.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01890; Thu, 28 Oct 93 07:10:54 -0700 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H4N4T29BQO0009F0@mc.duke.edu>; Thu, 28 Oct 1993 10:15:05 EST Date: Thu, 28 Oct 1993 10:12:23 -0500 (EST) From: James Dryfoos- Postmaster Subject: HdrMode oddness? To: pine-info@cac.washington.edu Message-Id: <01H4N4XH5X3O0009F0@mc.duke.edu> Organization: Duke University Medical Center, Durham NC, USA Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I have noticed something that I think is backwards? When displaying email with the HdrMode off (i.e. the short form) I notice that my id in the to: field contains the complete domain spec: To: DRYFO001@mc.duke.edu, jdd@mcismvs.mc.duke.edu However, if I press H and turn on full headers, it is shortened: To: DRYFO001, jdd@mcismvs.mc.duke.edu This is no big deal, just seems opposite from what I would expect. -- Jim P.s. Am using Pine 3.85 on Ultrix. (This message was not sent from there). From owner-pine-info@cac.washington.edu Thu Oct 28 10:24:44 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25034; Thu, 28 Oct 93 10:24:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04474; Thu, 28 Oct 93 09:39:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04468; Thu, 28 Oct 93 09:39:03 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10624; Thu, 28 Oct 93 09:38:54 -0700 Date: Thu, 28 Oct 1993 09:35:07 -0700 (PDT) From: David L Miller Subject: Re: HdrMode oddness? To: James Dryfoos- Postmaster Cc: pine-info@cac.washington.edu In-Reply-To: <01H4N4XH5X3O0009F0@mc.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Full Headers mode displays the raw message as it was recieved. With Full Headers off, Pine parses then reconstructs the headers into a fully qualified canonical form. Full Headers mode might actually be better described as Raw Message mode... |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 28 Oct 1993, James Dryfoos- Postmaster wrote: > I have noticed something that I think is backwards? > When displaying email with the HdrMode off (i.e. the short form) I notice that > my id in the to: field contains the complete domain spec: > > To: DRYFO001@mc.duke.edu, jdd@mcismvs.mc.duke.edu > > However, if I press H and turn on full headers, it is shortened: > > To: DRYFO001, jdd@mcismvs.mc.duke.edu > > This is no big deal, just seems opposite from what I would expect. > > -- Jim > > P.s. Am using Pine 3.85 on Ultrix. (This message was not sent from there). From owner-pine-info@cac.washington.edu Thu Oct 28 10:28:33 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25197; Thu, 28 Oct 93 10:28:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29329; Thu, 28 Oct 93 10:04:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ultrix.ramapo.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29323; Thu, 28 Oct 93 10:04:40 -0700 Received: by ultrix (5.57/Ultrix3.0-C) id AA03296; Thu, 28 Oct 93 13:06:59 -0400 Date: Thu, 28 Oct 1993 12:58:12 -0400 (EDT) From: "Jackie \"Oh!\" Owen" Subject: Wrong return address To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Attached is a message one of our faculty received. She (username: sscher) was trying to get some information from a listserv and incorrectly entered the To: address. Needless to say, the message was returned to her, but if you look at the From: line of the unsent message, it says that this message was sent by pchang, not ssher. I tried to replicate the problem with no luck. There is a user pchang on this system, but he has never logged in. No one else had this problem. The syslog entries for this and a few more similiar messages look normal. The password entries for each look okay also. We're running ULTRIX 4.3 and Pine 3.87. Any ideas, suggestions? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jackie Loucks Owen Network Administrator jowen@ultrix.ramapo.edu Ramapo College of NJ Mahwah, NJ "Time flies like an arrow. Fruit flies like a banana." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ---------- Forwarded message ---------- >From MAILER-DAEMON Mon Oct 25 17:36:11 1993 Date: Mon, 25 Oct 93 17:35:11 -0400 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: sscher Status: RO X-Status: ----- Transcript of session follows ----- 550 acdvm1.uottawa.ca.tcp... 550 Host unknown 550 listserv@acdvm1.uottawa.ca... Host unknown ----- Unsent message follows ----- Received: by ultrix (5.57/Ultrix3.0-C) id AA17521; Mon, 25 Oct 93 17:35:11 -0400 Date: Mon, 25 Oct 1993 17:33:47 -0400 (EDT) From: Pat Chang Subject: social work discussion group To: listserv@acdvm1.uottawa.ca Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII get socwork directory >From MAILER-DAEMON Mon Oct 25 17:39:24 1993 Date: Mon, 25 Oct 93 17:39:17 -0400 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: sscher Status: RO X-Status: ----- Transcript of session follows ----- 550 acdvm1.vottawa.ca.tcp... 550 Host unknown 550 listserv@acdvm1.vottawa.ca... Host unknown ----- Unsent message follows ----- Received: by ultrix (5.57/Ultrix3.0-C) id AA17723; Mon, 25 Oct 93 17:39:17 -0400 Date: Mon, 25 Oct 1993 17:38:05 -0400 (EDT) From: Pat Chang Subject: To: listserv@acdvm1.vottawa.ca Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII get socwork directry >From MAILER-DAEMON Mon Oct 25 17:43:28 1993 Date: Mon, 25 Oct 93 17:43:26 -0400 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: sscher Status: RO X-Status: ----- Transcript of session follows ----- 550 ab.umd.edu.tcp... 550 Host unknown 550 listserv@ab.umd.edu... Host unknown ----- Unsent message follows ----- Received: by ultrix (5.57/Ultrix3.0-C) id AA17868; Mon, 25 Oct 93 17:43:26 -0400 Date: Mon, 25 Oct 1993 17:42:35 -0400 (EDT) From: Pat Chang Subject: To: listserv@ab.umd.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII subscribe socwork From owner-pine-info@cac.washington.edu Thu Oct 28 11:03:34 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA26244; Thu, 28 Oct 93 11:03:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29707; Thu, 28 Oct 93 10:46:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ramsey.cs.laurentian.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29701; Thu, 28 Oct 93 10:46:28 -0700 Received: by ramsey.cs.laurentian.ca (5.65/DEC-Ultrix/4.3) id AA27551; Thu, 28 Oct 1993 13:45:42 -0400 Received: by thunderbird.auc.laurentian.ca (5.4.2/200.1.1.4) id AA12138; Thu, 28 Oct 1993 13:46:26 -0400 Date: Thu, 28 Oct 1993 13:44:44 -0400 (EDT) From: James Trainor Subject: name To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please remove my name from the mailing list. trainor@thunderbird.auc.laurentian.ca -jEt- From owner-pine-info@cac.washington.edu Thu Oct 28 11:47:32 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA27818; Thu, 28 Oct 93 11:47:32 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00142; Thu, 28 Oct 93 11:34:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00136; Thu, 28 Oct 93 11:34:08 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA06327; Thu, 28 Oct 93 11:33:59 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA05632; Thu, 28 Oct 93 11:33:52 -0700 Date: Thu, 28 Oct 1993 11:32:12 -0700 (PDT) From: Mark Crispin Subject: re: Wrong return address To: "Jackie \"Oh!\" Owen" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Is there any possibility that pchang and ssher have the same user number? From owner-pine-info@cac.washington.edu Thu Oct 28 11:58:34 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28166; Thu, 28 Oct 93 11:58:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00302; Thu, 28 Oct 93 11:48:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ultrix.ramapo.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00296; Thu, 28 Oct 93 11:48:27 -0700 Received: by ultrix (5.57/Ultrix3.0-C) id AA07700; Thu, 28 Oct 93 14:50:44 -0400 Date: Thu, 28 Oct 1993 14:49:30 -0400 (EDT) From: "Jackie \"Oh!\" Owen" Subject: re: Wrong return address To: Mark Crispin Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I checked that out first thing. They both have very different user IDs. ssher's account was created last year and pchang's acct was created on October 22. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jackie Loucks Owen Network Administrator jowen@ultrix.ramapo.edu Ramapo College of NJ Mahwah, NJ "Time flies like an arrow. Fruit flies like a banana." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Thu, 28 Oct 1993, Mark Crispin wrote: > Is there any possibility that pchang and ssher have the same user number? > > From owner-pine-info@cac.washington.edu Thu Oct 28 13:27:18 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01409; Thu, 28 Oct 93 13:27:18 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00897; Thu, 28 Oct 93 13:11:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from elwha.evergreen.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00891; Thu, 28 Oct 93 13:11:55 -0700 Received: by elwha.evergreen.edu (5.57/Ultrix3.0-C) id AA14795; Thu, 28 Oct 93 13:13:28 -0700 Date: Thu, 28 Oct 1993 13:08:00 -0700 (PDT) From: Joe Pollock Subject: Re: Wrong return address To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We've seen exactly the same thing here, with Pine 3.07 and Ultrix 4.2 (A?). In this case, the messages with the strange headers appeared in the user's sent-mail folder, with the name of a user of an account I had created a few hours earlier. The user has no idea what she did, and the debug files didn't look out of line. On Thu, 28 Oct 1993, Jackie "Oh!" Owen wrote: > Attached is a message one of our faculty received. She (username: > sscher) was trying to get some information from a listserv and > incorrectly entered the To: address. Needless to say, the message was > returned to her, but if you look at the From: line of the unsent > message, it says that this message was sent by pchang, not ssher. I > tried to replicate the problem with no luck. There is a user pchang on > this system, but he has never logged in. No one else had this problem. > The syslog entries for this and a few more similiar messages look normal. > The password entries for each look okay also. We're running ULTRIX 4.3 > and Pine 3.87. > From owner-pine-info@cac.washington.edu Thu Oct 28 14:12:43 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02787; Thu, 28 Oct 93 14:12:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10143; Thu, 28 Oct 93 13:54:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from helix.nih.gov by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10137; Thu, 28 Oct 93 13:54:44 -0700 Received: by helix.nih.gov (5.64/1.35(helix-1.0)) id AA24171; Thu, 28 Oct 93 16:54:44 -0400 Date: Thu, 28 Oct 1993 16:39:48 -0400 (EDT) From: Rick Troxel Subject: Rewrites of UNIX From line To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I recently discovered that Pine's save and extract operations rewrite the "Unix from line" of a message with my own address and the time of the operation. Can this possibly be a feature? This is with V3.85 on a Convex and V3.87 on an SGI. Thanks, Rick Troxel rick@helix.nih.gov 301/496-4823 /////////////////////////////////////////////////////////////////////////// All effort and exertion put forth by man from the fullness of his heart is worship, if it is prompted by the highest motives and the will to do service to humanity. --Abdu'l-Baha From owner-pine-info@cac.washington.edu Thu Oct 28 16:38:23 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07428; Thu, 28 Oct 93 16:38:23 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02032; Thu, 28 Oct 93 16:23:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from log.css.itd.umich.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02026; Thu, 28 Oct 93 16:23:18 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA10484; Thu, 28 Oct 93 19:23:15 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA03708; Thu, 28 Oct 93 19:23:14 -0400 Date: Thu, 28 Oct 1993 19:07:21 -0400 (EDT) From: Alex Tang Subject: 3.87/NetBSD/mail vaporizing. To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all. I've ported (sorta) 3.87 to NetBSD-0.8. It was fairly easy....i just changed a couple of things. But...the problem is that it doesn't work. :( It compiles and runs fine, but when I run it, the mail i send just vaporizes. At least as far as I can tell, i send the mail, and it never gets anywhere. (I can't even send to users on the same machine). I can see the message briefly pass through /usr/spool/mqueue, but then nothing. I think that The .pinedebug files are indicating that all went well. No errors. sendmail works ok, i can use ucb mail, and i had an old version of pine running (3.05), but it got deleted a while back. I can't figure out why it's doing this. I'm including my .pinedebug file below. Thanx...alex... Alex Tang --- ALTITUDE@UMICH.EDU...USERW00Y@UMICHUM.BITNET -----------+ U of M, SNRE: Student and Computer Consultant II, PGP on req.| ITD/CSS Consultant, Short asian with long hair :) Debug output of the Pine program (at debug level 6). Version 3.87 Thu Oct 28 19:22:18 1993 reading_pinerc "/usr/local/lib/pine.conf" Read 1582 characters pinerc : /usr/local/l : printer : "lpr" reading_pinerc "/usr/u/altitude/.pinerc" Read 6060 characters pinerc : /usr/u/altit : personal-name : "Alex Tang" pinerc : /usr/u/altit : printer : "attached-to-ansi" pinerc : /usr/u/altit : personal-print-comma : "enscript -2Gr" pinerc : /usr/u/altit : last-time-prune-ques : "93.10" pinerc : /usr/u/altit : user-domain : "umich.edu" pinerc : /usr/u/altit : use-only-domain-name : "yes" pinerc : /usr/u/altit : editor : "vi" pinerc : /usr/u/altit : incoming-folders : "Recycle.inbox {recycle.snre.umich.edu}inbox" pinerc : /usr/u/altit : folder-collections : "mail/[]" pinerc : /usr/u/altit : news-collections : "news *{news.itd.umich.edu/nntp}[]" pinerc : /usr/u/altit : feature-list : "old-growth" pinerc : /usr/u/altit : initial-keystroke-li : "i" pinerc : /usr/u/altit : last-version-used : "3.87" personal-name : Alex Tang user-id : user-domain : umich.edu umich.edu smtp-server : inbox-path : inbox inbox incoming-folders : Recycle.inbox {rec Recycle.inbox {rec folder-collection : mail/[] mail/[] news-collections : news *{news.itd.um news *{news.itd.um default-fcc : sent-mail sent-mail mail-directory : mail mail read-message-fold : signature-file : .signature .signature address-book : .addressbook .addressbook feature-list : old-growth old-growth initial-keystroke : i saved-msg-name-ru : default-folder default-folder sort-key : arrival reverse character-set : editor : vi vi image-viewer : use-only-domain-n : yes no yes printer : attached-to-ansi lpr attached-to-ansi personal-print-co : enscript -2Gr enscript -2Gr standard-printer : lpr lpr last-time-prune-q : 93.10 93.10 last-version-used : 3.87 3.87 bugs-nickname : bugs-fullname : bugs-address : elm-style-save : no no header-in-reply : no no feature-level : sapling sapling old-style-reply : no no compose-mime : show-all-characte : save-by-sender : no no Userid: altitude Fullname: "Alex Tang" User domain name being used "umich.edu" Local Domain name being used "snre.umich.edu" Host name being used "recycle.snre.umich.edu" Mail Domain name being used "umich.edu" new win size -----<24 80>------ Terminal type: vt100 Context [] type: LOCAL Context mail/[] type: LOCAL Context {recycle.snre.umich.edu}mail/[] type: REMOTE Context *{news.itd.umich.edu/nntp}[] type: REMOTE BBOARD OLDTECH About to open folder "INBOX" inbox: "INBOX" broach_folder: nickname for inbox is INBOX === mm_exists(2,/var/mail/altitude) called === Opened folder "/var/mail/altitude" with 2 messages Sorting by arrival/reverse First unseen returning 1 ==== expire_mail called ==== ---- MAIL INDEX ---- ***** new_mail pinging ***** New mail checked ******** new mail returning -1 ******** - process_cmd((99)c) - ---- COMPOSE SCREEN (not in pico yet) ---- === send called === Address book opened with 26 items === init_addr_disp called === new win size -----<24 80>------ cannonized To "altitude@recycle.snre.umich.edu" ====== context_mailbox: (sent-mail) === call_mailer === === expand_foldername called (/var/tmp//pinesend000765) === returning "/var/tmp//pinesend000765" Send command "(( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /var/tmp//pinesend000765) & )< /var/tmp//pinesend000765" ***** MAIL SENT ****** To: altitude@recycle.snre.umich.eduSubject: Testing, d6 Message ID: ---- MAIL INDEX ---- - process_cmd((113)q) - MAIL_CMD: quit ---- QUIT SCREEN ---- expunge and close mail stream "/var/mail/altitude" about to end_tty_driver From owner-pine-info@cac.washington.edu Thu Oct 28 23:25:13 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13821; Thu, 28 Oct 93 23:25:13 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17891; Thu, 28 Oct 93 23:14:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17885; Thu, 28 Oct 93 23:14:46 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04578; Thu, 28 Oct 93 23:14:35 -0700 Date: Thu, 28 Oct 1993 23:09:33 -0700 (PDT) From: Steve Hubert Subject: Re: 3.87/NetBSD/mail vaporizing. To: Alex Tang Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You could try some debugging by altering the source so that it stops after it creates the /tmp/pinesend123456 file and returns NULL. Then you could look at that file (the input to sendmail) to see if it looks right and try running it through sendmail with sendmail verboseness and debugging turned on. If your syslog is working you might be able to find some mention of the sendmail problem, there, too. Alternatively, you could try setting the smtp-server to some other SMTP host and see if avoiding the local sendmail fixes it for you. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Thu, 28 Oct 1993, Alex Tang wrote: > Hi all. I've ported (sorta) 3.87 to NetBSD-0.8. It was fairly easy....i > just changed a couple of things. But...the problem is that it doesn't > work. :( > > It compiles and runs fine, but when I run it, the mail i send just > vaporizes. At least as far as I can tell, i send the mail, and it never > gets anywhere. (I can't even send to users on the same machine). I can > see the message briefly pass through /usr/spool/mqueue, but then nothing. > > I think that The .pinedebug files are indicating that all went well. No > errors. > > sendmail works ok, i can use ucb mail, and i had an old version of pine > running (3.05), but it got deleted a while back. > I can't figure out why it's doing this. I'm including my .pinedebug file > below. > > Thanx...alex... > > Alex Tang --- ALTITUDE@UMICH.EDU...USERW00Y@UMICHUM.BITNET > -----------+ U of M, SNRE: Student and Computer Consultant II, > PGP on req.| ITD/CSS Consultant, Short asian with long hair :) > > > Debug output of the Pine program (at debug level 6). Version 3.87 > Thu Oct 28 19:22:18 1993 > > reading_pinerc "/usr/local/lib/pine.conf" > === call_mailer === > === expand_foldername called (/var/tmp//pinesend000765) === > returning "/var/tmp//pinesend000765" > Send command "(( /usr/lib/sendmail -oi -oem -t ; /bin/rm -f /var/tmp//pinesend000765) & )< /var/tmp//pinesend000765" From owner-pine-info@cac.washington.edu Fri Oct 29 05:49:16 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA19185; Fri, 29 Oct 93 05:49:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21008; Fri, 29 Oct 93 05:35:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21002; Fri, 29 Oct 93 05:35:18 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <13143-0@susssys1.reading.ac.uk>; Fri, 29 Oct 1993 12:35:11 +0000 Date: Fri, 29 Oct 1993 12:33:07 +0000 (GMT) From: Mike Roch Subject: Getting wrong mail To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 414 Someone posted a message the other day about users (apparently) getting other people's mail. Could they re-send that message to me please? We have a similar problem. Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AF Fax: 0734 753094 From owner-pine-info@cac.washington.edu Fri Oct 29 08:25:19 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21462; Fri, 29 Oct 93 08:25:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22533; Fri, 29 Oct 93 08:09:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from aces1.acenet.auburn.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22527; Fri, 29 Oct 93 08:09:08 -0700 Received: by acenet.auburn.edu (4.1/SMI-4.1 aces1 1.0) id AA21484; Fri, 29 Oct 93 10:09:06 CDT Date: Fri, 29 Oct 1993 10:07:02 -0500 (CDT) From: "John E. Burton Jr." Subject: Pine 3.87 and Folder Filters? To: Pine Mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have a couple of questions about pine and filters for mail folders. I'm not a programmer, just a user, so please keep responses "basic," and excuse me if the questions are FAQs. I know there was some discussion on this list earlier about filters, but I was not focusing on it at that time. I receive mail from several mailing list, and would like to have the incoming mail from these lists routed to a folder just for that list or topic. Can this be done? If so, how? I've read the technical notes, help menus on pine and looked at examples in the .pinerc file, but still cannot figure out how to do this. An example. I receive incoming mail messages from a list ROOTS-L@VM1.NoDak.edu and would like to have new incoming messages from this list got directly into a folder called "roots" instead of into my INBOX. How would I configure the .pinerc file to get the incoming mail messages from this source to be filtered/routed into my folder called roots instead of to my INBOX? Thanks very much. Appreciate any help. If this is something not of interest to others, you can just e-mail me direct rather than to the list. ------------------------------------------------------- John E. Burton, Jr. jburton@acenet.auburn.edu Extension Rural Sociologist Cooperative Extension Service 213 Extension Hall Tele: 205/844-5325 Auburn University, AL 36849 FAX: 205/844-9022 ------------------------------------------------------- From owner-pine-info@cac.washington.edu Fri Oct 29 08:50:08 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22205; Fri, 29 Oct 93 08:50:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23042; Fri, 29 Oct 93 08:32:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dir.bris.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23036; Fri, 29 Oct 93 08:32:14 -0700 Received: from adm1.bristol.ac.uk by dir.bris.ac.uk with SMTP (PP) id <02027-0@dir.bris.ac.uk>; Fri, 29 Oct 1993 15:31:42 +0000 Date: Fri, 29 Oct 1993 15:25:17 +0000 (GMT) From: Dave King Reply-To: Dave King Subject: Things for 3.88? To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII initial-keystroke-list ---------------------- When setting initial-keystroke in .pinerc to present mail sorted by arrival (reversed to get new messages at top of index) as in: initial-keystroke-list=i,$,r Gives rise to the following `error' : Can't mix characters and function keys in "initial-keystroke-list", skipping. If, however, the `$' is quoted with `\' as in initial-keystroke-list=i,\$,r Pine behaves as expected. New version message ------------------- It would be helpful to reserve the `new pine version' welcome message for versions of Pine that are FUNCTIONALLY different from previous versions because displaying this message for `maintenance' releases may lead to confusion, i.e. a user asking "What's new in this version?". Dave PS I forgot to mention the above points are Pine 3.87 on DYNIX/ptx 2.0.4, but I suspect are generic. ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) From owner-pine-info@cac.washington.edu Fri Oct 29 08:57:34 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22487; Fri, 29 Oct 93 08:57:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23291; Fri, 29 Oct 93 08:40:56 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stein.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23285; Fri, 29 Oct 93 08:40:54 -0700 Received: by stein2.u.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10553; Fri, 29 Oct 93 08:40:51 -0700 X-Sender: mramey@stein2.u.washington.edu Date: Fri, 29 Oct 1993 08:34:50 -0700 (PDT) From: Mike Ramey Subject: Re: Pine 3.87 and Folder Filters? To: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII YES! I would very much like a primer on mail filters. I think they are implemented via the .forward file -- not .pinerc. (cf the 'vacation' program) Is there any thorough & understandable documentation on the uses of the .forward file? Other than "read the source code"? ... and on available filter programs and how to use them ??? -mr On Fri, 29 Oct 1993, John E. Burton Jr. wrote: > I have a couple of questions about pine and filters for mail folders. > I'm not a programmer, just a user, so please keep responses "basic," and > excuse me if the questions are FAQs. I know there was some discussion on > this list earlier about filters, but I was not focusing on it at that time. From owner-pine-info@cac.washington.edu Fri Oct 29 09:47:26 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24145; Fri, 29 Oct 93 09:47:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24609; Fri, 29 Oct 93 09:33:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24601; Fri, 29 Oct 93 09:33:11 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA10761; Fri, 29 Oct 93 09:33:04 PDT Received: from hal.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA04531; Fri, 29 Oct 93 09:33:02 PDT Received: by hal.Law.USC.EDU (4.1/SMI-4.1) id AA05187; Fri, 29 Oct 93 09:33:01 PDT Date: Fri, 29 Oct 1993 09:27:17 -0700 (PDT) From: Elmar Kurgpold Reply-To: Elmar Kurgpold Subject: Re: Pine 3.87 and Folder Filters? To: "John E. Burton Jr." Cc: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII John, I have been using a program called "procmail". This program will allow you to assign any sort of function for your incoming mail, based on what is in the headers. For example, I have all mail that has a From line of "owner-pine-info" go into a folder in ~/mail/pine-info. You can download this program from archie. I'm no programmer either, but if you need some help drop me a line. TO THE PINE TEAM: As you can see I have mail from different people or mailing lists go into folders. My gripe is that when I enter the folder, the "current" message is the very last one. I would expect this to be the first *new* message, ie the one with the lowest number marked with an "N". I believe this is how it works for the INBOX. By the way, I'm running 3.87 on a Sun4m/Solaris 1.1. ------------------------------------- | Elmar Kurgpold | | Network Administrator | | University of Southern California | | The Law Center | | ekurgpol@Law.USC.EDU | | (213)740-2571 FAX: (213)740-5502 | ------------------------------------- On Fri, 29 Oct 1993, John E. Burton Jr. wrote: > > I have a couple of questions about pine and filters for mail folders. > I'm not a programmer, just a user, so please keep responses "basic," and > excuse me if the questions are FAQs. I know there was some discussion on > this list earlier about filters, but I was not focusing on it at that time. > > I receive mail from several mailing list, and would like to have the > incoming mail from these lists routed to a folder just for that list or > topic. Can this be done? If so, how? I've read the technical notes, > help menus on pine and looked at examples in the .pinerc file, but still > cannot figure out how to do this. > > An example. I receive incoming mail messages from a list > ROOTS-L@VM1.NoDak.edu and would like to have new incoming messages from > this list got directly into a folder called "roots" instead of into my > INBOX. How would I configure the .pinerc file to get the incoming mail > messages from this source to be filtered/routed into my folder called > roots instead of to my INBOX? > > Thanks very much. Appreciate any help. If this is something not of > interest to others, you can just e-mail me direct rather than to the list. > > ------------------------------------------------------- > John E. Burton, Jr. jburton@acenet.auburn.edu > Extension Rural Sociologist > Cooperative Extension Service > 213 Extension Hall Tele: 205/844-5325 > Auburn University, AL 36849 FAX: 205/844-9022 > ------------------------------------------------------- > > > From owner-pine-info@cac.washington.edu Fri Oct 29 09:56:32 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24359; Fri, 29 Oct 93 09:56:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24882; Fri, 29 Oct 93 09:41:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shamash.cdc.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24874; Fri, 29 Oct 93 09:41:31 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA24369; Fri, 29 Oct 93 11:41:19 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA19461; Sat, 30 Oct 93 00:29:53 +0800 Date: Sat, 30 Oct 1993 00:25:14 +0800 (TPE) From: Ed Greshko Subject: Re: Pine 3.87 and Folder Filters? To: "John E. Burton Jr." Cc: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, This is not something that is done in pine. It is not included in the pine package. I use the "filter" routine supplied as part of the elm package. Another alternative, I'm told, is procmail. I'm happy with the "filter" from elm. It can store messages in folders according to Subject:, To:, From:, and other things. You can also start a process depending on those same fields. Regards, Ed Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Fri Oct 29 09:57:54 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24406; Fri, 29 Oct 93 09:57:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24792; Fri, 29 Oct 93 09:40:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24786; Fri, 29 Oct 93 09:40:29 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA14715; Fri, 29 Oct 1993 11:44:20 -0500 Date: Fri, 29 Oct 1993 11:42:07 -0500 (CDT) From: "Robert A. Hayden" Subject: Re: Pine 3.87 and Folder Filters? To: "John E. Burton Jr." Cc: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 29 Oct 1993, John E. Burton Jr. wrote: > I receive mail from several mailing list, and would like to have the > incoming mail from these lists routed to a folder just for that list or > topic. Can this be done? If so, how? I've read the technical notes, > help menus on pine and looked at examples in the .pinerc file, but still > cannot figure out how to do this. I use and recommend using the 'filter' program that comes with elm. It is a very functional filter program and can easily handle by 65 or so defined filter fields I have set up. (also makes a great kill file for mailing lists :-) ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> Veteran of the Bermuda Triangle \/ Finger for PGP 2.3a Public Key <=> Expeditionary Force -- 1993-1951 -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Fri Oct 29 10:25:45 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25203; Fri, 29 Oct 93 10:25:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25341; Fri, 29 Oct 93 10:08:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25335; Fri, 29 Oct 93 10:08:07 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14478; Fri, 29 Oct 93 10:08:01 -0700 Date: Fri, 29 Oct 1993 10:00:42 -0700 (PDT) From: Terry Gray Subject: Re: Pine 3.87 and Folder Filters? To: Elmar Kurgpold Cc: "John E. Burton Jr." , Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 29 Oct 1993, Elmar Kurgpold wrote: > As you can see I have mail from different people or mailing lists go into > folders. My gripe is that when I enter the folder, the "current" message > is the very last one. I would expect this to be the first *new* message, > ie the one with the lowest number marked with an "N". I believe this is > how it works for the INBOX. Elmar, If you filter your incoming into folders defined in the "incoming-folders=" variable of your pinerc, and open them via that section of your List Folders screen, you'll get the behavior you want. The incoming-folders idea was exactly for this delivery filter case, or where you have inboxes on multiple machines, and accordingly the initial message is set to the first new one. In the saved-message folders, the last msg is thought to be more often of interest, and until the IMAP2bis extension is implemented that permits copying the message-state flags, looking for the first "New" msg is not very useful anyway. -teg From owner-pine-info@cac.washington.edu Fri Oct 29 10:27:25 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25326; Fri, 29 Oct 93 10:27:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25290; Fri, 29 Oct 93 10:06:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stein.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25284; Fri, 29 Oct 93 10:06:43 -0700 Received: by stein2.u.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24463; Fri, 29 Oct 93 10:06:41 -0700 X-Sender: mramey@stein2.u.washington.edu Date: Fri, 29 Oct 1993 10:04:49 -0700 (PDT) From: Mike Ramey Subject: Re: Pine 3.87 and Folder Filters? To: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I didn't know about the 'incoming-folders' parameter in the .pinerc file. A tutorial on how to use it would be very helpful. -mr On Fri, 29 Oct 1993, Mike Ramey wrote: > YES! I would very much like a primer on mail filters. > I think they are implemented via the .forward file -- not .pinerc. From owner-pine-info@cac.washington.edu Fri Oct 29 10:48:12 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25854; Fri, 29 Oct 93 10:48:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25711; Fri, 29 Oct 93 10:30:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stein.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25700; Fri, 29 Oct 93 10:30:01 -0700 Received: by stein2.u.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA27895; Fri, 29 Oct 93 10:29:56 -0700 X-Sender: mramey@stein2.u.washington.edu Date: Fri, 29 Oct 1993 10:12:49 -0700 (PDT) From: Mike Ramey Subject: .pinerc file "Updated by Pine(tm) 3.87" -- omissions To: Pine-Info Email List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My old (3.05?) .pinerc file was "Updated by Pine(tm) 3.87" when the new version was installed. I recently discovered that some of the information contained in a 'brand-new' pine 3.87 .pinerc file did not make it into my old 'updated' file. Specifically, the last 4 lines of the introductory paragraph (beginning with "For a variable to be unset it's value must be blank. ...") are missing from my 'updated' file. Also the section headers do not appear; such as: ####...#### Essential Parameters ####...#### This may be difficult because I had rearranged the order of entries in my .pinerc file, so that all changed entries would be at the top of the file. Also the description of parameters WAS -NOT- UPDATED! My old 'updated' file still contained: # Sub directory in users home directory where mail folders/files are kept # mail-directory= mail-directory=Mail (which I had changed so that all my directories begin with Capital Letters -- to segregate them from ordinary files). In a 'brand-new' 3.87 .pinerc file, the definition of this parameter is: # mail-directory is where postponed & interrupted msgs are held temp'y QUESTION: Under pine 3.87, if I want the directory 'mail' to be fully replaced by the directory 'Mail', are these the only changes required ? folder-collections=Mail/[] mail-directory=Mail REQUEST: Is it possible in future, to do a more thorough job of updating the .pinerc file? It would be helpful to alert users to changes in .pinerc which might affect them -- especially if .pinerc contains user changes. Thanks, -mr From owner-pine-info@cac.washington.edu Fri Oct 29 12:28:06 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28871; Fri, 29 Oct 93 12:28:06 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27947; Fri, 29 Oct 93 12:17:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from class.class.org by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27939; Fri, 29 Oct 93 12:17:43 -0700 Received: by class.class.org (4.1/CLASS-1.0) id AA29047; Fri, 29 Oct 93 12:17:37 PDT Date: Fri, 29 Oct 1993 12:17:03 -0700 (PDT) From: ABC News Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII unsub pine-info From owner-pine-info@cac.washington.edu Fri Oct 29 12:58:42 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29446; Fri, 29 Oct 93 12:58:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28397; Fri, 29 Oct 93 12:45:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28382; Fri, 29 Oct 93 12:45:00 -0700 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA19939; Fri, 29 Oct 93 12:44:55 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 29 Oct 93 20:32:11+0100 Date: 29 Oct 93 20:32:11+0100 From: ABC News Message-Id: <461576*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine-Info Email List From owner-pine-info@cac.washington.edu Fri Oct 29 14:06:31 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01960; Fri, 29 Oct 93 14:06:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08118; Fri, 29 Oct 93 13:50:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ultrix.ramapo.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08112; Fri, 29 Oct 93 13:50:35 -0700 Received: by ultrix (5.57/Ultrix3.0-C) id AA11616; Fri, 29 Oct 93 16:52:43 -0400 Date: Fri, 29 Oct 1993 16:51:24 -0400 (EDT) From: "Jackie \"Oh!\" Owen" Subject: Re: Pine 3.87 and Folder Filters? To: Mike Ramey Cc: Pine Mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII If you get the elm software, in the doc subdirectory, there is a Filter.guid which I found very helpful in implementing filters for one of our users. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Jackie Loucks Owen Network Administrator jowen@ultrix.ramapo.edu Ramapo College of NJ Mahwah, NJ "Time flies like an arrow. Fruit flies like a banana." ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Fri, 29 Oct 1993, Mike Ramey wrote: > I didn't know about the 'incoming-folders' parameter in the .pinerc file. > A tutorial on how to use it would be very helpful. -mr > > On Fri, 29 Oct 1993, Mike Ramey wrote: > > YES! I would very much like a primer on mail filters. > > I think they are implemented via the .forward file -- not .pinerc. > > From owner-pine-info@cac.washington.edu Sun Oct 31 07:26:38 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28502; Sun, 31 Oct 93 07:26:38 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18404; Sun, 31 Oct 93 07:14:33 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from discus.technion.ac.il by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18398; Sun, 31 Oct 93 07:13:54 -0800 Received: from localhost (oved@localhost) by discus.technion.ac.il (8.5/8.5) id RAA26185; Sun, 31 Oct 1993 17:13:13 +0200 Date: Sun, 31 Oct 1993 17:08:05 +0200 (EET) From: Oved Ben-Aroya Subject: Re: Addressbook format [ To: Rick Troth Cc: David Wall , pine-info@cac.washington.edu, ccsmbrk@technion.technion.ac.il In-Reply-To: <9306011637.AA19675@mx1.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 1 Jun 1993, Rick Troth wrote: > >We also have a program to convert between RICE mailer notebooks and the > >Pine addressbook. The author is Tom Remmers. (remmers@u.washington.edu.) ... > > Rick Troth , Rice University, Information Systems > Thanks Rick, we are using successfully your tools. However, we wonder if there is also a tool for VM's "names" conversion. -- \Oved From owner-pine-info@cac.washington.edu Sun Oct 31 11:11:19 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29796; Sun, 31 Oct 93 11:11:19 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19602; Sun, 31 Oct 93 11:01:48 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19596; Sun, 31 Oct 93 11:01:47 -0800 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA16744; Sun, 31 Oct 1993 13:05:45 -0600 Date: Sun, 31 Oct 1993 13:02:55 -0600 (CST) From: "Robert A. Hayden" Subject: Command line use of addressbook To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm curious to know is there is a way to send mail from the command line to a distribution in the addressbook. I have several scripts that I run automatically periodically to mail out FAQs and other things. Unfortunately, there is a series of mailing that I end up sending manually to a large (~150 person) distribution. I'm just wondering if there is a way to do it from the command line so I can slap it into my script and be done with it. Thanks much. ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> Veteran of the Bermuda Triangle \/ Finger for PGP 2.3a Public Key <=> Expeditionary Force -- 1993-1951 -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Sun Oct 31 11:56:44 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00193; Sun, 31 Oct 93 11:56:44 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18022; Sun, 31 Oct 93 11:48:36 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [128.193.164.25] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18016; Sun, 31 Oct 93 11:48:34 -0800 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA12656; Sun, 31 Oct 93 11:49:02 -0800 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA16031; Sun, 31 Oct 93 11:51:33 -0800 Date: Sun, 31 Oct 1993 11:49:16 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Command line use of addressbook To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 31 Oct 1993, Robert A. Hayden wrote: > I'm curious to know is there is a way to send mail from the command line > to a distribution in the addressbook. I have several scripts that I run > automatically periodically to mail out FAQs and other things. > Unfortunately, there is a series of mailing that I end up sending > manually to a large (~150 person) distribution. I'm just wondering if > there is a way to do it from the command line so I can slap it into my > script and be done with it. I have a couple of pine-format mailing lists that I mail to...the one I use most is called "og"... To mail to it I type: pine og (I have pine aliased to pine -zi and am using version 3.87 with the command line fix from 3.85) Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 From owner-pine-info@cac.washington.edu Sun Oct 31 22:36:55 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA04300; Sun, 31 Oct 93 22:36:55 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23286; Sun, 31 Oct 93 22:27:13 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bradley.bradley.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23280; Sun, 31 Oct 93 22:27:11 -0800 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA16368 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Mon, 1 Nov 93 00:27:10 -0600 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA26492; Mon, 1 Nov 93 00:27:09 CST Date: Mon, 1 Nov 1993 00:25:11 -0600 (CST) From: Matt Simmons Subject: pico for news To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When using pico for editting news articles, it has this annoying tendency to automatically clip long references lines into two smaller lines, so that I have to change them back to one line before it's a legal article again... This was not in the pico that came with 3.07... (i.e. the pico from 3.07 didn't divide the references line)... Can the 3.87 pico be changed back to the 3.07 pico behavior?? Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Mon Nov 1 08:05:04 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10597; Mon, 1 Nov 93 08:05:04 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26794; Mon, 1 Nov 93 07:30:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from peacock.uwaterloo.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26785; Mon, 1 Nov 93 07:29:42 -0800 Received: by peacock.uwaterloo.ca id <53922>; Mon, 1 Nov 1993 10:29:10 -0500 Date: Mon, 1 Nov 1993 10:15:20 -0500 From: "Sunjay T. Bedi" Subject: pine 3.87 on Ultrix 3.1 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Has anyone port/compiled this? ========================================================= Sunjay T. Bedi, (519)888-4567, ext. 5297 /\ /\ stbedi@peacock.uwaterloo.ca / \ / \ University of Waterloo /____\/____\ ========================================================= From owner-pine-info@cac.washington.edu Mon Nov 1 09:28:18 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13301; Mon, 1 Nov 93 09:28:18 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22765; Mon, 1 Nov 93 09:09:29 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uafhp.uark.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22759; Mon, 1 Nov 93 09:09:23 -0800 Received: from comp.uark.edu by uafhp.uark.edu with SMTP (1.37.109.4/15.6) id AA10852; Mon, 1 Nov 93 11:07:51 -0600 Received: by (5.0/SMI-SVR4) id AA07396; Mon, 1 Nov 93 10:57:23 CST Date: Mon, 1 Nov 1993 10:56:22 -0600 (CST) From: Gene Trantham Subject: Re: Addressbook format To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 0 > > Thanks Rick, we are using successfully your tools. However, we wonder > if there is also a tool for VM's "names" conversion. > > -- > \Oved I have such a tool. It is a Bourne shell script which relies heavily on awk (well, nawk actually). Anybody who wishes a copy can drop me a line in e-mail. I'd be happy to share. I am in the process of re-coding the utility in C, with a grammar constructed using lex & yacc. I'm a ways off on that, however (I'm a yacc novice). -- Gene Trantham University of Arkansas gtrantha@comp.uark.edu From owner-pine-info@cac.washington.edu Mon Nov 1 09:30:07 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13355; Mon, 1 Nov 93 09:30:07 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22775; Mon, 1 Nov 93 09:10:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uafhp.uark.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22769; Mon, 1 Nov 93 09:10:19 -0800 Received: from comp.uark.edu by uafhp.uark.edu with SMTP (1.37.109.4/15.6) id AA10425; Mon, 1 Nov 93 10:56:48 -0600 Received: by (5.0/SMI-SVR4) id AA07396; Mon, 1 Nov 93 10:57:23 CST Date: Mon, 1 Nov 1993 10:56:22 -0600 (CST) From: Gene Trantham Subject: Re: Addressbook format To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 555 > > Thanks Rick, we are using successfully your tools. However, we wonder > if there is also a tool for VM's "names" conversion. > > -- > \Oved I have such a tool. It is a Bourne shell script which relies heavily on awk (well, nawk actually). Anybody who wishes a copy can drop me a line in e-mail. I'd be happy to share. I am in the process of re-coding the utility in C, with a grammar constructed using lex & yacc. I'm a ways off on that, however (I'm a yacc novice). -- Gene Trantham University of Arkansas gtrantha@comp.uark.edu From owner-pine-info@cac.washington.edu Mon Nov 1 11:04:54 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16645; Mon, 1 Nov 93 11:04:54 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00945; Mon, 1 Nov 93 10:42:25 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00939; Mon, 1 Nov 93 10:42:23 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21848; Mon, 1 Nov 93 10:42:19 -0800 Date: Mon, 1 Nov 1993 10:26:14 -0800 (PST) From: David L Miller Subject: Re: .pinerc file "Updated by Pine(tm) 3.87" -- omissions To: Mike Ramey Cc: Pine-Info Email List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine does not really "understand" the comments in the .pinerc. When updating an old .pinerc, the old comments are preserved as much as possible to preserve any comments the user has inserted or modified. We plan to make Pine smarter about comments at some point in the future... |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 29 Oct 1993, Mike Ramey wrote: > My old (3.05?) .pinerc file was "Updated by Pine(tm) 3.87" when the new > version was installed. I recently discovered that some of the > information contained in a 'brand-new' pine 3.87 .pinerc file did not > make it into my old 'updated' file. Specifically, the last 4 lines of > the introductory paragraph (beginning with "For a variable to be unset > it's value must be blank. ...") are missing from my 'updated' file. > > Also the section headers do not appear; such as: > ####...#### Essential Parameters ####...#### > This may be difficult because I had rearranged the order of entries in my > .pinerc file, so that all changed entries would be at the top of the file. > > Also the description of parameters WAS -NOT- UPDATED! My old 'updated' > file still contained: > # Sub directory in users home directory where mail folders/files are kept > # mail-directory= > mail-directory=Mail > (which I had changed so that all my directories begin with Capital > Letters -- to segregate them from ordinary files). > > In a 'brand-new' 3.87 .pinerc file, the definition of this parameter is: > # mail-directory is where postponed & interrupted msgs are held temp'y > > QUESTION: Under pine 3.87, if I want the directory 'mail' to be fully > replaced by the directory 'Mail', are these the only changes required ? > folder-collections=Mail/[] > mail-directory=Mail > Unless you have some other setting, like read-message-folder, pointing to mail. > REQUEST: Is it possible in future, to do a more thorough job of updating > the .pinerc file? It would be helpful to alert users to changes in > .pinerc which might affect them -- especially if .pinerc contains user > changes. > > Thanks, -mr > From owner-pine-info@cac.washington.edu Mon Nov 1 11:07:28 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16718; Mon, 1 Nov 93 11:07:28 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00842; Mon, 1 Nov 93 10:37:47 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00830; Mon, 1 Nov 93 10:37:44 -0800 Resent-Message-Id: <9311011837.AA00830@mx1.cac.washington.edu> Message-Id: <9311011837.AA00830@mx1.cac.washington.edu> Received: from UWAVM.U.WASHINGTON.EDU by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with BSMTP id 7043; Mon, 01 Nov 93 10:37:03 PST Received: from ETSU.EAST-TENN-ST.EDU by UWAVM.U.WASHINGTON.EDU (Mailer R2.10 ptf008) with BSMTP id 3216; Mon, 01 Nov 93 10:37:02 PST Received: from ETSU.EAST-TENN-ST.EDU (NJE origin CMS2@ETSU) by ETSU.EAST-TENN-ST.EDU (LMail V1.1d/1.7f) with BSMTP id 0615; Mon, 1 Nov 1993 13:36:19 -0500 Resent-Date: Mon, 01 Nov 93 13:35:32 EST Resent-From: Bill Williams Resent-Organization: East Tennessee State University Resent-To: pine-info@cac.washington.edu Date: Wed, 27 Oct 93 08:14:05 EDT From: Bill Williams Organization: East Tennessee State University Subject: Binaries for AIX 3.2 To: pine-bugs@cac.washington.edu I am running AIX 3.2.3 and can build pine/pico just fine using the 'build a32'; however, when I run pine almost anything I do causes a IOTrap abend with core dump. It appears that this is a problem with the AIX 3.2.3 system which according to reports out in NetLand does not occur with AIX 3.2.4. I ftp-ed your aix32 binaries but they have the problem of not recognizing my 'vt220' terminal. There is a simple fix for this and I would like to request a re-build of the aix32 binaries (pine/pico) to solve the problem. The only change needed is to the 'makefile.a32' files and that is just an insertion of "-lcurses" into the LIBES as the first library. It should look like: LIBES = -lcurses -ltermcap -lc instead of: LIBES = -ltermcap -lc when this is done it should link without problems *and* recognize all the vtXXX's normally known to AIX. If you could rebuild those binaries with the -lcurses I would be very grateful! BTW: All my correspondence to the pine lists have been from this account which is an IBM VM/ESA System running RiceMail (MUA) and LMail (MTA) -- which does not support MIME at this time. I have no Pine/Pico available at this time on any of my machines.... and I really need it on my RS/6000 AIX 3.2.3 units. --------------------------------------- Bill Williams -- ETSU Systems Support East Tennessee (615) 929-6853 State University From owner-pine-info@cac.washington.edu Mon Nov 1 12:21:48 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18762; Mon, 1 Nov 93 12:21:48 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02394; Mon, 1 Nov 93 11:58:14 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from RUTGERS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02387; Mon, 1 Nov 93 11:58:12 -0800 Received: from mimsy.UUCP by rutgers.edu (5.59/SMI4.0/RU1.5/3.08) with UUCP id AA26951; Mon, 1 Nov 93 14:20:48 EST Received: by mimsy.cs.UMD.EDU (5.64/UMIACS-0.9/04-05-88) id AA27482; Mon, 1 Nov 93 14:18:38 -0500 Received: from ghost.uunet.ca (via uunet.ca) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA25651; Mon, 1 Nov 93 14:11:00 -0500 Received: from moore by mail.uunet.ca with UUCP id <101640(4)>; Mon, 1 Nov 1993 14:10:42 -0500 Received: by moore.com (4.1/smail2.5/01-12-90) id AA04097; Mon, 1 Nov 93 14:09:14 EST Date: Mon, 1 Nov 1993 14:06:40 -0500 From: Paul Maclauchlan Subject: Reading news To: Pine Info mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'd like to read news from the Pine mailreader. How can I convince Pine to look in a non-conventional place for news? Instead of /usr/spool/news, I keep my news in /usr/news/spool. This is on the local system (no NNTP or IMAP needed). Any help or hints are appreciated. -- .../Paul Maclauchlan Moore Corporation Limited, Toronto, Ontario (416) 364-2600 paul@moore.com -or- {...!uunet.ca,...!telly}!moore!paul "Living is easy with eyes closed, misunderstanding all you see"/JL'67 From owner-pine-info@cac.washington.edu Mon Nov 1 13:29:07 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20502; Mon, 1 Nov 93 13:29:07 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24398; Mon, 1 Nov 93 13:13:59 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from locus.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24390; Mon, 1 Nov 93 13:13:54 -0800 Received: by locus.halcyon.com id AA00274 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 1 Nov 1993 13:13:47 -0800 Date: Mon, 1 Nov 1993 21:08:54 +0000 From: Ralph Sims Subject: Possible bug with pine - imap allows login w/o passwd To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have been using pine (albeit 3.85, as that's the last linux port that I have--awaiting 3.88) via imap. It appears that if I close the remote mailbox and exit the host and rather invoke the remote host again via imap, that I am not prompted for a userid or password. Is there some type of 'hidden authentication' still in effect that would not allow someone 'posing' as me to log in via imap and access my mailbox during this brief period. It seems that if I exit the host and look at [INBOX] as a new folder and then go back to the remote host, all's well. Possibly, I'm seeing that pine is still connected via imap and doesn't actually close the connection until a new folder is opened. Ideas? From owner-pine-info@cac.washington.edu Mon Nov 1 15:38:34 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23924; Mon, 1 Nov 93 15:38:34 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06157; Mon, 1 Nov 93 15:25:11 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06151; Mon, 1 Nov 93 15:25:06 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01539; Mon, 1 Nov 93 15:24:57 -0800 Date: Mon, 1 Nov 1993 15:19:02 -0800 (PST) From: David L Miller Subject: Re: Reading news To: Paul Maclauchlan Cc: Pine Info mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can edit the c-client/os_???.h file for your system and change the definition of NEWSSPOOL, then rebuild. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 1 Nov 1993, Paul Maclauchlan wrote: > > I'd like to read news from the Pine mailreader. How can I convince Pine > to look in a non-conventional place for news? > > Instead of /usr/spool/news, I keep my news in /usr/news/spool. This is > on the local system (no NNTP or IMAP needed). > > Any help or hints are appreciated. > > -- > .../Paul Maclauchlan > Moore Corporation Limited, Toronto, Ontario (416) 364-2600 > paul@moore.com -or- {...!uunet.ca,...!telly}!moore!paul > "Living is easy with eyes closed, misunderstanding all you see"/JL'67 > > From owner-pine-info@cac.washington.edu Mon Nov 1 15:46:23 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24065; Mon, 1 Nov 93 15:46:23 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25374; Mon, 1 Nov 93 15:36:55 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from coho.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25368; Mon, 1 Nov 93 15:36:51 -0800 Received: by halcyon.com id AA04839 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 1 Nov 1993 15:36:44 -0800 From: Ralph Sims Message-Id: <199311012336.AA04839@halcyon.com> Subject: Re: Reading news To: dlm@cac.washington.edu (David L Miller) Date: Mon, 1 Nov 1993 15:36:41 -0800 (PST) Cc: paul@moore.com, pine-info@cac.washington.edu In-Reply-To: from "David L Miller" at Nov 1, 93 03:19:02 pm X-Mailer: ELM [version 2.4 PL13] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 172 > You can edit the c-client/os_???.h file for your system and change > the definition of NEWSSPOOL, then rebuild. Or, you can provide a symbolic link to /usr/spool/news. From owner-pine-info@cac.washington.edu Mon Nov 1 16:14:16 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24828; Mon, 1 Nov 93 16:14:16 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06732; Mon, 1 Nov 93 15:57:32 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06724; Mon, 1 Nov 93 15:57:30 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02919; Mon, 1 Nov 93 15:56:05 -0800 Date: Mon, 1 Nov 1993 15:50:13 -0800 (PST) From: David L Miller Subject: Re: Possible bug with pine - imap allows login w/o passwd To: Ralph Sims Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A folder remains open until you exit pine or open another folder, the exception being the INBOX which remains open until you exit Pine. Is this what you are seeing? |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 1 Nov 1993, Ralph Sims wrote: > I have been using pine (albeit 3.85, as that's the last linux port that I > have--awaiting 3.88) via imap. It appears that if I close the remote > mailbox and exit the host and rather invoke the remote host again via > imap, that I am not prompted for a userid or password. > > Is there some type of 'hidden authentication' still in effect that would > not allow someone 'posing' as me to log in via imap and access my mailbox > during this brief period. It seems that if I exit the host and look at > [INBOX] as a new folder and then go back to the remote host, all's well. > > Possibly, I'm seeing that pine is still connected via imap and doesn't > actually close the connection until a new folder is opened. > > Ideas? > > From owner-pine-info@cac.washington.edu Tue Nov 2 05:29:03 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06229; Tue, 2 Nov 93 05:29:03 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14244; Tue, 2 Nov 93 05:14:39 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14238; Tue, 2 Nov 93 05:14:37 -0800 Received: from quinag.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <16570-0@ppsw2.cam.ac.uk>; Tue, 2 Nov 1993 13:14:32 +0000 Date: Tue, 2 Nov 1993 13:13:47 GMT From: Barry Landy Reply-To: Barry Landy Subject: Finger in PC-PINE To: Pine Info list X-Sender: bl10@cus.cam.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Users of our system would like to find out about other users on the system, for example when they cannot remember their e-mail ID. If they also use the underlying UNIX system, finger does it for them. If they only use PINE on a PC, they have to exit PINE, use finger, then go back in to send the mail. It would be nice to have a "finger" option available on PINE's menu. This can only be classed as an "it would be nice" item for the wishlist. Since MAISTROM does it on the MAC, I assume that all the necessary IMAP features are already present. ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Tue Nov 2 06:29:11 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06829; Tue, 2 Nov 93 06:29:11 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29156; Tue, 2 Nov 93 06:11:09 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29150; Tue, 2 Nov 93 06:11:07 -0800 Received: from mumrik.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA18600; Tue, 2 Nov 93 15:11:05 +0100 Message-Id: <9311021411.AA18600@nada.kth.se> To: pine-info@cac.washington.edu Subject: INBOX again: BSD-mail-mbox model not allowed? Date: Tue, 02 Nov 1993 15:11:04 +0100 From: Peter Svanberg I've tried to read all about INBOX in the documentation and in old messages on this list. Conclusions: 1) It is impossible to get the BSD-mail behavior with BSD- format usage in PINE - i.e. that incoming, read and unread mail is handled in _one_ file, which is not in /usr/spool/mail. 2) With Tenex-format usage - on the other hand - this behavior is the default: /usr/spool/mail contents is silently moved to the mail.TxT file. Questions: 3) Is the silently-moving model considered bad for _all_ users? In what way? 4) If so, why is that model still used with Tenex? If not, why not allow it in BSD-format usage also? At least, I think, the documentation should warn, tell and explain about this big difference for users used to the BSD-mail program. I have not found anything about it. --- Peter Svanberg, NADA, KTH Email: psv@nada.kth.se Dept of Num An & CS, Royal Inst of Tech Phone: +46 8 790 71 40 S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From owner-pine-info@cac.washington.edu Tue Nov 2 08:47:59 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09139; Tue, 2 Nov 93 08:47:59 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15984; Tue, 2 Nov 93 08:17:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15978; Tue, 2 Nov 93 08:17:09 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13931; Tue, 2 Nov 93 08:16:03 -0800 Date: Tue, 2 Nov 1993 08:13:07 -0800 (PST) From: David L Miller Subject: Re: Finger in PC-PINE To: Barry Landy Cc: Pine Info list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Finger is not a function of IMAP. We are planning to add support for directory services, which might include some form of access to finger as well. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 2 Nov 1993, Barry Landy wrote: > Users of our system would like to find out about other users on the > system, for example when they cannot remember their e-mail ID. If they > also use the underlying UNIX system, finger does it for them. If they > only use PINE on a PC, they have to exit PINE, use finger, then go back > in to send the mail. It would be nice to have a "finger" option available > on PINE's menu. > This can only be classed as an "it would be nice" item for the wishlist. > Since MAISTROM does it on the MAC, I assume that all the necessary IMAP > features are already present. > > ======================================================================= > Barry Landy, Head of Systems and Development, > University of Cambridge Computing Service > Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 > > From owner-pine-info@cac.washington.edu Tue Nov 2 08:55:56 1993 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09438; Tue, 2 Nov 93 08:55:56 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16238; Tue, 2 Nov 93 08:31:16 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16232; Tue, 2 Nov 93 08:31:14 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14635; Tue, 2 Nov 93 08:30:59 -0800 Date: Tue, 2 Nov 1993 08:22:44 -0800 (PST) From: David L Miller Subject: Re: INBOX again: BSD-mail-mbox model not allowed? To: Peter Svanberg Cc: pine-info@cac.washington.edu In-Reply-To: <9311021411.AA18600@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can get this behavior by linking the mbox driver into Pine. This is the Berkeley format (bezerk) driver with silent moving added. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 2 Nov 1993, Peter Svanberg wrote: > I've tried to read all about INBOX in the documentation and in > old messages on this list. Conclusions: > > 1) It is impossible to get the BSD-mail behavior with BSD- > format usage in PINE - i.e. that incoming, read and unread > mail is handled in _one_ file, which is not in > /usr/spool/mail. > > 2) With Tenex-format usage - on the other hand - this behavior > is the default: /usr/spool/mail contents is silently moved to > the mail.TxT file. > > Questions: > > 3) Is the silently-moving model considered bad for _all_ users? > In what way? > > 4) If so, why is that model still used with Tenex? If not, why > not allow it in BSD-format usage also? > > At least, I think, the documentation should warn, tell and > explain about this big difference for users used to the > BSD-mail program. I have not found anything about it. > --- > Peter Svanberg, NADA, KTH Email: psv@nada.kth.se > Dept of Num An & CS, > Royal Inst of Tech Phone: +46 8 790 71 40 > S-100 44 Stockholm, SWEDEN Fax: +46 8 790 09 30 From owner-pine-info@cac.washington.edu Tue Nov 2 11:22:03 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14673; Tue, 2 Nov 93 11:22:03 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00922; Tue, 2 Nov 93 11:00:43 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.nada.kth.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00916; Tue, 2 Nov 93 11:00:34 -0800 Received: from mumrik.nada.kth.se by mail.nada.kth.se (5.61-bind 1.4+ida/nada-mx-1.0) id AA23801; Tue, 2 Nov 93 20:00:21 +0100 Message-Id: <9311021900.AA23801@nada.kth.se> To: David L Miller Cc: pine-info@cac.washington.edu Subject: Re: INBOX again: BSD-mail-mbox model not allowed? In-Reply-To: Your message of "Tue, 02 Nov 1993 08:22:44 PST." Date: Tue, 02 Nov 1993 20:00:20 +0100 From: Peter Svanberg Quoting: David L Miller > > You can get this behavior by linking the mbox driver into Pine. This > is the Berkeley format (bezerk) driver with silent moving added. Thanks - works fine! BTW, I saw there has been some progress to the MH driver - any change in the will-maybe-work-some-day plans I was told before? --- Peter Svanberg, Nada, KTH From owner-pine-info@cac.washington.edu Tue Nov 2 11:45:50 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15672; Tue, 2 Nov 93 11:45:50 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01183; Tue, 2 Nov 93 11:23:13 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01177; Tue, 2 Nov 93 11:23:10 -0800 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA11347; Tue, 2 Nov 93 11:21:38 -0800 Date: Tue, 2 Nov 1993 11:09:20 -0800 (PST) From: Mark Crispin Subject: Re: Possible bug with pine - imap allows login w/o passwd To: Ralph Sims Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 1 Nov 1993, Ralph Sims wrote: > I have been using pine (albeit 3.85, as that's the last linux port that I > have--awaiting 3.88) via imap. It appears that if I close the remote > mailbox and exit the host and rather invoke the remote host again via > imap, that I am not prompted for a userid or password. > > Is there some type of 'hidden authentication' still in effect that would > not allow someone 'posing' as me to log in via imap and access my mailbox > during this brief period. The only ``hidden authentication'' in Pine/imapd is that if you can rsh to the remote host for free, you can imap to it for free. In other words, the answer is NO. > Possibly, I'm seeing that pine is still connected via imap and doesn't > actually close the connection until a new folder is opened. This can happen. The primary INBOX is always kept open, and secondary streams can be recycled to open new folders. From owner-pine-info@cac.washington.edu Tue Nov 2 11:59:33 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16048; Tue, 2 Nov 93 11:59:33 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01246; Tue, 2 Nov 93 11:31:34 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01237; Tue, 2 Nov 93 11:31:25 -0800 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA11355; Tue, 2 Nov 93 11:31:06 -0800 Date: Tue, 2 Nov 1993 11:27:46 -0800 (PST) From: Mark Crispin Subject: Re: INBOX again: BSD-mail-mbox model not allowed? To: Peter Svanberg Cc: pine-info@cac.washington.edu In-Reply-To: <9311021411.AA18600@nada.kth.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 2 Nov 1993, Peter Svanberg wrote: > I've tried to read all about INBOX in the documentation and in > old messages on this list. Conclusions: > > 1) It is impossible to get the BSD-mail behavior with BSD- > format usage in PINE - i.e. that incoming, read and unread > mail is handled in _one_ file, which is not in > /usr/spool/mail. This is correct with unmodified Pine. If you modify the .../pine/pine.c file to have a line of mail_link (&mboxdriver); before the mail_link() call for bezerkdriver (you may also have to add mboxdriver in the list of driver externals elsewhere), then you will get that behavior. mbox is like tenex, but it uses the /usr/spool/mail format. > 2) With Tenex-format usage - on the other hand - this behavior > is the default: /usr/spool/mail contents is silently moved to > the mail.TxT file. This is correct. > 3) Is the silently-moving model considered bad for _all_ users? > In what way? Some people find it objectionable, which is why mboxdriver is normally turned off. > 4) If so, why is that model still used with Tenex? If not, why > not allow it in BSD-format usage also? This model is the only model meaningful for Tenex. But, because some people find mail.txt to be a dangerous name, it was changed to mail.TxT. From owner-pine-info@cac.washington.edu Tue Nov 2 12:20:25 1993 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16598; Tue, 2 Nov 93 12:20:25 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01435; Tue, 2 Nov 93 12:02:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from locus.halcyon.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01425; Tue, 2 Nov 93 12:02:28 -0800 Received: by locus.halcyon.com id AA01727 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Tue, 2 Nov 1993 12:02:23 -0800 Date: Tue, 2 Nov 1993 19:58:12 +0000 From: Ralph Sims Subject: Re: Possible bug with pine - imap allows login w/o passwd To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've just compiled 3.87 for linux. We're up to speed now. All that remains is to work on the the .pinerc file (beginning to resemble a sendmail.cf file to some degree with all the options available). Thanks to you and David Miller. The pieces to the puzzle are now easier to put together. On Tue, 2 Nov 1993, Mark Crispin wrote: > > Possibly, I'm seeing that pine is still connected via imap and doesn't > > actually close the connection until a new folder is opened. > This can happen. The primary INBOX is always kept open, and secondary > streams can be recycled to open new folders.