From owner-pine-info@cac.washington.edu Wed Sep 1 02:39:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17277; Wed, 1 Sep 93 02:39:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02632; Wed, 1 Sep 93 02:20:05 -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 AA02626; Wed, 1 Sep 93 02:20:02 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <12368-0@susssys1.reading.ac.uk>; Wed, 1 Sep 1993 10:18:01 +0100 Date: Wed, 1 Sep 1993 10:02:28 +0100 (BST) From: Mike Roch Subject: Re: Addition feature for novices To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: The 'automatically move read messages to mbox' trick of UCB mail is confusing for novices; without warning they suddenly have to look for mail in two places. Even if Pine implemented an 'auto save to Oldmail' on read messages, many users would be alarmed at seeing the consequent deletions on screen. This is why my suggestion makes it a user-choosable option, but if offered to users at the beginning of each month, many of them would say "yes". Where novices keep hundreds of mesages in a heap it's usually because it hasn't occured to them that it could be done any other way or because they fear losing messages by mucking about. "Move Inbox to Inbox-Aug-93?" would seem an unthreatening yet sensible suggestion to be making to these people. Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AH. Fax: 0734 753094 From owner-pine-info@cac.washington.edu Wed Sep 1 04:16:06 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19558; Wed, 1 Sep 93 04:16:06 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03580; Wed, 1 Sep 93 04:04:33 -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 AA03558; Wed, 1 Sep 93 04:04:29 -0700 Received: from carlisle.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <23654-0@Rye.city.ac.uk>; Wed, 1 Sep 1993 12:03:03 +0100 Date: Wed, 1 Sep 1993 12:03:01 +0100 (BST) From: "D.K.Brownlee" Subject: Pine 3.85 To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO X-Status: Any update on the release date? We've decided to go with pine as our primary unix mailer this year (Starting october). Should we be workign with 3.07, or do we wait? :) 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. From owner-pine-info@cac.washington.edu Wed Sep 1 06:57:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22230; Wed, 1 Sep 93 06:57:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04733; Wed, 1 Sep 93 06:44:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from leeman.york.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04727; Wed, 1 Sep 93 06:44:32 -0700 Received: from tower.york.ac.uk by leeman.york.ac.uk with SMTP (PP) id <23306-0@leeman.york.ac.uk>; Wed, 1 Sep 1993 14:41:55 +0100 Received: from pippin.york.ac.uk by tower.york.ac.uk via SMTP (920330.SGI/920502.SGI) for @leeman.york.ac.uk:pine-info@cac.washington.edu id AA25954; Wed, 1 Sep 93 14:45:08 +0100 Date: Wed, 1 Sep 93 14:45:08 +0000 From: Mike Brudenell To: Pine Info Subject: Re: Pine 3.85 Message-Id: In-Reply-To: Your message of Wed, 1 Sep 1993 12:03:01 +0100 (BST) Content-Type: TEXT/plain; charset=US-ASCII Status: RO X-Status: I, too, would DEARLY like to know this, as I have documentation, User Guides, and a course to write by the last week of September! Mike B-} > Any update on the release date? > > We've decided to go with pine as our primary unix > mailer this year (Starting october). Should we be > workign with 3.07, or do we wait? :) > > 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. From owner-pine-info@cac.washington.edu Wed Sep 1 08:22:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23937; Wed, 1 Sep 93 08:22:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05538; Wed, 1 Sep 93 08:07:46 -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 AA05532; Wed, 1 Sep 93 08:07:44 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21412; Wed, 1 Sep 93 08:07:39 -0700 Date: Wed, 1 Sep 1993 08:06:54 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.85 To: "D.K.Brownlee" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: RO X-Status: We are getting very close... ;) |\ | |\/| 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, 1 Sep 1993, D.K.Brownlee wrote: > Any update on the release date? > > We've decided to go with pine as our primary unix mailer this year > (Starting october). Should we be workign with 3.07, or do we wait? :) > > 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. > > > From owner-pine-info@cac.washington.edu Wed Sep 1 08:33:34 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24356; Wed, 1 Sep 93 08:33:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07661; Wed, 1 Sep 93 08:21:04 -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 AA07639; Wed, 1 Sep 93 08:21:00 -0700 Received: by cc.lut.fi (5.65c/IDA-1.4.4/Kim-2.2) id AA22773; Wed, 1 Sep 1993 18:20:50 +0300 Date: Wed, 1 Sep 1993 18:20:50 +0300 From: Hannu Martikka Message-Id: <199309011520.AA22773@cc.lut.fi> To: Pine Info Subject: Re: Pine 3.85 In-Reply-To: ; from Mike Brudenell on 1 September 93 14:45:08 +0000 References: Mailer: VM 5.35 (beta) / GNU Emacs 19.19.2 Reply-To: Hannu Martikka Organization: Lappeenranta University of Technology, Finland Status: RO X-Status: >>>>> "Mike" == Mike Brudenell writes: Mike> I, too, would DEARLY like to know this, as I have documentation, Mike> User Guides, and a course to write by the last week of September! > Any update on the release date? > > We've decided to go with pine as our primary unix > mailer this year (Starting october). Should we be > workign with 3.07, or do we wait? :) We too have decided to go with pine on our Univ. Question is the same... should we wait or use 3.07 and 3.84 (pc-pine)? -- 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 Wed Sep 1 08:44:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24623; Wed, 1 Sep 93 08:44:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05938; Wed, 1 Sep 93 08:31:17 -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 AA05932; Wed, 1 Sep 93 08:31:15 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22104; Wed, 1 Sep 93 08:31:00 -0700 Date: Wed, 1 Sep 1993 08:24:18 -0700 (PDT) From: David L Miller Subject: Re: Additional feature for novices To: Alan Ward Cc: Virtual Dave Lankes , Alan Ward , Mike Roch , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Wed, 1 Sep 1993, Alan Ward wrote: > On Tue, 31 Aug 1993, Virtual Dave Lankes wrote: > > > Also, having been a victim of NeXTMail that already does this, it creates > > nightmares for working in a distributed environment. If you are used to > > IMAP clients, moving from one computer to another, or even shared mail > > between accouts this is the worst thing possible. You end up with the old > > POP dilema of messages and mail on twenty computers all over the place. One of > > the features of PINE I love is the use of the Post Office as inbox rather > > than displacing mail. > > I don't know the technical problems but I think IMAP should manage mail > folders not just the inbox. I am just as likely to want access to the > mail message I sent in reply as the previous mail message I received. > Yes, IMAP can manage mail folders. PC-pine currently supports remote mail folders and Unix Pine 3.85 will also have remote folder support. Stay tuned for more 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 From owner-pine-info@cac.washington.edu Wed Sep 1 08:47:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24844; Wed, 1 Sep 93 08:47:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06004; Wed, 1 Sep 93 08:34:40 -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 AA05998; Wed, 1 Sep 93 08:34:38 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22317; Wed, 1 Sep 93 08:34:35 -0700 Date: Wed, 1 Sep 1993 08:32:35 -0700 (PDT) From: David L Miller Subject: Re: Just another suggestion To: "Jason R. Thorpe" Cc: "James D. Gillmore" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: We are planning to implement a "bounce" command in a future release of pine. It will not be available in 3.85, but will be there in a later 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 Tue, 31 Aug 1993, Jason R. Thorpe wrote: > On Tue, 31 Aug 1993, James D. Gillmore wrote: > > > I would like to suggest that in some future release a mechanism be in > > place that allows mail bounced for bad address (user unknown, host > > unknown) to be resent with the corrected information. Many times it is a > > fat fingered typo and up to now I tell the users to save the message as a > > file edit off the mail stuff and then read the file into a new pine session. > > Or perhaps, someone has a better idea? I am open to suggestions to a > > better way > > I just forward it to the correct address and hack out all the > unnecessaries, like the old mail stuff, right there (as well as the (fwd) > in the header...) > > Later... > > /***************************************************************************** > Jason R. Thorpe - OSU Computer Science Support Staff > Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu > *****************************************************************************/ > > > From owner-pine-info@cac.washington.edu Wed Sep 1 09:30:44 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26019; Wed, 1 Sep 93 09:30:44 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07971; Wed, 1 Sep 93 09:20:46 -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 AA07965; Wed, 1 Sep 93 09:20:44 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA22367; Wed, 1 Sep 93 12:20:41 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA12608; Wed, 1 Sep 93 10:21:21 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: Wed, 1 Sep 1993 10:14:13 -0600 (MDT) From: "Jeffrey M. Wolff" Subject: PINE Questions To: pine-info@cac.washington.edu In-Reply-To: <199309011520.AA22773@cc.lut.fi> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Please forgive the ignorance of these questions. I am new user of PINE (previously using ELM) and I have not been able to find a decent technical reference manual anywhere. Here are my questions: 1) How do I prevent PINE from creating ".pine-debug*" files in my home directory? 2) How do I prevent PINE from saving my sent-mail (limited disk space)? 3) Is there a way for PINE to automatically launch if there is mail in my inbox (equivalent to "elm -z" command)? 4) We are using PINE 3.05. Is this the latest version? 5) In my To and or From fields, the full name is coming in with quotation marks around it. How can I remove them? 6) When I Index my mail, the To field is e-mail address. Is there a way for me to see the person's full name (ala ELM)? I appreciate any answers that anyway can provide. -- Jeffrey M. Wolff | "In my mind....I'm already gone!" jwolff@nyx.cs.du.edu | - Kramer From owner-pine-info@cac.washington.edu Wed Sep 1 09:56:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26744; Wed, 1 Sep 93 09:56:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07273; Wed, 1 Sep 93 09:49:10 -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 AA07267; Wed, 1 Sep 93 09:49:09 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25625; Wed, 1 Sep 93 09:49:05 -0700 Date: Wed, 1 Sep 1993 09:36:36 -0700 (PDT) From: David L Miller Subject: Re: PINE Questions To: "Jeffrey M. Wolff" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: See my comments below. |\ | |\/| 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, 1 Sep 1993, Jeffrey M. Wolff wrote: > Please forgive the ignorance of these questions. I am new user of PINE > (previously using ELM) and I have not been able to find a decent technical > reference manual anywhere. > Have you looked at doc/tech-notes.* in the pine distribution? > Here are my questions: > > 1) How do I prevent PINE from creating ".pine-debug*" files in my home > directory? > To prevent the files from being created, remove the -DDEBUG flag from the pine/makefile.xxx and re-compile. If just having them empty is enough, use "pine -d 0". > 2) How do I prevent PINE from saving my sent-mail (limited disk space)? > Set default-fcc="" in your .pinerc. > 3) Is there a way for PINE to automatically launch if there is mail in my > inbox (equivalent to "elm -z" command)? > Quoted from a previous answer by Terry Gray: This feature is not built into Pine, but it is trivial to simulate it with a shell script. For example, you could create a script called "pinez" containing: -------------- #!/bin/sh if test -s /usr/spool/mail/xxx ;then pine ;else echo No mail ;fi -------------- where "xxx" is your user name. Then put "pinez" into your .cshrc instead of "elm -z" -teg > 4) We are using PINE 3.05. Is this the latest version? > The current distribution is Pine 3.07, but Pine 3.85 should be out real soon. > 5) In my To and or From fields, the full name is coming in with quotation > marks around it. How can I remove them? > The quotes are necessary because of some character(s) that are invalid in the fullname without quotes. > 6) When I Index my mail, the To field is e-mail address. Is there a way > for me to see the person's full name (ala ELM)? > I am not sure what ELM does, but Pine provides the best information it can with the available information. i.e. it will use the full name in the index if it is given. > I appreciate any answers that anyway can provide. > > -- > Jeffrey M. Wolff | "In my mind....I'm already gone!" > jwolff@nyx.cs.du.edu | - Kramer > > > > From owner-pine-info@cac.washington.edu Wed Sep 1 12:23:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02731; Wed, 1 Sep 93 12:23:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09058; Wed, 1 Sep 93 12:09:24 -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 AA09052; Wed, 1 Sep 93 12:09:18 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AB15641; Wed, 1 Sep 93 15:09:12 -0400 Received: from verifone.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 150748.14448; Wed, 1 Sep 1993 15:07:48 EDT Received: by verifone.com with UUCP/PMDF (DECUS UUCP); Wed, 1 Sep 1993 08:53:41 -1000 Received: from verifone.com by verifone.com (PMDF V4.2-11 #2386) id <01H2FF1H29ZG928ELG@verifone.com>; Wed, 1 Sep 1993 08:53:31 -1000 Date: Wed, 01 Sep 1993 08:53:31 -1000 From: "James H. Thompson - HNL" Subject: Auto Filing of read mail To: pine-info@cac.washington.edu Message-Id: <01H2FF1H29ZI928ELG@verifone.com> Organization: VeriFone X-Ps-Qualifiers: /FONT=Courier-Bold/LINES=66/LEFT_MARGIN=36/CALCULATE/TOP_MARGIN=36/BOTTOM_MARGIN=36 X-Envelope-To: cac.washington.edu!pine-info X-Vms-To: IN%"pine-info@cac.washington.edu" X-Vms-Cc: JIMMY_T Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT I can't imagine using a system that didn't automatically file the mail I've read out of the inbox. When I want to review unread mail, I don't want the folder cluttered with messages I've already read. The system I use now, auto files read messages into a read folder, but also leaves them in the newmail/inbox folder until you select a new folder or exit. Jim +------------------------------------+--------------------------------------+ | James H. Thompson | jimmy_t@verifone.com (Internet) | | VeriFone Inc. | uunet!verifone!jimmy_t (UUCP) | | 100 Kahelu Avenue | 808-623-2911 (Phone) | | Mililani, HI 96789 | 808-625-3201 (FAX) | +------------------------------------+--------------------------------------+ From owner-pine-info@cac.washington.edu Thu Sep 2 08:32:26 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23952; Thu, 2 Sep 93 08:32:26 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13709; Thu, 2 Sep 93 08:08:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from umd5.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13703; Thu, 2 Sep 93 08:08:44 -0700 Received: from yorick.umd.edu by umd5.umd.edu id ; Thu, 2 Sep 93 11:08:40 -0400 Received: by yorick.umd.edu id ; Thu, 2 Sep 93 11:08:39 -0400 Date: Thu, 2 Sep 1993 11:06:06 -0400 (EDT) From: LoUIs laRrY Reply-To: LoUIs laRrY Subject: convert mh mail to pine To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I've been using mh, now I want to use pine to organize my mail. Is there any way to convert my old mh mail files so it goes to pine folder? So I can use pine to accessed it? ----------------------------------- | Louis Larry ,,, | | louisl@umd5.umd.edu ( o o ) | -----------------------ooO-(_)-Ooo- From owner-pine-info@cac.washington.edu Thu Sep 2 09:21:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25647; Thu, 2 Sep 93 09:21:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20623; Thu, 2 Sep 93 09:05:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nic.cic.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20617; Thu, 2 Sep 93 09:05:42 -0700 Received: by nic.cic.net (4.1/SMI-4.1) id AA17568; Thu, 2 Sep 93 12:05:41 EDT Date: Thu, 2 Sep 1993 12:01:14 -0400 (EDT) From: Paul Holbrook Reply-To: Paul Holbrook Subject: compressed mail folders wanted ... To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Speaking as a system adminstrator who's always looking for more free disk space, it would be wonderful if Pine could deal with compressed mail folders. The idea is that you could have a cron job that would go around and compress old mail folders (say those not accessed in the last week). Pine would have to be smart enough to recogize the folders even with the compression suffix on the end, and then launch the uncompress program when the user tried to open the folder. This would result in a hit the first time you opened a folder you hadn't used in a while, but some folders are infrequently accessed. Consider the 'sent-mail' folders. I once tried to look at the folder opening code to see how hard this would be, and it looked like the main hassle would be the fact that instead of being named 'sent-mail', the folder name might be something like 'sent-mail.gz'. Clearly, you'd want to show the user the 'sent-mail' name and not the 'gz' (or 'Z') suffix. J. Paul Holbrook CICNet Technical Services Manager holbrook@cic.net (313) 998-7680 From owner-pine-info@cac.washington.edu Thu Sep 2 09:40:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26387; Thu, 2 Sep 93 09:40:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21143; Thu, 2 Sep 93 09:30:05 -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 AA21135; Thu, 2 Sep 93 09:30:03 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03610; Thu, 2 Sep 93 09:29:59 -0700 Date: Thu, 2 Sep 1993 09:27:59 -0700 (PDT) From: David L Miller Subject: Re: compressed mail folders wanted ... To: Paul Holbrook Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII That is a possibility for 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 Thu, 2 Sep 1993, Paul Holbrook wrote: > Speaking as a system adminstrator who's always looking for more free disk > space, it would be wonderful if Pine could deal with compressed mail > folders. The idea is that you could have a cron job that would go around > and compress old mail folders (say those not accessed in the last week). > Pine would have to be smart enough to recogize the folders even with the > compression suffix on the end, and then launch the uncompress program when > the user tried to open the folder. > > This would result in a hit the first time you opened a folder you hadn't > used in a while, but some folders are infrequently accessed. Consider the > 'sent-mail' folders. > > I once tried to look at the folder opening code to see how hard this > would be, and it looked like the main hassle would be the fact that > instead of being named 'sent-mail', the folder name might be something > like 'sent-mail.gz'. Clearly, you'd want to show the user the 'sent-mail' > name and not the 'gz' (or 'Z') suffix. > > J. Paul Holbrook > CICNet Technical Services Manager > holbrook@cic.net (313) 998-7680 > > > > > > > From owner-pine-info@cac.washington.edu Thu Sep 2 10:00:03 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26794; Thu, 2 Sep 93 10:00:03 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14160; Thu, 2 Sep 93 09:43:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from julian.uwo.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14154; Thu, 2 Sep 93 09:43:49 -0700 Received: by julian.uwo.ca id AA09212; Thu, 2 Sep 93 12:43:38 -0400 Date: Thu, 2 Sep 1993 12:40:13 -0400 (EDT) From: Mike Cote Subject: Re: convert mh mail to pine To: LoUIs laRrY Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 2 Sep 1993, LoUIs laRrY wrote: > I've been using mh, now I want to use pine to organize my mail. > Is there any way to convert my old mh mail files so it goes to > pine folder? So I can use pine to accessed it? > I ran into this recently. In the MH distribution there is a script called packmbox.sh. Here it is.... ---------- #! /bin/sh # packmbox - pack an MH folder back into a UUCP-style mbox # @(#)$Id: packmbox.sh,v 1.16 1992/02/14 17:05:31 jromine Exp $ # # Defaults: # `+folder' defaults to current folder # `msgs' defaults to all # # Context: # Current-Folder # # for simplicity (and speed) we don't parse command-line args (much) case $#/$1 in 1/-h*) echo "syntax: packmbox [+folder] [msgs] [-help]" 1>&2; exit 0;; esac format="%(msg) From \ %<{return-path}%(putstr)%|\ %<(nonnull(mbox{from}))%(putstr)%|nobody%>@\ %<(nonnull(host{from}))%(putstr)%|nowhere%>%> \ %(day{date}) %(month{date}) %2(mday{date}) \ %02(hour{date}):%02(min{date}):%02(sec{date}) \ %(void(year{date}))%<(gt 100)%4(putnum)%|19%02(putnum)%>" trap 'rm -f /tmp/packm$$; exit 1' 1 2 3 15 scan -noclear -noheader -noreverse -width 256 \ -format "${format}" $* >/tmp/packm$$ # tricky -- you must do this "cd" after scan has updated the context cd `mhpath` exec /' < $m echo "" done exit ------------ ----------- Mike Cote Computing and Communications Services University of Western Ontario Phone: (519) 661-2151, X 6048 London, Ontario Canada From owner-pine-info@cac.washington.edu Thu Sep 2 10:58:12 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28441; Thu, 2 Sep 93 10:58:12 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14448; Thu, 2 Sep 93 10:39:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14442; Thu, 2 Sep 93 10:39:33 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA04104; Thu, 2 Sep 93 10:37:04 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA26931; Thu, 2 Sep 93 10:42:16 -0700 Date: Thu, 2 Sep 1993 10:32:48 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: compressed mail folders wanted ... To: Paul Holbrook Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 2 Sep 1993, Paul Holbrook wrote: > Speaking as a system adminstrator who's always looking for more free disk > space, it would be wonderful if Pine could deal with compressed mail > folders. The idea is that you could have a cron job that would go around > and compress old mail folders (say those not accessed in the last week). > Pine would have to be smart enough to recogize the folders even with the > compression suffix on the end, and then launch the uncompress program when > the user tried to open the folder. I agree this would be cool...but... > > This would result in a hit the first time you opened a folder you hadn't > used in a while, but some folders are infrequently accessed. Consider the > 'sent-mail' folders. Ok...the sent mail folder...accessed EVERY time the user sends mail...not for reading, but writing...your cron job would (or should) never compress this one... > I once tried to look at the folder opening code to see how hard this > would be, and it looked like the main hassle would be the fact that > instead of being named 'sent-mail', the folder name might be something > like 'sent-mail.gz'. Clearly, you'd want to show the user the 'sent-mail' > name and not the 'gz' (or 'Z') suffix. If pine knew (say, by hardcoding to use compress {.Z} or gzip {.gz}) which compression method was to be used, it could filter out the .suffix...that wouldn't be too tuff...It could keep an internal list of which folders where compressed, etc (Ok, maybe not trivial, but not impossible)...and when they needed to be read, a zcat or gzcat could be done and piped right into pine without actually uncompressing the file...However, the hitch would come when you needed to write to the file...Tacking a message onto a LARGE folder could take a LONG time (depending on your system, I guess). I agree (becuase I'm a sysadmin who has disk space problems, too) that compressed mail folders would be an added bonus to what I consider the best mail software around (besides NeXTMail, of course), however, I think that it would probably be more trouble than it's worth from coding, system resources, and actual processing time standpoints... Later... /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Thu Sep 2 15:14:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06033; Thu, 2 Sep 93 15:14:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26495; Thu, 2 Sep 93 15:06:35 -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 AA26489; Thu, 2 Sep 93 15:06:33 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00625; Thu, 2 Sep 93 15:06:27 -0700 Date: Thu, 2 Sep 1993 15:06:17 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: inbox folder To: bob ellsworth s Cc: pine-info@cac.washington.edu, ron craig F In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Saving to the inbox is not permitted. The messages you get when this is attempted will be cleaned up in a future version. |\ | |\/| 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, 31 Aug 1993, bob ellsworth s wrote: > hi : we have observed that "pine" will not move a message from a generic > folder to the "inbox" folder. when we attempt this, pine says the "message > is saved and marked for deletion" but the message never shows up in "inbox". > > can anyone on the list comment on this. (we are currently running pine 3.05) > > > From owner-pine-info@cac.washington.edu Thu Sep 2 16:29:17 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07876; Thu, 2 Sep 93 16:29:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27572; Thu, 2 Sep 93 16:16:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27566; Thu, 2 Sep 93 16:16:39 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2I8TASD400003DE@VENUS.RESNTL.BHP.COM.AU>; Fri, 3 Sep 1993 09:15:15 GMT Date: Fri, 03 Sep 1993 09:01:44 +1000 (EST) From: Steve Woodyatt Subject: "filter" program for Pine To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Is there thought for including a "filter" program with Pine (similar to that which is supplied with elm), so that mail from specified sources or groups can be automatically foldered/handled/re-directed etc? My reason for wanting this is simple: the sheer volume of traffic generated by the pine-info mailing list is swamping my inbox!!!! I'll wait to see the replies to this, but then I must seriously consider unsubscribing to this list........ which is a shame because it is useful :-) Thanks Steve -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ BHP Research - Newcastle Laboratories, Australia./ / / \ Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / Internet: steve@resntl.bhp.com.au \ / / / ------------------------------------------------------------------\/\/\/-- From owner-pine-info@cac.washington.edu Thu Sep 2 16:56:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08670; Thu, 2 Sep 93 16:56:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27995; Thu, 2 Sep 93 16:42: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 AA27989; Thu, 2 Sep 93 16:42:54 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02736; Thu, 2 Sep 93 16:42:23 -0700 Date: Thu, 2 Sep 1993 16:40:43 -0700 (PDT) From: David L Miller Subject: Re: "filter" program for Pine To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We actually use the filter program from elm around here ;) |\ | |\/| 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, 3 Sep 1993, Steve Woodyatt wrote: > > Is there thought for including a "filter" program with Pine (similar to that > which is supplied with elm), so that mail from specified sources or groups > can be automatically foldered/handled/re-directed etc? > > My reason for wanting this is simple: the sheer volume of traffic > generated by the pine-info mailing list is swamping my inbox!!!! > > I'll wait to see the replies to this, but then I must seriously > consider unsubscribing to this list........ which is a shame because > it is useful :-) > > Thanks > > Steve > > -------------------------------------------------------------------/\/\--- > Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ > BHP Research - Newcastle Laboratories, Australia./ / / \ > Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ > Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / > Internet: steve@resntl.bhp.com.au \ / / / > ------------------------------------------------------------------\/\/\/-- > > From owner-pine-info@cac.washington.edu Thu Sep 2 17:12:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09587; Thu, 2 Sep 93 17:12:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28131; Thu, 2 Sep 93 16:58:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from optima.CS.Arizona.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28125; Thu, 2 Sep 93 16:58:18 -0700 Received: from wolf.CS.Arizona.EDU by optima.CS.Arizona.EDU (5.65c/15) via SMTP id AA21414; Thu, 2 Sep 1993 16:58:17 MST Received: by wolf.cs.arizona.edu; Thu, 2 Sep 1993 16:58:16 MST Date: Thu, 2 Sep 1993 16:57:04 -0700 (MST) From: Jim Davis Reply-To: Jim Davis Subject: Re: "filter" program for Pine To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 3 Sep 1993, Steve Woodyatt wrote: > > Is there thought for including a "filter" program with Pine (similar to that > which is supplied with elm), so that mail from specified sources or groups > can be automatically foldered/handled/re-directed etc? If you're on a UNIX system, then either 'deliver' or 'procmail' should do what you want. I use deliver with pine to have mail automatically stuffed into the right folders -- including mail from pine-info -- and it is very helpful. Ask archie for an archive site near you. -- Jim Davis | "Another casualty of the seduction of art." jdavis@cs.arizona.edu | -- Hobbes From owner-pine-info@cac.washington.edu Thu Sep 2 17:58:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10950; Thu, 2 Sep 93 17:58:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28780; Thu, 2 Sep 93 17:42: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 AA28774; Thu, 2 Sep 93 17:42:51 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17846; Thu, 2 Sep 93 17:42:33 -0700 Date: Thu, 2 Sep 1993 17:39:44 -0700 (PDT) From: Steve Hubert Subject: Re: "filter" program for Pine To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It looked to me like David's response could be misinterpreted so that you might think he was kidding (because of the wink). He wasn't kidding. The filter program that comes with elm can certainly be used. The delivery of mail into the various folders has nothing to do with the program you use to read the mail. I personally use procmail to filter my incoming mail. Any filter you come across may be used. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Thu, 2 Sep 1993, David L Miller wrote: > > We actually use the filter program from elm around here ;) From owner-pine-info@cac.washington.edu Thu Sep 2 18:21:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11565; Thu, 2 Sep 93 18:21:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29146; Thu, 2 Sep 93 18:13:54 -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 AA29140; Thu, 2 Sep 93 18:13:52 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA03047; Thu, 2 Sep 93 20:13:14 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA04198; Fri, 3 Sep 93 09:03:48 +0800 Date: Fri, 3 Sep 1993 08:58:20 +0800 (TPE) From: Ed Greshko Subject: Re: "filter" program for Pine To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 3 Sep 1993, Steve Woodyatt wrote: > > Is there thought for including a "filter" program with Pine (similar to that > which is supplied with elm), so that mail from specified sources or groups > can be automatically foldered/handled/re-directed etc? IMHO, why not simply use the filter program supplied with elm? The filter program is NOT only for elm. It is generic. As a matter of fact...that is what I'm doing. Using the elm filter program and composing with pine. > My reason for wanting this is simple: the sheer volume of traffic > generated by the pine-info mailing list is swamping my inbox!!!! > I'll wait to see the replies to this, but then I must seriously > consider unsubscribing to this list........ which is a shame because > it is useful :-) I wouldn't unsubscribe based on this small item. While pine is lacking in some features it is much better than elm is when including MIME attachments. (Read, user friendly.) So, just grab the filter from the elm source and use it. Hope this helps... 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 Thu Sep 2 18:35:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11834; Thu, 2 Sep 93 18:35:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29202; Thu, 2 Sep 93 18:21:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29196; Thu, 2 Sep 93 18:21:08 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2ID4VPHCW0003TD@VENUS.RESNTL.BHP.COM.AU>; Fri, 3 Sep 1993 11:19:08 GMT Date: Fri, 03 Sep 1993 11:18:24 +1000 (EST) From: Steve Woodyatt Subject: RE: "filter" program for Pine In-Reply-To: To: Ed Greshko Cc: Steve Woodyatt , pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Fri, 3 Sep 1993, Ed Greshko wrote: > I wouldn't unsubscribe based on this small item. While pine > is lacking in some features it is much better than elm is when including > MIME attachments. (Read, user friendly.) > Agreed Ed. I wasn't intending to discontine use of Pine - just maybe unsubscribe from the list! Now that I can use another filter program, I don't even have to do that.... Thanks to all who replied. Steve. -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ BHP Research - Newcastle Laboratories, Australia./ / / \ Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / Internet: steve@resntl.bhp.com.au \ / / / ------------------------------------------------------------------\/\/\/-- From owner-pine-info@cac.washington.edu Thu Sep 2 19:50:58 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12788; Thu, 2 Sep 93 19:50:58 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17183; Thu, 2 Sep 93 19:43:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sulu.biostat.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17177; Thu, 2 Sep 93 19:43:38 -0700 Received: by sulu.biostat.washington.edu (5.64/UW-NDC Revision: 2.21 ) id AA27585; Thu, 2 Sep 93 19:42:58 -0700 From: Nancy McGough Message-Id: <9309030242.AA27585@sulu.biostat.washington.edu> Subject: comp.mail.pine (WAS: "filter" program for Pine) To: pine-info@cac.washington.edu Date: Thu, 2 Sep 93 19:42:58 PDT In-Reply-To: ; from "Steve Woodyatt" at Sep 3, 93 9:01 am Reply-To: Nancy McGough X-Mailer: ELM [version 2.3 PL11] How about linking the pine-info mailing list to a newsgroup called comp.mail.pine? That way people can choose whether to participate via mail or news. Also, it'll be much easier for Pine users to find out about the discussion group -- currently it's pretty much just word of mouth. Nancy Quoting Steve Woodyatt, > My reason for wanting this is simple: the sheer volume of traffic > generated by the pine-info mailing list is swamping my inbox!!!! > > I'll wait to see the replies to this, but then I must seriously > consider unsubscribing to this list........ which is a shame because > it is useful :-) From owner-pine-info@cac.washington.edu Thu Sep 2 20:10:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13050; Thu, 2 Sep 93 20:10:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29961; Thu, 2 Sep 93 19:59:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from merlin.resmel.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29955; Thu, 2 Sep 93 19:59:42 -0700 Received: from [134.18.1.150] (gryphon.resmel.bhp.com.au) by merlin.resmel.bhp.com.au with SMTP id AA05460 (5.65c/IDA-1.4.4 for ); Fri, 3 Sep 1993 12:59:37 +1000 Message-Id: <199309030259.AA05460@merlin.resmel.bhp.com.au> X-Sender: ianh@monster.resmel.bhp.com.au Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 3 Sep 1993 12:59:38 +1000 To: pine-info@cac.washington.edu From: ianh@resmel.bhp.com.au (Ian Hoyle) Subject: Re: comp.mail.pine (WAS: "filter" program for Pine) >How about linking the pine-info mailing list to a newsgroup called >comp.mail.pine? That way people can choose whether to participate >via mail or news. Also, it'll be much easier for Pine users to >find out about the discussion group -- currently it's pretty much >just word of mouth. I suppose this means Nancy that you'll be proposing a call for votes etc etc for comp.mail.pine, generating discussion in news.groups etc etc :-) ian --- : Ian Hoyle, Senior Research Scientist /\/\ : BHP Research / / /\ : 245 Wellington Rd, Mulgrave, 3170, AUSTRALIA / / / \ : Phone +61-3-560-7066 / / / /\ \ : E-mail ianh@resmel.bhp.com.au \ \/ / / / : "Now I've got the bead on you with MY disintegrating gun. \ / / / : And when it disintegrates, it disintegrates. (pulls trigger) \/\/\/ : Well, what you do know, it disintegrated." : -- Duck Dodgers in the 24th and a half century From owner-pine-info@cac.washington.edu Thu Sep 2 21:29:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14013; Thu, 2 Sep 93 21:29:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00491; Thu, 2 Sep 93 21:18: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 AA00481; Thu, 2 Sep 93 21:18:27 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07614; Thu, 2 Sep 93 21:18:24 -0700 Date: Thu, 2 Sep 1993 21:16:54 -0700 (PDT) From: David L Miller Subject: Re: comp.mail.pine (WAS: "filter" program for Pine) To: Nancy McGough Cc: pine-info@cac.washington.edu In-Reply-To: <9309030242.AA27585@sulu.biostat.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Talk about overflowing inboxes!!! |\ | |\/| 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, 2 Sep 1993, Nancy McGough wrote: > How about linking the pine-info mailing list to a newsgroup called > comp.mail.pine? That way people can choose whether to participate > via mail or news. Also, it'll be much easier for Pine users to > find out about the discussion group -- currently it's pretty much > just word of mouth. > > Nancy > > > Quoting Steve Woodyatt, > > My reason for wanting this is simple: the sheer volume of traffic > > generated by the pine-info mailing list is swamping my inbox!!!! > > > > I'll wait to see the replies to this, but then I must seriously > > consider unsubscribing to this list........ which is a shame because > > it is useful :-) > From owner-pine-info@cac.washington.edu Fri Sep 3 08:21:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24546; Fri, 3 Sep 93 08:21:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04889; Fri, 3 Sep 93 08:10:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from helium.GAS.UUG.Arizona.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04883; Fri, 3 Sep 93 08:10:10 -0700 Received: by helium.GAS.uug.Arizona.EDU (4.1/Helium-MX-1.4) id AA08291; Fri, 3 Sep 93 08:10:09 MST Date: Fri, 3 Sep 1993 08:09:07 -0700 (MST) From: Mari J Stoddard Subject: Re: comp.mail.pine (WAS: "filter" program for Pine) To: Nancy McGough Cc: pine-info@cac.washington.edu In-Reply-To: <9309030242.AA27585@sulu.biostat.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It might be simpler to echo to bit.listserv.pine-info -- but in any case, a Usenet group would be great! Mari -- Mari J. Stoddard stoddard@gas.uug.arizona.edu University of Arizona Health Sciences Library in Tucson On Thu, 2 Sep 1993, Nancy McGough wrote: > How about linking the pine-info mailing list to a newsgroup called > comp.mail.pine? That way people can choose whether to participate > via mail or news. Also, it'll be much easier for Pine users to > find out about the discussion group -- currently it's pretty much > just word of mouth. > > Nancy > > > Quoting Steve Woodyatt, > > My reason for wanting this is simple: the sheer volume of traffic > > generated by the pine-info mailing list is swamping my inbox!!!! > > > > I'll wait to see the replies to this, but then I must seriously > > consider unsubscribing to this list........ which is a shame because > > it is useful :-) From owner-pine-info@cac.washington.edu Fri Sep 3 08:33:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24993; Fri, 3 Sep 93 08:33:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05080; Fri, 3 Sep 93 08:24:38 -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 AA05074; Fri, 3 Sep 93 08:24:37 -0700 Received: by stein1.u.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02125; Fri, 3 Sep 93 08:24:36 -0700 X-Sender: mramey@stein1.u.washington.edu Date: Fri, 3 Sep 1993 08:20:04 -0700 (PDT) From: Mike Ramey Subject: Re: "filter" program for Pine To: Steve Hubert Cc: Steve Woodyatt , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii How are these "mail-filter" programs used? Does it involve the .forward file? Can I use a mail-filter and the 'vacation' program at the same time? Can I use a shell script as a mail-filter/redirector? Where can I find information on use of the .forward file? -mr On Thu, 2 Sep 1993, Steve Hubert wrote: > The filter program that comes with elm can certainly be used. The > delivery of mail into the various folders has nothing to do with the > program you use to read the mail. I personally use procmail to filter my > incoming mail. Any filter you come across may be used. > --Steve Hubert > --Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Fri Sep 3 09:01:51 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25968; Fri, 3 Sep 93 09:01:51 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05544; Fri, 3 Sep 93 08:50:33 -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 AA05538; Fri, 3 Sep 93 08:50:29 -0700 Received: from black.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <27121-133@ppsw2.cam.ac.uk>; Fri, 3 Sep 1993 16:49:55 +0100 Received: from quinag.csi.cam.ac.uk by black.csi.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <00978-0@black.csi.cam.ac.uk>; Fri, 3 Sep 1993 16:33:03 +0100 Date: Fri, 3 Sep 1993 16:28:02 BST From: Barry Landy Subject: Re: "Reply-to" 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 Other contributors to this discussion have missed a point: PC-PINE users ONLY have the customisation provided by PINE, and cannot trigger features of the MTA instead (this comment also applies to the discussion on filtering). In our case, we cannot use the currently provided features to produce the proper reply address since while we can get the domain right, we cannot put in a friendly name (eg, I want to have barry.landy@whatever). ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 On 26 Aug 1993, Terry Gray wrote: > Several folks have requested that Pine support a "Reply-to" header. > This is definitely on the list and will probably make it into Pine 4.0. > However, in some cases it seems to me that the problem people are trying > to solve can be addressed already via the "user-domain" variable in the > .pinerc... > > This variable, if set, specifies what will be on the right side of the "@" > sign in the "From: " field of outgoing messages (among other things). For > example, if you receive some of your mail at "joe@blah.cs.washington.edu" but > you want people to send to a generic address such as "joe@u.washington.edu" > this can be done by setting "user-domain=u.washington.edu". > > In PC-Pine you can also set the left side of the @ in the From: field via > the userid variable. But on Unix Pine, the account names on the machine > where mail is delivered and the machine where you run Pine must match. > (That limitation is why a reply-to would be handy in some cases.) > > -teg > > From owner-pine-info@cac.washington.edu Fri Sep 3 10:36:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28643; Fri, 3 Sep 93 10:36:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07072; Fri, 3 Sep 93 10:06:15 -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 AA07066; Fri, 3 Sep 93 10:06:13 -0700 Received: from jhunix2.hcf.jhu.edu ([128.220.2.232]) by jhunix.hcf.jhu.edu with SMTP id <72885-2>; Fri, 3 Sep 1993 13:05:44 -0400 Date: Fri, 3 Sep 1993 12:59:20 -0400 From: Andy Poling Subject: Re: "Reply-to" To: Barry Landy Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 3 Sep 1993, Barry Landy wrote: > Other contributors to this discussion have missed a point: PC-PINE users > ONLY have the customisation provided by PINE, and cannot trigger features > of the MTA instead (this comment also applies to the discussion on > filtering). > In our case, we cannot use the currently provided features to produce the > proper reply address since while we can get the domain right, we cannot > put in a friendly name (eg, I want to have barry.landy@whatever). No Barry, I think you're missing a point of functionality. If the MTA is not doing the "friendly name", then how the heck is it supposed to handle it when it comes back (say, in a reply)?! Don't worry - it's a common mistake to try to move MTA functionality into the MUA. Rewriting of user addresses is definitely a job for the MTA. It may be true that the MTA needs a better interface to the administration of this functionality, but that can hardly be blamed on PINE... Filtering and automated routing of certain messages to certain mailboxes/maildrops, on the other hand, might fit nicely into a doitall MUA like PINE. -Andy "a place for everything and everything in its place"... 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 Fri Sep 3 14:11:44 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04639; Fri, 3 Sep 93 14:11:44 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21771; Fri, 3 Sep 93 13:58:13 -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 AA21765; Fri, 3 Sep 93 13:58:11 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA27607; Fri, 3 Sep 93 16:58:03 -0400 Received: from verifone.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 165607.6776; Fri, 3 Sep 1993 16:56:07 EDT Received: by verifone.com with UUCP/PMDF (DECUS UUCP); Fri, 3 Sep 1993 10:48:42 -1000 Received: from verifone.com by verifone.com (PMDF V4.2-11 #2386) id <01H2IBP783469284ET@verifone.com>; Fri, 3 Sep 1993 10:48:23 -1000 Date: Fri, 03 Sep 1993 10:48:23 -1000 From: "James H. Thompson - HNL" Subject: zipped folders To: pine-info@cac.washington.edu Message-Id: <01H2IBP783489284ET@verifone.com> Organization: VeriFone X-Ps-Qualifiers: /FONT=Courier-Bold/LINES=66/LEFT_MARGIN=36/CALCULATE/TOP_MARGIN=36/BOTTOM_MARGIN=36 X-Envelope-To: cac.washington.edu!pine-info X-Vms-To: IN%"pine-info@cac.washington.edu" X-Vms-Cc: JIMMY_T Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > To: IN%"holbrook@cic.net" "Paul Holbrook" > CC: IN%"pine-info@cac.washington.edu" > Subj: RE: compressed mail folders wanted ... On Thu, 2 Sep 1993, Jason R. Thorpe wrote: > > On Thu, 2 Sep 1993, Paul Holbrook wrote: > > > > I once tried to look at the folder opening code to see how hard this > > would be, and it looked like the main hassle would be the fact that > > instead of being named 'sent-mail', the folder name might be something > > like 'sent-mail.gz'. Clearly, you'd want to show the user the 'sent-mail' > > name and not the 'gz' (or 'Z') suffix. > > If pine knew (say, by hardcoding to use compress {.Z} or gzip {.gz}) which > compression method was to be used, it could filter out the .suffix...that > wouldn't be too tuff...It could keep an internal list of which folders > where compressed, etc (Ok, maybe not trivial, but not impossible)...and when > they needed to be read, a zcat or gzcat could be done and piped right into > pine without actually uncompressing the file...However, the hitch would > come when you needed to write to the file...Tacking a message onto a LARGE > folder could take a LONG time (depending on your system, I guess). > Most archivers have an option to quickly add a new file to an existing archive without having to decompress and recompress the whole archive. So if you were willing to reconsolidate the files in an achive back into one file when you want to read it, you should be able to add a message to a compressed archive without a huge overhead. One approach would be to keep every message as a separate file in the archive. Then you could retrieve or add a single message with only the overhead for compressing/decompressing one message. Jim +------------------------------------+--------------------------------------+ | James H. Thompson | jimmy_t@verifone.com (Internet) | | VeriFone Inc. | uunet!verifone!jimmy_t (UUCP) | | 100 Kahelu Avenue | 808-623-2911 (Phone) | | Mililani, HI 96789 | 808-625-3201 (FAX) | +------------------------------------+--------------------------------------+ From owner-pine-info@cac.washington.edu Fri Sep 3 23:02:10 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12815; Fri, 3 Sep 93 23:02:10 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16476; Fri, 3 Sep 93 22:52:14 -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 AA16470; Fri, 3 Sep 93 22:52:12 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27832; Fri, 3 Sep 93 22:52:10 -0700 Date: Fri, 3 Sep 1993 22:37:30 -0700 (PDT) From: Steve Hubert Subject: Re: "filter" program for Pine To: Mike Ramey Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 3 Sep 1993, Mike Ramey wrote: > How are these "mail-filter" programs used? > Does it involve the .forward file? > Can I use a mail-filter and the 'vacation' program at the same time? > Can I use a shell script as a mail-filter/redirector? > Where can I find information on use of the .forward file? -mr If you receive your mail on a system where the Mail Transfer Agent is sendmail, then the .forward file is the typical place where you would place the mail-filter program. You can feed the incoming messages to any program you want. It could be a shell script that does multiple things. The .forward file can also have more than one address, so you could give the vacation program as one address and a filter as another. (I hardly ever use vacation programs because of their tendency to send embarrassing vacation announcements to mailing lists that don't care, though modern vacation programs are fairly safe.) I can't remember where you can read about the .forward file. Probably in the Sendmail Installation and Operations Guide. Here is my .forward file as an example. There are two "addresses" separated by a comma. You can also put them on two separate lines, but some sendmails have trouble with that in rare cases. Each of these "addresses" is actually a shell script invocation. Quotes around the whole thing (because there are embedded spaces), a pipe character at the start (to tell sendmail this is a program instead of an address), and then the shell script. Sendmail will call each script with the message as standard input. The programs will be run under your UID. Procmail is available on the net and this is just the way he suggests calling it. The #hubert is there to distinguish it from other user's procmail calls, so that your mail won't be eliminated as a duplicate by some sendmails. A simple procmail will usually look at the From's and To's and maybe the Subject lines and filter messages into different mailboxes based on those. The other "address" is just a simple script. Note that I could throw in a comma followed by hubert on the end if I wanted a regular delivery to go to me, similar to the way it is shown in the vacation manual page (note that that backslash they show in the vacation man page isn't actually necessary or useful). "|IFS=' ';exec /usr/local/bin/procmail -t #hubert", "|/u2/staff/hubert/bin/mail-dup hubert@kamba.cac.washington.edu" Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Sun Sep 5 23:20:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10895; Sun, 5 Sep 93 23:20:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01919; Sun, 5 Sep 93 23:05:48 -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 AA01913; Sun, 5 Sep 93 23:05:47 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00849; Sun, 5 Sep 93 23:05:41 -0700 Date: Sun, 5 Sep 1993 22:42:01 -0700 (PDT) From: Terry Gray Subject: Re: inbox folder To: bob ellsworth s Cc: pine-info@cac.washington.edu, ron craig F In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In Pine 3.05, the name "inbox" is not always interpreted as THE inbox... You can, however, save to the full pathname, e.g. /usr/spool/mail/gray, moreover, if you create a link such as: cd ~/mail ln -s /usr/spool/mail/gray inbox things should work as you'd expect. You can probably find the missing messages by doing a G(oto) ~/inbox RET. In 3.85, saving to "inbox" should uniformly mean THE inbox, in all name contexts, so you won't need the link to get the expected behavior. -teg On Thu, 2 Sep 1993, David L Miller wrote: > > Saving to the inbox is not permitted. The messages you get when this is > attempted will be cleaned up in a future version. > > |\ | |\/| 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, 31 Aug 1993, bob ellsworth s wrote: > > > hi : we have observed that "pine" will not move a message from a generic > > folder to the "inbox" folder. when we attempt this, pine says the "message > > is saved and marked for deletion" but the message never shows up in "inbox". > > > > can anyone on the list comment on this. (we are currently running pine 3.05) > > From owner-pine-info@cac.washington.edu Mon Sep 6 01:21:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12602; Mon, 6 Sep 93 01:21:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02831; Mon, 6 Sep 93 01:13:49 -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 AA02825; Mon, 6 Sep 93 01:13:46 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #87) id m0oZbho-00003HC; Mon, 6 Sep 93 09:13 BST Date: Mon, 6 Sep 1993 09:04:50 +0100 (BST) From: Philip Hazel Subject: Re: "Reply-to" To: Andy Poling Cc: Barry Landy , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > > Other contributors to this discussion have missed a point: PC-PINE users > > ONLY have the customisation provided by PINE, and cannot trigger features > > of the MTA instead (this comment also applies to the discussion on > > filtering). > > No Barry, I think you're missing a point of functionality. If the MTA is > not doing the "friendly name", then how the heck is it supposed to handle > it when it comes back (say, in a reply)?! Don't worry - it's a common > mistake to try to move MTA functionality into the MUA. > > Rewriting of user addresses is definitely a job for the MTA. It may be > true that the MTA needs a better interface to the administration of this > functionality, but that can hardly be blamed on PINE... However, it is usually trivial to arrange for MTAs to interpret friendly names on input -- e.g. in Unix you set up a suitable alias file, but on the other hand many MTAs do not provide straightforward ways of re-writing headers on outgoing mail. Furthermore, consider a system with a main mailer machine and lots of user workstations. The main machine can be set up to receive mail for "Philip.Hazel@central.something" and deliver it to "ph10@my.local.workstation". However, the workstations themselves may well just emit SMTP mail to anywhere. Therefore, it is in the workstations that you have to do header re-writing. It is much easier if the individual users can simply tailor their MUAs to do this job; otherwise there is a big workload on some poor system administrator, which is also the case if you insist that all outgoing mail go through a central machine. -- 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 Sep 6 07:00:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17350; Mon, 6 Sep 93 07:00:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04201; Mon, 6 Sep 93 06:40:18 -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 AA04195; Mon, 6 Sep 93 06:40:13 -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 <05200-0@ppsw2.cam.ac.uk>; Mon, 6 Sep 1993 14:40:07 +0100 Date: Mon, 6 Sep 1993 14:33:33 BST From: Barry.Landy@UCS.CAM.AC.UK Reply-To: Barry.Landy@UCS.CAM.AC.UK Subject: Re: "Reply-to" To: pine-info@cac.washington.edu Message-Id: k-0100000 Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > On Fri, 3 Sep 1993, Barry Landy wrote: > > Other contributors to this discussion have missed a point: PC-PINE users > > ONLY have the customisation provided by PINE, and cannot trigger features > > of the MTA instead (this comment also applies to the discussion on > > filtering). > > In our case, we cannot use the currently provided features to produce the > > proper reply address since while we can get the domain right, we cannot > > put in a friendly name (eg, I want to have barry.landy@whatever). > > No Barry, I think you're missing a point of functionality. If the MTA is > not doing the "friendly name", then how the heck is it supposed to handle > it when it comes back (say, in a reply)?! Don't worry - it's a common > mistake to try to move MTA functionality into the MUA. > > Rewriting of user addresses is definitely a job for the MTA. It may be > true that the MTA needs a better interface to the administration of this > functionality, but that can hardly be blamed on PINE... > > Filtering and automated routing of certain messages to certain > mailboxes/maildrops, on the other hand, might fit nicely into a doitall > MUA like PINE. > > -Andy > > "a place for everything and everything in its place"... > > 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 Again, you miss a point (and I think that the underlying message is that the mail world is a good deal more complicated than appears at first sight!). The friendly name I wish to specify is on the domain I am specifying, but this is NOT the system on which the IMAP PINE is accessing resides. We have a mail hub/switch system (identified by the domain) which takes a mailid, and redirects to a different domain and userid; eg barry.landy@ucs.cam.ac.uk is redirected to bl10@cus.cam.ac.uk cus.cam.ac.uk is the unix system I am calling with PINE. Now, I dont want my PINE users (or myself for that matter) to have to get into any arcane actions on the unix system; the whole point is that they are PC users for whom a unix based mailer is being made available in a PC like manner. From owner-pine-info@cac.washington.edu Mon Sep 6 06:55:08 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17331; Mon, 6 Sep 93 06:55:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17325; Mon, 6 Sep 93 06:55:02 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 06 Sep 93 15:41:14+0200 Date: 06 Sep 93 15:41:14+0200 From: Jacob Palme DSV Message-Id: <393732*jpalme@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" Subject: Pine and PMDF cannot talk quoted printable to each other A friend of mine, who uses an Mail Transfer Agent called PMDF, recently sent mail to me which purported to be in MIME format. Pine, however, claimed that the format was illegal quoted- printable and refused to show the text to me. Two comments on this: (a) Which is wrong? Pine or PMDF? The one which is not correct should be corrected. (b) It would be better if Pine showed the text to me, even if Pine thought it was illegal MIME syntax. Quoted Printable, after all, is meant to be somewhat readable also to those who do not have fancy character sets. From owner-pine-info@cac.washington.edu Mon Sep 6 07:37:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17772; Mon, 6 Sep 93 07:37:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04109; Mon, 6 Sep 93 07:25: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 AA04103; Mon, 6 Sep 93 07:25:49 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #87) id m0oZhVr-00003OC; Mon, 6 Sep 93 15:25 BST Date: Mon, 6 Sep 1993 15:16:44 +0100 (BST) From: Philip Hazel Subject: Re: "Reply-to" To: Barry.Landy@UCS.CAM.AC.UK Cc: pine-info@cac.washington.edu In-Reply-To: k-0100000 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > The friendly name I wish to specify is on the domain I am specifying, but this > is NOT the system on which the IMAP PINE is accessing resides. > We have a mail hub/switch system (identified by the domain) which takes a > mailid, and redirects to a different domain and userid; eg > barry.landy@ucs.cam.ac.uk is redirected to bl10@cus.cam.ac.uk > cus.cam.ac.uk is the unix system I am calling with PINE. > Now, I dont want my PINE users (or myself for that matter) to have to get into > any arcane actions on the unix system; the whole point is that they are PC users > for whom a unix based mailer is being made available in a PC like manner. [This is adding to the above, not replying to it.] Furthermore, in this example, it is NOT appropriate to configure the cus.cam.ac.uk system to accept mail addressed to ucs.cam.ac.uk, since not all users of cus.cam.ac.uk have that as their domain address. Different groups of users who have their final mailboxes on cus.cam.ac.uk may well have different "friendly" mail addresses, e.g. john.doe@some-college.cam.ac.uk jill.person@some-department.cam.ac.uk which are handled via the mail hub/switch. There are thousands of users of this system. Apart from the fact that the MTA on cus.cam.ac.uk (smail3) doesn't have a re-writing facility, the sheer administrative effort of maintaining lists of per-user friendly mail addresses so that each outgoing message could have its headers re-written is too great. Much easier to let each user tailor their own world. Philip -- 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 Sep 6 07:25:16 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17604; Mon, 6 Sep 93 07:25:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17598; Mon, 6 Sep 93 07:25:13 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 06 Sep 93 16:12:06+0200 Date: 06 Sep 93 16:12:06+0200 From: Jacob Palme DSV Message-Id: <393738*jpalme@su-kom.dsv.su.se> In-Reply-To: <9308310850.AA17692@mx1.cac.washington.edu> To: Pine-Info Email List , "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Mike Roch Subject: Additional feature for novices > Several correspondents have sought tools for managing overlarge mailboxes > in the mail spool. The problem is usually caused by novices who don't > appreciate that subscribing to lots of lists (and forgetting how to use > "unsubscribe"), mailing themselves binaries from gopher servers, or simlply > keeping al their mail together rather than filing it in folders has an > impact on other users (or the whole system). The solution to this, of course, would be an unsubscribe command in Pine, which would automatically cause the user to unsubscribe from a list. And also of course, a subscribe command. Such commands, however, requires a standard for how to subscribe and unsubscribe to lists. Some people in RARE are working on such a standard. From owner-pine-info@cac.washington.edu Mon Sep 6 12:52:07 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21087; Mon, 6 Sep 93 12:52:07 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05158; Mon, 6 Sep 93 12:42: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 AA05152; Mon, 6 Sep 93 12:42:29 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA11761; Mon, 6 Sep 93 12:42:24 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA23706; Mon, 6 Sep 93 12:42:16 -0700 Date: Mon, 6 Sep 1993 12:39:29 -0700 (PDT) From: Mark Crispin Subject: re: Pine and PMDF cannot talk quoted printable to each other To: Jacob Palme DSV Cc: pine-info@cac.washington.edu In-Reply-To: <393732*jpalme@su-kom.dsv.su.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Without sample data and information such as the Pine version number, it's impossible to figure out what the problem was. I'll defer to other members of the Pine team to answer your request about displaying the text without decoding. From owner-pine-info@cac.washington.edu Tue Sep 7 09:36:49 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08189; Tue, 7 Sep 93 09:36:49 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13258; Tue, 7 Sep 93 09:19:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from netcomsv.netcom.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13252; Tue, 7 Sep 93 09:19:41 -0700 Received: from wndrsvr.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1) id AA19755; Tue, 7 Sep 93 09:19:58 PDT Received: by wndrsvr (5.65/1.35) id AA24317; Tue, 7 Sep 93 08:26:19 -0700 From: andyb@wndrsvr.la.ca.us (Andy) Message-Id: <9309071526.AA24317@wndrsvr> Subject: Need volunteer to test pine3.84x on ISC 3.0 To: pine-info@cac.washington.edu Date: Tue, 7 Sep 1993 08:26:18 -0700 (PDT) X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 636 I've finished cleaning up the pine port to ISC 3.0, but I find that it gets bus errors in places that make no sense. Being as how I've had numerous panics due to faulty hardware, I have to make the assumption that certain system files were damaged, and are causing problems for numerous programs. (Seems like programs which use various tcp/ip calls.) Being as how I'm not ready to go through the restore process and won't be for quite some time, I thought maybe someone out there might want to give my port of pine a shot on their machine. We can start with a binary and see how that goes. Any volunteers? Thanks! - Andy From owner-pine-info@cac.washington.edu Tue Sep 7 10:06:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09065; Tue, 7 Sep 93 10:06:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13865; Tue, 7 Sep 93 09:57:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mento.oit.unc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13859; Tue, 7 Sep 93 09:57:05 -0700 Received: by mento.oit.unc.edu (NeXT-1.0 (From Sendmail 5.52)/TAS/11-16-88) id AA23155; Tue, 7 Sep 93 12:56:54 EDT Date: Tue, 7 Sep 1993 12:55:12 -0400 (EDT) From: Paul Jones Subject: Good Morning America and PICO and PINE To: Andy Cc: pine-info@cac.washington.edu In-Reply-To: <9309071526.AA24317@wndrsvr> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This morning's GMA featured a story on sending e-mail to the White House (in the G-WHIZZ section of the show). The mailer and editor used? Our heroes--PICO and PINE. Also featured was gopher (terminal window version). ============================================== Paul Jones Office FOR Information Technology University of North Carolina Chapel Hill, NC Paul_Jones@unc.edu Visualize Whirled Peas! From owner-pine-info@cac.washington.edu Wed Sep 8 10:10:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13111; Wed, 8 Sep 93 10:10:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29936; Wed, 8 Sep 93 09:58:55 -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 AA29930; Wed, 8 Sep 93 09:58:53 -0700 Via: uk.ac.durham; Wed, 8 Sep 1993 17:58:37 +0100 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <10367-0@dummy1.dur.ac.uk>; Wed, 8 Sep 1993 17:58:30 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Wed, 8 Sep 93 17:58:26 BST Date: Wed, 8 Sep 1993 17:54:16 +0100 (BST) From: Barry Cornelius Subject: Pine and Pico with hpterm To: Pine Info Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have had problems with using pine and pico in hpterm windows (with HP's operating system HP-UX 8.07 and HP-UX 9.01). The problem is that the cursor-moving keys are not being understood. Does anyone have fixes for this? -- 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 Wed Sep 8 10:24:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13572; Wed, 8 Sep 93 10:24:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00392; Wed, 8 Sep 93 10:16:29 -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 AA00386; Wed, 8 Sep 93 10:16:27 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21566; Wed, 8 Sep 93 10:16:09 -0700 Date: Wed, 8 Sep 1993 10:12:08 -0700 (PDT) From: David L Miller Subject: Re: Pine and Pico with hpterm To: Barry Cornelius Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A patch will be included in the Pine 3.85 distribution, in the contrib/keypad-enable directory, that will enable the HPterm cursor keys as well as the application keypad. The reason it will only be a patch is that we do not currently support the application keypad, only the cursor keys. |\ | |\/| 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, 8 Sep 1993, Barry Cornelius wrote: > We have had problems with using pine and pico in hpterm windows (with HP's > operating system HP-UX 8.07 and HP-UX 9.01). The problem is that the > cursor-moving keys are not being understood. Does anyone have fixes for > this? > > -- > 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 Wed Sep 8 13:53:39 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20095; Wed, 8 Sep 93 13:53:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17242; Wed, 8 Sep 93 13:42:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17236; Wed, 8 Sep 93 13:42:41 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA13985; Wed, 8 Sep 93 13:40:11 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA24505; Wed, 8 Sep 93 13:45:20 -0700 Date: Wed, 8 Sep 1993 13:44:01 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Pine and Pico with hpterm To: Barry Cornelius Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 8 Sep 1993, Barry Cornelius wrote: > We have had problems with using pine and pico in hpterm windows (with HP's > operating system HP-UX 8.07 and HP-UX 9.01). The problem is that the > cursor-moving keys are not being understood. Does anyone have fixes for > this? No, but this is a problem for us, too. Probably everybody that has an X-console on their workstation... > > -- > 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 > > /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Wed Sep 8 14:10:48 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20600; Wed, 8 Sep 93 14:10:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04378; Wed, 8 Sep 93 14:01:53 -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 AA04372; Wed, 8 Sep 93 14:01:51 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27147; Wed, 8 Sep 93 14:01:48 -0700 Date: Wed, 8 Sep 1993 14:01:12 -0700 (PDT) From: David L Miller Subject: Re: Pine and Pico with hpterm To: "Jason R. Thorpe" Cc: Barry Cornelius , Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII By the way, HP-UX also comes with xterm which works fine with Pine. |\ | |\/| 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, 8 Sep 1993, Jason R. Thorpe wrote: > On Wed, 8 Sep 1993, Barry Cornelius wrote: > > > We have had problems with using pine and pico in hpterm windows (with HP's > > operating system HP-UX 8.07 and HP-UX 9.01). The problem is that the > > cursor-moving keys are not being understood. Does anyone have fixes for > > this? > > No, but this is a problem for us, too. Probably everybody that has an > X-console on their workstation... > > > > > -- > > 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 > > > > > > > > /***************************************************************************** > Jason R. Thorpe - OSU Computer Science Support Staff > Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu > *****************************************************************************/ > > > From owner-pine-info@cac.washington.edu Wed Sep 8 19:11:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29342; Wed, 8 Sep 93 19:11:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22722; Wed, 8 Sep 93 18:57:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22716; Wed, 8 Sep 93 18:57:12 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA16204; Wed, 8 Sep 93 18:54:16 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA24872; Wed, 8 Sep 93 18:59:10 -0700 Date: Wed, 8 Sep 1993 18:54:27 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Pine and Pico with hpterm To: David L Miller Cc: "Jason R. Thorpe" , Barry Cornelius , Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 8 Sep 1993, David L Miller wrote: > > By the way, HP-UX also comes with xterm which works fine with Pine. I'm aware of this...I use it extensively...However...the console on an HP9000/430 and any other HP 9000 that has X capability (the consoles) act just like an hpterm window (its what hpterm is based on)...this poses a problem if you need to use pine and you're trying to fix X, or do not have XDM enable on the console (or don't want to bring up a full xsession just to do a quick mail check) Anyway...just putting in my 3.2 cents (tax in Washington :-) ) Later... /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Wed Sep 8 19:39:39 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29746; Wed, 8 Sep 93 19:39:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22921; Wed, 8 Sep 93 19:21:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from netcomsv.netcom.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22901; Wed, 8 Sep 93 19:21:00 -0700 Received: from wndrsvr.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1) id AA27091; Wed, 8 Sep 93 19:20:04 PDT Received: by wndrsvr (5.65/1.35) id AA18420; Wed, 8 Sep 93 18:19:11 -0700 From: andyb@wndrsvr.la.ca.us (Andy) Message-Id: <9309090119.AA18420@wndrsvr> Subject: Pine on ISC 3.0 To: pine-info@cac.washington.edu Date: Wed, 8 Sep 1993 18:19:11 -0700 (PDT) In-Reply-To: X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 256 Seeing as how I didn't receive a single volunteer to test Pine 3.84x yet, I have to assume there is no interest in using Pine/Pico under ISC. Therefore, I will cease all work on it and may pick it up again in 6 months or so if I feel like it. - Andy From owner-pine-info@cac.washington.edu Wed Sep 8 20:42:59 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00497; Wed, 8 Sep 93 20:42:59 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23314; Wed, 8 Sep 93 20:31:04 -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 AA23308; Wed, 8 Sep 93 20:31:03 -0700 Received: from rac4.wam.umd.edu by pg2-srv.wam.umd.edu with SMTP id AA00695 (5.65c/IDA-1.4.4 for ); Wed, 8 Sep 1993 23:29:31 -0400 Received: by rac4.wam.umd.edu id AA18953 (5.65c/IDA-1.4.4); Wed, 8 Sep 1993 23:29:46 -0400 Date: Wed, 8 Sep 1993 23:29:17 -0400 (EDT) From: "Highway (SexyOne's Playtoy!) Man" Subject: Re: Pine on ISC 3.0 To: Andy Cc: pine-info@cac.washington.edu In-Reply-To: <9309090119.AA18420@wndrsvr> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 8 Sep 1993, Andy wrote: ISC or ICS... what's that? I would like to test 3.8x. --------------------- [ 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 Wed Sep 8 21:35:26 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01033; Wed, 8 Sep 93 21:35:26 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23614; Wed, 8 Sep 93 21:24:32 -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 AA23608; Wed, 8 Sep 93 21:24:31 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09309; Thu, 9 Sep 93 00:24:29 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA04122; Wed, 8 Sep 93 22:25:10 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: Wed, 8 Sep 1993 22:19:42 -0600 (MDT) From: "Jeffrey M. Wolff" Subject: Alias problem To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Has anyone other than me been unsucessful in entering an X400 gateway address to the addressbook? I have a person that need added to a distribution list, but I cannot because his X400 address is too long for Pine. Also...even though I have all of my address book entries sorted properly in the list (Last Name, First Name) when I prepare a distribution list made up of other aliases, it sorts them alphabetically based on their FIRST name. Any ideas here? I am using version 3.05. I would test a new version, but I also don't know what ISC is. Hey, and while I have already cluttered everyone's mailbox with this message, anyone know where I can get a simple yet effective mnailing list reflector package. (Respond via E-Mail to keep Pine traffic down, please). -- Jeffrey M. Wolff | "In my mind....I'm already gone!" jwolff@nyx.cs.du.edu | - Kramer From owner-pine-info@cac.washington.edu Wed Sep 8 22:32:39 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01681; Wed, 8 Sep 93 22:32:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23949; Wed, 8 Sep 93 22:12:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from netcomsv.netcom.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23943; Wed, 8 Sep 93 22:12:07 -0700 Received: from wndrsvr.UUCP by netcomsv.netcom.com with UUCP (4.1/SMI-4.1) id AA28267; Wed, 8 Sep 93 22:11:11 PDT Received: by wndrsvr (5.65/1.35) id AA23046; Wed, 8 Sep 93 22:07:10 -0700 From: andyb@wndrsvr.la.ca.us (Andy) Message-Id: <9309090507.AA23046@wndrsvr> Subject: Re: Pine on ISC 3.0 To: highway@wam.umd.edu (Highway) Date: Wed, 8 Sep 1993 22:07:09 -0700 (PDT) Cc: pine-info@cac.washington.edu In-Reply-To: from "Highway" at Sep 8, 93 11:29:17 pm X-Mailer: ELM [version 2.4 PL22] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 374 > On Wed, 8 Sep 1993, Andy wrote: > > ISC or ICS... what's that? I would like to test 3.8x. ISC stands for Interactive Systems Corporation, and that is the brand of Unix to which I have attempted to port Pine and friends. I would guess that if you were running it, you'd know it. Thanks for the thought though! (For the record, pico seems to work just fine.) - Andy From owner-pine-info@cac.washington.edu Thu Sep 9 00:39:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03259; Thu, 9 Sep 93 00:39:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24687; Thu, 9 Sep 93 00:25:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dutw1.wbmt.tudelft.nl by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24681; Thu, 9 Sep 93 00:25:12 -0700 Received: by dutw1.wbmt.tudelft.nl id AA02903 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 9 Sep 1993 09:24:27 +0200 Date: Thu, 9 Sep 1993 09:09:49 +0200 (MET DST) From: Tjeerd Jongeling Subject: Re: Alias problem To: "Jeffrey M. Wolff" Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII L.S. I did once with a "echo .... >> .addressbook" but my volatile mind has lost. However, i just have tried a tempoary-file construction and it works as well: Edit a file (vi x400.tmp) and enter the required string: Nick-NameFull Name"A=aa aaa/B=bb bbb/C=et cetera/"@400net.Country Finally append this file to the .addressbook (cat x400.tmp >> .addressbook) On Wed, 8 Sep 1993, Jeffrey M. Wolff wrote: > > Has anyone other than me been unsucessful in entering an X400 gateway > address to the addressbook? > > I have a person that need added to a distribution list, but I cannot > because his X400 address is too long for Pine. > > Also...even though I have all of my address book entries sorted properly > in the list (Last Name, First Name) when I prepare a distribution list made > up of other aliases, it sorts them alphabetically based on their FIRST name. > Any ideas here? I am using version 3.05. > > I would test a new version, but I also don't know what ISC is. > > Hey, and while I have already cluttered everyone's mailbox with this > message, anyone know where I can get a simple yet effective mnailing list > reflector package. (Respond via E-Mail to keep Pine traffic down, please). > > -- > Jeffrey M. Wolff | "In my mind....I'm already gone!" > jwolff@nyx.cs.du.edu | - Kramer > Tjeerd Jongeling - Technical University of Delft Tj.Jongeling@WbMT.TUDelft.NL From owner-pine-info@cac.washington.edu Thu Sep 9 05:34:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09129; Thu, 9 Sep 93 05:34:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26609; Thu, 9 Sep 93 05:04:40 -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 AA26603; Thu, 9 Sep 93 05:04:37 -0700 Received: from foss.ncl.ac.uk by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Thu, 9 Sep 1993 13:04:32 +0100 Received: from localhost (nqgc@localhost) by carr7.ncl.ac.uk (8.5/HP-UX.cf(V8.5.1.5)) id NAA02616; Thu, 9 Sep 1993 13:04:31 +0100 Date: Thu, 9 Sep 1993 12:20:02 +0000 (GMT) From: Quentin Campbell Subject: Re: "Reply-to" To: Philip Hazel Cc: Barry.Landy@UCS.CAM.AC.UK, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 6 Sep 1993, Philip Hazel wrote: > Date: Mon, 6 Sep 1993 15:16:44 +0100 (BST) > From: Philip Hazel > To: Barry.Landy@UCS.CAM.AC.UK > Cc: pine-info@cac.washington.edu > Subject: Re: "Reply-to" > > > .... > > [This is adding to the above, not replying to it.] > > Furthermore, in this example, it is NOT appropriate to configure the > cus.cam.ac.uk system to accept mail addressed to ucs.cam.ac.uk, since not > all users of cus.cam.ac.uk have that as their domain address. Different > groups of users who have their final mailboxes on cus.cam.ac.uk may well > have different "friendly" mail addresses, e.g. > > john.doe@some-college.cam.ac.uk > jill.person@some-department.cam.ac.uk > > which are handled via the mail hub/switch. There are thousands of users of > this system. Apart from the fact that the MTA on cus.cam.ac.uk (smail3) > doesn't have a re-writing facility, the sheer administrative effort of > maintaining lists of per-user friendly mail addresses so that each outgoing > message could have its headers re-written is too great. Much easier to let > each user tailor their own world. > There are good reasons for maintaining a central MTA with a re-writing capability. I feel that Philip Hazel's reply dismisses these to lightly. Unlike Cambridge this University has a single, central, mail hub serving all mail enabled Unix and Novell/PC systems on campus. It serves many hundreds of systems and many thousands of users and does per-user resignature as this message shows. One advantage of a central mail hub is that it can provide additional gateways for e-mail, such as TELEX and FAX for example, that individual departments/users cannot afford to install themselves. Moreover system administrators are freed from the tiresome and difficult task of maintaining complex mail configuration files, tables, etc. Any mail originating on a client is simply forwarded to the central mail hub which does all the work of re-signature, routing, list expansion, etc. Likewise, addresses on incoming mail are processed to determine the appropriate delivery mail box and system. In certain cases the message is forwarded to another destination. The central mail agent is sendmail with the IDA enhancements. The latter is the key to being able to re-write header and envelope addresses in incoming and outgoing mail. The main benefit to users is host hiding; users can and do move around and although their mailbox system may change their e-mail address does not. Their are secondary benefits such as "friendly" mail names, central aliasing and automatic re-direction of mail at the mail hub. The administration of e-mail addresses is simply a component of the centralised user registration system that our Computing Service maintains. The majority of our users (undergraduate) are automatically set up with a Unix username and a mail name derived from info passed to us from the Registrar's department at the start of each academic year. Staff users are added by hand when they register with the Computing Service. Quentin Campbell (postmaster) -- PHONE: +44 91 222 8209 Computing Service, FAX : +44 91 222 8765 University of Newcastle upon Tyne, TELEX: uk+53654-UNINEW_G United Kingdom, NE1 7RU. From owner-pine-info@cac.washington.edu Thu Sep 9 05:45:42 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09282; Thu, 9 Sep 93 05:45:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26735; Thu, 9 Sep 93 05:27:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26729; Thu, 9 Sep 93 05:27:14 -0700 Received: from black.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <07914-0@ppsw2.cam.ac.uk>; Thu, 9 Sep 1993 13:25:38 +0100 Received: from quinag.csi.cam.ac.uk by black.csi.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <00901-0@black.csi.cam.ac.uk>; Thu, 9 Sep 1993 13:25:35 +0100 Date: Thu, 9 Sep 1993 13:20:52 BST From: Barry Landy Subject: Re: "Reply-to" To: Quentin Campbell Cc: Philip Hazel , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 9 Sep 1993, Quentin Campbell wrote: > > There are good reasons for maintaining a central MTA with a re-writing > capability. I feel that Philip Hazel's reply dismisses these to lightly. > Neither Philip nor myself would deny your good reasons, nor do we dismiss them lightly. We are only trying to point out that there are multiple ways to skin this particular cat, and for the way that we have gone (for good local reasons) we need "Reply-To". ======================================================================= 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 Thu Sep 9 11:56:11 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19299; Thu, 9 Sep 93 11:56:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bishop.bishop.Hawaii.Org by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19255; Thu, 9 Sep 93 11:56:02 -0700 From: edwardy@bishop.bishop.hawaii.org Received: by bishop.bishop.hawaii.org (AIX 3.2/UCB 5.64/4.03) id AA33983; Thu, 9 Sep 1993 08:52:35 -1000 Date: Thu, 9 Sep 1993 08:48:52 +22305714 (HST) Subject: Unexpanded address header? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Aloha, A friend of mines was asking if this was possible in pine: >I need to find a way to make pine not automatically fill in the full >address of the person your sending mail to. For example, if I'm >sending mail to you, I want the header to show edwardy instead of >edwardy@uhunix.uhcc.hawaii.edu. This is especially needed in the cc: >line of the header when I'm using a mailing list from the addressbook. >Some lists that I send out here contain up 15 people. If I use a >list, it expands each person's full address on one line each. So the >headers are sometimes a whole lot bigger than the message itself. I suggested creating a dummy account with a .forward in it listing all the usernames, but that seems like a backward way of doing it.. any other solutions in pine? Edward Yagi edwardy@bishop.bishop.hawaii.org From owner-pine-info@cac.washington.edu Thu Sep 9 12:37:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20757; Thu, 9 Sep 93 12:37:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01207; Thu, 9 Sep 93 12:26:35 -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 AA01201; Thu, 9 Sep 93 12:26:33 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA03346; Thu, 9 Sep 1993 14:29:56 -0500 Date: Thu, 9 Sep 1993 14:27:47 -0500 (CDT) From: "Robert A. Hayden" Subject: New Version To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I apologize if this has been asked and answered, but I just got back from a three-week vacation to 1300 new mail messages, so I didn't really ready everying very closely. Anyways, is the new version (3.85 wasn't it?) out yet? If not, what's the time line? When I left, it was 'Real Soon Now{tm}'. Thanks much. {[> Robert A. Hayden ____ EARTH <]} {[> \ /__ smog | bricks <]} {[> aq650@slc4.INS.CWRU.Edu \/ / AIR -- mud -- FIRE <]} {[> hayden@krypton.mankato.msus.edu \/ beer | tequila <]} -=-=- WATER -=-=- 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 Sep 9 13:13:15 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22169; Thu, 9 Sep 93 13:13:15 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01576; Thu, 9 Sep 93 13:05:22 -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 AA01568; Thu, 9 Sep 93 13:05:20 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA03665; Thu, 9 Sep 1993 15:08:43 -0500 Date: Thu, 9 Sep 1993 15:06:22 -0500 (CDT) From: "Robert A. Hayden" Subject: Re: New Version To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 9 Sep 1993, David L Miller wrote: > Well, it's now down to 'A couple weeks{tm}.' > > I could stick my neck out and say we are tentatively planning on a > September 20 release, but I won't ;) Hmm, any chance we could possibly maybe see a list of changes and enhancements the new version will bring? Just to make us all drool a little bit more, of course. (Of couse, if documentation is the last thing you are working on, I suppose this doesn't exist yet :-) {[> Robert A. Hayden ____ EARTH <]} {[> \ /__ smog | bricks <]} {[> aq650@slc4.INS.CWRU.Edu \/ / AIR -- mud -- FIRE <]} {[> hayden@krypton.mankato.msus.edu \/ beer | tequila <]} -=-=- WATER -=-=- 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 Sep 9 13:15:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22341; Thu, 9 Sep 93 13:15:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04483; Thu, 9 Sep 93 13:02:16 -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 AA04477; Thu, 9 Sep 93 13:02:15 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22785; Thu, 9 Sep 93 13:02:11 -0700 Date: Thu, 9 Sep 1993 12:57:05 -0700 (PDT) From: David L Miller Subject: Re: New Version To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Well, it's now down to 'A couple weeks{tm}.' I could stick my neck out and say we are tentatively planning on a September 20 release, but I won't ;) |\ | |\/| 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, 9 Sep 1993, Robert A. Hayden wrote: > Hi, > > I apologize if this has been asked and answered, but I just got back from > a three-week vacation to 1300 new mail messages, so I didn't really ready > everying very closely. > > Anyways, is the new version (3.85 wasn't it?) out yet? If not, what's the > time line? When I left, it was 'Real Soon Now{tm}'. > > Thanks much. > > {[> Robert A. Hayden ____ EARTH <]} > {[> \ /__ smog | bricks <]} > {[> aq650@slc4.INS.CWRU.Edu \/ / AIR -- mud -- FIRE <]} > {[> hayden@krypton.mankato.msus.edu \/ beer | tequila <]} > -=-=- WATER -=-=- > 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 Sep 9 14:07:30 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23937; Thu, 9 Sep 93 14:07:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05468; Thu, 9 Sep 93 13:58:21 -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 AA05462; Thu, 9 Sep 93 13:58:20 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24521; Thu, 9 Sep 93 13:58:16 -0700 Date: Thu, 9 Sep 1993 13:53:31 -0700 (PDT) From: David L Miller Subject: Re: New Version To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 9 Sep 1993, Robert A. Hayden wrote: > On Thu, 9 Sep 1993, David L Miller wrote: > > > Well, it's now down to 'A couple weeks{tm}.' > > > > I could stick my neck out and say we are tentatively planning on a > > September 20 release, but I won't ;) > > Hmm, any chance we could possibly maybe see a list of changes and > enhancements the new version will bring? Just to make us all drool a > little bit more, of course. > > (Of couse, if documentation is the last thing you are working on, I > suppose this doesn't exist yet :-) > This is from the PC-pine 3.84 release notes. We have not reviewed it for Pine 3.85 yet, but it should give you an idea... ********PRELIMINARY******** II. EXECUTIVE SUMMARY Page - This is the first version of Pine that runs on DOS. - It has several major new features: o Multiple folder collections. o Remote folder create/append (requires new IMAPd). o Composer has Mark command for block cut/paste. o Improved handling of text attachments. o Improved mailbox lock handling: latest Pine will now be read-write. o Messages directly to you marked with "+" in Folder Index. o Several new .pinerc options. o Various UI improvements (command consistency, simplification, etc). o Easier access to newsgroups (but still not a full newsreader). - Several command key changes were needed to allow for new features: Page o Print is now "Y" instead of "L" o The Folder List is now uniformly accessible via "L" o Viewing/saving attachments is now done via "V" instead of "A" o SortIndex is now "$" instead of "Z" - There are several known limitations in the PC version: o There is no spelling checker. o Sorting the Index (by other than Arrival) is *hopelessly* slow. o The alternate editor function is not available. o Versions: initially only packet driver, Novell LWP, and FTP PC-TCP o Memory: it needs about 500K out of 640K. o Probably can't run image viewer from within Pine, due to memory. o Performance optimization still needs to be done. From owner-pine-info@cac.washington.edu Thu Sep 9 14:25:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24397; Thu, 9 Sep 93 14:25:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05739; Thu, 9 Sep 93 14:17:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gray.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05731; Thu, 9 Sep 93 14:17:15 -0700 Received: from phx.cam.ac.uk by ppsw1.cam.ac.uk with GB-CAM (PP-6.0) as ppsw.cam.ac.uk id <23198-0@ppsw1.cam.ac.uk>; Thu, 9 Sep 1993 22:17:06 +0100 Date: Thu, 09 Sep 93 22:16:52 BST From: Barry.Landy@UCS.CAM.AC.UK To: edwardy@bishop.bishop.hawaii.org Cc: pine-info@cac.washington.edu Subject: Re: [Unexpanded address header?] Message-Id: > Aloha, > A friend of mines was asking if this was possible in pine: > > >I need to find a way to make pine not automatically fill in the full > >address of the person your sending mail to. For example, if I'm > >sending mail to you, I want the header to show edwardy instead of > >edwardy@uhunix.uhcc.hawaii.edu. This is especially needed in the cc: > >line of the header when I'm using a mailing list from the addressbook. > >Some lists that I send out here contain up 15 people. If I use a > >list, it expands each person's full address on one line each. So the > >headers are sometimes a whole lot bigger than the message itself. > > > I suggested creating a dummy account with a .forward in it listing all > the usernames, but that seems like a backward way of doing it.. any > other solutions in pine? > > Edward Yagi > edwardy@bishop.bishop.hawaii.org > No, please do not permit that. In general it would mean that someone outside your mail domain receiving such a message and attempting to reply to all the Cc: list would generate incorrect addresses for them; indeed, if you used nicknames/aliases he would not know who to reply to at all. ======================================================================= 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 Thu Sep 9 14:28:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24550; Thu, 9 Sep 93 14:28:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05843; Thu, 9 Sep 93 14:21:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gray.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05837; Thu, 9 Sep 93 14:21:25 -0700 Received: from phx.cam.ac.uk by ppsw1.cam.ac.uk with GB-CAM (PP-6.0) as ppsw.cam.ac.uk id <23257-0@ppsw1.cam.ac.uk>; Thu, 9 Sep 1993 22:21:19 +0100 Date: Thu, 09 Sep 93 22:21:05 BST From: Barry.Landy@UCS.CAM.AC.UK To: David L Miller Cc: Pine Info Subject: Re: New Version Message-Id: In-Reply-To: > Well, it's now down to 'A couple weeks{tm}.' > > I could stick my neck out and say we are tentatively planning on a > September 20 release, but I won't ;) > > |\ | |\/| 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 > > Wonderful news - especially as we are relying (as are many others) on having this in production for the new academic year now fast approaching. It would be very important for me to know what bugs are fixed (in PC-PINE), especially the 'black screen' effect I reported when doing compose in the "-k" version for PC. We would also very much like to know when you expect Unix Pine to catch up with PC PINE. These two in particular have major implications for our documentation, courses etc etc. Thanks for all the hard work; you guys must be really sweating! ======================================================================= 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 Thu Sep 9 15:13:06 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26049; Thu, 9 Sep 93 15:13:06 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06612; Thu, 9 Sep 93 15:04: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 AA06606; Thu, 9 Sep 93 15:04:12 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA15543; Thu, 9 Sep 93 15:04:04 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA09221; Thu, 9 Sep 93 15:04:02 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA00652; Thu, 9 Sep 93 15:04:02 PDT Received: by hal.usc.edu (4.1/SMI-4.1) id AA29456; Thu, 9 Sep 93 15:04:01 PDT Date: Thu, 9 Sep 1993 15:00:49 -0700 (PDT) From: Elmar Kurgpold Reply-To: Elmar Kurgpold Subject: Attachments not recognized To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We are still working out the details for standard setups, and have come across an apparent glitch. I believe I have gone through the whole technical notes document twice (at least 8') What happens is when I attach a data file and mail it back to myself, I seem to get the encoded file but cannot detach it once received. When I check for attachments, I am asked... Enter attachment number to view or save (1 - 1) There has been times when the attached file is seemingly not included, and the file bombed. When this happened, I believe there was an attachment but it was empty. Specifically, I am trying to send WordPerfect files created in DOS and then copied up to my Unix disk via NFS. It works great with ascii files. I've attached a portion of the message below. One more question: Will there be block editing capabilities in future versions of pico/pine? ---------- Forwarded message ---------- Date: Thu, 9 Sep 1993 14:41:52 -0700 (PDT) From: Elmar Kurgpold To: Elmar Kurgpold Subject: here's coming --1915757200-358981935-747610992:#29384 Content-Type: APPLICATION/octet-stream; name="charmap.tst" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: /1dQQ9YEAAABCgABAAAAAPv/BQAyABEBAAD//w4AAABCAAAABgAQAAAAUAAA AP//WgAAAKYAAAD//xEAAAAAAQAAQ291cmllciAxMGNwaQAIA3wAeAAAAAAA AAAAAAAAAQAAAABVXtsBeAAUHgwXjAoAAAAEEUDJAIfPAQABAFgCQP////// /////////////////////////////////////////wAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ...etc --1915757200-358981935-747610992:#29384-- From owner-pine-info@cac.washington.edu Thu Sep 9 16:42:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28448; Thu, 9 Sep 93 16:42:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08228; Thu, 9 Sep 93 16:33:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from minnie.bell.inmet.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08219; Thu, 9 Sep 93 16:33:18 -0700 Received: by minnie.bell.inmet.com (4.1/SMI-4.1) id AA10490; Thu, 9 Sep 93 16:36:01 PDT Date: Thu, 9 Sep 1993 16:25:38 -0700 (PDT) From: Paul Tarr Subject: Comments on "Attachments not recognized" To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We also are having trouble with attachments. When a pine mail message with attachments (a wordperfect file as noted by Elmar Kurgpold) is sent to an OpenWindows 3.0 mail tool (SUN based X-11 system), the attachment is not recognized. The attachment exists as part of the body of the message not an attachment. From owner-pine-info@cac.washington.edu Thu Sep 9 19:02:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01738; Thu, 9 Sep 93 19:02:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09863; Thu, 9 Sep 93 18:55:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09857; Thu, 9 Sep 93 18:54:52 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2S6D6QCTC0002U6@VENUS.RESNTL.BHP.COM.AU>; Fri, 10 Sep 1993 11:52:55 GMT Date: Fri, 10 Sep 1993 11:41:50 +1000 (EST) From: Steve Woodyatt Subject: BUG in Addressbook handling To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Hi all, Just a warning about the use of long addressbook lists - they cause Pine to crash. I'm not sure whether it's simply the number of entries, or what. I have a reasonably long addressbook, with a number of levels of 'indirection'. For example, my research section is made up of 3 research groups, each which are split over 2 physical sites (separated by ~1100 kms). So, when I want to mail all members of the research section, my addressbook entry looks like: Section Whole Research Section (Group1, Group2, Group3) Group1 First Group (Group1Site1,Group1Site2) Group2 Second Group (Group2Site1,Group2Site2) Group3 Third-and-Final Group (Group3Site1,Group3Site2) Group1Site1 First Group Site 1 (name1,name2,name3,name4) Group1Site2 First Group Site 2 (name5,name6,name7,name8) From owner-pine-info@cac.washington.edu Fri Sep 10 08:20:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14293; Fri, 10 Sep 93 08:20:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15300; Fri, 10 Sep 93 08:12:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from helium.GAS.UUG.Arizona.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15294; Fri, 10 Sep 93 08:12:06 -0700 Received: by helium.GAS.uug.Arizona.EDU (4.1/Helium-MX-1.4) id AA19530; Fri, 10 Sep 93 08:11:50 MST Date: Fri, 10 Sep 1993 08:10:33 -0700 (MST) From: Mari J Stoddard Subject: Re: BUG in Addressbook handling To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 10 Sep 1993, Steve Woodyatt wrote: > Just a warning about the use of long addressbook lists - they cause Pine > to crash. I'm not sure whether it's simply the number of entries, or what. Does long translate to more than 10 lines, more than ten screens, or more than 10 thousand? Thanks -- Mari -- Mari J. Stoddard stoddard@gas.uug.arizona.edu University of Arizona Health Sciences Library in Tucson From owner-pine-info@cac.washington.edu Fri Sep 10 09:25:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16467; Fri, 10 Sep 93 09:25:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16396; Fri, 10 Sep 93 09:15:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hermes.acs.ryerson.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16390; Fri, 10 Sep 93 09:15:21 -0700 Received: by hermes.acs.ryerson.ca (AIX 3.2/UCB 5.64/4.03) id AA25294; Fri, 10 Sep 1993 12:14:27 -0400 Date: Fri, 10 Sep 1993 12:10:36 -500 (EDT) From: Paul Ribeiro Subject: Re: BUG in Addressbook handling To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 10 Sep 1993, Mari J Stoddard wrote: > Does long translate to more than 10 lines, more than ten screens, or more for me it died on 22 recipients.... - to be specific it shows the list on the screen, if you cursor up it exits with BUG in pine: received abort signal (I'm still on 3.05a - can't upgrade until the aix port is available) /P From owner-pine-info@cac.washington.edu Fri Sep 10 13:49:07 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24972; Fri, 10 Sep 93 13:49:07 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21051; Fri, 10 Sep 93 13:33:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from laidbak.ucs.indiana.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21045; Fri, 10 Sep 93 13:33:56 -0700 Received: from loris.cisab.indiana.edu by PO4.Indiana.EDU; id AA13038 (5.65c+jsm/2.5.1jsm); Fri, 10 Sep 1993 15:33:48 -0500 Received: by loris.cisab.indiana.edu (AIX 3.2/UCB 5.64/4.03) id AA19873; Fri, 10 Sep 1993 15:32:33 -0500 Date: Fri, 10 Sep 1993 15:29:49 -500 (EST) From: Shan Duncan Subject: Re: BUG in Addressbook handling 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 Fri, 10 Sep 1993, Paul Ribeiro wrote: > Date: Fri, 10 Sep 1993 12:10:36 -500 (EDT) > From: Paul Ribeiro > To: pine-info@cac.washington.edu > Subject: Re: BUG in Addressbook handling > > On Fri, 10 Sep 1993, Mari J Stoddard wrote: > > Does long translate to more than 10 lines, more than ten screens, or more > for me it died on 22 recipients.... > - to be specific it shows the list on the screen, if you cursor up it > exits with > BUG in pine: received abort signal > (I'm still on 3.05a - can't upgrade until the aix port is available) > /P > I reported the same problem using 3.05a and 3.07 running aix 3.2.x but have not had the time to try and chase it down. Is this problem unique to the rs6ks running pine? -sdd From owner-pine-info@cac.washington.edu Fri Sep 10 17:08:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01755; Fri, 10 Sep 93 17:08:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24327; Fri, 10 Sep 93 16:57:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uhunix.uhcc.Hawaii.Edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24321; Fri, 10 Sep 93 16:57:16 -0700 Received: from (uhunix3.uhcc.Hawaii.Edu) by uhunix.uhcc.Hawaii.Edu (4.1/Sun690) id AA03881; Fri, 10 Sep 93 13:56:30 HST Received: by (4.1/uhunix3) id AA21593; Fri, 10 Sep 93 12:54:07 HST Date: Fri, 10 Sep 1993 12:48:56 -1000 (HST) From: "Lee Ann M. Sakihara" Reply-To: "Lee Ann M. Sakihara" Subject: Re: BUG in Addressbook handling To: Shan Duncan Cc: Paul Ribeiro , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I don't know if this is the same problem. I'm getting an error message from the mailer, but I think the mail is being distributed to everyone on the list. I have 34 recipients on this list. The hardware is a Sun 4/690, OS is SunOS 4.1.3, pine version 3.05. Here's part of the error message: ============================================================================== From: Mail Delivery Subsystem To: miyamura@uhunix3.uhcc.Hawaii.Edu Subject: Returned mail: Unable to deliver mail ----- Transcript of session follows ----- 554 Unbalanced '<' 554 >,>,,,... Unbalanced '<' ----- Unsent message follows ----- Received: from (uhunix3.uhcc.Hawaii.Edu) by uhunix.uhcc.Hawaii.Edu (4.1/Sun690) id AA08332; Fri, 10 Sep 93 09:49:53 HST Received: by (4.1/uhunix3) id AA15343; Fri, 10 Sep 93 09:49:51 HST ============================================================================== On Fri, 10 Sep 1993, Shan Duncan wrote: > Date: Fri, 10 Sep 1993 15:29:49 -500 (EST) > From: Shan Duncan > To: Paul Ribeiro > Cc: pine-info@cac.washington.edu > Subject: Re: BUG in Addressbook handling > > On Fri, 10 Sep 1993, Paul Ribeiro wrote: > > > Date: Fri, 10 Sep 1993 12:10:36 -500 (EDT) > > From: Paul Ribeiro > > To: pine-info@cac.washington.edu > > Subject: Re: BUG in Addressbook handling > > > > On Fri, 10 Sep 1993, Mari J Stoddard wrote: > > > Does long translate to more than 10 lines, more than ten screens, or more > > for me it died on 22 recipients.... > > - to be specific it shows the list on the screen, if you cursor up it > > exits with > > BUG in pine: received abort signal > > (I'm still on 3.05a - can't upgrade until the aix port is available) > > /P > > > > > I reported the same problem using 3.05a and 3.07 running aix 3.2.x > but have not had the time to try and chase it down. Is this problem > unique to the rs6ks running pine? > > > -sdd > > From owner-pine-info@cac.washington.edu Sun Sep 12 09:10:51 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27452; Sun, 12 Sep 93 09:10:51 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16508; Sun, 12 Sep 93 08:58:48 -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 AA16502; Sun, 12 Sep 93 08:58:46 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA17498; Sun, 12 Sep 93 11:58:45 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA16682; Sun, 12 Sep 93 09:59:34 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, 12 Sep 1993 09:59:11 -0600 (MDT) From: "Jeffrey M. Wolff" Subject: Questions To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Below is a partial output from .pine-debug* after I sent a message to test a couple of problems I am having. This mail was sent to a distribution list and my first question is why are these names being listed alphabetically by their FIRST names. This is an excerpt from my .addressbook which shows the entries in question. Christy Allison, Christy piranha@jhunix.hcf.jhu.edu Sarah Butcher, Sarah butcher95@alison.sbc.edu Board District Board (Christy,I,Sarah) I Wolff, Jeffrey M. jwolff@nyx.cs.du.edu As you can see, the aliases are entered in last name, first name format so that they sort alphabetically on their last name in the list. That works fine, but in the distribution list they sort on the first name. The second question is my full name. As you can see, it shows up on mail as "Jeffrey M. Wolff". How do I get rid of the quotation marks? When I originally configured the .pinerc in my home dir, I put my name in quotation marks on the fullname= line. But then I realized I don't need the quotation and I removed them. PINE still puts them in. I have even tried deleting my .pinerc and reconfiguring but with the same results. Can anyone help on these issues? -- Jeffrey M. Wolff | "In my mind....I'm already gone!" jwolff@nyx.cs.du.edu | - Kramer -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Debug output of the Pine program (at debug level 2). Version 3.05 Sun Sep 12 09:35:53 1993 ***** MAIL SENT ***** To: District Board -- Christy Allison , "Jeffrey M. Wolff" , Sarah Butcher Subject: Information Message ID: From owner-pine-info@cac.washington.edu Sun Sep 12 10:18:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28165; Sun, 12 Sep 93 10:18:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06038; Sun, 12 Sep 93 09:59:59 -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 AA06032; Sun, 12 Sep 93 09:59:57 -0700 Received: from jhunix.hcf.jhu.edu ([128.220.2.5]) by jhunix.hcf.jhu.edu with SMTP id <71006-5>; Sun, 12 Sep 1993 12:59:54 -0400 Date: Sun, 12 Sep 1993 12:55:48 -0400 From: Andy Poling Subject: Re: Questions To: "Jeffrey M. Wolff" Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 12 Sep 1993, Jeffrey M. Wolff wrote: [...] > The second question is my full name. As you can see, it shows up on mail > as "Jeffrey M. Wolff". How do I get rid of the quotation marks? When I > originally configured the .pinerc in my home dir, I put my name in > quotation marks on the fullname= line. But then I realized I don't need > the quotation and I removed them. PINE still puts them in. I have even > tried deleting my .pinerc and reconfiguring but with the same results. [...] > Debug output of the Pine program (at debug level 2). Version 3.05 > Sun Sep 12 09:35:53 1993 > > ***** MAIL SENT ***** > To: District Board -- Christy Allison , > "Jeffrey M. Wolff" , > Sarah Butcher > Subject: Information > Message ID: You most certainly DO need quotes around your chosen comment - because it contains a period ("."). Periods (and other special characters) may not be in unquoted comments in addresses. Alternatively, if you remove the "." after the "M", PINE will probably stop putting quotes around your comment... -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 Sun Sep 12 12:43:21 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29635; Sun, 12 Sep 93 12:43:21 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17140; Sun, 12 Sep 93 12:33: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 AA17134; Sun, 12 Sep 93 12:33:23 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA19565; Sun, 12 Sep 93 12:33:18 -0700 Date: Sun, 12 Sep 1993 12:32:06 -0700 (PDT) From: Mark Crispin Subject: re: Questions To: "Jeffrey M. Wolff" Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Someone else will have to answer your sorting problem, but in answer to why your name is in quotes, any name that has a period in it has to be quoted. That's the RFC 822 rules. Spell out your middle name, remove the period after the M, or get rid of it entirely; do any of these and the quotes will magically vanish. From owner-pine-info@cac.washington.edu Sun Sep 12 15:56:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01800; Sun, 12 Sep 93 15:56:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07639; Sun, 12 Sep 93 15:46:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07633; Sun, 12 Sep 93 15:46:33 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2W6ML7X4G0007ZE@VENUS.RESNTL.BHP.COM.AU>; Mon, 13 Sep 1993 08:43:41 GMT Date: Mon, 13 Sep 1993 08:42:57 +1000 (EST) From: Steve Woodyatt Subject: RE: BUG in Addressbook handling In-Reply-To: To: Mari J Stoddard Cc: Steve Woodyatt , pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Fri, 10 Sep 1993, Mari J Stoddard wrote: > On Fri, 10 Sep 1993, Steve Woodyatt wrote: > > Does long translate to more than 10 lines, more than ten screens, or more > than 10 thousand? > > Well, for some reason, my whole email message didn't get posted. Here it is again: Just a warning about the use of long addressbook lists - they cause Pine to crash. I'm not sure whether it's simply the number of entries, or what. I have a reasonably long addressbook, with a number of levels of 'indirection'. For example, my research section is made up of 3 research groups, each which are split over 2 physical sites (separated by ~1100 kms). So, when I want to mail all members of the research section, my addressbook entry looks like: Section Whole Research Section (Group1, Group2, Group3) Group1 First Group (Group1Site1,Group1Site2) Group2 Second Group (Group2Site1,Group2Site2) Group3 Third-and-Final Group (Group3Site1,Group3Site2) Group1Site1 First Group Site 1 (name1,name2,name3,name4) Group1Site2 First Group Site 2 (name5,name6,name7,name8) From owner-pine-info@cac.washington.edu Sun Sep 12 16:37:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02152; Sun, 12 Sep 93 16:37:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07793; Sun, 12 Sep 93 16:25:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07787; Sun, 12 Sep 93 16:25:52 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2W80Z1QHC00087Q@VENUS.RESNTL.BHP.COM.AU>; Mon, 13 Sep 1993 09:23:30 GMT Date: Mon, 13 Sep 1993 09:22:08 +1000 (EST) From: Steve Woodyatt Subject: RE: Re: Re: Bugs in addressbook. To: pine-info@cac.washington.edu Cc: stoddard@gas.uud.arizona.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT This is getting *ridiculous*! I've now attempted to send this full message 3 times to the pine-info mailing list (about the Bugs in addressbooks), and all that gets transmitted is the first screenful of my message!!!!! Is this also a bug in Pico? Here is the 2nd screenfull, seeing I can't get all of the message!. The saga continues..... ------------------------------------------------------------------------ Group1Site2 First Group Site 2 (name5,name6,name7,name8) From owner-pine-info@cac.washington.edu Sun Sep 12 18:12:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03114; Sun, 12 Sep 93 18:12:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08182; Sun, 12 Sep 93 18:02:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08176; Sun, 12 Sep 93 18:02:09 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2WBD7H5IO0008KC@VENUS.RESNTL.BHP.COM.AU>; Mon, 13 Sep 1993 10:59:40 GMT Date: Mon, 13 Sep 1993 10:55:13 +1000 (EST) From: Steve Woodyatt Subject: RE: Re: Re: Bugs in addressbook. In-Reply-To: To: Jim Davis Cc: Steve Woodyatt , pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Sun, 12 Sep 1993, Jim Davis wrote: > Why don't you try sending this message to yourself before sending repeated > partial messages to a (worldwide) mailing list? If there really is a bug > somewhere, then that might help narrow it down, too. > Jim and the whole mailing list. 1. My apologies for all this extra mail :-( 2. I *have* tried to send it to myself (and other individuals) and the message *does* get through whole. Ergo, it must be the pine-info mailing list that does it. :-( 3. I have isolated the problem to an "elipsis" (i.e. 3 dots/periods sitting in the first character field of the message body. After the last line: Group1Site2 First Group Site 2 (name5, etc) of the message, this elipsis (3 dots) occurred. *That* is where the message gets truncated. I hypothesise: DO the andminstrators of the pine-info mailing list directly use sendmail to bounce all the pine-info messages? If so, a "dot" in the first character field of any of the text will cause sendmail to barf at the remainder of the file. I can only assume that is the problem. :-( 4. I have now taken the offending characters out of the mail message, and will try one last time. IF this doesn't work, I'll give up! Apologies again, Steve -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ BHP Research - Newcastle Laboratories, Australia./ / / \ Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / Internet: steve@resntl.bhp.com.au \ / / / ------------------------------------------------------------------\/\/\/-- From owner-pine-info@cac.washington.edu Sun Sep 12 18:13:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03152; Sun, 12 Sep 93 18:13:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08196; Sun, 12 Sep 93 18:04:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08190; Sun, 12 Sep 93 18:04:09 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H2WBG6T2LC0008KJ@VENUS.RESNTL.BHP.COM.AU>; Mon, 13 Sep 1993 11:02:03 GMT Date: Mon, 13 Sep 1993 11:02:15 +1000 (EST) From: Steve Woodyatt Subject: This WILL work. To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Again apologies for all the extra traffic. Here finally is the WHOLE message, minus offending characters. Can anyone shed some light on the problem documented below. Thank you. ====================================================================== Just a warning about the use of long addressbook lists - they cause Pine to crash. I'm not sure whether it's simply the number of entries, or what. I have a reasonably long addressbook, with a number of levels of 'indirection'. For example, my research section is made up of 3 research groups, each which are split over 2 physical sites (separated by ~1100 kms). So, when I want to mail all members of the research section, my addressbook entry looks like: Section Whole Research Section (Group1, Group2, Group3) Group1 First Group (Group1Site1,Group1Site2) Group2 Second Group (Group2Site1,Group2Site2) Group3 Third-and-Final Group (Group3Site1,Group3Site2) Group1Site1 First Group Site 1 (name1,name2,name3,name4) Group1Site2 First Group Site 2 (name5,name6,name7,name8) and so on. I then choose to compose a message to the "Section" alias, which brings up the Pico editor with the last few lines of a long list of names. If I then choose to move the cursor UP through the list (to look at names earlier on the list), I get: Bug in Pine detected: "Received abort signal". Exiting pine. Now, if I try sending to any of the "Group" aliases (or "GroupSite" aliases) it works perfectly. (That is, I can cursor up the list to check/modify any of the entries). The overall number of names in the whole "Section" alias is in excess of 60. Is this a problem? Steve. P.S. I also tried to remove one of the levels of 'indirection', by redifining the "Section" alias to be (Group1Site1,Group1Site2,Group2Site1....) It fails in the same way. P.S. If any of the Pine developers would like a copy of the addressbook to test, please e-mail me. I don't wish to broadcast my whole book to the Internet!!! -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ BHP Research - Newcastle Laboratories, Australia./ / / \ Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / Internet: steve@resntl.bhp.com.au \ / / / ------------------------------------------------------------------\/\/\/-- From owner-pine-info@cac.washington.edu Sun Sep 12 21:32:40 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05271; Sun, 12 Sep 93 21:32:40 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18772; Sun, 12 Sep 93 21:20:36 -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 AA18766; Sun, 12 Sep 93 21:20:34 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA18799; Mon, 13 Sep 93 00:20:33 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA20516; Sun, 12 Sep 93 22:21:22 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, 12 Sep 1993 22:20:19 -0600 (MDT) From: Jeffrey Wolff Subject: Problems To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Well, removing the period from my Fullname solved my quotation mark problem. Thanks to those people that were able to help. Anyone have any ideas about the sorting problem? Or is this a bug in PINE. -- Jeffrey M. Wolff | "In my mind....I'm already gone!" jwolff@nyx.cs.du.edu | - Kramer From owner-pine-info@cac.washington.edu Sun Sep 12 23:08:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06209; Sun, 12 Sep 93 23:08:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09672; Sun, 12 Sep 93 22:58:58 -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 AA09666; Sun, 12 Sep 93 22:58:56 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28273; Sun, 12 Sep 93 22:58:26 -0700 Date: Sun, 12 Sep 1993 22:56:04 -0700 (PDT) From: Steve Hubert Subject: RE: Re: Re: Bugs in addressbook. To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'll look into why the lines beginning with dots are terminating the messages. We are using sendmail but I thought we were ignoring dots. Sorry for the problems and thanks for debugging it. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Mon, 13 Sep 1993, Steve Woodyatt wrote: > 2. I *have* tried to send it to myself (and other individuals) and > the message *does* get through whole. Ergo, it must be the pine-info > mailing list that does it. :-( From owner-pine-info@cac.washington.edu Mon Sep 13 13:19:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24365; Mon, 13 Sep 93 13:19:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18058; Mon, 13 Sep 93 13:03:52 -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 AA18052; Mon, 13 Sep 93 13:03:50 -0700 Received: by acenet.auburn.edu (4.1/SMI-4.1 aces1 1.0) id AA19403; Mon, 13 Sep 93 15:03:48 CDT Date: Mon, 13 Sep 1993 15:03:34 -0500 (CDT) From: "John E. Burton Jr." Reply-To: "John E. Burton Jr." Subject: User Questions To: Pine Mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'm a user, not running any systems. However, I have a couple of questions about pine that I have not been able to get answered. Sorry if these are DUMB questions (probably FAQs), but I have not had much luck any place else. 1. Other than using the F forward command for each message one at a time, is it possible to read a message into another message? Sometimes I want to put two or more messages together into one message and send them to someone. 2. How do you set up the .pinerc or other files so that messages are ordered in Reverse order automatically as received? For example, I like to see the most recent messages at the top of the list instead of the older messages. Currently, our pine mailer puts the oldest messages first on the list in a folder. 3. Is there any more detailed instructions on using pine available some place (ftp?) that is a little more advanced or detailed than what is available on-line? By the way, I'm using pine 3.07 on a UNIX system. Appreciate any help or information. You can reply directly to my e-mail address rather than boring everyone else. By the way, I like pine much better than some other mail programs I've used over the years. Thanks very much. ------------------------------------------------------- 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 Mon Sep 13 13:55:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25998; Mon, 13 Sep 93 13:55:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18572; Mon, 13 Sep 93 13:29: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 AA18566; Mon, 13 Sep 93 13:29:29 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16498; Mon, 13 Sep 93 13:29:26 -0700 Date: Mon, 13 Sep 1993 13:23:53 -0700 (PDT) From: David L Miller Subject: Re: User Questions 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 See my comments below. |\ | |\/| 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, 13 Sep 1993, John E. Burton Jr. wrote: > > I'm a user, not running any systems. However, I have a couple of > questions about pine that I have not been able to get answered. Sorry if > these are DUMB questions (probably FAQs), but I have not had much luck any > place else. > > 1. Other than using the F forward command for each message one at a > time, is it possible to read a message into another message? Sometimes I > want to put two or more messages together into one message and send them > to someone. > About the only way to do this right now is to save the messages to a file, then compose a new message and read (^R) that file. > 2. How do you set up the .pinerc or other files so that messages are > ordered in Reverse order automatically as received? For example, I like > to see the most recent messages at the top of the list instead of the > older messages. Currently, our pine mailer puts the oldest messages first > on the list in a folder. > You can use the Sort option to reverse the order of messages. You cannot currently set a default sort order though. > 3. Is there any more detailed instructions on using pine available some > place (ftp?) that is a little more advanced or detailed than what is > available on-line? > The source distribution includes a few files on the doc directory (tech-notes, etc). There are also a few other files on ftp.cac.washington.edu in the /mail directory. > By the way, I'm using pine 3.07 on a UNIX system. > > Appreciate any help or information. You can reply directly to my > e-mail address rather than boring everyone else. > > By the way, I like pine much better than some other mail programs I've > used over the years. > > Thanks very much. > > ------------------------------------------------------- > 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 Mon Sep 13 14:21:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26786; Mon, 13 Sep 93 14:21:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19298; Mon, 13 Sep 93 14:09:28 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from red3.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19292; Mon, 13 Sep 93 14:09:26 -0700 Received: by red3.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20282; Mon, 13 Sep 93 14:09:22 -0700 Date: Mon, 13 Sep 1993 14:03:57 -0700 (PDT) From: David Wall Subject: Re: User Questions 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 I've noted one additional option below. --David Wall Computing & Communications...Client Services 3-8491 Univ. of Washington HG-45 davidw@u.washington.edu On Mon, 13 Sep 1993, David L Miller wrote: > > On Mon, 13 Sep 1993, John E. Burton Jr. wrote: > > > > 2. How do you set up the .pinerc or other files so that messages are > > ordered in Reverse order automatically as received? For example, I like > > to see the most recent messages at the top of the list instead of the > > older messages. Currently, our pine mailer puts the oldest messages first > > on the list in a folder. > > > You can use the Sort option to reverse the order of messages. You cannot > currently set a default sort order though. > You could get the effect you want by using an alias and command line option. In your .cshrc you could have this alias: alias pine 'pine -iz -sort R' From owner-pine-info@cac.washington.edu Tue Sep 14 11:39:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22900; Tue, 14 Sep 93 11:39:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28383; Tue, 14 Sep 93 11:19:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from netnews.ciesin.org by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28377; Tue, 14 Sep 93 11:19:25 -0700 Received: from superball.ciesin.org by mail.ciesin.org with SMTP id AA09461 (5.65c/IDA-1.4.4 for ); Tue, 14 Sep 1993 14:19:15 -0400 Date: Tue, 14 Sep 1993 14:17:06 -0400 (EDT) From: Viswanath Gopalakrishnan Subject: Maximum allowable length of addresses in pine To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there a limit on the number of characters in an address in pine ? I have this address which is 62 ( believe it or not) characters long. When I try entering this address in the To: field, I am able to enter all the charcters, but it gets chopped up when it is being sent out. Any clues ? Thanks Vishy From owner-pine-info@cac.washington.edu Tue Sep 14 11:59:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23481; Tue, 14 Sep 93 11:59:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28577; Tue, 14 Sep 93 11:49:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tardis.svsu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28571; Tue, 14 Sep 93 11:49:28 -0700 Received: by tardis.svsu.edu (5.57/Ultrix3.0-C) id AA16347; Tue, 14 Sep 93 14:49:15 -0400 Date: Tue, 14 Sep 1993 14:44:21 -0400 (EDT) From: "John J. Guettler" Subject: Re: Questions To: "Jeffrey M. Wolff" Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Actually, what I think is happening is that the names are being listed alphabetically by the alias name (Christy,I,Sarah), rather than by your actual first names. John J. Guettler Saginaw Valley State University On Sun, 12 Sep 1993, Jeffrey M. Wolff wrote: > Below is a partial output from .pine-debug* after I sent a message to test > a couple of problems I am having. This mail was sent to a distribution list > and my first question is why are these names being listed alphabetically by > their FIRST names. > > This is an excerpt from my .addressbook which shows the entries in question. > > Christy Allison, Christy piranha@jhunix.hcf.jhu.edu > Sarah Butcher, Sarah butcher95@alison.sbc.edu > Board District Board (Christy,I,Sarah) > I Wolff, Jeffrey M. jwolff@nyx.cs.du.edu > > As you can see, the aliases are entered in last name, first name format so > that they sort alphabetically on their last name in the list. That works > fine, but in the distribution list they sort on the first name. . .(text deleted) . > Debug output of the Pine program (at debug level 2). Version 3.05 > Sun Sep 12 09:35:53 1993 > > ***** MAIL SENT ***** > To: District Board -- Christy Allison , > "Jeffrey M. Wolff" , > Sarah Butcher > Subject: Information > Message ID: From owner-pine-info@cac.washington.edu Tue Sep 14 18:47:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05008; Tue, 14 Sep 93 18:47:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08577; Tue, 14 Sep 93 18:14:39 -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 AA08571; Tue, 14 Sep 93 18:14:36 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA10666; Tue, 14 Sep 93 20:14:33 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA14052; Wed, 15 Sep 93 09:09:26 +0800 Date: Wed, 15 Sep 1993 09:02:30 +0800 (TPE) From: Ed Greshko Subject: Questions related to PC pine.... To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, I've a few questions related to PC pine.... 1. Since PC pine is not windows based (future?) what program would be used to display GIF images? From where can that be ftp'd? 2. In a dial-up slip enviornment, how does one make the combination of PC pine and IMAP interoperate so that a user may "download" their messages and read them "off-line". 3. Being in Asia, we see "BOGUS DATE" displayed frequently since many places use Time Zones that are not official. Can this check be gotten around? Thanks.... 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 Wed Sep 15 12:45:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26448; Wed, 15 Sep 93 12:45:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18832; Wed, 15 Sep 93 12:35:47 -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 AA18826; Wed, 15 Sep 93 12:35:45 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA21310; Wed, 15 Sep 93 12:35:42 PDT Date: Wed, 15 Sep 1993 12:34:00 -0700 (PDT) From: Steve Hubert Subject: Re: Maximum allowable length of addresses in pine To: Viswanath Gopalakrishnan Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Does the message actually get sent correctly? I believe that the display of the address may look like it is chopped up in the composer but that it is only the display that is wrong. Steve Hubert On Tue, 14 Sep 1993, Viswanath Gopalakrishnan wrote: > > Is there a limit on the number of characters in an address in pine ? > > I have this address which is 62 ( believe it or not) characters long. When > I try entering this address in the To: field, I am able to enter all the > charcters, but it gets chopped up when it is being sent out. > > Any clues ? > > Thanks > > Vishy > > From owner-pine-info@cac.washington.edu Wed Sep 15 12:49:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26490; Wed, 15 Sep 93 12:49:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18930; Wed, 15 Sep 93 12:41:28 -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 AA18924; Wed, 15 Sep 93 12:41:26 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA21332; Wed, 15 Sep 93 12:41:13 PDT Date: Wed, 15 Sep 1993 12:39:14 -0700 (PDT) From: Steve Hubert Subject: Re: BUG in Addressbook handling To: Steve Woodyatt Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 10 Sep 1993, Steve Woodyatt wrote: > > Hi all, > > Just a warning about the use of long addressbook lists - they cause Pine > to crash. I'm not sure whether it's simply the number of entries, or what. Some addressbook bugs have been fixed since 3.07, though it isn't altogether clear (to me) which bugs were fixed. In particular, Steve's addressbook which caused the problem he reported in 3.07 no longer causes a problem in the soon-to-be-released 3.85. Steve Hubert From owner-pine-info@cac.washington.edu Wed Sep 15 16:08:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03760; Wed, 15 Sep 93 16:08:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22088; Wed, 15 Sep 93 15:51:35 -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 AA22082; Wed, 15 Sep 93 15:51:33 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA21854; Wed, 15 Sep 93 15:50:17 PDT Date: Wed, 15 Sep 1993 15:48:24 -0700 (PDT) From: Steve Hubert Subject: Re: Alias problem To: "Jeffrey M. Wolff" Cc: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is fixed in the soon-to-be-released version 3.85. The mini-window where you enter the address will scroll to the right if you bump into the right hand edge. Thanks. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 8 Sep 1993, Jeffrey M. Wolff wrote: > Has anyone other than me been unsucessful in entering an X400 gateway > address to the addressbook? > > I have a person that need added to a distribution list, but I cannot > because his X400 address is too long for Pine. From owner-pine-info@cac.washington.edu Wed Sep 15 16:27:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04461; Wed, 15 Sep 93 16:27:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22645; Wed, 15 Sep 93 16:18:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tenorman.uoregon.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22623; Wed, 15 Sep 93 16:18:09 -0700 Received: by tenorman.uoregon.edu (5.0/UofO NetSvc-12/02/92 SMI-SVR4) id AA00763; Wed, 15 Sep 93 16:17:31 PDT Date: Wed, 15 Sep 93 16:17:31 PDT From: jneher@darkwing.uoregon.edu (Jonathan Neher) Message-Id: <9309152317.AA00763@tenorman.uoregon.edu> To: pine-info@cac.washington.edu Subject: pine for Solaris2.X X-Sun-Charset: US-ASCII Content-Length: 182 I've heard the the next version of pine will support Sun Solaris 2.2. Does anyone know the timeframe for this release? Please reply via e-mail since I don't subscribe. Thanks, Jon From owner-pine-info@cac.washington.edu Wed Sep 15 16:38:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04963; Wed, 15 Sep 93 16:38:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22825; Wed, 15 Sep 93 16:28: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 AA22819; Wed, 15 Sep 93 16:28:57 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06880; Wed, 15 Sep 93 16:28:55 -0700 Date: Wed, 15 Sep 1993 16:28:29 -0700 (PDT) From: David L Miller Subject: Re: pine for Solaris2.X To: Jonathan Neher Cc: pine-info@cac.washington.edu In-Reply-To: <9309152317.AA00763@tenorman.uoregon.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Next week. |\ | |\/| 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, 15 Sep 1993, Jonathan Neher wrote: > I've heard the the next version of pine will support Sun Solaris 2.2. > Does anyone know the timeframe for this release? > Please reply via e-mail since I don't subscribe. > > Thanks, > > Jon > From owner-pine-info@cac.washington.edu Thu Sep 16 07:24:04 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21068; Thu, 16 Sep 93 07:24:04 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09580; Thu, 16 Sep 93 07:11:33 -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 AA09574; Thu, 16 Sep 93 07:11:32 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA02593; Thu, 16 Sep 93 10:11:29 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA07978; Thu, 16 Sep 93 10:11:28 -0400 Date: Thu, 16 Sep 1993 10:10:54 -0400 (EDT) From: Mike Kuniavsky Reply-To: Mike Kuniavsky Subject: ansi-printing emulators To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Does anyone have a canonical list of what terminal emulation software supports the "attached-to-ansi" printing method (and, equally importantly, what does not)? If such as list doesn't exist, then I'd be willing to put one together if people send me their experiences. Thanks. Mike Kuniavsky ITD/US UNIX Support mikek@umich.edu (313)764-1178 From owner-pine-info@cac.washington.edu Thu Sep 16 07:58:04 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21814; Thu, 16 Sep 93 07:58:04 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09768; Thu, 16 Sep 93 07:48:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sulu.biostat.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09762; Thu, 16 Sep 93 07:48:56 -0700 Received: by sulu.biostat.washington.edu (5.64/UW-NDC Revision: 2.21 ) id AA21234; Thu, 16 Sep 93 07:48:12 -0700 From: Nancy McGough Message-Id: <9309161448.AA21234@sulu.biostat.washington.edu> Subject: Re: ansi-printing emulators To: pine-info@cac.washington.edu Date: Thu, 16 Sep 93 7:48:12 PDT In-Reply-To: ; from "Mike Kuniavsky" at Sep 16, 93 10:10 am Reply-To: Nancy McGough X-Mailer: ELM [version 2.3 PL11] On a related note, does anyone know the relation between standalone utility ansiprint and pine? E.g., does pine use the same script that ansiprint uses? Anyone know of an anon ftp site for ansiprint that I can point people to? Thanks, Nancy PS - I don't think Pine's "attached-to-ansi" or ansiprint work with Windows Terminal; they do work with Kermit. Quoting Mike Kuniavsky, > Does anyone have a canonical list of what terminal emulation software > supports the "attached-to-ansi" printing method (and, equally importantly, > what does not)? If such as list doesn't exist, then I'd be willing to put > one together if people send me their experiences. Thanks. > > Mike Kuniavsky ITD/US UNIX Support > mikek@umich.edu (313)764-1178 From owner-pine-info@cac.washington.edu Thu Sep 16 08:59:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23879; Thu, 16 Sep 93 08:59:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10080; Thu, 16 Sep 93 08:45:40 -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 AA10074; Thu, 16 Sep 93 08:45:38 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA13732; Thu, 16 Sep 1993 10:49:02 -0500 Date: Thu, 16 Sep 1993 10:47:47 -0500 (CDT) From: "Robert A. Hayden" Subject: Attached-to-ansi To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When I was using WinQVT for Windows (a vt100 communications program), printing to attached-to-ansi woul dump it to the printer I had on LPT1. Of course, now that I'm using linux and connecting with a different program, it doesn't work any more. Oh well. {[> Robert A. Hayden ____ EARTH <]} {[> \ /__ smog | bricks <]} {[> aq650@slc4.INS.CWRU.Edu \/ / AIR -- mud -- FIRE <]} {[> hayden@krypton.mankato.msus.edu \/ beer | tequila <]} -=-=- WATER -=-=- 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 Sep 16 09:06:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24440; Thu, 16 Sep 93 09:06:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01602; Thu, 16 Sep 93 08:50:49 -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 AA01596; Thu, 16 Sep 93 08:50:47 -0700 Received: by stein3.u.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10540; Thu, 16 Sep 93 08:50:47 -0700 X-Sender: mramey@stein3.u.washington.edu Date: Thu, 16 Sep 1993 08:48:57 -0700 (PDT) From: Mike Ramey Reply-To: Mike Ramey Subject: Re: ansi-printing emulators -- for Postscript-only printers ??? To: pine-info@cac.washington.edu In-Reply-To: <9309161448.AA21234@sulu.biostat.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii I have several customers who HP LaserJet printers with the (old?) HP Postscript cartridges which will process ONLY Postscript input. Currently if they try to ansi-print their (ASCII) messages from pine, the Postscript-only printer ignores the print request. [ Removing the Postscript cartridge - requiring power-off/on - is not an option. ] Has anyone figured out out to use the pine 'Print' (L) command with a Postscript-only [ HP LaserJet ] printer ??? -mr From owner-pine-info@cac.washington.edu Thu Sep 16 09:13:34 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24626; Thu, 16 Sep 93 09:13:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10142; Thu, 16 Sep 93 08:58:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10136; Thu, 16 Sep 93 08:58:05 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA19229; Thu, 16 Sep 93 08:58:32 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA07854; Thu, 16 Sep 93 09:00:30 -0700 Date: Thu, 16 Sep 1993 08:59:41 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: ansi-printing emulators To: Mike Kuniavsky Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 16 Sep 1993, Mike Kuniavsky wrote: > Does anyone have a canonical list of what terminal emulation software > supports the "attached-to-ansi" printing method (and, equally importantly, > what does not)? If such as list doesn't exist, then I'd be willing to put > one together if people send me their experiences. Thanks. I have successfully used Crosstalk for Windows, Qmodem, WinQVT, and WinQTV-Net. > > Mike Kuniavsky ITD/US UNIX Support > mikek@umich.edu (313)764-1178 > > > > > > /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Thu Sep 16 09:14:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24673; Thu, 16 Sep 93 09:14:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01692; Thu, 16 Sep 93 08:53:10 -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 AA01684; Thu, 16 Sep 93 08:53:08 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20672; Thu, 16 Sep 93 08:53:03 -0700 Date: Thu, 16 Sep 1993 08:50:34 -0700 (PDT) From: David L Miller Subject: Re: ansi-printing emulators To: Nancy McGough Cc: pine-info@cac.washington.edu In-Reply-To: <9309161448.AA21234@sulu.biostat.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The pine distribution contains an ansiprint replacement in the contrib directory. The following is stripped from the code: /* * ansiprt.c * * Simple filter to wrap ANSI media copy escape sequences around * text on stdin. Writes /dev/tty to get around things that might be * trapping stdout. This is actually a feature because it was written * to be used with pine's personal print option set up to take "enscript" * output and send it displayward to be captured/printed to a postscript * device. Pine, of course, uses popen() to invoke the personal print * command, and interprets stdout as diagnostic messages from the command. * * Michael Seibel, mikes@cac.washington.edu * * 21 Apr 92 * */ |\ | |\/| 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, 16 Sep 1993, Nancy McGough wrote: > On a related note, does anyone know the relation between standalone > utility ansiprint and pine? E.g., does pine use the same script that > ansiprint uses? Anyone know of an anon ftp site for ansiprint that > I can point people to? > > Thanks, > Nancy > > > PS - I don't think Pine's "attached-to-ansi" or ansiprint work with > Windows Terminal; they do work with Kermit. > > > Quoting Mike Kuniavsky, > > Does anyone have a canonical list of what terminal emulation software > > supports the "attached-to-ansi" printing method (and, equally importantly, > > what does not)? If such as list doesn't exist, then I'd be willing to put > > one together if people send me their experiences. Thanks. > > > > Mike Kuniavsky ITD/US UNIX Support > > mikek@umich.edu (313)764-1178 > From owner-pine-info@cac.washington.edu Thu Sep 16 10:02:34 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25984; Thu, 16 Sep 93 10:02:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10405; Thu, 16 Sep 93 09:45:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sulu.biostat.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10399; Thu, 16 Sep 93 09:45:05 -0700 Received: by sulu.biostat.washington.edu (5.64/UW-NDC Revision: 2.21 ) id AA21996; Thu, 16 Sep 93 09:44:21 -0700 From: Nancy McGough Message-Id: <9309161644.AA21996@sulu.biostat.washington.edu> Subject: Re: ansi-printing emulators -- for Postscript-only printers ??? To: pine-info@cac.washington.edu Date: Thu, 16 Sep 93 9:44:20 PDT In-Reply-To: ; from "Mike Ramey" at Sep 16, 93 8:48 am Reply-To: Nancy McGough X-Mailer: ELM [version 2.3 PL11] What about using option 3 (personally selected print command) and specifying: enscript | ansiprint Or if you want to be "gaudy" and save some paper: enscript -2r -G -fCourier7 | ansiprint Does this work? -Nancy Quoting Mike Ramey, > I have several customers who HP LaserJet printers with the (old?) > HP Postscript cartridges which will process ONLY Postscript input. > Currently if they try to ansi-print their (ASCII) messages from pine, > the Postscript-only printer ignores the print request. [ Removing the > Postscript cartridge - requiring power-off/on - is not an option. ] > Has anyone figured out out to use the pine 'Print' (L) command with a > Postscript-only [ HP LaserJet ] printer ??? -mr From owner-pine-info@cac.washington.edu Thu Sep 16 10:47:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27563; Thu, 16 Sep 93 10:47:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03444; Thu, 16 Sep 93 10:28:05 -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 AA03438; Thu, 16 Sep 93 10:28:04 -0700 Received: by stein1.u.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02387; Thu, 16 Sep 93 10:27:59 -0700 X-Sender: koolkid@stein1.u.washington.edu Date: Thu, 16 Sep 1993 10:19:35 -0700 (PDT) From: "Timothy F. Lee" Subject: Re: ansi-printing emulators -- for Postscript-only printers ??? To: Nancy McGough Cc: pine-info@cac.washington.edu In-Reply-To: <9309161644.AA21996@sulu.biostat.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii On Thu, 16 Sep 1993, Nancy McGough wrote: > What about using option 3 (personally selected print command) > and specifying: > enscript | ansiprint > Or if you want to be "gaudy" and save some paper: > enscript -2r -G -fCourier7 | ansiprint > Does this work? > -Nancy That technically wouldn't work because enscript wouldn't know where where to get it's input. A better method would be to write an external shell script, and call that script to from within Pine, when printing to a postscript only printer. Here is a "hack" that a friend and I worked out together. The only problem is that it tends to hang, when trying to ansiprint the enscripted file. Maybe someone on this list can offer some suggestions. As a consultant, I get many questions reguarding the printing of e-mail to postscript printers, so any help would be greatly appreciated. Thanks... ------------------------------- #!/bin/sh # # ansipsprint v1.0c # # Concept: Timothy Lee # Implementation: Jared Reisinger # Last Change: 08 Sep 1993 # # Overview # -------- # "ansipsprint" allows you to send regular files to local PostScript # printers which can't handle raw text. This is intended for use # with any program that would normally invoke "ansiprint" (or "ansiprt", # which Pine uses) to print a text file on a local printer. # # All flags and parameters used on the command line are passed verbatim # to "enscript", and stdin is also redirected, so "ansipsprint" will # accept the file either on the command line or through a pipe. ESC= # escape character OPEN=${ESC}[5i # open printer ANSI sequence CLOSE=${ESC}[4i # close printer ANSI sequence TEMPFILE=/usr/tmp/.ansipsprint$$ # temp file name enscript -p $TEMPFILE $@ <&0 > /dev/null 2>&1 # enscript to the temp file echo -n "${OPEN}" > /dev/tty # start printer cat $TEMPFILE > /dev/tty # send file to printer echo -n "${CLOSE}" > /dev/tty # stop printer rm -f $TEMPFILE # remove temp file echo -n "file has been sent" # exit message exit 0 # exit successfully! # The End! From owner-pine-info@cac.washington.edu Thu Sep 16 10:47:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27603; Thu, 16 Sep 93 10:47:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03476; Thu, 16 Sep 93 10: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 AA03466; Thu, 16 Sep 93 10:28:55 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA24160 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Thu, 16 Sep 93 12:27:36 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA15311; Thu, 16 Sep 93 12:27:35 CDT Date: Thu, 16 Sep 1993 12:26:02 -0500 (CDT) From: Matt Simmons Subject: Re: ansi-printing emulators To: "Jason R. Thorpe" Cc: Mike Kuniavsky , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 16 Sep 1993, Jason R. Thorpe wrote: > On Thu, 16 Sep 1993, Mike Kuniavsky wrote: > > Does anyone have a canonical list of what terminal emulation software > > supports the "attached-to-ansi" printing method (and, equally importantly, > > what does not)? If such as list doesn't exist, then I'd be willing to put > > one together if people send me their experiences. Thanks. > I have successfully used Crosstalk for Windows, Qmodem, WinQVT, and > WinQTV-Net. I have used it with Telix (MSDOS), Kermit (MSDOS), NCSA Telnet (MSDOS), and Jr-Comm (Amiga). Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || _____\________________________________________________||_________________ __/ High Gamma, Lambda Chi Alpha, Colony #099, Init Num 1193 _/ ACBU Projectionist Bradley University, Peoria, Illinois From owner-pine-info@cac.washington.edu Thu Sep 16 11:21:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28720; Thu, 16 Sep 93 11:21:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10842; Thu, 16 Sep 93 11:08:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bambam.u.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10836; Thu, 16 Sep 93 11:08:30 -0700 Received: by bambam.u.washington.edu (5.57/Ultrix3.0-C) id AA16652; Thu, 16 Sep 93 11:08:10 -0700 Date: Thu, 16 Sep 1993 11:06:36 -0700 (PDT) From: Il Hwan Oh Subject: Re: ansi-printing emulators -- for Postscript-only printers ??? To: "Timothy F. Lee" Cc: Nancy McGough , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You need to do enscript -p | ansiprt ansiprint doesn't work from pine, but ansiprt, which came with the pine distribution, does. On Thu, 16 Sep 1993, Timothy F. Lee wrote: > > On Thu, 16 Sep 1993, Nancy McGough wrote: > > What about using option 3 (personally selected print command) > > and specifying: > > enscript | ansiprint > > Or if you want to be "gaudy" and save some paper: > > enscript -2r -G -fCourier7 | ansiprint > > Does this work? > > -Nancy > > That technically wouldn't work because enscript wouldn't know > where where to get it's input. A better method would be to write an > external shell script, and call that script to from within Pine, when > printing to a postscript only printer. Here is a "hack" that a friend and > I worked out together. The only problem is that it tends to hang, when > trying to ansiprint the enscripted file. Maybe someone on this list can > offer some suggestions. As a consultant, I get many questions reguarding > the printing of e-mail to postscript printers, so any help would be > greatly appreciated. Thanks... > > ------------------------------- > > #!/bin/sh > # > # ansipsprint v1.0c > # > # Concept: Timothy Lee > # Implementation: Jared Reisinger > # Last Change: 08 Sep 1993 > # > # Overview > # -------- > # "ansipsprint" allows you to send regular files to local PostScript > # printers which can't handle raw text. This is intended for use > # with any program that would normally invoke "ansiprint" (or "ansiprt", > # which Pine uses) to print a text file on a local printer. > # > # All flags and parameters used on the command line are passed verbatim > # to "enscript", and stdin is also redirected, so "ansipsprint" will > # accept the file either on the command line or through a pipe. > > ESC= # escape character > > OPEN=${ESC}[5i # open printer ANSI sequence > CLOSE=${ESC}[4i # close printer ANSI sequence > > TEMPFILE=/usr/tmp/.ansipsprint$$ # temp file name > > enscript -p $TEMPFILE $@ <&0 > /dev/null 2>&1 # enscript to the temp file > > echo -n "${OPEN}" > /dev/tty # start printer > cat $TEMPFILE > /dev/tty # send file to printer > echo -n "${CLOSE}" > /dev/tty # stop printer > > rm -f $TEMPFILE # remove temp file > > echo -n "file has been sent" # exit message > exit 0 # exit successfully! > > # The End! > Il Hwan Oh | "You live and learn. Computer Facilities Manager | At any rate, you live." University of Washington, Tacoma | -- Douglas Adams iho@cac.washington.edu | From owner-pine-info@cac.washington.edu Thu Sep 16 11:52:50 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00943; Thu, 16 Sep 93 11:52:50 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10979; Thu, 16 Sep 93 11:37:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10973; Thu, 16 Sep 93 11:37:39 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA20441; Thu, 16 Sep 93 11:37:59 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA07980; Thu, 16 Sep 93 11:39:52 -0700 Date: Thu, 16 Sep 1993 11:39:08 -0700 (PDT) From: "Jason R. Thorpe" Reply-To: "Jason R. Thorpe" Subject: Re: ansi-printing emulators -- for Postscript-only printers ??? To: "Timothy F. Lee" Cc: Nancy McGough , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 16 Sep 1993, Timothy F. Lee wrote: > > On Thu, 16 Sep 1993, Nancy McGough wrote: > > What about using option 3 (personally selected print command) > > and specifying: > > enscript | ansiprint > > Or if you want to be "gaudy" and save some paper: > > enscript -2r -G -fCourier7 | ansiprint > > Does this work? > > -Nancy > > That technically wouldn't work because enscript wouldn't know > where where to get it's input. A better method would be to write an > external shell script, and call that script to from within Pine, when > printing to a postscript only printer. Here is a "hack" that a friend and > I worked out together. The only problem is that it tends to hang, when > trying to ansiprint the enscripted file. Maybe someone on this list can > offer some suggestions. As a consultant, I get many questions reguarding > the printing of e-mail to postscript printers, so any help would be > greatly appreciated. Thanks... Why not...I use something similar all the time... a2ps | lp -dlwrm9 works just fine...I guess it would depend on enscript being able to read stdin (which...I hope it can...) > > ------------------------------- > > #!/bin/sh > # > # ansipsprint v1.0c > # > # Concept: Timothy Lee > # Implementation: Jared Reisinger > # Last Change: 08 Sep 1993 > # > # Overview > # -------- > # "ansipsprint" allows you to send regular files to local PostScript > # printers which can't handle raw text. This is intended for use > # with any program that would normally invoke "ansiprint" (or "ansiprt", > # which Pine uses) to print a text file on a local printer. > # > # All flags and parameters used on the command line are passed verbatim > # to "enscript", and stdin is also redirected, so "ansipsprint" will > # accept the file either on the command line or through a pipe. > > ESC= # escape character > > OPEN=${ESC}[5i # open printer ANSI sequence > CLOSE=${ESC}[4i # close printer ANSI sequence > > TEMPFILE=/usr/tmp/.ansipsprint$$ # temp file name > > enscript -p $TEMPFILE $@ <&0 > /dev/null 2>&1 # enscript to the temp file > > echo -n "${OPEN}" > /dev/tty # start printer > cat $TEMPFILE > /dev/tty # send file to printer > echo -n "${CLOSE}" > /dev/tty # stop printer > > rm -f $TEMPFILE # remove temp file > > echo -n "file has been sent" # exit message > exit 0 # exit successfully! > > # The End! > /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Thu Sep 16 15:06:51 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07864; Thu, 16 Sep 93 15:06:51 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08186; Thu, 16 Sep 93 14:47: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 AA08180; Thu, 16 Sep 93 14:47:10 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA22477 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Thu, 16 Sep 93 16:47:08 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA22623; Thu, 16 Sep 93 16:47:07 CDT Date: Thu, 16 Sep 93 16:47:07 CDT From: zarthac@cs1.bradley.edu (Matt Simmons) Message-Id: <9309162147.AA22623@cs1.bradley.edu> To: pine-info@cac.washington.edu To: pine-info@cac.washington.edu Subject: Re: Mail Newsgroups: bu.banter,bu.help Organization: WDW Monorail Driver Wannabe Reply-To: zarthac@cs1.bradley.edu X-Newsreader: TIN [version 1.2 PL1] In article <27a4h6$kkk@bradley.bradley.edu> Pete Hartman wrote: : In <27a351$j0q@bradley.bradley.edu> pwh@bradley.bradley.edu (Pete Hartman) writes: : >I'm double checking it at the moment. I'll also be checking and posting : >about when the last good backup was so that if you lost mail I might be : >able to recover some or all of it. I do know that last night's scheduled : >full backup didn't get done, so at the least I *cannot* restore any mail : >from yesterday. : The last good backup appears to be dated the 11th. That would be very : early Saturday morning. I cannot restore any mail or files created : since then. : One bit of advice for mail: if you enter your mailbox, and do NOT see : the number of messages you think you are supposed to have, ALWAYS exit : without re-writing your mailbox. In dmail, that's "e" for "exit". I : have no idea what the equivalent is in elm or pine. : -- : Pete Hartman Bradley University pwh@bradley.bradley.edu : The animal that coils in a circle is the serpent; : that's why so many cults and myths of the serpent exist, because it's hard : to represent the return of the sun by the coiling of a hippopotamus. Is it possible to exit pine w/o writing the mailbox? i.e. an emergency stop or something like that... Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/You don't understand, there are so many fish in this pond we call school, _/and when I hook the littlest minnow, they expect me to reel them in. --Brent From owner-pine-info@cac.washington.edu Thu Sep 16 17:53:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12266; Thu, 16 Sep 93 17:53:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13168; Thu, 16 Sep 93 17:35:15 -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 AA13162; Thu, 16 Sep 93 17:35:05 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA05647; Thu, 16 Sep 93 20:35:02 -0400 Received: from isavax.UUCP by uucp3.uu.net with UUCP/RMAIL (queueing-rmail) id 203304.19662; Thu, 16 Sep 1993 20:33:04 EDT From: gc%isag1@uunet.UU.NET (George Colt) Message-Id: <9309162336.AA02801@isag1.isa.com> Subject: Re: ansi-printing emulators To: pine-info@cac.washington.edu Date: Thu, 16 Sep 1993 19:36:47 -0400 (EDT) In-Reply-To: from "Matt Simmons" at Sep 16, 93 12:26:02 pm Reply-To: gc%isag1@uunet.UU.NET X-Pmrqc: 1 X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 804 >From the keyboard of Matt Simmons: > On Thu, 16 Sep 1993, Jason R. Thorpe wrote: > > On Thu, 16 Sep 1993, Mike Kuniavsky wrote: > > > Does anyone have a canonical list of what terminal emulation software > > > supports the "attached-to-ansi" printing method (and, equally importantly, > > > what does not)? If such as list doesn't exist, then I'd be willing to put > > > one together if people send me their experiences. Thanks. > > I have successfully used Crosstalk for Windows, Qmodem, WinQVT, and > > WinQTV-Net. > I have used it with Telix (MSDOS), Kermit (MSDOS), NCSA Telnet (MSDOS), > and Jr-Comm (Amiga). Works well with CUTC and Reflection, too. -- | George Colt ISA, Inc. | | Email : colt@isag1.isa.com Chesapeake, VA. | From owner-pine-info@cac.washington.edu Fri Sep 17 09:01:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28031; Fri, 17 Sep 93 09:01:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17394; Fri, 17 Sep 93 08:45:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [192.220.128.14] by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17384; Fri, 17 Sep 93 08:44:55 -0700 Received: by nethost.multnomah.lib.or.us (4.1/1.34) id AA17891; Fri, 17 Sep 93 08:50:20 PDT Date: Fri, 17 Sep 1993 08:48:22 -0700 (PDT) From: Brian Williams Subject: Re: ansi-printing emulators To: George Colt Cc: pine-info@cac.washington.edu In-Reply-To: <9309162336.AA02801@isag1.isa.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 16 Sep 1993, George Colt wrote: > >From the keyboard of Matt Simmons: > > On Thu, 16 Sep 1993, Jason R. Thorpe wrote: > > > On Thu, 16 Sep 1993, Mike Kuniavsky wrote: > > > > Does anyone have a canonical list of what terminal emulation software > > > > supports the "attached-to-ansi" printing method (and, equally importantly, > > > > what does not)? If such as list doesn't exist, then I'd be willing to put > > > > one together if people send me their experiences. Thanks. > > > I have successfully used Crosstalk for Windows, Qmodem, WinQVT, and > > > WinQTV-Net. > > I have used it with Telix (MSDOS), Kermit (MSDOS), NCSA Telnet (MSDOS), > > and Jr-Comm (Amiga). > > Works well with CUTC and Reflection, too. Works ok with Procomm (DOS) and Microphone (Mac). 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 From owner-pine-info@cac.washington.edu Fri Sep 17 09:17:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28685; Fri, 17 Sep 93 09:17:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17827; Fri, 17 Sep 93 09:05:43 -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 AA17819; Fri, 17 Sep 93 09:05:41 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA22844; Fri, 17 Sep 93 09:05:39 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA19968; Fri, 17 Sep 93 09:05:35 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA13668; Fri, 17 Sep 93 09:05:34 PDT Date: Fri, 17 Sep 93 09:05:34 PDT From: ekurgpol@Law.USC.EDU (Elmar Kurgpold) Message-Id: <9309171605.AA13668@develop.Law.USC.EDU> To: pine-info@cac.washington.edu, mikek@css.itd.umich.edu Subject: Re: ansi-printing emulators > Does anyone have a canonical list of what terminal emulation software > supports the "attached-to-ansi" printing method (and, equally importantly, > what does not)? If such as list doesn't exist, then I'd be willing to put > one together if people send me their experiences. Thanks. > > Mike Kuniavsky ITD/US UNIX Support > mikek@umich.edu (313)764-1178 Mike, I also have been successful with Procomm (2.4, I think) for the PC. We also use PC-NFS, and version 4.0 telnet.exe does not support it. Version 5.0 telnet does very nicely though. ------------------------------------- | 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 Fri Sep 17 20:08:55 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18492; Fri, 17 Sep 93 20:08:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27148; Fri, 17 Sep 93 19:53:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hellcow.css.itd.umich.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27142; Fri, 17 Sep 93 19:53:51 -0700 Received: by hellcow.css.itd.umich.edu (4.1/2.25) id AA07896; Fri, 17 Sep 93 22:54:42 EDT Message-Id: <9309180254.AA07896@hellcow.css.itd.umich.edu> Date: Fri, 17 Sep 93 22:54:42 EDT From: "Paul Southworth" To: pine-info@cac.washington.edu Subject: pine and shlibs Have pine developers considered creating shared libraries for use in pine? Perhaps a libpico shlib? Seems like pine is getting really *big*. Like, a couple more revisions down the road seems like it will approach the size of the x11r5 X server... From owner-pine-info@cac.washington.edu Sat Sep 18 12:54:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29744; Sat, 18 Sep 93 12:54:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23089; Sat, 18 Sep 93 12:44:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23083; Sat, 18 Sep 93 12:44:09 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA23339; Sat, 18 Sep 93 12:44:57 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA16040; Sat, 18 Sep 93 12:46:54 -0700 Date: Sat, 18 Sep 1993 12:44:40 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: pine and shlibs To: Paul Southworth Cc: pine-info@cac.washington.edu In-Reply-To: <9309180254.AA07896@hellcow.css.itd.umich.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 17 Sep 1993, Paul Southworth wrote: > Have pine developers considered creating shared libraries for use > in pine? Perhaps a libpico shlib? Seems like pine is getting really > *big*. Like, a couple more revisions down the road seems like it > will approach the size of the x11r5 X server... This is also a concern of ours...Pine is definitely a resource hog (but that doesn't mean that I don't think it's a cool mailer...) When 80 or so users are using pine on one of our Sequents, 128Meg memory is a little shy... /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ From owner-pine-info@cac.washington.edu Sat Sep 18 15:47:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01571; Sat, 18 Sep 93 15:47:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03015; Sat, 18 Sep 93 15:38:36 -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 AA03009; Sat, 18 Sep 93 15:38:35 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24211; Sat, 18 Sep 93 15:38:32 -0700 Date: Sat, 18 Sep 1993 14:14:32 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: pine and shlibs To: "Jason R. Thorpe" Cc: Paul Southworth , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Jason and Paul, I have two questions and two comments. The questions are concerned with how much physical memory is used by the code itself; the comments concern memory required for Pine's *data*... 1. If one is using a *reasonable* version of Unix that provides for sharing text (code) segments by all users of the system, what is the advantage of shared libraries in this particular case? (I'm not asking Why shared libraries in general? which I think I understand; I just don't see the benefit for Pine in the normal VM case.) 2. Does anyone know for sure that Sequent PTX *does* support shared code segments? We have a large Sequent (typical peaks of 800 simultaneous users, almost all running Pine) and the system *is* memory hungry --but we've seen conflicting data on whether or not the code segment is really being shared amongst all the Pine processes... Either way, we must also consider the issue of memory for data: 3. The Berkeley mailbox driver, the one normally used by Pine, assumes the existence of a decent virtual memory system. It therefore reads the entire mailbox into virtual memory and relies on the paging system for optimal 'conservation' of physical memory. Unfortunately, we have not had time to do any careful analysis of working sets or Pine behaviors that might inadvertently keep the working sets larger than necessary. However... 4. If you are willing to forego INBOX compatibility with other mailers that require Bky format, then you can use Pine with the "tenex2" driver. Upon startup, this driver pulls mail from /usr/spool/mail, and puts it into a file called ~/mail.txt in a format first used for Tenex mailers. The message delimiters contain a length field and a fixed-length flags field, so that updating message state does not require rewriting the mailbox. In this case, the driver builds a list of pointers to the beginning of messages on disk, and does not read the entire mailbox into VM. In this mailbox format, text searches --which Pine doesn't support yet, but will someday-- are slower, but most other operations are faster. Moreover, the typical process RSS will be smaller than when using the Bky driver. (Whether that *should* matter on a good VM system is another question...) Pine 3.85 uses the Tenex2 driver whenever the file ~/mail.txt exists, so if you want to try this out: -pick up 3.85 next week (earlier versions lack the latest tenex driver) -touch mail.txt -Run pine. Note that this operation is not easily reversible; that is, you can't just cat mail.txt back to /usr/spool/mail if you don't want to use the Tenex driver any more. -teg p.s. the comparison to X program sizes was a bit of a low blow! Consider: 213 shiva2:bin> size xclock pine.new.new text data bss dec hex 798720 163840 30544 993104 f2750 xclock 757760 303104 82736 1143600 117330 pine.new.new So in terms of code size, we have another 40K-worth of code to write before we've even matched xclock!! :) On Sat, 18 Sep 1993, Jason R. Thorpe wrote: > On Fri, 17 Sep 1993, Paul Southworth wrote: > > > Have pine developers considered creating shared libraries for use > > in pine? Perhaps a libpico shlib? Seems like pine is getting really > > *big*. Like, a couple more revisions down the road seems like it > > will approach the size of the x11r5 X server... > > This is also a concern of ours...Pine is definitely a resource hog (but > that doesn't mean that I don't think it's a cool mailer...) When 80 or so > users are using pine on one of our Sequents, 128Meg memory is a little shy... > > /***************************************************************************** > Jason R. Thorpe - OSU Computer Science Support Staff > Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu > *****************************************************************************/ > > > From owner-pine-info@cac.washington.edu Sat Sep 18 17:28:52 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02437; Sat, 18 Sep 93 17:28:52 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23910; Sat, 18 Sep 93 17:22:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23904; Sat, 18 Sep 93 17:22:18 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA24464; Sat, 18 Sep 93 17:22:11 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA17483; Sat, 18 Sep 93 17:24:08 -0700 Date: Sat, 18 Sep 1993 17:21:05 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: pine and shlibs To: Terry Gray Cc: "Jason R. Thorpe" , Paul Southworth , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Terry... I see your point...thank you... I will check with Sequent as to whether or not PTX supports shared code segments... Later... /***************************************************************************** Jason R. Thorpe - OSU Computer Science Support Staff Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu *****************************************************************************/ On Sat, 18 Sep 1993, Terry Gray wrote: > Jason and Paul, > I have two questions and two comments. The questions are concerned with how > much physical memory is used by the code itself; the comments concern memory > required for Pine's *data*... > > 1. If one is using a *reasonable* version of Unix that provides for sharing > text (code) segments by all users of the system, what is the advantage of > shared libraries in this particular case? (I'm not asking Why shared > libraries in general? which I think I understand; I just don't see the > benefit for Pine in the normal VM case.) > > 2. Does anyone know for sure that Sequent PTX *does* support shared code > segments? We have a large Sequent (typical peaks of 800 simultaneous users, > almost all running Pine) and the system *is* memory hungry --but we've seen > conflicting data on whether or not the code segment is really being shared > amongst all the Pine processes... > > Either way, we must also consider the issue of memory for data: > > 3. The Berkeley mailbox driver, the one normally used by Pine, assumes the > existence of a decent virtual memory system. It therefore reads the entire > mailbox into virtual memory and relies on the paging system for optimal > 'conservation' of physical memory. Unfortunately, we have not had time to do > any careful analysis of working sets or Pine behaviors that might > inadvertently keep the working sets larger than necessary. However... > > 4. If you are willing to forego INBOX compatibility with other mailers that > require Bky format, then you can use Pine with the "tenex2" driver. Upon > startup, this driver pulls mail from /usr/spool/mail, and puts it into a file > called ~/mail.txt in a format first used for Tenex mailers. The message > delimiters contain a length field and a fixed-length flags field, so that > updating message state does not require rewriting the mailbox. In this case, > the driver builds a list of pointers to the beginning of messages on disk, > and does not read the entire mailbox into VM. In this mailbox format, text > searches --which Pine doesn't support yet, but will someday-- are slower, but > most other operations are faster. Moreover, the typical process RSS will be > smaller than when using the Bky driver. (Whether that *should* matter on a > good VM system is another question...) > > Pine 3.85 uses the Tenex2 driver whenever the file ~/mail.txt exists, so if > you want to try this out: > -pick up 3.85 next week (earlier versions lack the latest tenex driver) > -touch mail.txt > -Run pine. > > Note that this operation is not easily reversible; that is, you can't > just cat mail.txt back to /usr/spool/mail if you don't want to use the > Tenex driver any more. > > -teg > > p.s. the comparison to X program sizes was a bit of a low blow! Consider: > > 213 shiva2:bin> size xclock pine.new.new > text data bss dec hex > 798720 163840 30544 993104 f2750 xclock > 757760 303104 82736 1143600 117330 pine.new.new > > So in terms of code size, we have another 40K-worth of code to write > before we've even matched xclock!! :) > > On Sat, 18 Sep 1993, Jason R. Thorpe wrote: > > > On Fri, 17 Sep 1993, Paul Southworth wrote: > > > > > Have pine developers considered creating shared libraries for use > > > in pine? Perhaps a libpico shlib? Seems like pine is getting really > > > *big*. Like, a couple more revisions down the road seems like it > > > will approach the size of the x11r5 X server... > > > > This is also a concern of ours...Pine is definitely a resource hog (but > > that doesn't mean that I don't think it's a cool mailer...) When 80 or so > > users are using pine on one of our Sequents, 128Meg memory is a little shy... > > > > /***************************************************************************** > > Jason R. Thorpe - OSU Computer Science Support Staff > > Bellnet: (503) 623-8514 Internet: thorpej@prism.cs.orst.edu > > *****************************************************************************/ > > > > > > > From owner-pine-info@cac.washington.edu Sat Sep 18 19:08:30 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03561; Sat, 18 Sep 93 19:08:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24181; Sat, 18 Sep 93 19:02:18 -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 AA24175; Sat, 18 Sep 93 19:02:16 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA15728; Sat, 18 Sep 1993 21:05:46 -0500 Date: Sat, 18 Sep 1993 20:44:31 -0500 (CDT) From: "Robert A. Hayden" Subject: Interfacing to PGP To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I don't remember this being discussed in the past, but I figure I'll bring it up. :-) Is there any plans in the future (most probably too late for 3.85) to allow transparent use of PGP from within pine? (ie, being able to sign and/or encrypt the message). For the most part, it seems it would be pretty easy to do this, simply passing the mail message through PGP prior to it it being sent on its way. -- As for how to do it from a use standpoint? Make it an Old-Growth option or have to user define 'pgp=yes' in .pinerc. Then, to invoke a pgp mailing, you would press something like shift-C or perhaps some other key. The message would be composed normally, but, when you exit, you are asked 'Encrypt (y/n) [n]'. Pressing return defaults to no encryption and simply sends out the message with your PGP signature [ie, pgp -sa filename] If you ask for encryption, it seeks your public-keyring, matching the people you are mailing to to their public keys. It also adds your PGP signature. [ie, pgp -esa filename address1 address2 address3 ...] -- er . . . In any case, it's a feature I would find most usefule and I'd think it would be a pretty easy thing to add. I appreciate any comments. {[> Robert A. Hayden ____ <[} #include {[> \ /__ <]} PGP Key Available on Request {[> aq650@slc4.INS.CWRU.Edu \/ / <]} -=-=-=- {[> hayden@krypton.mankato.msus.edu \/ <]} Question Authority -=-=-=-=-=- 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 Sep 19 00:05:03 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06267; Sun, 19 Sep 93 00:05:03 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05195; Sat, 18 Sep 93 23:30: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 AA05189; Sat, 18 Sep 93 23:30:38 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26406; Sat, 18 Sep 93 23:30:34 -0700 Date: Sat, 18 Sep 1993 23:26:26 -0700 (PDT) From: Terry Gray Subject: Re: Questions To: "John J. Guettler" Cc: "Jeffrey M. Wolff" , Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It's even simpler than that: they show up in the address in the same order that they were defined in the "Board" alias... -teg On Tue, 14 Sep 1993, John J. Guettler wrote: > Actually, what I think is happening is that the names are being listed > alphabetically by the alias name (Christy,I,Sarah), rather than by your > actual first names. > > John J. Guettler > Saginaw Valley State University > > On Sun, 12 Sep 1993, Jeffrey M. Wolff wrote: > > > Below is a partial output from .pine-debug* after I sent a message to test > > a couple of problems I am having. This mail was sent to a distribution list > > and my first question is why are these names being listed alphabetically by > > their FIRST names. > > > > This is an excerpt from my .addressbook which shows the entries in question. > > > > Christy Allison, Christy piranha@jhunix.hcf.jhu.edu > > Sarah Butcher, Sarah butcher95@alison.sbc.edu > > Board District Board (Christy,I,Sarah) > > I Wolff, Jeffrey M. jwolff@nyx.cs.du.edu > > > > As you can see, the aliases are entered in last name, first name format so > > that they sort alphabetically on their last name in the list. That works > > fine, but in the distribution list they sort on the first name. > . > .(text deleted) > . > > Debug output of the Pine program (at debug level 2). Version 3.05 > > Sun Sep 12 09:35:53 1993 > > > > ***** MAIL SENT ***** > > To: District Board -- Christy Allison , > > "Jeffrey M. Wolff" , > > Sarah Butcher > > Subject: Information > > Message ID: > > From owner-pine-info@cac.washington.edu Sun Sep 19 00:19:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06444; Sun, 19 Sep 93 00:19:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05269; Sat, 18 Sep 93 23:49:25 -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 AA05263; Sat, 18 Sep 93 23:49:24 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26486; Sat, 18 Sep 93 23:49:20 -0700 Date: Sat, 18 Sep 1993 23:38:50 -0700 (PDT) From: Terry Gray Subject: Re: Questions related to PC pine.... 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 On Wed, 15 Sep 1993, Ed Greshko wrote: > I've a few questions related to PC pine.... Ed, I didn't see a response to this, so will try to answer part of it... > 1. Since PC pine is not windows based (future?) what program would be > used to display GIF images? From where can that be ftp'd? I can't recall the name of the one we've been playing with, but I've never gotten it to work successfully from *within* PC-Pine, due to memory limitations... > 2. In a dial-up slip enviornment, how does one make the combination of > PC pine and IMAP interoperate so that a user may "download" their > messages and read them "off-line". With SLIP or PPP installed, and a dialup connection established, PC-Pine connects to the IMAP server in the usual way. The two things you will quickly discover are that: o Pine lacks a *convenient* way of saving all (or NEW) messages from your INBOX to a local folder on the PC, although you can do it one- at-a-time. o Once you have the desired messages saved locally, you can read them offline (by ignoring the error you get when Pine tries to talk to the IMAP server), but there is no way to reply or forward or compose new messages while offline. YET. Both of these issues will be addressed as soon as we can get to them. > 3. Being in Asia, we see "BOGUS DATE" displayed frequently since > many places use Time Zones that are not official. Can this check be > gotten around? I'll defer to our resident time-format expert, Mark... -teg From owner-pine-info@cac.washington.edu Sun Sep 19 18:27:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18661; Sun, 19 Sep 93 18:27:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10741; Sun, 19 Sep 93 18:19: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 AA10735; Sun, 19 Sep 93 18:19:35 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04308; Sun, 19 Sep 93 18:19:34 -0700 Date: Sun, 19 Sep 1993 18:17:57 -0700 (PDT) From: Steve Hubert Subject: Re: Questions To: Terry Gray Cc: "John J. Guettler" , "Jeffrey M. Wolff" , Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 18 Sep 1993, Terry Gray wrote: > It's even simpler than that: they show up in the address in the same order > that they were defined in the "Board" alias... > > -teg Well, yes, but I think they are being sorted when you define the list in the first place, so you don't get to choose the order by entering them in your desired order. (You could edit .addressbook and change the order, though.) Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle > On Tue, 14 Sep 1993, John J. Guettler wrote: > > > Actually, what I think is happening is that the names are being listed > > alphabetically by the alias name (Christy,I,Sarah), rather than by your > > actual first names. From owner-pine-info@cac.washington.edu Sun Sep 19 19:28:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19161; Sun, 19 Sep 93 19:28:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28503; Sun, 19 Sep 93 19:21:06 -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 AA28497; Sun, 19 Sep 93 19:21:03 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA29663; Sun, 19 Sep 93 19:21:01 -0700 Date: Sun, 19 Sep 1993 19:10:04 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Terry Gray Cc: "Jason R. Thorpe" , Paul Southworth , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To expand on Terry's message about the Berkeley mailbox driver, the reason why it is implemented that way has to do with a ``safe'' means of updating the mailbox. The problem is that in the mbox format, it is possible for a folder to grow after an update -- that is, the introduction of Status/X-Status header lines may result in a message becoming larger. Basically, there are two choices on how to deal with this: 1) use the disk for a second copy 2) use memory for a second copy System managers tend to use nasty things called ``disk quotas'' which would make strategy #1 useless for a folder that is any larger than the amount of unused space in the user's disk quota. The other problem with strategy #1 is that one of the locking schemes commonly used (remember, Pine has to use *all* forms of locking to be sure it interacts properly with other software) involves the use of an flock() system call, which in turn requires that the inode of the folder not change. So you can't just ``write the new version of the file then rename'' as you might do with an editor; you have to write the new version, then copy the new version on top of the old version. Hence strategy #2, which does the work in memory and merely uses the disk as a saved image of the memory version for future use. The tenex folder avoids this problem, because the fundamental nature of the format guarantees that no message can ever become larger than it currently is. The space for flags is pre-allocated and guaranteed to be in a single place, neither of which is true in mbox format. -- Mark -- From owner-pine-info@cac.washington.edu Mon Sep 20 02:09:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24622; Mon, 20 Sep 93 02:09:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29764; Mon, 20 Sep 93 02:01:21 -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 AA29758; Mon, 20 Sep 93 02:01:16 -0700 Received: from monera.newcastle.ac.uk (monera.ncl.ac.uk) by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 ) with SMTP; Mon, 20 Sep 1993 10:01:13 +0100 Date: Mon, 20 Sep 1993 09:44:10 +0100 (BST) From: Alan Ward Subject: Re: pine and shlibs 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 Trying out the Tenex2 driver.. I don't actually have a file mail.txt at the moment but I have had. Silly name to save to.. but I bet I'm not the only one. I might have got a surprise with 3.85? Alan Ward Alan.Ward@newcastle.ac.uk Department of Microbiology Medical School University of Newcastle upon Tyne NE2 4HH UK On Sat, 18 Sep 1993, Terry Gray wrote: > Pine 3.85 uses the Tenex2 driver whenever the file ~/mail.txt exists, so if > you want to try this out: > -pick up 3.85 next week (earlier versions lack the latest tenex driver) > -touch mail.txt > -Run pine. > > Note that this operation is not easily reversible; that is, you can't > just cat mail.txt back to /usr/spool/mail if you don't want to use the > Tenex driver any more. > > -teg > From owner-pine-info@cac.washington.edu Mon Sep 20 02:47:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25208; Mon, 20 Sep 93 02:47:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13077; Mon, 20 Sep 93 02:34:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from leeman.york.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13071; Mon, 20 Sep 93 02:34:05 -0700 Received: from tower.york.ac.uk by leeman.york.ac.uk with SMTP (PP) id <13381-0@leeman.york.ac.uk>; Mon, 20 Sep 1993 10:29:37 +0100 Received: from pippin.york.ac.uk by tower.york.ac.uk via SMTP (920330.SGI/920502.SGI) for @leeman.york.ac.uk:pine-info@cac.washington.edu id AA03654; Mon, 20 Sep 93 10:35:09 +0100 Date: Mon, 20 Sep 93 10:35:09 +0000 From: Mike Brudenell To: pine-info@cac.washington.edu Subject: Re: pine and shlibs Message-Id: In-Reply-To: Your message of Mon, 20 Sep 1993 09:44:10 +0100 (BST) Content-Type: TEXT/plain; charset=US-ASCII I concur... I sincerely hope that simple instructions are given for compiling up a version of Pine that does NOT include this "feature" (stronger words spring to mind!) I often use the filename "msg.txt" when exporting a message I need temporarily. I can quite well believe others using "mail.txt" with DISASTROUS consequences (in the developers' own words the process of converting to Tenex format is "not easily reversible!") Mike B-( > Trying out the Tenex2 driver.. > I don't actually have a file mail.txt at the moment but > I have had. Silly name to save to.. but I bet I'm not > the only one. I might have got a surprise with 3.85? > Alan Ward From owner-pine-info@cac.washington.edu Mon Sep 20 03:34:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26174; Mon, 20 Sep 93 03:34:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00108; Mon, 20 Sep 93 03:22:44 -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 AA00102; Mon, 20 Sep 93 03:22:40 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00308; Mon, 20 Sep 93 03:22:17 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA18872; Mon, 20 Sep 93 03:21:50 -0700 Date: Mon, 20 Sep 1993 03:20:48 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Alan Ward Cc: Terry Gray , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 20 Sep 1993 09:44:10 +0100 (BST), Alan Ward wrote: > Trying out the Tenex2 driver.. > I don't actually have a file mail.txt at the moment but I have had. > Silly name to save to.. but I bet I'm not the only one. I might have > got a surprise with 3.85? Pine has always had this behavior. So does mm, and so (I think) does babyl. From owner-pine-info@cac.washington.edu Mon Sep 20 03:48:42 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26310; Mon, 20 Sep 93 03:48:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00169; Mon, 20 Sep 93 03:37: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 AA00163; Mon, 20 Sep 93 03:37:25 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00315; Mon, 20 Sep 93 03:37:18 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA18917; Mon, 20 Sep 93 03:37:09 -0700 Date: Mon, 20 Sep 1993 03:22:39 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Mike Brudenell Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please explain how it is ``disastrous'' to have Pine decide to use a format of mail that is faster, more efficient, and uses *substantially* less memory? Pine will *NOT* convert formats just because a file named mail.txt exists on the home directory. The mail.txt file must be empty or in the proper format. If the file is non-empty and not in the proper format, then it is ignored. Other UNIX-based programs, such as zmail, babyl, mm, and mh, will convert your INBOX to their preferred formats just because you had the audacity to run those programs. Personally, I can't see why anyone would want to convert back (once you use Pine, you want to stick with Pine, right?), but the program to convert back is trivial (about 10 lines using c-client). It is ``not easily reversible'' only because Pine doesn't have a command to reverse (Pine's older brother, the MailManager application under NEXTSTEP, does have this feature). If you want, though, I'll write and post the program. From owner-pine-info@cac.washington.edu Mon Sep 20 04:49:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27318; Mon, 20 Sep 93 04:49:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13857; Mon, 20 Sep 93 04:31:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from leeman.york.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13851; Mon, 20 Sep 93 04:31:43 -0700 Received: from tower.york.ac.uk by leeman.york.ac.uk with SMTP (PP) id <14503-0@leeman.york.ac.uk>; Mon, 20 Sep 1993 12:27:15 +0100 Received: from pippin.york.ac.uk by tower.york.ac.uk via SMTP (920330.SGI/920502.SGI) for @leeman.york.ac.uk:pine-info@cac.washington.edu id AA09000; Mon, 20 Sep 93 12:32:48 +0100 Date: Mon, 20 Sep 93 12:32:48 +0000 From: Mike Brudenell To: Mark Crispin Subject: Re: Pine and the Tenex mail driver Cc: pine-info@cac.washington.edu Message-Id: In-Reply-To: Your message of Mon, 20 Sep 1993 03:22:39 -0700 (PDT) Content-Type: TEXT/plain; charset=US-ASCII > Please explain how it is ``disastrous'' to have Pine > decide to use a format of mail that is faster, more > efficient, and uses *substantially* less memory? We have a large proportion of "naive" users and not very many staff to support them (but doesn't everyone think this?!). Anything which can leap in and change things to a different format from the "norm" is unwelcome, opening the door for increased support problems. Also, we have a number of other little utilities which (perhaps stupidly, I admit:-) kind of assume that a person's mailbox is in the standard place for our system. I believe it should be a decision of the system administrators whether or not to switch to a particular format of mailbox, not the whim of some program. (Particularly one that doesn't make this clear in its documentation!) > Pine will *NOT* convert formats just because a file > named mail.txt exists on the home directory. The > mail.txt file must be empty or in the proper format. If > the file is non-empty and not in the proper format, then > it is ignored. At least this is a small mercy I suppose. So a judiciously placed "return (0)" or something when in the mail.txt file format test should suffice ;-) [See below] > Other UNIX-based programs, such as zmail, babyl, mm, and > mh, will convert your INBOX to their preferred formats > just because you had the audacity to run those > programs. None of which we use, nor have any intention of using. This argument is a red herring ("I only broke into the bank 'cause others do it, Guv!") IRIX on our Silicon Graphics kit comes with "mail" and "Mail" (BSD-type). And until now we have been using Elm. All of these happily use the same basic "inbox" format (and keep their sticky little fingers to themselves). > Personally, I can't see why anyone would want to convert > back (once you use Pine, you want to stick with Pine, > right?) Strange... that's what we thought about Elm! > but the program to convert back is trivial > (about 10 lines using c-client). Which has to be written, and explanation on how to backtrack given to those users who've run into the problem. No thanks! > It is ``not easily > reversible'' only because Pine doesn't have a command to > reverse (Pine's older brother, the MailManager > application under NEXTSTEP, does have this feature). If > you want, though, I'll write and post the program. Thanks for the offer, but I think I would prefer to look at disabling the feature (I'm sure I can hack it out fairly easily ... a One of main aims at migrating our existing userbase from Elm to Pine is to ease the learning curve and reduce support load (which Pine looks to be very good at). I see little reason to be forced ("encouraged"?) down a route whereby mailbox formats can potentially get munged from the system default format. STOP PRESS... I have just received the second message indicating that this is NOT a new feature due in the next release of Pine (as I had originally thought from previous messages) but is already present in 3.07. I've tried it... and it is! Consequently even as I type I am recompiling, specifically excluding the Tenex driver--thank heavens for modular programs! Sigh. Mike B-) From owner-pine-info@cac.washington.edu Mon Sep 20 05:18:54 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27866; Mon, 20 Sep 93 05:18:54 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00606; Mon, 20 Sep 93 05:07:43 -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 AA00600; Mon, 20 Sep 93 05:07:40 -0700 Received: from monera.newcastle.ac.uk (monera.ncl.ac.uk) by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Mon, 20 Sep 1993 13:07:36 +0100 Date: Mon, 20 Sep 1993 13:08:51 +0100 (BST) From: Alan Ward Subject: Re: pine and shlibs 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 On Mon, 20 Sep 1993, Mark Crispin wrote: > Please explain how it is ``disastrous'' to have Pine decide to use a format of > mail that is faster, more efficient, and uses *substantially* less memory? > > Pine will *NOT* convert formats just because a file named mail.txt exists on > the home directory. The mail.txt file must be empty or in the proper format. > If the file is non-empty and not in the proper format, then it is ignored. > That's the response I wanted Thanks Alan Ward Alan.Ward@newcastle.ac.uk Department of Microbiology Medical School University of Newcastle upon Tyne NE2 4HH From owner-pine-info@cac.washington.edu Mon Sep 20 08:18:36 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01082; Mon, 20 Sep 93 08:18:36 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00950; Mon, 20 Sep 93 06:57:02 -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 AA00944; Mon, 20 Sep 93 06:57:00 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA29594; Mon, 20 Sep 93 09:56:49 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA03031; Mon, 20 Sep 93 09:56:48 -0400 Date: Mon, 20 Sep 1993 09:51:20 -0400 (EDT) From: Alex Tang Subject: Re: pine and shlibs To: Mark Crispin Cc: Mike Brudenell , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 20 Sep 1993, Mark Crispin wrote: > Pine will *NOT* convert formats just because a file named mail.txt exists on > the home directory. The mail.txt file must be empty or in the proper format. > If the file is non-empty and not in the proper format, then it is ignored. Hmm. I did just check this feature. It's nice, but I do have one question to bring up. When pine is initiated using a Tenex2 style mailbox, and then an export message is done using the filename "mail.txt", it will ask (and be able to) append the message to the file mail.txt. This causes problems when pine is run again. It will say "bad message number X" where x is the last message, and then close the inbox. I know that for most people on this list, it would not be a problem, but for users who are not familiar with how the mailbox/mail.txt works, it could be a problem. Could it be possible to make pine disallow saving to mail.txt if it currently being used as the mailbox? > It is ``not easily reversible'' only > because Pine doesn't have a command to reverse (Pine's older brother, the > MailManager application under NEXTSTEP, does have this feature). If you want, > though, I'll write and post the program. I would be interested in this. Thanx...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 :) From owner-pine-info@cac.washington.edu Mon Sep 20 08:57:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02298; Mon, 20 Sep 93 08:57:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01430; Mon, 20 Sep 93 08:43:08 -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 AA01424; Mon, 20 Sep 93 08:43:05 -0700 Received: from irwin.cs.uoguelph.ca by herman.cs.uoguelph.ca with SMTP (1.37.109.4/16.2) id AA06624; Mon, 20 Sep 93 11:40:43 -0400 Received: by irwin.cs.uoguelph.ca (1.37.109.4/16.2) id AA13940; Mon, 20 Sep 93 11:41:26 -0400 Date: Mon, 20 Sep 1993 11:40:07 -0400 (EDT) From: Jim Lennie Subject: Archive for mail list To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there an archive of past messages sent to this list? From owner-pine-info@cac.washington.edu Mon Sep 20 10:12:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05469; Mon, 20 Sep 93 10:12:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17734; Mon, 20 Sep 93 09:46:40 -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 AA17728; Mon, 20 Sep 93 09:46:39 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17888; Mon, 20 Sep 93 09:46:38 -0700 Date: Mon, 20 Sep 1993 09:42:31 -0700 (PDT) From: David L Miller Subject: Getting pine.tar on DC600 tape. (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We do not have the resources to make tapes of Pine, but perhaps there is some kind sole out there who can help... I don't remember any reports one way or the other about CTIX, what is it similar to? |\ | |\/| 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 ---------- Forwarded message ---------- Date: Fri, 17 Sep 1993 17:05:13 -0400 (EDT) From: Yigal M. Rechtman To: owner-pine-info@cac.washington.edu Subject: Getting pine.tar on DC600 tape. Hello owners: I am VERY new to this list (this is my 1st posting 8-) ) and would like to describe a situation and some questions that arise from it: I have two old System/80 of Unisys runnig a CTIX O/S which is version 5.2.25; I am told I can not upgrdate the unix/ctix version due to chip incompitabilty. I would like to run a free-of-charge bbs using this old equipment and employ pine for this end. The questions that come to mind (my mind, that is): 1) Is it ok? 2) Can I get a version of pine.tar on a DC600, say if I send you one? 3) will it run on v.5.2.25? Thank you, Yigal Rechtman From owner-pine-info@cac.washington.edu Mon Sep 20 10:51:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07377; Mon, 20 Sep 93 10:51:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17218; Mon, 20 Sep 93 09:25:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from wuecl.wustl.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17212; Mon, 20 Sep 93 09:25:07 -0700 Return-Path: Received: by wuecl.wustl.edu (5.65a/1.35); id AA22224; Mon, 20 Sep 93 11:24:49 -0500 Date: Mon, 20 Sep 1993 11:21:43 -0500 (CDT) From: Chris Dunphy Subject: mail.txt????? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Wouldn't it make more sense to have ".mail.txt" or something else? Preferably a hidden dot file. I know that I would not care to have any extra files in my home directory, which I prefer to leave containing no actual files, but only the various sub-directories that I do my work in.... Chris Dunphy (cmd1@wuecl.wustl.edu) From owner-pine-info@cac.washington.edu Mon Sep 20 11:01:47 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07629; Mon, 20 Sep 93 11:01:47 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02223; Mon, 20 Sep 93 10:48: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 AA02215; Mon, 20 Sep 93 10:48:45 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00544; Mon, 20 Sep 93 10:48:37 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA20103; Mon, 20 Sep 93 10:48:27 -0700 Date: Mon, 20 Sep 1993 10:47:11 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs 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 On Mon, 20 Sep 1993 09:51:20 -0400 (EDT), Alex Tang wrote: > I do have one question to > bring up. When pine is initiated using a Tenex2 style mailbox, and then > an export message is done using the filename "mail.txt", it will ask (and be > able to) append the message to the file mail.txt. This causes problems when > pine is run again. It will say "bad message number X" where x is the last > message, and then close the inbox. I believe that Pine 3.85 won't let you make this mistake. Older versions of Pine assumed that all mailboxes were in mbox format, and would append in that format without checking. From owner-pine-info@cac.washington.edu Mon Sep 20 11:58:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09644; Mon, 20 Sep 93 11:58:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19678; Mon, 20 Sep 93 11:26:50 -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 AA19672; Mon, 20 Sep 93 11:26:48 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20313; Mon, 20 Sep 93 11:26:41 -0700 Date: Mon, 20 Sep 1993 11:17:20 -0700 (PDT) From: Terry Gray Subject: Re: pine and shlibs To: Mark Crispin Cc: Alex Tang , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mark, Alex refers to "export message"... rather than "save message" Unlike Save, Export should (and I think does) append to any file, if you say yes to the "append" prompt. We made Export preserve the "From " line so that such files *could* be read as mailboxes, but Export was intended to copy the message text to a *file* not a "folder". So Export to a mail.txt file used as a Tenex-format INBOX is a problem... though I hope not one that will occur very often. Save, rather than Export, certainly should be used whenever there is an expectation of "mailboxness", and should be safe in the situation described. (Alex, if you really were using Save rather than Export, please disregard this message.) -teg On Mon, 20 Sep 1993, Mark Crispin wrote: > On Mon, 20 Sep 1993 09:51:20 -0400 (EDT), Alex Tang wrote: > > I do have one question to > > bring up. When pine is initiated using a Tenex2 style mailbox, and then > > an export message is done using the filename "mail.txt", it will ask (and be > > able to) append the message to the file mail.txt. This causes problems when > > pine is run again. It will say "bad message number X" where x is the last > > message, and then close the inbox. > > I believe that Pine 3.85 won't let you make this mistake. Older versions of > Pine assumed that all mailboxes were in mbox format, and would append in that > format without checking. > > From owner-pine-info@cac.washington.edu Mon Sep 20 12:06:56 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10182; Mon, 20 Sep 93 12:06:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02480; Mon, 20 Sep 93 11:41:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from csgrad.cs.vt.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02474; Mon, 20 Sep 93 11:41:55 -0700 Received: by csgrad.cs.vt.edu (5.65/DEC-Ultrix/4.3) id AA12816; Mon, 20 Sep 1993 14:41:51 -0400 Date: Mon, 20 Sep 1993 14:40:36 -0400 (EDT) From: Laurence Lundblade Reply-To: Laurence Lundblade Subject: Re: pine and shlibs To: Mark Crispin Cc: Alex Tang , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII The command in question is export, which is just used to copy a message out of the mail store into a text file. It does no checking at all, and I don't think any is appropriate. Tenex2 seems like a good idea. If there's not a bunch of people using it yet, how about putting the mail file where this isn't going to happen, like in subdirectory? It's real easy to clobber a file name mail.txt Just an idea.... LL On 20 Sep 1993, Mark Crispin wrote: > On Mon, 20 Sep 1993 09:51:20 -0400 (EDT), Alex Tang wrote: > > I do have one question to > > bring up. When pine is initiated using a Tenex2 style mailbox, and then > > an export message is done using the filename "mail.txt", it will ask (and be > > able to) append the message to the file mail.txt. This causes problems when > > pine is run again. It will say "bad message number X" where x is the last > > message, and then close the inbox. > > I believe that Pine 3.85 won't let you make this mistake. Older versions of > Pine assumed that all mailboxes were in mbox format, and would append in that > format without checking. > > > From owner-pine-info@cac.washington.edu Mon Sep 20 13:09:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13506; Mon, 20 Sep 93 13:09:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02847; Mon, 20 Sep 93 12:49:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ACF4.NYU.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02841; Mon, 20 Sep 93 12:49:47 -0700 Received: by acf4.NYU.EDU (5.65/DEC-Ultrix/4.3) id AA10007; Mon, 20 Sep 1993 15:49:09 -0400 Date: Mon, 20 Sep 1993 15:46:40 -0400 (EDT) From: "Yigal M. Rechtman" Subject: Re: Getting pine.tar on DC600 tape. (fwd) 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 On Mon, 20 Sep 1993, David L Miller wrote: > > I don't remember any reports one way or the other about CTIX, what is it > similar to? > [stuff deleted] What it is - is Unix V. Why it is called CTIX I have no idea. Nor am I a "Meven" about Unix in General. It IS unix, but for some reason the people who made it's shell call it CTIX. What I understand is, that it is tied directly to the S/80 chip, and therefor the Ctix/Unix can not be upgraded - somthing on these lines. Yigal From owner-pine-info@cac.washington.edu Mon Sep 20 13:37:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14289; Mon, 20 Sep 93 13:37:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21780; Mon, 20 Sep 93 13:16: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 AA21774; Mon, 20 Sep 93 13:16:57 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23498; Mon, 20 Sep 93 13:16:35 -0700 Date: Mon, 20 Sep 1993 12:59:24 -0700 (PDT) From: David L Miller Subject: Re: Getting pine.tar on DC600 tape. (fwd) To: "Yigal M. Rechtman" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII >From the version you gave me (5.2.25), I would _guess_ that it is a port of System V, Release 2. In that case, you probably have an uphill road ahead of you to get Pine ported to CTIX. I hear that the System/80 was originally built by Convergent Technologies, if that helps. Sorry I can't be of more help... |\ | |\/| 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, 20 Sep 1993, Yigal M. Rechtman wrote: > > > On Mon, 20 Sep 1993, David L Miller wrote: > > > > > I don't remember any reports one way or the other about CTIX, what is it > > similar to? > > > [stuff deleted] > > What it is - is Unix V. Why it is called CTIX I have no idea. Nor am I a > "Meven" about Unix in General. It IS unix, but for some reason the people > who made it's shell call it CTIX. What I understand is, that it is tied > directly to the S/80 chip, and therefor the Ctix/Unix can not be upgraded > - somthing on these lines. > > Yigal > > > From owner-pine-info@cac.washington.edu Mon Sep 20 13:50:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14725; Mon, 20 Sep 93 13:50:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22090; Mon, 20 Sep 93 13:32:32 -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 AA22084; Mon, 20 Sep 93 13:32:30 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23782; Mon, 20 Sep 93 13:32:23 -0700 Date: Mon, 20 Sep 1993 13:12:28 -0700 (PDT) From: Terry Gray Subject: Re: pine and shlibs 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 On Mon, 20 Sep 1993, Mark Crispin wrote: > If Export preserves an mbox-format ``From '' line, then how does it > differ from Save? Just in the semantics of the target? A Save that always > saves in mbox format even if the user uses Tenex format? In Pine, saved messages are always in mbox format too, unless the folder already exists in a different format. This is true regardless of the format of the INBOX. (This is considered a feature by most folks, who use other messaging tools with the same saved-msg folders; e.g. trn) The differences between save and export are: -Save preserves the *entire* message, complete with Received-from headers, whereas Export omits the normally-hidden headers and omits attachments. -Save sniffs the target folder and appends in whatever format the folder already is; but if it doesn't exist yet, Pine uses mbox format. In contrast, Export always uses mbox format. -Save normally stores to a folder in the default folder collection (typically in ~/mail) whereas Export uses the home directory by default. As you know, there are several complex issues lurking concerning mailbox formats and how to specify/control/accommodate them... As soon as we get 3.85 out the door, we need to focus on this as a generic problem. -teg From owner-pine-info@cac.washington.edu Mon Sep 20 14:06:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15223; Mon, 20 Sep 93 14:06:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03036; Mon, 20 Sep 93 13:10:32 -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 AA03030; Mon, 20 Sep 93 13:10:12 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00639; Mon, 20 Sep 93 13:10:04 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA20541; Mon, 20 Sep 93 13:09:56 -0700 Date: Mon, 20 Sep 1993 11:41:28 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Terry Gray Cc: Laurence Lundblade , pine-info@CAC.Washington.EDU In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Terry and Laurence - I see. This is the same problem we had in MM back in 1979. There was a LIST command to list messages to the lineprinter, and then came a FILE-LIST command to put a listing to a file, and sure enough, someone did a FILE-LIST and specified MAIL.TXT as the target. Oops. If Export preserves an mbox-format ``From '' line, then how does it differ from Save? Just in the semantics of the target? A Save that always saves in mbox format even if the user uses Tenex format? I'm wondering if we can't make Export a bit more paranoid. Perhaps it should refuse to write to an extant file, or it should see if the file opens as a mailbox first? -- Mark -- From owner-pine-info@cac.washington.edu Mon Sep 20 14:32:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17019; Mon, 20 Sep 93 14:32:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03397; Mon, 20 Sep 93 14:18:25 -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 AA03391; Mon, 20 Sep 93 14:18:21 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA04671; Mon, 20 Sep 93 17:18:17 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA19280; Mon, 20 Sep 93 17:18:15 -0400 Date: Mon, 20 Sep 1993 17:14:50 -0400 (EDT) From: Alex Tang Subject: Re: pine and shlibs To: Terry Gray Cc: Mark Crispin , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 20 Sep 1993, Terry Gray wrote: > Mark, > Alex refers to "export message"... rather than "save message" > Unlike Save, Export should (and I think does) append to any file, > if you say yes to the "append" prompt. > > We made Export preserve the "From " line so that such files *could* be > read as mailboxes, but Export was intended to copy the message text to a > *file* not a "folder". So Export to a mail.txt file used as a > Tenex-format INBOX is a problem... though I hope not one that will occur > very often. Save, rather than Export, certainly should be used whenever > there is an expectation of "mailboxness", and should be safe in the > situation described. > > (Alex, if you really were using Save rather than Export, please disregard > this message.) Yes, this is exactly what I was trying to say. (but I screwed it up....duh.) The problem that I forsee is that if someone actually does export the message to mail.txt, it will make it so pine will not be able to read the folder. Is there some way to make it so it can't save to this file if it's being used as the inbox? (or rename the inbox)? thanx...alex... From owner-pine-info@cac.washington.edu Mon Sep 20 14:54:17 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17874; Mon, 20 Sep 93 14:54:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23402; Mon, 20 Sep 93 14:42:10 -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 AA23396; Mon, 20 Sep 93 14:42:07 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25641; Mon, 20 Sep 93 14:42:06 -0700 Date: Mon, 20 Sep 1993 14:36:45 -0700 (PDT) From: Steve Hubert Subject: Re: pine and shlibs To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Here's a workaround that might save some of you from having to edit source to prevent mail.txt from taking over as inbox. If a user explicitly defines inbox-path to be something, then when INBOX is opened it will use that instead of asking for the generic INBOX (which has the mail.txt semantics wired-in). So, inbox-path=/usr/spool/mail/hubert would cause my mail to be read from and left in /usr/spool/mail/hubert even if I had a mail.txt file in my home directory. As system manager, you ought to be able to define inbox-path in the /usr/local/lib/pine.conf file so it is something like inbox-path=/usr/spool/mail/$USER or inbox-path=/usr/spool/mail/$LOGNAME or whatever is appropriate for your system. A user could still override this with an explicit inbox-path="" Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Mon Sep 20 15:19:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18907; Mon, 20 Sep 93 15:19:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23952; Mon, 20 Sep 93 15:08:47 -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 AA23946; Mon, 20 Sep 93 15:08:40 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA01530; Mon, 20 Sep 93 15:08:37 PDT Date: Mon, 20 Sep 1993 15:04:48 -0700 (PDT) From: Steve Hubert Subject: emergency stop To: Matt Simmons Cc: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Is it possible to exit pine w/o writing the mailbox? i.e. an emergency > stop or something like that... There is no designed-in feature to do this. About the only way I can think to do it is to kill the pine process. A kill -9 would cause it to die without having a chance to rewrite the mailbox. Of course, pine does do automatic checkpointing based on keystroke counts, so it is possible that the mailbox will already have been updated if you've been looking at it and changing it. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Mon Sep 20 16:24:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21126; Mon, 20 Sep 93 16:24:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25519; Mon, 20 Sep 93 16:16:29 -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 AA25511; Mon, 20 Sep 93 16:16:27 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA25806; Mon, 20 Sep 93 16:16:25 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA23082; Mon, 20 Sep 93 16:16:24 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA02816; Mon, 20 Sep 93 16:16:24 PDT Date: Mon, 20 Sep 93 16:16:23 PDT From: ekurgpol@Law.USC.EDU (Elmar Kurgpold) Message-Id: <9309202316.AA02816@develop.Law.USC.EDU> To: pine-info@cac.washington.edu Subject: Re: Attachments not recognized This is a repost. I had hoped that someone would have a suggestion for this, but don't have any answers yet. One person posted that they were experiencing the same problem. Basically, it works sometimes, and others it doesn't. What I expect to see when I try to extract an attachment is: > Enter attachment number to view or save (1 - 2) ...and not: > Enter attachment number to view or save (1 - 1) This is Pine version 3.07-- is it fixed in the new release? Someone please tell me where I made my lame mistake. ------------------------------------- | Elmar Kurgpold | | Network Administrator | | University of Southern California | | The Law Center | | ekurgpol@Law.USC.EDU | | (213)740-2571 FAX: (213)740-5502 | ------------------------------------- > What happens is when I attach > a data file and mail it back to myself, I seem to get the encoded file but > cannot detach it once received. When I check for attachments, I am > asked... > > Enter attachment number to view or save (1 - 1) > > There has been times when the attached file is seemingly not included, and > the file bombed. When this happened, I believe there was an attachment > but it was empty. Specifically, I am trying to send WordPerfect files > created in DOS and then copied up to my Unix disk via NFS. It works great > with ascii files. > > I've attached a portion of the message below. > > One more question: Will there be block editing capabilities in future > versions of pico/pine? > > ---------- Forwarded message ---------- > Date: Thu, 9 Sep 1993 14:41:52 -0700 (PDT) > From: Elmar Kurgpold > To: Elmar Kurgpold > Subject: > > here's coming > > > --1915757200-358981935-747610992:#29384 > Content-Type: APPLICATION/octet-stream; name="charmap.tst" > Content-Transfer-Encoding: BASE64 > Content-ID: > Content-Description: > > /1dQQ9YEAAABCgABAAAAAPv/BQAyABEBAAD//w4AAABCAAAABgAQAAAAUAAA > AP//WgAAAKYAAAD//xEAAAAAAQAAQ291cmllciAxMGNwaQAIA3wAeAAAAAAA > AAAAAAAAAQAAAABVXtsBeAAUHgwXjAoAAAAEEUDJAIfPAQABAFgCQP////// > /////////////////////////////////////////wAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > > ...etc > > --1915757200-358981935-747610992:#29384-- > > > > > > From owner-pine-info@cac.washington.edu Mon Sep 20 19:13:58 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25312; Mon, 20 Sep 93 19:13:58 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04823; Mon, 20 Sep 93 19:04:15 -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 AA04817; Mon, 20 Sep 93 19:04:08 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA06253; Mon, 20 Sep 93 22:04:06 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA24321; Mon, 20 Sep 93 22:04:05 -0400 Date: Mon, 20 Sep 1993 22:02:52 -0400 (EDT) From: Alex Tang Subject: Re: pine and shlibs 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 Mon, 20 Sep 1993, Steve Hubert wrote: > Here's a workaround that might save some of you from having to edit > source to prevent mail.txt from taking over as inbox. If a user > explicitly defines inbox-path to be something, then when INBOX is opened > it will use that instead of asking for the generic INBOX (which has the > mail.txt semantics wired-in). So, > > inbox-path=/usr/spool/mail/hubert > Hi. I've got a question regarding this workaround. Is it possible to get a tenex2 style mailbox without it being named mail.txt? thanx...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 :) From owner-pine-info@cac.washington.edu Mon Sep 20 23:34:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28707; Mon, 20 Sep 93 23:34:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05678; Mon, 20 Sep 93 23:17:52 -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 AA05672; Mon, 20 Sep 93 23:17:47 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01577; Mon, 20 Sep 93 23:17:42 -0700 Date: Mon, 20 Sep 1993 23:15:38 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Alex Tang Cc: Steve Hubert , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 20 Sep 1993 22:02:52 -0400 (EDT), Alex Tang wrote: > Hi. I've got a question regarding this workaround. Is it possible to get a > tenex2 style mailbox without it being named mail.txt? Yes, but it won't be recognized as an INBOX. Specifically, mail won't be snarfed from /usr/spool/mail/$USER into it. Only ~/mail.txt is recognized as a Tenex style INBOX, and only when you open it as INBOX, not as mail.txt. From owner-pine-info@cac.washington.edu Tue Sep 21 01:07:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00935; Tue, 21 Sep 93 01:07:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05980; Tue, 21 Sep 93 00:57:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from wuecl.wustl.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05976; Tue, 21 Sep 93 00:57:54 -0700 Return-Path: Received: by wuecl.wustl.edu (5.65a/1.35); id AA18696; Tue, 21 Sep 93 02:57:36 -0500 Date: Tue, 21 Sep 1993 02:55:02 -0500 (CDT) From: Chris Dunphy Subject: Re: pine and shlibs To: Mark Crispin Cc: Alex Tang , Steve Hubert , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 20 Sep 1993, Mark Crispin wrote: > On Mon, 20 Sep 1993 22:02:52 -0400 (EDT), Alex Tang wrote: > > Hi. I've got a question regarding this workaround. Is it possible to get a > > tenex2 style mailbox without it being named mail.txt? > > Yes, but it won't be recognized as an INBOX. Specifically, mail won't be > snarfed from /usr/spool/mail/$USER into it. Only ~/mail.txt is recognized as > a Tenex style INBOX, and only when you open it as INBOX, not as mail.txt. > But what I want to know is if it is possible to have an INBOX of a different name. I don't like the idea of a file name ~/mail.txt in my home directory, cluttering up my otherwise organized directory structure. I would much rather have it as ~/.mail.txt, or ~/.inbox, or best of all, in my ~/mail subdirectory with all my other folders as ~/Mail/inbox...... Is this possible, and if not, why not? Why not make this the default? Chris From owner-pine-info@cac.washington.edu Tue Sep 21 05:30:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05767; Tue, 21 Sep 93 05:30:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01494; Tue, 21 Sep 93 05:21:10 -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 AA01488; Tue, 21 Sep 93 05:21:04 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA19644; Tue, 21 Sep 93 08:19:01 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA08232; Tue, 21 Sep 93 08:19:34 EDT Date: Tue, 21 Sep 1993 08:18:44 -0400 (EST) From: Keith Christopher Subject: Re: Attachments not recognized To: pine-info@cac.washington.edu In-Reply-To: <9309202316.AA02816@develop.Law.USC.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 128 How does one turn off the saved sent messages option ? ` Keith Christopher Welch Medical Library Unix System Adminstrator From owner-pine-info@cac.washington.edu Tue Sep 21 09:09:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11689; Tue, 21 Sep 93 09:09:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03885; Tue, 21 Sep 93 08:56: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 AA03879; Tue, 21 Sep 93 08:56:05 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13268; Tue, 21 Sep 93 08:56:02 -0700 Date: Tue, 21 Sep 1993 08:54:30 -0700 (PDT) From: David L Miller Subject: Re: Attachments not recognized To: Elmar Kurgpold Cc: pine-info@cac.washington.edu In-Reply-To: <9309202316.AA02816@develop.Law.USC.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This sounds like a problem that will be fixed in Pine 3.85. There has been alot of improvement made to attachment processing. Pine 3.85 will be available later this week. |\ | |\/| 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, 20 Sep 1993, Elmar Kurgpold wrote: > This is a repost. I had hoped that someone would have a suggestion for > this, but don't have any answers yet. One person posted that they were > experiencing the same problem. Basically, it works sometimes, and others > it doesn't. > > What I expect to see when I try to extract an attachment is: > > Enter attachment number to view or save (1 - 2) > ...and not: > > Enter attachment number to view or save (1 - 1) > > This is Pine version 3.07-- is it fixed in the new release? > Someone please tell me where I made my lame mistake. > > ------------------------------------- > | Elmar Kurgpold | > | Network Administrator | > | University of Southern California | > | The Law Center | > | ekurgpol@Law.USC.EDU | > | (213)740-2571 FAX: (213)740-5502 | > ------------------------------------- > > > What happens is when I attach > > a data file and mail it back to myself, I seem to get the encoded file but > > cannot detach it once received. When I check for attachments, I am > > asked... > > > > Enter attachment number to view or save (1 - 1) > > > > There has been times when the attached file is seemingly not included, and > > the file bombed. When this happened, I believe there was an attachment > > but it was empty. Specifically, I am trying to send WordPerfect files > > created in DOS and then copied up to my Unix disk via NFS. It works great > > with ascii files. > > > > I've attached a portion of the message below. > > > > One more question: Will there be block editing capabilities in future > > versions of pico/pine? > > > > ---------- Forwarded message ---------- > > Date: Thu, 9 Sep 1993 14:41:52 -0700 (PDT) > > From: Elmar Kurgpold > > To: Elmar Kurgpold > > Subject: > > > > here's coming > > > > > > --1915757200-358981935-747610992:#29384 > > Content-Type: APPLICATION/octet-stream; name="charmap.tst" > > Content-Transfer-Encoding: BASE64 > > Content-ID: > > Content-Description: > > > > /1dQQ9YEAAABCgABAAAAAPv/BQAyABEBAAD//w4AAABCAAAABgAQAAAAUAAA > > AP//WgAAAKYAAAD//xEAAAAAAQAAQ291cmllciAxMGNwaQAIA3wAeAAAAAAA > > AAAAAAAAAQAAAABVXtsBeAAUHgwXjAoAAAAEEUDJAIfPAQABAFgCQP////// > > /////////////////////////////////////////wAAAAAAAAAAAAAAAAAA > > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > > > > ...etc > > > > --1915757200-358981935-747610992:#29384-- > > > > > > > > > > > > > > From owner-pine-info@cac.washington.edu Tue Sep 21 16:34:52 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27011; Tue, 21 Sep 93 16:34:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12272; Tue, 21 Sep 93 16:26:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12262; Tue, 21 Sep 93 16:26:38 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H38SOHFD74000CQ7@VENUS.RESNTL.BHP.COM.AU>; Wed, 22 Sep 1993 09:24:37 GMT Received: by squiggle.resntl.bhp.com.au (920330.SGI/920323.SGI.Irix.3.3) for @venus.resntl.bhp.com.au:pine-info@cac.washington.edu id AA18868; Wed, 22 Sep 93 09:26:17 +1000 Date: Wed, 22 Sep 1993 09:22:16 +1000 (EST) From: Steve Woodyatt Subject: Folder names in save To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Hi all, Probably something that has been addressed in the new version of Pine, however I'll mention it anyway. I regularly receive mail with headers of the form: From: Tourenne To:uunet.UU.NET!uunet!VENUS.RESNTL.BHP.COM.AU!steve@squiggle.resntl.bhp.com.au Subject: RE: Hello When I go to save the message in a folder, it tries to create a folder named: uunet.UU.NET!vital!unixmailgate!tourenne@squiggle.resntl.bhp.com.au which of course I want to change. The only problem is that the length of the name of that default folder leaves me no room to type a new folder name in, after the prompt! Steve. -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / / /\ BHP Research - Newcastle Laboratories, Australia./ / / \ Snail : P.O. Box 188, Wallsend 2287 / / / /\ \ Tel : +61 49 510695 Fax: +61 49 502126 \ \/ / / / Internet: steve@resntl.bhp.com.au \ / / / ------------------------------------------------------------------\/\/\/-- From owner-pine-info@cac.washington.edu Tue Sep 21 20:29:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01392; Tue, 21 Sep 93 20:29:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11423; Tue, 21 Sep 93 20:13:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11417; Tue, 21 Sep 93 20:13:20 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA03730; Tue, 21 Sep 93 20:14:11 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA09121; Tue, 21 Sep 93 20:16:13 -0700 Date: Tue, 21 Sep 1993 20:13:46 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Shared libs on PTX? (fwd) To: PINE Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII For all of you who were wondering about shared libs for pine/pico...please read the forwarded message...it may disappoint some...but make others happy... Later... ------------------------------------------------------------------------------ Jason R. Thorpe | | 434 Weatherford Hall OSU Computer Science | thorpej@xanth.cs.orst.edu | Corvallis, OR 97331 Support Staff | | (503) 737-9533 ---------- Forwarded message ---------- Date: Sun, 19 Sep 1993 21:53:45 -0700 From: maddog@sequent.com To: "Jason R. Thorpe" , Chris LaFournaise Subject: Re: Shared libs on PTX? > Hey y'all... > > Do any of you know if PTX supports shared libraries (like SunOS, I guess...)? > > I'm looking for a way to make Pine shew up less resources... DYNIX/ptx does not support shared libraries. It does only load one copy of a certain portion of each distinct binary that is invoked. -john From owner-pine-info@cac.washington.edu Wed Sep 22 00:20:10 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04603; Wed, 22 Sep 93 00:20:10 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12258; Wed, 22 Sep 93 00:11:00 -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 AA12252; Wed, 22 Sep 93 00:10:58 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04616; Wed, 22 Sep 93 00:10:51 -0700 Date: Wed, 22 Sep 1993 00:01:39 -0700 (PDT) From: Mark Crispin Subject: Re: pine and shlibs To: Chris Dunphy Cc: Alex Tang , Steve Hubert , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII No, a tenex-format INBOX is fixed as ~/mail.txt There are some good reasons why this is the case. Here are some of them: I didn't want to get involved with subdirectories, because: 1) using an existing name (such as ~/mail/, ~/Mail/, ~/Mailboxes, etc.) would bring it into conflict with other applications which think they own the contents of a particular named subdirectory. 2) using a new name would be Yet Another Subdirectory Name for mail. The ~/.mail.txt is an idea, but I don't like the idea of a large file such as your mail INBOX being an invisible file. This is particularly the case on systems with disk quotas. Try explaining to a person why he is over quota ``but I only have one little file in my directory'' sometime. A problem with it being user-configurable means that you run the risk of bad behavior happening when the configuration file gets corrupted or lost. In a past life as a systems programmer, I had to deal with entirely too many ``my mail disappeared'' problem reports that turned out to be a entirely due to a non-standard setting in a configuration file getting zapped. Another problem with it being user-configurable means that you have a user services problem. It's one thing to ask for your mail file to be restored by an operator (or ask a systems programmer to fix a problem in your mail file) when it is in a well-known place. It is quite another when it can be almost anywhere. From owner-pine-info@cac.washington.edu Wed Sep 22 00:57:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05579; Wed, 22 Sep 93 00:57:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16213; Wed, 22 Sep 93 00:48:16 -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 AA16207; Wed, 22 Sep 93 00:48:14 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21612; Wed, 22 Sep 93 00:48:13 -0700 Date: Wed, 22 Sep 1993 00:32:28 -0700 (PDT) From: Terry Gray Subject: Re: mail.txt behavior (pine and shlibs) To: pine-info@cac.washington.edu Cc: Chris Dunphy , Alex Tang In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII For the record, I need to point out that Mark's explanation/defense of the current Pine/IMAPd behavior (wherein the existence of a zero-length mail.txt file will trigger Pine or IMAPd to begin using the Tenex driver for INBOX processing)... does not represent a consensus position of the Pine team. After we get 3.85 out the door* we will be focusing on the inter-related problems of hierarchy support, selecting among different folder namespaces, and controlling mailbox format. Stay tuned... -teg * Is it Sept. 20 yet? Depending on feedback from a few folks checking out some bug fixes for us, we *may* be within 24 hours... From owner-pine-info@cac.washington.edu Wed Sep 22 05:06:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11082; Wed, 22 Sep 93 05:06:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13367; Wed, 22 Sep 93 04:58:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from terminus.cs.umb.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13361; Wed, 22 Sep 93 04:58:07 -0700 Received: by terminus.cs.umb.edu id AA28354 (5.65c/IDA-1.4.4); Wed, 22 Sep 1993 07:58:04 -0400 Date: Wed, 22 Sep 1993 07:58:04 -0400 From: Robert Morris Message-Id: <199309221158.AA28354@terminus.cs.umb.edu> To: MRC@CAC.Washington.EDU Cc: cmd1@wuecl.wustl.edu, altitude@umich.edu, hubert@cac.washington.edu, pine-info@cac.washington.edu In-Reply-To: Mark Crispin's message of Wed, 22 Sep 1993 00:01:39 -0700 (PDT) Subject: pine and shlibs Reply-To: ram@cs.umb.edu >>>>> On Wed, 22 Sep 1993 00:01:39 -0700 (PDT), Mark Crispin said: > A problem with it being user-configurable means that you run the risk of bad > behavior happening when the configuration file gets corrupted or lost. In a > past life as a systems programmer, I had to deal with entirely too many ``my > mail disappeared'' problem reports that turned out to be a entirely due to a > non-standard setting in a configuration file getting zapped. > Another problem with it being user-configurable means that you have a user > services problem. It's one thing to ask for your mail file to be restored by > an operator (or ask a systems programmer to fix a problem in your mail file) > when it is in a well-known place. It is quite another when it can be almost > anywhere. I would say that a good approach to both of these issues is not to apply dictatorial solutions because they are easier, but to provide sufficient resource discovery tools for the end user and system administrators. Examples which come to mind of solutions to analagous problems are the ucb `which' command to tell you which of possibly many identically named commands in your path you are executing, and the -query option to xrdb, the X windows resource database utility, with which you can find out the value of any of the ten thousand variables controlling your X-windows behavior. Of course, in that instance just knowing what to look for can be a daunting task, but the biggest administrative problems come from sorcerer's apprentices---users who blindly took a wizard's configuration over the system configuration. That's a small group which might deserve what it gets if the rest of the world gets something good. Pine is already well past the point where "keep it simple" arguments deserve automatic priority. Keep it useful is now more important. Bob From owner-pine-info@cac.washington.edu Wed Sep 22 10:07:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19441; Wed, 22 Sep 93 10:07:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22025; Wed, 22 Sep 93 09:54:10 -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 AA22019; Wed, 22 Sep 93 09:54:05 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <14721-0@dummy1.dur.ac.uk>; Wed, 22 Sep 1993 17:51:24 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Wed, 22 Sep 93 17:51:20 BST Date: Wed, 22 Sep 1993 17:48:22 +0100 (BST) From: Barry Cornelius Subject: accents and umlauts in Pine To: Pine Info Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have a number of users wishing to send messages in European languages. In particular, they wish to compose messages containing accents and umlauts. The mailer that they use is the Unix version of Pine. It so happens that they access Unix from MS-DOS on a PC. For the letter a with an umlaut they type alt-132. This works for pico, but they have not succeeded in getting it to work when they are in the message-composition part of Pine. Should they be setting the character-set variable to ISO-8859-1? Another question: what role has the show-all-characters variable? Thanks in advance. -- 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 Wed Sep 22 11:05:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21183; Wed, 22 Sep 93 11:05:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23016; Wed, 22 Sep 93 10:53:04 -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 AA23010; Wed, 22 Sep 93 10:53:02 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14353; Wed, 22 Sep 93 10:52:48 -0700 Date: Wed, 22 Sep 1993 10:18:31 -0700 (PDT) From: David L Miller Subject: Re: accents and umlauts in Pine To: Barry Cornelius Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Barry, Yes, you should be setting character-set=ISO-8859-1 if you are going to be using 8-bit characters. If you have character-set=US-ASCII, the terminal driver is not initialized with LPASS8 and high bits will be stripped in Pine. Pico is 8-bit clean and does not care what character-set you are using. The show-all-characters variable has been deprecated. It used to switch between filtering and non-filtering of mismatched character sets. i.e. if your character-set was US-ASCII, any non-US-ASCII character would be displayed as '_'. This feature has been removed. If your character-set does not match an incoming message, you will be warned, but Pine will blast away... --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 Wed, 22 Sep 1993, Barry Cornelius wrote: > We have a number of users wishing to send messages in European > languages. In particular, they wish to compose messages containing > accents and umlauts. The mailer that they use is the Unix version > of Pine. It so happens that they access Unix from MS-DOS on a PC. > For the letter a with an umlaut they type alt-132. This works for > pico, but they have not succeeded in getting it to work when they > are in the message-composition part of Pine. > > Should they be setting the character-set variable to ISO-8859-1? > > Another question: what role has the show-all-characters variable? > > Thanks in advance. > > -- > 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 Wed Sep 22 12:37:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24206; Wed, 22 Sep 93 12:37:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24472; Wed, 22 Sep 93 12:22:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from flipper.pvv.unit.no by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24466; Wed, 22 Sep 93 12:21:54 -0700 Received: by flipper.pvv.unit.no id AA10618 (5.65c8/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 22 Sep 1993 21:21:04 +0200 From: Arnt Gulbrandsen Message-Id: <199309221921.AA10618@flipper.pvv.unit.no> Subject: Re: accents and umlauts in Pine To: pine-info@cac.washington.edu Date: Wed, 22 Sep 1993 21:21:02 +0200 (EET) In-Reply-To: from "Barry Cornelius" at Sep 22, 93 05:48:22 pm X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 730 X-Charset: ASCII X-Char-Esc: 29 > We have a number of users wishing to send messages in European > languages. In particular, they wish to compose messages containing > accents and umlauts. The mailer that they use is the Unix version > of Pine. It so happens that they access Unix from MS-DOS on a PC. > For the letter a with an umlaut they type alt-132. Which is the PC code for a-umlaut. The ISO-8859-1 code is not 132, and you have to use the ISO-8859 character sets. You need a PC telnet client with the ability to translate between the ISO-8859-n and PC character sets. I don't know any, but it would be fairly easy to graft Keld Simonsen's code into NCSA telnet to do it, send me mail if you want details. -- Arnt Gulbrandsen agulbra@pvv.unit.no From owner-pine-info@cac.washington.edu Wed Sep 22 15:33:46 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00620; Wed, 22 Sep 93 15:33:46 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16566; Wed, 22 Sep 93 15:20:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from herald.usask.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16558; Wed, 22 Sep 93 15:19:54 -0700 Received: by herald.usask.ca (5.65/DEC-Ultrix/4.3) id AA15402; Wed, 22 Sep 1993 16:19:44 -0600 for pine-info@cac.washington.edu Date: Wed, 22 Sep 1993 16:19:24 -0600 (CST) From: Earl Fogel Reply-To: Earl Fogel Subject: IMAP client for Windows? To: CW-EMAIL%TECMTYVM.BITNET@uwavm.u.washington.edu, pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Is there such a thing as IMAP client software for Microsoft Windows? Earl Fogel Computing Services phone: (306) 966-4861 University of Saskatchewan email: earl.fogel@usask.ca From owner-pine-info@cac.washington.edu Wed Sep 22 16:36:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02667; Wed, 22 Sep 93 16:36:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16891; Wed, 22 Sep 93 16:24:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from donald.uoregon.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16885; Wed, 22 Sep 93 16:24:56 -0700 Received: from OREGON.UOREGON.EDU by OREGON.UOREGON.EDU (PMDF V4.2-13 #3475) id <01H397CDPIVA95MLPN@OREGON.UOREGON.EDU>; Wed, 22 Sep 1993 16:24:48 PDT Date: Wed, 22 Sep 1993 16:24:47 -0700 (PDT) From: Rick Millhollin Subject: Pine for VMS? To: pine-info@cac.washington.edu Message-Id: <01H397CE246G95MLPN@OREGON.UOREGON.EDU> X-Vms-To: IN%"pine-info@cac.washington.edu" Mime-Version: 1.0 Content-Transfer-Encoding: 7BIT Do you folks know of a VMS port of Pine? From owner-pine-info@cac.washington.edu Wed Sep 22 17:30:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04511; Wed, 22 Sep 93 17:30:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00430; Wed, 22 Sep 93 17:10: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 AA00424; Wed, 22 Sep 93 17:10:10 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25127; Wed, 22 Sep 93 17:10:06 -0700 Date: Wed, 22 Sep 1993 17:08:46 -0700 (PDT) From: David L Miller Subject: Re: Pine for VMS? To: Rick Millhollin Cc: pine-info@cac.washington.edu In-Reply-To: <01H397CE246G95MLPN@OREGON.UOREGON.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We have heard of several stabs at a VMS port of Pine, but not of any successes. If you find/complete one, we would like to hear about it! |\ | |\/| 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, 22 Sep 1993, Rick Millhollin wrote: > Do you folks know of a VMS port of Pine? From owner-pine-info@cac.washington.edu Wed Sep 22 20:40:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07285; Wed, 22 Sep 93 20:40:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17924; Wed, 22 Sep 93 20:25:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17918; Wed, 22 Sep 93 20:25:08 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA12553; Wed, 22 Sep 93 20:25:57 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA25186; Wed, 22 Sep 93 20:28:00 -0700 Date: Wed, 22 Sep 1993 20:27:34 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: IMAP client for Windows? To: Earl Fogel Cc: CW-EMAIL%TECMTYVM.BITNET@uwavm.u.washington.edu, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 22 Sep 1993, Earl Fogel wrote: > Is there such a thing as IMAP client software for Microsoft Windows? Run pine in a window...crufty, true, but it works... 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 Thu Sep 23 17:43:25 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10059; Thu, 23 Sep 93 17:43:25 -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 AA09353; Thu, 23 Sep 93 17:16:06 -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 AA09304; Thu, 23 Sep 93 17:15:51 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16788; Thu, 23 Sep 93 17:15:48 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01205; Thu, 23 Sep 93 17:15:47 -0700 Reply-To: Terry Gray Message-Id: Date: Thu, 23 Sep 1993 17:13:38 -0700 (PDT) From: Terry Gray To: Pine Announcement Distribution Subject: Pine 3.85 released X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu THE NEWS... On behalf of the entire Pine team, I'm pleased to be able to tell you that Version 3.85 of Pine and PC-Pine is now available. The release also includes new versions of Pico and IMAPd. This version is believed to run on quite a few more Unix flavors than previous versions. STATUS... Although some code in 3.85 is relatively "fresh", we are not aware of any serious bugs --otherwise you would be waiting even longer for this message :) Like many of you, we've been working toward installing this version at UW in time for Fall Quarter... and we know that we're late. So, if anyone finds any serious bugs, please let us know ASAP so that we can address them quickly! (Of course, we want to know about not-so-serious bugs as well.) Please note: there are bugs that you have reported to us that are not yet fixed... though hopefully no show-stoppers. If you find one that is really annoying you, please gently remind us! And if in doubt, report it! 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. Because attachment encoding/decoding has not *yet* been performance-tuned, this will be slower than FTP, but may be more convenient. (Let us know what you think!) RELEASE NOTES EXCERPTS... The complete release notes are available via the "R" command on the Main menu of Pine 3.85. Here are some highlights... EXECUTIVE SUMMARY - Pine 3.85 is the first integrated Unix/DOS release, and the first PC-Pine source-code release. It also brings Unix Pine in sync with changes introduced in PC-Pine 3.84 last July. - Pine 3.85 has several major new features (compared to Pine 3.07): o Various UI improvements (command consistency, simplification, etc). o Multiple folder collections. o Remote folder create/append (requires new IMAPd). o Composer has Mark command for block cut/paste. o Improved handling of text and postscript attachments. o Improved mailbox lock handling: latest Pine will now be read-write. o Messages directly to you marked with "+" in Folder Index. o Messages that have been answered marked with "A" in Folder Index. o Several new .pinerc options. o Easier access to newsgroups (but still not a full newsreader). - Several command key changes were needed to allow for new features: o Print is now "Y" instead of "L" o The Folder List is now uniformly accessible via "L" o Viewing/saving attachments is now done via "V" instead of "A" o SortIndex is now "$" instead of "Z" - There are several known limitations in the PC version: o There is no spelling checker. o Sorting the Index (by other than Arrival) is *hopelessly* slow. o The alternate editor function is not available. o Memory: it needs about 500K out of 640K. o Probably can't run image viewer from within Pine, due to memory. o Performance optimization still needs to be done. o Versions: packet driver, Novell LWP, FTP PC-TCP, Sun PC-NFS NEW FEATURES/IMPROVEMENTS (3.07 to 3.85) - Release includes PC-Pine ports, as well as Unix Pine. - Support for multiple folder collections. - Ability to create and/or append to remote folders via (new) IMAPd. - Mark and cut feature in composer. - Messages directly to you marked with "+" in Folder Index. - Messages that have been answered marked with "A" in Folder Index. - Ability to view plain text attachments. - Correct MIME type assigned for text, postscript and TIFF files. - Configurable by feature (instead of having to choose 1 feature level). - Initial keystroke list in configuration or command line. - Command line -p flag to specify an alternate personal config file. - Command line -P flag to specify an alternate system-wide config file. - Command line -o flag for opening a mailbox Read-Only. - More support for USENET news access via both IMAP and NNTP (The NNTP driver reads/updates local newsrc configuration files). - Changed order of reply prompts to reduce mistakes. - In the Save command, folder name completion using TAB key. - More consistency of commands across screens. - Main menu command selection via Prev/Next/Enter. - An option for automatically saving read-messages upon quitting. - Better INBOX lock handling: latest Pine always gets read-write access. - Improved display defaults for charsets other than us-ascii. - PC-Pine: code-page translation to ISO-8859 charset. - PC-Pine: improvements in how location of config files are specified. - PC-Pine: generate X-Sender line with authenticated address. - PC-Pine: more config flexibility in specifying location of support files. - PC-Pine: prompts before saving user name in pinerc; can disable save. - PC-Pine: NNTP driver changed to warn of missing NEWSRC file. - PC-Pine: if \PINE\PINE.PWD exists, prompts for saving passwd on disk. - Changed Keyboard lock strategy to eliminate use of system passwd file. - Removed disk quota command (hard to make it accurate!) - Reorganized source code to make ports more straight forward. - Integrated several contributed ports. - Pinerc configuration variable for addressbook location. - SMTP-host config variable now allows a list of host names. - Choice of several rules for generating default folder names in Save. - Several other new .pinerc options. - Many bug fixes! Handling Locking with multiple sessions. Pine 3.84 introduced a new mechanism to handle competition between multiple sessions for a single INBOX. Previously, the first session would have to be stopped before another could get read/write permissions on an open inbox. Now, the newest session forces the older session to surrender read/write access to the mailbox. Note: non-standard mailbox formats exist wherein multiple sessions may all have read-write access. See the Tech Notes in the Pine distribution for more details. Folder Collections. Pine allows you to have full access to sets of folders on you local machine and any IMAP server. These sets of folders are called "collections" and Pine has some special new browsing features to take advantage of them. By default, everyone has one folder collection. Additional collections may be defined by editing your .pinec configuration file. MIME Attachments. Pine now recognizes attachments which are displayable text and marks them the appropriate MIME type for text. Pine has a new system for determining which MIME text attachments should be displayed automatically and which should be displayable on request. In addition there is a new text attachment viewer module just for browsing these attachments. Finally, Pine will now recognize postscript files and TIFF image files and assign the correct MIME type information in the message. OTHER THINGS YOU SHOULD KNOW Several commands can be enabled by .pinerc options, but not all of them actually exist yet. In particular: Flag, Bounce, Pipe, Apply, Zoom Also: news item eXclude/uneXclude and news group subscription/unsubscription are note yet available. Unfortunately, when you Save a message to a folder, the message state flags (e.g. whether it was Deleted, or Answered) are not preserved. This will be fixed in the next release. NNTP vs. IMAP for News: Having a local newsrc file is only needed if news groups are accessed via NNTP rather than IMAP. If you have an account on a machine storing news files, and runs IMAPd, leave your newsrc file there and use IMAP to access news, rather than NNTP. This is accomplished by omitting the /nntp flag in the news host specification in your .pinerc. (NOTE: full NetNews functionality is not yet available in Pine; stay tuned.) The Goto command must now be explicitly enabled by a .pinerc option... Because it requires explicit text input, as opposed to picking from a list of folders, Goto was deemed to be a more power-user oriented command. In the past, it was the only way to get from Index or View back to Folders without first going to the Main menu, but with the advent of "L ListFldrs" that is no longer true. (NOTE: Unix system managers may restore Goto for everyone at once by enabling the command in the global pine config file.) If a file called .mailboxlist exists in any folder-collection directory, attempts to list folders in that collection may fail. Pine will interpret the contents of that file as the list of interesting mailboxes... but if the empty file exists, then it will appear that all of your folders have disappeared. Unfortunately, we just recently learned that Stanford's Xlview program will silently create this file. The next version of Pine will definitely be changed to avoid this problem. If a file called ~/mail.txt exists and is either empty or appears to be a Tenex-style mailbox, Pine will decide to use its "tenex2" driver which will move all pending mail from /usr/spool/mail/$USER to mail.txt, and use mail.txt as your INBOX. This behavior is subject to change. Pine 3.85 will not permit you to create folders ending in .txt This is due to constraints on how mailbox drivers are selected, and is also likely to change in the next release. However, you can rename an existing folder to end in .txt. COMING ATTRACTIONS (but don't ask when!) - Shared (plus personal) address books - Improved network news support, including posting and subscribing - Implementation of "missing" commands (Bounce, Pipe, Flag) - Improved MIME support, including "mailcap" - For PC-Pine, beginnings of "offline" support - For PC-Pine, performance improvement - A Windows/Winsock version (though not initially a GUI) - Access to remote support files: address books, newsrc, pinerc - Operations on multiple messages (aggregate operations) - Threaded Index views - Improved Search capability - Access to directory services from Composer We hope you will find Pine 3.85 useful. Comments are always welcome; please send them to: pine@cac.washington.edu -teg From owner-pine-info@cac.washington.edu Thu Sep 23 19:38:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12399; Thu, 23 Sep 93 19:38:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18103; Thu, 23 Sep 93 19:26:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nic.cic.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18097; Thu, 23 Sep 93 19:26:44 -0700 Received: by nic.cic.net (4.1/SMI-4.1) id AA22017; Thu, 23 Sep 93 22:26:42 EDT Date: Thu, 23 Sep 1993 22:20:21 -0400 (EDT) From: Paul Holbrook Subject: patch to 3.85 to mark msgs cc to self with + To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine 3.85 contains the really nifty feature that messages that are sent directly to you (ie, your mail address is in the To: field) are marked in the index with a +. This feature allows you to quickly see what messages you might want to look at first, as opposed to messages that might be to a mailing list. An old Xerox mailer used to have this feature (any Hardy users out there?), but it would also allow you to mark messages cc'd directly to you as well. So below I present a small hack to allow you to mark messages to yourself. If you install this, you'll see a '+' if the message has you in the to *or* cc list. (I have a vague recollection that I might have suggested this feature to the Pine folks, so I get to hack it the way I want it. And if I didn't suggest it, they must have read my mind.) Now all I want is the ability to sort on messages with that '+' mark. J. Paul Holbrook CICNet Technical Services Manager holbrook@cic.net (313) 998-7680 This patch was made to the file mailindx.c, which can be found in the pine3.85/pine directory. *** mailindx.c.ORIG Tue Sep 21 03:15:11 1993 --- mailindx.c Thu Sep 23 22:05:27 1993 *************** *** 726,731 **** --- 726,735 ---- for(addr = envelope->to; addr && to_us == ' '; addr = addr->next) if(address_is_us(addr, ps_global)) to_us = '+'; + /* holbrook hack 9/23/93 to also mark messages cc'd to us */ + for(addr = envelope->cc; addr && to_us == ' '; addr = addr->next) + if(address_is_us(addr, ps_global)) + to_us = '+'; sprintf(status, "%c %s %-3ld %s %2d ", to_us, status_string(cache), message_number, month_abbrev(d.month), d.day); From owner-pine-info@cac.washington.edu Thu Sep 23 20:58:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13488; Thu, 23 Sep 93 20:58:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18839; Thu, 23 Sep 93 20:49:50 -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 AA18833; Thu, 23 Sep 93 20:49:48 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA23167 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Thu, 23 Sep 93 22:49:46 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA00795; Thu, 23 Sep 93 22:49:45 CDT Date: Thu, 23 Sep 1993 22:48:17 -0500 (CDT) From: Matt Simmons Subject: Pine 3.85 bug (already =) ) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Sep 23 21:09:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13826; Thu, 23 Sep 93 21:09:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24545; Thu, 23 Sep 93 20:56:00 -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 AA24539; Thu, 23 Sep 93 20:55:59 -0700 Received: by jade.saintmarys.edu (1.37.109.4/16.2) id AA01103; Thu, 23 Sep 93 22:57:49 -0500 Date: Thu, 23 Sep 1993 22:53:52 -0500 (EST) From: Dan Mandell Reply-To: Dan Mandell Subject: .addressbook format To: "pine-info@cac.washington.edu" Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII When I try to create an addressbook with a list with 67 names in it constructed according to the pattern (as I close as I can tell) of the addressbooks created by pine 3.07, I have not found it to work. Either the names in the list get jumbled once I have run pine 3.07 or it simply hangs. Is the problem that Pine doesn't want to handle lists with 67 names, or am I not recognizing some subtle format considerations. Does the recent version of Pine handle long address lists more easily? Dan -- ===================================== Dan Mandell, Academic Computing Saint Mary's College Internet: dmandell@saintmarys.edu From owner-pine-info@cac.washington.edu Thu Sep 23 21:16:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13937; Thu, 23 Sep 93 21:16:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19057; Thu, 23 Sep 93 21:08:09 -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 AA19051; Thu, 23 Sep 93 21:08:07 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04438; Thu, 23 Sep 93 21:08:04 -0700 Date: Thu, 23 Sep 1993 21:05:31 -0700 (PDT) From: David L Miller Reply-To: 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 Hmmm... Which platform are you running trying it on? Do you still have the core file? |\ | |\/| 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 Sep 23 21:48:16 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14440; Thu, 23 Sep 93 21:48:16 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24759; Thu, 23 Sep 93 21:37:47 -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 AA24753; Thu, 23 Sep 93 21:37:45 -0700 Received: from rac6.wam.umd.edu by pg2-srv.wam.umd.edu with SMTP id AA21155 (5.65c/IDA-1.4.4 for ); Fri, 24 Sep 1993 00:37:12 -0400 Received: by rac6.wam.umd.edu id AA00950 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 24 Sep 1993 00:37:38 -0400 Date: Fri, 24 Sep 1993 00:35:32 -0400 (EDT) From: Lord Highway of K'tara Subject: Saving Mail into other folders... To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Okay... when I save incoming mail to other folders... it changes the >From field in the mail format... before: From blah@blah.blah.edu Save to folder: From highway@wam.umd.edu How do I change this or remedy this. --------------------- [ 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 Sep 23 21:48:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14442; Thu, 23 Sep 93 21:48:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19242; Thu, 23 Sep 93 21:37:31 -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 AA19236; Thu, 23 Sep 93 21:37:28 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA24875 (5.65b/IDA-1.4.3 for dlm@cac.washington.edu); Thu, 23 Sep 93 23:37:27 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA01823; Thu, 23 Sep 93 23:37:26 CDT Date: Thu, 23 Sep 1993 23:36:06 -0500 (CDT) From: Matt Simmons Subject: Re: Pine 3.85 bug (already =) ) 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 On Thu, 23 Sep 1993, David L Miller wrote: > Hmmm... Which platform are you running trying it on? Do you still have > the core file? Block delete is fun!!!! no core, sorry it didn't spew core when it died... I'm running on a sun... 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 Sep 23 21:57:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14616; Thu, 23 Sep 93 21:57:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19294; Thu, 23 Sep 93 21:47:30 -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 AA19288; Thu, 23 Sep 93 21:47:29 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04886; Thu, 23 Sep 93 21:47:26 -0700 Date: Thu, 23 Sep 1993 21:45:45 -0700 (PDT) From: David L Miller Subject: Re: .addressbook format To: Dan Mandell Cc: "pine-info@cac.washington.edu" In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Are you using tabs between fields? If that isn't it, send me a copy as an attachment and I will take a look at it. |\ | |\/| 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, Dan Mandell wrote: > When I try to create an addressbook with a list with 67 names in it > constructed according to the pattern (as I close as I can tell) of the > addressbooks created by pine 3.07, I have not found it to work. Either > the names in the list get jumbled once I have run pine 3.07 or it simply > hangs. Is the problem that Pine doesn't want to handle lists with 67 > names, or am I not recognizing some subtle format considerations. > > Does the recent version of Pine handle long address lists more easily? > > Dan > > -- > ===================================== > Dan Mandell, Academic Computing > Saint Mary's College > Internet: dmandell@saintmarys.edu > > > > From owner-pine-info@cac.washington.edu Thu Sep 23 22:21:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14946; Thu, 23 Sep 93 22:21:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19411; Thu, 23 Sep 93 22:10: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 AA19405; Thu, 23 Sep 93 22:10:21 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05194; Thu, 23 Sep 93 22:10:19 -0700 Date: Thu, 23 Sep 1993 22:09:04 -0700 (PDT) From: Steve Hubert Subject: Re: .addressbook format To: Dan Mandell Cc: "pine-info@cac.washington.edu" In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 23 Sep 1993, Dan Mandell wrote: > Does the recent version of Pine handle long address lists more easily? Yes, there are several bugs in the 3.07 addressbook code. We hope we got most of them. Steve Hubert From owner-pine-info@cac.washington.edu Thu Sep 23 22:26:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15045; Thu, 23 Sep 93 22:26:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24895; Thu, 23 Sep 93 22:16:28 -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 AA24889; Thu, 23 Sep 93 22:16:26 -0700 Received: by jade.saintmarys.edu (1.37.109.4/16.2) id AA07447; Fri, 24 Sep 93 00:18:16 -0500 Date: Fri, 24 Sep 1993 00:13:48 -0500 (EST) From: Dan Mandell Subject: Re: .addressbook format 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 Sorry for the premature report of an addressbook problem. I had created a file to serve as an addressbook with a mail list with 67 entries in Pine 3.07. I had omitted commas at the end of one or two lines - once I corrected this, and fed the resulting addressbook to pine it did seem to work OK. Thanks, Dan On Thu, 23 Sep 1993, David L Miller wrote: > > Are you using tabs between fields? If that isn't it, send me a copy as > an attachment and I will take a look at it. > > |\ | |\/| 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, Dan Mandell wrote: > > > When I try to create an addressbook with a list with 67 names in it > > constructed according to the pattern (as I close as I can tell) of the > > addressbooks created by pine 3.07, I have not found it to work. Either > > the names in the list get jumbled once I have run pine 3.07 or it simply > > hangs. Is the problem that Pine doesn't want to handle lists with 67 > > names, or am I not recognizing some subtle format considerations. > > > > Does the recent version of Pine handle long address lists more easily? > > > > Dan > > > > -- > > ===================================== > > Dan Mandell, Academic Computing > > Saint Mary's College > > Internet: dmandell@saintmarys.edu > > > > > > > > > -- ===================================== Dan Mandell, Academic Computing Saint Mary's College Internet: dmandell@saintmarys.edu From owner-pine-info@cac.washington.edu Thu Sep 23 22:36:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15222; Thu, 23 Sep 93 22:36:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24921; Thu, 23 Sep 93 22:26:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nico.aarnet.edu.au by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24915; Thu, 23 Sep 93 22:26:45 -0700 Received: from cruskit.aarnet.edu.au by nico.aarnet.edu.au with SMTP id AA14243 (5.65cAARN/IDA-1.4.4 for ); Fri, 24 Sep 1993 15:25:10 +1000 Received: from localhost by cruskit.aarnet.edu.au id for aarnet.edu.au; Fri, 24 Sep 1993 15:25:11 +1000 Date: Fri, 24 Sep 1993 15:24:33 +1000 (EST) From: Andy Linton Subject: Pine dumps core when I quit To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've just upgraded to 3.85 from 3.07. Both versions have the 'feature' that they dump a core in my home directory when I 'quit'. I really don't need an 8-9 Mbyte core file permanently hanging around. I'm running on a Sun IPX with SunOS4.1.3. I tried rebuilding 3.85 with debugging turned off but than doesn't seem to help. Is this a Sun specific feature or is it just me? andy -- Andy Linton A.Linton@aarnet.edu.au Network Engineer phone: +61 6 249 2874 AARNet fax: +61 6 249 1369 -- From owner-pine-info@cac.washington.edu Fri Sep 24 00:23:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16747; Fri, 24 Sep 93 00:23:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20105; Fri, 24 Sep 93 00:11:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hula.oit.Hawaii.Edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20099; Fri, 24 Sep 93 00:11:09 -0700 Received: by hula.oit.Hawaii.Edu (4.1/SMI-4.1.1) id AA28790; Thu, 23 Sep 93 21:12:34 HST Date: Thu, 23 Sep 1993 21:11:08 -1000 (HST) From: David Lassner Subject: Re: Pine dumps core when I quit To: Andy Linton Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Andy -- Works ok for me under 4.1.3 on a SPARC2. david > I've just upgraded to 3.85 from 3.07. Both versions have the 'feature' > that they dump a core in my home directory when I 'quit'. I really don't > need an 8-9 Mbyte core file permanently hanging around. > > I'm running on a Sun IPX with SunOS4.1.3. I tried rebuilding 3.85 with > debugging turned off but than doesn't seem to help. > > Is this a Sun specific feature or is it just me? > > andy From owner-pine-info@cac.washington.edu Fri Sep 24 00:51:55 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17469; Fri, 24 Sep 93 00:51:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20269; Fri, 24 Sep 93 00:43:25 -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 AA20263; Fri, 24 Sep 93 00:43:22 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA13371; Fri, 24 Sep 93 02:41:41 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA04128; Fri, 24 Sep 93 15:25:41 +0800 Date: Fri, 24 Sep 1993 15:24:12 +0800 (TPE) From: Ed Greshko Subject: Re: Pine dumps core when I quit To: Andy Linton Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Andy Linton wrote: > I've just upgraded to 3.85 from 3.07. Both versions have the 'feature' > that they dump a core in my home directory when I 'quit'. I really don't > need an 8-9 Mbyte core file permanently hanging around. > > I'm running on a Sun IPX with SunOS4.1.3. I tried rebuilding 3.85 with > debugging turned off but than doesn't seem to help. > > Is this a Sun specific feature or is it just me? Sounds like it is a "Sun specific feature". I've been using both pine 3.07 and now 3.85 on a MIPS machine and it has never had the occasion to core dump. 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 Sep 24 05:05:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22770; Fri, 24 Sep 93 05:05:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21775; Fri, 24 Sep 93 04:53:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21769; Fri, 24 Sep 93 04:53:41 -0700 Received: from vax.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <11749-0@oxmail.ox.ac.uk>; Fri, 24 Sep 1993 12:53:26 +0100 Received: by vax.ox.ac.uk (MX V3.3 VAX) id 15253; Fri, 24 Sep 1993 12:53:20 +0100 Date: Fri, 24 Sep 1993 12:53:15 +0100 From: "Neil J Long, Dept of Materials" To: PINE-INFO@CAC.WASHINGTON.EDU Cc: long@vax.ox.ac.uk Message-Id: <00973062.3C0AE7E8.15253@vax.ox.ac.uk> Subject: NEWSRC format for PC-Pine Hi I have been trying my luck with PC-Pine 3.85 and news reading. I finally found the format that seems to work, e.g. comp.lang.c : Without any included item numbers there are lots of [HOLES] messages from the NNTP server which appear as message missing. Exiting Pine I get a message that it is updating the status of the folder (I guess to mark them as read/unread) but nothing changes in the newsrc file (I found it had to go in c:\newsrc). Could someone help me get the format, etc right. Thanks Neil From owner-pine-info@cac.washington.edu Fri Sep 24 06:09:35 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23627; Fri, 24 Sep 93 06:09:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26608; Fri, 24 Sep 93 06:01:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from paradiso.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26602; Fri, 24 Sep 93 06:01:33 -0700 Message-Id: <9309241301.AA26602@mx2.cac.washington.edu> Received: from localhost by paradiso.umd.edu (8.5/16.2) id JAA01602; Fri, 24 Sep 1993 09:01:42 -0400 From: Rocky Giannini Subject: Problems compiling Pine 3.85 under Solaris 2.2 To: pine-info@cac.washington.edu Date: Fri, 24 Sep 1993 09:01:41 -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: 769 I just tried compiling Pine 3.85 under Solaris 2.2 and got the following error messages: ---- Making Pine. rm -f os.h ln -s osdep/os-sv4.h os.h ./cmplhlp2.sh < pine.hlp > helptext.h cc -DSV4 -g -DDEBUG -c addrbook.c "/usr/include/unistd.h", line 156: identifier redeclared: rename "addrbook.c", line 200: warning: semantics of ">" change in ANSI C; use explicit cast "ddrbook.c", line 204: warning: semantics of ">" change in ANSI C; use explicit cast "addrbook.c", line 1342: cannot recover from previous errors cc: acomp failed for addrbook.c *** Error code 1 make: Fatal error: Command failed for target `addrbook.o' ---- Pico compiled fine. Could someone please tell me what's going wrong here? Thanks! -Rocky -- Rocky Giannini UMUC Unix and VMS Systems From owner-pine-info@cac.washington.edu Fri Sep 24 06:26:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23877; Fri, 24 Sep 93 06:26:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22429; Fri, 24 Sep 93 06:18:54 -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 AA22421; Fri, 24 Sep 93 06:18:52 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <13016-0@dummy1.dur.ac.uk>; Fri, 24 Sep 1993 14:15:06 +0100 Received: from altair (altair.dur.ac.uk) by vega.dur.ac.uk; Fri, 24 Sep 93 14:15:04 BST Date: Fri, 24 Sep 1993 14:12:49 +0100 (BST) From: Barry Cornelius Subject: Re: Problems compiling Pine 3.85 under Solaris 2.2 To: Rocky Giannini Cc: pine-info@cac.washington.edu In-Reply-To: <9309241301.AA26602@mx2.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 583 On Fri, 24 Sep 1993, Rocky Giannini wrote: > I just tried compiling Pine 3.85 under Solaris 2.2 and got the following > error messages: > [stuff deleted] I think your problem is that you are not compiling using the -Xs option. I have successfully compiled 3.85 for SunOS 5.2 (Solaris 2.2), having used: /opt/SUNWspro/bin/cc -Xs ... for the compilations. -- 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 Sep 24 06:26:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23912; Fri, 24 Sep 93 06:26:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22449; Fri, 24 Sep 93 06:19:53 -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 AA22443; Fri, 24 Sep 93 06:19:52 -0700 Received: by herald.usask.ca (5.65/DEC-Ultrix/4.3) id AA10750; Fri, 24 Sep 1993 07:19:50 -0600 for pine-info@cac.washington.edu Date: Fri, 24 Sep 1993 07:18:00 -0600 (CST) From: Peter Scott U Sask Library Systems Dept Subject: Pine Demo To: pine-info@cac.washington.edu In-Reply-To: <9309241301.AA26602@mx2.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I notice that the Pine demo at telnet to demo.cac.washington.edu (login pinedemo) is running version 3.07. Will this be upgraded soon to the latest version? From owner-pine-info@cac.washington.edu Fri Sep 24 07:38:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25229; Fri, 24 Sep 93 07:38:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23168; Fri, 24 Sep 93 07:30:40 -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 AA23162; Fri, 24 Sep 93 07:30:38 -0700 Received: from comet.med.utah.edu by corona.med.utah.edu (4.1/SMI-4.0 [uucc-nhj/15FEB1991]) id AA28779; Fri, 24 Sep 93 08:30:35 MDT Received: by comet.med.utah.edu (5.57/Ultrix3.0-C) id AA06793; Fri, 24 Sep 93 08:30:35 -0600 Date: Fri, 24 Sep 1993 08:28:44 -0600 (MDT) From: "Paul G. Leo Jr." Subject: global addressbook To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Perhaps this has already been covered, sorry if I missed it. Is there a way to set a global addressbook in pine, or import one? Is there a way to have more than one addressbook? 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 Sep 24 08:34:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26733; Fri, 24 Sep 93 08:34:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23981; Fri, 24 Sep 93 08:25:56 -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 AA23975; Fri, 24 Sep 93 08:25:55 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14824; Fri, 24 Sep 93 08:25:51 -0700 Date: Fri, 24 Sep 1993 08:24:24 -0700 (PDT) From: Terry Gray Subject: Re: global addressbook To: "Paul G. Leo Jr." Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Alas, not yet. But this is definitely on the "short list". -teg On Fri, 24 Sep 1993, Paul G. Leo Jr. wrote: > > Perhaps this has already been covered, sorry if I missed it. Is there a > way to set a global addressbook in pine, or import one? Is there a way to > have more than one addressbook? > > > 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 Sep 24 08:57:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27721; Fri, 24 Sep 93 08:57:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24429; Fri, 24 Sep 93 08:44:47 -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 AA24423; Fri, 24 Sep 93 08:44:44 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12516; Fri, 24 Sep 93 08:44:41 -0700 Date: Fri, 24 Sep 1993 08:38:40 -0700 (PDT) From: David L Miller Subject: Re: global addressbook To: "Paul G. Leo Jr." Cc: Terry Gray , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The first step in that direction has been taken, with the addition of the "address-book" variable in the .pinerc file for Pine 3.85. The only problem with using this now to share a single addressbook is that there are file locking problems that have not been addressed... As Terry hinted at, there will be support for multiple and remote addressbooks in a future release. The remote case is almost trivial, but the multiple case requires some redesign... --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 Fri, 24 Sep 1993, Terry Gray wrote: > Alas, not yet. But this is definitely on the "short list". > > -teg > > On Fri, 24 Sep 1993, Paul G. Leo Jr. wrote: > > > > > Perhaps this has already been covered, sorry if I missed it. Is there a > > way to set a global addressbook in pine, or import one? Is there a way to > > have more than one addressbook? > > > > > > 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 Sep 24 09:02:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27933; Fri, 24 Sep 93 09:02:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24594; Fri, 24 Sep 93 08:51:09 -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 AA24588; Fri, 24 Sep 93 08:51:07 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12664; Fri, 24 Sep 93 08:51:01 -0700 Date: Fri, 24 Sep 1993 08:47:51 -0700 (PDT) From: David L Miller Subject: Re: NEWSRC format for PC-Pine To: "Neil J Long, Dept of Materials" Cc: PINE-INFO@CAC.WASHINGTON.EDU, long@vax.ox.ac.uk In-Reply-To: <00973062.3C0AE7E8.15253@vax.ox.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The easiest way to "get it right" is to copy a .newsrc from a Unix host. Pine uses the same format, and you can pick up right where you left off with rn/trn/nn... Right now, Newsreading in Pine is *very* primitive, but enhancements are very definitely coming. |\ | |\/| 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, 24 Sep 1993, Neil J Long, Dept of Materials wrote: > Hi > I have been trying my luck with PC-Pine 3.85 and news reading. I finally found > the format that seems to work, e.g. > comp.lang.c : > Without any included item numbers there are lots of [HOLES] messages from the > NNTP server which appear as message missing. Exiting Pine I get a message that > it is updating the status of the folder (I guess to mark them as read/unread) > but nothing changes in the newsrc file (I found it had to go in c:\newsrc). > Could someone help me get the format, etc right. > Thanks > Neil > From owner-pine-info@cac.washington.edu Fri Sep 24 09:31:56 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29039; Fri, 24 Sep 93 09:31:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27492; Fri, 24 Sep 93 09:20:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nova.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27486; Fri, 24 Sep 93 09:20:41 -0700 Received: from localhost by nova.umd.edu (8.5/16.2) id MAA18459; Fri, 24 Sep 1993 12:19:59 -0400 Date: Fri, 24 Sep 1993 12:14:15 -0400 (EDT) From: Rocky Giannini Reply-To: Rocky Giannini Subject: Pine dumps core when replying. To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I have found a repeatable bug in the Solaris version of Pine. When replying to a message I get a core dump about 80% of the time. Is anyone else having this problem? .pine-debug file follows: ======================================================================== Debug output of the Pine program (at debug level 2). Version 3.85 Fri Sep 24 12:08:59 1993 reading_pinerc "/usr/local/lib/pine.conf" Read 5974 characters pinerc : /usr/local/l : default-fcc : "mail.sent" pinerc : /usr/local/l : mail-directory : "Mail" pinerc : /usr/local/l : read-message-folder : "received" pinerc : /usr/local/l : signature-file : ".signature" pinerc : /usr/local/l : feature-list : "old-growth" reading_pinerc "/users/systems/rocky/.pinerc" Read 5864 characters pinerc : /users/syste : last-time-prune-ques : "93.9" pinerc : /users/syste : default-fcc : "" pinerc : /users/syste : editor : "/usr/local/bin/emacs" pinerc : /users/syste : folder-collections : "Mail/[]" pinerc : /users/syste : last-version-used : "3.85" personal-name : user-id : user-domain : smtp-server : inbox-path : inbox inbox incoming-folders : folder-collection : Mail/[] Mail/[] news-collections : default-fcc : mail.sent mail-directory : Mail Mail read-message-fold : received received 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 : /usr/local/bin/ema /usr/local/bin/ema image-viewer : use-only-domain-n : no no printer : attached-to-ansi attached-to-ansi personal-print-co : standard-printer : lp lp last-time-prune-q : 93.9 93.9 last-version-used : 3.85 3.85 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: rocky Fullname: "Rocky Giannini" User domain name being used "" Local Domain name being used "nova" Host name being used "nova" Mail Domain name being used "nova" ioctl(TIOCWINSZ) failed :Invalid argument Terminal type: vt100 Context Mail/[] type: LOCAL About to open folder "INBOX" inbox: "INBOX" broach_folder: nickname for inbox is INBOX Opened folder "/var/mail/rocky" with 4 messages Sorting by arrival ---- MAIL INDEX ---- Want_to read: RETURN (13) about to end_tty_driver Pine Panic: Received abort signal Rocky Giannini UMUC Unix and VMS Systems From owner-pine-info@cac.washington.edu Fri Sep 24 10:18:20 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01110; Fri, 24 Sep 93 10:18:20 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26051; Fri, 24 Sep 93 10:05:47 -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 AA26045; Fri, 24 Sep 93 10:05:45 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <17485-0@dummy1.dur.ac.uk>; Fri, 24 Sep 1993 18:04:14 +0100 Received: from altair (altair.dur.ac.uk) by vega.dur.ac.uk; Fri, 24 Sep 93 18:04:11 BST Date: Fri, 24 Sep 1993 18:01:51 +0100 (BST) From: Barry Cornelius Subject: Re: Pine dumps core when replying. To: Rocky Giannini Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 694 On Fri, 24 Sep 1993, Rocky Giannini wrote: > I have found a repeatable bug in the Solaris version of Pine. When replying > to a message I get a core dump about 80% of the time. Is anyone else > having this problem? > [stuff deleted] Are you using pine-bin-solaris from pine.ftp.washington.edu or a binary that you have built yourself? I have built a version of Pine 3.85 for SunOS 5.2 (Solaris 2.2) and it doesn't seem to suffer from the problem you mention. -- 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 Sep 24 11:28:22 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04116; Fri, 24 Sep 93 11:28:22 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28184; Fri, 24 Sep 93 11:18:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28178; Fri, 24 Sep 93 11:18:12 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA06435; Fri, 24 Sep 93 11:19:02 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA01910; Fri, 24 Sep 93 11:21:05 -0700 Date: Fri, 24 Sep 1993 11:20:11 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Pine dumps core when I quit To: Andy Linton Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Andy Linton wrote: > I've just upgraded to 3.85 from 3.07. Both versions have the 'feature' > that they dump a core in my home directory when I 'quit'. I really don't > need an 8-9 Mbyte core file permanently hanging around. > > I'm running on a Sun IPX with SunOS4.1.3. I tried rebuilding 3.85 with > debugging turned off but than doesn't seem to help. On a Sun SparcStation 2 running SunOS 4.1.3 we do not have this problem... > > Is this a Sun specific feature or is it just me? > > andy > -- > Andy Linton A.Linton@aarnet.edu.au > Network Engineer phone: +61 6 249 2874 > AARNet fax: +61 6 249 1369 > -- > > > > ------------------------------------------------------------------------------ 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 Sep 24 11:31:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04235; Fri, 24 Sep 93 11:31:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27548; Fri, 24 Sep 93 11:17:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay2.pipex.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27542; Fri, 24 Sep 93 11:17:54 -0700 Received: from tdc.dircon.co.uk by relay1.pipex.net with SMTP (PP) id <23271-0@relay1.pipex.net>; Fri, 24 Sep 1993 19:17:22 +0100 Received: from tdc.dircon.co.uk by tdc.dircon.co.uk id aa16981; 24 Sep 93 19:18 BST Subject: Pine 3.85 under SCO - dumps core on message To: pine-info@cac.washington.edu Date: Fri, 24 Sep 1993 19:18:33 +0100 (BST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3045 From: Ben Knox Message-Id: <9309241918.aa16969@tdc.dircon.co.uk> I've managed to compile pine under SCO UNIX v3.2.4 (after some twiddling with the c-client code to get mmdf working). I used the os-gen files under pine/osdep to get it all compiled. All seems to work pretty well (ie I can read messages), accept when I try to read the following message: ^A^A^A^A >From MAILER-DAEMON Tue Jun 22 20:00:52 1993 Received: by figment.dircon.co.uk (5.65c/2.00) id AA20061; Tue, 22 Jun 1993 15:59:34 -0300 Date: Tue, 22 Jun 1993 15:59:34 -0300 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Cannot send message for 3 days Message-Id: <199306221859.AA20061@figment.dircon.co.uk> To: sys0001 Status: O X-Status: ----- Transcript of session follows ----- 421 fax_server.dircon.co.uk (tcpld)... Deferred: Connection timed out during user open with fax_server.dircon.co.uk ----- Unsent message follows ----- Received: by figment.dircon.co.uk (5.65c/2.00) id AA02515; Sat, 19 Jun 1993 15:59:21 -0300 From: sys0001 (TDC administration account) Message-Id: <199306191859.AA02515@figment.dircon.co.uk> Subject: queue test To: asd@fax_server Date: Sat, 19 Jun 1993 19:59:20 +0100 (BST) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 20 see how this works? ^A^A^A^A The ^A^A^A^As are the MMDF separators. The message causes a core dump in the following way: I press RETURN to display the message and the following is displayed: >From MAILER-DAEMON Tue Jun 22 20:00:52 1993 Received: by figment.dircon.co.uk (5.65c/2.00) id AA20061; Tue, 22 Jun 1993 15:59:34 -0300 Date: Tue, 22 Jun 1993 15:59:34 -0300 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Cannot send message for 3 days Message-Id: <199306221859.AA20061@figment.dircon.co.uk> To: sys0001 Status: O X-Status: ----- Transcript of session follows ----- 421 fax_server.dircon.co.uk (tcpld)... Deferred: Connection timed out during user open with fax_server.dircon.co.uk ----- Unsent message follows ----- Received: by figment.dircon.co.uk (5.65c/2.00) Floating exception(coredump) Looking at the core dump with sdb shows the following: $ sdb pine 0x3b9f7 in Writechar:969: prev_tab(ps_global->ttyo->screen_cols, tabspacing)) *t Writechar(ch=9,new_esc_len=245640) [ttyout.c:969] PutLine0n8b(x=13,y=0,line=^Iid AA02515; Sat, 19 Jun 1993 15:59:21 -0300^JFrom: sys0001 (TDC administration account)^JMessage-Id: <199306191859.AA02515@figmen,length=44) [ttyout.c:1099] redraw_scroll_text(0x13) [mailview.c:1724] scroll_scroll_text(new_top_line=0,redraw=1) [mailview.c:2097] scrolltool(text=0x46d0ec,title=MESSAGE TEXT,pages=0,style=3,source=1,att=0) [mailview.c:1215] mail_view_screen(pine_state=0x46495c) [mailview.c:238] main(argc=2,argv=0x7ffffde4) [pine.c:599] * The .pine-debug file doesn't show anything of interest at the point where the core dump occurs. Is this a bug? Regards, Ben -- Ben Knox ben@dircon.co.uk ...!pipex!dircon!ben From owner-pine-info@cac.washington.edu Fri Sep 24 12:41:52 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07118; Fri, 24 Sep 93 12:41:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29159; Fri, 24 Sep 93 12:31:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from medusa.unm.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29153; Fri, 24 Sep 93 12:31:44 -0700 Received: from [129.24.128.120] (som06.unm.edu) by MEDUSA.UNM.EDU (PMDF V4.2-14 #5028) id <01H3BTVFS24G000467@MEDUSA.UNM.EDU>; Fri, 24 Sep 1993 13:31:41 MDT Date: Fri, 24 Sep 1993 13:31:51 -0700 From: sday@MEDUSA.UNM.EDU (Stephen F. Day UNM Med Ctr Comp Svcs) Subject: Re: NEWSRC format for PC-Pine To: "Neil J Long, Dept of Materials" , PINE-INFO@CAC.WASHINGTON.EDU Message-Id: <01H3BTVG4NG2000467@MEDUSA.UNM.EDU> Content-Transfer-Encoding: 7BIT At 12:53 1993-09-24 +0100, Neil J Long, Dept of Materials wrote: >Hi >I have been trying my luck with PC-Pine 3.85 and news reading. I finally found >the format that seems to work, e.g. >comp.lang.c : >Without any included item numbers there are lots of [HOLES] messages from the >NNTP server which appear as message missing. Exiting Pine I get a message that >it is updating the status of the folder (I guess to mark them as read/unread) >but nothing changes in the newsrc file (I found it had to go in c:\newsrc). >Could someone help me get the format, etc right. I simply copied my .newsrc from my Unix account and it seems to work well from that. If you don't have a Unix template to go by, e-mail me and I'll send you a copy of mine. However, I do have a concern of my own regarding reading news in PC-Pine -- It seems that it takes f-o-r-e-v-e-r when I go into news groups that have more than a handful of articles posted. I have a 486DX/66MHz system running DOS 6 and NCSA Telnet with plenty of disc space. When I went into a group with 154 articles, it has been sorting for the past hour nonstop (I hope my hard disc survives!) -- I've let it sort for several hours before I finally give up and turn the darn thing off. This is true for any news group I have tried -- I can't imagine any user wanting to wait that long to read news!! Our Mac users use NewsWatcher and the results are fairly instantaneous (well, at least compared to what I have seen with the news on PC-Pine). Any ideas what's causing this?? Thanks! >Neil =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Stephen F. Day (SFD7) AT&TNET: (505) 277-1698 Director BITNET/CREN: SDAY@MEDUSA Medical Ctr Computer Services INTERNET: sday@medusa.UNM.EDU University of New Mexico TECHNET: UNMSDAY =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-pine-info@cac.washington.edu Fri Sep 24 12:58:52 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07792; Fri, 24 Sep 93 12:58:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29475; Fri, 24 Sep 93 12:50:39 -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 AA29469; Fri, 24 Sep 93 12:50:38 -0700 Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27006; Fri, 24 Sep 93 12:50:23 -0700 Date: Fri, 24 Sep 1993 12:44:04 -0700 (PDT) From: Terry Gray Subject: Re: NEWSRC format for PC-Pine To: "Stephen F. Day UNM Med Ctr Comp Svcs" Cc: "Neil J Long, Dept of Materials" , PINE-INFO@CAC.WASHINGTON.EDU In-Reply-To: <01H3BTVG4NG2000467@MEDUSA.UNM.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Stephen F. Day UNM Med Ctr Comp Svcs wrote: > However, I do have a concern of my own regarding reading news in PC-Pine -- > It seems that it takes f-o-r-e-v-e-r when I go into news groups that have > more than a handful of articles posted. I have a 486DX/66MHz system > running DOS 6 and NCSA Telnet with plenty of disc space. When I went into a > group with 154 articles, it has been sorting for the past hour nonstop (I > hope my hard disc survives!) -- I've let it sort for several hours before I > finally give up and turn the darn thing off. This is true for any news > group I have tried -- I can't imagine any user wanting to wait that long to > read news!! >From the Release Notes (type R from the main menu to view them): ---------- VIII. PC-PINE DIFFERENCES/LIMITATIONS -Sorting the index is *hopelessly* slow right now... especially for newsgroups accessed via NNTP. ---------- > Our Mac users use NewsWatcher and the results are fairly instantaneous > (well, at least compared to what I have seen with the news on PC-Pine). > > Any ideas what's causing this?? Thanks! Yes. We're painfully aware of what's happening, and hope to make substantial improvements in PC-Pine sorting performance. For now, all I can say is: learn to like "arrival" order... :) -teg From owner-pine-info@cac.washington.edu Fri Sep 24 13:32:43 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09373; Fri, 24 Sep 93 13:32:43 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00288; Fri, 24 Sep 93 13:21: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 AA00282; Fri, 24 Sep 93 13:21:23 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20985; Fri, 24 Sep 93 13:21:20 -0700 Date: Fri, 24 Sep 1993 13:20:40 -0700 (PDT) From: David L Miller Subject: Re: patch to 3.85 to mark msgs cc to self with + To: Paul Holbrook Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks for the patch. We will put it in the contrib directory for the next 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, 23 Sep 1993, Paul Holbrook wrote: > Pine 3.85 contains the really nifty feature that messages that are sent > directly to you (ie, your mail address is in the To: field) are marked in > the index with a +. This feature allows you to quickly see what messages > you might want to look at first, as opposed to messages that might be to > a mailing list. > > An old Xerox mailer used to have this feature (any Hardy users out > there?), but it would also allow you to mark messages cc'd directly to > you as well. So below I present a small hack to allow you to mark > messages to yourself. If you install this, you'll see a '+' if the > message has you in the to *or* cc list. (I have a vague recollection > that I might have suggested this feature to the Pine folks, so I get to > hack it the way I want it. And if I didn't suggest it, they must have > read my mind.) > > Now all I want is the ability to sort on messages with that '+' mark. > > J. Paul Holbrook > CICNet Technical Services Manager > holbrook@cic.net (313) 998-7680 > > This patch was made to the file mailindx.c, which can be found in the > pine3.85/pine directory. > > *** mailindx.c.ORIG Tue Sep 21 03:15:11 1993 > --- mailindx.c Thu Sep 23 22:05:27 1993 > *************** > *** 726,731 **** > --- 726,735 ---- > for(addr = envelope->to; addr && to_us == ' '; addr = addr->next) > if(address_is_us(addr, ps_global)) > to_us = '+'; > + /* holbrook hack 9/23/93 to also mark messages cc'd to us */ > + for(addr = envelope->cc; addr && to_us == ' '; addr = addr->next) > + if(address_is_us(addr, ps_global)) > + to_us = '+'; > > sprintf(status, "%c %s %-3ld %s %2d ", to_us, status_string(cache), > message_number, month_abbrev(d.month), d.day); > > > From owner-pine-info@cac.washington.edu Fri Sep 24 14:04:25 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10757; Fri, 24 Sep 93 14:04:25 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29249; Fri, 24 Sep 93 13:52:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from skinner.cs.uoregon.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29243; Fri, 24 Sep 93 13:52:29 -0700 Received: from majestix.cs.uoregon.edu by skinner.cs.uoregon.edu with SMTP id AA21852 (5.65/IDA-1.4.2 for pine-info@cac.washington.edu); Fri, 24 Sep 93 13:52:27 -0700 Date: Fri, 24 Sep 1993 13:50:31 -0700 (PDT) From: "Tom C. May" Subject: RS/6000 installation To: pine-info@cac.washington.edu Cc: Tom May Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I built pine 3.85 on an RS/6000 730 without any difficulty. However, executing it results in the following message & termination::: Who are you? (Unable to look up login name) Any idea what isn't configured correctly??? Thanks, -tm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Tom C. May _________ tcmay@cs.uoregon.edu _ _ Computer & Info Science | Office : (503) 346-0892 | \ / | University of Oregon | Fax : (503) 346-5373 | \/ | Eugene, OR 97403-1202 ........|...................................| |.. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ---------- Forwarded message ---------- Date: Thu, 23 Sep 1993 22:20:21 -0400 (EDT) From: Paul Holbrook To: pine-info@cac.washington.edu Subject: patch to 3.85 to mark msgs cc to self with + Pine 3.85 contains the really nifty feature that messages that are sent directly to you (ie, your mail address is in the To: field) are marked in the index with a +. This feature allows you to quickly see what messages you might want to look at first, as opposed to messages that might be to a mailing list. An old Xerox mailer used to have this feature (any Hardy users out there?), but it would also allow you to mark messages cc'd directly to you as well. So below I present a small hack to allow you to mark messages to yourself. If you install this, you'll see a '+' if the message has you in the to *or* cc list. (I have a vague recollection that I might have suggested this feature to the Pine folks, so I get to hack it the way I want it. And if I didn't suggest it, they must have read my mind.) Now all I want is the ability to sort on messages with that '+' mark. J. Paul Holbrook CICNet Technical Services Manager holbrook@cic.net (313) 998-7680 This patch was made to the file mailindx.c, which can be found in the pine3.85/pine directory. *** mailindx.c.ORIG Tue Sep 21 03:15:11 1993 --- mailindx.c Thu Sep 23 22:05:27 1993 *************** *** 726,731 **** --- 726,735 ---- for(addr = envelope->to; addr && to_us == ' '; addr = addr->next) if(address_is_us(addr, ps_global)) to_us = '+'; + /* holbrook hack 9/23/93 to also mark messages cc'd to us */ + for(addr = envelope->cc; addr && to_us == ' '; addr = addr->next) + if(address_is_us(addr, ps_global)) + to_us = '+'; sprintf(status, "%c %s %-3ld %s %2d ", to_us, status_string(cache), message_number, month_abbrev(d.month), d.day); From owner-pine-info@cac.washington.edu Fri Sep 24 14:12:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10920; Fri, 24 Sep 93 14:12:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29311; Fri, 24 Sep 93 14:03: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 AA29305; Fri, 24 Sep 93 14:03:48 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02656; Fri, 24 Sep 93 14:03:42 -0700 Date: Fri, 24 Sep 1993 13:51:51 -0700 (PDT) From: Mark Crispin Subject: Re: NEWSRC format for PC-Pine To: "Neil J Long, Dept of Materials" Cc: PINE-INFO@CAC.WASHINGTON.EDU, long@vax.ox.ac.uk In-Reply-To: <00973062.3C0AE7E8.15253@vax.ox.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Neil J Long, Dept of Materials wrote: > I have been trying my luck with PC-Pine 3.85 and news reading. I finally found > the format that seems to work, e.g. > comp.lang.c : > Without any included item numbers there are lots of [HOLES] messages from the > NNTP server which appear as message missing. Exiting Pine I get a message that > it is updating the status of the folder (I guess to mark them as read/unread) > but nothing changes in the newsrc file (I found it had to go in c:\newsrc). > Could someone help me get the format, etc right. The problem is that you have a space between the newsgroup name and the colon. There should be a space after the colon, but not before. Normally, you should not be manually creating or editing a newsrc file. If you go to a newsgroup that is not in the newsrc file, Pine will automatically add it to the list in the proper format. The [HOLES] message indicates that you are talking to an NNTP server that does not support the new LISTGROUP command. With such an NNTP server, there is no way to know what message numbers exist and what ones do not exist, so even though it knows that there are, say, 435 messages in the newsgroup with a range of 5 to 899 it does not know what the 332nd message is (there are gaps in the sequence). Such holes will show up in the browser as empty mesages. With an NNTP server that supports the LISTGROUP command, Pine can suppress the holes. The INN NNTP server is such a server. From owner-pine-info@cac.washington.edu Fri Sep 24 14:21:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11306; Fri, 24 Sep 93 14:21:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01222; Fri, 24 Sep 93 14:09:13 -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 AA01216; Fri, 24 Sep 93 14:09:04 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22035; Fri, 24 Sep 93 14:08:59 -0700 Date: Fri, 24 Sep 1993 14:07:23 -0700 (PDT) From: David L Miller Subject: Re: Pine 3.85 under SCO - dumps core on message To: Ben Knox Cc: pine-info@cac.washington.edu In-Reply-To: <9309241918.aa16969@tdc.dircon.co.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In sdb, can you get the value of "tabspacing"? |\ | |\/| 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, 24 Sep 1993, Ben Knox wrote: > I've managed to compile pine under SCO UNIX v3.2.4 (after some twiddling > with the c-client code to get mmdf working). I used the os-gen files under > pine/osdep to get it all compiled. > > All seems to work pretty well (ie I can read messages), accept when I try to > read the following message: > > ^A^A^A^A From owner-pine-info@cac.washington.edu Fri Sep 24 14:48:14 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12719; Fri, 24 Sep 93 14:48:14 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29604; Fri, 24 Sep 93 14:39:39 -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 AA29598; Fri, 24 Sep 93 14:39:37 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA02701; Fri, 24 Sep 93 14:39:23 -0700 Date: Fri, 24 Sep 1993 14:31:29 -0700 (PDT) From: Mark Crispin Reply-To: Mark Crispin Subject: Re: NEWSRC format for PC-Pine To: "Stephen F. Day UNM Med Ctr Comp Svcs" Cc: "Neil J Long, Dept of Materials" , PINE-INFO@CAC.WASHINGTON.EDU In-Reply-To: <01H3BTVG4NG2000467@MEDUSA.UNM.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 24 Sep 1993, Stephen F. Day UNM Med Ctr Comp Svcs wrote: > However, I do have a concern of my own regarding reading news in PC-Pine -- > It seems that it takes f-o-r-e-v-e-r when I go into news groups that have > more than a handful of articles posted. I have a 486DX/66MHz system > running DOS 6 and NCSA Telnet with plenty of disc space. When I went into a > group with 154 articles, it has been sorting for the past hour nonstop (I > hope my hard disc survives!) -- I've let it sort for several hours before I > finally give up and turn the darn thing off. This is true for any news > group I have tried -- I can't imagine any user wanting to wait that long to > read news!! If you can establish an IMAP-based news server (meaning that the .newsrc is on the server, so you have an account on the server), you'll find that sorting will be much faster. It won't be instantaneous, but there would be a lot less work on the network and on the PC. Also, UNIX Pine and PC Pine will be at much closer to the same speed. What is happening is that Pine is ending up fetching all the messages and sorting. With UNIX Pine, this is merely an annoyance, but in PC Pine, it is disasterous; since it only has limited caching (and even index information has to be rolled out to disk -- thank you, DOS 640K limits...) it often ends up fetching the same information, over and over again. We know that this is terrible. We don't sort NNTP newsgroups with PC Pine. We will be working on this. We apologize for this problem, but given the long delays to release Pine 3.85 we really didn't want to hold the release another several months to get this fixed. It is my hope that we will have more frequent releases (including maintenance releases) after this. > Our Mac users use NewsWatcher and the results are fairly instantaneous > (well, at least compared to what I have seen with the news on PC-Pine). Do you have sorting in NewsWatcher? I would be very interested to know how the Mac does it (I suspect it keeps a local cache on the disk). From owner-pine-info@cac.washington.edu Fri Sep 24 15:02:40 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13278; Fri, 24 Sep 93 15:02:40 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29665; Fri, 24 Sep 93 14:47:54 -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 AA29659; Fri, 24 Sep 93 14:47:51 -0700 Received: by halcyon.com id AA28751 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 24 Sep 1993 14:47:41 -0700 From: Ralph Sims Message-Id: <199309242147.AA28751@halcyon.com> Subject: Re: RS/6000 installation To: tcmay@cs.uoregon.edu (Tom C. May) Date: Fri, 24 Sep 1993 14:47:38 -0700 (PDT) Cc: pine-info@cac.washington.edu, tcmay@skinner.cs.uoregon.edu In-Reply-To: from "Tom C. May" at Sep 24, 93 01:50:31 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: 238 > I built pine 3.85 on an RS/6000 730 without any difficulty. However, > executing it results in the following message & termination::: It didn't build on ULTRIX 4.1. Pico did, but pine didn't. Anyone have help for this architecture? From owner-pine-info@cac.washington.edu Fri Sep 24 15:17:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13825; Fri, 24 Sep 93 15:17:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02196; Fri, 24 Sep 93 15:06: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 AA02190; Fri, 24 Sep 93 15:06:23 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23209; Fri, 24 Sep 93 15:06:18 -0700 Date: Fri, 24 Sep 1993 15:05:14 -0700 (PDT) From: David L Miller Subject: Re: RS/6000 installation To: Ralph Sims Cc: pine-info@cac.washington.edu In-Reply-To: <199309242147.AA28751@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII What kind of symptoms are you getting? |\ | |\/| 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, 24 Sep 1993, Ralph Sims wrote: > > I built pine 3.85 on an RS/6000 730 without any difficulty. However, > > executing it results in the following message & termination::: > > It didn't build on ULTRIX 4.1. Pico did, but pine didn't. Anyone have > help for this architecture? From owner-pine-info@cac.washington.edu Fri Sep 24 16:34:50 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16923; Fri, 24 Sep 93 16:34:50 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00198; Fri, 24 Sep 93 16:24:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bgumail.bgu.ac.il by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00192; Fri, 24 Sep 93 16:24:23 -0700 Received: by bgumail.bgu.ac.il (5.65/DEC-Ultrix/4.3) id AA02081; Sat, 25 Sep 1993 01:19:25 +0200 Date: Sat, 25 Sep 1993 01:15:52 +0200 (IST) From: Eran Lachs Subject: ULTRIX installation [Re: RS/6000 installation] To: Ralph Sims Cc: pine-info@cac.washington.edu In-Reply-To: <199309242147.AA28751@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Ralph Sims wrote: > It didn't build on ULTRIX 4.1. Pico did, but pine didn't. Anyone have > help for this architecture? I just now built Pine 3.85 under Ultrix 4.1.3 - './build ult' is all it took. Bravo Pine team ! Eran Lachs email: eran@bgumail.bgu.ac.il System Group phone: +972 57 461745 Ben Gurion University Computation Center fax: +972 57 236090 Beer Sheva, Israel From owner-pine-info@cac.washington.edu Fri Sep 24 16:52:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17740; Fri, 24 Sep 93 16:52:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04069; Fri, 24 Sep 93 16:38:49 -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 AA04063; Fri, 24 Sep 93 16:38:47 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25075; Fri, 24 Sep 93 16:38:27 -0700 Date: Fri, 24 Sep 1993 16:37:31 -0700 (PDT) From: Steve Hubert Subject: Re: ULTRIX installation 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 Hmm. Works for me, too. I just tried it on a system that claims to be ULTRIX V4.1 (Rev. 52) System #3: Fri Oct 4 21:55:10 PDT 1991 UWS V4.1 (Rev. 197) Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Sat, 25 Sep 1993, Eran Lachs wrote: > On Fri, 24 Sep 1993, Ralph Sims wrote: > > > It didn't build on ULTRIX 4.1. Pico did, but pine didn't. Anyone have > > help for this architecture? > > I just now built Pine 3.85 under Ultrix 4.1.3 - './build ult' is all it took. > Bravo Pine team ! > > Eran Lachs email: eran@bgumail.bgu.ac.il > System Group phone: +972 57 461745 > Ben Gurion University Computation Center fax: +972 57 236090 > Beer Sheva, Israel From owner-pine-info@cac.washington.edu Fri Sep 24 17:06:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18807; Fri, 24 Sep 93 17:06:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04558; Fri, 24 Sep 93 16:59:09 -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 AA04552; Fri, 24 Sep 93 16:59:08 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25442; Fri, 24 Sep 93 16:59:04 -0700 Date: Fri, 24 Sep 1993 16:43:00 -0700 (PDT) From: Steve Hubert Subject: Re: RS/6000 installation To: "Tom C. May" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Don't really know, but it means that this simple function is returning NULL. char * get_system_login() { if(unix_pwd == NULL) { if(!pwd_looked_up) { unix_pwd = getpwuid(getuid()); pwd_looked_up = 1; } if(unix_pwd == NULL) return((char *)NULL); } return(unix_pwd->pw_name); } which looks like it means that getpwuid(getuid()) is returning NULL. I don't remember seeing this problem before. Here's a little test program to test the hypothesis that this is where it is failing. #include #include #include main() { struct passwd *pw; uid_t uid; uid = getuid(); printf("uid = %lu\n", uid); pw = getpwuid(uid); if(!pw) { printf("getpwuid(%lu) returned NULL\n", uid); }else { if(!pw->pw_name) printf("pw->pw_name is NULL\n"); else printf("You are %s\n", pw->pw_name); } } Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Fri, 24 Sep 1993, Tom C. May wrote: > I built pine 3.85 on an RS/6000 730 without any difficulty. However, > executing it results in the following message & termination::: > > Who are you? (Unable to look up login name) > > Any idea what isn't configured correctly??? > > Thanks, > -tm > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Tom C. May _________ tcmay@cs.uoregon.edu _ _ > Computer & Info Science | Office : (503) 346-0892 | \ / | > University of Oregon | Fax : (503) 346-5373 | \/ | > Eugene, OR 97403-1202 ........|...................................| |.. > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Fri Sep 24 17:26:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19406; Fri, 24 Sep 93 17:26:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04890; Fri, 24 Sep 93 17:10:41 -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 AA04884; Fri, 24 Sep 93 17:10:35 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28250; Fri, 24 Sep 93 17:10:33 -0700 Date: Fri, 24 Sep 1993 17:08:32 -0700 (PDT) From: David L Miller Subject: Re: ULTRIX installation To: Steve Hubert Cc: Ralph Sims , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I also tried the pre-compiled pine-bin.ultrix and it works fine on the same system... If you can give us some details of exactly what did and did not work, we will see if we can help. |\ | |\/| 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, 24 Sep 1993, Steve Hubert wrote: > Hmm. Works for me, too. I just tried it on a system that claims to be > > ULTRIX V4.1 (Rev. 52) System #3: Fri Oct 4 21:55:10 PDT 1991 > UWS V4.1 (Rev. 197) > > Steve Hubert > Networks and Distributed Computing, Univ. of Washington, Seattle > > > On Sat, 25 Sep 1993, Eran Lachs wrote: > > > On Fri, 24 Sep 1993, Ralph Sims wrote: > > > > > It didn't build on ULTRIX 4.1. Pico did, but pine didn't. Anyone have > > > help for this architecture? > > > > I just now built Pine 3.85 under Ultrix 4.1.3 - './build ult' is all it took. > > Bravo Pine team ! > > > > Eran Lachs email: eran@bgumail.bgu.ac.il > > System Group phone: +972 57 461745 > > Ben Gurion University Computation Center fax: +972 57 236090 > > Beer Sheva, Israel > From owner-pine-info@cac.washington.edu Fri Sep 24 17:51:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20372; Fri, 24 Sep 93 17:51:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04941; Fri, 24 Sep 93 17:14:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from medusa.unm.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04935; Fri, 24 Sep 93 17:13:59 -0700 Received: from [-127.24.128.129] (mccsmgr.unm.edu) by MEDUSA.UNM.EDU (PMDF V4.2-14 #5028) id <01H3C3QN28BK00049U@MEDUSA.UNM.EDU>; Fri, 24 Sep 1993 18:14:06 MDT Date: Fri, 24 Sep 1993 18:09:03 -0700 (PDT) From: "Stephen F. Day UNM MCCS" Subject: new incoming mail & PC-Pine To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Sender: sday@medusa.unm.edu Okay... Have another question regarding PC-Pine. I've noted that PC-Pine correctly picks up all new mail messages when I first fire up PC-Pine. However, all new messages after that point are not picked up by PC-Pine and I have to exit PC-Pine and re-enter PC-Pine to see these newer messages. Surely there's an easier way to do this, isn't there? Thanks! Stephen From owner-pine-info@cac.washington.edu Fri Sep 24 18:42:26 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21179; Fri, 24 Sep 93 18:42:26 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00774; Fri, 24 Sep 93 18:31:38 -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 AA00768; Fri, 24 Sep 93 18:31:36 -0700 Received: from nyx.cs.du.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA02295; Fri, 24 Sep 93 21:31:32 -0400 Received: by nyx.cs.du.edu (4.1/SMI-4.1) id AA19501; Fri, 24 Sep 93 19:32:22 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: Fri, 24 Sep 1993 19:28:12 -0600 (MDT) From: Jeffrey Wolff Subject: Debug Mode To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Would command should I execute to build Pine (Sun version) so that it does not creat the .pine-debug? files in my home directory? I was successfully able to build it last night but realized when I ran the binary that it still created those annoying files. Last night, I issued the very simple "build sun" and sat back to watch. My compliments to the design team for ease of use. -- Jeffrey M. Wolff jwolff@nyx.cs.du.edu George Mason University From owner-pine-info@cac.washington.edu Fri Sep 24 21:54:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23147; Fri, 24 Sep 93 21:54:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01314; Fri, 24 Sep 93 21:15:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from kenya.isu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01308; Fri, 24 Sep 93 21:15:39 -0700 Message-Id: <9309250415.AA01308@mx2.cac.washington.edu> Received: by kenya.isu.edu with SMTP (1.37.109.4/16.2) id AA15250; Fri, 24 Sep 93 22:14:30 -0600 To: pine-info@cac.washington.edu Subject: Problems with HP terminals... Date: Fri, 24 Sep 1993 22:14:30 -0600 From: Daniel Simmons I just grabbed 3.85 and compiled it on my HP 9000/710 running HP-UX 9.01. Everything seems to work spiffy. Well, everything that's ever worked, that is. I have for some time, experienced a problem using pine and pico with HP terminals. That is, they have a propensity for turning on reverse video and then not turning it off. For instance, when composing a new message, each header component is highlighted (reverse video) when the user is supposed to enter that part (to, subject, etc.). On HP terminals, though, when you press enter to go to the next part it gets highlighted but the previous part stays highlighted as well. This is particularly annoying when doing something like selecting a folder--the highlight doesn't move, it just covers everything. With the new pico and the ability to mark a region of text the same problem occurs if you set the mark, move down over some text, and then move back up--"unmarking" some of it--it all stays marked. Of course, you can always hit ctrl-l and redraw the screen correctly, but it is still frustrating. I've looked at the code a little bit, but the problem is non-obvious on first perusal. I'm willing to go at it, but I thought I might ask for some overall pointers first. (For instance, when highlighting is turned off, does that section of text get redrawn or do you attempt to just tell the terminal to turn it off or something?) As a token of my good faith, here's my version of the patch that enables the keypad on hp terminals. The old contrib patch didn't apply right to the new pico/tcap.c, and it didn't cover pine/ttyout.c at all. So, here's a small patch that seems to work for both of those files with ver. 3.85. Danny ---------- cut here ----------- *** pico/tcap.c.cln Mon Sep 20 14:52:00 1993 --- pico/tcap.c Fri Sep 24 21:32:59 1993 *************** *** 98,103 **** --- 98,104 ---- char *KU, *KD, *KL, *KR; char *KPPU, *KPPD, *KPHOME, *KPEND; + char *KS, *KE; /* start and end keypad mode (HP terminals) */ struct KBSTREE *kpadseqs = NULL; *************** *** 180,185 **** --- 181,188 ---- SR = tgetstr("sr", &p); TI = tgetstr("ti", &p); TE = tgetstr("te", &p); + KS = tgetstr("ks", &p); + KE = tgetstr("ke", &p); eolexist = (CE != NULL); /* will we be able to use clear to EOL? */ revexist = (SO != NULL); *************** *** 316,326 **** --- 319,335 ---- if (CS != NULL) putpad(tgoto(CS, term.t_nrow, 0)) ; } + + if(KS) /* enter keypad transmit mode */ + putpad(KS); } tcapclose() { + if(KS && KE) /* get out of keypad transmit mode */ + putpad(KE); + if(!Pmaster){ if(gmode&MDFKEY) puts("\033[99l"); /* reset UW-NCSA telnet keys */ *** pine/ttyout.c.cln Fri Sep 24 21:47:37 1993 --- pine/ttyout.c Fri Sep 24 21:50:45 1993 *************** *** 130,136 **** *_startinsert, *_endinsert, *_insertchar, *_deletechar, *_deleteline, *_insertline, *_scrollregion, *_scrollup, *_scrolldown, ! *_termcap_init, *_termcap_end; static int _lines, _columns; char termname[40]; #ifndef USE_TERMINFO --- 130,137 ---- *_startinsert, *_endinsert, *_insertchar, *_deletechar, *_deleteline, *_insertline, *_scrollregion, *_scrollup, *_scrolldown, ! *_termcap_init, *_termcap_end, ! *_keypad_start, *_keypad_end; static int _lines, _columns; char termname[40]; #ifndef USE_TERMINFO *************** *** 270,275 **** --- 271,278 ---- _scrollup = tgetstr("sr", &ptr); _termcap_init = tgetstr("ti", &ptr); _termcap_end = tgetstr("te", &ptr); + _keypad_start = tgetstr("ks", &ptr); + _keypad_end = tgetstr("ke", &ptr); _lines = tgetnum("li"); _columns = tgetnum("co"); tabspacing = ((tabspacing=tgetnum("it"))==-1 ? 8: tabspacing); *************** *** 341,348 **** { if(_termcap_init != NULL) { tputs(_termcap_init, 1, outchar); - fflush(stdout); } } --- 344,354 ---- { if(_termcap_init != NULL) { tputs(_termcap_init, 1, outchar); } + if(_keypad_start != NULL) { + tputs(_keypad_start, 1, outchar); + } + fflush(stdout); } *************** *** 408,413 **** --- 414,421 ---- EndInverse(); MoveCursor( _lines - 1, 0); NewLine(); + if(_keypad_end != NULL) + tputs(_keypad_end, 1, outchar); if(_termcap_end != NULL) tputs(_termcap_end, 1, outchar); fflush(stdout); ---------- cut here ------------- -------- Daniel Simmons electronic mail : simmdan@isu.edu Idaho State University voice mail : (208) 236-3199 Computer Center snail mail : Box 8037, Pocatello From owner-pine-info@cac.washington.edu Fri Sep 24 22:11:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23378; Fri, 24 Sep 93 22:11:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06629; Fri, 24 Sep 93 22:01:21 -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 AA06623; Fri, 24 Sep 93 22:01:19 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA19824; Sat, 25 Sep 1993 00:04:53 -0500 Date: Sat, 25 Sep 1993 00:01:52 -0500 (CDT) From: "Robert A. Hayden" Subject: News To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm somewhat confused about what exactly Pine 3.85 can do with news. I know the news implementation is somewhat limited at this point, what I'm really interested in if I can post to new. The reason is that I'd like to at the same time I send out some FAQs to different mailing lists, I'd like to be able to post them without having to go off and invoke my reader and post a second time. Am I missing something? (very probably). {[> 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 Fri Sep 24 22:26:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23545; Fri, 24 Sep 93 22:26:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06732; Fri, 24 Sep 93 22:18:27 -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 AA06726; Fri, 24 Sep 93 22:18:25 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29368; Fri, 24 Sep 93 22:18:22 -0700 Date: Fri, 24 Sep 1993 22:18:06 -0700 (PDT) From: Steve Hubert Subject: Re: News To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sorry, you're not missing anything. There is no ability to post from pine yet. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Fri Sep 24 22:28:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23590; Fri, 24 Sep 93 22:28:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06724; Fri, 24 Sep 93 22:18:10 -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 AA06718; Fri, 24 Sep 93 22:18:08 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28942; Fri, 24 Sep 93 22:18:05 -0700 Date: Fri, 24 Sep 1993 22:13:15 -0700 (PDT) From: Terry Gray Subject: Re: News To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Unfortunately, News posting didn't make it into 3.85, but it is definitely coming. What you can do with news in 3.85 is, given a pre-existing newsrc, read news groups in the same way that you would read mail folders. Enhancements to make this easier, as well as posting/subscribing/unsubscribing, are high priorities for us. (You may have noticed that we have a lot of "high priorities for us"... which is why I'm not predicting a release date.) -teg On Sat, 25 Sep 1993, Robert A. Hayden wrote: > > I'm somewhat confused about what exactly Pine 3.85 can do with news. I > know the news implementation is somewhat limited at this point, what I'm > really interested in if I can post to new. The reason is that I'd like > to at the same time I send out some FAQs to different mailing lists, I'd > like to be able to post them without having to go off and invoke my > reader and post a second time. > > Am I missing something? (very probably). > > {[> 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 Fri Sep 24 22:35:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23736; Fri, 24 Sep 93 22:35:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06768; Fri, 24 Sep 93 22:26:21 -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 AA06762; Fri, 24 Sep 93 22:26:20 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29468; Fri, 24 Sep 93 22:26:15 -0700 Date: Fri, 24 Sep 1993 22:20:47 -0700 (PDT) From: Steve Hubert Subject: Re: Debug Mode To: Jeffrey Wolff Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Jeffrey Wolff wrote: > Would command should I execute to build Pine (Sun version) so that it does not > creat the .pine-debug? files in my home directory? If you run pine with the argument -d0 it will not make the .pine-debugX files. So you could just create an alias or script called pine that does that. Alternatively, you can rebuild the source. You need to remove the declaration of the DEBUG macro from the makefile in the pine directory. So look for the appropriate makefile in the pine subdirectory (makefile.sun, I guess, and delete the -DDEBUG from it. Then do make -f makefile.sun clean make -f makefile.sun in the pine directory to rebuild it. > I was successfully able to build it last night but realized when I ran the > binary that it still created those annoying files. > > Last night, I issued the very simple "build sun" and sat back to watch. My > compliments to the design team for ease of use. The design team wasn't able to be here tonight, but I accept your compliments on their behalf. Thanks! > -- > Jeffrey M. Wolff > jwolff@nyx.cs.du.edu > George Mason University Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Fri Sep 24 22:35:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23777; Fri, 24 Sep 93 22:35:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06776; Fri, 24 Sep 93 22:27:16 -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 AA06770; Fri, 24 Sep 93 22:27:14 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02181; Fri, 24 Sep 93 22:27:11 -0700 Date: Fri, 24 Sep 1993 22:25:58 -0700 (PDT) From: David L Miller Subject: Re: Debug Mode To: Jeffrey Wolff Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Edit pine/makefile and remove the "-DDEBUG" flag. This will remove all debug code from Pine. |\ | |\/| 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, 24 Sep 1993, Jeffrey Wolff wrote: > > Would command should I execute to build Pine (Sun version) so that it does not > creat the .pine-debug? files in my home directory? > > I was successfully able to build it last night but realized when I ran the > binary that it still created those annoying files. > > Last night, I issued the very simple "build sun" and sat back to watch. My > compliments to the design team for ease of use. > > -- > Jeffrey M. Wolff > jwolff@nyx.cs.du.edu > George Mason University > > From owner-pine-info@cac.washington.edu Fri Sep 24 22:54:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23980; Fri, 24 Sep 93 22:54:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06882; Fri, 24 Sep 93 22:44:01 -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 AA06876; Fri, 24 Sep 93 22:43:59 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02371; Fri, 24 Sep 93 22:43:55 -0700 Date: Fri, 24 Sep 1993 22:31:24 -0700 (PDT) From: David L Miller Subject: Re: Problems with HP terminals... To: Daniel Simmons Cc: pine-info@cac.washington.edu In-Reply-To: <9309250415.AA01308@mx2.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks for the new patch! I'll make sure it gets into the next maintenance release. We have seen similar highlighting problems on other systems. It is kinda hard for us to deal with HP terminal problems as we do not have any (that I know of :) around here :( On Linux systems we found that not all terminal drivers did "the right thing" wrt highlighting.... If you have the time and motivation to help us with HP terminal handling, I would be happy to include your patches and/or help in any way I can. |\ | |\/| 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, 24 Sep 1993, Daniel Simmons wrote: > I just grabbed 3.85 and compiled it on my HP 9000/710 running HP-UX 9.01. > Everything seems to work spiffy. > > Well, everything that's ever worked, that is. I have for some time, > experienced a problem using pine and pico with HP terminals. That is, they > have a propensity for turning on reverse video and then not turning it off. > For instance, when composing a new message, each header component is > highlighted (reverse video) when the user is supposed to enter that part > (to, subject, etc.). On HP terminals, though, when you press enter to go > to the next part it gets highlighted but the previous part stays > highlighted as well. This is particularly annoying when doing something > like selecting a folder--the highlight doesn't move, it just covers > everything. With the new pico and the ability to mark a region of text the > same problem occurs if you set the mark, move down over some text, and then > move back up--"unmarking" some of it--it all stays marked. Of course, you > can always hit ctrl-l and redraw the screen correctly, but it is still > frustrating. > > I've looked at the code a little bit, but the problem is non-obvious on > first perusal. I'm willing to go at it, but I thought I might ask for > some overall pointers first. (For instance, when highlighting is turned > off, does that section of text get redrawn or do you attempt to just tell > the terminal to turn it off or something?) > > As a token of my good faith, here's my version of the patch that enables > the keypad on hp terminals. The old contrib patch didn't apply right to > the new pico/tcap.c, and it didn't cover pine/ttyout.c at all. So, here's > a small patch that seems to work for both of those files with ver. 3.85. > > Danny > > ---------- cut here ----------- > > *** pico/tcap.c.cln Mon Sep 20 14:52:00 1993 > --- pico/tcap.c Fri Sep 24 21:32:59 1993 > *************** > *** 98,103 **** > --- 98,104 ---- > > char *KU, *KD, *KL, *KR; > char *KPPU, *KPPD, *KPHOME, *KPEND; > + char *KS, *KE; /* start and end keypad mode (HP terminals) */ > > struct KBSTREE *kpadseqs = NULL; > > *************** > *** 180,185 **** > --- 181,188 ---- > SR = tgetstr("sr", &p); > TI = tgetstr("ti", &p); > TE = tgetstr("te", &p); > + KS = tgetstr("ks", &p); > + KE = tgetstr("ke", &p); > > eolexist = (CE != NULL); /* will we be able to use clear to EOL? */ > revexist = (SO != NULL); > *************** > *** 316,326 **** > --- 319,335 ---- > if (CS != NULL) > putpad(tgoto(CS, term.t_nrow, 0)) ; > } > + > + if(KS) /* enter keypad transmit mode */ > + putpad(KS); > } > > > tcapclose() > { > + if(KS && KE) /* get out of keypad transmit mode */ > + putpad(KE); > + > if(!Pmaster){ > if(gmode&MDFKEY) > puts("\033[99l"); /* reset UW-NCSA telnet keys */ > *** pine/ttyout.c.cln Fri Sep 24 21:47:37 1993 > --- pine/ttyout.c Fri Sep 24 21:50:45 1993 > *************** > *** 130,136 **** > *_startinsert, *_endinsert, *_insertchar, *_deletechar, > *_deleteline, *_insertline, > *_scrollregion, *_scrollup, *_scrolldown, > ! *_termcap_init, *_termcap_end; > static int _lines, _columns; > char termname[40]; > #ifndef USE_TERMINFO > --- 130,137 ---- > *_startinsert, *_endinsert, *_insertchar, *_deletechar, > *_deleteline, *_insertline, > *_scrollregion, *_scrollup, *_scrolldown, > ! *_termcap_init, *_termcap_end, > ! *_keypad_start, *_keypad_end; > static int _lines, _columns; > char termname[40]; > #ifndef USE_TERMINFO > *************** > *** 270,275 **** > --- 271,278 ---- > _scrollup = tgetstr("sr", &ptr); > _termcap_init = tgetstr("ti", &ptr); > _termcap_end = tgetstr("te", &ptr); > + _keypad_start = tgetstr("ks", &ptr); > + _keypad_end = tgetstr("ke", &ptr); > _lines = tgetnum("li"); > _columns = tgetnum("co"); > tabspacing = ((tabspacing=tgetnum("it"))==-1 ? 8: tabspacing); > *************** > *** 341,348 **** > { > if(_termcap_init != NULL) { > tputs(_termcap_init, 1, outchar); > - fflush(stdout); > } > } > > > --- 344,354 ---- > { > if(_termcap_init != NULL) { > tputs(_termcap_init, 1, outchar); > } > + if(_keypad_start != NULL) { > + tputs(_keypad_start, 1, outchar); > + } > + fflush(stdout); > } > > > *************** > *** 408,413 **** > --- 414,421 ---- > EndInverse(); > MoveCursor( _lines - 1, 0); > NewLine(); > + if(_keypad_end != NULL) > + tputs(_keypad_end, 1, outchar); > if(_termcap_end != NULL) > tputs(_termcap_end, 1, outchar); > fflush(stdout); > > ---------- cut here ------------- > > -------- > Daniel Simmons electronic mail : simmdan@isu.edu > Idaho State University voice mail : (208) 236-3199 > Computer Center snail mail : Box 8037, Pocatello > > From owner-pine-info@cac.washington.edu Fri Sep 24 22:59:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24074; Fri, 24 Sep 93 22:59:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06899; Fri, 24 Sep 93 22:50: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 AA06893; Fri, 24 Sep 93 22:50:51 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02433; Fri, 24 Sep 93 22:50:50 -0700 Date: Fri, 24 Sep 1993 22:48:14 -0700 (PDT) From: David L Miller Subject: Re: Debug Mode To: Steve Hubert Cc: Jeffrey Wolff , Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ahhh, I missed that fix ;) Older versions of Pine would create an empty .pine-debug with -d0. Either -d0 or removing -DDEBUG will work, depending on how 'permanent' you want the change to be... |\ | |\/| 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, 24 Sep 1993, Steve Hubert wrote: > On Fri, 24 Sep 1993, Jeffrey Wolff wrote: > > > Would command should I execute to build Pine (Sun version) so that it does not > > creat the .pine-debug? files in my home directory? > > If you run pine with the argument -d0 it will not make the .pine-debugX > files. So you could just create an alias or script called pine that does > that. Alternatively, you can rebuild the source. You need to remove the > declaration of the DEBUG macro from the makefile in the pine directory. > So look for the appropriate makefile in the pine subdirectory > (makefile.sun, I guess, and delete the -DDEBUG from it. Then do > > make -f makefile.sun clean > make -f makefile.sun > > in the pine directory to rebuild it. > > > I was successfully able to build it last night but realized when I ran the > > binary that it still created those annoying files. > > > > Last night, I issued the very simple "build sun" and sat back to watch. My > > compliments to the design team for ease of use. > > The design team wasn't able to be here tonight, but I accept your compliments > on their behalf. Thanks! > > > -- > > Jeffrey M. Wolff > > jwolff@nyx.cs.du.edu > > George Mason University > > Steve Hubert > Networks and Distributed Computing, Univ. of Washington, Seattle > From owner-pine-info@cac.washington.edu Sat Sep 25 04:28:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29121; Sat, 25 Sep 93 04:28:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08747; Sat, 25 Sep 93 04:19:43 -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 AA08741; Sat, 25 Sep 93 04:19:41 -0700 Received: from vortex.yorku.ca ([130.63.232.15]) by nexus.yorku.ca with SMTP id <9223>; Sat, 25 Sep 1993 07:19:38 -0400 Received: by vortex.yorku.ca (4.1/SMI-4.1) id AA13697; Sat, 25 Sep 93 07:24:21 EDT Date: Sat, 25 Sep 1993 07:18:30 -0400 From: Ian Lumb Reply-To: Ian Lumb Subject: Thanks!! To: PINE INFO Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Greetings:- I would like to express my thanks to the Pine Team for incorporating many substantial improvements and new features into version 3.85. Personally, I really like the `incoming-folders' and `folder-collections' enhancements - I was already performing functions related to the latter of these manually! With the ability to now provide one's own name for one's Pine addressbook, it's also good to know that global addressbooks are just a release (or three :-) away. Saving mail from one's inbox by some user-specifiable default strategy is also terrific. Would it be possible to do the same for outgoing mail? For example, would it be possible to develop a .pinerc option something like Fcc-name-rule=by-recipient instead of the current sent-mail One other question: Is is possible to make the rich header option the default option when one is composing a message? In passing, I have successfully built and use Pine version 3.85 on two Suns, SPARC 1+ (SunOS 4.1) SPARC 10/30 (SunOS 4.1.3) where it is enjoyed by our user community :-) 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 Sat Sep 25 06:12:43 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00311; Sat, 25 Sep 93 06:12:43 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03069; Sat, 25 Sep 93 06:00:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sun4nl.nluug.nl by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03062; Sat, 25 Sep 93 06:00:15 -0700 Received: from nlbull by sun4nl.nluug.nl via EUnet id AA23097 (5.65b/CWI-3.3); Sat, 25 Sep 1993 15:00:13 +0200 Received: from localhost by wilg.bull.nl with SMTP (BULL 5.61++/Bull-NL-1.0.24-1.6) id AA01854; Sat, 25 Sep 93 12:54:50 GMT (MET) Message-Id: <9309251254.AA01854@wilg.bull.nl> To: pine-info@cac.washington.edu Subject: Portability of Pine (3.85) Date: Sat, 25 Sep 93 14:54:48 EET From: Jos Vos Hello, I'm using a Bull DPX/2 system, running a SVR3.1-based UNIX, including sockets, TCP/IP, etc. After getting Pine 3.85, I tried to get it running on my system. But that's a lot of work... Copying the OS-dependent files, and then the trial-and-error when building Pine. My suggestion is: wouldn't it be better to add proper #ifdef's for all the system-dependencies in *.[ch] files? A Configure script also would be nice, of course ... I've ported *a lot* of software packages to a lot of UNIX systems, including the DPX/2 I'm using for Pine now, but I never had to spent so much time on porting a package ... Nevertheless, I'll continue, because I think Pine will be a good alternative for people using UNIX e-mail without being UNIX-users themselves. -- -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Sat Sep 25 10:09:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02755; Sat, 25 Sep 93 10:09:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10239; Sat, 25 Sep 93 09:50: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 AA10233; Sat, 25 Sep 93 09:50:52 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06749; Sat, 25 Sep 93 09:50:49 -0700 Date: Sat, 25 Sep 1993 09:41:16 -0700 (PDT) From: David L Miller Subject: Re: Thanks!! To: Ian Lumb Cc: PINE INFO In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII |\ | |\/| 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, 25 Sep 1993, Ian Lumb wrote: > Greetings:- > > I would like to express my thanks to the Pine Team for incorporating many > substantial improvements and new features into version 3.85. Personally, I > really like the `incoming-folders' and `folder-collections' enhancements - > I was already performing functions related to the latter of these > manually! > We blush in appreciation of your praise :-) > With the ability to now provide one's own name for one's Pine > addressbook, it's also good to know that global addressbooks are just a > release (or three :-) away. > We will be trying to make more frequent releases in the future. We got hung up entirely too long getting PC-pine out the door :-( Rumor has it "The Boss" has a release schedule planned for the next year (or five :-) but we will avoid giving out "expected" release dates for a while... > Saving mail from one's inbox by some user-specifiable default strategy is > also terrific. Would it be possible to do the same for outgoing mail? For > example, would it be possible to develop a .pinerc option something like > > Fcc-name-rule=by-recipient > > instead of the current > > sent-mail > > One other question: Is is possible to make the rich header option the > default option when one is composing a message? > Hmmm... I can see some merit in having these options... We will keep them in mind... > In passing, I have successfully built and use Pine version 3.85 on two > Suns, > > SPARC 1+ (SunOS 4.1) > > SPARC 10/30 (SunOS 4.1.3) > > where it is enjoyed by our user community :-) > Great! > 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 Sat Sep 25 10:10:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02807; Sat, 25 Sep 93 10:10:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10308; Sat, 25 Sep 93 10:01:45 -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 AA10302; Sat, 25 Sep 93 10:01:43 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06907; Sat, 25 Sep 93 10:01:39 -0700 Date: Sat, 25 Sep 1993 09:52:20 -0700 (PDT) From: David L Miller Subject: Re: Portability of Pine (3.85) To: Jos Vos Cc: pine-info@cac.washington.edu In-Reply-To: <9309251254.AA01854@wilg.bull.nl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We feel that the inconvenience of the initial port to a new platform is by far outweighed by the ease of maintenance once it is done. If you have the dependencies scattered throughout the code, it can become a major nightmare to keep track of what code is doing what very quickly. I've done *maintenance* on alot of packages and I can tell you tat it is very nice to not have to worry about OS-dependencies when I am trying to concentrate on functionality! |\ | |\/| 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, 25 Sep 1993, Jos Vos wrote: > Hello, > > I'm using a Bull DPX/2 system, running a SVR3.1-based UNIX, including > sockets, TCP/IP, etc. > > After getting Pine 3.85, I tried to get it running on my system. > But that's a lot of work... Copying the OS-dependent files, > and then the trial-and-error when building Pine. > > My suggestion is: wouldn't it be better to add proper #ifdef's for > all the system-dependencies in *.[ch] files? A Configure script also > would be nice, of course ... > > I've ported *a lot* of software packages to a lot of UNIX systems, > including the DPX/2 I'm using for Pine now, but I never had to spent > so much time on porting a package ... > > Nevertheless, I'll continue, because I think Pine will be a good > alternative for people using UNIX e-mail without being UNIX-users > themselves. > > -- > -- Jos Vos (UUCP: ...!{uunet,mcsun,sun4nl}!nlbull!jos) > -- Bull Netherlands, Professional Services, Amsterdam, The Netherlands From owner-pine-info@cac.washington.edu Sat Sep 25 13:58:11 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05525; Sat, 25 Sep 93 13:58:11 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11486; Sat, 25 Sep 93 13:49:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from gray.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11480; Sat, 25 Sep 93 13:49:39 -0700 Received: from phx.cam.ac.uk by ppsw1.cam.ac.uk with GB-CAM (PP-6.0) as ppsw.cam.ac.uk id <22084-0@ppsw1.cam.ac.uk>; Sat, 25 Sep 1993 21:49:34 +0100 Date: Sat, 25 Sep 93 21:49:19 BST From: Barry.Landy@UCS.CAM.AC.UK To: pine-info@cac.washington.edu Subject: DNS resolving problem Message-Id: We are trying to use the LWP version of pine 385, and find that there is a problem resolving our DNS addresses. PC-Pine doesn't appear to handle DNS names which only have CNAME records. We use CNAMEs to keep the actual location of the IMAP and SMTP services out of PINERC etc (so that they are aliases of the machines which supply the service, so we can switch thing around of a machine drops, or for maintenance. Names which have DNS A-records work fine so I don't think it's a setup problem. Also, the packet driver version copes with this correctly, so it is specific to the LWP support. An urgent fix would be appreciated, as we would like to use the LWP version for our student service. From owner-pine-info@cac.washington.edu Sat Sep 25 14:20:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05756; Sat, 25 Sep 93 14:20:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11601; Sat, 25 Sep 93 14:12:57 -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 AA11595; Sat, 25 Sep 93 14:12:56 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01327; Sat, 25 Sep 93 14:12:51 -0700 Date: Sat, 25 Sep 1993 14:08:21 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: DNS resolving problem To: Barry.Landy@UCS.CAM.AC.UK Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sat, 25 Sep 1993 Barry.Landy@UCS.CAM.AC.UK wrote: > We are trying to use the LWP version of pine 385, and find that there is a > problem resolving our DNS addresses. > PC-Pine doesn't appear to handle DNS names which only have CNAME records. > We use CNAMEs to keep the actual location of the IMAP and SMTP services out > of PINERC etc (so that they are aliases of the machines which supply the > service, so we can switch thing around of a machine drops, or for maintenance. > Names which have DNS A-records work fine so I don't think it's a setup > problem. Barry, As you probably know, Alasdair Grant reported this to us yesterday. We had been assuming that it was an LWP bug, but maybe not... For the benefit of any LWP experts on the list who might be able to help, MikeS sez : The library call now doing the work is "rhost()" from the 4.0 toolkit. Suggestions, anyone? -teg From owner-pine-info@cac.washington.edu Sat Sep 25 14:42:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06005; Sat, 25 Sep 93 14:42:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04590; Sat, 25 Sep 93 14:33:20 -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 AA04584; Sat, 25 Sep 93 14:33:19 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA01116 sendmail 5.67/UCSD-2.2-sun via SMTP Sat, 25 Sep 93 14:33:10 -0700 for pine-info@cac.washington.edu Received: from weber.ucsd.edu (localhost [127.0.0.1]) by weber.ucsd.edu (8.6.beta.12/UCSDGENERIC.4c) with ESMTP id OAA03752; Sat, 25 Sep 1993 14:33:09 -0700 Message-Id: <199309252133.OAA03752@weber.ucsd.edu> To: Barry.Landy@UCS.CAM.AC.UK Cc: pine-info@cac.washington.edu Subject: Re: DNS resolving problem In-Reply-To: Your message of "Sat, 25 Sep 1993 21:49:19 -0000." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 25 Sep 1993 14:33:08 -0700 From: "Michael J. Corrigan" I don't know if this is related but domain addresses corresponding to CNAME records are supposed to be canonicalized to hosts with A or MX records: >From RFC-1123: 5.2.2 Canonicalization: RFC-821 Section 3.1 The domain names that a Sender-SMTP sends in MAIL and RCPT commands MUST have been "canonicalized," i.e., they must be fully-qualified principal names or domain literals, not nicknames or domain abbreviations. A canonicalized name either identifies a host directly or is an MX name; it cannot be a CNAME. ---------------------------------------------------------------------------- We are trying to use the LWP version of pine 385, and find that there is a problem resolving our DNS addresses. PC-Pine doesn't appear to handle DNS names which only have CNAME records. We use CNAMEs to keep the actual location of the IMAP and SMTP services ou t of PINERC etc (so that they are aliases of the machines which supply the service, so we can switch thing around of a machine drops, or for maintena nce. Names which have DNS A-records work fine so I don't think it's a setup pro blem. Also, the packet driver version copes with this correctly, so it is specif ic to the LWP support. An urgent fix would be appreciated, as we would like to use the LWP versio n for our student service. From owner-pine-info@cac.washington.edu Sun Sep 26 00:15:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12231; Sun, 26 Sep 93 00:15:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14144; Sun, 26 Sep 93 00:05:48 -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 AA14138; Sun, 26 Sep 93 00:05:45 -0700 Received: by halcyon.com id AA27586 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sun, 26 Sep 1993 00:05:43 -0700 From: Ralph Sims Message-Id: <199309260705.AA27586@halcyon.com> Subject: Re: ULTRIX installation To: dlm@cac.washington.edu (David L Miller) Date: Sun, 26 Sep 1993 00:05:40 -0700 (PDT) Cc: pine-info@cac.washington.edu In-Reply-To: from "David L Miller" at Sep 24, 93 05:08:32 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: 642 > If you can give us some details of exactly what did and did not work, we > will see if we can help. Well, it appears the problems were in the compiler options. I reduced the options to -O -d=const (memory may have lapsed on that last one) and it compiled. I dropped the -g3 -Olimit 800 flags, and used gcc 2.45 to compile it. Aside from a couple of warnings it worked fine. I normally have at least one initial problem compiling pine over the past 18 months, but things work out well in the end. The original build, using ULTRIX 4.1's traditional cc compiler just died without much complaining. In any event, we're up and running. From owner-pine-info@cac.washington.edu Sun Sep 26 00:18:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12270; Sun, 26 Sep 93 00:18:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14170; Sun, 26 Sep 93 00:10:23 -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 AA14164; Sun, 26 Sep 93 00:10:21 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02693; Sun, 26 Sep 93 00:10:14 -0700 Date: Sat, 25 Sep 1993 23:58:49 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: Pine Demo To: Peter Scott U Sask Library Systems Dept Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 24 Sep 1993, Peter Scott U Sask Library Systems Dept wrote: > I notice that the Pine demo at telnet to demo.cac.washington.edu (login > pinedemo) is running version 3.07. Will this be upgraded soon to the > latest version? Yes, sometime this coming week. -teg From owner-pine-info@cac.washington.edu Sun Sep 26 18:52:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25732; Sun, 26 Sep 93 18:52:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09863; Sun, 26 Sep 93 18:37:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nico.aarnet.edu.au by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09857; Sun, 26 Sep 93 18:37:42 -0700 Received: from cruskit.aarnet.edu.au by nico.aarnet.edu.au with SMTP id AA21248 (5.65cAARN/IDA-1.4.4 for ); Mon, 27 Sep 1993 11:37:37 +1000 Received: from localhost by cruskit.aarnet.edu.au id for aarnet.edu.au; Mon, 27 Sep 1993 11:37:39 +1000 Date: Mon, 27 Sep 1993 11:26:19 +1000 (EST) From: Andy Linton Subject: Pine dumping core on Sun To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I posted a query last week to the mailing list about a problem with Pine dumping core when I quit. My thanks to all those who responded. The responses indicated that no one else had this problem so I've dug a little more. My working environment on the Sun is X-windows with twm as the window manager. If I fire up pine inside an xterm session and quit things are fine but I want to have pine as a menu item so in my .twmrc I have the following menu item: "pine" !"xterm -title pine -name pine -e pine -i &" When I quit from this I get the core dump. I can also repeat it if I run the command 'xterm -e pine' at the shell prompt. Using dbx I see: $ dbx /usr/local/bin/pine core Reading symbolic information... Read 31859 symbols program terminated by signal SEGV (no mapping at the fault address) (dbx) where MoveCursor(row = 47, col = 0), line 500 in "Scratch/pine3.85/pine/ttyout.c" end_screen(), line 409 in "Scratch/pine3.85/pine/ttyout.c" fast_clean_up(), line 242 in "Scratch/pine3.85/pine/signals.c" hup_signal(), line 262 in "Scratch/pine3.85/pine/signals.c" _sigtramp() at 0xf7712c4c fclose() at 0xf77136f0 _fwalk() at 0xf77135f8 _cleanup() at 0xf771368c `xs`exit() at 0xf7713308 quit_screen(pine_state = (nil)), line 1592 in "Scratch/pine3.85/pine/pine.c" main(argc = 2, argv = 0xf7fff944), line 599 in "Scratch/pine3.85/pine/pine.c" I'll ask the question again - is this just me or can other people repeat this problem? I'd guess that there's some cleaning up of the terminal going on after the xterm has gone away. -- Andy Linton A.Linton@aarnet.edu.au Network Engineer phone: +61 6 249 2874 AARNet fax: +61 6 249 1369 -- From owner-pine-info@cac.washington.edu Sun Sep 26 22:05:08 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28237; Sun, 26 Sep 93 22:05:08 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10478; Sun, 26 Sep 93 21:56: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 AA10472; Sun, 26 Sep 93 21:56:23 -0700 Received: by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA02096; Sun, 26 Sep 93 21:57:06 -0700 Date: Sun, 26 Sep 1993 21:55:56 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Pine dumping core on Sun To: Andy Linton Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Andy Linton wrote: > My working environment on the Sun is X-windows with twm as the window > manager. If I fire up pine inside an xterm session and quit things are > fine but I want to have pine as a menu item so in my .twmrc I have the > following menu item: > > "pine" !"xterm -title pine -name pine -e pine -i &" > > I'll ask the question again - is this just me or can other people repeat > this problem? > > I'd guess that there's some cleaning up of the terminal going on after > the xterm has gone away. My guess would be to write a script called xpine or something and have it sleep after pine exits (so the terminal can clean up) and then kill the term window... 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 Sun Sep 26 22:13:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28384; Sun, 26 Sep 93 22:13:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20943; Sun, 26 Sep 93 22:06:22 -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 AA20937; Sun, 26 Sep 93 22:06:19 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA14547; Mon, 27 Sep 93 00:06:00 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA05982; Mon, 27 Sep 93 13:04:09 +0800 Date: Mon, 27 Sep 1993 12:59:45 +0800 (TPE) From: Ed Greshko Subject: Re: Pine dumping core on Sun To: Andy Linton Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Andy Linton wrote: > I posted a query last week to the mailing list about a problem with Pine > dumping core when I quit. > > My thanks to all those who responded. The responses indicated that no one > else had this problem so I've dug a little more. > > My working environment on the Sun is X-windows with twm as the window > manager. If I fire up pine inside an xterm session and quit things are > fine but I want to have pine as a menu item so in my .twmrc I have the > following menu item: > > "pine" !"xterm -title pine -name pine -e pine -i &" > > When I quit from this I get the core dump. I can also repeat it if I run > the command 'xterm -e pine' at the shell prompt. > > I'll ask the question again - is this just me or can other people repeat > this problem? Ever since I got pine 3.07 (and now 3.85) I've started it up using an alias that equates to: xterm -geom 80x29+75+536 -e pine > /dev/null & (Don't remember my logic for the > /dev/null & part..." Anyway, it has never dumped core on my MIPS....and I've tried using your examples and it has not dumped core. So, I suppose it may be just your portion of the universe. :-) I'm using the Motif window manager. 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 Mon Sep 27 01:38:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01790; Mon, 27 Sep 93 01:38:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22169; Mon, 27 Sep 93 01:21:16 -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 AA22163; Mon, 27 Sep 93 01:21:13 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <26148-0@susssys1.reading.ac.uk>; Mon, 27 Sep 1993 09:21:03 +0100 Date: Mon, 27 Sep 1993 09:17:51 +0100 (BST) From: Mike Roch Subject: Re: News To: Steve Hubert Cc: "Robert A. Hayden" , Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 24 Sep 1993, Steve Hubert wrote: > Sorry, you're not missing anything. There is no ability to post from > pine yet. > To post a message to news.group.name you can always Compose a message to news-group-name@cs.utexas.edu. This gateway forwards mail to news. 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 Mon Sep 27 08:57:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09833; Mon, 27 Sep 93 08:57:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25148; Mon, 27 Sep 93 08:18:29 -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 AA25141; Mon, 27 Sep 93 08:18:27 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA12374; Mon, 27 Sep 93 11:16:24 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA06732; Mon, 27 Sep 93 11:16:45 EDT Date: Mon, 27 Sep 1993 11:15:56 -0400 (EST) From: Keith Christopher Subject: Compiling Pine3.85 using GCC To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1469 under solaris2.2, here's the error: ddrbook.c: In function `addr_book': addrbook.c:845: `h_use_address_book' undeclared (first use this function) addrbook.c:845: (Each undeclared identifier is reported only once addrbook.c:845: for each function it appears in.) addrbook.c:847: `h_address_book' undeclared (first use this function) addrbook.c: In function `add_add': addrbook.c:1759: `h_oe_add_addr' undeclared (first use this function) addrbook.c:1787: `h_oe_add_nick' undeclared (first use this function) addrbook.c: In function `create_list': addrbook.c:1923: `h_oe_crlst_full' undeclared (first use this function) addrbook.c:1944: `h_oe_crlst_nick' undeclared (first use this function) addrbook.c:1991: `h_oe_crlst_addr' undeclared (first use this function) addrbook.c: In function `addr_to_list': addrbook.c:2108: `h_oe_adlst_addr' undeclared (first use this function) addrbook.c: In function `change_address_entry': addrbook.c:2195: `h_oe_editab_nick' undeclared (first use this function) addrbook.c:2251: `h_oe_editab_full' undeclared (first use this function) addrbook.c:2274: `h_oe_editab_addr' undeclared (first use this function) addrbook.c:2322: `h_oe_editab_al' undeclared (first use this function) addrbook.c: In function `search_book': addrbook.c:2396: `h_oe_searchab' undeclared (first use this function) *** Error code 1 make: Fatal error: Command failed for target `addrbook.o' Keith Christopher Welch Medical Library Unix System Adminstrator From owner-pine-info@cac.washington.edu Mon Sep 27 09:51:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12041; Mon, 27 Sep 93 09:51:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26727; Mon, 27 Sep 93 09:37:50 -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 AA26721; Mon, 27 Sep 93 09:37:48 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08623; Mon, 27 Sep 93 09:37:45 -0700 Date: Mon, 27 Sep 1993 09:35:23 -0700 (PDT) From: David L Miller Subject: Re: Compiling Pine3.85 using GCC To: Keith Christopher Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I took a stab at making Pine 3.85 compile with GCC 2.4.5 under Solaris, but didn't get very far before time ran out. If you get it working, we would be happy to include your changes though... |\ | |\/| 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, 27 Sep 1993, Keith Christopher wrote: > under solaris2.2, > > here's the error: > > > ddrbook.c: In function `addr_book': > addrbook.c:845: `h_use_address_book' undeclared (first use this function) > addrbook.c:845: (Each undeclared identifier is reported only once > addrbook.c:845: for each function it appears in.) > addrbook.c:847: `h_address_book' undeclared (first use this function) > addrbook.c: In function `add_add': > addrbook.c:1759: `h_oe_add_addr' undeclared (first use this function) > addrbook.c:1787: `h_oe_add_nick' undeclared (first use this function) > addrbook.c: In function `create_list': > addrbook.c:1923: `h_oe_crlst_full' undeclared (first use this function) > addrbook.c:1944: `h_oe_crlst_nick' undeclared (first use this function) > addrbook.c:1991: `h_oe_crlst_addr' undeclared (first use this function) > addrbook.c: In function `addr_to_list': > addrbook.c:2108: `h_oe_adlst_addr' undeclared (first use this function) > addrbook.c: In function `change_address_entry': > addrbook.c:2195: `h_oe_editab_nick' undeclared (first use this function) > addrbook.c:2251: `h_oe_editab_full' undeclared (first use this function) > addrbook.c:2274: `h_oe_editab_addr' undeclared (first use this function) > addrbook.c:2322: `h_oe_editab_al' undeclared (first use this function) > addrbook.c: In function `search_book': > addrbook.c:2396: `h_oe_searchab' undeclared (first use this function) > *** Error code 1 > make: Fatal error: Command failed for target `addrbook.o' > > > > Keith Christopher > Welch Medical Library > Unix System Adminstrator > > From owner-pine-info@cac.washington.edu Mon Sep 27 09:56:20 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12296; Mon, 27 Sep 93 09:56:20 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13104; Mon, 27 Sep 93 09:44:10 -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 AA13098; Mon, 27 Sep 93 09:44:08 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA01820; Mon, 27 Sep 93 09:44:54 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA05827; Mon, 27 Sep 93 09:47:02 -0700 Date: Mon, 27 Sep 1993 09:45:55 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Compiling Pine3.85 using GCC To: Keith Christopher Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Keith Christopher wrote: > under solaris2.2, > > here's the error: Pine is in K&R C (Ahh...purists!) GCC is ANSI compliant. To compile K&R with GCC you must use the -traditional flag. > > > ddrbook.c: In function `addr_book': > addrbook.c:845: `h_use_address_book' undeclared (first use this function) > addrbook.c:845: (Each undeclared identifier is reported only once > addrbook.c:845: for each function it appears in.) > addrbook.c:847: `h_address_book' undeclared (first use this function) > addrbook.c: In function `add_add': > addrbook.c:1759: `h_oe_add_addr' undeclared (first use this function) > addrbook.c:1787: `h_oe_add_nick' undeclared (first use this function) > addrbook.c: In function `create_list': > addrbook.c:1923: `h_oe_crlst_full' undeclared (first use this function) > addrbook.c:1944: `h_oe_crlst_nick' undeclared (first use this function) > addrbook.c:1991: `h_oe_crlst_addr' undeclared (first use this function) > addrbook.c: In function `addr_to_list': > addrbook.c:2108: `h_oe_adlst_addr' undeclared (first use this function) > addrbook.c: In function `change_address_entry': > addrbook.c:2195: `h_oe_editab_nick' undeclared (first use this function) > addrbook.c:2251: `h_oe_editab_full' undeclared (first use this function) > addrbook.c:2274: `h_oe_editab_addr' undeclared (first use this function) > addrbook.c:2322: `h_oe_editab_al' undeclared (first use this function) > addrbook.c: In function `search_book': > addrbook.c:2396: `h_oe_searchab' undeclared (first use this function) > *** Error code 1 > make: Fatal error: Command failed for target `addrbook.o' > > > > Keith Christopher > Welch Medical Library > Unix System Adminstrator > > > ------------------------------------------------------------------------------ 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 Mon Sep 27 10:21:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13865; Mon, 27 Sep 93 10:21:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13276; Mon, 27 Sep 93 10:06:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from qualcomm.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13265; Mon, 27 Sep 93 10:06:09 -0700 Received: from herbie.qualcomm.com by qualcomm.com; id AA21094 sendmail 5.65/QC-main-2.1 via SMTP Mon, 27 Sep 93 10:05:56 -0700 for pine-info@cac.washington.edu Received: by herbie; id AA07340 sendmail 5.67/QC-subsidiary-2.1 Mon, 27 Sep 93 10:05:54 -0700 for pine-info@cac.washington.edu Date: Mon, 27 Sep 1993 10:04:55 -0700 (PDT) From: Jason Hough Subject: Nevermind To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I answered my own question. All I have to do is type in the first part of the word and hit return. :P Thanks anyway! :D --------------------------------------------------------------------------- Jason Hough | jhough@qualcomm.com "This world shaprens teeth..." - Marillion --------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Mon Sep 27 10:21:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13867; Mon, 27 Sep 93 10:21:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13314; Mon, 27 Sep 93 10:09:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from qualcomm.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13308; Mon, 27 Sep 93 10:09:35 -0700 Received: from herbie.qualcomm.com by qualcomm.com; id AA21094 sendmail 5.65/QC-main-2.1 via SMTP Mon, 27 Sep 93 10:05:56 -0700 Received: by herbie; id AA07340 sendmail 5.67/QC-subsidiary-2.1 Mon, 27 Sep 93 10:05:54 -0700 for pine-info@cac.washington.edu Date: Mon, 27 Sep 1993 10:04:55 -0700 (PDT) From: Jason Hough Subject: Nevermind To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From owner-pine-info@cac.washington.edu Mon Sep 27 10:21:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13895; Mon, 27 Sep 93 10:21:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13278; Mon, 27 Sep 93 10:06:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from revival.evansville.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13266; Mon, 27 Sep 93 10:06:09 -0700 Received: by revival (Linux Smail3.1.28.1 #4) id m0ohHJV-0004HQC; Mon, 27 Sep 93 12:04 GMT Date: Mon, 27 Sep 1993 12:01:43 +0000 From: Patrick Heck Subject: Turning off update command in 3.85 To: Pine Info List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there a way through the pine.conf configuration file to disable the update command? I've already had some users get confused when they stumbled upon this command. I like the ease of obtaining update files, but don't really need this ability for my typical users. Patrick Heck University of Evansville heck@evansville.edu From owner-pine-info@cac.washington.edu Mon Sep 27 10:24:28 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14086; Mon, 27 Sep 93 10:24:28 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13161; Mon, 27 Sep 93 09:57:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from qualcomm.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13155; Mon, 27 Sep 93 09:57:50 -0700 Received: from herbie.qualcomm.com by qualcomm.com; id AA19570 sendmail 5.65/QC-main-2.1 via SMTP Mon, 27 Sep 93 09:57:27 -0700 for pine-info@cac.washington.edu Received: by herbie; id AA07307 sendmail 5.67/QC-subsidiary-2.1 Mon, 27 Sep 93 09:57:19 -0700 for pine-info@cac.washington.edu Date: Mon, 27 Sep 1993 09:49:44 -0700 (PDT) From: Jason Hough Subject: Feature for future version To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Something I'd like to see in Pine, when you go to select a mail folder and hit W to search for a mailbox, as you type in the name of the mailbox I'd like it to highlight whatever match it can find from what I've entered so far. I don't know about the rest of you but I have about 75 folders, and it would be real nice to not have to type in the whole name. For example, mailbox name is hotline.todo if I enter "hot" and thats the only mailbox with that beginning, it's already highlighted and I can enter it right then. Whether it does this automatically, or similar to a file completion key (like escape), I think that would be a helpful, if small, feature. Just a suggestion --------------------------------------------------------------------------- Jason Hough | jhough@qualcomm.com Computer Support Hotline x4122 pager 621-8657 --------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Mon Sep 27 10:25:58 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14147; Mon, 27 Sep 93 10:25:58 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13368; Mon, 27 Sep 93 10:14:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bart.meiko.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13362; Mon, 27 Sep 93 10:13:56 -0700 Received: by bart.meiko.com id AA10464 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 27 Sep 1993 13:13:52 -0400 Date: Mon, 27 Sep 1993 12:55:22 -0400 (EDT) From: Mike Stok Subject: Mail folders... To: pine-info@cac.washington.edu Cc: Mike Stok Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I am planning to upgrade pine to 3.85, but have been stumped by the new mail folders stuff... This may be due to my not having read the documentation, or the effects of prolonged exposure to Sam Adams over the weekend (though I'd rather be down the Vic any day, Barry). Anyway the problem I'm creating is that I have all sorts of folders in ~/mail which used to show up in Pine 3.07 quite happily when I did a 'G'oto folder, in 3.85 Pine is seeing the contents of the directory 'cos it gripes about not being able to create saved-messages, but when I use L from the main menu all I can see is an INBOX in my mail collection. I have tried fiddling about with adding collections to my folder-collections, but to no avail... I get: -------------------------------------------------------------------------------- Folder-collection (Local) -------------------------------------------------------------------------------- [ ** Empty List ** Select Here to Try Re-Expanding ] when I set my folder-collections to mail/[],~/mail/[], and yet when I list the directory they folders are there, and when I try to add an existing folder I get the message [Can't create folder mail/llnl: folder already exists] which suggests I'm pointed at the right place. I'm on a Sun running 4.1.3 with a "better" bind & resolv+2.1, what do I have to do to see these mail folders? Mike (open mouth, insert foot :-) Stok -- 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 Mon Sep 27 10:35:12 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14606; Mon, 27 Sep 93 10:35:12 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13411; Mon, 27 Sep 93 10:22:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from umailsrv0.umd.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13405; Mon, 27 Sep 93 10:22:03 -0700 Received: by umailsrv0.UMD.EDU (5.57/Ultrix3.0-C) id AA14641; Mon, 27 Sep 93 13:21:46 -0400 Received: from CSC-HW/MAILQ by csc-hw.umd.edu (Mercury 1.1); Mon, 27 Sep 93 13:21:54 EDT To: pine-info@cac.washington.edu From: "Darren Henderson" Organization: Computer Science Center Date: 27 Sep 93 13:21:17 EDT Subject: your mailing list Priority: normal X-Mailer: Pegasus Mail v2.3 (R5). Message-Id: <3A39E4E5483@csc-hw.umd.edu> Please add me to your mailing list. I am not familiar with the syntax to do this, so if you could tell me exactly what to do, I will do it. Thank you. Darren Henderson From owner-pine-info@cac.washington.edu Mon Sep 27 11:18:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16320; Mon, 27 Sep 93 11:18:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28209; Mon, 27 Sep 93 10:52: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 AA28203; Mon, 27 Sep 93 10:52:53 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10594; Mon, 27 Sep 93 10:52:46 -0700 Date: Mon, 27 Sep 1993 10:47:00 -0700 (PDT) From: David L Miller Subject: Re: Mail folders... To: Mike Stok Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Check for a .mailboxlist file. If pine finds this file, it will assume that it is a list of folders. A couple days before we released 3.85 we found out that there are a some programs out there (e.g. XLview) that create empty .mailboxlist files that trip us up. The workaround for now is to delete or rename the .mailboxlist file. |\ | |\/| 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, 27 Sep 1993, Mike Stok wrote: > I am planning to upgrade pine to 3.85, but have been stumped by the new > mail folders stuff... This may be due to my not having read the > documentation, or the effects of prolonged exposure to Sam Adams over the > weekend (though I'd rather be down the Vic any day, Barry). Anyway the > problem I'm creating is that I have all sorts of folders in ~/mail which > used to show up in Pine 3.07 quite happily when I did a 'G'oto folder, in > 3.85 Pine is seeing the contents of the directory 'cos it gripes about > not being able to create saved-messages, but when I use L from the main > menu all I can see is an INBOX in my mail collection. I have tried > fiddling about with adding collections to my folder-collections, but to > no avail... > > I get: > > -------------------------------------------------------------------------------- > Folder-collection (Local) > -------------------------------------------------------------------------------- > > [ ** Empty List ** Select Here to Try Re-Expanding ] > > when I set my folder-collections to mail/[],~/mail/[], and yet when I list > the directory they folders are there, and when I try to add an existing > folder I get the message > > [Can't create folder mail/llnl: folder already exists] > > which suggests I'm pointed at the right place. > > I'm on a Sun running 4.1.3 with a "better" bind & resolv+2.1, what do I > have to do to see these mail folders? > > Mike (open mouth, insert foot :-) Stok > > -- > 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 Mon Sep 27 11:19:30 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16361; Mon, 27 Sep 93 11:19:30 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28247; Mon, 27 Sep 93 10:54:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from wuecl.wustl.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28237; Mon, 27 Sep 93 10:54:07 -0700 Received: by wuecl.wustl.edu (4.1/SMI-SVR4) id AA00662; Mon, 27 Sep 93 12:53:44 CDT Date: Mon, 27 Sep 1993 12:51:47 -0500 (CDT) From: Chris Dunphy Subject: Other than /usr/local.... To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to suggest that in the future there should be an option to build to specify a default destination directory other than /usr/local.... Yes, I know you can edit the source, but I think enough people out there would be interested in this to make it a little more convenient. Chris Dunphy From owner-pine-info@cac.washington.edu Mon Sep 27 11:25:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16491; Mon, 27 Sep 93 11:25:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13638; Mon, 27 Sep 93 10:58:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from wugate.wustl.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13632; Mon, 27 Sep 93 10:58:01 -0700 Received: by wugate.wustl.edu (5.65c+/WUSTL-0.3) with SMTP id AA01709; Mon, 27 Sep 1993 12:57:51 -0500 Received: by whats-next.ecs.wustl.edu (NX5.67c/NX3.0M) id AA01023; Mon, 27 Sep 93 12:52:51 -0500 Date: Mon, 27 Sep 1993 12:51:36 -0500 (CDT) From: Timothy Bergeron Subject: Re: Mail folders... To: Mike Stok Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I encountered the same problem that Mike describes. Something had created a .mailboxlist list in my home directory. After I removed this file, the folders showed up in the folder list as expected. Timothy Bergeron On Mon, 27 Sep 1993, Mike Stok wrote: > I am planning to upgrade pine to 3.85, but have been stumped by the new > mail folders stuff... This may be due to my not having read the > documentation, or the effects of prolonged exposure to Sam Adams over the > weekend (though I'd rather be down the Vic any day, Barry). Anyway the > problem I'm creating is that I have all sorts of folders in ~/mail which > used to show up in Pine 3.07 quite happily when I did a 'G'oto folder, in > 3.85 Pine is seeing the contents of the directory 'cos it gripes about > not being able to create saved-messages, but when I use L from the main > menu all I can see is an INBOX in my mail collection. I have tried > fiddling about with adding collections to my folder-collections, but to > no avail... > > I get: > > -------------------------------------------------------------------------------- > Folder-collection (Local) > -------------------------------------------------------------------------------- > > [ ** Empty List ** Select Here to Try Re-Expanding ] > > when I set my folder-collections to mail/[],~/mail/[], and yet when I list > the directory they folders are there, and when I try to add an existing > folder I get the message > > [Can't create folder mail/llnl: folder already exists] > > which suggests I'm pointed at the right place. > > I'm on a Sun running 4.1.3 with a "better" bind & resolv+2.1, what do I > have to do to see these mail folders? > > Mike (open mouth, insert foot :-) Stok > > -- > 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 Mon Sep 27 11:29:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16734; Mon, 27 Sep 93 11:29:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13750; Mon, 27 Sep 93 11:05:46 -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 AA13744; Mon, 27 Sep 93 11:05:31 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA22748; Mon, 27 Sep 93 14:05:23 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA05368; Mon, 27 Sep 93 14:05:22 -0400 Date: Mon, 27 Sep 1993 13:46:40 -0400 (EDT) From: Alex Tang Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: John Ladwig Cc: pine-bugs@cac.washington.edu, pine-info@cac.washington.edu In-Reply-To: <9309271732.AA14448@saturn.soils.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, John Ladwig wrote: > I'm running Pine and Pico on both sun4c/SunOS4.1.2 and NeXT(black)/ > Stuff deleted.... > Under some userids on the NEXTSTEP 2.1 installation, Pico does not > recognize ^M (or the return key) in vt102 emulation from CUTCP Telnet > 2.2/TC or vt320 emulation from MS-Kermit 3.13(pl8) in vt320 emulation. > This problem doesn't appear on the NeXT console, as near as I can tell. > > Primary symptom is the "[ Can now UnJustify! ]" message being given at > every carriage return, with paragraph wrapping. This in itself isn't > awful, but if one tries to respond to various prompts for filenames, > enclosure headers, and the like, one is completely out of luck, since > the carriage return is interpreted as ^J, and mapped to Justify in > some cases and Attach in others, depending on context. Hi. I'm having very similar problems. I've seen it on pine 3.05, 3.07, and now 3.85. i've seen it happen at different places. First, We have a NeXT running NeXTstep 3.0, If we use console to run pine in the NeXT, it works fine. If we use MacNCSA Telnet 2.5/2.6 to telnet to the next, we get the ^J mapping thing. It only happens when within PINE or PICO. If I use an alternate editor (vi), it works fine. The second place I see it is on my NetBSD-0.8 box. It's the same circumstances when using NCSA telnet for mac. If i telnet directly to the NetBSD macine, I get the ^J thing. If i use NCSA to telnet to a sun pine works fine, and if i telnet to my netbsd box, it works fine then too. i'm confused. ...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 :) From owner-pine-info@cac.washington.edu Mon Sep 27 12:22:47 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19481; Mon, 27 Sep 93 12:22:47 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29891; Mon, 27 Sep 93 12:07:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from darkwing.uoregon.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29885; Mon, 27 Sep 93 12:07:15 -0700 Received: by darkwing.uoregon.edu (4.1/UofO NetSvc-02/24/93) id AA26341; Mon, 27 Sep 93 12:07:03 PDT Date: Mon, 27 Sep 1993 12:04:25 -0700 (PDT) From: Jason Fosback Subject: Re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: John Ladwig Cc: pine-info@cac.washington.edu In-Reply-To: <9309271732.AA14448@saturn.soils.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, John Ladwig wrote: > Under some userids on the NEXTSTEP 2.1 installation, Pico does not > recognize ^M (or the return key) in vt102 emulation from CUTCP Telnet > 2.2/TC or vt320 emulation from MS-Kermit 3.13(pl8) in vt320 emulation. > This problem doesn't appear on the NeXT console, as near as I can tell. This problem is a bug in the telnetd that ships with NeXTSTEP. A newer version of the telnetd will fix the problem under NeXTSTEP 2.x, but under 3.x, it will not. You can try adding the line: stty -extproc to the .login or /etc/login.std. This fixes the bug under 3.x, and should work under 2.x as well. -jason ___________________________________________________________________ Jason Fosback, User Support Analyst | No sir, I didn't like it ---- University of Oregon ---- | -R&S Internet: jfosback@oregon.uoregon.edu | Star Trek: NeXT mail: jfosback@darkwing.uoregon.edu | The NeXT Generation... From owner-pine-info@cac.washington.edu Mon Sep 27 12:48:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20390; Mon, 27 Sep 93 12:48:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14334; Mon, 27 Sep 93 12:36:29 -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 AA14328; Mon, 27 Sep 93 12:36:27 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA04253; Mon, 27 Sep 93 12:37:14 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA06207; Mon, 27 Sep 93 12:39:22 -0700 Date: Mon, 27 Sep 1993 12:38:38 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Feature for future version To: Jason Hough Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Jason Hough wrote: > Something I'd like to see in Pine, when you go to select a mail folder > and hit W to search for a mailbox, as you type in the name of the mailbox > I'd like it to highlight whatever match it can find from what I've > entered so far. I don't know about the rest of you but I have about 75 > folders, and it would be real nice to not have to type in the whole name. > > For example, mailbox name is hotline.todo > > if I enter "hot" and thats the only mailbox with that beginning, it's > already highlighted and I can enter it right then. Whether it does this > automatically, or similar to a file completion key (like escape), I think > that would be a helpful, if small, feature. Try hitting ...3.85 has foldername completion... > > Just a suggestion > > > --------------------------------------------------------------------------- > Jason Hough | jhough@qualcomm.com > Computer Support Hotline > x4122 pager 621-8657 > --------------------------------------------------------------------------- > > > ------------------------------------------------------------------------------ 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 Mon Sep 27 18:25:22 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03755; Mon, 27 Sep 93 18:25:22 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16147; Mon, 27 Sep 93 18:10:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from nico.aarnet.edu.au by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16141; Mon, 27 Sep 93 18:10:55 -0700 Received: from cruskit.aarnet.edu.au by nico.aarnet.edu.au with SMTP id AA26517 (5.65cAARN/IDA-1.4.4 for ); Tue, 28 Sep 1993 11:07:50 +1000 Received: from localhost by cruskit.aarnet.edu.au id for aarnet.edu.au; Tue, 28 Sep 1993 11:07:52 +1000 Date: Tue, 28 Sep 1993 11:04:19 +1000 (EST) From: Andy Linton Subject: Re: Pine dumping core on Sun To: "Jason R. Thorpe" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 26 Sep 1993, Jason R. Thorpe wrote: > On Mon, 27 Sep 1993, Andy Linton wrote: > > > My working environment on the Sun is X-windows with twm as the window > > manager. If I fire up pine inside an xterm session and quit things are > > fine but I want to have pine as a menu item so in my .twmrc I have the > > following menu item: > > > > "pine" !"xterm -title pine -name pine -e pine -i &" > > > > I'll ask the question again - is this just me or can other people repeat > > this problem? > > > > I'd guess that there's some cleaning up of the terminal going on after > > the xterm has gone away. > > My guess would be to write a script called xpine or something and have it > sleep after pine exits (so the terminal can clean up) and then kill the > term window... > I did just that and it 'solves' the problem. e.g. My menu item now reads: "pine" !"xterm -title pine -name pine -e mypine -i &" where 'mypine' looks like: -- #!/bin/sh pine $* sleep 1 -- I still think that this feature is a bug! -- Andy Linton A.Linton@aarnet.edu.au Network Engineer phone: +61 6 249 2874 AARNet fax: +61 6 249 1369 -- From owner-pine-info@cac.washington.edu Mon Sep 27 20:55:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06909; Mon, 27 Sep 93 20:55:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08233; Mon, 27 Sep 93 20:14:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cari.telecom.uqam.ca by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08227; Mon, 27 Sep 93 20:14:37 -0700 Received: from nobel.si.uqam.ca by cari.telecom.uqam.ca (4.1/SMI-4.2.1.pop NIS) id AA08587; Mon, 27 Sep 93 23:14:31 EDT Received: by nobel.si.uqam.ca (1.37.109.4/16.2) id AA22568; Mon, 27 Sep 93 23:14:38 -0400 Date: Mon, 27 Sep 1993 23:14:08 +0500 (EST) From: "Lavallee, Marc" Subject: Subscription To: pine-info@CAC.Washington.EDU Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please add me to the PINE mailing list From owner-pine-info@cac.washington.edu Mon Sep 27 21:15:37 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07379; Mon, 27 Sep 93 21:15:37 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16770; Mon, 27 Sep 93 21:06:21 -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 AA16764; Mon, 27 Sep 93 21:06:18 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA06936; Mon, 27 Sep 93 21:06:03 -0700 Date: Mon, 27 Sep 1993 20:52:03 -0700 (PDT) From: Mark Crispin Subject: re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: John Ladwig , Alex Tang , Jason Fosback Cc: pine-bugs@cac.washington.edu, pine-info@cac.washington.edu In-Reply-To: <9309271732.AA14448@saturn.soils.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This problem is due to a bug in the very old version of the BSD Unix Telnet server that NeXT runs. As of NEXTSTEP 3.1, this problem is still not fixed. On ftp.cac.washington.edu, the file next/telnetd-for-3.0 contains a more modern version of telnetd that fixes this problem for NEXTSTEP 3.0 systems. I built it from vanilla BSD sources, which are readily available over the net from a number of ftp services. Use the following procedure to install it: % ftp ftp.cac.washington.edu Name: anonymous Password: foo ftp> binary ftp> cd next ftp> get telnetd-for-3.0 ftp> quit % chmod +x telnetd-for-3.0 % su Password: # mv /usr/etc/telnetd /usr/etc/telnetd.old # mv telnetd-for-3.0 /usr/etc/telnetd Unfortunately, it appears that NeXT broke the TTY driver in NEXTSTEP 3.1, so this fixed telnetd does not work. I tried recompiling under 3.1, but it still doesn't work. Since NeXT doesn't supply sources, I'm clueless on how to help for 3.1, other than ``don't run 3.1 if you care about a working Telnet server.'' If you can configure your Telnet client to send CR NUL instead of CR LF when the RETURN key is hit, that will work around the problem. Unfortunately, it also means that you must type CTRL/J after the user name and password when you log in instead of RETURN. From owner-pine-info@cac.washington.edu Mon Sep 27 22:34:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08755; Mon, 27 Sep 93 22:34:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16985; Mon, 27 Sep 93 22:17:04 -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 AA16979; Mon, 27 Sep 93 22:17:03 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA00924; Mon, 27 Sep 93 22:17:50 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA00756; Mon, 27 Sep 93 22:19:58 -0700 Date: Mon, 27 Sep 1993 22:12:34 -0700 (PDT) From: "Jason R. Thorpe" Subject: address at command line... To: PINE Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Folks... I love pine and try to convert all users to it...It is very cool...However, I've found a little annoyance with the new pine that is documented in the man pages to work...I have yet to be able to specify an address on the command line...I get spit into the main menu and am told that "4 is an unrecognized command"...something like that. Any ideas? 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 Tue Sep 28 03:30:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14693; Tue, 28 Sep 93 03:30:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11176; Tue, 28 Sep 93 03:21:02 -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 AA11152; Tue, 28 Sep 93 03:20:59 -0700 Received: from dxcoms.cern.ch by dxmint.cern.ch (5.65/DEC-Ultrix/4.3) id AA10213; Tue, 28 Sep 1993 11:20:57 +0100 Received: by dxcoms.cern.ch (5.65/DEC-Ultrix/4.3) id AA09976; Tue, 28 Sep 1993 11:20:56 +0100 From: dimou@dxcoms.cern.ch (M. Dimou-Zacharova) Message-Id: <9309281020.AA09976@dxcoms.cern.ch> Subject: Pine 3.07 on decstations. Problem with gif files To: pine-info@cac.washington.edu Date: Tue, 28 Sep 1993 11:20:55 +0100 (MET) 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: 509 I must have made a mistake while installing Pine 3.07 on an Ultrix 4.3 decstation because when I want to view a gif attachment i get the following: Display result: sh: syntax error at line 1: `/usr/tmp/pine-image-view13209.2GI] If I have to explain more, please, let me know. Thanks in advance for any help - maria Maria Dimou-Zacharova Postmaster at CERN CH-1211 Geneva 23 Switzerland Email : dimou@dxcern.cern.ch X.400 : C=ch; ADMD=arcom; PRMD=cern; O=cern; OU=dxcern; S=dimou; Tel. : +41-22-7673356 From owner-pine-info@cac.washington.edu Tue Sep 28 04:48:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16205; Tue, 28 Sep 93 04:48:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11798; Tue, 28 Sep 93 04:35:41 -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 AA11792; Tue, 28 Sep 93 04:35:38 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA24072; Tue, 28 Sep 93 06:35:24 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA12678; Tue, 28 Sep 93 19:32:53 +0800 Date: Tue, 28 Sep 1993 19:30:36 +0800 (TPE) From: Ed Greshko Subject: Re: address at command line... To: "Jason R. Thorpe" Cc: PINE In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Jason R. Thorpe wrote: > Folks... > > I love pine and try to convert all users to it...It is very > cool...However, I've found a little annoyance with the new pine that is > documented in the man pages to work...I have yet to be able to specify an > address on the command line...I get spit into the main menu and am told > that "4 is an unrecognized command"...something like that. Any ideas? Hummm....it works fine for me. Can you give a few more details of you set up? OS, hardware, terminal type, etc.? I'm running pine 3.85 on a MIPS platform. 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 Tue Sep 28 08:09:33 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19209; Tue, 28 Sep 93 08:09:33 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13225; Tue, 28 Sep 93 07:56:59 -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 AA13219; Tue, 28 Sep 93 07:56:58 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12300; Tue, 28 Sep 93 07:56:51 -0700 Date: Tue, 28 Sep 1993 07:49:57 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: address at command line... To: "Michael A. Crowley" Cc: "Jason R. Thorpe" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mike, Jason has confirmed to me that he indeed does have Pine aliased with -i. Folks: we've been bit by the law of unintended consequences again, which is a polite way of saying we failed to think about the interaction of the new keystroke list option with existing aliases that included -i. Sorry about that... We'll be discussing today what, if anything, might be reasonable to do about this. (In retrospect, I would vote for the new keystroke list to be -I in caps, and leave -i alone. Command line options are the one place in Pine where we've allowed input to be case-sensitive.) -teg On Tue, 28 Sep 1993, Michael A. Crowley wrote: > > I found a similar thing which happened because many of us > used the alias: > alias pine 'pine -iz' > > The new keystroke feature now has the "i" option take a series of > commands for advance keystroke input. It can take them with > or without a space after the "i", and in the above alias, it gets > confused with the "z" present. Had we used "-zi" instead, we > never would have noticed this. > From owner-pine-info@cac.washington.edu Tue Sep 28 08:16:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19523; Tue, 28 Sep 93 08:16:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13356; Tue, 28 Sep 93 08:06:49 -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 AA13350; Tue, 28 Sep 93 08:06:47 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12347; Tue, 28 Sep 93 08:06:41 -0700 Date: Tue, 28 Sep 1993 08:05:22 -0700 (PDT) From: Terry Gray Subject: Re: Pine 3.07 on decstations. Problem with gif files To: maria.dimou@cern.ch Cc: pine-info@cac.washington.edu In-Reply-To: <9309281020.AA09976@dxcoms.cern.ch> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Maria, Is the "image-viewer=" variable set correctly in your .pinerc, or in the system-wide pine.conf file? It should specify the path of a suitable program such as xloadimage or xv. -teg On Tue, 28 Sep 1993, M. Dimou-Zacharova wrote: > I must have made a mistake while installing Pine 3.07 on an Ultrix 4.3 > decstation because when I want to view a gif attachment i get the following: > > Display result: sh: syntax error at line 1: `/usr/tmp/pine-image-view13209.2GI] > > If I have to explain more, please, let me know. > > Thanks in advance for any help > > - maria > > Maria Dimou-Zacharova > Postmaster at CERN > CH-1211 Geneva 23 > Switzerland > Email : dimou@dxcern.cern.ch > X.400 : C=ch; ADMD=arcom; PRMD=cern; O=cern; OU=dxcern; S=dimou; > Tel. : +41-22-7673356 > From owner-pine-info@cac.washington.edu Tue Sep 28 09:20:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21936; Tue, 28 Sep 93 09:20:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14601; Tue, 28 Sep 93 09:04:49 -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 AA14591; Tue, 28 Sep 93 09:04:35 -0700 Received: from vega.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <23716-0@dummy1.dur.ac.uk>; Tue, 28 Sep 1993 17:04:27 +0100 Received: from altair (altair.dur.ac.uk) by vega.dur.ac.uk; Tue, 28 Sep 93 17:04:23 BST Date: Tue, 28 Sep 1993 16:54:21 +0100 (BST) From: Barry Cornelius Subject: Re: address at command line... To: Terry Gray Cc: "Michael A. Crowley" , "Jason R. Thorpe" , Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1650 On Tue, 28 Sep 1993, Terry Gray wrote: > Mike, > Jason has confirmed to me that he indeed does have Pine aliased with -i. > > Folks: we've been bit by the law of unintended consequences again, > which is a polite way of saying we failed to think about the interaction > of the new keystroke list option with existing aliases that included -i. > Sorry about that... We'll be discussing today what, if anything, might be > reasonable to do about this. (In retrospect, I would vote for the new > keystroke list to be -I in caps, and leave -i alone. Command line > options are the one place in Pine where we've allowed input to be > case-sensitive.) This is one that has hit us too. In the past the department concerned had advised its users to have an alias for "pine" that did "pine -iz". Yesterday, they rang up to moan that this was causing problems. They also include a departmental bin dirtectory in the search path, and so I suggested they include in that directory a shell script called pine that does: if parameter is -iz then echo change your pine alias to "pine -z -i" else exec /usr/local/share/bin/pine $* endif [The file /usr/local/share/bin/pine is the place where the executable for pine is located.] Agreed that it's tortuous, but hopefully it is solving their problem. I haven't given any thought as to what I would suggest for the next release of Pine. -- 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 Tue Sep 28 09:31:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22435; Tue, 28 Sep 93 09:31:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14978; Tue, 28 Sep 93 09:19:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from darkwing.uoregon.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14972; Tue, 28 Sep 93 09:19:27 -0700 Received: by darkwing.uoregon.edu (4.1/UofO NetSvc-02/24/93) id AA09473; Tue, 28 Sep 93 09:19:25 PDT Date: Tue, 28 Sep 1993 09:11:40 -0700 (PDT) From: Jason Fosback Subject: re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: Mark Crispin Cc: John Ladwig , Alex Tang , pine-bugs@cac.washington.edu, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 27 Sep 1993, Mark Crispin wrote: > This problem is due to a bug in the very old version of the BSD Unix Telnet > server that NeXT runs. As of NEXTSTEP 3.1, this problem is still not fixed. [Good stuff on how to get a working telnetd for 2.x, 3.0 deleted] > Unfortunately, it appears that NeXT broke the TTY driver in NEXTSTEP 3.1, so > this fixed telnetd does not work. I tried recompiling under 3.1, but it still > doesn't work. Since NeXT doesn't supply sources, I'm clueless on how to help > for 3.1, other than ``don't run 3.1 if you care about a working Telnet > server.'' My previous message stands about this problem for 3.1. I had tried recompiling the telnetd that Mark is talking about, but it is definitely broken under NeXTSTEP 3.1. If you add an obscure, undocumented command to your .login, or to /etc/login.std, this problem with the CTRL-J will go away. Believe me, it works. We have more than 40 NeXTSTEP machines that this is working on. The CTRL-J problem is not just limited to Pine or Pico, either. Try using tin, rn, or any other vt-100 oriented program. Again, if you add the following to your .login, it will fix the problem: stty -extproc -jason ___________________________________________________________________ Jason Fosback, User Support Analyst | No sir, I didn't like it ---- University of Oregon ---- | -R&S Internet: jfosback@oregon.uoregon.edu | Star Trek: NeXT mail: jfosback@darkwing.uoregon.edu | The NeXT Generation... From owner-pine-info@cac.washington.edu Tue Sep 28 10:43:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25456; Tue, 28 Sep 93 10:43:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19865; Tue, 28 Sep 93 10:32:00 -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 AA19859; Tue, 28 Sep 93 10:31:56 -0700 Received: by mhc.mtholyoke.edu (5.57/Ultrix4.2a_930410.01) id AA22760; Tue, 28 Sep 93 13:31:32 -0400 Date: Tue, 28 Sep 1993 13:30:30 -0400 (EDT) From: "Michael A. Crowley" Subject: Re: address at command line... To: Barry Cornelius Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I believe "pine -zi" works fine. "pine -iz" does not. Mike From owner-pine-info@cac.washington.edu Tue Sep 28 11:12:50 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26484; Tue, 28 Sep 93 11:12:50 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20069; Tue, 28 Sep 93 11:03:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from NOC4.DCCS.UPENN.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20063; Tue, 28 Sep 93 11:03:29 -0700 Received: from LEXIS.POP.UPENN.EDU by noc4.dccs.upenn.edu id AA04091; Tue, 28 Sep 93 14:03:27 -0400 Return-Path: Received: by lexis id AA32008; Tue, 28 Sep 1993 14:08:46 -0400 Posted-Date: Tue, 28 Sep 1993 14:05:05 -0400 (EDT) Date: Tue, 28 Sep 1993 14:05:05 -0400 (EDT) From: Tim Cheney Reply-To: Tim Cheney Subject: Is there an IMAP query TSR for DOS w/TCPIP To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Does anyone know of a DOS TSR that could periodically poll a UNIX mail server running IMAPD for new mail over a TCP/IP network and announce the new mail? From owner-pine-info@cac.washington.edu Tue Sep 28 11:18:09 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26611; Tue, 28 Sep 93 11:18:09 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20123; Tue, 28 Sep 93 11:09:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20117; Tue, 28 Sep 93 11:09:08 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA10430; Tue, 28 Sep 93 11:09:54 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA03925; Tue, 28 Sep 93 11:10:40 -0700 Date: Tue, 28 Sep 1993 11:08:40 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: address at command line... To: Ed Greshko Cc: PINE In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 28 Sep 1993, Ed Greshko wrote: > On Mon, 27 Sep 1993, Jason R. Thorpe wrote: > > > Folks... > > > > I love pine and try to convert all users to it...It is very > > cool...However, I've found a little annoyance with the new pine that is > > documented in the man pages to work...I have yet to be able to specify an > > address on the command line...I get spit into the main menu and am told > > that "4 is an unrecognized command"...something like that. Any ideas? > > Hummm....it works fine for me. > > Can you give a few more details of you set up? OS, hardware, > terminal type, etc.? HP 9000/433 68040-50 HP-UX 9.01 X11R5, I usually run from an x-terminal, but it happens to matter what term type I use. Pine is aliased: alias pine -z -i It worked with the older versions... > > I'm running pine 3.85 on a MIPS platform. > > 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 > > > ------------------------------------------------------------------------------ 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 Tue Sep 28 11:25:10 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26981; Tue, 28 Sep 93 11:25:10 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20153; Tue, 28 Sep 93 11:14:41 -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 AA20147; Tue, 28 Sep 93 11:14:40 -0700 Received: from stimpy.css.itd.umich.edu by css.itd.umich.edu (5.67/2.2) id AA03130; Tue, 28 Sep 93 14:14:38 -0400 Received: by stimpy.css.itd.umich.edu (5.67/dumb-1.0) id AA18236; Tue, 28 Sep 93 14:14:36 -0400 Date: Tue, 28 Sep 1993 14:11:51 -0400 (EDT) From: Alex Tang Subject: saved messages marked as NEW/folder lock To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Tue Sep 28 11:34:04 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27336; Tue, 28 Sep 93 11:34:04 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20196; Tue, 28 Sep 93 11:21:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20190; Tue, 28 Sep 93 11:21:40 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA10552; Tue, 28 Sep 93 11:22:18 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA04370; Tue, 28 Sep 93 11:23:02 -0700 Date: Tue, 28 Sep 1993 11:20:40 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: address at command line... To: Terry Gray Cc: "Michael A. Crowley" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 28 Sep 1993, Terry Gray wrote: > Mike, > Jason has confirmed to me that he indeed does have Pine aliased with -i. > > Folks: we've been bit by the law of unintended consequences again, > which is a polite way of saying we failed to think about the interaction > of the new keystroke list option with existing aliases that included -i. > Sorry about that... We'll be discussing today what, if anything, might be > reasonable to do about this. (In retrospect, I would vote for the new > keystroke list to be -I in caps, and leave -i alone. Command line > options are the one place in Pine where we've allowed input to be > case-sensitive.) If you can tell me where pine parses it's command-line I'll make the hack and edit our local man pages... 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 Tue Sep 28 11:36:34 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27470; Tue, 28 Sep 93 11:36:34 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20214; Tue, 28 Sep 93 11:26:35 -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 AA20208; Tue, 28 Sep 93 11:26:33 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA03798; Tue, 28 Sep 1993 13:30:09 -0500 Date: Tue, 28 Sep 1993 13:27:29 -0500 (CDT) From: "Robert A. Hayden" Subject: Command Line Options (Was: Re: address at command line...) To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 28 Sep 1993, Michael A. Crowley wrote: > I believe "pine -zi" works fine. "pine -iz" does not. I have mine running as 'pine -i -z' and it works just as it always has. But I agree, the initial keystroke list should use -I or some other identifier to avoid confusion. {[> 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 Tue Sep 28 12:24:53 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29291; Tue, 28 Sep 93 12:24:53 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20522; Tue, 28 Sep 93 12:15:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20516; Tue, 28 Sep 93 12:15:14 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA11198; Tue, 28 Sep 93 12:15:58 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA05745; Tue, 28 Sep 93 12:18:06 -0700 Date: Tue, 28 Sep 1993 12:17:47 -0700 (PDT) From: "Jason R. Thorpe" 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 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.... A "mis-feature" for us too... > > ...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." > > > ------------------------------------------------------------------------------ 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 Tue Sep 28 14:23:54 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03932; Tue, 28 Sep 93 14:23:54 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21227; Tue, 28 Sep 93 14:13:09 -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 AA21221; Tue, 28 Sep 93 14:13:07 -0700 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA02456; Tue, 28 Sep 93 17:13:03 -0400 Received: from smc.UUCP by uucp3.uu.net with UUCP/RMAIL (queueing-rmail) id 171109.27647; Tue, 28 Sep 1993 17:11:09 EDT Received: from sol by smc.com (4.1/Standard-Microsystems-Corporation) id AA18275; Tue, 28 Sep 93 16:56:19 EDT Date: Tue, 28 Sep 1993 16:42:30 -0400 (EDT) From: Tom Adams Reply-To: Tom Adams Subject: Automatic fill of user's real name in compose To: Pine Distribution List Cc: adams@smc.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII 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 (I assume the above is what is normally expected when the machine is fully qualified in the /etc/hosts file.) 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 Tue Sep 28 15:52:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07910; Tue, 28 Sep 93 15:52:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21922; Tue, 28 Sep 93 15:34:30 -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 AA21916; Tue, 28 Sep 93 15:34:28 -0700 Received: by kamba.cac.washington.edu (NeXT-1.0 (From Sendmail 5.52)/UW-NDC Revision: 2.27 ) id AA19350; Tue, 28 Sep 93 15:34:27 PDT Date: Tue, 28 Sep 1993 15:30:19 -0700 (PDT) From: Steve Hubert Subject: pine -i fix To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="16820114-2053975998-749255665:#19302" --16820114-2053975998-749255665:#19302 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Here is a context diff to change the behavior of the -i flag in pine3.85. This fix changes -i back to its old behavior. That is, -i means start in the index and -i doesn't take any arguments. There is a new flag, -I, which requires an argument. The argument is a comma-separated list of initial keystrokes. An alternative workaround to the problem of -i causing unexpected failures in aliases is to have another flag come after the -i. That is, pine -i -z will always work correctly. Pine -iz will never work correctly, and pine -zi will not work correctly if the alias is invoked with arguments. Sorry for the inconvenience. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle --16820114-2053975998-749255665:#19302 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=diff1 Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Diff to fix -i problem KioqIGFyZ3MuYy5vbGQJVHVlIFNlcCAyOCAxNToxOToxNSAxOTkzCi0tLSBh cmdzLmMJVHVlIFNlcCAyOCAxNToyMTo1NyAxOTkzCioqKioqKioqKioqKioq KgoqKiogMSw1ICoqKioKICAjaWYgIWRlZmluZWQobGludCkgJiYgIWRlZmlu ZWQoRE9TKQohIHN0YXRpYyBjaGFyIHJjc2lkW10gPSAiJElkOiBhcmdzLmMs diA0LjIyIDE5OTMvMDkvMjEgMTY6NDY6MzggaHViZXJ0IEV4cCAkIjsKICAj ZW5kaWYKICAvKi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KICAKLS0tIDEs NSAtLS0tCiAgI2lmICFkZWZpbmVkKGxpbnQpICYmICFkZWZpbmVkKERPUykK ISBzdGF0aWMgY2hhciByY3NpZFtdID0gIiRJZDogYXJncy5jLHYgNC4yMyAx OTkzLzA5LzI4IDIyOjIxOjI2IGh1YmVydCBFeHAgJCI7CiAgI2VuZGlmCiAg LyotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCiAgCioqKioqKioqKioqKioq KgoqKiogMTM5LDE0NCAqKioqCi0tLSAxMzksMTQ3IC0tLS0KICAJCSBjYXNl ICdvJzoKICAJCSAgIHBpbmVfc3RhdGUtPm9wZW5fcmVhZG9ubHlfb25fc3Rh cnR1cCA9IDE7CiAgCQkgICBicmVhazsKKyAJCSBjYXNlICdpJzoKKyAJCSAg IHBpbmVfc3RhdGUtPnN0YXJ0X2luX2luZGV4ID0gMTsKKyAJCSAgIGJyZWFr OwogIC8qIEpVU1QgV0hJTEVURVNUSU5HRk9MREVSUyAqLwogIAkJIGNhc2Ug J2wnOgogIAkJICAgcGluZV9zdGF0ZS0+ZXhwYW5kZWRfZm9sZGVycyA9IDE7 CioqKioqKioqKioqKioqKgoqKiogMTQ1LDE1MSAqKioqCiAgCQkgICBicmVh azsKICAvKiBFTkQgT0YgV0hJTEVURVNUSU5HRk9MREVSUyAqLwogIAkJIC8q IHRoZXNlIHRha2UgYXJndW1lbnRzICovCiEgCQkgY2FzZSAnZic6IGNhc2Ug J3AnOiAgLyogc3RyaW5nIGFyZ3MgKi8KICAjaWZuZGVmIERPUwogIAkJIGNh c2UgJ1AnOiAgLyogYWxzbyBhIHN0cmluZyAqLwogICNlbmRpZgotLS0gMTQ4 LDE1NCAtLS0tCiAgCQkgICBicmVhazsKICAvKiBFTkQgT0YgV0hJTEVURVNU SU5HRk9MREVSUyAqLwogIAkJIC8qIHRoZXNlIHRha2UgYXJndW1lbnRzICov CiEgCQkgY2FzZSAnZic6IGNhc2UgJ3AnOiBjYXNlICdJJzogIC8qIHN0cmlu ZyBhcmdzICovCiAgI2lmbmRlZiBET1MKICAJCSBjYXNlICdQJzogIC8qIGFs c28gYSBzdHJpbmcgKi8KICAjZW5kaWYKKioqKioqKioqKioqKioqCioqKiAx NjQsMTY5ICoqKioKLS0tIDE2NywxNzUgLS0tLQogIAkJICAgICBjYXNlICdm JzoKICAJCSAgICAgICBmb2xkZXIgPSBzdHI7CiAgCQkgICAgICAgYnJlYWs7 CisgCQkgICAgIGNhc2UgJ0knOgorIAkJICAgICAgIGNtZF9saXN0ID0gc3Ry OworIAkJICAgICAgIGJyZWFrOwogIAkJICAgICBjYXNlICdwJzoKICAJCSAg ICAgICBpZihzdHIgIT0gTlVMTCkKICAJCQkgIHBpbmVfc3RhdGUtPnBpbmVy YyA9IGNweXN0cihzdHIpOwoqKioqKioqKioqKioqKioKKioqIDIwMSwyMjUg KioqKgogIAkJICAgfQogIAkJICAgZ290byBMb29wOwogIAotIAkJIC8qIHRo aXMgaGFzIGFuIG9wdGlvbmFsIGFyZ3VtZW50ICovCi0gCQkgY2FzZSAnaSc6 Ci0gCQkgICBpZigqKysqYXYpIHsKLSAJCSAgICAgIGNtZF9saXN0ID0gKmF2 OwotIAkJICAgICAgZ290byBMb29wOwotIAkJICAgfQotIAkJICAgLS1hYzsg KythdjsKLSAJCSAgIGlmKGFjKSB7Ci0gCQkgICAgICBpZigqKmF2ICE9ICct JykgewotIAkJCSBjbWRfbGlzdCA9ICphdjsKLSAJCQkgZ290byBMb29wOwot IAkJICAgICAgfWVsc2UgewotIAkJCSBwaW5lX3N0YXRlLT5zdGFydF9pbl9p bmRleCA9IDE7Ci0gCQkJIGJyZWFrOwotIAkJICAgICAgfQotIAkJICAgfWVs c2UgewotIAkJICAgICAgcGluZV9zdGF0ZS0+c3RhcnRfaW5faW5kZXggPSAx OwotIAkJICAgICAgZ290byBMb29wOwotIAkJICAgfQogIAkJIGRlZmF1bHQ6 CiAgCQkgICBmcHJpbnRmKHN0ZGVyciwgIkVycm9yOiB1bmtub3duIGZsYWcg XCIlY1wiXG4iLCBjKTsKICAJCSAgICsrdXNhZ2U7Ci0tLSAyMDcsMjEyIC0t LS0KKioqKioqKioqKioqKioqCioqKiAyNDAsMjQ2ICoqKioKICAJdmFyc1tW X0lOSVRfQ01EX0xJU1RdLmNvbW1hbmRfbGluZV92YWwubCA9CiAgCQkJcGFy c2VfbGlzdChjbWRfbGlzdCwgY29tbWFzKzEsICZlcnJvcik7CiAgCWlmKGVy cm9yKSB7CiEgCSAgICBmcHJpbnRmKHN0ZGVyciwgIkVycm9yIGluIC1pIGFy Z3VtZW50IFwiJXNcIjogJXNcbiIsIGNtZF9saXN0LAogIAkJCQkJCQkJICAg IGVycm9yKTsKICAJICAgIGV4aXQoLTEpOwogIAl9Ci0tLSAyMjcsMjMzIC0t LS0KICAJdmFyc1tWX0lOSVRfQ01EX0xJU1RdLmNvbW1hbmRfbGluZV92YWwu bCA9CiAgCQkJcGFyc2VfbGlzdChjbWRfbGlzdCwgY29tbWFzKzEsICZlcnJv cik7CiAgCWlmKGVycm9yKSB7CiEgCSAgICBmcHJpbnRmKHN0ZGVyciwgIkVy cm9yIGluIC1JIGFyZ3VtZW50IFwiJXNcIjogJXNcbiIsIGNtZF9saXN0LAog IAkJCQkJCQkJICAgIGVycm9yKTsKICAJICAgIGV4aXQoLTEpOwogIAl9Cioq KioqKioqKioqKioqKgoqKiogMzA1LDMxMSAqKioqCiAgICAgICAgICBwcmlu dGYoIlx0IC1zb3J0IDxzb3J0PiBcdFNvcnQgLSBTcGVjaWZ5IHNvcnQgb3Jk ZXIgb2YgZm9sZGVyOlxuIik7CiAgICAgICAgICBwcmludGYoIlx0XHRcdCAg ICAgICAgc3ViamVjdCwgYXJyaXZhbCwgZGF0ZSwgZnJvbSwgc2l6ZSwgL3Jl dmVyc2VcbiIpOwogICAgICAgICAgcHJpbnRmKCJcdCAtaVx0XHRJbmRleCAt IEdvIGRpcmVjdGx5IHRvIGluZGV4LCBieXBhc3NpbmcgbWFpbCBtZW51XG4i KTsKISAgICAgICAgIHByaW50ZigiXHQgLWkgPGtleXN0cm9rZV9saXN0Plx0 SW5pdGlhbCBrZXlzdHJva2VzIHRvIGJlIGV4ZWN1dGVkXG4iKTsKICAgICAg ICAgIHByaW50ZigiXHQgLW4gPG51bWJlcj5cdEVudHJ5IGluIGluZGV4IHRv IGJlZ2luIG9uXG4iKTsKICAJcHJpbnRmKCJcdCAtbyBcdFx0UmVhZE9ubHkg LSBPcGVuIGZpcnN0IGZvbGRlciByZWFkLW9ubHlcbiIpOwogICAgICAgICAg cHJpbnRmKCJcdCAtY29uZlx0XHRDb25maWd1cmF0aW9uIC0gUHJpbnQgb3V0 IGJsYW5rIGdsb2JhbCBjb25maWd1cmF0aW9uXG4iKTsKLS0tIDI5MiwyOTgg LS0tLQogICAgICAgICAgcHJpbnRmKCJcdCAtc29ydCA8c29ydD4gXHRTb3J0 IC0gU3BlY2lmeSBzb3J0IG9yZGVyIG9mIGZvbGRlcjpcbiIpOwogICAgICAg ICAgcHJpbnRmKCJcdFx0XHQgICAgICAgIHN1YmplY3QsIGFycml2YWwsIGRh dGUsIGZyb20sIHNpemUsIC9yZXZlcnNlXG4iKTsKICAgICAgICAgIHByaW50 ZigiXHQgLWlcdFx0SW5kZXggLSBHbyBkaXJlY3RseSB0byBpbmRleCwgYnlw YXNzaW5nIG1haWwgbWVudVxuIik7CiEgICAgICAgICBwcmludGYoIlx0IC1J IDxrZXlzdHJva2VfbGlzdD5cdEluaXRpYWwga2V5c3Ryb2tlcyB0byBiZSBl eGVjdXRlZFxuIik7CiAgICAgICAgICBwcmludGYoIlx0IC1uIDxudW1iZXI+ XHRFbnRyeSBpbiBpbmRleCB0byBiZWdpbiBvblxuIik7CiAgCXByaW50Zigi XHQgLW8gXHRcdFJlYWRPbmx5IC0gT3BlbiBmaXJzdCBmb2xkZXIgcmVhZC1v bmx5XG4iKTsKICAgICAgICAgIHByaW50ZigiXHQgLWNvbmZcdFx0Q29uZmln dXJhdGlvbiAtIFByaW50IG91dCBibGFuayBnbG9iYWwgY29uZmlndXJhdGlv blxuIik7Cg== --16820114-2053975998-749255665:#19302-- From owner-pine-info@cac.washington.edu Tue Sep 28 17:25:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12839; Tue, 28 Sep 93 17:25:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22453; Tue, 28 Sep 93 17:13:42 -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 AA22447; Tue, 28 Sep 93 17:13:31 -0700 Received: by vanbc.wimsey.com (Smail3.1.28.1) id m0ohpAX-0000hTC; Tue, 28 Sep 93 17:13 PDT Received: from valiant.te.CdnAir.CA by jumbo1.CdnAir.CA with SMTP id AA17629 (5.65c/IDA-1.4.4 for ); Tue, 28 Sep 1993 17:06:13 -0700 Received: by valiant.te.CdnAir.CA (AIX 3.2/UCB 5.64/4.03) id AA32119; Tue, 28 Sep 1993 17:06:48 -0700 Date: Tue, 28 Sep 1993 17:04:25 -0700 (PDT) From: Grant Fengstad Subject: Incorporation of mailcap To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have recently installed Pine 3.85 on one of our RS6000's and things went very smoothly... World of difference from 3.07... Anyways, I was kind of surprised that pine doesn't use the mailcap file in order to determine how to handle MIME. How difficult would it be to incorporate? Also, is is possible for Pine to handle Postscript documents (ie: pass them on to Ghostview?) ***************************************************************************** ___ Grant Fengstad, Canadi>n Airlines ___....-----'---`-----....___ 3600 Lysander Lane ========================================= Richmond, B.C. CANADA V7B 1C3 ___`---..._______...---'___ Email: G.Fengstad@CdnAir.CA (___) _|_|_|_ (___) Phone: (604)279-6053 \\____.-'_.---._`-.____// Live long and Prosper ~~~~`.__`---'__.'~~~~ ---------------------------------------- ~~~~~ Standard Disclaimers go here... ***************************************************************************** From owner-pine-info@cac.washington.edu Tue Sep 28 18:20:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14424; Tue, 28 Sep 93 18:20:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25521; Tue, 28 Sep 93 18:13: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 AA25515; Tue, 28 Sep 93 18:13:34 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12691; Tue, 28 Sep 93 18:13:02 -0700 Date: Tue, 28 Sep 1993 18:09:01 -0700 (PDT) From: David L Miller Subject: Re: Incorporation of mailcap To: Grant Fengstad Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We did not have time to get mailcap into 3.85, but we plan to include it into 4.0. Pine will recognize a Postscript attachment and label it appropriately on outgoing mail, but it currently does not know how to call a PS viewer. All this will come with mailcap... |\ | |\/| 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, Grant Fengstad wrote: > > I have recently installed Pine 3.85 on one of our RS6000's and things > went very smoothly... World of difference from 3.07... Anyways, I was > kind of surprised that pine doesn't use the mailcap file in order to > determine how to handle MIME. How difficult would it be to incorporate? > Also, is is possible for Pine to handle Postscript documents (ie: pass > them on to Ghostview?) > > ***************************************************************************** > ___ Grant Fengstad, Canadi>n Airlines > ___....-----'---`-----....___ 3600 Lysander Lane > ========================================= Richmond, B.C. CANADA V7B 1C3 > ___`---..._______...---'___ Email: G.Fengstad@CdnAir.CA > (___) _|_|_|_ (___) Phone: (604)279-6053 > \\____.-'_.---._`-.____// Live long and Prosper > ~~~~`.__`---'__.'~~~~ ---------------------------------------- > ~~~~~ Standard Disclaimers go here... > ***************************************************************************** > > From owner-pine-info@cac.washington.edu Tue Sep 28 18:32:27 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14649; Tue, 28 Sep 93 18:32:27 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22800; Tue, 28 Sep 93 18:24: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 AA22794; Tue, 28 Sep 93 18:24:09 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA09287; Tue, 28 Sep 93 18:24:04 -0700 Date: Tue, 28 Sep 1993 18:20:23 -0700 (PDT) From: Mark Crispin 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 On Tue, 28 Sep 1993 14:11:51 -0400 (EDT), 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? This is a lack of feature. You can call it a bug if you like. The fix will be to write the code to preserve flags. This will be done in a future version. > 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. That's unfortunately correct. The second Pine cannot steal the folder lock without the first Pine's consent, but if the first Pine is suspended it cannot give that consent. Unfortunately, when it gets resumed, the lock-steal request hits, with the results you note. The workaround, at least for the time being, is not to do this. :-) -- Mark -- From owner-pine-info@cac.washington.edu Wed Sep 29 08:45:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04756; Wed, 29 Sep 93 08:45:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02587; Wed, 29 Sep 93 08:27:56 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from adelicia.belmont.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02581; Wed, 29 Sep 93 08:27:54 -0700 Received: from BELMONT.EDU by BELMONT.EDU (PMDF V4.2-13 #4825) id <01H3IMTSK2J400080B@BELMONT.EDU>; Wed, 29 Sep 1993 10:27:50 CDT Date: Wed, 29 Sep 1993 10:25:48 -0500 (CDT) From: REYNOLDSR@BELMONT.EDU Subject: pine on a VAX To: pine-info@cac.washington.edu Message-Id: <01H3IMUAMKQQ00080B@BELMONT.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Does anyone know if Pine is available for VAX systems? Also, if anyone is using a nice email similar to Pine on a VAX system I would like to know. I do know about All-in-one but thats about it. Thanks. Randall Reynolds Belmont University 615-386-4471 REYNOLDSR@BELMONT.EDU From owner-pine-info@cac.washington.edu Wed Sep 29 08:51:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05051; Wed, 29 Sep 93 08:51:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02872; Wed, 29 Sep 93 08:41:11 -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 AA02866; Wed, 29 Sep 93 08:41:09 -0700 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H3IPMTPW000004WY@mc.duke.edu>; Wed, 29 Sep 1993 11:47:08 EST Date: Wed, 29 Sep 1993 11:46:05 -0500 (EST) From: James Dryfoos- Postmaster Subject: Unknown text "IBM437" To: pine-info@cac.washington.edu Message-Id: <01H3IPOLLFKK0004WY@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 Is it possible to get Pine to deal with: [Part 1, "Text_1" Unknown text "IBM437" 3 lines] [Can not display this part. Use the "A" command to save in a file] We are bringing up a PMDF/cc:Mail gateway that apparently puts text into this charset. -- Jim From owner-pine-info@cac.washington.edu Wed Sep 29 08:59:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05310; Wed, 29 Sep 93 08:59:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03038; Wed, 29 Sep 93 08:48:19 -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 AA03032; Wed, 29 Sep 93 08:48:18 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23070; Wed, 29 Sep 93 08:48:09 -0700 Date: Wed, 29 Sep 1993 08:46:29 -0700 (PDT) From: David L Miller Subject: Re: pine on a VAX To: REYNOLDSR@BELMONT.EDU Cc: pine-info@cac.washington.edu In-Reply-To: <01H3IMUAMKQQ00080B@BELMONT.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There are unsubstantiated rumors of a VMS(Posix) port of Pine floating around, but we have not seen it... |\ | |\/| 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 REYNOLDSR@BELMONT.EDU wrote: > Does anyone know if Pine is available for VAX systems? Also, if anyone is using > a nice email similar to Pine on a VAX system I would like to know. I do know about All-in-one but thats about it. Thanks. > Randall Reynolds Belmont University 615-386-4471 > REYNOLDSR@BELMONT.EDU From owner-pine-info@cac.washington.edu Wed Sep 29 09:26:55 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06644; Wed, 29 Sep 93 09:26:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03392; Wed, 29 Sep 93 09:03:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cc.lut.fi by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03384; Wed, 29 Sep 93 09:03:23 -0700 Received: by cc.lut.fi (5.65c/IDA-1.4.4/Kim-2.2) id AA11969; Wed, 29 Sep 1993 18:03:19 +0200 Date: Wed, 29 Sep 1993 18:03:19 +0200 From: Hannu Martikka Message-Id: <199309291603.AA11969@cc.lut.fi> To: pine-info@cac.washington.edu Subject: pine 3.85 problems in hpux. Mailer: VM 5.35 (beta) / GNU Emacs 19.19.2 Reply-To: Hannu Martikka Organization: Lappeenranta University of Technology, Finland 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 Wed Sep 29 09:38:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07270; Wed, 29 Sep 93 09:38:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03584; Wed, 29 Sep 93 09:09:56 -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 AA03578; Wed, 29 Sep 93 09:09:54 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23566; Wed, 29 Sep 93 09:09:48 -0700 Date: Wed, 29 Sep 1993 09:07:05 -0700 (PDT) From: David L Miller Subject: Re: Unknown text "IBM437" To: James Dryfoos- Postmaster Cc: pine-info@cac.washington.edu In-Reply-To: <01H3IPOLLFKK0004WY@mc.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The latest (3.85) version of Pine will go ahead and display the message with a warning. Since IBM437 is not part of the MIME standard, we would strongly suggest that this behavior be changed if at all possible. |\ | |\/| 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, James Dryfoos- Postmaster wrote: > Is it possible to get Pine to deal with: > > [Part 1, "Text_1" Unknown text "IBM437" 3 lines] > [Can not display this part. Use the "A" command to save in a file] > > We are bringing up a PMDF/cc:Mail gateway that apparently puts text into this > charset. > > -- Jim From owner-pine-info@cac.washington.edu Wed Sep 29 10:02:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08477; Wed, 29 Sep 93 10:02:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04448; Wed, 29 Sep 93 09:49:50 -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 AA04442; Wed, 29 Sep 93 09:49:48 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA04530; Wed, 29 Sep 93 09:49:45 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA03801; Wed, 29 Sep 93 09:49:46 PDT Received: from develop by develop.Law.USC.EDU (4.1/SMI-4.1) id AA12026; Wed, 29 Sep 93 09:49:45 PDT Date: Wed, 29 Sep 1993 09:41:45 -0700 (PDT) From: Elmar Kurgpold Reply-To: Elmar Kurgpold Subject: Error messages on startup with IMAP... To: 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 1) I am getting the following errors after typing the username and password and before I enter the index. I thought it was an indication of junk in my .addressbook, but it is not. The messages go away as soon as I hit a key to go into the index. ...first... [{develop}inbox : [PARSE] Must use comma to separate addresses: faculty;@faculty] ...and then... [{develop}inbox : [PARSE] Junk at end of address: ::"ekurgpol@law.usc.edu"@sutr>] 2) Why isn't there a way to move one word backwards at time? In other words, the opposite of ^[SPACE] ? And by the way, thanks for the feature! 3) While I'm at it, if someone wants to save me some time and tell me if there is an option to disable the bell in pine, that would be nice. ------------------------------------- | 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 Sep 29 10:07:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08893; Wed, 29 Sep 93 10:07:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04597; Wed, 29 Sep 93 09:55: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 AA04588; Wed, 29 Sep 93 09:55:04 -0700 Received: from tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu by welchgate.welch.jhu.edu (4.1/1.34) id AA11410; Wed, 29 Sep 93 12:52:59 EDT Received: by tomahawk.welch.jhu.edu.tomahawk.welch.jhu.edu (5.0/SMI-SVR4) id AA10334; Wed, 29 Sep 93 12:53:22 EDT Date: Wed, 29 Sep 1993 12:53:11 -0400 (EST) From: Keith Christopher Subject: Re: Compiling Pine3.85 using GCC 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 Content-Length: 2288 I will try and see what I come up with. Keith Christopher Welch Medical Library Unix System Adminstrator On Mon, 27 Sep 1993, David L Miller wrote: > > I took a stab at making Pine 3.85 compile with GCC 2.4.5 under Solaris, but > didn't get very far before time ran out. If you get it working, we would be > happy to include your changes though... > > |\ | |\/| 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, 27 Sep 1993, Keith Christopher wrote: > > > under solaris2.2, > > > > here's the error: > > > > > > ddrbook.c: In function `addr_book': > > addrbook.c:845: `h_use_address_book' undeclared (first use this function) > > addrbook.c:845: (Each undeclared identifier is reported only once > > addrbook.c:845: for each function it appears in.) > > addrbook.c:847: `h_address_book' undeclared (first use this function) > > addrbook.c: In function `add_add': > > addrbook.c:1759: `h_oe_add_addr' undeclared (first use this function) > > addrbook.c:1787: `h_oe_add_nick' undeclared (first use this function) > > addrbook.c: In function `create_list': > > addrbook.c:1923: `h_oe_crlst_full' undeclared (first use this function) > > addrbook.c:1944: `h_oe_crlst_nick' undeclared (first use this function) > > addrbook.c:1991: `h_oe_crlst_addr' undeclared (first use this function) > > addrbook.c: In function `addr_to_list': > > addrbook.c:2108: `h_oe_adlst_addr' undeclared (first use this function) > > addrbook.c: In function `change_address_entry': > > addrbook.c:2195: `h_oe_editab_nick' undeclared (first use this function) > > addrbook.c:2251: `h_oe_editab_full' undeclared (first use this function) > > addrbook.c:2274: `h_oe_editab_addr' undeclared (first use this function) > > addrbook.c:2322: `h_oe_editab_al' undeclared (first use this function) > > addrbook.c: In function `search_book': > > addrbook.c:2396: `h_oe_searchab' undeclared (first use this function) > > *** Error code 1 > > make: Fatal error: Command failed for target `addrbook.o' > > > > > > > > Keith Christopher > > Welch Medical Library > > Unix System Adminstrator > > > > > From owner-pine-info@cac.washington.edu Wed Sep 29 10:09:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08980; Wed, 29 Sep 93 10:09:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04229; Wed, 29 Sep 93 09:37: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 AA04223; Wed, 29 Sep 93 09:37:52 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24237; Wed, 29 Sep 93 09:37:45 -0700 Date: Wed, 29 Sep 1993 09:37:13 -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 Do other variables get copied from pine.conf? |\ | |\/| 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 Wed Sep 29 10:14:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09225; Wed, 29 Sep 93 10:14:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04440; Wed, 29 Sep 93 09:49:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from flipper.pvv.unit.no by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04434; Wed, 29 Sep 93 09:49:44 -0700 Received: by flipper.pvv.unit.no id AA15064 (5.65c8/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 29 Sep 1993 17:48:52 +0100 From: Arnt Gulbrandsen Message-Id: <199309291648.AA15064@flipper.pvv.unit.no> Subject: Re: Unknown text "IBM437" To: pine-info@cac.washington.edu Date: Wed, 29 Sep 1993 17:48:51 +0100 (MET) In-Reply-To: <01H3IPOLLFKK0004WY@mc.duke.edu> from "James Dryfoos- Postmaster" at Sep 29, 93 11:46:05 am X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 731 X-Charset: ASCII X-Char-Esc: 29 > Is it possible to get Pine to deal with: > > [Part 1, "Text_1" Unknown text "IBM437" 3 lines] > [Can not display this part. Use the "A" command to save in a file] > > We are bringing up a PMDF/cc:Mail gateway that apparently puts text into this > charset. It is possible, but the right thing to do is to make the gateway use MIME as the RFCs say. Code page 437 is not a MIME character set, and only boneheads think every other machine should support machine X's character set - even if it's a sane charater set, and code page 437 is isn't: It can do some very naughty things if a 7-bit program uses it. Sorry I'm grumpy, I'm too tired and anyway that gateway deserves flamage. -- Arnt Gulbrandsen agulbra@pvv.unit.no From owner-pine-info@cac.washington.edu Wed Sep 29 11:53:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14169; Wed, 29 Sep 93 11:53:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27004; Wed, 29 Sep 93 11:39: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 AA26998; Wed, 29 Sep 93 11:39:13 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA09825; Wed, 29 Sep 93 11:39:03 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA26605; Wed, 29 Sep 93 11:38:55 -0700 Date: Wed, 29 Sep 1993 11:25:35 -0700 (PDT) From: Mark Crispin Subject: re: Error messages on startup with IMAP... To: Elmar Kurgpold Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII These [PARSE] messages are routine. They do not indicate any problems in your .addressbook or your configuration. They *do* indicate problems in the headers of one or more of the messages in your mailbox. Since there is no way anyone can control what sort of garbage gets deposited in your mailbox, it's pretty much routine to see [PARSE] messages. The sole purpose that these messages is that Pine's parser is alerting you to the fact that it saw something that was invalid under the RFC-822 or MIME standards. It's done some error recovery, which generally involves tossing out whatever confused it. When the offending message is displayed in Pine, the display may surprise you if you weren't alerted to the possibility of a problem. For example, To: All the Gang would probably show up as: To: All@Law.USC.EDU and a complaint generated about `` the Gang'' being a non-comma separated address. The [PARSE] token is a key to the Pine main program from the parser that it may want to suppress these messages as ``babble''. I don't think Pine keys on it yet. In the future, the parser will offer better communication to Pine so that the offending message can be flagged as having had a problem. Presently, it gives a set of [PARSE] messages without an indication of what caused it; the parser presently has no idea about ``message numbers'' and just parses strings that are spoon-fed to it. Of course, in a perfect world, people won't run mail programs that compose invalid RFC-822/MIME, and you would never see such messages. People who believe in perfect worlds also believe in UFOs, the Easter Bunny, and the triumphant arrival of the SS Titanic in New York Harbor.... :-) On Wed, 29 Sep 1993 09:41:45 -0700 (PDT), Elmar Kurgpold wrote: > 1) I am getting the following errors after typing the username and password > and > before I enter the index. I thought it was an indication of junk in my > .addressbook, but it is not. The messages go away as soon as I hit a key to > go > into the index. > > ...first... > [{develop}inbox : [PARSE] Must use comma to separate addresses: > faculty;@faculty] > ...and then... > [{develop}inbox : [PARSE] Junk at end of address: > ::"ekurgpol@law.usc.edu"@sutr>] From owner-pine-info@cac.washington.edu Wed Sep 29 12:18:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15178; Wed, 29 Sep 93 12:18:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27155; Wed, 29 Sep 93 12:07:51 -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 AA27149; Wed, 29 Sep 93 12:07:48 -0700 Received: by cc.lut.fi (5.65c/IDA-1.4.4/Kim-2.2) id AA18798; Wed, 29 Sep 1993 21:07:40 +0200 Date: Wed, 29 Sep 1993 21:07:40 +0200 From: Hannu Martikka Message-Id: <199309291907.AA18798@cc.lut.fi> To: David L Miller Cc: pine-info@cac.washington.edu Subject: Re: pine 3.85 problems in hpux. In-Reply-To: ; from David L Miller on 29 September 1993 09:37:13 -0700 References: <199309291603.AA11969@cc.lut.fi> Mailer: VM 5.35 (beta) / GNU Emacs 19.19.2 Reply-To: Hannu Martikka Organization: Lappeenranta University of Technology, Finland >>>>> "David" == David L Miller writes: David> Do other variables get copied from pine.conf? Yes, all other variables seem to be ok. - Goodi From owner-pine-info@cac.washington.edu Wed Sep 29 12:45:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16265; Wed, 29 Sep 93 12:45:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07701; Wed, 29 Sep 93 12:32:08 -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 AA07691; Wed, 29 Sep 93 12:32:04 -0700 Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-14 #1234) id <01H3H8R4UJE88WWAKL@INNOSOFT.COM>; Wed, 29 Sep 1993 12:31:05 PST Date: Wed, 29 Sep 1993 11:59:25 -0800 (PST) From: Ned Freed Subject: Re: fwd: from pine-info, bad mouthing us In-Reply-To: Your message dated "Wed, 29 Sep 1993 11:53:44 -0800 (PST)" <01H3IPW9K89E8WWG95@INNOSOFT.COM> To: agulbra@pvv.unit.no Cc: SERVICE@INNOSOFT.COM, pine-info@cac.washington.edu Message-Id: <01H3IR82RQW28WWAKL@INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > It is possible, but the right thing to do is to make the gateway use MIME > as the RFCs say. Code page 437 is not a MIME character set, and only > boneheads think every other machine should support machine X's character > set - even if it's a sane charater set, and code page 437 is isn't: It can > do some very naughty things if a 7-bit program uses it. I hate to have to be so heavy-handed here, but you're simply dead wrong on this. IBM437 is defined in RFC1345. That takes care of the sanity and definition issues completely. And all character sets in RFC1345 are registered for use in conjunction with MIME -- see RFC1340 for the *official* IANA list. I happen to think that registering absolutely all the charcter sets in RFC1345 was a mistake, since some of them are not adequately defined to be used in an interoperable fashion. But nobody asked me and IANA did in fact register them all for use with MIME. (If you think that IANA doesn't have the necessary authority you need to reread RFC1341 or RFC1521 for a reality check on this point.) IBM437 is one character set that is adequately defined, in my opinion. If you have a problem with this definition, you should be discussing it with the Keld Simonsen (author of RFC1345). You can do this either directly or you might want to consider the ietf-charsets working group (ietf-charsets-request@innosoft.com) for this purpose. I also think that releasing IBM437 stuff on the Internet is something to be avoided if at all possible. However, the gateway at issue contains very complete facilities for handling character set conversions and is quite capable of converting IBM437 into whatever character set is appropriate. This can be done seamlessly, efficiently, and automatically. The difficulty lies in picking an appropriate character set to convert IBM437 to: depending on local usage there are several possible character sets it might make sense to use as a target. (All things being equal I'd probably pick ISO-8859-1 myself.) Once you pick something setting up conversions is trivial -- the point is that the local administrator does have to pick something and configure accordingly. And in case you didn't notice, the administrator in question here is in the very early stages of both setting up the gateway *and* getting Pine going. It is therefore quite reasonable for him to ask about this in multiple forums to see what the best approach is. You should not assume that just because things are working in a particular way now that they will stay that way. But in the absence of proper configuration information the gateway has no choice but to operate in a loss-less and completely standards-compliant fashion, which in turn means that IBM437 stuff is produced. As for Pine's actions in this case, I have no problem with them either. A user agent should be able to pick and choose what character sets it supports, and if it wants to make it hard or impossible to use IBM437 directly that's fine. The issue here isn't one of standardized use versus nonstandardized use -- it is entirely within Pine's purview to do whatever it likes with the material presented to it, just as it is entirely within the gateway's purview to produce IBM437 character set labels. > Sorry I'm grumpy, I'm too tired and anyway that gateway deserves flamage. Grumpy or not, before you flame like this you need to learn to distinguish between what the standards actually say and what you'd like them to say. I don't particularly like what they say in this area either but that doesn't change matters. And while you're at it you might also want to consider the difference between bad design and bad initial configuration. Ned From owner-pine-info@cac.washington.edu Wed Sep 29 13:07:23 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17556; Wed, 29 Sep 93 13:07:23 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27438; Wed, 29 Sep 93 12:56:09 -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 AA27432; Wed, 29 Sep 93 12:56:07 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA09890; Wed, 29 Sep 93 12:55:51 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA26844; Wed, 29 Sep 93 12:55:38 -0700 Date: Wed, 29 Sep 1993 12:51:31 -0700 (PDT) From: Mark Crispin Subject: Re: fwd: from pine-info, bad mouthing us To: Ned Freed Cc: agulbra@pvv.unit.no, SERVICE@INNOSOFT.COM, pine-info@cac.washington.edu In-Reply-To: <01H3IR82RQW28WWAKL@INNOSOFT.COM> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Ned - Please enlighten me. I'll be the first to admit that I may be wrong, but here is how I see it: RFC-1345 character sets are undeniably listed in RFC-1340, and the IANA has undeniable authority to register MIME character sets. But I see nothing in RFC-1340 that indicates that RFC-1345 character sets are registered for use in MIME. In fact, I see an entirely separate list of character sets registered for MIME on the previous page of RFC-1340. As far as I know, RFC-1340 registers RFC-1345 character sets as registered character sets. I don't think that that says that they are registered MIME character sets, particularly as RFC-1340 has a separate list of registered MIME character sets. Damned if I know what use a list of registered character sets might have if it isn't for MIME, but that's how I interpret the situation. -- Mark -- From owner-pine-info@cac.washington.edu Wed Sep 29 13:19:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17921; Wed, 29 Sep 93 13:19:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08697; Wed, 29 Sep 93 13:08:28 -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 AA08691; Wed, 29 Sep 93 13:08:26 -0700 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24671; Wed, 29 Sep 93 13:08:18 -0700 Date: Wed, 29 Sep 1993 13:01:37 -0700 (PDT) From: Terry Gray Subject: Re: new incoming mail & PC-Pine To: "Stephen F. Day UNM MCCS" Cc: Pine Info , service@innosoft.com In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Stephen, We believe this to be a characteristic of the VMS (PMDF) IMAP server you are connecting to, but are CC'ing the folks at Innosoft for comment. (New mail notification is supported in UW's Unix IMAP server.) -teg On Fri, 24 Sep 1993, Stephen F. Day UNM MCCS wrote: > Okay... Have another question regarding PC-Pine. I've noted that > PC-Pine correctly picks up all new mail messages when I first fire up > PC-Pine. However, all new messages after that point are not picked up by > PC-Pine and I have to exit PC-Pine and re-enter PC-Pine to see these > newer messages. Surely there's an easier way to do this, isn't there? > > Thanks! > > Stephen From owner-pine-info@cac.washington.edu Wed Sep 29 13:23:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18075; Wed, 29 Sep 93 13:23:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08797; Wed, 29 Sep 93 13:13:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from medusa.unm.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08789; Wed, 29 Sep 93 13:13:18 -0700 Received: from [-127.24.128.129] (mccsmgr.unm.edu) by MEDUSA.UNM.EDU (PMDF V4.2-14 #5028) id <01H3IUSTKZ800007QQ@MEDUSA.UNM.EDU>; Wed, 29 Sep 1993 14:13:19 MDT Date: Wed, 29 Sep 1993 13:58:50 -0700 (PDT) From: "Stephen F. Day UNM MCCS" Subject: refreshing INBOX in PC-Pine To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Sender: sday@medusa.unm.edu Using PC-Pine 3.85 isn't bad, but I do have a few questions: 1. How do I get Pine to "re-fresh" the INBOX? What I mean is that new incoming mail that come in after I have fired up PC-Pine is not being seen unless I exit Pine altogether and then fire it up again. 2. What kind of encryption does PC-Pine use to send binaries? I note that I cannot accept all binaries sent to me -- so I want to know what my options are, and how to instruct others on how to encrypt their binaries to be sent to me. Thanks! =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Stephen F. Day (SFD7) AT&TNET: (505) 277-1698 Director BITNET/CREN: SDAY@MEDUSA Medical Ctr Computer Services INTERNET: sday@medusa.UNM.EDU University of New Mexico TECHNET: UNMSDAY =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-pine-info@cac.washington.edu Wed Sep 29 13:40:14 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19001; Wed, 29 Sep 93 13:40:14 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27705; Wed, 29 Sep 93 13:29: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 AA27699; Wed, 29 Sep 93 13:29:06 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA09913; Wed, 29 Sep 93 13:28:59 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA26944; Wed, 29 Sep 93 13:28:52 -0700 Date: Wed, 29 Sep 1993 13:25:11 -0700 (PDT) From: Mark Crispin Subject: re: refreshing INBOX in PC-Pine To: "Stephen F. Day UNM MCCS" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 29 Sep 1993 13:58:50 -0700 (PDT), Stephen F. Day UNM MCCS wrote: > 1. How do I get Pine to "re-fresh" the INBOX? What I mean is that new > incoming mail that come in after I have fired up PC-Pine is not being > seen unless I exit Pine altogether and then fire it up again. This is apparently only a problem if you are using Innosoft's VMS-based IMAP server. Other IMAP servers will automatically ``refresh'' without any action on your part. There is nothing that PC-Pine can do about this. Innosoft is aware of the problem in their software, but they don't have a solution yet. The only thing I can suggest is to set up a UNIX system as an IMAP server instead of VMS. > 2. What kind of encryption does PC-Pine use to send binaries? I note > that I cannot accept all binaries sent to me -- so I want to know what my > options are, and how to instruct others on how to encrypt their binaries > to be sent to me. PC-Pine does not use ``encryption'' per se. It uses the BASE64 encoding of the MIME Draft Standard (RFC-1521). So, you should be able to receive binaries sent from a MIME-compliant mailer. From owner-pine-info@cac.washington.edu Wed Sep 29 13:54:05 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19557; Wed, 29 Sep 93 13:54:05 -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 AA18066; Wed, 29 Sep 93 13:23:04 -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 AA18060; Wed, 29 Sep 93 13:23:01 -0700 Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08998; Wed, 29 Sep 93 13:22:55 -0700 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18600; Wed, 29 Sep 93 13:22:54 -0700 Reply-To: Terry Gray Message-Id: Date: Wed, 29 Sep 1993 13:21:04 -0700 (PDT) From: Terry Gray To: Pine Announcement Distribution Subject: Pine 3.85 Bug Status X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu Folks, We've learned of several problems in 3.85 that you should be aware of... 1. Backspace/delete in, or after, spell-checking a message sometimes makes the message evaporate, or turn into garbage, or Pine to crash. 2. The new meaning of the -i flag breaks some aliases. We will revert to old semantics of -i, and add -I for the new keystroke list. 3. Feature-list options in the global pine.conf file (e.g. enable-goto-cmd) are nullified by defining *any* feature-list entries in one's personal .pinerc. We will fix this by making global and personal feature lists additive, and will provide a way to negate globally-set features. 4. A message with a null To: field will cause Pine to crash. 5. The new "Can't delete open folder" policy is causing chagrin. We will revert to the old policy. All of these (and more!) will be fixed in 3.86... a maintenance release planned for next week. In the meantime, a diff for the -i command line conflict has already been posted to the pine-info list, and we expect to post a diff for the spell-check bug soon. As always, apologies for any difficulties these bugs may have caused. -teg p.s. As you all know by now :) the goto command was made optional in Pine 3.85, for the reasons mentioned in the release notes. We assumed, perhaps incorrectly, that the pine users who had discovered and come to love Goto in previous versions were typically power users, and a small percentage of the total population. We'd love to have feedback on whether the new (option-enabled) Goto is OK, or whether you would prefer to see it always enabled. From owner-pine-info@cac.washington.edu Wed Sep 29 14:28:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20993; Wed, 29 Sep 93 14:28:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28052; Wed, 29 Sep 93 14:14:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from SIGURD.INNOSOFT.COM by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28046; Wed, 29 Sep 93 14:14:37 -0700 Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V4.3-0 #1234) id <01H3ITRQLPM89AN1Q6@SIGURD.INNOSOFT.COM>; Wed, 29 Sep 1993 14:14:17 PDT Date: Wed, 29 Sep 1993 13:46:03 -0700 (PDT) From: Ned Freed Subject: RFC1340 and RFC1345 traumas In-Reply-To: Your message dated "Wed, 29 Sep 1993 12:51:31 -0700 (PDT)" To: Mark Crispin Cc: agulbra@pvv.unit.no, SERVICE@INNOSOFT.COM, pine-info@cac.washington.edu Message-Id: <01H3IUU0WOBO9AN1Q6@SIGURD.INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > Please enlighten me. I'll be the first to admit that I may be wrong, but > here is how I see it: > RFC-1345 character sets are undeniably listed in RFC-1340, and the IANA > has undeniable authority to register MIME character sets. > But I see nothing in RFC-1340 that indicates that RFC-1345 character sets > are registered for use in MIME. In fact, I see an entirely separate list of > character sets registered for MIME on the previous page of RFC-1340. If the character sets are not registered for use with MIME, what precisely are they registered for? You must answer this question before such an indication would be either necessary or meaningful. The only reasonable interpretation of the lack of any indication in the document as to the registration status as meaning everything has the same status. There is only one character set registry at present. This registry is for use with MIME. Nobody else has ever set one up -- there are plenty of things that might make use of a such a registry besides MIME, but to my knowledge none of them have done anything formal with IANA. As such, character sets are either registered or they are not -- they don't have a "status" associated with them and they don't have a "recommended use" associated with them. As a matter of fact, this is probably the wrong place to do this. Any registered character set should be legal for use in MIME. But MIME is being used for lots of things besides email now. What needs to happen is a profile of the proper character sets for use in MIME-based email (as opposed to netnews, local clipboard formats, world-wide-web, etc. etc. etc. which may need to make completely different choices). RFC1502 provides an example of a similar profile for the X.400 community -- read it and you'll find that they blew it in ways we never even dreamed of! > As far as I know, RFC-1340 registers RFC-1345 character sets as > registered character sets. I don't think that that says that they are > registered MIME character sets, particularly as RFC-1340 has a separate list > of registered MIME character sets. What is a "registered character set" if it isn't for use with MIME? The separation of the lists is an artefact of the separate sources involved as far as I can tell, and that's all it is. > Damned if I know what use a list of registered character sets might have > if it isn't for MIME, but that's how I interpret the situation. Precisely! And please note: I DO NOT LIKE ANY OF THIS THIS. I think it is terrible, confusing, and we have well and truly opened the pandora's box we tried so hard to contain in the IETF-822 working group. And it was done without our knowledge or consent and pretty much in direct contradiction to the consensus reached in the working group. But hating it and getting angry about it don't change it. What I am trying to do is pursue this through the means available to me -- the Character Set Working Group and the Application Area Directorate, and see if we cannot make some sense out of all this chaos. I must confess, however, that the current imbroglio involving MIME content subtype registration is a bigger concern of mine, and I'm spending much more time in that area than on character sets. Finally, it is vital to keep in mind that this all becomes moot once the gateway is properly configured. As such, this is all academic insofar as the present situation is concerned. Nevertheless, it is far from academic in that other software will undoubtedly start using character sets off the registered list, and is in fact entirely justified in doing so until and unless we get a email-specific profile in place. This is especially true since there are any number of people going around saying that not only is everything in RFC1340 of completely equal status, that therefore I should have every expectation of, say, T.61 working just as well as US-ASCII. Not! Ned From owner-pine-info@cac.washington.edu Wed Sep 29 15:07:02 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23409; Wed, 29 Sep 93 15:07:02 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11035; Wed, 29 Sep 93 14:50:14 -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 AA11028; Wed, 29 Sep 93 14:50:11 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03689; Wed, 29 Sep 93 14:50:10 -0700 Date: Wed, 29 Sep 1993 14:39:05 -0700 (PDT) From: Michael Seibel Reply-To: Michael Seibel Subject: spell check bug fix To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1506698872-749339410:#22617" --0-1506698872-749339410:#22617 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We've recently fixed a bug in pine's composer that could cause pine 3.85 to crash after spell-checking a composition. At best, the problem caused random junk to get appended to outgoing messages after a spell-check. Either way, it's quite annoying. Attached is a context diff for the fix that will be included in the upcoming pine 3.86 maintenance release. Apologies for any problems this bug may have caused! Michael Seibel Networks and Distributed Computing mikes@cac.washington.edu University of Washington, Seattle (206) 543 - 0359 --0-1506698872-749339410:#22617 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="spell.bug.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Bug fix for pico/line.c KioqIGxpbmUuYy5vbGQJV2VkIEp1bCAgNyAxNzowMDo0MyAxOTkzCi0tLSBs aW5lLmMJV2VkIFNlcCAyOSAwOTo0NzowOSAxOTkzCioqKioqKioqKioqKioq KgoqKiogMSw1ICoqKioKICAjaWYJIWRlZmluZWQobGludCkgJiYgIWRlZmlu ZWQoRE9TKQohIHN0YXRpYyBjaGFyIHJjc2lkW10gPSAiJElkOiBsaW5lLmMs diA0LjMgMTk5My8wNy8wOCAwMDowMDoxMyBkbG0gRXhwICQiOwogICNlbmRp ZgogIC8qCiAgICogUHJvZ3JhbToJTGluZSBtYW5hZ2VtZW50IHJvdXRpbmVz Ci0tLSAxLDUgLS0tLQogICNpZgkhZGVmaW5lZChsaW50KSAmJiAhZGVmaW5l ZChET1MpCiEgc3RhdGljIGNoYXIgcmNzaWRbXSA9ICIkSWQ6IGxpbmUuYyx2 IDQuNCAxOTkzLzA5LzI5IDE2OjQ2OjQ1IG1pa2VzIEV4cCAkIjsKICAjZW5k aWYKICAvKgogICAqIFByb2dyYW06CUxpbmUgbWFuYWdlbWVudCByb3V0aW5l cwoqKioqKioqKioqKioqKioKKioqIDQ1NCw0NjQgKioqKgotLS0gNDU0LDQ3 MiAtLS0tCiAgCQlpZiAod3AtPndfZG90byA8IGRvdG8pCiAgCQkgIHdwLT53 X2RvdG8gPSBkb3RvOwogIAkgICAgfQorIAogIAkgICAgaWYgKHdwLT53X21h cmtwPT1kb3RwICYmIHdwLT53X21hcmtvPj1kb3RvKSB7CiAgCQl3cC0+d19t YXJrbyAtPSBjaHVuazsKICAJCWlmICh3cC0+d19tYXJrbyA8IGRvdG8pCiAg CQkgIHdwLT53X21hcmtvID0gZG90bzsKICAJICAgIH0KKyAKKyAJICAgIGlm ICh3cC0+d19pbWFya3A9PWRvdHAgJiYgd3AtPndfaW1hcmtvPj1kb3RvKSB7 CisgCQl3cC0+d19pbWFya28gLT0gY2h1bms7CisgCQlpZiAod3AtPndfaW1h cmtvIDwgZG90bykKKyAJCSAgd3AtPndfaW1hcmtvID0gZG90bzsKKyAJICAg IH0KKyAKICAJICAgIHdwID0gd3AtPndfd25kcDsKICAJfQogIAluIC09IGNo dW5rOwo= --0-1506698872-749339410:#22617-- From owner-pine-info@cac.washington.edu Wed Sep 29 15:10:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23518; Wed, 29 Sep 93 15:10:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28333; Wed, 29 Sep 93 14:59:01 -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 AA28327; Wed, 29 Sep 93 14:58:46 -0700 Received: by digi.syd.deg.csiro.au id AA04711 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 30 Sep 1993 08:00:03 +1000 Date: Thu, 30 Sep 1993 07:57:28 +1000 (EST) From: Jack Churchill Subject: Re: Unknown text "IBM437" To: James Dryfoos- Postmaster Cc: pine-info@cac.washington.edu In-Reply-To: <01H3IPOLLFKK0004WY@mc.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 29 Sep 1993, James Dryfoos- Postmaster wrote: > Is it possible to get Pine to deal with: > > [Part 1, "Text_1" Unknown text "IBM437" 3 lines] > [Can not display this part. Use the "A" command to save in a file] > > We are bringing up a PMDF/cc:Mail gateway that apparently puts text into this > charset. I don't think IBM437 is "MIME-compliant". I'd fix the problem at the source and use PMDF's character conversion channel to modify the character set on the fly - unless it disturbs your cc:mail users. 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 Thu Sep 30 02:39:28 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11627; Thu, 30 Sep 93 02:39:28 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05154; Thu, 30 Sep 93 02:27:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05144; Thu, 30 Sep 93 02:27:10 -0700 Received: from vax.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <07287-0@oxmail.ox.ac.uk>; Thu, 30 Sep 1993 10:26:56 +0100 Received: by vax.ox.ac.uk (MX V3.3 VAX) id 2975; Thu, 30 Sep 1993 10:26:51 +0100 Date: Thu, 30 Sep 1993 10:26:47 +0100 From: NEIL J LONG To: PINE-INFO@CAC.WASHINGTON.EDU Cc: long@vax.ox.ac.uk Message-Id: <00973504.C43FEB84.2975@vax.ox.ac.uk> Subject: Extracting 'dead' attachments Hello 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. Thanks Neil From owner-pine-info@cac.washington.edu Thu Sep 30 03:54:40 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13077; Thu, 30 Sep 93 03:54:40 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01886; Thu, 30 Sep 93 03:23:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from flipper.pvv.unit.no by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01880; Thu, 30 Sep 93 03:23:54 -0700 Received: by flipper.pvv.unit.no id AA23092 (5.65c8/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 30 Sep 1993 11:23:01 +0100 From: Arnt Gulbrandsen Message-Id: <199309301023.AA23092@flipper.pvv.unit.no> Subject: MIME character sets, and an apology To: pine-info@cac.washington.edu Date: Thu, 30 Sep 1993 11:23:00 +0100 (MET) X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3088 X-Charset: ASCII X-Char-Esc: 29 Of course I regret what I yesterday - my brain is awake now and properly functioning. I'd like to apologise, and to quote some RFCs: RFC1341, on character set use in MINE: NOTE: Beyond US-ASCII, an enormous proliferation of character sets is possible. It is the opinion of the IETF working group that a large number of character sets is NOT a good thing. We would prefer to specify a single character set that can be used universally for representing all of the world's languages in electronic mail. Unfortunately, existing practice in several communities seems to point to the continued use of multiple character sets in the near future. For this reason, we define names for a small number of character sets for which a strong constituent base exists. It is our hope that ISO 10646 or some other effort will eventually define a single world character set which can then be specified for use in Internet mail, but in the advance of that definition we cannot specify the use of ISO 10646, Unicode, or any other character set whose definition is, as of this writing, incomplete. The defined charset values are: US-ASCII -- as defined in [US-ASCII]. ISO-8859-X -- where "X" is to be replaced, as necessary, for the parts of ISO-8859 [ISO- 8859]. Note that the ISO 646 character sets have deliberately been omitted in favor of their 8859 replacements, which are the designated character sets for Internet mail. As of the publication of this document, the legitimate values for "X" are the digits 1 through 9. Note that the character set used, if anything other than US-ASCII, must always be explicitly specified in the Content-Type field. No other character set name may be used in Internet mail without the publication of a formal specification and its registration with IANA as described in Appendix F, or by private agreement, in which case the character set name must begin with "X-". Implementors are discouraged from defining new character sets for mail use unless absolutely necessary. RFC1345, about itself: Status of the Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Summary This memo lists a selection of characters and their presence in some coded character sets. So I apologise for tone, but I'm not sure whether I should apologise for the content of my message. -- Arnt Gulbrandsen agulbra@pvv.unit.no From owner-pine-info@cac.washington.edu Thu Sep 30 08:06:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17727; Thu, 30 Sep 93 08:06:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07622; Thu, 30 Sep 93 07:52:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from medusa.unm.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07616; Thu, 30 Sep 93 07:52:05 -0700 Received: from MEDUSA.UNM.EDU by MEDUSA.UNM.EDU (PMDF V4.2-14 #5028) id <01H3JXCK9RLC00081K@MEDUSA.UNM.EDU>; Thu, 30 Sep 1993 08:52:00 MDT Date: Thu, 30 Sep 1993 08:38:25 -0600 (MDT) From: "Stephen F. Day [Med Ctr Comp Svcs]" Subject: Re: Extracting 'dead' attachments In-Reply-To: Your message dated "Thu, 30 Sep 1993 10:26:47 +0100" <00973504.C43FEB84.2975@vax.ox.ac.uk> To: NEIL J LONG Cc: pine-info@cac.washington.edu, "Stephen F. Day [Med Ctr Comp Svcs]" Message-Id: <01H3JXUT48QS00081K@MEDUSA.UNM.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT >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. PMDF also provides a IMAP2 server; however, there is a small glitch in its IMAP services -- while in Pine, it doesn't concurrently update your 'inbox' for new mail messages. You must exit and re-enter Pine to read new NEWMAIL -- which sort of makes DIR/NEW comparatively more attractive. :-{ I am happy with PMDF, but like everything else -- there's always room for improvment! :-) I should add that if you are within a university setting, their educational rates are fairly reasonable and affordable (however, I don't know how this would translate outside the U.S.). >Neil =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Stephen F. Day (SFD7) AT&TNET: (505) 277-1698 Director BITNET/CREN: SDAY@MEDUSA Medical Ctr Computer Services INTERNET: sday@medusa.UNM.EDU University of New Mexico TECHNET: UNMSDAY =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-pine-info@cac.washington.edu Thu Sep 30 09:51:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21904; Thu, 30 Sep 93 09:51:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09516; Thu, 30 Sep 93 09:26:37 -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 AA09508; Thu, 30 Sep 93 09:26:35 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA12512 (5.65b/IDA-1.4.3 for pine-info@cac.washington.edu); Thu, 30 Sep 93 11:26:33 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA20328; Thu, 30 Sep 93 11:26:33 CDT Date: Thu, 30 Sep 1993 11:24:54 -0500 (CDT) From: Matt Simmons Subject: pine editor "feature" To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When you mark text for deletion, and hit ctrl-x, the editing mark will be lost and pine or pico will exit.. Could this be changed so that when you mark something and (inadvertantly) hit an exit key, it'll say something to the effect of "You have marked text, exiting will remove the mark, blah blah blah Are you sure you want to?" || || || | | | | | | zarthac |/ \|| |_|--|_/"\ @ | | ||/"\| |= |_|__||===| cs1 | \\__|_\ / | || | || bradley |= /\ || | || | ||##| || | || edu /"\ | | || | || ||AA| | |/\| | || | || ||: | | | |--| || |/\|/\| ||__|,'`. |++| / \ | ||| | |= | /____\ |++|/ ===|||=== | |----|__|----------\ \ / / /\ | | |----------| | | |/ \ .---+ \/:::::::::::| | |+|-.-.-, \ | | | | ||| | ||"| | + + | | |"| | ,' `.| |####| | | ,' `. | /_____\ / == \| | /_____\ | |___| | / /\ \ | |___|==== /_____\ |/__|/()\|__\| /_____\ | |_____|--| |/--\| |--|_____| | \:::/---| | | |---\|_|/ | | | | | | | | | | | |::::| | | | | | | | | | | | | | | | ____ | _____------------____| | __------_ --- -------- Cinderella's Castle From owner-pine-info@cac.washington.edu Thu Sep 30 10:11:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22640; Thu, 30 Sep 93 10:11:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10004; Thu, 30 Sep 93 09:55:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from minnie.bell.inmet.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09996; Thu, 30 Sep 93 09:55:52 -0700 Received: by minnie.bell.inmet.com (4.1/SMI-4.1) id AA08337; Thu, 30 Sep 93 09:58:57 PDT Date: Thu, 30 Sep 1993 09:52:58 -0700 (PDT) From: Paul Tarr Subject: Attachment Viewing To: pine-info@cac.washington.edu Cc: Paul Tarr Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Thu Sep 30 10:29:27 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24324; Thu, 30 Sep 93 10:29:27 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10271; Thu, 30 Sep 93 10:10:50 -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 AA10265; Thu, 30 Sep 93 10:10:49 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23443; Thu, 30 Sep 93 10:10:35 -0700 Date: Thu, 30 Sep 1993 10:08:05 -0700 (PDT) From: David L Miller Subject: Re: pine editor "feature" 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 Hmmm... You mean you want even more prompts?!?!? ;) |\ | |\/| 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, Matt Simmons wrote: > When you mark text for deletion, and hit ctrl-x, the editing mark will be > lost and pine or pico will exit.. Could this be changed so that when you > mark something and (inadvertantly) hit an exit key, it'll say something > to the effect of "You have marked text, exiting will remove the mark, > blah blah blah Are you sure you want to?" > > || > || > || > | | | > | | | zarthac > |/ \|| > |_|--|_/"\ @ > | | ||/"\| > |= |_|__||===| cs1 > | \\__|_\ / > | || | || bradley > |= /\ || | || > | ||##| || | || edu > /"\ | | || | || > ||AA| | |/\| | || | || > ||: | | | |--| || |/\|/\| > ||__|,'`. |++| / \ | ||| | |= > | /____\ |++|/ ===|||=== | > |----|__|----------\ \ / / /\ > | | |----------| | | |/ \ > .---+ \/:::::::::::| | |+|-.-.-, > \ | | | | ||| | > ||"| | + + | | |"| | > ,' `.| |####| | | ,' `. | > /_____\ / == \| | /_____\ | > |___| | / /\ \ | |___|==== > /_____\ |/__|/()\|__\| /_____\ | > |_____|--| |/--\| |--|_____| | > \:::/---| | | |---\|_|/ | > | | | | | | | | | > | |::::| | | | | | | > | | | | | | | | | > ____ | _____------------____| | __------_ > --- -------- > > Cinderella's Castle > > > From owner-pine-info@cac.washington.edu Thu Sep 30 10:46:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25209; Thu, 30 Sep 93 10:46:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10566; Thu, 30 Sep 93 10:22:17 -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 AA10560; Thu, 30 Sep 93 10:22:15 -0700 Received: by watsun.cc.columbia.edu (5.59/FCB/jba) id AA23057; Thu, 30 Sep 93 13:22:13 EDT Date: Thu, 30 Sep 1993 13:17:43 -0400 (EDT) From: Joseph Brennan Subject: re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 install a standard 3.85 I'd be happy. Joseph Brennan Academic Information Systems Columbia University in the City of New York brennan@columbia.edu From owner-pine-info@cac.washington.edu Thu Sep 30 10:46:48 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25219; Thu, 30 Sep 93 10:46:48 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03782; Thu, 30 Sep 93 10:24:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bart.meiko.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03776; Thu, 30 Sep 93 10:24:44 -0700 Received: by bart.meiko.com id AA06950 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 30 Sep 1993 13:24:41 -0400 Date: Thu, 30 Sep 1993 13:16:45 -0400 (EDT) From: Mike Stok Subject: Good Windows Terminal Emulator? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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... I don't have a PC to hand, and the user is connected via a 2400bps modem to a service which eventually sprouts him into my computer as a telnet connection. He is emulating a VT100, any helpful hints about how to get a pine message printed to a file on his PC would be able to get captured to a file or sent to the normal Windows printing system. Sorry if this is more of a Windows than Pine question, 3.85 is pretty neat, 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 Sep 30 11:22:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26926; Thu, 30 Sep 93 11:22:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11344; Thu, 30 Sep 93 10:52:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from rush.wustl.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11336; Thu, 30 Sep 93 10:52:31 -0700 Received: by rush.wustl.edu (5.0/SMI-SVR4) id AA07870; Thu, 30 Sep 93 12:52:05 CDT Date: Thu, 30 Sep 1993 12:49:41 -0500 (CDT) From: Chris Dunphy Subject: Pine bug! To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 226 Pine will let you send mail with no "to:" field, causing bad things to happen and postmaster to get mail. Is there a way to make pine check to be sure there is a non-null to: field before sending mail? Chris Dunphy From owner-pine-info@cac.washington.edu Thu Sep 30 11:19:07 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26610; Thu, 30 Sep 93 11:19:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bishop.bishop.Hawaii.Org by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26601; Thu, 30 Sep 93 11:19:01 -0700 From: edwardy@bishop.bishop.hawaii.org Received: by bishop.bishop.hawaii.org (AIX 3.2/UCB 5.64/4.03) id AA30480; Thu, 30 Sep 1993 08:14:38 -1000 Date: Thu, 30 Sep 1993 08:04:05 +22305714 (HST) Subject: Re: Good Windows Terminal Emulator? To: Mike Stok Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 30 Sep 1993, Mike Stok wrote: > I don't have a PC to hand, and the user is connected via a 2400bps modem > to a service which eventually sprouts him into my computer as a telnet > connection. He is emulating a VT100, any helpful hints about how to get > a pine message printed to a file on his PC would be able to get captured > to a file or sent to the normal Windows printing system. I was just recently working on this problem. Im not too sure about the software you are using, but if it is a VT100 emulator on a PC I was successful in printing files directly to the printer by sending an escape sequence to pipe it to lpt1 and then sending another to stop it. Here is the program: dosprint echo 'Printing.. Please wait.' pr -f -l64 $1 > ~/.prx echo '[5i' cat ~/.prx echo '[4i' \rm ~/.prx (replace with the escape key) Its not elegant, and I couldve probably piped the pr through the cat, but this works for DOS machines. I tested it on PCs running Procomm via asynch and also on LanWorkPlace for DOS's tnvt220 via ethernet and was successful in printing it to lasers/dotmatrix/deskwriters. (you can change the pr parameters to your preference) As far as printing directly to a file, I havent tried this yet, but there are utility programs out there (wuarchive?) that redirects anything sent to lpt1 to a file. Course, that would mean starting that utility BEFORE you enter your comm program and that EVERYTHING sent to the printer would be sent to that file. > -- > 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 > > ____Edward_K_Yagi_____________________________________________________________ edwardy@bishop.bishop.hawaii.org Bishop Museum Computer Dept - ,o. edwardy@uhunix.bitnet Phone#847-8238 FAX 842-1329 - O7 O ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Thu Sep 30 12:36:53 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01421; Thu, 30 Sep 93 12:36:53 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04281; Thu, 30 Sep 93 11:37:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from xanth.CS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04275; Thu, 30 Sep 93 11:37:45 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA22667; Thu, 30 Sep 93 11:38:31 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA20733; Thu, 30 Sep 93 11:40:39 -0700 Date: Thu, 30 Sep 1993 11:39:40 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Good Windows Terminal Emulator? To: Mike Stok Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Thu Sep 30 13:17:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03454; Thu, 30 Sep 93 13:17:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13615; Thu, 30 Sep 93 12:31:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from medusa.unm.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13606; Thu, 30 Sep 93 12:31:36 -0700 Received: from MEDUSA.UNM.EDU by MEDUSA.UNM.EDU (PMDF V4.2-14 #5028) id <01H3K7ACS5HC00081K@MEDUSA.UNM.EDU>; Thu, 30 Sep 1993 13:31:43 MDT Date: Thu, 30 Sep 1993 13:24:44 -0600 (MDT) From: "Stephen F. Day [Med Ctr Comp Svcs]" Subject: RE: Good Windows Terminal Emulator? In-Reply-To: Your message To: Mike Stok Cc: pine-info@cac.washington.edu, "Stephen F. Day [Med Ctr Comp Svcs]" Message-Id: <01H3K7MLGXTG00081K@MEDUSA.UNM.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Thu, 30 Sep 1993, Mike Stok wrote: > I don't have a PC to hand, and the user is connected via a 2400bps modem > to a service which eventually sprouts him into my computer as a telnet > connection. He is emulating a VT100, any helpful hints about how to get > a pine message printed to a file on his PC would be able to get captured > to a file or sent to the normal Windows printing system. You didn't indicate which operating system you were using, so I thought I would provide a VMS solution as well: $ v = f$verify(0) ! PCPRINT.COM $! $! Print VMS files on the printer that is attached to your VT102, $! VT200, or VT300, or PC with MS-DOS Kermit or other VT terminal $! emulator that supports the "transparent print" function. $! $! Author: Mark Buda $! $! Usage: $! pcprint :== @sys$login:pcprint.com $! pcprint file.ext [,...] $! $ print_in_progress = 0 $ type := type $ write := write $ say := write sys$output $ sayerr := write sys$error $ ff[0,8] = 12 $ esc[0,8] = 27 $ rp_on = esc + "[5i" ! Remote printer "ON" sequence $ rp_off = esc + "[4i" ! Remote printer "OFF" sequence $! $ on error then goto exit_pcprint $ on control_y then goto ctly_exit $! $ file = p1 $check_file: $ file = f$edit(file,"collapse") $! if file .eqs. "" $! then $! read/prompt="_Filename: "/end_of_file=exit_pcprint sys$command file $! goto check_file $! endif $ if file .nes. "" then goto search_for_file $ read/prompt="_Filename: "/end_of_file=exit_pcprint sys$command file $ goto check_file $ search_for_file: $ f = f$search(file) $! if f .eqs. "" $! then $! sayerr "%PCPRINT-F-FNF, File not found - ''file'" $! goto exit_pcprint $! endif $ if f .nes. "" then goto file_is_found $ sayerr "%PCPRINT-F-FNF, File not found - ''file'" $ goto exit_pcprint $ file_is_found: $ say rp_on $ print_in_progress = 1 $ type 'file' $ print_in_progress = 0 $ say ff $ goto exit_pcprint $! $ctly_exit: $ if print_in_progress then say ff $ goto exit_pcprint $! $exit_pcprint: $ say rp_off $ v = f$verify(v) $ exit =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Stephen F. Day (SFD7) AT&TNET: (505) 277-1698 Director BITNET/CREN: SDAY@MEDUSA Medical Ctr Computer Services INTERNET: sday@medusa.UNM.EDU University of New Mexico TECHNET: UNMSDAY =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-pine-info@cac.washington.edu Thu Sep 30 13:17:45 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03498; Thu, 30 Sep 93 13:17:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04623; Thu, 30 Sep 93 12:30:39 -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 AA04617; Thu, 30 Sep 93 12:30:37 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA11909; Thu, 30 Sep 93 12:30:27 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA01338; Thu, 30 Sep 93 12:30:20 -0700 Date: Thu, 30 Sep 1993 12:10:32 -0700 (PDT) From: Mark Crispin Subject: re: ^J <=> ^M confusion with Pico (1.6, 2.0) on NeXTSTEP 2.1 To: Joseph Brennan Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII 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 install > a standard 3.85 I'd be happy. Hi - I share your frustration with this problem, being someone who personally experiences it daily. Fortunately, there are several forms of attack to this problem: Attack #1: Avoid CTRL/J in Pine and Pico as you have done. Pros: Fixes it in Pine. Cons: Doesn't solve the general problem. Attack #2: In your NCSA config.tel file, add the line crmap=4.3BSDCRNUL # map return key to CR/NUL instead of CR/LF Pros: The official BSD UNIX hacker's workaround. Works for all systems which have the broken BSD telnetd, and doesn't require cooperation on the part of those systems to fix it. Cons: A dreadful kludge against the intent of newline handling in the Telnet protocol. You have to login in using CTRL/J instead of return (that is, I have to type mrc instead of mrc to the login: prompt, and ditto for the password prompt. Then RETURN works right). Attack #3: For NEXTSTEP 2.x and 3.0 *ONLY*, acquire a copy of vanilla BSD telnetd source (available from several sources) and rebuild telnetd. The broken version of telnetd distributed by NeXT is 5.45 (6/28/90). The fixed version is 5.48 (3/1/91) or later. A binary for 3.0 is on ftp.cac.washington.edu in the next/ directory. Pros: The correct fix for the bug. Cons: Can't do it on NEXTSTEP 3.1, for unknown reasons. Attack #4: It is claimed by reliable sources that ``stty -extproc'' in the user's .login file will work around this problem as well. Pros: Works with NEXTSTEP 3.1 Cons: I haven't personally verified to see if there are any undesirable side effects. There are other strategies, but the four that I've listed above are likely to be the only productive ones. On the other hand, bopping certain vendors on the head with a sledgehammer on the head *is* emotionally satisfying after experiencing this infuriating bug... -- Mark -- From owner-pine-info@cac.washington.edu Thu Sep 30 15:01:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07626; Thu, 30 Sep 93 15:01:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16270; Thu, 30 Sep 93 14:38:41 -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 AA16264; Thu, 30 Sep 93 14:38:37 -0700 Received: from cs1.bradley.edu by bradley.bradley.edu with SMTP id AA02842 (5.65b/IDA-1.4.3 for dlm@cac.washington.edu); Thu, 30 Sep 93 16:38:36 -0500 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA27154; Thu, 30 Sep 93 16:38:35 CDT Date: Thu, 30 Sep 1993 16:35:51 -0500 (CDT) From: Matt Simmons Subject: Re: pine editor "feature" 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 On Thu, 30 Sep 1993, David L Miller wrote: > Hmmm... You mean you want even more prompts?!?!? ;) > On Thu, 30 Sep 1993, Matt Simmons wrote: > > When you mark text for deletion, and hit ctrl-x, the editing mark will be > > lost and pine or pico will exit.. Could this be changed so that when you > > mark something and (inadvertantly) hit an exit key, it'll say something > > to the effect of "You have marked text, exiting will remove the mark, > > blah blah blah Are you sure you want to?" Yeah, well... for idiots like me who hit ctrl-x instead of ctrl-k... Plus, this prompt wouldn't appear for mildly intelligent people (i.e. I'd see it alot).... It'd just appear if you screw up (or if you meant to mark something and leave, for whatever reason...) From owner-pine-info@cac.washington.edu Thu Sep 30 15:09:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08249; Thu, 30 Sep 93 15:09:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16387; Thu, 30 Sep 93 14:46:43 -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 AA16381; Thu, 30 Sep 93 14:46:40 -0700 Received: from tellus.csc.fi by csc.fi with SMTP id AA03148 (5.65c8+/IDA-1.4.4 for ); Thu, 30 Sep 1993 23:46:32 +0200 Received: from localhost.csc.fi by tellus.csc.fi (4.1/SMI-4.1) id AA26818; Thu, 30 Sep 93 23:45:16 +0200 Message-Id: <9309302145.AA26818@tellus.csc.fi> To: Mark Crispin Cc: Joseph Brennan , 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 "Thu, 30 Sep 1993 12:10:32 MST." Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 30 Sep 1993 23:45:16 +0200 From: Pekka Kytolaakso 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 ins= tall > > a standard 3.85 I'd be happy. > = > Hi - > = > I share your frustration with this problem, being someone who personally > experiences it daily. Fortunately, there are several forms of attack to= this > problem: > = > Attack #1: Avoid CTRL/J in Pine and Pico as you have done. > Pros: Fixes it in Pine. > Cons: Doesn't solve the general problem. I think this is the best. We have similar problems with SGI's xwsh terminal-program: when doing X cut&paste I either paste into xwsh or copy from xwsh and paste into xterm (or whatever) the pasted text has ^J as end-of-line character instead of ^M. This makes cut&past impossible to use with pine. > Attack #2: In your NCSA config.tel file, add the line > crmap=3D4.3BSDCRNUL # map return key to CR/NUL instead of CR/LF > Pros: The official BSD UNIX hacker's workaround. Works for all syste > ms > which have the broken BSD telnetd, and doesn't require cooperation on > the part of those systems to fix it. > Cons: A dreadful kludge against the intent of newline handling in the > Telnet > protocol. You have to login in using CTRL/J instead of return (that > is, I have to type mrc instead of mrc to the login: > prompt, and ditto for the password prompt. Then RETURN works right). > > Attack #3: For NEXTSTEP 2.x and 3.0 *ONLY*, acquire a copy of vanilla BS= D > telnetd source (available from several sources) and rebuild telnetd. > The broken version of telnetd distributed by NeXT is 5.45 (6/28/90). > The fixed version is 5.48 (3/1/91) or later. A binary for 3.0 is on > ftp.cac.washington.edu in the next/ directory. > Pros: The correct fix for the bug. > Cons: Can't do it on NEXTSTEP 3.1, for unknown reasons. > = > Attack #4: It is claimed by reliable sources that ``stty -extproc'' in t= he > user's .login file will work around this problem as well. > Pros: Works with NEXTSTEP 3.1 > Cons: I haven't personally verified to see if there are any undesirab > le > side effects. > = > There are other strategies, but the four that I've listed above are like= ly to > be the only productive ones. On the other hand, bopping certain vendors= on > the head with a sledgehammer on the head *is* emotionally satisfying aft= er > experiencing this infuriating bug... > = > -- Mark -- A way (hack :-) might be to add a configuration parameter (yes, one more) like = # fill-command defines the control chacter used to fill paragraphs # the default value is 11 (^J), 0 means fill no in use = fill-command=3D The problems with this are - screen-menu shows ^J as fill (runtime change) - help file has wrong key (must edit help-file) Neither of these are serious because when a user changes this he should now what the fill command is. 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 me= 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). 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 Thu Sep 30 15:15:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08384; Thu, 30 Sep 93 15:15:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16572; Thu, 30 Sep 93 14:57:22 -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 AA16564; Thu, 30 Sep 93 14:57:16 -0700 Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.2-14 #1234) id <01H3H8R4UJE88WWAKL@INNOSOFT.COM>; Thu, 30 Sep 1993 14:56:31 PST Date: Thu, 30 Sep 1993 14:08:17 -0800 (PST) From: Ned Freed Subject: Re: MIME character sets, and an apology In-Reply-To: Your message dated "Thu, 30 Sep 1993 12:20:39 -0800 (PST)" <01H3K55AU09E8WWH56@INNOSOFT.COM> To: pine-info@cac.washington.edu, Arnt Gulbrandsen Cc: NED@INNOSOFT.COM Message-Id: <01H3KALQ0HKW8WWAKL@INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > Of course I regret what I yesterday - my brain is awake now and properly > functioning. I'd like to apologise, and to quote some RFCs: > RFC1341, on character set use in MINE: > ... > RFC1345, about itself: > ... > This memo provides information for the Internet community. It does > not specify an Internet standard. Distribution of this memo is > unlimited. Let me take these points in reverse order and begin by repeating something I said in private mail: The fact that RFC1345 is informational is itself meaningless. There is no requirement that character sets designated for MIME use be described by standards-track documents. If anything, the intention is precisely the opposite -- a standards-track document defining character sets would effectively put the IETF in the character set business for itself. We (speaking as an IETF member here) do not want to be in this business! There are two many people defining character sets already! This is also borne out by actual RFCs as well. RFC1489 defines a Cyrillic character set, RFC1456 defines VISCII (for Vietnamese), and RFC1468 defines ISO-2022-JP (for Japanese). There are also at least four other documents of this sort that will be published as RFCs in the near future. These character sets are specifically intended for use with MIME and were/will be approved for such use at the time of their publication. And *all* of these documents are informational RFCs. RFC1345 differs in that it defins a mnemonic encoding as well as describing existing usage. But if anything its status is even more assured -- the character sets it documents are in the latest assigned numbers RFC: RFC1340! In the final analysis you really cannot have it both ways. Either publication as an informational RFC is sufficient or it is not. If it is RFC1345 defines character sets for use with MIME. If it is not none of the others (ISO-2022-JP, VISII, etc.) are allowed in MIME messages either. And if this is true why on earth were these documents published? Now let's return to the language in RFC1341, some of which I wrote. RFC1341 is, to put it in the most charitable terms possible, naive. I still believe that a proliferation of character sets is a bad thing. I still hope for the One True Character Set to come and rescue us all from all this character set dementia. But I've largely given up hope -- we've yet to satisfactorily determine how to transmit either ISO10646, let alone its BMP subset, in MIME, and even if we licked this problem today we'd still have issues with various communities whose needs are *not* met by ISO10646. However, regardless of how I feel we have to distinguish between fact and wishful thinking when it comes to labelling things as illegal. RFC1340 registered the RFC1345 character sets. You can argue that this was a bad idea (it was). You can argue that this was done contrary to the wishes of the IETF-822 working group (it was). You can argue that just because something is allowed is no reason to do it (it isn't). You can argue that we need to do something about it NOW (I've, along with John Klensin, have been trying for over a year). But the fact remains that an implementor, starting with the RFC index and without any other information, would rapidly come to the conclusion that RFC1340 contains the list of permitted character sets and that the ones in RFC1345 are legal. Making a case that usage out of RFC1345 is illegal requires a lot of twisting and turning that simply cannot be part of determining whether or not something is standards-compliant. My position here is an awkward one and I admit it. I freely admit that I don't approve of open use of IBM437 or any of the other character sets in RFC1345. But I cannot accept assertions that such usage is illegal. To do so would mean, among other things, that I think that the present situation is tolerable. And I don't think it is. I have also had second thoughts about what I said about Pine supporting or not supporting character sets outside of the list in RFC1341 (or RFC1521). Let me use a somewhat different example to make my point -- we've picked on poor old IBM437 enough now. I mostly use VMS machines. VMS machines use a character set called (in RFC1345 parlance) DEC-MCS. VT200 and VT300 terminals use DEC-MCS as their native character set as well. The mail utility on VMS, VMS MAIL, is quite popular. (We provide a replacement for it that works a lot better, but it would be foolish for me to think that VMS MAIL usage is disappearing because of this.) It provides native support for DEC-MCS and all messages are assumed to be in DEC-MCS. This leads to interesting issues when things like IMAP or POP servers and/or Pine clients are installed/served from a VMS machine. We commonly use a simple trick to eliminate most of the problems. DEC-MCS is quite close to ISO-8859-1: it has things like an OE-ligature while ISO-8859-1 doesn't, but there are only 8 differences of this sort. This means that most of the time pretending DEC-MCS is the same as ISO-8859-1 is an acceptable solution. We do this whenever and whereever it is feasible to do so. But there are sites where the 8 different characters do matter and where this trick won't work well enough to depend on. We cannot change the fact that people's mailboxes are in DEC-MCS format, so we convert incoming mail into this character set whenever it makes sense to do so. And of course we label the message accordingly. And when mail is sent off-site it is converted into ISO-8859-1 (or whatever is appropriate) as it goes out. But what does the IMAP server and the Pine client do? You get errors, that's what. So now we're back to the same set of issues -- should Pine have to deal with stuff like DEC-MCS directly? You say no, such usage is just as illegal in this case as it was with IBM437. But there's a very important difference here. This usage is entirely local. The usage on the network is completely in compliance with RFC1341. This is a local matter. And it is axiomatic that local matters are just that: local and not subject to standardization. (Getting POP and IMAP on the standards track was a major challenge because of this axiom. Only the fact that either one can be used on the real Internet made it possible to standardize these protocols.) One possible solution is for the IMAP server to do this conversion. (This is what we'll probably implement if need be.) But this involves information loss, and if the information loss was important enough to make labelling DEC-MCS as ISO-8859-1 infeasible, it probably means that converting to make Pine happy is not acceptable either. The point I'm trying to make here is that Pine, like any MUA, is subject to requirements and needs that lie outside the realm of standardization. For example, Pine and IMAP contains support to read UNIX mailboxes in a variety of different formats. You will not find these formats documented in any RFCs, nor will you find people arguing that because these formats are not documented in a standards-track RFC that Pine has no business supporting them. I am not arguing that Pine should support either IBM437 or DEC-MCS -- this is a bridge we'll cross when someone has a real need and documents that need. All I'm saying is that even if it were true that use of such character sets is illegal on the Internet, this would not in and of itself eliminate any chance of needing support for them in Pine. Ned From owner-pine-info@cac.washington.edu Thu Sep 30 16:25:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10502; Thu, 30 Sep 93 16:25:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17743; Thu, 30 Sep 93 16:11:49 -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 AA17735; Thu, 30 Sep 93 16:11:47 -0700 Received: by stein2.u.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09042; Thu, 30 Sep 93 16:11:44 -0700 X-Sender: mramey@stein2.u.washington.edu Date: Thu, 30 Sep 1993 16:09:18 -0700 (PDT) From: Mike Ramey Subject: newsgroup rather than mailing list ? To: Pine-Info Email List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Would it be useful to conduct the pine-info discussion on a newsgroup 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 From owner-pine-info@cac.washington.edu Thu Sep 30 16:41:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11002; Thu, 30 Sep 93 16:41:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05994; Thu, 30 Sep 93 16:20:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from SIGURD.INNOSOFT.COM by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05988; Thu, 30 Sep 93 16:20:49 -0700 Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V4.3-0 #1234) id <01H3KB15NJLS9AN313@SIGURD.INNOSOFT.COM>; Thu, 30 Sep 1993 16:20:20 PDT Date: Thu, 30 Sep 1993 16:11:29 -0700 (PDT) From: Ned Freed Subject: RE: MIME character sets, and an apology In-Reply-To: Your message dated "Thu, 30 Sep 1993 14:08:17 -0800 (PST)" <01H3KALQ0HKW8WWAKL@INNOSOFT.COM> To: Ned Freed Cc: pine-info@cac.washington.edu, Arnt Gulbrandsen , NED@INNOSOFT.COM Message-Id: <01H3KDINY2DK9AN313@SIGURD.INNOSOFT.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT One additional note. I Bcc'ed a bunch of this discussion to John Klensin, who is the co-director of the Application Area of the IETF/IESG. John is also the specific person who most often oversees character set issues in the IETF (poor guy!). Here is his response (extracted from a list of bullets sent in response to several things I'd asked him, but nevertheless quoted in its entirety): -- The 822 WG set up a registration procedure. I haven't been happy about the charset aspect of it from day 1, which clearly hasn't been a secret. But that procedure made it into a Proposed Standard, Keld followed it and registered a bunch of stuff with IANA. IANA followed it and accepted the registrations. So your users aren't using "something from 1345", they are using something from the IANA-maintained registration list, which is perfectly valid (however stupid it may also be). (John gave me permission to quote him as well.) Now, I suppose we could ask for a full IESG ruling on this issue, but it would only make a lot of busy people needlessly busier, and, assuming they would bother, would probably produce exactly the same opinion. In other words, this is as official as it is likely to get. Use of RFC1345 character sets in MIME messages is legal. Stupid, but legal. The only real issue here is how we want to deal with the unfortunate situation that's developed. Ned From owner-pine-info@cac.washington.edu Thu Sep 30 17:03:16 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11759; Thu, 30 Sep 93 17:03:16 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06105; Thu, 30 Sep 93 16:48:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from herald.usask.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06099; Thu, 30 Sep 93 16:48:04 -0700 Received: by herald.usask.ca (5.65/DEC-Ultrix/4.3) id AA19990; Thu, 30 Sep 1993 17:48:02 -0600 for pine-info@cac.washington.edu Date: Thu, 30 Sep 1993 17:41:34 -0600 (CST) From: "Darryl Friesen (4758)" Subject: Re: newsgroup rather than mailing list ? To: pine-info@cac.washington.edu 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?) 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 It would also, in my opinion, be a better place for discussion on topics such as the recent character sets/standards thread. While interesting to some, this line of discussion, in its present form, doesn't relate directly to pine (the first couple of messages did), and tends to fill the inbox rather quickly. Just my $0.02 worth. - Darryl ------------------------------------------------------------ Darryl Friesen | friesenda@sask.usask.ca Client Services | Darryl.Friesen@usask.ca Dept of Computing Services | University of Saskatchewan | "Team OS/2" ------------------------------------------------------------ From owner-pine-info@cac.washington.edu Thu Sep 30 17:48:48 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13731; Thu, 30 Sep 93 17:48:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19137; Thu, 30 Sep 93 17:29:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from minnie.bell.inmet.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19129; Thu, 30 Sep 93 17:29:41 -0700 Received: by minnie.bell.inmet.com (4.1/SMI-4.1) id AA10934; Thu, 30 Sep 93 17:32:41 PDT Date: Thu, 30 Sep 1993 17:31:45 -0700 (PDT) From: Paul Tarr 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 Mike: Some of use do not have access to a newsgroup. 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?) 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 > > From owner-pine-info@cac.washington.edu Thu Sep 30 18:14:48 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14376; Thu, 30 Sep 93 18:14:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19771; Thu, 30 Sep 93 18:03:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from hellcow.css.itd.umich.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19765; Thu, 30 Sep 93 18:03:19 -0700 Received: by hellcow.css.itd.umich.edu (4.1/2.25) id AA05259; Thu, 30 Sep 93 21:04:15 EDT Date: Thu, 30 Sep 1993 21:02:19 -0400 (EDT) From: Paul Southworth 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?) 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 > This is a good idea, in my opinion. 1. It permits easy use of kill files to reduce noise. 2. Can be easily ignored when you're busy. 3. Will be readable with the PINE newsreaders of the future. 4. Will increase readership. From owner-pine-info@cac.washington.edu Thu Sep 30 21:44:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17633; Thu, 30 Sep 93 21:44:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19783; Thu, 30 Sep 93 18:04:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from venus.resntl.bhp.com.au by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19777; Thu, 30 Sep 93 18:04:45 -0700 Received: from squiggle.resntl.bhp.com.au by VENUS.RESNTL.BHP.COM.AU (PMDF V4.2-11 #2434) id <01H3LGOWJDOW000F9E@VENUS.RESNTL.BHP.COM.AU>; Fri, 1 Oct 1993 11:01:40 GMT Received: by squiggle.resntl.bhp.com.au (920330.SGI/920323.SGI.Irix.3.3) for @venus.resntl.bhp.com.au:mramey@u.washington.edu id AA01528; Fri, 1 Oct 93 11:02:46 +1000 Date: Fri, 01 Oct 1993 11:01:38 +1000 (EST) From: Steve Woodyatt Subject: RE: newsgroup rather than mailing list ? In-Reply-To: To: Paul Tarr Cc: Mike Ramey , Pine-Info Email List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Thu, 30 Sep 1993, Paul Tarr wrote: > Some of use do not have access to a newsgroup. > > 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?) 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 > > > > Yes, but the mailing list could still be administered for people with no News access. The rest of us could use the newsgroup, and select which articles to read! Steve -------------------------------------------------------------------/\/\--- Steve Woodyatt, Research Scientist, Geoscience & Spatial Systems. / \ BHP Research - Newcastle Laboratories, Australia./ ! ! \ Snail : P.O. Box 188, Wallsend 2287 /CENSORED\ Tel : +61 49 510695 Fax: +61 49 502126 \ ! ! / Internet: steve@resntl.bhp.com.au \ / ------------------------------------------------------------------\/\/\/--