From owner-pine-info@cac.washington.edu Thu Jul 1 00:49:17 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00741; Thu, 1 Jul 93 00:49:17 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16056; Thu, 1 Jul 93 00:38:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.liv.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16050; Thu, 1 Jul 93 00:38:39 -0700 Received: from liverpool.ac.uk by mailhub.liverpool.ac.uk with SMTP (PP) id <26078-0@mailhub.liverpool.ac.uk>; Thu, 1 Jul 1993 08:38:55 +0100 Date: Thu, 1 Jul 1993 08:34:25 +0100 (BST) From: Chris Wooff Subject: Re: saving messages in pine To: Shyela Aberman Cc: pine-info@cac.washington.edu In-Reply-To: <9307010322.AA10710@ vader.cc.emory.edu > Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Wed, 30 Jun 1993, Shyela Aberman wrote: > > I have no idea if this has been brought up already. When I try to save a > piece of mail, pine asks me what I want to name the folder but defaults to > the sender's address. I believe that the decision as to whether or not pine uses the sender's address in providing a default folder name is controlled by the elm-style-save option in the .pinerc. Of course I'm not trying to imply that your current problem shouldn't be looked at. I'm simply suggesting a temporary workround for you. Chris Wooff From owner-pine-info@cac.washington.edu Thu Jul 1 01:21:35 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01672; Thu, 1 Jul 93 01:21:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00603; Thu, 1 Jul 93 01:09:53 -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 AA00597; Thu, 1 Jul 93 01:09:52 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #86) id m0oBJiH-00003DC; Thu, 1 Jul 93 09:09 BST Date: Thu, 1 Jul 1993 09:07:00 +0100 (BST) From: Philip Hazel Subject: Re: saving messages in pine To: Shyela Aberman Cc: pine-info@cac.washington.edu In-Reply-To: <9307010322.AA10710@ vader.cc.emory.edu > Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: > for example, I cannot type the folder I want the mail to be saved in, because > the long address has pushed the cursor too far to the right, and the terminal > beeps instead of wrapping. I don't know if this is a problem with my terminal This problem arises even when the default is short, if the name of the file you want to save in is long. I hit this problem every now and again, but hadn't got around to grumbling about it yet. It would be nice if something could be done about it (having the field scroll left/right would be one solution). 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 Thu Jul 1 01:50:32 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02301; Thu, 1 Jul 93 01:50:32 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16431; Thu, 1 Jul 93 01:40:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ns.uta.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16425; Thu, 1 Jul 93 01:40:38 -0700 Received: from rainbow.uta.edu.uta.edu by ns.uta.edu with SMTP; Thu, 1 Jul 1993 3:39:21 CDT Received: by rainbow.uta.edu.uta.edu (4.1/SMI-4.1) id AA11352; Thu, 1 Jul 93 03:41:09 CDT Date: Thu, 1 Jul 1993 03:34:23 -0500 (CDT) From: "Dr. Abdelsalam Helal" Subject: Re: saving messages in pine To: Philip Hazel Cc: Shyela Aberman , 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 Thu, 1 Jul 1993, Philip Hazel wrote: > > for example, I cannot type the folder I want the mail to be saved in, because > > the long address has pushed the cursor too far to the right, and the terminal > > beeps instead of wrapping. I don't know if this is a problem with my terminal > > This problem arises even when the default is short, if the name of the file > you want to save in is long. I hit this problem every now and again, but > hadn't got around to grumbling about it yet. It would be nice if something > could be done about it (having the field scroll left/right would be one > solution). > I too have hit the same problem. I get away by enlarging the width of the pine window; something I am never proud of doing :-) If shell variables could be interpreted and evaluated by pine, I imagine this could ease the problem, where one can store long path names in shell variables (at least for UNIX folks of pine). Sumi Helal -------------------------------------------------------------------------- Abdelsalam Helal, Assistant professor Office Phone: (817) 273-3600 Computer Science Engineering Dept. Fax: (817) 273-3784 University of Texas at Arlington Email: helal@cse.uta.edu Box 19015, Arlington, TX 76019 Fedex Info:416 Yates St,Rm 300 -------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Jul 1 02:10:57 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02885; Thu, 1 Jul 93 02:10:57 -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 AA02879; Thu, 1 Jul 93 02:10:49 -0700 From: edwardy@bishop.bishop.hawaii.org Received: by bishop.bishop.hawaii.org (AIX 3.2/UCB 5.64/4.03) id AA21252; Wed, 30 Jun 1993 23:08:44 -1000 Date: Wed, 30 Jun 1993 23:00:30 +22305714 (HST) Subject: Long string handling (Re: saving messages in pine) To: 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: > > for example, I cannot type the folder I want the mail to be saved in, because > > the long address has pushed the cursor too far to the right, and the terminal > > beeps instead of wrapping. I don't know if this is a problem with my terminal > > This problem arises even when the default is short, if the name of the file > you want to save in is long. I hit this problem every now and again, but > hadn't got around to grumbling about it yet. It would be nice if something > could be done about it (having the field scroll left/right would be one > solution). > I have also encountered this problem for the first time today, except that it was in the Address book. When specifying a long email address: pinkerton%foo.bar.org@very.long.address.edu the address book allows me to enter the address, but upon calling it up during compose, it cuts off the end, thus ending with an invalid address. Iv worked around this by setting aliases in my shell i.e. alias pink='pine pinkerton%.. etc etc' I realise the addressing method is a mailing config problem on our side, but there must be alot of addresses/sites that require long addresses as such. Edward Yagi ps. anybody know of a spellchecker for the RS6000 running AIX3.2 for pine? ____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 Jul 1 11:02:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14807; Thu, 1 Jul 93 11:02:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22126; Thu, 1 Jul 93 10:50: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 AA22120; Thu, 1 Jul 93 10:50:46 -0700 Date: Thu, 1 Jul 1993 10:44:49 -0700 (PDT) From: Michael Seibel Subject: Re: Long string handling (Re: saving messages in pine) To: edwardy@bishop.bishop.hawaii.org 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: Good news! Horizontal scrolling is just one of a long list of features and fixes in the upcoming release. Stay tuned (and thanks for your patience)! Michael Seibel Networks and Distributed Computing mikes@cac.washington.edu University of Washington, Seattle (206) 543 - 0359 From owner-pine-info@cac.washington.edu Fri Jul 2 12:00:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18479; Fri, 2 Jul 93 12:00:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07567; Fri, 2 Jul 93 11:44:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from reggae.concert.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07561; Fri, 2 Jul 93 11:44:27 -0700 Received: from jade.ncat.edu by reggae.concert.net (5.59/tas-reggae/8-15-92) id AA25037; Fri, 2 Jul 93 14:36:00 -0400 Received: by jade.ncat.edu (5.57/TAS/11-16-88) id AA05062; Fri, 2 Jul 93 14:35:59 -0400 Date: Fri, 2 Jul 1993 14:21:14 -0400 (EDT) From: Cary Burnette Subject: Disabling Quota message on startup To: Pine INFO Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Hello: I just upgraded to Pine v3.07 from v3.05, and am having problems with Pine incorrectly reporting quota usage messages when it starts up. We are Running RISC/Ultrix v4.3 and AFS. I think the AFS quota system may be causing the erroneous messages. I would like to disable the quota feature, can someone point me to the code that would only disable this feature in Pine. Thanks Cary -- --------------------------------------------------------------------- Cary Burnette | kerm@ncat.edu Dept. of Electrical Engineering | McNair Hall | North Carolina A&T State University | Phone: (919)334-7648 Greensboro, NC 27411 | FAX: (919)334-7662 From owner-pine-info@cac.washington.edu Fri Jul 2 13:29:45 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20828; Fri, 2 Jul 93 13:29:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09564; Fri, 2 Jul 93 13:17:02 -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 AA09558; Fri, 2 Jul 93 13:17:00 -0700 Received: by tardis.svsu.edu (5.57/Ultrix3.0-C) id AA13425; Fri, 2 Jul 93 16:16:53 -0400 Date: Fri, 2 Jul 1993 16:09:54 -0400 (EDT) From: "John J. Guettler" Subject: Sender: and Reply-To: Headers To: Pine Info List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I've noticed from looking at the full headers of messages in my sent-mail folder that Pine (3.05) occasionally puts in Sender: and Reply-To: headers, in addition to the From: header, all three with the same data, my name and e-mail address. What criteria is it using to decide whether or not to include those two extra header lines? John J. Guettler Saginaw Valley State University From owner-pine-info@cac.washington.edu Fri Jul 2 13:57:05 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21608; Fri, 2 Jul 93 13:57:05 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09727; Fri, 2 Jul 93 13:42:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stubbs.ucop.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09721; Fri, 2 Jul 93 13:42:47 -0700 Received: by stubbs.ucop.edu (5.57/1.34) id AA19925; Fri, 2 Jul 93 13:41:43 -0700 Date: Fri, 2 Jul 1993 13:40:20 -0700 (PDT) From: "Mark H. Needleman" Subject: signoff To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Could I get signed off of this list - Ill be on vacation for a month and will sign back up when I get back - sorry to disturb the whole list but I tried pine-request and pine-info-request and those are invalid ids Mark Needleman University of California From owner-pine-info@cac.washington.edu Fri Jul 2 14:11:29 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22095; Fri, 2 Jul 93 14:11:29 -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 AA22089; Fri, 2 Jul 93 14:11:27 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 02 Jul 93 23:01:10+0200 Date: 02 Jul 93 23:01:10+0200 From: Sven Olofsson DSV Message-Id: <347167*SVENO@su-kom.dsv.su.se> In-Reply-To: To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Cary Burnette , Pine INFO Mailing List Subject: Disabling Quota message on startup Status: O X-Status: > I just upgraded to Pine v3.07 from v3.05, and am having problems with > Pine incorrectly reporting quota usage messages when it starts up. We are > Running RISC/Ultrix v4.3 and AFS. I think the AFS quota system may be > causing the erroneous messages. I would like to disable the quota feature, > can someone point me to the code that would only disable this feature > in Pine. I eliminated the line "#define USE_QUOTAS" in the file pine/os-unx.h before building pine with "build ult". The erroneous message disappeared after that. > Thanks > > Cary Sven Olofsson, Dept. of Computer and Systems Sciences, Stockholm University email: sveno@dsv.su.se From owner-pine-info@cac.washington.edu Sun Jul 4 16:39:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26054; Sun, 4 Jul 93 16:39:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23990; Sun, 4 Jul 93 16:28:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from port10.columbus.pub-ip.psi.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23984; Sun, 4 Jul 93 16:28:18 -0700 Subject: PINE port to SCO To: pine-info@cac.washington.edu Date: Sun, 4 Jul 1993 19:28:09 -0400 (EDT) From: Steven E Frazier Reply-To: Steven E Frazier X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 66 Message-Id: <9307041928.aa20660@eng.futurenet.com> Status: O X-Status: Is there a pine port for SCO? Is anyone working on it? thanks. From owner-pine-info@cac.washington.edu Mon Jul 5 07:53:11 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09962; Mon, 5 Jul 93 07:53:11 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21822; Mon, 5 Jul 93 07:41:56 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from offsv1.cis.McMaster.CA by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21816; Mon, 5 Jul 93 07:41:51 -0700 Received: by offsv1.cis.mcmaster.ca id AA13640 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Mon, 5 Jul 1993 10:42:09 -0400 Date: Mon, 5 Jul 1993 10:38:05 -0400 (EDT) From: Carolynn Spring Subject: Subscribe To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: SUB pine-info Carolynn Spring From owner-pine-info@cac.washington.edu Mon Jul 5 13:05:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13684; Mon, 5 Jul 93 13:05:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00855; Mon, 5 Jul 93 12:56:00 -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 AA00849; Mon, 5 Jul 93 12:55:59 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02113; Mon, 5 Jul 93 12:55:56 -0700 Date: Mon, 5 Jul 1993 12:47:11 -0700 (PDT) From: Terry Gray Subject: Re: signoff To: "Mark H. Needleman" 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: Mark, I'm CC'ing the list to indicate that "pine-info-request" *should* be a valid ID; it should go to a "majordomo" process which will either handle the request or forward it to Sheryl Erez for manual processing. However "pine-request" is not a valid ID. (Just send to "pine" if you want to reach the pine team, and to "pine-bugs" to report problems.) We'll get you off the list shortly, but could you also send me an instance of a bounced msg to "pine-info-request" ? Or did it just go into a black hole? (Please send to me, not the whole list.) Have a good vacation! -teg On Fri, 2 Jul 1993, Mark H. Needleman wrote: > Could I get signed off of this list - Ill be on vacation for a month and > will sign back up when I get back - sorry to disturb the whole list but I > tried pine-request and pine-info-request and those are invalid ids > > Mark Needleman > University of California > > From owner-pine-info@cac.washington.edu Thu Jul 8 08:32:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07276; Thu, 8 Jul 93 08:32:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04837; Thu, 8 Jul 93 08:17:04 -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 AA04831; Thu, 8 Jul 93 08:17:02 -0700 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0AQKDR6J400CXXO@mc.duke.edu>; Thu, 8 Jul 1993 11:21:54 EST Date: Thu, 08 Jul 1993 11:20:40 -0500 (EST) From: James Dryfoos- Postmaster Subject: New pine and inbox folder To: pine-info@cac.washington.edu Message-Id: <01H0AQKUJLSI00CXXO@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 Status: O X-Status: Why does the new Pine not always put the inbox folder at the top as did previous version? Now it moves around as folders are added and deleted and this makes it a bit harder to go back to. Since I switch from and to the inbox a lot, it would be nice to have it as it was. -- Jim From owner-pine-info@cac.washington.edu Thu Jul 8 09:38:48 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09445; Thu, 8 Jul 93 09:38:48 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05444; Thu, 8 Jul 93 08:53:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ees1a0.engr.ccny.cuny.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05438; Thu, 8 Jul 93 08:53:26 -0700 Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1) id AA17460; Thu, 8 Jul 93 11:53:01 EDT Date: Thu, 8 Jul 1993 11:51:44 -0400 (EDT) From: Dan Schlitt Subject: Re: New pine and inbox folder To: James Dryfoos- Postmaster Cc: pine-info@cac.washington.edu In-Reply-To: <01H0AQKUJLSI00CXXO@mc.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I agree that the inbox folder should have a fixed place in the folder display screen. Upper left as it is in 3.05 is ideal. /dan Dan Schlitt School of Engineering Computer Systems dan@ee-mail.engr.ccny.cuny.edu City College of New York (212)650-6760 New York, NY 10031 From owner-pine-info@cac.washington.edu Thu Jul 8 09:53:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09844; Thu, 8 Jul 93 09:53:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05967; Thu, 8 Jul 93 09:14:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from stein2.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05961; Thu, 8 Jul 93 09:14:38 -0700 Received: by stein2.u.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05684; Thu, 8 Jul 93 09:14:38 -0700 X-Sender: mramey@stein2.u.washington.edu Date: Thu, 8 Jul 1993 09:11:05 -0700 (PDT) From: Mike Ramey Subject: re: New pine and inbox folder To: Sheryl Erez Cc: James Dryfoos- Postmaster , 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: I hope 'sent-mail' and 'saved-messages' will also be in the #2 and #3 positions also. Have you given any thought to 'aligning' the names of these two folders to (for example): sent-mail saved-mail or sent-messages saved-messages ... or at least giving users the option of changing -both- of these names (via the .pinerc file). Currently only one of these may be altered in .pinerc (to the best of my knowledge). -Mike Ramey 685-0940 Wilcox-171 U-W Civil Eng FX-10 Seattle WA 98195. On Thu, 8 Jul 1993, Sheryl Erez wrote: > James, > > That was a bug. In the next version INBOX will be back where it belongs. > > Sheryl Erez > erez@cac.washington.edu > UW Network Information Center > > On Thu, 08 Jul 1993 11:20:40 -0500 (EST), James Dryfoos- Postmaster wrote: > > > Subject: New pine and inbox folder > > To: pine-info@cac.washington.edu > > > > Why does the new Pine not always put the inbox folder at the top as did > > previous version? Now it moves around as folders are added and deleted > > and this makes it a bit harder to go back to. Since I switch from and > > to the inbox a lot, it would be nice to have it as it was. > > > > -- Jim > From owner-pine-info@cac.washington.edu Thu Jul 8 09:55:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09946; Thu, 8 Jul 93 09:55:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05637; Thu, 8 Jul 93 09:02: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 AA05631; Thu, 8 Jul 93 09:02:48 -0700 Received: by herald.usask.ca (5.65/DEC-Ultrix/4.3) id AA29220; Thu, 8 Jul 1993 10:02:41 -0600 for pine-info@cac.washington.edu Date: Thu, 8 Jul 1993 10:00:27 -0600 (CST) From: Peter Scott U Sask Library Systems Dept Subject: Rich headers To: 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: Can Pine be set up to have the rich headers features as a default when composing/replying/forwarding a message? Peter Scott....Manager, Small Systems....University of Saskatchewan Libraries scottp@herald.usask.ca Phone 306-966-5920 FAX 306-966-6040 From owner-pine-info@cac.washington.edu Thu Jul 8 10:36:01 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11155; Thu, 8 Jul 93 10:36:01 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08920; Thu, 8 Jul 93 10:26:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from csd4.csd.uwm.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08914; Thu, 8 Jul 93 10:26:28 -0700 Received: by csd4.csd.uwm.edu; id AA15132; Thu, 8 Jul 93 12:25:53 -0500 From: David A Rasmussen Message-Id: <9307081725.AA15132@csd4.csd.uwm.edu> Subject: Re: New pine and inbox folder To: dan@ees1a0.engr.ccny.cuny.edu (Dan Schlitt) Date: Thu, 8 Jul 1993 12:25:52 -0500 (CDT) Cc: POSTMAST@mc.duke.edu, pine-info@cac.washington.edu In-Reply-To: from "Dan Schlitt" at Jul 8, 93 11:51:44 am Word-Of-The-Day: feeble Content-Type: text Content-Length: 866 Status: O X-Status: >From owner-pine-info@cac.washington.edu Thu Jul 8 12:16:14 1993 > >I agree that the inbox folder should have a fixed place in the folder >display screen. Upper left as it is in 3.05 is ideal. > while we're on the subject of folders, someone brought up the fact that if you save a message in a folder other than what is named by the user on the from line, and it gets saved in the current working directory as opposed to the mail folder directory, naive users can't find what they've saved later. I don't know what to suggest here. ??? This is how it was working with pine 3.05. I haven't looked at 3.07 yet regarding this action. -- Dave Rasmussen - SysAdm/Hacker/Consulting Supervisor, UWM Computing Svcs Div. Internet:dave@uwm.edu, Uucp:uwm!dave, Bitnet:dave%uwm.edu@INTERBIT AT&T:414-229-5133 USmail:Box 413 EMS380,Milwaukee,WI 53201 HAM: N9REJ From owner-pine-info@cac.washington.edu Thu Jul 8 09:07:39 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08617; Thu, 8 Jul 93 09:07:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tsippi.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08611; Thu, 8 Jul 93 09:07:32 -0700 Date: Thu, 8 Jul 1993 09:05:50 -0700 (PDT) From: Sheryl Erez Subject: re: New pine and inbox folder To: James Dryfoos- Postmaster Cc: pine-info@cac.washington.edu In-Reply-To: <01H0AQKUJLSI00CXXO@mc.duke.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: James, That was a bug. In the next version INBOX will be back where it belongs. Sheryl Erez erez@cac.washington.edu UW Network Information Center On Thu, 08 Jul 1993 11:20:40 -0500 (EST), James Dryfoos- Postmaster wrote: > Subject: New pine and inbox folder > To: pine-info@cac.washington.edu > > Why does the new Pine not always put the inbox folder at the top as did > previous version? Now it moves around as folders are added and deleted > and this makes it a bit harder to go back to. Since I switch from and > to the inbox a lot, it would be nice to have it as it was. > > -- Jim From owner-pine-info@cac.washington.edu Thu Jul 8 13:16:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17373; Thu, 8 Jul 93 13:16:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09593; Thu, 8 Jul 93 13:01:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mcmail.CIS.McMaster.CA by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09583; Thu, 8 Jul 93 13:01:35 -0700 Received: by mcmail.cis.mcmaster.ca id AA26309 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 8 Jul 1993 16:01:52 -0400 Date: Thu, 8 Jul 1993 16:01:24 -0400 (EDT) From: Muriel McKay Subject: Re: Rich headers 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: I have had many requests for this feature also . =============================================================================== Muriel McKay, Analyst, Desktop Computing Support. CIS. ABB132 ext. 3630 On Thu, 8 Jul 1993, Peter Scott U Sask Library Systems Dept wrote: > Can Pine be set up to have the rich headers features as a default when > composing/replying/forwarding a message? > > Peter Scott....Manager, Small Systems....University of Saskatchewan Libraries > scottp@herald.usask.ca Phone 306-966-5920 FAX 306-966-6040 > > From owner-pine-info@cac.washington.edu Thu Jul 8 22:47:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27899; Thu, 8 Jul 93 22:47:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12098; Thu, 8 Jul 93 22:34:05 -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 AA12092; Thu, 8 Jul 93 22:34:03 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA26235; Fri, 9 Jul 1993 00:23:55 -0500 Date: Fri, 9 Jul 1993 00:20:16 -0500 (CDT) From: "Robert A. Hayden" Subject: Inability to resolve sender for reply To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: This is something that I noticed on our system here (Ultrix). If a person send me mail using elm, and then I try to reply to the message (using pine, of course), the 'To:' line turns up blank and I actually have to ^z out and do a 'frm' to determine who the sender is and then paste in the address (or hope they have a .signature). Is this a bug with pine, elm, something else, or totally normal operation? Thanks for your time. [> Robert Hayden ____ <] Drive defensively, [> \ /__ <] Buy a tank. [> hayden@krypton.mankato.msus.edu \/ / <]<-----------------------------> [> aq650@slc4.INS.CWRU.Edu \/ <] #include -=-=- (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ From owner-pine-info@cac.washington.edu Fri Jul 9 12:47:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15731; Fri, 9 Jul 93 12:47:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22311; Fri, 9 Jul 93 12:33:30 -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 AA22305; Fri, 9 Jul 93 12:33:23 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA00893; Fri, 9 Jul 1993 14:35:57 -0500 Date: Fri, 9 Jul 1993 14:33:13 -0500 (CDT) From: "Robert A. Hayden" Subject: Pine and News Posting To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I'm curious as to when/if the ability to post to news will be added to pine. The reason I ask is in one of the projects I work on, I send out several files to different people through mail and also post those same files to different newsgroups. If I could do it all in one shot (for example, by adding the newsgroup names to the distribution lists), it would save me much headaches, time and effort. Just curious, actually. [> Robert Hayden ____ <] Drive defensively, [> \ /__ <] Buy a tank. [> hayden@krypton.mankato.msus.edu \/ / <]<-----------------------------> [> aq650@slc4.INS.CWRU.Edu \/ <] #include -=-=- (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ From owner-pine-info@cac.washington.edu Fri Jul 9 14:18:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18383; Fri, 9 Jul 93 14:18:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23751; Fri, 9 Jul 93 14:05:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from uwavm.u.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23745; Fri, 9 Jul 93 14:05:49 -0700 Received: from orca.fhcrc.org by UWAVM.U.WASHINGTON.EDU (IBM VM SMTP V2R1) with TCP; Fri, 09 Jul 93 14:05:42 PDT Received: by orca.fhcrc.org (AIX 3.2/UCB 5.64/4.03) id AA19310; Fri, 9 Jul 1993 14:07:03 -0700 Date: Fri, 9 Jul 1993 14:02:37 -800 (PDT) From: Brent Blumenstein Reply-To: Brent Blumenstein Subject: attachments To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Status: O X-Status: Is there someone out there who could give me a quick mini course on mail attachments, and particularly the degree of standardization across commonly used mail platforms, such as pine cc:mail, Da Vinci mail, pine (of course), elm, xms, MCIMail, PSI, other commercial mail services, ... e-mail or a phone call would be accepted. It would be optimal to have a quick answer in about an hour or so. Maybe others are also curious. -- Brent A. Blumenstein | tel.: 206 667 4623 Fred Hutchinson Cancer Research Center | fax: 206 667 4408 1124 Columbia Street MP-557 | e-mail: brentb@orca.fhcrc.org Seattle, WA 98104 USA | From owner-pine-info@cac.washington.edu Fri Jul 9 16:25:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22958; Fri, 9 Jul 93 16:25:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16855; Fri, 9 Jul 93 16:18: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 AA16849; Fri, 9 Jul 93 16:18:18 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA01139 sendmail 5.67/UCSD-2.2-sun via SMTP Fri, 9 Jul 93 16:18:16 -0700 for pine-info@cac.washington.edu Received: from weber.ucsd.edu (localhost [127.0.0.1]) by weber.ucsd.edu (8.1C/UCSDGENERIC.4c) with SMTP id QAA23251; Fri, 9 Jul 1993 16:18:15 -0700 Message-Id: <199307092318.QAA23251@weber.ucsd.edu> X-Authentication-Warning: weber.ucsd.edu: Host localhost claimed to be weber.ucsd.edu To: pine-info@cac.washington.edu Subject: Re: Pine and News Posting In-Reply-To: Your message of "Fri, 09 Jul 1993 14:33:13 -0500." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 09 Jul 1993 16:18:14 -0700 From: "Michael J. Corrigan" Status: O X-Status: On the other hand, the ability to mail while posting is already present in trn3.x. The posting template has a Cc: line whose entries get emailed to. -Mike Corrigan I'm curious as to when/if the ability to post to news will be added to pin e. The reason I ask is in one of the projects I work on, I send out several files to different people through mail and also post those same files to different newsgroups. If I could do it all in one shot (for example, by adding the newsgroup names to the distribution lists), it would save me much headaches, time and effort. Just curious, actually. [> Robert Hayden ____ <] Drive defensively, [> \ /__ <] Buy a tank. [> hayden@krypton.mankato.msus.edu \/ / <]<----------------------------- > [> aq650@slc4.INS.CWRU.Edu \/ <] #include -=-=- (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ From owner-pine-info@cac.washington.edu Fri Jul 9 18:18:46 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25196; Fri, 9 Jul 93 18:18:46 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17394; Fri, 9 Jul 93 18:11:04 -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 AA17388; Fri, 9 Jul 93 18:11:02 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA02622; Fri, 9 Jul 93 18:09:00 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA00705; Fri, 9 Jul 93 18:13:34 -0700 Date: Fri, 9 Jul 1993 17:56:15 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: attachments To: Brent Blumenstein 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: On Fri, 9 Jul 1993, Brent Blumenstein wrote: > Is there someone out there who could give me a quick mini course on mail > attachments, and particularly the degree of standardization across > commonly used mail platforms, such as pine cc:mail, Da Vinci mail, pine > (of course), elm, xms, MCIMail, PSI, other commercial mail services, Well, to mail an attachment use the Attchmnt: part of the header...just put ine filename of the file you wish to attach...you may use the browser (^T) to select the file also...There is a place to type in a comment (between the "") at the end of the filename...pine puts them there for you... To view an attachment, pine will tell you that there is an attachment to view or save. Use the 'A' command (when reading you mail) and pine will prompt you to for which attachment and view or save...If you are using an x-terminal and have xv (or some other graphics viewer defined in your .pinerc) pine will automatically display GIF images. That's it....it's really simple...I can blaze through messages with 3 to 4 meg of attachments in no time...but be careful with attachments...you can wasily fill up a mail spool with them...it's happened here before... As for a standard...Pine supports the MIME standard (1.0, I believe). It automatically encodes your attachment and sends it off with your message and decodes attachemts sent to you whenn saved or displayed. If an attachment is an ASCII file in one of the standard character sets...to see a list of those fonts...I think that they are listed in the latest RFC...you can get it by anonymous ftp at ftp.cac.washington.edu. > e-mail or a phone call would be accepted. It would be optimal to have a > quick answer in about an hour or so. Maybe others are also curious. Well, this wasn't within an hour, but I hope I've been helpful. 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 Fri Jul 9 18:18:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25222; Fri, 9 Jul 93 18:18:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17404; Fri, 9 Jul 93 18:12:55 -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 AA17398; Fri, 9 Jul 93 18:12:51 -0700 Received: by digi.syd.deg.csiro.au id AA15304 (5.65c/IDA-1.4.4 for pine mailing list ); Sat, 10 Jul 1993 11:14:32 +1000 Date: Sat, 10 Jul 1993 11:11:24 +1000 (EST) From: Jack Churchill Subject: uuencode To: pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Is it too difficult to modify pine to at least accept uuencoded attachemnts and automatically extract and decode them (with prompting)? I like to be "backward compatible" since I believe there will lots of other mailers which will continue to use uuencode for a while until MIME takes over (if ever). Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Sat Jul 10 06:17:50 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03616; Sat, 10 Jul 93 06:17:50 -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 AA03610; Sat, 10 Jul 93 06:17:48 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 10 Jul 93 15:11:02+0200 Date: 10 Jul 93 15:11:02+0200 From: Jacob Palme DSV Message-Id: <353785*jpalme@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" Subject: Exporting what I have just written Status: O X-Status: Is there a simple way of exporting the message I have just sent to a file. I know I can do it by going first to the main menu, then to the folders- menu, then switch current folder to "sent-mail", then opening this folder, then exporting the last entry in it, and then going back to the main menu and then to the folders menu and switching back to the incoming folder again. But that seems to me a little too clumsy. Especially since the other mail system I use, SuperKOM, gives me a copy of the last read message on a file with just one single command, as opposed to the 7 commands in sequence which Pine requires. From owner-pine-info@cac.washington.edu Mon Jul 12 01:05:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27412; Mon, 12 Jul 93 01:05:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10462; Mon, 12 Jul 93 00:56:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.liv.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10456; Mon, 12 Jul 93 00:56:18 -0700 Received: from liverpool.ac.uk by mailhub.liverpool.ac.uk with SMTP (PP) id <13708-0@mailhub.liverpool.ac.uk>; Mon, 12 Jul 1993 08:56:14 +0100 Date: Mon, 12 Jul 1993 08:49:01 +0100 (BST) From: Chris Wooff Subject: Re: Exporting what I have just written To: Jacob Palme DSV Cc: Pine mailer discussions group In-Reply-To: <353785*jpalme@su-kom.dsv.su.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On 10 Jul 1993, Jacob Palme DSV wrote: > Is there a simple way of exporting the message I have just sent to a file. > I know I can do it by going first to the main menu, then to the folders- > menu, then switch current folder to "sent-mail", then opening this > folder, then exporting the last entry in it, and then going back to > the main menu and then to the folders menu and switching back to > the incoming folder again. If you always want to have your outgoing messages stored in a folder other than sent-mail then why not change the value default-fcc in your .pinerc file? On the other hand if you want to selectively specify the folder for outgoing mail then use the pseudo Header-field Fcc: which becomes visible when you enable the "Rich-Hdr" facility. Of course this does assume you are in a position to make such a decision before you send the mail Chris Wooff From owner-pine-info@cac.washington.edu Mon Jul 12 03:31:06 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29330; Mon, 12 Jul 93 02:33:56 -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 AA29324; Mon, 12 Jul 93 02:33:55 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 12 Jul 93 11:21:02+0200 Date: 12 Jul 93 11:21:02+0200 From: Jacob Palme DSV Message-Id: <353845*jpalme@su-kom.dsv.su.se> In-Reply-To: To: Jacob Palme DSV , "Pine mailer discussions group (pine-infoEcac.washington.edu)" , David Wall Subject: Swedish character sets Status: O X-Status: Thank you for the help on Pine. I am not sure what you need about "the Swedish character set". There are several different computer character sets which try to satisfy the requirements of the Swedish language. The most important of them are ISO 8859-1 Macintosh character set IBM PC CP 850 or CP 837 character sets There is also a Swedish variant of ASCII, where some ASCII characters are replaced with national Swedish variants. The easiest way for you to get information about the Swedish character sets is to go to a Macintosh computer. Cut out the portion below the dotted line below, and give it as input to Microsoft Word on a Macintosh. Tell Word to interpret the file as an RTF file. Then print it in some of the most common fonts, e.g. Times, Helvetica and New York. You will then see the Swedish characters and the ASCII character they replace. Warning: A question mark in the table indicates a character where I do not know the Swedish corresponding character, I am writing this from home and I have the full tables at work, where I will not be until August. --------------------------------------------------- {\rtf1\mac\deff2 {\fonttbl{\f0\fswiss Chicago;}{\f2\froman New York;}{\f3\fswiss Geneva;}{\f4\fmodern Monaco;}{\f5\fscript Venice;}{\f11\fnil Cairo;}{\f13\fnil Zapf Dingbats;}{\f14\fnil Bookman;}{\f15\fnil N Helvetica Narrow;}{\f16\fnil Palatino;} {\f18\fnil Zapf Chancery;}{\f20\froman Times;}{\f21\fswiss Helvetica;}{\f22\fmodern Courier;}{\f23\ftech Symbol;}{\f24\fnil Mobile;}{\f34\fnil New Century Schlbk;}{\f128\fnil MacHumaine;}{\f144\fnil PretzelSV;}{\f202\fnil B New Baskerville Bold;} {\f203\fnil BI New Baskerville BoldIt;}{\f204\fnil I New Baskerville Italic;}{\f205\fnil New Baskerville;}{\f1817\fnil CarawayBold;}{\f1836\fnil Ashley;}{\f5673\fnil Tekton Bold;}{\f11647\fnil Formata Bold;}{\f11649\fnil Formata Italic;} {\f11650\fnil Formata BoldItalic;}{\f11655\fnil Formata Regular;}{\f14862\fnil Stone Serif Bold;}{\f14863\fnil Stone Serif SemiboldItalic;}{\f14864\fnil Stone Serif Semibold;}}{\colortbl\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255; \red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;}{\stylesheet{\s242 \f22\fs20 \sbasedon0\snext0 page number;}{\f22\fs20 \sbasedon222\snext0 Normal;}{\s1\fi-980\li980\sb140\sa140 \f14 \sbasedon0\snext1 paragraf;}}\paperw11880\paperh16820\margl1021\margr1021\margt1134\margb1134\widowctrl\ftnbj\fracwidth \sectd \sbknone\pgnrestart\pgnx720\pgny720\linemod0\linex0\cols1\endnhere \pard\plain \f22\fs20 Swedish character set\par \'8c\tab \}\tab a with ring\par \'8a\tab \{\tab a with two dots\par \'9a\tab |\tab o with two dots\par \'9f\tab ?\tab u with two dots\par \'8e\tab ?\tab e with accent acute\par \'81\tab ]\tab A with ring\par \'80\tab [\tab A with two dots\par \'85\tab \\\tab O with two dots\par \'86\tab ?\tab U with two dots\par \'83\tab ?\tab E with accent actue\par \par \par } From owner-pine-info@cac.washington.edu Mon Jul 12 10:10:40 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07762; Mon, 12 Jul 93 10:10:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tsippi.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07756; Mon, 12 Jul 93 10:10:37 -0700 Date: Mon, 12 Jul 1993 10:01:27 -0700 (PDT) From: Sheryl Erez Subject: Re: New pine and inbox folder To: David A Rasmussen Cc: pine-info@cac.washington.edu In-Reply-To: <9307081725.AA15132@csd4.csd.uwm.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Dave, Both Pine 3.05 and 3.07 have this behavior when the configuration variable "elm-style-save" is set on. While being true to Elm, this practice has confused many people so it was changed for the next (August) Pine release. Sheryl Erez erez@cac.washington.edu UW Network Information Center On Thu, 8 Jul 1993 12:25:52 -0500 (CDT), David A Rasmussen wrote: > while we're on the subject of folders, someone brought up the fact that if > you save a message in a folder other than what is named by the user on the > from line, and it gets saved in the current working directory as opposed to > the mail folder directory, naive users can't find what they've saved > later. > > I don't know what to suggest here. ??? > > This is how it was working with pine 3.05. I haven't looked at 3.07 > yet regarding this action. > > -- > Dave Rasmussen - SysAdm/Hacker/Consulting Supervisor, UWM Computing Svcs Div. > Internet:dave@uwm.edu, Uucp:uwm!dave, Bitnet:dave%uwm.edu@INTERBIT > AT&T:414-229-5133 USmail:Box 413 EMS380,Milwaukee,WI 53201 HAM: N9REJ From owner-pine-info@cac.washington.edu Mon Jul 12 15:31:50 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19733; Mon, 12 Jul 93 15:31:50 -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 AA19113; Mon, 12 Jul 93 15:18:09 -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 AA19107; Mon, 12 Jul 93 15:18:08 -0700 Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19740; Mon, 12 Jul 93 15:17:34 -0700 Received: from [128.95.135.14] by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00597; Mon, 12 Jul 93 15:17:33 -0700 Reply-To: Michael Seibel Message-Id: Date: Mon, 12 Jul 1993 15:14:09 PDT From: Michael Seibel To: Pine Announcement Distribution Subject: ANNOUNCING general availability of PC-Pine 3.84 (Beta #3) X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu, pcpine-alpha@cac.washington.edu Status: O X-Status: This note is to announce (finally!) general availability of the Pine port to DOS; the first widely-available release of PC-Pine. It's distributed in executable form compatible with either FTP Inc's PC/TCP, Novell's LAN WorkPlace for DOS, or a suitable packet-driver. PC-Pine is intended to look and feel very much like Pine on UNIX, however enhancements in 3.84 have had some impact on the user-interface (e.g., print is no longer "L"). As we understand the importance of a common interface, a source release of the next version, 3.85, is planned for August. It will bring the UNIX version into line with this release and include several new ports (including DOS). We believe version 3.84 is reasonably stable and free of serious bugs, but still consider it a test version. We'll try to have any reported bugs fixed in the upcoming source release. How to get your very own copy... mkdir pine cd \pine ftp ftp.cac.washington.edu cd /mail binary get pcpine_n.zip <-- Novell LWP version or get pcpine_f.zip <-- FTP PC/TCP version or get pcpine_p.zip <-- WATTCP/packet-driver version quit pkunzip *.zip The packet-driver version, and in some cases the PC/TCP and LWP versions, will need additional configuration prior to running pine. The extra step is described in the distribution's INSTALL.TXT file. Otherwise, typing "pine" after unpacking should get you started. Pine will prompt for and insert in its configuration file (pinerc) information it needs to run. However, it might be best to look at the INSTALL.TXT file first, so you know what Pine will ask you for. Alternatively, you can edit (and rename) the sample pinerc file, PINERC.SAM, as appropriate. Lastly, PC-Pine's access to incoming mail and other remote folders is via the Interactive Mail Access Protocol (IMAP). To take full advantage of the new support for remote folder collection access (e.g., folders of previously archived messages on a UNIX host), it's necessary to install the latest IMAPd server, also available from ftp.cac.washington.edu in the /mail directory under imap.tar.Z. Enjoy! The Pine Team University of Washington From owner-pine-info@cac.washington.edu Mon Jul 12 16:07:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21298; Mon, 12 Jul 93 16:07:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01515; Mon, 12 Jul 93 15:57:30 -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 AA01511; Mon, 12 Jul 93 15:57:27 -0700 Received: by wugate.wustl.edu (5.65c+/WUSTL-0.3) with SMTP id AA22963; Mon, 12 Jul 1993 17:58:15 -0500 Received: from whats-next by fcrc-next.ecs.wustl.edu (NX5.67c/NX3.0M) id AA07520; Mon, 12 Jul 93 17:58:26 -0500 Received: by whats-next.ecs.wustl.edu (NX5.67c/NX3.0X) id AA06190; Mon, 12 Jul 93 17:58:19 -0500 Date: Mon, 12 Jul 1993 17:51:21 -0500 (CDT) From: "J. Nicholas Laneman" Subject: A couple of questions.... To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Hey, before I start with the questions, let me first compliment you guys on your coding. Pine is great! And after installing it on a couple different machines and not getting a single error in the process, what can I say besides Wow! Now then, for the questions. The department for which I work deals with the language departments quite a lot. Right now, we support email for faculty and students on NeXT machines running pine and imap. Our concern right now is to allow use of 8-bit characters in email messages. That is, instead of filtering them out or not displaying them, we'd like to set it up so that people can just type away and have their email look as close to the written language as possible. Can you lead me to a solution for this. We use CUTCP on IBM PC clones and NCSA Telnet UW version on the Mac. If this is a FAQ, I apologize, but I am not a member of this mail list (yet). My supervisor just asked me today to get to work on this project for him. Well, I made it seem as though I had tons of questions, but apparently I only had one. My thanks in advance for any and all help. Please respond to me directly, if you don't mind. If no one has compiled a list of answers for this question, I'll be glad to post one when I sign onto the list. Thanks, JNL ----------------------------------------------- J. Nicholas Laneman Computer Science & Electrical Engineering Major Specialist, Educational Computing Services Washington University, St. Louis, Mo. jnl1@fcrc-next.ecs.wustl.edu From owner-pine-info@cac.washington.edu Mon Jul 12 18:58:15 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25111; Mon, 12 Jul 93 18:58:15 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22364; Mon, 12 Jul 93 18:48:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from kalama.doe.Hawaii.Edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22358; Mon, 12 Jul 93 18:48:56 -0700 Received: by kalama.doe.Hawaii.Edu (5.0/SMI-4.1) id AA03488; Mon, 12 Jul 93 15:46:15 HST Date: Mon, 12 Jul 1993 15:31:52 -1000 (HST) From: Lee Ann Sakihara Reply-To: Lee Ann Sakihara Subject: inbox is "readonly", interrupted-mail is empty To: Pine Information list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Length: 902 Status: O X-Status: We are having a few problems running Pine 3.05 under Solaris 2.2 (aka SunOS 5.2), at times the inbox becomes flagged as "readonly" and in order to resolve the problem, we delete the file: /tmp/.\\var\\mail\\username This is a temporary solution, but we're wondering if we should install pine 3.07 or if it has something to do with Solaris. The second problem we encountered is that when a session is disconnected while composing a message. Normally pine creates the file interrupted-mail which would contain the text of the message that was being composed when the system was interrupted. What happens on our system is the interrupted-mail file is created, but it contains 0 bytes. Any suggestions are welcome. Thanks in advance. Lee Ann M. Sakihara Internet: leeann@uhunix.uhcc.hawaii.edu University of Hawaii Computing Center Bitnet: leeann@uhunix.bitnet From owner-pine-info@cac.washington.edu Mon Jul 12 20:08:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26080; Mon, 12 Jul 93 20:08:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22835; Mon, 12 Jul 93 20:00:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from RUTGERS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22829; Mon, 12 Jul 93 20:00:55 -0700 Received: from mimsy.UUCP by rutgers.edu (5.59/SMI4.0/RU1.5/3.08) with UUCP id AA27957; Mon, 12 Jul 93 22:20:00 EDT Received: by mimsy.UMD.EDU (smail2.5) id AA19090; 12 Jul 93 22:19:40 EDT (Mon) Received: from ghost.uunet.ca (via uunet.ca) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA03295; Mon, 12 Jul 93 22:06:28 -0400 Received: from moore by mail.uunet.ca with UUCP id <101455(5)>; Mon, 12 Jul 1993 22:06:20 -0400 Received: by moore.com (4.1/smail2.5/01-12-90) id AA28500; Mon, 12 Jul 93 22:04:16 EDT Date: Mon, 12 Jul 1993 22:00:06 -0400 From: Paul Maclauchlan Subject: Arrow keys To: Pine Info mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I have a user in Australia, coming into my system via Infonet's packet switch network. He usually connects via a direct call from in town. He reports that the arrow keys no longer work. His PC comms software (ProComm) is set to VT100 emulation, and so is his account. Any ideas what could cause this? Any work-arounds? BTW, I typically use Pine via ProComm from Windows with vt100 emulation. Also, he reports an error message: "RDF DENIED", and then his connection froze. Is this a Pine error message? Thanks for any help you can offer. -- .../Paul Maclauchlan Moore Corporation Limited, Toronto, Ontario (416) 364-2600 paul@moore.com -or- {...!uunet.ca,...!telly}!moore!paul "We're too busy singing to put anybody down." The Monkees From owner-pine-info@cac.washington.edu Mon Jul 12 22:18:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27394; Mon, 12 Jul 93 22:18:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02977; Mon, 12 Jul 93 22:08:53 -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 AA02971; Mon, 12 Jul 93 22:08:51 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00364; Mon, 12 Jul 93 22:08:47 -0700 Date: Mon, 12 Jul 1993 22:05:29 -0700 (PDT) From: Mark Crispin Subject: re: A couple of questions.... To: "J. Nicholas Laneman" 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: Pine supports the ISO-8859-x (x is a number from 1 to 9) character sets, and does the proper MIME conversion to transmit these 8-bit characters over SMTP which is a 7-bit stream. Pine even supports ISO-2022-JP (Japanese), albeit only for reading. I am not absolutely sure, but I have empirical evidence that suggests that the 8-bit character set used on NeXTs is NOT one of the international standard character sets but rather is some private character set used only by NeXT. This may require some filtering, or perhaps a private version of Terminal.app that converts to the standard character sets. From owner-pine-info@cac.washington.edu Mon Jul 12 22:37:32 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27639; Mon, 12 Jul 93 22:37:32 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03031; Mon, 12 Jul 93 22:24:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from world.std.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03025; Mon, 12 Jul 93 22:24:26 -0700 Received: by world.std.com (5.65c/Spike-2.0) id AA16261; Tue, 13 Jul 1993 01:24:24 -0400 Date: Tue, 13 Jul 1993 01:24:24 -0400 From: bzs@world.std.com (Barry Shein) Message-Id: <199307130524.AA16261@world.std.com> To: pine-info@cac.washington.edu Subject: emacs/rmail (babyl) -> pine folder? Status: O X-Status: Does anyone by any wild chance have a program that can translate an emacs/rmail (BABYL) format mail folder (RMAIL file) to a pine mail folder? Someone here ran emacs/rmail to try it and later regretted it. Unfortunately it's not entirely trivial (I don't think) because BABYL format throws away the Unix "From" line (not to be confused with the "From:" line.) Thanks. -Barry Shein Software Tool & Die | bzs@world.std.com | uunet!world!bzs Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD From owner-pine-info@cac.washington.edu Mon Jul 12 22:54:39 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27786; Mon, 12 Jul 93 22:54:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03121; Mon, 12 Jul 93 22:45:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03115; Mon, 12 Jul 93 22:45:20 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA00580; Mon, 12 Jul 93 22:42:47 -0700 Date: Mon, 12 Jul 1993 22:41:41 -0700 (PDT) From: Mark Crispin Subject: re: emacs/rmail (babyl) -> pine folder? To: Barry Shein Cc: pine-info@cac.washington.edu In-Reply-To: <199307130524.AA16261@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I'm not aware of such a program, but if some nice person would like to write a c-client driver for babyl format I'll consider it for inclusion in future releases of c-client (meaning that Pine will eventually support babyl format as well). From owner-pine-info@cac.washington.edu Tue Jul 13 01:06:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00180; Tue, 13 Jul 93 01:06:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24160; Tue, 13 Jul 93 00:57:44 -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 AA24154; Tue, 13 Jul 93 00:57:43 -0700 Via: uk.ac.sheffield; Tue, 13 Jul 1993 08:57:06 +0100 Received: from sunc.sheffield.ac.uk by pp.shef.ac.uk with SMTP (PP) id <05011-0@pp.shef.ac.uk>; Tue, 13 Jul 1993 08:50:39 +0100 From: Chris Martin Date: Tue, 13 Jul 93 08:57:54 BST Message-Id: <21429.9307130757@sunc.sheffield.ac.uk> Received: from ss3.noname by sunc.sheffield.ac.uk; Tue, 13 Jul 93 08:57:54 BST Received: by ss3.noname (4.1/SMI-4.1) id AA06353; Tue, 13 Jul 93 08:56:46 BST To: bzs@world.std.com Cc: pine-info@cac.washington.edu In-Reply-To: <199307130524.AA16261@world.std.com> (bzs@world.std.com) Subject: Re: emacs/rmail (babyl) -> pine folder? Status: O X-Status: You can run Emacs again and then save the messages using C-o file RET which "appends a copy of the current message to the file , writing it in Unix mail format" I hope this helps, Chris From owner-pine-info@cac.washington.edu Tue Jul 13 01:44:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00895; Tue, 13 Jul 93 01:44:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03694; Tue, 13 Jul 93 01:36:21 -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 AA03688; Tue, 13 Jul 93 01:36:12 -0700 Received: by digi.syd.deg.csiro.au id AA00236 (5.65c/IDA-1.4.4 for pine mailing list ); Tue, 13 Jul 1993 18:37:54 +1000 Date: Tue, 13 Jul 1993 18:30:33 +1000 (EST) From: Jack Churchill Subject: pc-pine To: pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Just tested pc-pine and it's very good. It's slow sending attachments to the server but I suppose that's to be expected (I'm using a 386/33). It's also slow switching between folders on the server. Otherwise, it all works so far. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Tue Jul 13 03:07:55 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02546; Tue, 13 Jul 93 03:07:55 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24748; Tue, 13 Jul 93 03:00:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from natalie.ibmpcug.co.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24742; Tue, 13 Jul 93 03:00:38 -0700 Message-Id: <9307131000.AA24742@mx1.cac.washington.edu> Received: from ibmpcug.co.uk by natalie.ibmpcug.co.uk id <01781-0@natalie.ibmpcug.co.uk>; Tue, 13 Jul 1993 10:55:02 +0100 Subject: SCO port of Pine? To: pine-info@cac.washington.edu Date: Tue, 13 Jul 1993 10:54:54 +0100 (MET DST) Reply-To: jake@ibmpcug.co.uk X-Mailer: ELM [version 2.4 PL21] Content-Type: text Content-Length: 436 From: System Administrator Status: O X-Status: Hello, I know this has been asked before but nothing was mentioned.. >From "pine-ports" of the Pine 3.07 docs.. sco --- Santa Cruz Operation UNIX Some work has been done on this, in particular a version of the c-client has been ported, though it is not included here yet. This will probably be in the next major release. So when is the next major release? Or better still is the SCO port ready available yet? Thanks, Jake From owner-pine-info@cac.washington.edu Tue Jul 13 05:08:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04768; Tue, 13 Jul 93 05:08:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25425; Tue, 13 Jul 93 04:45:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25419; Tue, 13 Jul 93 04:45:16 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <04168-0@susssys1.reading.ac.uk>; Tue, 13 Jul 1993 12:44:53 +0100 Date: Tue, 13 Jul 1993 12:42:36 +0100 (BST) From: Mike Roch Subject: Pine Crashes To: pine-info@cac.washington.edu Cc: sxsgilli@reading.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="587204512-1648954721-742563875:#17638" Status: O X-Status: --587204512-1648954721-742563875:#17638 Content-Type: TEXT/PLAIN; charset=US-ASCII >From time to time Pine crashes here due to some condition related to message/header format. Would it be possible for Pine to deal with messages it doesn't understand with a message like "Can't read that one" as opposed to crashing out completely? A crash is about the most alarming thing that can happen to the sort of people Pine is aimed at - data is seldom lost but it takes quite a lot of TLC to persuade people that it doesn't matter. I attach a message from the ECS mail list that has this effect for us. Another instance that's come up recently is where a message from a mailing list has a "Reply-to:" but no "From:" field. Pine copes Ok except when you hit ^T to try to take the address; instead of "Can't - nothing to take" (or even "Can't - don't know why") you get a crash with core dump. Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AX. Fax: 0734 753094 --587204512-1648954721-742563875:#17638 Content-Type: MESSAGE/RFC822 Content-ID: Content-Description: Forwarded message 'The Quiet ECS Information List ...' Return-Path: <@ca.ualberta.cs.scapa:edm.isac.ca!steve@isagate> Received: from scapa.cs.ualberta.ca by susssys1.reading.ac.uk with SMTP (PP) id <15563-0@susssys1.reading.ac.uk>; Mon, 28 Jun 1993 22:58:59 +0100 Received: from isagate by scapa.cs.ualberta.ca with UUCP id <42373-1>; Mon, 28 Jun 1993 15:58:17 -0600 Received: by isagate.edm.isac.ca (/\==/\ Smail3.1.20.1 #20.1) id ; Mon, 28 Jun 93 10:04 MDT Received: from isa486-1 by isasun-1.edm.isac.ca with smtp (Smail3.1.26.7 #1) id m0oALlJ-000cwVC; Mon, 28 Jun 93 10:08 MDT Date: Mon, 28 Jun 1993 11:03:42 -0600 From: Steve Hole Subject: The Quiet ECS Information List ... To: ECS Information Message-ID: Priority: Normal X-Read-Ack: No X-Delivery-Ack: No MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY=Part9306281043B --Part9306281043B Content-Type: TEXT/PLAIN; charset=US-ASCII Several people have been asking me about how quiet the ecs-info list has been lately. It has been very quiet, primarily due to the work being done on the ECSMail version 2.00 release. The traffic has been on the ECS Alpha Testers list instead as they have been working with the new version of ECSMail for Windows. The number of people on this list have been restricted for all the standard reasons. A quick update on the status of ECSMail. Version 2.00 has been in alpha testing for 8 weeks now. That is 2 weeks longer than we wanted, but we were required to make some changes to the message display code to support reading bulletin boards (Usenet NEWS) effectively. We also had some very good suggestions made concerning the address book and compose function integration. The combined impact on the user interface has delayed the release of the Beta demonstration version of ECSMail. Work is proceeding on ECSMail for Macintosh and ECSMail for DOS. Both are scheduled to enter testing at the end of July. We are on target for both platforms. We are somewhat concerned that the strict interface conformance requirements of the Macintosh will cause delays in the production release. We have some very good help in that area from Alex Nishri at the U of T and a few others though. Besides being busy on the software, we have also been preparing a lot of documentation including: * Introductory and technical information on ECSMail * User manuals and guides * Pricing information I have attached a new text announcement document for ECSMail that tells people how to get these documents and who to contact in ISA. All formal documents concerned with ECSMail will be delivered in postscript format. Having said all this, I am leaving on a couple of weeks vacation. I will be back on July 12 and can be contacted then. I recommend that you send mail to the addresses in the attached document if you would like information while I am gone. We will be releasing a beta demonstration version 2.00 of ECSMail for Windows on July 14! It will be available at the locations listed in the attachment. Production release of ECSMail for Windows version 2.00 will be made on July 30. Pricing information for the ECSMail MUA Set can be obtained by contacting: ECS Sales More detailed information is provided in the attachment. Cheers. -- Steve Hole Director: Research and Development ISA Corp. Email: steve@edm.isac.ca --Part9306281043B Content-Type: TEXT/PLAIN; name="ANNOUNCE.TXT" ECSMail Announcement -------------------- ISA Corp. announces the release of the ECSMail componant of its Enterprisewide Communication Services. What is ECSMail? ---------------- ECSMail is an electronic mail product for building enterprise mail systems. It is designed from start to finish as a system for establishing mail services througout an organization, with external organizations and the world information system in general. It does this by using a completely standards based architecture. ECSMail is comprised of the following system components: ECSMail MUA Set - a set of Mail User Agents (MUA) ECSMail MTA Set - a set of Message Transport Agents (MTA) ECSMail MS Set - a set of Message Services (MS) ECSMail provides a robust set of features, including: * A distributed client/server architecture that separates message transport, message storage, and the user interface into separate applications. The applications communicate with each other using standards based application protocols. Messages are moved through the system using protocols inside of network file systems. * Multi-part, multimedia mail messages supporting both the MIME and X.400 message formats. Files (e.g. binaries, images, text, voice, application) can be attached and sent along with a message. Different parts of the messsage can be extracted and displayed (using the necessary application) to the user. Messages can be constructed with arbitrarily complex structures. * Multiple message service access and management. Message folders can be simultaneously accessed from any number of remote message services and from local disks. Entire folders or individual messages can be dragged and dropped between message services and folders. * Hierarchical folder structures. * Dynamic message grouping within folders. Messages can be grouped and sorted using any combination of message header criteria into a message group. Messages in a message group can be listed and manipulated as a single object. Message group messages can be displayed or hidden on command by a double mouse click or menu selection. * Integration of mail and bulletin boards (NEWS, BBS) message services in a single interface. Bulletin board message services (NEWS groups) appear as a list of folders and threading of broadcast messages will be supported. * Privancy Enhanced Mail (PEM). Message attachments can be securely encrypted using public key encryption. Digital signatures, and digital timestamps can be attached to message attachments or to the entire message. * Forms in mail. Messages can be composed inside of a forms interface as a special message part. ECSMail comes with a forms design and a builtin forms display tool. * Draft message support. Users will be able to create and store draft messages, and select draft messages from both public and private draft message stores. * Integration with "mail enabled applications". ECSMail supports the MAPI, VIM, and XAPIA interapplication communication standards. * Personal configuration files. * Message delivery services like: - Asynchronous new mail notification. - Delivery receipts (acknowledgments). - Read receipts (acknowledgments). - Message priorities. * Personal address book lookup and management. Addresses can be loaded manually, copied from incoming mail, or copied from a Directory User Agent (DUA). * Integration with Directory Services. The user can query local and network-wide address information while composing messages. Addresses can be copied from the Directory User Agent (DUA) to the user's local address book. This facility is provided using either X.500 or LDAP conformant DUAs. The ECSDirectory products provide the Directory Service components necessary for the integrated DUA lookup. The ECSMail MUA Set ------------------- The ECSMail MUA Set is a group of client user interfaces that run on a number of different platforms. ECSMail MUA can function as both a "remote" MUA and a "local" MUA. While functioning in remote mode, it will access a remote message service using standards based mail access protocols. In local mode, it will access a local message store using operating system dependent message service access routines. ECSMail is has been designed and implemented to be as independent as possible from operating system, display, and network protocols. We have achieved this by building driver libraries for the OS and displays, and using Mark Crispin's c-client drivers for message service access (both local and remote message stores). The ECSMail MUA Set will support the following operating system, display, and mail application protocol combinations: OS - Unix, DOS, Microsoft NT, Microsoft Windows, OS/2, Mac System 7, OpenVMS Displays - X11 (R4, R5, Motif), Microsoft Windows, Presentation Manager, Mac Finder, ASCII Character Formats - Internet message format (MIME, RFC822). X.400 (OSI) message format. Protocols - Internet mail protocols (SMTP, IMAP, NNTP). X.400 (OSI) mail protocols (P1, P7, P7+). The ECSMail MTA Set ------------------- The ECSMail MTA Set is a group of message transport agents (MTA) that run on a number of different "server" platforms. The MTA set is responsible for transporting messages between machines on the network. The ECSMail MTA Set will support the following operating system and mail application protocol combinations: OS - Unix, Microsoft NT, OS/2, OpenVMS Formats - Internet message format (MIME, RFC822). X.400 (OSI) message format. Protocols - Internet mail protocols (SMTP, NNTP). X.400 (OSI) mail protocols (P1). The MTA set is capable of translating between the Internet and X.400 message formats. Messages can be gatewayed between X.400 mail systems and Internet mail systems. The ECSMail MS Set ------------------ The ECSMail MS Set is a group of message servers (MS) that run on a number of different "server" platforms. The MS Set is responsible for managing messages stored on the mail server and providing access service to the MUA. MUA's manage remotely stored mail messages through the message service MS Set applications. The ECSMail MTA Set will support the following operating system and mail application protocol combinations: OS - Unix, Microsoft NT, OS/2, OpenVMS Formats - Internet message format (MIME, RFC822). X.400 (OSI) message format. Protocols - Internet mail protocols (IMAP). X.400 (OSI) mail protocols (P7, P7+). How Do I Get More Information? ------------------------------ More information is available from ISA on request. Related technical information documents that can be obtained from ISA include: * Enterprise Communications Service (ECS) Overview * Introduction to ECSMail * ECSMail Features Summary * Introduction to ECSDirectory * ECSDirectory Features Summary The technical documents can be obtained by contacting: ECS Publications Coordinator 835 10040 - 104 Street Edmonton, Alberta, Canada T5J 0Z2 Phone: 403-420-8081 Fax: 403-420-8037 or by sending a request through electronic mail to the address: ECS Publications Pricing for the ECS products and ISA business information can be obtained by contacting: ECS Sales 835 10040 - 104 Street Edmonton, Alberta, Canada T5J 0Z2 Phone: 403-420-8081 Fax: 403-420-8037 or by sending a request through electronic mail to the address: ECS Sales How Do I Get The Software? -------------------------- A demonstration version of the Microsoft Windows version of ECSMail is available via anonymous ftp from ftp.srv.ualberta.ca in the directory /pub/windows/utilities/ecs.tar.Z This version of ECSMail only supports the TCP/IP based mail access and transport protocols (IMAP2, SMTP), and can deliver MIME format messages. It provides only "basic functionality" - it does the things that most mailers do. Some of the advanced features are not implemented. See the readme.txt file in the distribution for a complete description of what features are implemented in the demo. We encourage you to get the software and try it out. This version of ecs is released for demonstration purposes only - IT IS NOT IN THE PUBLIC DOMAIN. Restrictions on the Software ---------------------------- The mailer is designed to support several different TCP/IP stacks through the use of dynamic link libraries (DLL). The demo software is Microsoft Windows based and supports the WinSock DLL interface. The following WinSock implementations are known to work with ECSMail MUA for Windows: * Beame and Whiteside - BWTCP 2.x, 3.x * FTP Software - PCTCP 2.2 * Microsoft TCP/IP - (BETA) * Novell Lan Workplace * Sun Microsystems - PCNFS 4.x, 5.x * SuperTCP 1.1 * NetManage Chameleon We are currently working on providing: * DEC Pathworks * (Public Domain) University of Waterloo - WatTCP Any compliant WinSock DLL implementation should work with ECSMail. Mailing lists ------------- Announcements and general discussion about ECSMail can be obtained from the ECS Information mailing list. To join the mailing list send a message to ecs-info-request@edm.isac.ca To submit messages to the mailing list, send mail to ecs-info@edm.isac.ca If there are problems with the list, then send mail to owner-ecs-info@edm.isac.ca ISA Corp. is a technology integration company that focuses on building and supporting standards based, distributed network applications. --Part9306281043B-- --587204512-1648954721-742563875:#17638-- From owner-pine-info@cac.washington.edu Tue Jul 13 08:44:07 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08097; Tue, 13 Jul 93 08:44:07 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05154; Tue, 13 Jul 93 08:28:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from emoryu1.cc.emory.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05150; Tue, 13 Jul 93 08:28:09 -0700 Received: by emoryu1.cc.emory.edu (5.65/Emory_cc.3.4.6) via MAILPROG id AA02168 ; Tue, 13 Jul 93 11:28:07 -0400 Return-Path: curt@unix.cc.emory.edu Date: Tue, 13 Jul 1993 11:27:40 -0400 (EDT) From: Curt Stauffer Subject: help To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: From owner-pine-info@cac.washington.edu Tue Jul 13 10:56:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13098; Tue, 13 Jul 93 10:56:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28833; Tue, 13 Jul 93 10:31:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28827; Tue, 13 Jul 93 10:31:33 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA05996; Tue, 13 Jul 93 10:31:29 -0700 Date: Tue, 13 Jul 1993 10:28:47 -0700 (PDT) From: Laurence Lundblade Subject: Re: inbox is "readonly", interrupted-mail is empty To: Lee Ann Sakihara Cc: Pine Information list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: This sounds like some problems with the way it was ported to Solaris 2.2. Both the locking and disconnect handling stuff vary from machine to machine. The locking stuff is in the c-client, in the os dependent files there, and the disconnect handling is in pine/signals.c. LL On 12 Jul 1993, Lee Ann Sakihara wrote: > > We are having a few problems running Pine 3.05 under Solaris 2.2 > (aka SunOS 5.2), at times the inbox becomes flagged as "readonly" and in > order to resolve the problem, we delete the file: > > /tmp/.\\var\\mail\\username > > This is a temporary solution, but we're wondering if we should > install pine 3.07 or if it has something to do with Solaris. > > The second problem we encountered is that when a session is > disconnected while composing a message. Normally pine creates the file > interrupted-mail which would contain the text of the message that was > being composed when the system was interrupted. What happens on our > system is the interrupted-mail file is created, but it contains 0 bytes. > > Any suggestions are welcome. Thanks in advance. > > Lee Ann M. Sakihara Internet: leeann@uhunix.uhcc.hawaii.edu > University of Hawaii Computing Center Bitnet: leeann@uhunix.bitnet > > > > > From owner-pine-info@cac.washington.edu Tue Jul 13 11:51:18 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15808; Tue, 13 Jul 93 11:51:18 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06198; Tue, 13 Jul 93 11:32:30 -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 AA06192; Tue, 13 Jul 93 11:32:28 -0700 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01386; Tue, 13 Jul 93 11:32:21 -0700 Date: Tue, 13 Jul 1993 11:24:42 -0700 (PDT) From: Mark Crispin Subject: Re: Pine Crashes To: Mike Roch Cc: pine-info@cac.washington.edu, sxsgilli@reading.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Hi Mike - Please accept our assurances on this point: If Pine crashes, for any reason, it is a bug. There is absolutely no intention on the part of the Pine team for any crash to be part of expected Pine behavior. Thus, asking us to change a Pine crash to ``can't display that message'' doesn't make much sense. If we knew that a particular condition made Pine crash, we'd fix the bug that caused the crash. We expect that in a few weeks there will be a major new release of Pine that fixes a great many bugs. Unlike 3.07, which was an interim release of patches to 3.05, the new Pine (probably 3.85) consists of major rewrites of large sections of the Pine and c-client code. We hope that this new release will be a great deal more featureful and bug-free; we've spent over a year working on it! From owner-pine-info@cac.washington.edu Tue Jul 13 12:42:53 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17761; Tue, 13 Jul 93 12:42:53 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00500; Tue, 13 Jul 93 12:23:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from world.std.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00494; Tue, 13 Jul 93 12:22:58 -0700 Received: by world.std.com (5.65c/Spike-2.0) id AA14722; Tue, 13 Jul 1993 15:01:25 -0400 Date: Tue, 13 Jul 1993 15:01:25 -0400 From: bzs@world.std.com (Barry Shein) Message-Id: <199307131901.AA14722@world.std.com> To: C.Martin@sheffield.ac.uk Cc: pine-info@cac.washington.edu In-Reply-To: Chris Martin's message of Tue, 13 Jul 93 08:57:54 BST <21429.9307130757@sunc.sheffield.ac.uk> Subject: emacs/rmail (babyl) -> pine folder? Status: O X-Status: From: Chris Martin >You can run Emacs again and then save the messages using C-o file RET >which "appends a copy of the current message to the file , >writing it in Unix mail format" Yes, that works one by one. The real problem here is that the person ran emacs/rmail on someone else's advice I guess and immediately decided she had no idea how to use it and didn't want to get into this so quit. But it had already grabbed all her messages. So she won't be able to go thru one by one, I suppose one of us could do this for her plus or minus the privacy issue (of course we'd ask, but she may not be thrilled and I wouldn't blame her.) Anyhow, I guess I was just as concerned for the NEXT time this happens, which I'll guess it inevitably will. Thanks. -Barry Shein Software Tool & Die | bzs@world.std.com | uunet!world!bzs Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD From owner-pine-info@cac.washington.edu Tue Jul 13 13:10:46 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18967; Tue, 13 Jul 93 13:10:46 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01033; Tue, 13 Jul 93 12:53:31 -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 AA01027; Tue, 13 Jul 93 12:53:30 -0700 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <11983-0@susssys1.reading.ac.uk>; Tue, 13 Jul 1993 20:53:04 +0100 Date: Tue, 13 Jul 1993 20:35:10 +0100 (BST) From: Mike Roch Subject: Re: Pine Crashes To: Mark Crispin Cc: pine-info@cac.washington.edu, sxsgilli@reading.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I didn't mean to nit-pick, Mark; I'm a fan! The reason for the suggestion is that Pine retains some dignity (control?) when crashing ("Abort signal received ....") so some sort of recovery (restart but refuse to re-open last message mentioned in .pine-debug ?) seemed possible. I can see that if Pine can't tell that it crashed because of message/header content this isn't much help, but that's always been the cause we've seen here. Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AX. Fax: 0734 753094 From owner-pine-info@cac.washington.edu Tue Jul 13 13:35:01 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19745; Tue, 13 Jul 93 13:35:01 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06871; Tue, 13 Jul 93 13:14:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06865; Tue, 13 Jul 93 13:14:55 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01468; Tue, 13 Jul 93 13:14:45 -0700 Date: Tue, 13 Jul 1993 13:08:15 -0700 (PDT) From: Mark Crispin Subject: Re: Pine Crashes To: Mike Roch Cc: pine-info@cac.washington.edu, sxsgilli@reading.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Mike - Usually, the crashes have been things such as false pointer calculations, chasing null pointers, buffer overruns -- the usual stuff that creeps into C programs no matter how careful the programmer may be. Pine traps various exception signals, but generally at this point it hasn't a clue as to how it happened or what damage may have been done to its internal data structures (this latter point is important; if a boundary condition error caused a loop to romp through memory, you don't want Pine doing further write to the folder based upon that clobbered data!). The ``abort signal received...'' is essentially a replacement for the default behavior, which is usually something like ``segmentation violation (core dumped)'' or ``IOT trap (core dumped)'' etc. The only real ``dignity'' that Pine retains in this case is some sort of restoration of terminal modes, etc; if you've ever had an emacs crash and leave your terminal in a wierd state you'd understand what I'm talking about. There are a few internal consistency checks in Pine which trigger error conditions, and there is recovery code such as you suggest. Anyway, our intent is to stomp out all of these bugs. Pine 3.05 has several known bugs which cause this; 3.07 has somewhat fewer; we think the latest version has none. Coming soon to an FTP server near you... -- Mark -- From owner-pine-info@cac.washington.edu Tue Jul 13 13:57:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20384; Tue, 13 Jul 93 13:57:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01665; Tue, 13 Jul 93 13:36:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bwc.bwc.org.il by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01658; Tue, 13 Jul 93 13:35:58 -0700 Received: from saturn.bwc.org (saturn.bwc.org.il) by bwc.bwc.org with SMTP id AA11457 (5.65c/IDA-1.4.4 for ); Tue, 13 Jul 1993 23:36:59 +0300 Received: by saturn.bwc.org (4.1/SMI-4.1) id AA22997; Tue, 13 Jul 93 23:36:59 IDT Date: Tue, 13 Jul 1993 23:07:42 +0300 (IDT) From: Bob Gregory Subject: Re: emacs/rmail (babyl) -> pine folder? To: pine-info@cac.washington.edu In-Reply-To: <21429.9307130757@sunc.sheffield.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Tue, 13 Jul 1993, Chris Martin wrote: > You can run Emacs again and then save the messages using C-o file RET > which "appends a copy of the current message to the file , > writing it in Unix mail format" The method described works, but is tedious to type. What I do is define an emacs keyboard macro, e.g. (fset 'rmail2bezerk "/tmp/mbox d") Which stores the current message in bezerk folder "/tmp/mbox", and marks it for deletion. In RMAIL mode, map the macro to a suitable key, e.g. (local-set-key "e" (quote rmail2bezerk)) I use "e", because "x" is redundantly mapped to "expunge", and because it is adjacent to "d". This makes it real easy to browse a babyl folder and delete, or copy and delete, each message - cleanup as you convert. I suppose something like this can be written properly in elisp with a mode to do a whole folder, but I'm not enough of an emacs hack, and the above was good enough for me. -- Bob Gregory From owner-pine-info@cac.washington.edu Tue Jul 13 21:04:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02561; Tue, 13 Jul 93 21:04:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06262; Tue, 13 Jul 93 20:54:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06256; Tue, 13 Jul 93 20:54:49 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA03124; Tue, 13 Jul 93 20:54:45 -0700 Date: Tue, 13 Jul 1993 20:46:55 -0700 (PDT) From: Laurence Lundblade Subject: Re: Arrow keys To: Paul Maclauchlan Cc: Pine Info mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Hello, If the arrow keys don't work you can always use ^F, ^B, ^N, ^P (emacs cursor motion keys) in place of ->, <-, \/, and ^. Pine accepts the arrow key escape sequences for most of the common terminals including at least two generated by vtxxx terminals. It also doesn't depend on any configuration like termcap, so the problem is probably on his end or the network connection. The RDF DENIED is not a Pine error message. LL On 12 Jul 1993, Paul Maclauchlan wrote: > > I have a user in Australia, coming into my system via Infonet's packet > switch network. He usually connects via a direct call from in town. > > He reports that the arrow keys no longer work. His PC comms software > (ProComm) is set to VT100 emulation, and so is his account. > > Any ideas what could cause this? Any work-arounds? > > BTW, I typically use Pine via ProComm from Windows with vt100 emulation. > > Also, he reports an error message: "RDF DENIED", and then his connection > froze. Is this a Pine error message? > > Thanks for any help you can offer. > > -- > .../Paul Maclauchlan > Moore Corporation Limited, Toronto, Ontario (416) 364-2600 > paul@moore.com -or- {...!uunet.ca,...!telly}!moore!paul > "We're too busy singing to put anybody down." The Monkees > > > > From owner-pine-info@cac.washington.edu Wed Jul 14 05:41:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11661; Wed, 14 Jul 93 05:41:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08992; Wed, 14 Jul 93 05:28:02 -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 AA08986; Wed, 14 Jul 93 05:28:00 -0700 Via: uk.ac.durham; Wed, 14 Jul 1993 13:27:23 +0100 Received: from vega.dur.ac.uk by durham.ac.uk; Wed, 14 Jul 93 13:27:48 +0100 Received: from wansbeck.dur.ac.uk by vega.dur.ac.uk; Wed, 14 Jul 93 13:27:13 BST Date: Wed, 14 Jul 1993 13:22:11 +0100 (BST) From: Barry Cornelius Subject: PC-Pine To: pine-info@cac.washington.edu Cc: John Martin Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I tried PC-Pine Release 3.84 yesterday. I used it as follows: (a) with LANWorkPlace for Dos (on a standalone PC rather than a Novell-networked PC), (b) with the existing IMAP daemon running on a Sun (i.e., the one that comes with Pine 3.07 rather than the new version of IMAP). This experiment was successful: after asking for my username and password, I was able to read my inbox from the Unix machine containing mailboxes. It was reasonably fast. When PC-Pine started up the first time, it asked me for values for the user-id, personal-name and user-domain variables. I supplied appropriate values and these were stored in the \PINE\PINERC file. These values are used to generate the From line of a message. Later, I changed the settings of these variables in the PINERC file. I was then able to send messages masquerading as someone else. This is not desirable! Have I got something wrong? Is there anyway in which this can be avoided? -- 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 Jul 14 08:40:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02097; Wed, 14 Jul 93 08:40:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10382; Wed, 14 Jul 93 08:27:27 -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 AA10376; Wed, 14 Jul 93 08:27:25 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00533; Wed, 14 Jul 93 08:26:59 -0700 Date: Wed, 14 Jul 1993 08:20:05 -0700 (PDT) From: David L Miller Subject: Re: PC-Pine To: Barry Cornelius Cc: pine-info@cac.washington.edu, John Martin In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Unfortunately, from a PC there is no way to enforce things like user-id, etc. No matter what we do (short of PEM or other secure mail system) we will always have authentication problems with PC-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 15tn Ave NE, Seattle WA 98105, USA On Wed, 14 Jul 1993, Barry Cornelius wrote: > I tried PC-Pine Release 3.84 yesterday. I used it as follows: > > (a) with LANWorkPlace for Dos (on a standalone PC rather than > a Novell-networked PC), > > (b) with the existing IMAP daemon running on a Sun (i.e., the one > that comes with Pine 3.07 rather than the new version of IMAP). > > This experiment was successful: after asking for my username and password, > I was able to read my inbox from the Unix machine containing mailboxes. It > was reasonably fast. > > When PC-Pine started up the first time, it asked me for values for the > user-id, personal-name and user-domain variables. I supplied appropriate > values and these were stored in the \PINE\PINERC file. These values are > used to generate the From line of a message. > > Later, I changed the settings of these variables in the PINERC file. I was then > able to send messages masquerading as someone else. This is not desirable! > Have I got something wrong? Is there anyway in which this can be avoided? > > -- > 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 Jul 14 11:31:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08535; Wed, 14 Jul 93 11:31:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13099; Wed, 14 Jul 93 10:50:27 -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 AA13093; Wed, 14 Jul 93 10:50:24 -0700 Received: from carlisle.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <21398-0@Rye.city.ac.uk>; Wed, 14 Jul 1993 18:40:15 +0100 Date: Wed, 14 Jul 1993 18:47:22 +0100 (BST) From: "D.K.Brownlee" Subject: PC-Pine authentication To: David L Miller Cc: Barry Cornelius , pine-info@cac.washington.edu, John Martin In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Wouldn't it be possible to make PC-Pine ensure it had connected to the IMAP server & validated the user account & password that way before sending any mail - ie 1st time in a session the user goes to send a mail message, if they have not previously in that session read their inbox pcpine does some form of test-connect to the IMAP server to ensure their account details are valid? 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. On Wed, 14 Jul 1993, David L Miller wrote: > > Unfortunately, from a PC there is no way to enforce things like user-id, > etc. No matter what we do (short of PEM or other secure mail system) we > will always have authentication problems with PC-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 15tn Ave NE, Seattle WA 98105, USA > > > On Wed, 14 Jul 1993, Barry Cornelius wrote: > > > I tried PC-Pine Release 3.84 yesterday. I used it as follows: > > > > (a) with LANWorkPlace for Dos (on a standalone PC rather than > > a Novell-networked PC), > > > > (b) with the existing IMAP daemon running on a Sun (i.e., the one > > that comes with Pine 3.07 rather than the new version of IMAP). > > > > This experiment was successful: after asking for my username and password, > > I was able to read my inbox from the Unix machine containing mailboxes. It > > was reasonably fast. > > > > When PC-Pine started up the first time, it asked me for values for the > > user-id, personal-name and user-domain variables. I supplied appropriate > > values and these were stored in the \PINE\PINERC file. These values are > > used to generate the From line of a message. > > > > Later, I changed the settings of these variables in the PINERC file. I was then > > able to send messages masquerading as someone else. This is not desirable! > > Have I got something wrong? Is there anyway in which this can be avoided? > > > > -- > > 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 Jul 14 12:25:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10413; Wed, 14 Jul 93 12:25:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14497; Wed, 14 Jul 93 12:13: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 AA14491; Wed, 14 Jul 93 12:13:57 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03048; Wed, 14 Jul 93 12:13:56 -0700 Date: Wed, 14 Jul 1993 12:12:21 -0700 (PDT) From: Steve Hubert Subject: Re: Pine Crashes To: Mark Crispin Cc: Mike Roch , pine-info@cac.washington.edu, sxsgilli@reading.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: > Anyway, our intent is to stomp out all of these bugs. Pine 3.05 has > several known bugs which cause this; 3.07 has somewhat fewer; we think the > latest version has none. Now that's optimism! From owner-pine-info@cac.washington.edu Wed Jul 14 13:06:24 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11652; Wed, 14 Jul 93 13:06:24 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14884; Wed, 14 Jul 93 12:43:41 -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 AA14878; Wed, 14 Jul 93 12:43:38 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA29219; Wed, 14 Jul 93 12:43:36 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA20535; Wed, 14 Jul 93 12:43:36 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA19485; Wed, 14 Jul 93 12:43:35 PDT Date: Wed, 14 Jul 93 12:43:35 PDT From: ekurgpol@Law.USC.EDU (Elmar Kurgpold) Message-Id: <9307141943.AA19485@develop.Law.USC.EDU> To: pine-info@cac.washington.edu Subject: Port to PC-NFS?? Status: O X-Status: Any hope of running PC-Pine on PC-NFS? ------------------------- | Elmar Kurgpold | | Network Administrator | | USC Law Center | | ekurgpol@Law.USC.EDU | | (213)740-5709 | | (213)740-5502 FAX | ------------------------- From owner-pine-info@cac.washington.edu Wed Jul 14 14:07:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14727; Wed, 14 Jul 93 14:07:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16016; Wed, 14 Jul 93 13:52: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 AA16010; Wed, 14 Jul 93 13:52:37 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07702; Wed, 14 Jul 93 13:52:26 -0700 Date: Wed, 14 Jul 1993 13:46:47 -0700 (PDT) From: David L Miller Subject: Re: PC-Pine authentication To: "D.K.Brownlee" Cc: Barry Cornelius , pine-info@cac.washington.edu, John Martin In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: That just makes them get a little more creative. There are so many loopholes in current email *transport* mechanisms that anything you do on a user agent (like pine) is just window dressing. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Wed, 14 Jul 1993, D.K.Brownlee wrote: > > Wouldn't it be possible to make PC-Pine ensure it had connected to the > IMAP server & validated the user account & password that way before > sending any mail - ie 1st time in a session the user goes to send > a mail message, if they have not previously in that session read > their inbox pcpine does some form of test-connect to the IMAP server > to ensure their account details are valid? > > 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. > > > On Wed, 14 Jul 1993, David L Miller wrote: > > > > > Unfortunately, from a PC there is no way to enforce things like user-id, > > etc. No matter what we do (short of PEM or other secure mail system) we > > will always have authentication problems with PC-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 15tn Ave NE, Seattle WA 98105, USA > > > > > > On Wed, 14 Jul 1993, Barry Cornelius wrote: > > > > > I tried PC-Pine Release 3.84 yesterday. I used it as follows: > > > > > > (a) with LANWorkPlace for Dos (on a standalone PC rather than > > > a Novell-networked PC), > > > > > > (b) with the existing IMAP daemon running on a Sun (i.e., the one > > > that comes with Pine 3.07 rather than the new version of IMAP). > > > > > > This experiment was successful: after asking for my username and password, > > > I was able to read my inbox from the Unix machine containing mailboxes. It > > > was reasonably fast. > > > > > > When PC-Pine started up the first time, it asked me for values for the > > > user-id, personal-name and user-domain variables. I supplied appropriate > > > values and these were stored in the \PINE\PINERC file. These values are > > > used to generate the From line of a message. > > > > > > Later, I changed the settings of these variables in the PINERC file. I was then > > > able to send messages masquerading as someone else. This is not desirable! > > > Have I got something wrong? Is there anyway in which this can be avoided? > > > > > > -- > > > 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 Jul 14 14:22:01 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15125; Wed, 14 Jul 93 14:22:01 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16235; Wed, 14 Jul 93 14:08:34 -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 AA16227; Wed, 14 Jul 93 14:08:33 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08002; Wed, 14 Jul 93 14:08:27 -0700 Date: Wed, 14 Jul 1993 14:06:41 -0700 (PDT) From: David L Miller Subject: Re: Port to PC-NFS?? To: Elmar Kurgpold Cc: pine-info@cac.washington.edu In-Reply-To: <9307141943.AA19485@develop.Law.USC.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: We've got the developer's kit, but we decided to get the others working before we tackled yet another version. If demand is great enough, we may include PC-NFS support in future releases. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Wed, 14 Jul 1993, Elmar Kurgpold wrote: > Any hope of running PC-Pine on PC-NFS? > > ------------------------- > | Elmar Kurgpold | > | Network Administrator | > | USC Law Center | > | ekurgpol@Law.USC.EDU | > | (213)740-5709 | > | (213)740-5502 FAX | > ------------------------- > From owner-pine-info@cac.washington.edu Wed Jul 14 14:31:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15489; Wed, 14 Jul 93 14:31:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16370; Wed, 14 Jul 93 14:17: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 AA16364; Wed, 14 Jul 93 14:17:51 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08103; Wed, 14 Jul 93 14:17:50 -0700 Date: Wed, 14 Jul 1993 14:14:52 -0700 (PDT) From: David L Miller Subject: Ultrix Quota fix for 3.07 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I think this has been posted before, and it will be fixed in the next release, but here is a simple fix to make quota checking in Pine work under Ultrix: -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA -------- Start of diff -------- *** pine3.07/pine/os-unx.c Thu Jul 9 09:50:46 1992 --- pine3.07a/pine/os-unx.c Mon Apr 5 10:40:48 1993 *************** *** 622,627 **** --- 622,628 ---- dprint(7, (debugfile, "Quota check: UID:%d stat: %d %x\n", getuid(), statx.st_dev, statx.st_dev)); + memset((void *)"ax, 0, sizeof(struct dqblk)); if(quota(Q_GETDLIM, getuid(), statx.st_dev, "ax) < 0) { dprint(5, (debugfile, "Quota failed : %s\n", error_description(errno))); -------- End of diff -------- From owner-pine-info@cac.washington.edu Wed Jul 14 14:40:42 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15926; Wed, 14 Jul 93 14:40:42 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13393; Wed, 14 Jul 93 14:26:53 -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 AA13387; Wed, 14 Jul 93 14:26:50 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA24766; Wed, 14 Jul 1993 16:29:26 -0500 Date: Wed, 14 Jul 1993 16:24:27 -0500 (CDT) From: "Robert A. Hayden" Subject: .signature options To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: This is something that I'd like to see in pine (among many other thing). If, when adding an address, you could also toggle a Y/N .signature flag. The reason is that when doing administrative work on several of my mailing lists, it becomes old to have to edit out my .sig every time (because the server gets mad if you have error producing lines). -- Building on that, a field in the address file allowing you to designate one of several signatures would also be interesting. (say one field you edit with a number 0-9 or an N, default being 0. You then have a seperate file or as part of the .pinerc where you can designate each # as a different file.) Could be nice for companies where anything going outside local needs to have a large disclaimer, while in house then need little or nothing on the end. {[> Robert A. Hayden ____ hayden@krypton.mankato.msus.edu <]} {[> \ /__ hayden@att2.cs.mankato.msus.edu <]} {[> \/ / aq650@slc4.INS.CWRU.Edu <]} {[> #include \/ <]} -=-=- (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Random Thought: Beauty is only skin deep, but Ugly goes straight to the bone. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From owner-pine-info@cac.washington.edu Wed Jul 14 15:01:10 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16600; Wed, 14 Jul 93 15:01:10 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13555; Wed, 14 Jul 93 14:51: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 AA13549; Wed, 14 Jul 93 14:51:27 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA03187; Wed, 14 Jul 93 14:51:08 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA00811; Wed, 14 Jul 93 14:51:00 -0700 Date: Wed, 14 Jul 1993 14:20:49 -0700 (PDT) From: Mark Crispin Subject: Re: PC-Pine authentication To: David L Miller Cc: "D.K.Brownlee" , Barry Cornelius , pine-info@cac.washington.edu, John Martin In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I need to step in on this discussion before it gets too far out of hand and too many misunderstandings arise. The issue of authentication of outgoing mail messages is an important one, and we treat it as such. We consider it to be of great importance that an authentication mechanism be trustworthy. [On a personal note: I was once ejected from a computer system and subjected to disciplinary action for an act I did not commit, on the basis of falsified authentication data. Although I might wish that system administrators have become a bit more cognizant of reality in the intervening two decades, this has not happened. If anything, they're even more clueless today.] ``Trustworthy'' means that authentication must give a reasonable assurance of accuracy. Most of the proposed mechanisms to accomplish authentication are feel-good kludges that are easily circumvented and break another capability. This does not mean that we have thrown up our hands and said ``it's impossible so forget it.'' Rather, we *will* provide an outgoing message authentication mechanism in future releases. This will include mailer patches so it will be possible to distinguish between messages which have been authenticated and non-authenticated messages. It is important to understand that PC Pine does *NOT* introduce any new authentication problems. These problems have always been there, since the beginnings of ARPAnet e-mail over 20 years ago. It is only recently that we all have become sensitized to this problem and the urgency of its fix. Please be assured that a fix *will* be forthcoming. We have been dealing with the problem, and its consequences, for some time now and it is reaching the point of urgency. It is just that the fix must be an infrastructure fix, not a PC Pine fix. Regards, -- Mark -- From owner-pine-info@cac.washington.edu Wed Jul 14 15:06:56 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16810; Wed, 14 Jul 93 15:06:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13569; Wed, 14 Jul 93 14:57:44 -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 AA13563; Wed, 14 Jul 93 14:57:16 -0700 Received: by digi.syd.deg.csiro.au id AA11166 (5.65c/IDA-1.4.4); Thu, 15 Jul 1993 07:58:56 +1000 Date: Thu, 15 Jul 1993 07:55:23 +1000 (EST) From: Jack Churchill Subject: Re: Port to PC-NFS?? To: David L Miller Cc: Elmar Kurgpold , 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, 14 Jul 1993, David L Miller wrote: > We've got the developer's kit, but we decided to get the others working > before we tackled yet another version. If demand is great enough, we > may include PC-NFS support in future releases. What would a pc-nfs version actually provide that the DOS version doesn't? Do you mean it will be a Windows-API application like PC-Eudora? 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 Wed Jul 14 15:50:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17896; Wed, 14 Jul 93 15:50:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17581; Wed, 14 Jul 93 15:37:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bwc.bwc.org.il by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17563; Wed, 14 Jul 93 15:37:03 -0700 Received: from saturn.bwc.org (saturn.bwc.org.il) by bwc.bwc.org with SMTP id AA15051 (5.65c/IDA-1.4.4); Thu, 15 Jul 1993 01:38:17 +0300 Received: by saturn.bwc.org (4.1/SMI-4.1) id AA02148; Thu, 15 Jul 93 01:38:16 IDT Date: Thu, 15 Jul 1993 01:36:04 +0300 (IDT) From: Bob Gregory Subject: Re: Port to PC-NFS?? To: David L Miller Cc: Elmar Kurgpold , 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: Hey, If you're soliciting interest, we would *definitely* like to see PC-Pine running over PC/NFS! Bob Gregory Data Processing Department Domain Baha'i World Centre FAX 972(4)358525 TELEX 922-46626(BAYT IL) Admin P.O. Box 155 VOICE 972(4)358419 DIALCOM 5005:BAI001 Bwc.Org 31-001 Haifa, ISRAEL SCUD 33 20" N. / 44 26" E. On Wed, 14 Jul 1993, David L Miller wrote: > > We've got the developer's kit, but we decided to get the others working > before we tackled yet another version. If demand is great enough, we > may include PC-NFS support in future releases. > > -- > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > > On Wed, 14 Jul 1993, Elmar Kurgpold wrote: > > > Any hope of running PC-Pine on PC-NFS? > > > > ------------------------- > > | Elmar Kurgpold | > > | Network Administrator | > > | USC Law Center | > > | ekurgpol@Law.USC.EDU | > > | (213)740-5709 | > > | (213)740-5502 FAX | > > ------------------------- > > > From owner-pine-info@cac.washington.edu Wed Jul 14 15:59:45 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18150; Wed, 14 Jul 93 15:59:45 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13853; Wed, 14 Jul 93 15:51:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cse.ogi.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13847; Wed, 14 Jul 93 15:51:31 -0700 Received: by ogicse.cse.ogi.edu (/\==/\ Smail3.1.25.1 #25.4) id ; Wed, 14 Jul 93 15:51 PDT Received: by admin.ogi.edu.ogi.edu (4.1/SMI-4.1) id AA03030; Wed, 14 Jul 93 15:51:29 PDT Date: Wed, 14 Jul 1993 15:51:06 -0700 (PDT) From: Jon Crowhurst Subject: Please unsubscribe me To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-=--=--=--=--=--=--=-- Jon Crowhurst (503) 690-1035 crowhurs@admin.ogi.edu Oregon Graduate Institute, 20000 NW Walker Road, Beaverton, OR 97006 --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-=--=--=--=--=--=--=-- From owner-pine-info@cac.washington.edu Wed Jul 14 16:02:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18238; Wed, 14 Jul 93 16:02:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17760; Wed, 14 Jul 93 15:51:54 -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 AA17754; Wed, 14 Jul 93 15:51:52 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09833; Wed, 14 Jul 93 15:51:41 -0700 Date: Wed, 14 Jul 1993 15:41:17 -0700 (PDT) From: David L Miller Subject: Re: Port to PC-NFS?? To: Jack Churchill Cc: Elmar Kurgpold , 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: I guess I was a little vague (and slightly mis-informed) on my previous post. The network protocol stacks supported in the current release are PC-TCP from FTP Software, LAN WorkPlace from Novell, and WATTCP from U. Waterloo. PC-NFS from Sun will be supported *very* soon. Other than running on the different vendor's stacks, the versions are identical. Windows support is a whole different subject that we have not thoroughly investigated yet. Hopefully we will have a bit better handle on the effort required than we had on the DOS port before we jump in with both feet ;^) -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 15 Jul 1993, Jack Churchill wrote: > On Wed, 14 Jul 1993, David L Miller wrote: > > > We've got the developer's kit, but we decided to get the others working > > before we tackled yet another version. If demand is great enough, we > > may include PC-NFS support in future releases. > > What would a pc-nfs version actually provide that the DOS version doesn't? > Do you mean it will be a Windows-API application like PC-Eudora? > > 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 Wed Jul 14 16:04:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18344; Wed, 14 Jul 93 16:04:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17803; Wed, 14 Jul 93 15:55:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from louie.udel.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17795; Wed, 14 Jul 93 15:54:58 -0700 Received: from apache.dtcc.edu by louie.udel.edu id aa11965; 14 Jul 93 18:52 EDT Received: from weave by apache.dtcc.edu (5.4.2/5.40/1.0) id AA28701; Wed, 14 Jul 1993 18:52:35 -0400 Date: Wed, 14 Jul 1993 18:45:24 PDT From: Ken Weaverling Subject: [PARSE] Junk at end of address To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I am typing this with the new PC version of Pine. That's the good news! It is giving me parse errors when loading my inbox. They occur on some funky To: lines that I get on mail from Digital's "Easynet" The error message looks like... [{pima.dtcc.edu}INBOX [PARSE] Junk at end of address: @cop.dec.com (@kw)] The actual mail in my mail file looks like... To: mail11.;@cop.dec.com (@kw) The way pine displays it is.... To: mail11.@pima.dtcc.edu; Pine 3.07 doesn't give the error, but munges the line identically. Other mail agents don't choke on it, including mailx, elm, and mush. The sender claims she sets up a mail alias for me on their VMS mail and she just sends to the alias. It always arrives without a problem. P.S. On the authentication problem, I realize that it is easy to spoof mail, but we shouldn't make it TOO easy. One should be required to login to the imapd server to send mail and then use that login id at least to construct the From: line. From owner-pine-info@cac.washington.edu Wed Jul 14 16:05:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18414; Wed, 14 Jul 93 16:05:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17789; Wed, 14 Jul 93 15:54: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 AA17783; Wed, 14 Jul 93 15:54:34 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09849; Wed, 14 Jul 93 15:54:22 -0700 Date: Wed, 14 Jul 1993 15:52:28 -0700 (PDT) From: David L Miller Subject: Re: Port to PC-NFS?? To: Bob Gregory Cc: Elmar Kurgpold , 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: It is coming very soon. I had mis-interpreted the current status of the PC-NFS version when I sent that message. So hang on, it's almost 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 15 Jul 1993, Bob Gregory wrote: > Hey, > > If you're soliciting interest, we would *definitely* like to see PC-Pine > running over PC/NFS! > > Bob Gregory Data Processing Department > Domain Baha'i World Centre FAX 972(4)358525 TELEX 922-46626(BAYT IL) > Admin P.O. Box 155 VOICE 972(4)358419 DIALCOM 5005:BAI001 > Bwc.Org 31-001 Haifa, ISRAEL SCUD 33 20" N. / 44 26" E. > > > On Wed, 14 Jul 1993, David L Miller wrote: > > > > > We've got the developer's kit, but we decided to get the others working > > before we tackled yet another version. If demand is great enough, we > > may include PC-NFS support in future releases. > > > > -- > > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > > > > > On Wed, 14 Jul 1993, Elmar Kurgpold wrote: > > > > > Any hope of running PC-Pine on PC-NFS? > > > > > > ------------------------- > > > | Elmar Kurgpold | > > > | Network Administrator | > > > | USC Law Center | > > > | ekurgpol@Law.USC.EDU | > > > | (213)740-5709 | > > > | (213)740-5502 FAX | > > > ------------------------- > > > > > > > > > From owner-pine-info@cac.washington.edu Wed Jul 14 16:07:27 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18498; Wed, 14 Jul 93 16:07:27 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17589; Wed, 14 Jul 93 15:37:26 -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 AA17583; Wed, 14 Jul 93 15:37:25 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09547; Wed, 14 Jul 93 15:37:21 -0700 Date: Wed, 14 Jul 1993 15:35:11 -0700 (PDT) From: David L Miller Subject: Re: .signature options To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: The first option has been decided against to keep the number of queries to a minimum. Either option is valid, we just decided to go the other way. Something related to variable signatures may be possible 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 15tn Ave NE, Seattle WA 98105, USA On Wed, 14 Jul 1993, Robert A. Hayden wrote: > This is something that I'd like to see in pine (among many other thing). > > If, when adding an address, you could also toggle a Y/N .signature flag. > The reason is that when doing administrative work on several of my mailing > lists, it becomes old to have to edit out my .sig every time (because the > server gets mad if you have error producing lines). > > -- > > Building on that, a field in the address file allowing you to designate > one of several signatures would also be interesting. (say one field you > edit with a number 0-9 or an N, default being 0. You then have a seperate > file or as part of the .pinerc where you can designate each # as a > different file.) Could be nice for companies where anything going outside > local needs to have a large disclaimer, while in house then need little or > nothing on the end. > > {[> Robert A. Hayden ____ hayden@krypton.mankato.msus.edu <]} > {[> \ /__ hayden@att2.cs.mankato.msus.edu <]} > {[> \/ / aq650@slc4.INS.CWRU.Edu <]} > {[> #include \/ <]} > -=-=- > (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Random Thought: > > Beauty is only skin deep, but Ugly goes straight to the bone. > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > > From owner-pine-info@cac.washington.edu Wed Jul 14 16:12:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18659; Wed, 14 Jul 93 16:12:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17938; Wed, 14 Jul 93 16:03:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17932; Wed, 14 Jul 93 16:03:23 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA04880; Wed, 14 Jul 93 16:03:22 -0700 Date: Wed, 14 Jul 1993 15:59:36 -0700 (PDT) From: Laurence Lundblade Subject: Re: .signature options To: Pine Info Cc: David L Miller , "Robert A. Hayden" In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: If you put your signature in a file called ".s" or something else nice and short all you have to do is type four characters: ^R . s RETURN to have it inserted where you want. You could have several of them too: .s1 .s2 .s3 .... Not real fancy and automatic, but workable. LL > On Wed, 14 Jul 1993, Robert A. Hayden wrote: > > > This is something that I'd like to see in pine (among many other thing). > > > > If, when adding an address, you could also toggle a Y/N .signature flag. > > The reason is that when doing administrative work on several of my mailing > > lists, it becomes old to have to edit out my .sig every time (because the > > server gets mad if you have error producing lines). > > From owner-pine-info@cac.washington.edu Wed Jul 14 16:50:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20230; Wed, 14 Jul 93 16:50:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18513; Wed, 14 Jul 93 16:39:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from louie.udel.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18505; Wed, 14 Jul 93 16:39:13 -0700 Received: from apache.dtcc.edu by louie.udel.edu id aa13483; 14 Jul 93 19:37 EDT Received: from weave by apache.dtcc.edu (5.4.2/5.40/1.0) id AA29210; Wed, 14 Jul 1993 19:37:09 -0400 Date: Wed, 14 Jul 1993 19:17:11 PDT From: Ken Weaverling Subject: To: Pine Info Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Some thoughts on PC Pine... Many of our faculty work in two person offices with one PC. Others may also share PCs, like someone jumping on the secretary's PC. I won't even go into the horrors of thousands of students using PCs all over campus. With the PC port of Pine, it assumes one user to one computer. The pinerc file has info like full name, user name, etc... Isn't there someway to get this information from the imap server when the user logs in to the INBOX? Can't you take the username used and get full name info somehow by either using the SMTP port to do EXPN commands or using NIS somehow? Or, allow me as a sys admin to put a global configuration file somewhere and let pine query it for the additional items based on the username used to login. I can then store and maintain a copy on a PC file server somewhere. Another thought, forcing file\path naming (\pine for example) is a drag in a school environment. I would rather be able to somehow specify where the configuration files and even mail folder is via an environment variable. I am not sure about the feasibility of some of these suggestions. I just thought I'd throw them up for discussion. From owner-pine-info@cac.washington.edu Wed Jul 14 17:27:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21220; Wed, 14 Jul 93 17:27:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18958; Wed, 14 Jul 93 17:12:48 -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 AA18952; Wed, 14 Jul 93 17:12:43 -0700 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA07708; Wed, 14 Jul 93 19:12:36 CDT Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA11326; Thu, 15 Jul 93 08:07:09 +0800 Date: Thu, 15 Jul 1993 08:05:46 +0800 (TPE) From: Ed Greshko Subject: Re: Pine Crashes To: Steve Hubert Cc: Mark Crispin , Mike Roch , pine-info@cac.washington.edu, sxsgilli@reading.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Wed, 14 Jul 1993, Steve Hubert wrote: > > Anyway, our intent is to stomp out all of these bugs. Pine 3.05 has > > several known bugs which cause this; 3.07 has somewhat fewer; we think the > > latest version has none. > > Now that's optimism! > No, that's confidence......or wishful thinking.... :-) :-) 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 Jul 14 16:56:41 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20344; Wed, 14 Jul 93 16:56:41 -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 AA20338; Wed, 14 Jul 93 16:56:38 -0700 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 15 Jul 93 01:51:08+0200 Date: 15 Jul 93 01:51:08+0200 From: Ken Weaverling Message-Id: <356909*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine Info Mailing List Status: O X-Status: From owner-pine-info@cac.washington.edu Wed Jul 14 17:38:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21428; Wed, 14 Jul 93 17:38:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19109; Wed, 14 Jul 93 17:28:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from camembert.syd.deg.CSIRO.AU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19103; Wed, 14 Jul 93 17:28:05 -0700 Received: by camembert.syd.deg.csiro.au id AA04490 (5.65c/IDA-1.4.4 for Pine Info Mailing List ); Thu, 15 Jul 1993 10:27:34 +1000 Date: Thu, 15 Jul 1993 10:26:34 +1000 (EST) From: Jack Churchill Reply-To: Jack Churchill Subject: Re: your mail To: Ken Weaverling Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Status: O X-Status: On Wed, 14 Jul 1993, Ken Weaverling wrote: > Some thoughts on PC Pine... > > Many of our faculty work in two person offices with one PC. Others may > also share PCs, like someone jumping on the secretary's PC. I won't even > go into the horrors of thousands of students using PCs all over campus. > > With the PC port of Pine, it assumes one user to one computer. The pinerc > file has info like full name, user name, etc... I haven't looked into yet but perhaps one way around it for those servers using IDA-Sendmail is to use the xaliases file to remap the From field to what the sysadmin wants by way of the hidden_hosts and/or pseudonyms file. 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 Wed Jul 14 19:03:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22766; Wed, 14 Jul 93 19:03:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19789; Wed, 14 Jul 93 18:55:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from rip.hrb.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19783; Wed, 14 Jul 93 18:55:52 -0700 Received: from icf2.hrb.com by RIP.HRB.COM (PMDF V4.2-11 #4198) id <01H0JQIABS1S0007YF@RIP.HRB.COM>; Wed, 14 Jul 1993 21:55:32 EDT Received: from icf.hrb.com by icf.hrb.com (PMDF V4.2-11 #4198) id <01H0JQ6TVH34DZ6L6I@icf.hrb.com>; Wed, 14 Jul 1993 21:55:14 EDT Date: Wed, 14 Jul 1993 21:54:17 -0400 (EDT) From: Greg Isett Subject: Port to Windows/NT To: pine-info@cac.washington.edu Message-Id: <01H0JQHXJ870DZ6L6I@icf.hrb.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Status: O X-Status: >If you're soliciting interest, we would *definitely* like to see PC-Pine >running over PC/NFS! I'd also be interested in a port to Windows/NT (Multinet TCP/IP). ------------------------------------------------------------------------------- Greg Isett Internet: gwi@icf.hrb.com HRB Systems FAX : (814)234-7720 300 Science Park Road Voice : (814)238-4311 State College, Pa. USA 16804-0060 ------------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Jul 15 00:11:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25932; Thu, 15 Jul 93 00:11:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21188; Thu, 15 Jul 93 00:00:34 -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 AA21182; Thu, 15 Jul 93 00:00:33 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16407; Thu, 15 Jul 93 00:00:26 -0700 Date: Wed, 14 Jul 1993 23:49:44 -0700 (PDT) From: Terry Gray Subject: Re: PC-Pine with multiple users To: Ken Weaverling Cc: Pine Info Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Ken, Short term, I can only think of one feature that might help: -you can use the -p command line option to specify alternate pinerc files -you could then create BAT files to hide this, e.g. joepine.bat marypine.bat, etc. Not as elegant as you (or we) would like, but a start. Long term, we will be looking hard at the whole configuration issue. We want to be able to have personal preferences, addressbook, etc, be stored in one place and accessible by any version of pine running on any platform. One possibility is to use IMAP or its upcoming companion support protocol (IMSP, from Carnegie Mellon) to access the config data. Note that there are really two issues: 1. indicating to the system who you are (with authentication) and 2. getting the personal config info for that individual. Remote file access protocols (e.g. NFS or Netware) are sometimes used to get at the config files, but we need a light-weight solution that can be implemented easily on any machine. The authentication problem ultimately calls for Kerberos, but we haven't had time to address that yet. -teg On Wed, 14 Jul 1993, Ken Weaverling wrote: > Some thoughts on PC Pine... > > Many of our faculty work in two person offices with one PC. Others may > also share PCs, like someone jumping on the secretary's PC. I won't even > go into the horrors of thousands of students using PCs all over campus. > > With the PC port of Pine, it assumes one user to one computer. The pinerc > file has info like full name, user name, etc... > > Isn't there someway to get this information from the imap server when the > user logs in to the INBOX? Can't you take the username used and get full > name info somehow by either using the SMTP port to do EXPN commands or > using NIS somehow? > > Or, allow me as a sys admin to put a global configuration file somewhere > and let pine query it for the additional items based on the username used > to login. I can then store and maintain a copy on a PC file server somewhere. > > Another thought, forcing file\path naming (\pine for example) is a drag > in a school environment. I would rather be able to somehow specify where > the configuration files and even mail folder is via an environment variable. > > I am not sure about the feasibility of some of these suggestions. I just > thought I'd throw them up for discussion. > > From owner-pine-info@cac.washington.edu Thu Jul 15 00:23:00 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26159; Thu, 15 Jul 93 00:23:00 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21284; Thu, 15 Jul 93 00:14: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 AA21278; Thu, 15 Jul 93 00:14:55 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18054; Thu, 15 Jul 93 00:14:51 -0700 Date: Thu, 15 Jul 1993 00:03:31 -0700 (PDT) From: Terry Gray Subject: Re: more on sending authentication To: Ken Weaverling 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: On Wed, 14 Jul 1993, Ken Weaverling wrote: > P.S. On the authentication problem, I realize that it is easy to spoof > mail, but we shouldn't make it TOO easy. One should be required to login > to the imapd server to send mail and then use that login id at least to > construct the From: line. Ken, Mark has given the big-picture answer, but I wanted to add one point: Tying the "From: " line to the IMAP login has several serious problems: 1. Many people have more than one acct where they receive mail, and the acct names differ. Pine has no way of knowing which, if any, of those login names should be used for constructing the From: line. 2. Even with a single acct, it is *usual* but not *guaranteed* that your preferred outgoing username be the same as your login name. 3. Some people who act in different *roles* need to be able to change From line info depending on what type of mail they are answering. 4. The fact that you might tie the *username* to a login doesn't give as much security as you might hope, as usernames are not unique across systems. That is, you need to worry about the "right side" of the "From: " address as well as the left side. Having said that, let me reiterate Mark's point that we *are* concerned about authentication, but we need to solve the problem at the transport (MTA) level, rather than the user-agent (MUA) level. Either that or simply wait for end-to-end solutions such as PEM. -teg From owner-pine-info@cac.washington.edu Thu Jul 15 01:20:36 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27734; Thu, 15 Jul 93 01:20:36 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21644; Thu, 15 Jul 93 01:10:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21638; Thu, 15 Jul 93 01:10:23 -0700 Received: by mail.swip.net (5.65c8-/1.2) id AA03313; Thu, 15 Jul 1993 10:10:20 +0200 Received: from marilyn.abalon.se by abalon.se (4.1/SMI-4.1) id AA03783; Thu, 15 Jul 93 10:06:25 MET Date: Thu, 15 Jul 93 10:06:25 MET From: clindh@abalon.se (Christer Lindh) Message-Id: <9307150806.AA03783@abalon.se> Received: by marilyn.abalon.se (4.1/SMI-4.1) id AA19623; Thu, 15 Jul 93 10:06:16 +0200 To: pine-info@cac.washington.edu Subject: Re: ANNOUNCING general availability of PC-Pine 3.84 (Beta #3) Status: O X-Status: >>Re PC-PINE: > We believe version 3.84 is reasonably stable and free of serious > bugs, but still consider it a test version. We'll try to have any > reported bugs fixed in the upcoming source release. It worked like a charm, right out of the box with ONE, but major, exception: I can't type any 8-bit characters! And any 8-bit chars sent in a mail from UNIX-PINE (as ISO-8859-1) show up as "_", despite me having these option set: character-set=ISO-8859-1 feature-list=old-growth,show-all-characters I really hope this is supposed to work in the final release, else PC-PINE is utterly useless to us and the rest of the world that needs 8-bit charsets. The reason we have switched the UNIX users to Pine is the support for encoding and decoding 8-bit chars without the user having to bother. If it is to be implemented, will PC-PINE have map-tables to map from the PC codetable to for example ISO-8859-n and vice verse? If so, please implement that in UNIX-PINE as well. We need that to map Swedish 7-bit (ISO 646-SE) to ISO-8859-1 for the users that have 7-bit terminals (ie a '}' becomes a ISO 8859-1 "a-ring") We would also like to see support for ISO-8859 in the HEADERS. That is part of the MIME standard I believe. Also, can we hope on some rudimentary mouse-support in the future? (I bet a Windows-version is faaar away) -- :: clindh@abalon.se :: o/ :: :: :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. :: :: 59.19 N, 17.57 E :: /!> :: Love it or leave it. :: :: * All disclaimers apply * :: ! climb! :: :: From owner-pine-info@cac.washington.edu Thu Jul 15 02:22:34 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29227; Thu, 15 Jul 93 02:22:34 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21990; Thu, 15 Jul 93 02:10:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21984; Thu, 15 Jul 93 02:10:16 -0700 Received: by mail.swip.net (5.65c8-/1.2) id AA05372; Thu, 15 Jul 1993 11:10:14 +0200 Received: from marilyn.abalon.se by abalon.se (4.1/SMI-4.1) id AA03872; Thu, 15 Jul 93 10:11:54 MET Date: Thu, 15 Jul 93 10:11:54 MET From: clindh@abalon.se (Christer Lindh) Message-Id: <9307150811.AA03872@abalon.se> Received: by marilyn.abalon.se (4.1/SMI-4.1) id AA19624; Thu, 15 Jul 93 10:11:45 +0200 To: pine-info@cac.washington.edu Subject: JPEG and Pine Status: O X-Status: Is there a reason PINE doesn't recognize JPEG-files as being just JPEG when attaching them? GIF works fine. It must be possible to see that it's a JPEG by looking at the file, "xv" and other viewers can. PC-Pine doesn't support it either. The "jpeg" subtype is part of the MIME standard. From owner-pine-info@cac.washington.edu Thu Jul 15 02:22:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29233; Thu, 15 Jul 93 02:22:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21974; Thu, 15 Jul 93 02:05:41 -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 AA21968; Thu, 15 Jul 93 02:05:38 -0700 Received: from carlisle.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <02393-0@Rye.city.ac.uk>; Thu, 15 Jul 1993 09:55:39 +0100 Date: Thu, 15 Jul 1993 10:02:15 +0100 (BST) From: "D.K.Brownlee" Subject: Re: PC-Pine authentication To: 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: You do what you can - nowthing short of dropping SMTP altogether is going to stop people telnetting to ol' port 25, but if you can simply go into a pinerc & change your ID it lowers the skill needed to fake messages. I don't know too much about IMAP - does it support mail sending as well as processing mailboxes? 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. On Wed, 14 Jul 1993, David L Miller wrote: > > That just makes them get a little more creative. There are so many > loopholes in current email *transport* mechanisms that anything you do > on a user agent (like pine) is just window dressing. > > -- > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > > On Wed, 14 Jul 1993, D.K.Brownlee wrote: > > > > > Wouldn't it be possible to make PC-Pine ensure it had connected to the > > IMAP server & validated the user account & password that way before > > sending any mail - ie 1st time in a session the user goes to send > > a mail message, if they have not previously in that session read > > their inbox pcpine does some form of test-connect to the IMAP server > > to ensure their account details are valid? > > > > 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. > > > > > > On Wed, 14 Jul 1993, David L Miller wrote: > > > > > > > > Unfortunately, from a PC there is no way to enforce things like user-id, > > > etc. No matter what we do (short of PEM or other secure mail system) we > > > will always have authentication problems with PC-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 15tn Ave NE, Seattle WA 98105, USA > > > > > > > > > On Wed, 14 Jul 1993, Barry Cornelius wrote: > > > > > > > I tried PC-Pine Release 3.84 yesterday. I used it as follows: > > > > > > > > (a) with LANWorkPlace for Dos (on a standalone PC rather than > > > > a Novell-networked PC), > > > > > > > > (b) with the existing IMAP daemon running on a Sun (i.e., the one > > > > that comes with Pine 3.07 rather than the new version of IMAP). > > > > > > > > This experiment was successful: after asking for my username and password, > > > > I was able to read my inbox from the Unix machine containing mailboxes. It > > > > was reasonably fast. > > > > > > > > When PC-Pine started up the first time, it asked me for values for the > > > > user-id, personal-name and user-domain variables. I supplied appropriate > > > > values and these were stored in the \PINE\PINERC file. These values are > > > > used to generate the From line of a message. > > > > > > > > Later, I changed the settings of these variables in the PINERC file. I was then > > > > able to send messages masquerading as someone else. This is not desirable! > > > > Have I got something wrong? Is there anyway in which this can be avoided? > > > > > > > > -- > > > > Barry Cornelius Electronic mail: Barry.Cornelius@durham.ac.uk > > > > Post: Computing Service, University of Durham, Durham, DH1 3LE, England > > > > Phone: Durham (091 or +44 91) 374 4717, Secretary:374 2892, Fax:374 3741 > > > > > > > > > > > > > > > > > > > > > > > > From owner-pine-info@cac.washington.edu Thu Jul 15 02:30:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29376; Thu, 15 Jul 93 02:30:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22026; Thu, 15 Jul 93 02:13:37 -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 AA22020; Thu, 15 Jul 93 02:13:34 -0700 Received: from carlisle.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <02628-0@Rye.city.ac.uk>; Thu, 15 Jul 1993 10:03:26 +0100 Date: Thu, 15 Jul 1993 10:10:38 +0100 (BST) From: "D.K.Brownlee" Subject: .signature options (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: A simple local/remote signature file option would be quite useful. Also a file containing a list of 'nosig' addresses could help with the 1st problem - maybe a boolean flag in the address book? David |\/| D.K.Brownlee@city.ac.uk. Network Analyst. Postmaster. Hostmaster. | | Telephone: (+44) 71 477 8000 Ext:3757. Snailmail: E308, City University, Northampton Sq, Islington, London ECIV 0HB. ---------- Forwarded message ---------- Date: Wed, 14 Jul 1993 16:24:27 -0500 (CDT) From: "Robert A. Hayden" To: Pine Info Subject: .signature options This is something that I'd like to see in pine (among many other thing). If, when adding an address, you could also toggle a Y/N .signature flag. The reason is that when doing administrative work on several of my mailing lists, it becomes old to have to edit out my .sig every time (because the server gets mad if you have error producing lines). -- Building on that, a field in the address file allowing you to designate one of several signatures would also be interesting. (say one field you edit with a number 0-9 or an N, default being 0. You then have a seperate file or as part of the .pinerc where you can designate each # as a different file.) Could be nice for companies where anything going outside local needs to have a large disclaimer, while in house then need little or nothing on the end. {[> Robert A. Hayden ____ hayden@krypton.mankato.msus.edu <]} {[> \ /__ hayden@att2.cs.mankato.msus.edu <]} {[> \/ / aq650@slc4.INS.CWRU.Edu <]} {[> #include \/ <]} -=-=- (GEEK CODE 0.3): GSS d- p--/-p+ c++ l++ m+/* s-/++ g+ w++ t++ r++ x+ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Random Thought: Beauty is only skin deep, but Ugly goes straight to the bone. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From owner-pine-info@cac.washington.edu Thu Jul 15 02:37:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29524; Thu, 15 Jul 93 02:37:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22061; Thu, 15 Jul 93 02:23:55 -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 AA22055; Thu, 15 Jul 93 02:23:53 -0700 Received: by flipper.pvv.unit.no id AA10903 (5.65c8/IDA-1.4.4 for pine-info@cac.washington.edu); Thu, 15 Jul 1993 11:24:07 +0200 From: Arnt Gulbrandsen Message-Id: <199307150924.AA10903@flipper.pvv.unit.no> Subject: Re: PC-Pine To: pine-info@cac.washington.edu Date: Thu, 15 Jul 1993 11:24:06 +0200 (EET) In-Reply-To: from "Barry Cornelius" at Jul 14, 93 01:22:11 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: 769 X-Charset: ASCII X-Char-Esc: 29 Status: O X-Status: > When PC-Pine started up the first time, it asked me for values for the > user-id, personal-name and user-domain variables. I supplied appropriate > values and these were stored in the \PINE\PINERC file. These values are > used to generate the From line of a message. I noticed this, too. In a lab environment where a thousand students use the PCs this is not viable. It would be much better for PC-Pine to ask the server about this info. The server should know, and it seems a natural extension to IMAP that the client can ask the server what the headers should contain. (Another possible extension is "what other accounts should I check?" to cater for postmaster, support, personal vs. business accounts and so on.) -- Arnt Gulbrandsen agulbra@pvv.unit.no From owner-pine-info@cac.washington.edu Thu Jul 15 02:50:08 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29714; Thu, 15 Jul 93 02:50:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22120; Thu, 15 Jul 93 02:36:09 -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 AA22114; Thu, 15 Jul 93 02:36:07 -0700 Received: from carlisle.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <03136-0@Rye.city.ac.uk>; Thu, 15 Jul 1993 10:25:54 +0100 Date: Thu, 15 Jul 1993 10:31:06 +0100 (BST) From: "D.K.Brownlee" Subject: Re: more on sending authentication To: 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: 1 & 3 could be taken care of by permitting the user to specify a 'from' account they wish to use, and this is checked as an IMAP login. If they change this during a session, an new validation is performed. (If needed). So they can be whoever they want - as long as they are validated. Specifying a 'Reply-To:' line would probably get past problem 2 (At least if the remote end mailer is not *too* dumb :) Again -all your aiming for is to make it harder to fake mail using pine than to go direct to the telnet port... (Untill we get real security at the mda end) 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. On Thu, 15 Jul 1993, Terry Gray wrote: > > On Wed, 14 Jul 1993, Ken Weaverling wrote: > > > P.S. On the authentication problem, I realize that it is easy to spoof > > mail, but we shouldn't make it TOO easy. One should be required to login > > to the imapd server to send mail and then use that login id at least to > > construct the From: line. > > Ken, > Mark has given the big-picture answer, but I wanted to add one point: > Tying the "From: " line to the IMAP login has several serious problems: > > 1. Many people have more than one acct where they receive mail, and > the acct names differ. Pine has no way of knowing which, if any, > of those login names should be used for constructing the From: line. > > 2. Even with a single acct, it is *usual* but not *guaranteed* that > your preferred outgoing username be the same as your login name. > > 3. Some people who act in different *roles* need to be able to change > From line info depending on what type of mail they are answering. > > 4. The fact that you might tie the *username* to a login doesn't give > as much security as you might hope, as usernames are not unique > across systems. That is, you need to worry about the "right side" > of the "From: " address as well as the left side. > > Having said that, let me reiterate Mark's point that we *are* concerned > about authentication, but we need to solve the problem at the transport > (MTA) level, rather than the user-agent (MUA) level. Either that or > simply wait for end-to-end solutions such as PEM. > > -teg > From owner-pine-info@cac.washington.edu Thu Jul 15 03:28:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00646; Thu, 15 Jul 93 03:28:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16465; Thu, 15 Jul 93 03:19:53 -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 AA16459; Thu, 15 Jul 93 03:19:51 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05156; Thu, 15 Jul 93 03:19:44 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03180; Thu, 15 Jul 93 03:19:35 -0700 Date: Thu, 15 Jul 1993 03:12:35 -0700 (PDT) From: Mark Crispin Subject: Re: PC-Pine authentication To: "D.K.Brownlee" 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: On Thu, 15 Jul 1993 10:02:15 +0100 (BST), D.K.Brownlee wrote: > You do what you can - nowthing short of dropping SMTP altogether > is going to stop people telnetting to ol' port 25, but if you can > simply go into a pinerc & change your ID it lowers the skill needed > to fake messages. It may be possible to ameliorate this somewhat, while keeping essential functionality. We'll discuss it within the Pine team a bit first. > I don't know too much about IMAP - does it support mail sending as > well > as processing mailboxes? No, and it won't. There are excellent reasons why message posting should not be in IMAP, which I will not go into here (being that this is the Pine-info list, not the IMAP list). The IMAP list archive on ftp.cac.washington.edu in the file mail/imap_archive has some messages on this subject. From owner-pine-info@cac.washington.edu Thu Jul 15 04:04:12 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01272; Thu, 15 Jul 93 04:04:12 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22504; Thu, 15 Jul 93 03:50: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 AA22498; Thu, 15 Jul 93 03:50:45 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19342; Thu, 15 Jul 93 03:50:36 -0700 Date: Thu, 15 Jul 1993 03:30:12 -0700 (PDT) From: Terry Gray Reply-To: Terry Gray Subject: Re: PC-Pine To: Arnt Gulbrandsen Cc: pine-info@cac.washington.edu In-Reply-To: <199307150924.AA10903@flipper.pvv.unit.no> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Status: O X-Status: Arnt, The reasons why it is not feasible or desirable to tie the config info (especially the username used to create From: lines) to the IMAP server providing the *inbox* have been mentioned in a previous message. However, we completely agree that personal configuration info should be obtained (or at least obtainable) from *some* server. We just haven't gotten to that yet, as our initial target for PC-Pine was the single-user PC case. Also, telling the MUA how to build outgoing messages is definitely outside the intended scope of IMAP, but definitely within the intended scope of IMSP... There are several issues that must be kept distinct: 1. Making PC-Pine "multi-user"... that is making it aware of user identity at start up so it can go find the appropriate personal configuration info. (Right now you must do this manually via the -p flag, although a frontend menu or script could hide that). 2. Location of personal config files. Clearly there needs to be a way for any Pine on any platform to get at a single instance of a user's config data. (Right now you must rely on file access protocols, e.g NFS for this.) 3. Authentication of sent mail. This is an MTA issue, but we will definitely be exploring ways to reduce the risks of abuse. (Some simple things might be helpful, but it is hard to justify anything elaborate with the "telnet xxx 25" option available.) Regarding the "what other accounts should I check?" question: That is exactly what the new "incoming-folders" variable in the PINERC is for, although it is general enough to use for multiple incoming folders on either a single host or multiple hosts. -teg On Thu, 15 Jul 1993, Arnt Gulbrandsen wrote: > > When PC-Pine started up the first time, it asked me for values for the > > user-id, personal-name and user-domain variables. I supplied appropriate > > values and these were stored in the \PINE\PINERC file. These values are > > used to generate the From line of a message. > > I noticed this, too. In a lab environment where a thousand students > use the PCs this is not viable. It would be much better for PC-Pine > to ask the server about this info. The server should know, and it > seems a natural extension to IMAP that the client can ask the server > what the headers should contain. (Another possible extension is "what > other accounts should I check?" to cater for postmaster, support, > personal vs. business accounts and so on.) > > -- > Arnt Gulbrandsen > agulbra@pvv.unit.no > From owner-pine-info@cac.washington.edu Thu Jul 15 08:40:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06521; Thu, 15 Jul 93 08:40:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24739; Thu, 15 Jul 93 08:25:46 -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 AA24731; Thu, 15 Jul 93 08:25:44 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28240; Thu, 15 Jul 93 08:25:39 -0700 Date: Thu, 15 Jul 1993 08:23:10 -0700 (PDT) From: David L Miller Subject: Re: JPEG and Pine To: Christer Lindh Cc: pine-info@cac.washington.edu In-Reply-To: <9307150811.AA03872@abalon.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Our MIME support still has a long way to go to be complete. We will work on adding the rest of the MIME subtypes as fast as time and resources permit. When we do add new subtypes, they will be supported across all platforms. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 15 Jul 1993, Christer Lindh wrote: > Is there a reason PINE doesn't recognize JPEG-files as being just JPEG > when attaching them? GIF works fine. It must be possible to see > that it's a JPEG by looking at the file, "xv" and other viewers can. > > PC-Pine doesn't support it either. > > The "jpeg" subtype is part of the MIME standard. > From owner-pine-info@cac.washington.edu Thu Jul 15 08:41:41 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06584; Thu, 15 Jul 93 08:41:41 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17730; Thu, 15 Jul 93 08:32:04 -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 AA17724; Thu, 15 Jul 93 08:31:53 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA28621; Thu, 15 Jul 93 11:31:43 -0400 Received: from merint.UUCP by spool.uu.net with UUCP/RMAIL (queueing-rmail) id 112811.4222; Thu, 15 Jul 1993 11:28:11 EDT Received: by merint (AIX 3.2/UCB 5.64/4.03) id AA24381; Thu, 15 Jul 1993 08:42:05 -0600 From: merint!alexc@uunet.UU.NET (Alex M. Chan) Message-Id: <9307151442.AA24381@merint> To: uunet!pine-info%cac.washington.edu@uunet.UU.NET Cc: alexc%merint@uunet.UU.NET Subject: Re: security issues of sending mail ... Date: Thu, 15 Jul 93 08:42:05 -0700 Status: O X-Status: May I suggest this .. 1. there will be a uniq config file for each use on the PC. 2. the information in the config file will be encoded with a user's access password to send mail from the PC. 3. if the use wanted to send mail from the PC, pine will ask the user for the password before and decode the config details for that user and then send the message out to the mail server. This way more then one person can share a PC. But each user will have their own ID code. Just like login to any unix system (almost). ### On a separate issue, we are running pine on an RS6000 with AIX 3.2.3 and am wondering if it is possible to get Smail2.5 to run on it with pine ? We have only a connection to the net via uunet using the UUCP program. The *)(&(* sendmail.cf on this machine is a mess and I am no expert in sendmail.cf ... so to get it to rewrite the internet style of address to let it send over UUCP ... someone have suggested to try Smail2.5, I have managed to get hold of the source code, but I come to a point to figure out how AIX handle mail. AIX have this in the /bin directory -r-sr-sr-x 1 root mail 28708 Nov 28 1992 /bin/bellmail -r-xr-xr-x 3 bin mail 131699 Nov 28 1992 /bin/mail -r-xr-xr-x 3 bin mail 131699 Nov 28 1992 /bin/mailx -r-xr-xr-x 1 bin mail 15096 Dec 18 1991 /bin/mhmail -r-xr-sr-x 1 bin mail 4402 Nov 28 1992 /bin/rmail wondering if anyone out there know how to configure Smail2.5 on AIX with sendmail ? (In my personal view, AIX should NOT be allowed to exist in the first place, but there is another story ... :(( ) -- Alex Chan, Technical Support Manager. ( alexc%merint.uucp@uunet.uu.net ) Meridian International, Inc. POB 10010, Ogden, Utah 84409 (801)394-9446 Quote of the Day : "We are Microsoft. UNIX is irrelevant. OS/2 is irrelevant. Openness is futile. Prepare to be assimilated." - Gates From owner-pine-info@cac.washington.edu Thu Jul 15 10:17:14 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10013; Thu, 15 Jul 93 10:17:14 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18289; Thu, 15 Jul 93 10:04:48 -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 AA18283; Thu, 15 Jul 93 10:04:46 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA15230; Thu, 15 Jul 93 10:02:37 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA06526; Thu, 15 Jul 93 10:07:15 -0700 Date: Thu, 15 Jul 1993 10:06:25 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: JPEG and Pine To: Christer Lindh Cc: pine-info@cac.washington.edu In-Reply-To: <9307150811.AA03872@abalon.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Thu, 15 Jul 1993, Christer Lindh wrote: > Is there a reason PINE doesn't recognize JPEG-files as being just JPEG > when attaching them? GIF works fine. It must be possible to see > that it's a JPEG by looking at the file, "xv" and other viewers can. > > PC-Pine doesn't support it either. > > The "jpeg" subtype is part of the MIME standard. This is also something that we would like to see...JPEG is the preferred method of storing images here because they are sooo much smaller than GIFs. 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 Jul 15 15:48:11 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21261; Thu, 15 Jul 93 15:48:11 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20005; Thu, 15 Jul 93 15:36: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 AA19999; Thu, 15 Jul 93 15:36:16 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05560; Thu, 15 Jul 93 15:36:10 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA05380; Thu, 15 Jul 93 15:36:04 -0700 Date: Thu, 15 Jul 1993 15:19:13 -0700 (PDT) From: Mark Crispin Subject: re: [PARSE] Junk at end of address To: Ken Weaverling 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: Ken - The address string mail11.;@cop.dec.com (@kw) is not in compliance with RFC-822 (or to my knowledge any other e-mail standards). The problem is the semicolon; this is explicitly defined as a ``special'' in RFC-822. Consequently, it has to be quoted. Ref: RFC-822, pp 44-47, definitions of ``local-part'', ``atom'', ``specials''. The string: "mail11.;"@cop.dec.com (@kw) would have parsed successfully. In order to deal with the buggy mail programs that still fail to write the host field in the mailbox (e.g. ``To: Joe, Fred, Sally''), Pine will try to parse an address with a missing host field. Thus, it reads ``mail11.'', sees a special other than an @, and assumes this is a missing host address and substitutes the local host name. Having now finished the address parse, it goes further, encounters the semicolon when it was not expecting one (it is only permitted as a group list terminator), and reports an error. To be truly pedantic, Pine should have choked at the period. Technically, period is also a special, but can be used to attach multiple words (e.g. foo.bar.zap). However, words cannot be null, so ``mail11.'' isn't valid since there is nothing after the period. I have no trouble believing that mailx, elm, and mush ignore this syntax error instead of reporting it to the user as Pine does. That doesn't mean that these programs do the ``right thing'', because there is no right thing in parsing this address. I do not believe that any useful information exists with this address. It's totally garbaged. I suggest that you report it as a bug in your site's mailer, and be thankful that Pine took the trouble to alert you to the problem instead of ignoring it. From owner-pine-info@cac.washington.edu Thu Jul 15 20:57:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27553; Thu, 15 Jul 93 20:57:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05254; Thu, 15 Jul 93 20:37:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from csc-srv.wam.umd.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA05248; Thu, 15 Jul 93 20:37:06 -0700 Received: from rac2.wam.umd.edu by csc-srv.wam.umd.edu with SMTP id AA27477 (5.65c/IDA-1.4.4 for ); Thu, 15 Jul 1993 23:35:28 -0400 Received: by rac2.wam.umd.edu id AA12629 (5.65c/IDA-1.4.4); Thu, 15 Jul 1993 23:36:46 -0400 Date: Thu, 15 Jul 1993 23:32:30 -0400 (EDT) From: Mike Grupenhoff Subject: Re: Port to Windows/NT To: Greg Isett Cc: pine-info@cac.washington.edu In-Reply-To: <01H0JQHXJ870DZ6L6I@icf.hrb.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Wed, 14 Jul 1993, Greg Isett wrote: > > >If you're soliciting interest, we would *definitely* like to see PC-Pine > >running over PC/NFS! > > I'd also be interested in a port to Windows/NT (Multinet TCP/IP). > Don't forget OS/2, with IBM's TCP/IP package. It may not be that difficult either, since gcc has already been ported to OS/2. Other large UNIX programs, like elm, have been ported sucessfully. -- Mike Grupenhoff kashmir@wam.umd.edu MIME mail accepted From owner-pine-info@cac.washington.edu Fri Jul 16 00:25:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00128; Fri, 16 Jul 93 00:25:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06249; Fri, 16 Jul 93 00:11:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cheviot.ncl.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06243; Fri, 16 Jul 93 00:11:53 -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; Fri, 16 Jul 1993 08:11:50 +0100 Date: Fri, 16 Jul 1993 08:09:48 +0100 (BST) From: Alan Ward Subject: Re: Port to Windows/NT To: 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: I second that request for OS/2 Thanks Alan Ward Alan.Ward@newcastle.ac.uk Department of Microbiology Medical School University of Newcastle upon Tyne NE2 4HH On Thu, 15 Jul 1993, Mike Grupenhoff wrote: > On Wed, 14 Jul 1993, Greg Isett wrote: > > > >If you're soliciting interest, we would *definitely* like to see PC-Pine > > >running over PC/NFS! > > I'd also be interested in a port to Windows/NT (Multinet TCP/IP). > > Don't forget OS/2, with IBM's TCP/IP package. It may not be that > difficult either, since gcc has already been ported to OS/2. Other large > UNIX programs, like elm, have been ported sucessfully. > > -- > Mike Grupenhoff > kashmir@wam.umd.edu > MIME mail accepted > From owner-pine-info@cac.washington.edu Fri Jul 16 03:18:23 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03777; Fri, 16 Jul 93 03:18:23 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22576; Fri, 16 Jul 93 03:07:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22570; Fri, 16 Jul 93 03:07:23 -0700 Received: by mail.swip.net (5.65c8-/1.2) id AA17373; Fri, 16 Jul 1993 12:07:21 +0200 Received: from marilyn.abalon.se by abalon.se (4.1/SMI-4.1) id AA25922; Fri, 16 Jul 93 09:19:58 MET Date: Fri, 16 Jul 93 09:19:58 MET From: clindh@abalon.se (Christer Lindh) Message-Id: <9307160719.AA25922@abalon.se> Received: by marilyn.abalon.se (4.1/SMI-4.1) id AA20259; Fri, 16 Jul 93 09:19:49 +0200 To: pine-info@cac.washington.edu Subject: Offline reading and answering? X-Zippy: Am I accompanied by a PARENT or GUARDIAN? Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Status: O X-Status: As PC-PINE stands today, it depends on being connected to a network, (and it works great that way). When I go on business trips or on vacation, I usually download a bunch of the most overflowing inboxes and read it and answer them on my laptop. I've done this in a very brute way, with emacs and a (UNIX) script that'll mail out the answer when I get back. Pine could fit in here, using a version without any Imapd, SMTP or network dependicies. Turning off the ability to read remote boxes if it is compiled without net can't be hard. The thing(?) that would require some work would be queuing outgoing mail in a folder ("outgoing") instead of using SMTP to send it directly. That could be handed over to something that sent it using SMTP later on. Any thoughts on this? Does anyone know of other solutions to it? -- :: clindh@abalon.se :: o/ :: :: :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. :: :: 59.19 N, 17.57 E :: /!> :: Love it or leave it. :: :: * All disclaimers apply * :: ! climb! :: :: From owner-pine-info@cac.washington.edu Fri Jul 16 08:21:21 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08788; Fri, 16 Jul 93 08:21:21 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09190; Fri, 16 Jul 93 08:08: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 AA09184; Fri, 16 Jul 93 08:08:13 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03810; Fri, 16 Jul 93 08:08:09 -0700 Date: Fri, 16 Jul 1993 08:06:17 -0700 (PDT) From: David L Miller Subject: Re: Offline reading and answering? To: Christer Lindh Cc: pine-info@cac.washington.edu In-Reply-To: <9307160719.AA25922@abalon.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Dial-up and disconnected operation are on the agenda for future releases. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Fri, 16 Jul 1993, Christer Lindh wrote: > As PC-PINE stands today, it depends on being connected to a network, > (and it works great that way). > > When I go on business trips or on vacation, I usually download a bunch > of the most overflowing inboxes and read it and answer them on my > laptop. I've done this in a very brute way, with emacs and a (UNIX) > script that'll mail out the answer when I get back. > > Pine could fit in here, using a version without any Imapd, SMTP or > network dependicies. Turning off the ability to read remote boxes if > it is compiled without net can't be hard. > > The thing(?) that would require some work would be queuing outgoing > mail in a folder ("outgoing") instead of using SMTP to send it directly. > > That could be handed over to something that sent it using SMTP later > on. > > Any thoughts on this? Does anyone know of other solutions to it? > > -- > :: clindh@abalon.se :: o/ :: :: > :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. :: > :: 59.19 N, 17.57 E :: /!> :: Love it or leave it. :: > :: * All disclaimers apply * :: ! climb! :: :: > From owner-pine-info@cac.washington.edu Fri Jul 16 08:23:52 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08859; Fri, 16 Jul 93 08:23:52 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23824; Fri, 16 Jul 93 08:14:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from INDIV-GW.CENT.NET by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23818; Fri, 16 Jul 93 08:14:00 -0700 Received: by individual.com (5.65c/Spike-2.1) id AA18425; Fri, 16 Jul 1993 11:11:25 -0400 Date: Fri, 16 Jul 1993 11:08:32 -0400 (EDT) From: Adam J Weitzman Subject: What about a Reply-To: line in rich headers? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Our site has been using Pine on a Sun SPARCstation 2 running SunOS 4.1.2 for about two months now and we love it. I have a question regarding adding header lines that don't already exist. I would like to be able to add arbitrary header lines to a message (which are allowed under RFC-822), but *especially* I want to be able to add a Reply-To: line. Is there any way to do this already that I'm just ignorant of? - Adam J Weitzman INDIVIDUAL, Inc. weitzman@individual.com From owner-pine-info@cac.washington.edu Fri Jul 16 08:48:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09725; Fri, 16 Jul 93 08:48:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09611; Fri, 16 Jul 93 08:33: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 AA09605; Fri, 16 Jul 93 08:33:13 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04462; Fri, 16 Jul 93 08:33:08 -0700 Date: Fri, 16 Jul 1993 08:32:21 -0700 (PDT) From: David L Miller Subject: Re: What about a Reply-To: line in rich headers? To: Adam J Weitzman 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: Arbitrary header lines are planned for future versions of 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 15tn Ave NE, Seattle WA 98105, USA On Fri, 16 Jul 1993, Adam J Weitzman wrote: > Our site has been using Pine on a Sun SPARCstation 2 running SunOS 4.1.2 > for about two months now and we love it. I have a question regarding > adding header lines that don't already exist. I would like to be able to > add arbitrary header lines to a message (which are allowed under RFC-822), > but *especially* I want to be able to add a Reply-To: line. Is there any > way to do this already that I'm just ignorant of? > > - Adam J Weitzman > INDIVIDUAL, Inc. > weitzman@individual.com > > > From owner-pine-info@cac.washington.edu Fri Jul 16 12:21:26 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17448; Fri, 16 Jul 93 12:21:26 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13085; Fri, 16 Jul 93 12:00:56 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from kate.ibmpcug.co.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13077; Fri, 16 Jul 93 12:00:52 -0700 Subject: SCO Pine?? To: pine-info@cac.washington.edu Date: Fri, 16 Jul 1993 20:00:34 +0100 (BST) X-Mailer: ELM [version 2.4 PL2] Content-Type: text Content-Length: 421 From: jake@ibmpcug.co.uk Message-Id: <9307162000.aa07061@kate.ibmpcug.co.uk> Status: O X-Status: Hello, I am sure people have asked this before, but I am still waiting for a SCO port of pine. Is anyone working on it? >From the pine-ports doc sco --- Santa Cruz Operation UNIX Some work has been done on this, in particular a version of the c-client has been ported, though it is not included here yet. This will probably be in the next major release. Where is this part-port available from? Thanks, Jake From owner-pine-info@cac.washington.edu Fri Jul 16 14:18:08 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21699; Fri, 16 Jul 93 14:18:08 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25985; Fri, 16 Jul 93 14:10:13 -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 AA25979; Fri, 16 Jul 93 14:10:11 -0700 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AB28281; Fri, 16 Jul 93 17:10:15 -0400 Received: from verifone.UUCP by spool.uu.net with UUCP/RMAIL (queueing-rmail) id 170721.17195; Fri, 16 Jul 1993 17:07:21 EDT Received: by verifone.com with UUCP/PMDF (DECUS UUCP); Fri, 16 Jul 1993 10:57:07 -1000 Received: from verifone.com by verifone.com (PMDF V4.2-11 #2386) id <01H0LW2T9AV491YRL4@verifone.com>; Fri, 16 Jul 1993 10:57:03 -1000 Date: Fri, 16 Jul 1993 10:57:03 -1000 From: "James H. Thompson - HNL" Subject: PICO for MS-DOS? To: pine-info@cac.washington.edu Message-Id: <01H0LW2TA3SY91YRL4@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 Status: O X-Status: Any plans to release a standalone version of PICO for MS-DOS? 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 Jul 16 15:03:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23208; Fri, 16 Jul 93 15:03:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15713; Fri, 16 Jul 93 14:55:42 -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 AA15707; Fri, 16 Jul 93 14:55:41 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16974; Fri, 16 Jul 93 14:55:36 -0700 Date: Fri, 16 Jul 1993 14:54:57 -0700 (PDT) From: David L Miller Subject: Re: PICO for MS-DOS? To: "James H. Thompson - HNL" Cc: pine-info@cac.washington.edu In-Reply-To: <01H0LW2TA3SY91YRL4@verifone.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I expect that to happen with the source release (August) if not sooner. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Fri, 16 Jul 1993, James H. Thompson - HNL wrote: > Any plans to release a standalone version of PICO for MS-DOS? > > 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 Sat Jul 17 01:46:31 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02928; Sat, 17 Jul 93 01:46:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02922; Sat, 17 Jul 93 01:46:26 -0700 Received: by digi.syd.deg.csiro.au id AA01497 (5.65c/IDA-1.4.4 for pine mailing list ); Sat, 17 Jul 1993 18:46:07 +1000 Date: Sat, 17 Jul 1993 18:40:51 +1000 (EST) From: Jack Churchill Subject: pico "problem" To: pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I'm not sure if it's a design feature, a bug or my problem. When I type in a line of text above an existing line and the line I typed in wraps to a new line, the existing line is included in the new wrapped line. Sometimes this is annoying, other times useful but I'm wondering if it's only happening to me. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Sat Jul 17 09:26:04 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07428; Sat, 17 Jul 93 09:26:04 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22504; Sat, 17 Jul 93 09:15:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from louie.udel.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22498; Sat, 17 Jul 93 09:15:09 -0700 Received: from pima.dtcc.edu by louie.udel.edu id aa21014; 17 Jul 93 12:11 EDT Received: by pima.dtcc.edu (5.4.2/5.40/1.0) id AA00978; Sat, 17 Jul 1993 12:11:11 -0400 Date: Sat, 17 Jul 1993 12:11:11 -0400 From: Ken Weaverling Message-Id: <9307171611.AA00978@pima.dtcc.edu> In-Reply-To: Jack Churchill "pico "problem"" (Jul 17, 18:40) X-Mailer: Mail User's Shell (7.2.4 2/2/92) To: Jack Churchill , pine mailing list Subject: Re: pico "problem" Status: O X-Status: >>>---> On Jul 17, 18:40, Jack Churchill wrote: > I'm not sure if it's a design feature, a bug or my problem. When I type > in a line of text above an existing line and the line I typed in wraps to > a new line, the existing line is included in the new wrapped line. I have also seen that problem. It catches newbies off-guard. It doesn't happen if there is a blank line below the one you are typing on. I had been meaning to say something on the list about it, but hadn't before now. -- Ken Weaverling, Sys Admin/Faith Healer, Delaware Tech College weave@dtcc.edu "The teaching of COBOL should be made a criminal offense." -- Edsger Dijkstra From owner-pine-info@cac.washington.edu Sat Jul 17 10:12:59 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07791; Sat, 17 Jul 93 10:12:59 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00316; Sat, 17 Jul 93 10:04:48 -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 AA00310; Sat, 17 Jul 93 10:04:46 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07170; Sat, 17 Jul 93 10:04:40 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03526; Sat, 17 Jul 93 10:04:33 -0700 Date: Sat, 17 Jul 1993 09:55:15 -0700 (PDT) From: Mark Crispin Subject: re: Offline reading and answering? To: Christer Lindh Cc: pine-info@cac.washington.edu In-Reply-To: <9307160719.AA25922@abalon.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Christer - Offline reading and answering is a very important issue for us (we call it ``disconnected operation''). There is still a minor change needed to the IMAP protocol to enable it -- a unique ID mechanism -- plus a fair amount of programming... However, I can guarantee that it will happen. It has been identified as a MUST DO project some time ago. It was not a target of this release (after all, we've slipped about a year on it already and the UNIX version is still a week or so away), but I hope that it'll be in the next release. Also, most of the members of the Pine team are laptop users and are thus personally sensitized to the need. A SLIP link can be nice, but that still doesn't work well from airplanes!! :-) Regards, -- Mark -- From owner-pine-info@cac.washington.edu Sat Jul 17 11:43:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08757; Sat, 17 Jul 93 11:43:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23072; Sat, 17 Jul 93 11:35:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from port10.columbus.pub-ip.psi.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23064; Sat, 17 Jul 93 11:35:34 -0700 Subject: SCO Port - What's going on with it? To: pine-info@cac.washington.edu Date: Sat, 17 Jul 1993 14:35:20 -0400 (EDT) From: Steven E Frazier Reply-To: Steven E Frazier X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 130 Message-Id: <9307171435.aa18362@eng.futurenet.com> Status: O X-Status: What is going on with the Pine port to SCO, anything? The docs say that it has been started and should be available soon, when? From owner-pine-info@cac.washington.edu Sat Jul 17 12:12:36 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09163; Sat, 17 Jul 93 12:12:36 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00737; Sat, 17 Jul 93 12:05: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 AA00731; Sat, 17 Jul 93 12:05:38 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA07234; Sat, 17 Jul 93 12:05:32 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA03824; Sat, 17 Jul 93 12:05:27 -0700 Date: Sat, 17 Jul 1993 10:04:41 -0700 (PDT) From: Mark Crispin Subject: Pine on Macs To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: I don't think this has been mentioned yet, but PC Pine *does* work on a Mac under SoftPC. I installed the packet driver version PC Pine on SoftPC's simulated hard disk along with the appropriate configuration files. Then, having attached the Mac's modem to SoftPC's COM1, I dialed out using PC Kermit and logged into a SLIP server. I then exited Kermit, and started the freeware EtherSLIP packet driver in its place. Finally, I ran PC Pine, and lo and behold, it works! I wish I could find a packet driver that knows how to talk to the Mac's Ethernet driver. That might require nagging the vendors of SoftPC. For best performance, it should be run on a 68030 based Mac or better. My experience on a 33MHz 68030 Mac is that it runs acceptably, although Pico is a little bit slower than comfortable. I would not recommend using it on a 68000 based Mac such as a PowerBook- 100 or a Mac Plus. Nor would I recommend PC Pine on an XT class PC. However, I've run Pine on both and it works like a champ, albeit slowly. It's good for impressing people as to just how crazy you really are... :-) I don't think Pine will take the Mac world by storm. Hopefully a ready- for-prime-time version of Mailstrom will. We've thought on and off about a specific Mac port of Pine. The good news is that THINK C makes large parts of the porting trivial. The bad news is that THINK C's console package isn't powerful enough to run Pine; it simulates a ``glass TTY'' (e.g. an ADM-3) with no cursor addressing. So work would have to be done to build a terminal emulator. It isn't clear that it's a productive use of time to port a character based application to the Mac. But, if you have SoftPC you can play around with the concept. The main difference is that a native Mac port -- if one is ever done -- would be a lot faster. -- Mark -- From owner-pine-info@cac.washington.edu Sat Jul 17 23:16:05 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15212; Sat, 17 Jul 93 23:16:05 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26021; Sat, 17 Jul 93 23:08:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26014; Sat, 17 Jul 93 23:08:01 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06631; Sat, 17 Jul 93 23:08:00 -0700 Date: Sat, 17 Jul 1993 23:07:49 -0700 (PDT) From: Steve Hubert Reply-To: Steve Hubert Subject: re: Offline reading and answering? To: 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 Sat, 17 Jul 1993, Mark Crispin wrote: > (after > all, we've slipped about a year on it already and the UNIX version is still a > week or so away) A more realistic estimate for the Unix version is sometime in August. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle From owner-pine-info@cac.washington.edu Sun Jul 18 22:39:18 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28812; Sun, 18 Jul 93 22:39:18 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06883; Sun, 18 Jul 93 22:28:17 -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 AA06877; Sun, 18 Jul 93 22:28:15 -0700 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09689; Mon, 19 Jul 93 01:28:11 -0400 Received: from merint.UUCP by spool.uu.net with UUCP/RMAIL (queueing-rmail) id 012624.16793; Mon, 19 Jul 1993 01:26:24 EDT Received: by merint (AIX 3.2/UCB 5.64/4.03) id AA09621; Sun, 18 Jul 1993 22:07:48 -0600 From: merint!alexc@uunet.UU.NET (Alex M. Chan) Message-Id: <9307190407.AA09621@merint> To: uunet!pine-info%cac.washington.edu@uunet.UU.NET Cc: alexc%merint@uunet.UU.NET Subject: Re: more on PC-PINE ... Date: Sun, 18 Jul 93 22:07:48 -0700 Status: O X-Status: We are also looking for a version of pine that would allow people to compose and read message off-line and use the "uucp" program to have the mail transfered to other hosts. Of course using SLIP PPP or other method is nice, but it is not necesssary. I am wondering if there would be a version of PC PINE in the future that would support this in the future. (A version for the MAC would be nice too.) From owner-pine-info@cac.washington.edu Mon Jul 19 08:55:51 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09613; Mon, 19 Jul 93 08:55:51 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09117; Mon, 19 Jul 93 08:46:05 -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 AA09111; Mon, 19 Jul 93 08:46:02 -0700 Received: from shiva1.cac.washington.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA16974; Mon, 19 Jul 93 11:45:40 -0400 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25663; Mon, 19 Jul 93 08:45:29 -0700 Date: Mon, 19 Jul 1993 08:40:05 -0700 (PDT) From: David L Miller Subject: Re: more on PC-PINE ... To: "Alex M. Chan" Cc: pine-info%cac.washington.edu@uunet.uu.net, alexc%merint@uunet.uu.net In-Reply-To: <9307190407.AA09621@merint> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Sun, 18 Jul 1993, Alex M. Chan wrote: > > > We are also looking for a version of pine that would allow people > to compose and read message off-line and use the "uucp" program > to have the mail transfered to other hosts. Of course using SLIP > PPP or other method is nice, but it is not necesssary. > We have someone looking into this... > I am wondering if there would be a version of PC PINE in the future > that would support this in the future. (A version for the MAC would > be nice too.) > PC PINE does run on a MAC!!! Crank up SoftPC, connect the MAC modem to COM1, start packet drivers (EtherSLIP), and you are ready to roll with PC-pine! A MAC/SoftPC ethernet version would be nice, but we can't find any packet drivers for this ... From owner-pine-info@cac.washington.edu Mon Jul 19 09:17:22 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10469; Mon, 19 Jul 93 09:17:22 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09308; Mon, 19 Jul 93 09:09:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from qualcom.qualcomm.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09302; Mon, 19 Jul 93 09:09:32 -0700 Received: by qualcomm.com; id AA08366 sendmail 5.65/QC-main-2.1 Mon, 19 Jul 93 09:09:25 -0700 for pine-info@cac.washington.edu Date: Mon, 19 Jul 1993 09:09:08 -0700 (PDT) From: Jason Hough Reply-To: Jason Hough Subject: Signatures To: 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: If you will notice in my message, as well as the one attached, the signature is inserted before the text of the included message. Is there a switch or something in Pine that will append the signature at the end of the included message? +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- Jason Hough / jhough@qualcomm.com / CS Hotline / Ext. 5707 / Page:621-8657 "I like to help the humans." - Kramer, _Seinfeld_ +-+-PINE+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+NTTAWWT+-+- On Mon, 19 Jul 1993, David L Miller wrote: > > > -- > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > On Sun, .... From owner-pine-info@cac.washington.edu Mon Jul 19 10:15:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12462; Mon, 19 Jul 93 10:15:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07536; Mon, 19 Jul 93 10:04:16 -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 AA07530; Mon, 19 Jul 93 10:04:15 -0700 Received: by krypton.mankato.msus.edu (5.65/DEC-Ultrix/4.3) id AA16744; Mon, 19 Jul 1993 12:06:56 -0500 Date: Mon, 19 Jul 1993 12:02:45 -0500 (CDT) From: "Robert A. Hayden" Subject: Pico Request To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Here's a request I have for pico. Blocking. I use my account (and thus pine et al) over a relatively slow 9600 baud modem. One of the most annoying things is when I want to delete several lines and every time I do a ^K it will delete the line and then rewrite the whole screen. If there was a way to block a section and then delete all of the blocked material, it would significantly reduce the amount of screen rewrite and headaches. I'd think a singly key sequence that toggled blocking on/off would do the trick, in order to keep it simple. {[> Robert A. Hayden ____ hayden@krypton.mankato.msus.edu <]} {[> \ /__ hayden@att2.cs.mankato.msus.edu <]} {[> \/ / aq650@slc4.INS.CWRU.Edu <]} {[> #include \/ <]} -=-=- GEEK CODE v1.0.1: GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Random Thought: "Real education must be limited to men who *insist* on knowing. The rest is mere sheep-herding." -- Ezra Pound -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- From owner-pine-info@cac.washington.edu Mon Jul 19 10:36:25 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14256; Mon, 19 Jul 93 10:36:25 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07995; Mon, 19 Jul 93 10:27:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07989; Mon, 19 Jul 93 10:27:35 -0700 Received: from norman.nwnet.net by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA07980; Mon, 19 Jul 93 10:27:13 -0700 Date: Mon, 19 Jul 1993 10:23:43 -0700 (PDT) From: Laurence Lundblade Subject: Re: Signatures 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 Status: O X-Status: Yes, you can add "old-style-reply=yes" to your .pinerc and the signature will come at the end. The idea is that having the "reply" or new text at the top with the past references at the bottom is more readable than the old conventional way of doing it. LL On 19 Jul 1993, Jason Hough wrote: > If you will notice in my message, as well as the one attached, the signature is > inserted before the text of the included message. Is there a switch or something in Pine > that will append the signature at the end of the included message? > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- > Jason Hough / jhough@qualcomm.com / CS Hotline / Ext. 5707 / Page:621-8657 > "I like to help the humans." > - Kramer, _Seinfeld_ > +-+-PINE+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+NTTAWWT+-+- > > > On Mon, 19 Jul 1993, David L Miller wrote: > > > > > > > -- > > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > > > On Sun, .... > > > > > > > From owner-pine-info@cac.washington.edu Mon Jul 19 11:56:08 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17823; Mon, 19 Jul 93 11:56:08 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09423; Mon, 19 Jul 93 11:46:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from INDIV-GW.CENT.NET by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09417; Mon, 19 Jul 93 11:46:03 -0700 Received: by individual.com (5.65c/Spike-2.1) id AA02309; Mon, 19 Jul 1993 14:43:23 -0400 Date: Mon, 19 Jul 1993 13:27:25 -0400 (EDT) From: Adam J Weitzman Subject: Re: Signatures To: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Mon, 19 Jul 1993, Laurence Lundblade wrote: > Yes, you can add "old-style-reply=yes" to your .pinerc and the signature > will come at the end. The idea is that having the "reply" or new text > at the top with the past references at the bottom is more readable than > the old conventional way of doing it. By the way, who decided this? I think the old-style reply is at least 100x more readable than the "new" way, maily because (a) you can get the context of the message being replied to much easier than having to flip between the bottom and top of the message all the time, (b) it encourages people to edit the quoted text to only leave what's important as opposed to just leaving the whole thing at the bottom, which saves bandwidth, and (c) if you have a message with many points you want to respond to, it facilitates going into the middle of the message and putting your points there, rather than collecting them all in one place where it's sometimes hard to figure out what's being responded to. Thank goodness they have a setting for it, or I don't think I'd be using Pine at all. - Adam J Weitzman INDIVIDUAL, Inc. weitzman@individual.com From owner-pine-info@cac.washington.edu Mon Jul 19 13:27:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20962; Mon, 19 Jul 93 13:27:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10619; Mon, 19 Jul 93 13:18:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ericir.syr.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10613; Mon, 19 Jul 93 13:18:03 -0700 Received: by ericir.syr.edu (NX5.67c/NX3.0M) id AA23482; Mon, 19 Jul 93 16:18:25 -0400 Date: Mon, 19 Jul 1993 16:17:33 -0400 (EDT) From: Virtual Dave Lankes Subject: sub-directories To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: Is there any plan to permit sub-directories in Pine mail folders (I guess they would be sub-folders). It would help us organize, but could add too much complexity. ..................................................... : "Virtual" Dave Lankes rdlankes@ericir.syr.edu : : AskERIC Consultant <--SPIN--> EGIS Coordinator : : School of Information Studies,Syracuse University : ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From owner-pine-info@cac.washington.edu Mon Jul 19 13:34:17 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21217; Mon, 19 Jul 93 13:34:17 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10657; Mon, 19 Jul 93 13:24:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from optima.CS.Arizona.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10651; Mon, 19 Jul 93 13:24:20 -0700 Received: from wolf.CS.Arizona.EDU by optima.CS.Arizona.EDU (5.65c/15) via SMTP id AA22441; Mon, 19 Jul 1993 13:24:16 MST Received: by wolf.cs.arizona.edu; Mon, 19 Jul 1993 13:24:15 MST Date: Mon, 19 Jul 1993 13:13:06 -0700 (MST) From: Jim Davis Reply-To: Jim Davis Subject: Re: Signatures To: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Status: O X-Status: On Mon, 19 Jul 1993, Adam J Weitzman wrote: > (b) it > encourages people to edit the quoted text to only leave what's important > as opposed to just leaving the whole thing at the bottom, which saves > bandwidth Absolutely. Also, how do you know some new text doesn't follow the old quoted text at the bottom? I end up scanning the old message (bloated sig and all) again anyway. > Thank goodness they have a setting for it, or I don't think I'd be using > Pine at all. I'll second that. As much as I like pine, if the old-style-reply option goes away, I'm freeing up some disk space. -- Jim Davis | "He gave me so many flowers I thought it was an jdavis@cs.arizona.edu | allergy test." -- Clarissa Darling From owner-pine-info@cac.washington.edu Mon Jul 19 13:44:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21754; Mon, 19 Jul 93 13:44:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10732; Mon, 19 Jul 93 13:36:05 -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 AA10726; Mon, 19 Jul 93 13:36:04 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA22100 sendmail 5.67/UCSD-2.2-sun via SMTP Mon, 19 Jul 93 13:36:03 -0700 for pine-info@cac.washington.edu Received: from localhost (localhost [127.0.0.1]) by weber.ucsd.edu (8.3/UCSDGENERIC.4c) with SMTP id NAA21686; Mon, 19 Jul 1993 13:36:02 -0700 Message-Id: <199307192036.NAA21686@weber.ucsd.edu> To: pine-info@cac.washington.edu Subject: elm-style-save=yes + '%'-hack From: addresses + UNIX Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 19 Jul 1993 13:36:02 -0700 From: "Michael J. Corrigan" Status: RO X-Status: Say that received mail has a From: address like user%host@domain. With elm-style-save=yes option, when saving the message, pine prompts with a default savefilename 'user%host'. If you accept the default then pine refuses to create a savefilename with a '%' sign (although it could). Is there some way to get around this problem ? (i.e. to have the default savefile name be based on the From: line and be permissible to pine) The user who has this problem wanted pine to strip the "%host" in addition to the @domain. Is this feature worthy of consideration as a pine-enhancement ? Apologies if this matter is covered in the documentation or has been resolved on the pine-info list (looked but didn't find). Thanks -Mike Corrigan From owner-pine-info@cac.washington.edu Mon Jul 19 13:54:52 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22008; Mon, 19 Jul 93 13:54:52 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11477; Mon, 19 Jul 93 13:45: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 AA11471; Mon, 19 Jul 93 13:45:51 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07206; Mon, 19 Jul 93 13:45:47 -0700 Date: Mon, 19 Jul 1993 13:43:04 -0700 (PDT) From: David L Miller Subject: Re: sub-directories To: Virtual Dave Lankes 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: PC-pine and the upcoming Unix pine support folder collections which are logical groupings of folders. Work is in progress to define a way to handle hierarchical folders, but it is not completed yet. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Mon, 19 Jul 1993, Virtual Dave Lankes wrote: > Is there any plan to permit sub-directories in Pine mail folders (I guess > they would be sub-folders). It would help us organize, but could add too > much complexity. > > ..................................................... > : "Virtual" Dave Lankes rdlankes@ericir.syr.edu : > : AskERIC Consultant <--SPIN--> EGIS Coordinator : > : School of Information Studies,Syracuse University : > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > From owner-pine-info@cac.washington.edu Mon Jul 19 20:45:13 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03394; Mon, 19 Jul 93 20:45:13 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12827; Mon, 19 Jul 93 20:35:34 -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 AA12821; Mon, 19 Jul 93 20:35:33 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA17668; Mon, 19 Jul 93 20:33:27 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA21758; Mon, 19 Jul 93 20:38:05 -0700 Date: Mon, 19 Jul 1993 20:34:23 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Signatures 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 Status: O X-Status: On Mon, 19 Jul 1993, Jason Hough wrote: > If you will notice in my message, as well as the one attached, the signature is > inserted before the text of the included message. Is there a switch or something in Pine > that will append the signature at the end of the included message? > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- > Jason Hough / jhough@qualcomm.com / CS Hotline / Ext. 5707 / Page:621-8657 > "I like to help the humans." > - Kramer, _Seinfeld_ > +-+-PINE+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+NTTAWWT+-+- > Yeah...Set the OLD-STYLE-REPLY (sp?) flag to YES in .pinerc... 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 Mon Jul 19 20:55:23 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03499; Mon, 19 Jul 93 20:55:23 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12876; Mon, 19 Jul 93 20:47:19 -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 AA12870; Mon, 19 Jul 93 20:47:15 -0700 Received: from mundania.CS.ORST.EDU by instruction.CS.ORST.EDU (1.37.109.4/1.35) id AA17709; Mon, 19 Jul 93 20:44:15 -0700 Received: by mundania.CS.ORST.EDU (1.37.109.4/CS-Client) id AA21766; Mon, 19 Jul 93 20:48:38 -0700 Date: Mon, 19 Jul 1993 20:45:45 -0700 (PDT) From: "Jason R. Thorpe" Subject: Re: Pico Request To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Mon, 19 Jul 1993, Robert A. Hayden wrote: > Here's a request I have for pico. > > Blocking. > > I use my account (and thus pine et al) over a relatively slow 9600 baud > modem. One of the most annoying things is when I want to delete several > lines and every time I do a ^K it will delete the line and then rewrite > the whole screen. Yeah...A VERY cool idea...I'd like to see this too, cause when I'm not in my office, I have to dial in at 2400 or sometimes 1200 (AARGH!) baud! > > If there was a way to block a section and then delete all of the blocked > material, it would significantly reduce the amount of screen rewrite and > headaches. > > I'd think a singly key sequence that toggled blocking on/off would do the > trick, in order to keep it simple. > > {[> Robert A. Hayden ____ hayden@krypton.mankato.msus.edu <]} > {[> \ /__ hayden@att2.cs.mankato.msus.edu <]} > {[> \/ / aq650@slc4.INS.CWRU.Edu <]} > {[> #include \/ <]} > -=-=- > GEEK CODE v1.0.1: GSS d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ > n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Random Thought: > > "Real education must be limited to men who *insist* on knowing. The rest > is mere sheep-herding." > -- Ezra Pound > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > /***************************************************************************** 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 Tue Jul 20 03:05:42 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09080; Tue, 20 Jul 93 03:05:42 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18494; Tue, 20 Jul 93 02:48:43 -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 AA18488; Tue, 20 Jul 93 02:48:42 -0700 Via: uk.co.ggr; Tue, 20 Jul 1993 10:47:59 +0100 Received: from uk0x04.ggr.co.uk by uk0x08.ggr.co.uk; Tue, 20 Jul 93 10:48:59 BST Received: from uk0x04.ggr.co.uk by mailhub.ggr.co.uk (5.59/imd-070593) id AA14818; Tue, 20 Jul 93 10:34:17 BST Received: by uk0x04.ggr.co.uk (4.1/imd110593) id AA08608; Tue, 20 Jul 93 10:38:26 BST Date: Tue, 20 Jul 1993 10:33:04 +0100 (BST) From: Ian Dunkin Subject: Re: Pico Request To: "Jason R. Thorpe" Cc: "Robert A. Hayden" , Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Status: O X-Status: On Mon, 19 Jul 1993, Robert A. Hayden wrote: > > If there was a way to block a section and then delete all of the blocked > material, it would significantly reduce the amount of screen rewrite and > headaches. On Mon, 19 Jul 1993, Jason R. Thorpe replied: > > Yeah...A VERY cool idea...I'd like to see this too, cause when I'm not in > my office, I have to dial in at 2400 or sometimes 1200 (AARGH!) baud! Since pico is a cut-down MicroEMACS, which itself does provide this functionality (set-mark, kill-region), presumably it was actually turned _off_ in pico? I. From owner-pine-info@cac.washington.edu Tue Jul 20 05:28:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11341; Tue, 20 Jul 93 05:28:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19436; Tue, 20 Jul 93 05:15:16 -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 AA19429; Tue, 20 Jul 93 05:15:14 -0700 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0RBK7QGEO00016Q@mc.duke.edu>; Tue, 20 Jul 1993 08:20:17 EST Date: Tue, 20 Jul 1993 08:14:44 -0500 (EST) From: James Dryfoos- Postmaster Subject: Pine 3.07, MIME attachments and core dump. To: pine-info@cac.washington.edu Message-Id: <01H0RBRMH6PW00016Q@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 Status: O X-Status: Though told 3.07 was supposed to fix this, I still get consistent core dump when responding to mail that has text and a text attachment. Here is the contents of the message I try to reply to as viewed using mail: >From JR@mc.duke.edu Mon Jul 19 17:22:59 1993 Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0QGFNC8AO000D2X@mc.duke.edu>; Mon, 19 Jul 1993 17:29:45 EST Date: Mon, 19 Jul 1993 17:29:45 -0500 (EST) From: JR@mc.duke.edu Subject: What happened to my CLIF mailing list? To: dryfo001@mc.duke.edu Message-Id: <01H0QGO7WXHW000D2X@mc.duke.edu> Organization: Duke University Medical Center, Durham NC, USA Mime-Version: 1.0 Content-Type: MESSAGE/RFC822 Status: R Return-path: Received: from MAILSERV-DAEMON by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0QGKQR2U800004Y@mc.duke.edu>; Mon, 19 Jul 1993 17:26:46 EST Date: Mon, 19 Jul 1993 17:26:46 -0500 (EST) From: "PMDF Mailserv V4.2" Subject: Errors in MAILSERV command processing To: JR@mc.duke.edu Message-id: <01H0QGKRLMDU00004Y@mc.duke.edu> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Error processing the command: sub CLIF "Cee Jay Dozar" No such mailing list CLIF %MAILSERV-W-LNF, mailing list not found Subsequent commands ignored because of previous error. Ignored: sub CLIF "Les Cordova" Ignored: unsub CLIF Use the HELP command to get a list of legal MAILSERV commands. Here is the contents of the message I try to reply to as viewed using pine with headers on: Received: from mc.duke.edu by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0QGFNC8AO000D2X@mc.duke.edu>; Mon, 19 Jul 1993 17:29:45 EST Date: Mon, 19 Jul 1993 17:29:45 -0500 (EST) From: JR@mc.duke.edu Subject: What happened to my CLIF mailing list? To: dryfo001@mc.duke.edu Message-Id: <01H0QGO7WXHW000D2X@mc.duke.edu> Organization: Duke University Medical Center, Durham NC, USA Mime-Version: 1.0 Content-Type: MESSAGE/RFC822 Return-path: Received: from MAILSERV-DAEMON by mc.duke.edu (PMDF V4.2-13 #3229) id <01H0QGKQR2U800004Y@mc.duke.edu>; Mon, 19 Jul 1993 17:26:46 EST Date: Mon, 19 Jul 1993 17:26:46 -0500 (EST) From: "PMDF Mailserv V4.2" Subject: Errors in MAILSERV command processing To: JR@mc.duke.edu Message-id: <01H0QGKRLMDU00004Y@mc.duke.edu> MIME-version: 1.0 Content-type: TEXT/PLAIN; CHARSET=US-ASCII Content-transfer-encoding: 7BIT Error processing the command: sub CLIF "Cee Jay Dozar" No such mailing list CLIF %MAILSERV-W-LNF, mailing list not found Subsequent commands ignored because of previous error. Ignored: sub CLIF "Les Cordova" Ignored: unsub CLIF Use the HELP command to get a list of legal MAILSERV commands. Here is the contents of the message I try to reply to as viewed using pine with headers off: Date: Mon, 19 Jul 1993 17:29:45 -0500 (EST) From: JR@mc.duke.edu To: dryfo001@mc.duke.edu Subject: What happened to my CLIF mailing list? Parts/attachments: 1 Shown 861 bytes Message 1.1 Shown 7 lines Text ---------------------------------------- ----- Part 1 "Included Message" ----- Date: Mon, 19 Jul 1993 17:26:46 -0500 (EST) From: "PMDF Mailserv V4.2" To: JR@mc.duke.edu Subject: Errors in MAILSERV command processing Error processing the command: sub CLIF "Cee Jay Dozar" No such mailing list CLIF %MAILSERV-W-LNF, mailing list not found Subsequent commands ignored because of previous error. Ignored: sub CLIF "Les Cordova" Ignored: unsub CLIF Use the HELP command to get a list of legal MAILSERV commands. Sorry for all the stuff above. Was not sure what was helpful. -- Jim From owner-pine-info@cac.washington.edu Tue Jul 20 08:43:02 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14533; Tue, 20 Jul 93 08:43:02 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15492; Tue, 20 Jul 93 08:33:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mach1.wlu.ca by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15486; Tue, 20 Jul 93 08:33:09 -0700 Received: by mach1.wlu.ca (5.65/1.35) id AA00491; Tue, 20 Jul 93 11:32:45 -0400 Date: Tue, 20 Jul 1993 11:20:58 -0300 (EDT) From: bob ellsworth s Reply-To: bob ellsworth s Subject: imapd problems on ptx To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Status: O X-Status: hi : i am having problems with the imapd server daemon on a ptx sequent symmetry system. (v 2.0.0) i have placed the imapd executable in the /usr/etc/ directory and added the appropriate entries to /etc/services and /etc/inetd.conf but whenever i attempt to connect to the imapd daemon from pine or mtest the following scenario unfolds: - the imapd2b daemon announces itself - the impad daemon requests a login and password which i provide i then get the following three messages - IMAP connection broken in reply. - Login failed: IMAP connection broken in reply - Too many login failures i have tried connecting from a second ptx mainframe using pine 3.05 and also from a pc using the pc/tcp version of pine. also when i try a telnet to the 143 port, imapd wakes up and announces itself but the connection is broken once i try to enter an IMAP command manually. Can any of the pine people or ptx people on this list provide me with some suggestions as to how to proceed on this problem. thanks. From owner-pine-info@cac.washington.edu Tue Jul 20 10:17:29 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17714; Tue, 20 Jul 93 10:17:29 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22882; Tue, 20 Jul 93 10:06:53 -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 AA22876; Tue, 20 Jul 93 10:06:51 -0700 Via: uk.ac.bristol; Tue, 20 Jul 1993 18:06:21 +0100 Via: uk.ac.bristol.adm1; Tue, 20 Jul 1993 18:04:38 +0100 Date: Tue, 20 Jul 1993 17:31:50 +0100 (BST) From: Dave King Original-Sender: Dave King Reply-To: Dave King Subject: Re: imapd problems on ptx To: bob ellsworth s 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: Bob, I encountered exactly the same problem (on ptx 1.4), but have applied the following patch, kindly supplied by Mark (Crispin). As the saying goes "It worked for me", and imap works with PCPine, etc. as expected. *** imapd.c Tue Jul 13 14:44:42 1993 --- imapd-ptx.c Wed Jul 14 15:31:33 1993 *************** *** 47,52 **** --- 47,54 ---- #include #include #include "misc.h" + #include + #include /* Autologout timer */ *************** *** 147,152 **** --- 149,157 ---- char *s,*t = "OK",*u,*v; struct hostent *hst; void (*f) () = NIL; + t_sync (0); + ioctl (0,I_PUSH,"tirdwr"); + dup2 (0,1); mail_link (&tenexdriver); /* install the Tenex mail driver */ mail_link (&bezerkdriver); /* install the Berkeley mail driver */ mail_link (&imapdriver); /* install the IMAP driver */ Going on past experience (and much frustration) of porting C code to ptx, Pine is in a class of its own. It compiled "as delivered", and has never let me down. Cheers, Dave PS I think the "tirdwr" kludge must rate #2 to "-lseq" for ptx fixups ... ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Email: Dave.King@uk.ac.Bristol Tel: 0272 303961 (Direct Line) On Tue, 20 Jul 1993, bob ellsworth s wrote: > hi : i am having problems with the imapd server daemon on a ptx sequent > symmetry system. (v 2.0.0) i have placed the imapd executable in the > /usr/etc/ directory and added the appropriate entries to /etc/services and > /etc/inetd.conf but whenever i attempt to connect to the imapd daemon from > pine or mtest the following scenario unfolds: > > - the imapd2b daemon announces itself > - the impad daemon requests a login and password which i provide > > i then get the following three messages > > - IMAP connection broken in reply. > - Login failed: IMAP connection broken in reply > - Too many login failures > > i have tried connecting from a second ptx mainframe using pine 3.05 and > also from a pc using the pc/tcp version of pine. also when i try a > telnet to the 143 port, imapd wakes up and announces itself but the > connection is broken once i try to enter an IMAP command manually. > > Can any of the pine people or ptx people on this list provide me with some > suggestions as to how to proceed on this problem. thanks. > > From owner-pine-info@cac.washington.edu Tue Jul 20 15:58:24 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07962; Tue, 20 Jul 93 15:58:24 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18428; Tue, 20 Jul 93 15:45:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from UCS.ORST.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18420; Tue, 20 Jul 93 15:45:30 -0700 Received: by ucs.orst.edu (5.57/fma-120691); id AA09027; Tue, 20 Jul 93 15:45:29 -0700 Date: Tue, 20 Jul 1993 15:41:30 -0700 (PDT) From: Debra Crowe Subject: PINE & Disk Quotas To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine-folk, We've recently implemented disk quotas on our mail spool area in an attempt to control the problem of users who let their mail inbox get out of control (10MB...). Interestingly enough, we've noticed a quirk with pine not allowing users who've reached their mail spool limit to delete any messages from their inbox. Elm and mail will allow the messages to be deleted, but pine won't 'expunge' them. We're running pine vsn 3.05 on a DEC 5900 w/Ultrix 4.3. Anyone else aware of this problem/feature and it's fix? Will an upgrade to 3.07 fix this? Thanks, Debra Crowe, User Services Email: crowede@ucs.orst.edu University Computing Services Phone: (503) 737-2998 Oregon State University Corvallis, OR 97331 From owner-pine-info@cac.washington.edu Tue Jul 20 16:35:07 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11800; Tue, 20 Jul 93 16:35:07 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18682; Tue, 20 Jul 93 16:24:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18676; Tue, 20 Jul 93 16:24:57 -0700 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA10436; Tue, 20 Jul 93 16:24:54 -0700 Date: Tue, 20 Jul 1993 16:09:57 -0700 (PDT) From: Mark Crispin Subject: re: PINE & Disk Quotas To: Debra Crowe Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi Debra - That particular quirk isn't fixed yet, but it is on my list (= I'm the turkey to beat up about it). The problem is that Pine makes a worst-case guess of how much disk space it will need to complete a checkpoint or expunge before it will do it, and if it cannot obtain that worst-case space it will decline to do the operation. Pine's estimate is a bit too conservative; it multiplies the number of messages by the size of a maximum-sized Status:/X-Status: pair of lines and adds that to the current message size. It makes no adjustment for messages which may already have Status:/X-Status: lines; doing this via kludge is easy, doing it right (safely) is hard. Worse, it makes no adjustment in expunge for messages which are deleted. The concept to fix the latter is easy; an implementation that is guaranteed safe is much harder. In particular, I am worried about the scenario of what happens when the user does an expunge, but even after the expunge she is still over quota. [This is particularly likely to happen in transition to quotas, such as you are doing now.] Some systems will not permit you to rewrite data over quota, even if the result of the rewrite is to make you be less over quota. In other words, I am very worried about the prospect of leaving the user with a damaged mail folder. Although it's bad to force the user to seek expert help when she is over quota, it's worse to risk destroying her mail folder. It's one thing to accept the risk by running Elm or mail; it's quite another for Pine (which is advertised to be a safe ``rubber room'') to make such decisions... The workaround for this problem is to be sure that the user is alerted to the problem when she crosses her soft quota, so she doesn't reach her hard quota. This isn't the final word on this issue. -- Mark -- From owner-pine-info@cac.washington.edu Wed Jul 21 06:49:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06681; Wed, 21 Jul 93 06:49:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27615; Wed, 21 Jul 93 06:33:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ees1a0.engr.ccny.cuny.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27609; Wed, 21 Jul 93 06:33:54 -0700 Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1) id AA17177; Wed, 21 Jul 93 09:21:32 EDT Date: Wed, 21 Jul 1993 08:52:41 -0400 (EDT) From: Dan Schlitt Subject: Re: PINE & Disk Quotas To: Debra Crowe Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Disk quotas are a good thing but they are not the answer to all disk useage problems. I lean toward the position that they are not a good solution to the system mailbox size problem. The solution that I have used is to monitor the useage on a regular basis. In most cases the disk partition that contains the system mail spool also has other spools in it. Quotas will control the aggregate use of all of these spools and not just the mailboxes. On our Sun systems we NFS mount the mailspool. The Sun quota suite is not good about warning users of quota problems on NFS mounted directories. I would not want mail to fail and be lost because of quota problems, even for an uncooperative user who insists on keeping a very large system mailbox. I value e-mail service too highly to allow this kind of problem. It is my impression that sendmail will not know about the quotas on the system mail spool when it accepts mail from a remote site. Such mail will be queued in sendmail's spool directory for local delivery. If these two spools share the same partition then what has the quota gained you in saved disk space? It has just delayed the delivery of the mail at best. Generally mailboxes grow fairly slowly so regular monitoring will allow the manager to detect problems before they become critical. Exceptions are cases where a user is the subject of a "mail bombing" or does something dumb like having a 10 Meg file mailed to them. Those cases will probably require intervention even in the presence of quotas. I monitor disk useage on a partition basis ( df(1) ) daily. The spool partition needs to have enough free space that I can detect and deal with problems before they create real problems. At weekly intervals I use a public domain program called cobwebs to list large and old mailboxes. You can probably write an awk script or a perl program to do the same thing. I have adopted a variety of methods of dealing with large mailboxes which range from notification of the user to immediate active intervention. Once users realize that there are limits to what is acceptable in the way of keeping mail in the system mailbox they will tend to keep thing reasonable. Monitoring overall disk useage is good management so that is not really added time spent on mail. It doesn't take much time to scan the list of big and old mailboxes. I spend very little time in managing this proble. This is not to say that Mark shouldn't fix the things that he says he would like to fix. It does suggest that quotas may be a meat axe approach to a problem that is better treated more delicately. Dan Schlitt School of Engineering Computer Systems dan@ee-mail.engr.ccny.cuny.edu City College of New York (212)650-6760 New York, NY 10031 From owner-pine-info@cac.washington.edu Wed Jul 21 08:39:21 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15032; Wed, 21 Jul 93 08:39:21 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23591; Wed, 21 Jul 93 08:22:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [156.12.23.1] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23585; Wed, 21 Jul 93 08:22:02 -0700 Received: by acad.csv.kutztown.edu.csv.kutztown.edu (5.61/1.35) id AA10540; Wed, 21 Jul 93 11:22:34 -0400 Date: Wed, 21 Jul 1993 11:17:46 -0400 (EDT) From: "Lisa M. Frye" Subject: Re: PINE & Disk Quotas To: Debra Crowe Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Another possibility is the program mailclean. We have just starting using this program here at Kutztown and I am finding it works well. You can set a size of how large an inbox can become and run mailclean. If mailclean encounters an inbox that is larger than the specified size, it will save the inbox in the /tmp (by default, which can be changed) directory. The user will receive a mail message indicating that their inbox was too large and it will tell them where there inbox was saved and how they can access it. Then you can clean the /tmp directory as you wish. The "folder" created in the /tmp directory is accessible by pine. So far, this is working great - it keeps our inboxes to a manageable size and still allows the user ample time to retrieve the "other inbox". Lisa Frye 683-4474 Computer Services LMS Annex Room 105 Kutztown University frye@acad.csv.kutztown.edu "You can bring a person to the university, but you can't make them think." From owner-pine-info@cac.washington.edu Wed Jul 21 09:25:31 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19260; Wed, 21 Jul 93 09:25:31 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23930; Wed, 21 Jul 93 09:10:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from camco1.wa.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23924; Wed, 21 Jul 93 09:10:17 -0700 Received: by camco2.celestial.com (Smail3.1.28.1 #9) id m0oIgir-0002kDC; Wed, 21 Jul 93 09:08 PDT Date: Wed, 21 Jul 1993 09:03:13 +0100 (PDT) From: Bill Campbell Subject: Pine 3.07 on SCO -- testing help wanted To: pine-info@cac.washington.edu Cc: Bill Campbell , Ray Jones , sco-list-post@celestial.com Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm composing this e-mail in pico on pine 3.07 as compiled on an SCO ODT 3.0 (well actually 2.1 beta :-) system. At this point it still needs testing. I did find a problem where asking for disk space caused an exec to fail, but haven't really looked at that yet. Is there anybody out there who would like to help me test this (I've never used pine before so don't know what to expect). Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Software UUCP: ...!thebes!camco!bill 6641 East Mercer Way uunet!camco!bill Mercer Island, WA 98040; (206) 947-5591 SPEED COSTS MONEY -- HOW FAST DO YOU WANT TO GO? From owner-pine-info@cac.washington.edu Thu Jul 22 08:43:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23804; Thu, 22 Jul 93 08:43:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18119; Thu, 22 Jul 93 08:25:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from phloem.uoregon.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18113; Thu, 22 Jul 93 08:25:29 -0700 Received: from ccmail.uoregon.edu (ccmail-mailhost.uoregon.edu) by phloem.uoregon.edu (4.1/UofO NetSvc-02/16/93) id AA12454; Thu, 22 Jul 93 08:25:27 PDT Received: from cc:Mail by ccmail.uoregon.edu id AA743354808 Thu, 22 Jul 93 08:26:48 pst Date: Thu, 22 Jul 93 08:26:48 pst From: Rich_Haller@ccmail.uoregon.edu (Rich Haller) Message-Id: <9306227433.AA743354808@ccmail.uoregon.edu> To: pine-info@cac.washington.edu Subject: International character sets MIME supports several ISO international character sets in addition to US-ASCII. Does the current unix pine client (and any others) support creation and display of text from a vt100 (emulated) keyboard in any of these alternate charsets? If so, where can I find the documentation? From owner-pine-info@cac.washington.edu Thu Jul 22 09:01:09 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25353; Thu, 22 Jul 93 09:01:09 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19107; Thu, 22 Jul 93 08:49: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 AA19099; Thu, 22 Jul 93 08:49:51 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15668; Thu, 22 Jul 93 08:49:49 -0700 Date: Thu, 22 Jul 1993 08:45:19 -0700 (PDT) From: David L Miller Subject: Re: International character sets To: Rich Haller Cc: pine-info@cac.washington.edu In-Reply-To: <9306227433.AA743354808@ccmail.uoregon.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine supports international character sets to the extent that it assumes that if you say you are using ISO-8859-7, that that is what you are indeen entering. i.e. It does not attempt to do any translation. Most vt100 emulators allow you to specify an alternate keyboard mapping, so you can set it up to use whatever character set you want. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 22 Jul 1993, Rich Haller wrote: > > MIME supports several ISO international character sets in addition to US-ASCII. > Does the current unix pine client (and any others) support creation and display > of text from a vt100 (emulated) keyboard in any of these alternate charsets? If > so, where can I find the documentation? > From owner-pine-info@cac.washington.edu Thu Jul 22 11:45:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10350; Thu, 22 Jul 93 11:45:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25801; Thu, 22 Jul 93 11:34:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from netnews.ciesin.org by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25795; Thu, 22 Jul 93 11:34:35 -0700 Received: from spring.ciesin.org by mail.ciesin.org with SMTP id AA10558 (5.65c/IDA-1.4.4 for ); Thu, 22 Jul 1993 14:34:35 -0400 Date: Thu, 22 Jul 1993 14:32:45 -0400 (EDT) From: Viswanath Gopalakrishnan Subject: Problems with setting default editor To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! I am unable to set the default editor to vi, using the entry in my .pinerc file. I am using pine 3.04 on Sparc10s, under AFS. Any clues as to what I could be missing ? Thanks Vishy =========================================================================== Viswanath "Vishy" Gopalakrishnan, vishy@mail.ciesin.org Consortium for International Earth Science Information Network [CIESIN] =========================================================================== From owner-pine-info@cac.washington.edu Thu Jul 22 12:04:10 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12999; Thu, 22 Jul 93 12:04:10 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26584; Thu, 22 Jul 93 11:54:03 -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 AA26578; Thu, 22 Jul 93 11:54:01 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20278; Thu, 22 Jul 93 11:53:56 -0700 Date: Thu, 22 Jul 1993 11:49:33 -0700 (PDT) From: David L Miller Subject: Re: Problems with setting default editor 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 You cannot set an alternate editor to be default. You always have to use "^_" to get to it. You also cannot use the alternate editor on the headers. Sorry. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 22 Jul 1993, Viswanath Gopalakrishnan wrote: > > Hi! > > I am unable to set the default editor to vi, using the entry in my > .pinerc file. I am using pine 3.04 on Sparc10s, under AFS. > > Any clues as to what I could be missing ? > > Thanks > > Vishy > > =========================================================================== > Viswanath "Vishy" Gopalakrishnan, vishy@mail.ciesin.org > Consortium for International Earth Science Information Network [CIESIN] > =========================================================================== > > > From owner-pine-info@cac.washington.edu Thu Jul 22 14:32:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23818; Thu, 22 Jul 93 14:32:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04252; Thu, 22 Jul 93 14:18:18 -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 AA04246; Thu, 22 Jul 93 14:18:12 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA03309; Thu, 22 Jul 93 17:18:00 -0400 Received: from merint.UUCP by spool.uu.net with UUCP/RMAIL (queueing-rmail) id 171226.29782; Thu, 22 Jul 1993 17:12:26 EDT Received: by merint (AIX 3.2/UCB 5.64/4.03) id AA06136; Thu, 22 Jul 1993 15:09:55 -0600 From: merint!root@uunet.UU.NET (God) Message-Id: <9307222109.AA06136@merint> To: uunet!pine-info%cac.washington.edu@uunet.UU.NET Cc: alexc%merint@uunet.UU.NET Subject: Spell Checker ... (ispell) Date: Thu, 22 Jul 93 15:09:54 -0700 Is there a way to include ispell in pine/pico ? It will be very helpful to allow use to use the "ispell" program to correct the mispelled words before the e-mail is being sendout. Ispell is part of the GNU program list. From owner-pine-info@cac.washington.edu Thu Jul 22 14:50:43 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25370; Thu, 22 Jul 93 14:50:43 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04388; Thu, 22 Jul 93 14:36:09 -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 AA04382; Thu, 22 Jul 93 14:36:04 -0700 Received: from shiva1.cac.washington.edu by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA09331; Thu, 22 Jul 93 17:35:39 -0400 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24251; Thu, 22 Jul 93 14:35:26 -0700 Date: Thu, 22 Jul 1993 14:34:26 -0700 (PDT) From: David L Miller Subject: Re: Spell Checker ... (ispell) To: God Cc: pine-info%cac.washington.edu@uunet.uu.net, alexc%merint@uunet.uu.net In-Reply-To: <9307222109.AA06136@merint> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Set your alternate editor to ispell. Then ispell will be called whenever you press "^_". -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Thu, 22 Jul 1993, God wrote: > > > Is there a way to include ispell in pine/pico ? It will be very > helpful to allow use to use the "ispell" program to correct the > mispelled words before the e-mail is being sendout. Ispell is > part of the GNU program list. > > From owner-pine-info@cac.washington.edu Fri Jul 23 02:10:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11757; Fri, 23 Jul 93 02:10:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07889; Fri, 23 Jul 93 01:50:29 -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 AA07883; Fri, 23 Jul 93 01:50:26 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #86) id m0oJIpa-000036C; Fri, 23 Jul 93 09:50 BST Date: Fri, 23 Jul 1993 09:47:45 +0100 (BST) From: Philip Hazel Subject: Re: Problems with setting default editor To: David L Miller Cc: Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 22 Jul 1993, David L Miller wrote: > > You cannot set an alternate editor to be default. You always have to use > "^_" to get to it. You also cannot use the alternate editor on the > headers. Sorry. It would be very nice, though, if Pine were to enter your alternative editor automatically when you moved the cursor down into the text part of the message from the headers. (And when you are doing "reply".) I make lots of mistakes trying to operate with two different editors. I'm quite happy for it to go back to the default editor when you exit your alternative editor. 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 Fri Jul 23 03:54:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18421; Fri, 23 Jul 93 03:54:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25753; Fri, 23 Jul 93 03:39:37 -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 AA25746; Fri, 23 Jul 93 03:39:35 -0700 Via: uk.co.ggr; Fri, 23 Jul 1993 11:38:57 +0100 Received: from uk0x04.ggr.co.uk by uk0x08.ggr.co.uk; Fri, 23 Jul 93 11:39:53 BST Received: from uk0x04.ggr.co.uk by mailhub.ggr.co.uk (5.59/imd-070593) id AA28680; Fri, 23 Jul 93 11:32:54 BST Received: by uk0x04.ggr.co.uk (4.1/imd110593) id AA11173; Fri, 23 Jul 93 11:37:04 BST Date: Fri, 23 Jul 1993 11:33:56 +0100 (BST) From: Ian Dunkin Subject: Re: Problems with setting default editor To: Philip Hazel Cc: David L Miller , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 23 Jul 1993, Philip Hazel wrote: > It would be very nice, though, if Pine were to enter your alternative > editor automatically when you moved the cursor down into the text part of > the message from the headers. (And when you are doing "reply".) I make lots > of mistakes trying to operate with two different editors. I'm quite happy > for it to go back to the default editor when you exit your alternative > editor. Yes, agreed exactly. The automatic invocation to be an _option_, I suppose. And returning to the default editor on exit from the alternative editor would let you review the header fields once more before sending, and so on. I. From owner-pine-info@cac.washington.edu Fri Jul 23 06:43:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29027; Fri, 23 Jul 93 06:43:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00657; Fri, 23 Jul 93 06:25:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from offsv1.cis.McMaster.CA by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00651; Fri, 23 Jul 93 06:25:17 -0700 Received: by offsv1.cis.mcmaster.ca id AA13443 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 23 Jul 1993 09:25:41 -0400 Date: Fri, 23 Jul 1993 09:16:07 -0400 (EDT) From: Carolynn Spring Subject: Re: Problems with Distribution Lists (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I was wondering if anyone has experienced this problem and could shed some light on it for me. We have some time-sensitive notes that have to go out to a wide audience right now. Any help would be really appreciated. Thanks. ------------------------------------------------------------------------------- Carolynn Spring email: spring@mcmaster.ca Consultant, Desktop Support spring@mcmail.cis.mcmaster.ca Computing and Information Services McMaster University, ABB-132 ------------------------------------------------------------------------------ Further to the Memory fault problem stated below, I was wondering if disk space [or rather, the lack of it] was an issue. Investigation shows the following: Disk usage: /dev/home 54% /dev/usr 90% (This was at 98% at 5:00 pm yesterday) Home directories of the accounts that couldn't send messages: /home/mcmail/psych /home/mcmail/spring /home/mcmail/blanche /home/mcmail/mailhelp Home directory of the ONE known account that could send to a distribution list: /usr/people/mckay The alias file is located in /usr/local/pine and most lists are located in /usr/local/pine/dists. Carlene was trying to send to c-mcafee located in her directory and the alias points there. Carolynn Spring MAILHELP - PINE Administrator. ABB 132, ext. 7090 > > > The error message " sh: 13546 Memory fault " appears in the bottom > left hand corner of the screen approximately 1 to 5 minutes after sending > a message to a distribution list. The number changes but the message goes > to noone altho a copy is kept in sent-mail. This is true regardless of the > size of the message as I tried to send out a five line message and one > that was >10,000 bytes. Three different people tried to send to a > distribution list including mailhelp, blanche and psych. We all got > Memory faults. The lists and approx number of ids in each list that we > tried to send to were > c-alluse - 2068, pineuser - 1975, and c-mcaffee - 145. Any ideas? > > From owner-pine-info@cac.washington.edu Fri Jul 23 08:31:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06262; Fri, 23 Jul 93 08:31:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03859; Fri, 23 Jul 93 08:12: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 AA03853; Fri, 23 Jul 93 08:12:32 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09825; Fri, 23 Jul 93 08:12:23 -0700 Date: Fri, 23 Jul 1993 08:10:31 -0700 (PDT) From: David L Miller Subject: Re: Problems with setting default editor To: Ian Dunkin Cc: Philip Hazel , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is a single keystroke really that objectionable? -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Fri, 23 Jul 1993, Ian Dunkin wrote: > On Fri, 23 Jul 1993, Philip Hazel wrote: > > > It would be very nice, though, if Pine were to enter your alternative > > editor automatically when you moved the cursor down into the text part of > > the message from the headers. (And when you are doing "reply".) I make lots > > of mistakes trying to operate with two different editors. I'm quite happy > > for it to go back to the default editor when you exit your alternative > > editor. > > Yes, agreed exactly. The automatic invocation to be an _option_, I > suppose. And returning to the default editor on exit from the > alternative editor would let you review the header fields once more > before sending, and so on. > > I. > > > From owner-pine-info@cac.washington.edu Fri Jul 23 08:47:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07551; Fri, 23 Jul 93 08:47:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09966; Fri, 23 Jul 93 08:25:03 -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 AA09960; Fri, 23 Jul 93 08:24:59 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #86) id m0oJOzQ-000036C; Fri, 23 Jul 93 16:24 BST Date: Fri, 23 Jul 1993 16:13:44 +0100 (BST) From: Philip Hazel Subject: Re: Problems with setting default editor To: David L Miller Cc: Ian Dunkin , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Is a single keystroke really that objectionable? Not _objectionable_, but it is not an easy keystroke to make. You've been typing alphabetic things and pressing return to fill in the header; it would be nice to be able to go straight on without having to fiddle around to find ^_, which is not a key I can get at by touch-typing. I have to stop and look and it just feels uncomfortable. I'm clearly not the only person who feels this way. ... and, when replying, it is ANOTHER keystroke, after the millions of "Y"s you have to type to reply to everybody, include the original, use the "Reply-To" field, etc. I do tend to sit with my finger on "Y" when replying... Don't get me wrong. I think Pine is very good. Like many people, I don't even bother to comment about things I think are lousy! 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 Fri Jul 23 09:00:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08500; Fri, 23 Jul 93 09:00:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04813; Fri, 23 Jul 93 08:39:45 -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 AA04807; Fri, 23 Jul 93 08:39:43 -0700 Via: uk.co.ggr; Fri, 23 Jul 1993 16:38:28 +0100 Received: from uk0x04.ggr.co.uk by uk0x08.ggr.co.uk; Fri, 23 Jul 93 16:39:25 BST Received: from uk0x04.ggr.co.uk by mailhub.ggr.co.uk (5.59/imd-070593) id AA29973; Fri, 23 Jul 93 16:31:23 BST Received: by uk0x04.ggr.co.uk (4.1/imd110593) id AA11624; Fri, 23 Jul 93 16:35:33 BST Date: Fri, 23 Jul 1993 16:24:55 +0100 (BST) From: Ian Dunkin Subject: Re: Problems with setting default editor To: David L Miller Cc: Philip Hazel , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 23 Jul 1993, David L Miller wrote: > Is a single keystroke really that objectionable? I think it's more a problem with confusion, as Philip Hazel remarked in his original posting. > I make lots > of mistakes trying to operate with two different editors. The natural thing to do is to start typing away madly as soon as you get into the text area, and it's easy to forget which editor you're in. MY alternative editor of choice for Pine is actually MicroEMACS (our own slightly extended version). So pico is similar enough to feel familiar, and I _always_ pitch into word operations, marks, &c, till I realise that pico is beeping madly at me to stop because it's had those particular functions removed. So it's just a Would-Be-Nice. I. From owner-pine-info@cac.washington.edu Fri Jul 23 09:11:51 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09517; Fri, 23 Jul 93 09:11:51 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10122; Fri, 23 Jul 93 08:55:07 -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 AA10116; Fri, 23 Jul 93 08:55:03 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #86) id m0oJPSX-00003FC; Fri, 23 Jul 93 16:55 BST Date: Fri, 23 Jul 1993 16:54:04 +0100 (BST) From: Philip Hazel Subject: Re: Problems with setting default editor To: Ian Dunkin Cc: David L Miller , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > The natural thing to do is to start typing away madly as soon as you get > into the text area, and it's easy to forget which editor you're in. MY > alternative editor of choice for Pine is actually MicroEMACS (our own > slightly extended version). So pico is similar enough to feel familiar, > and I _always_ pitch into word operations, marks, &c, till I realise > that pico is beeping madly at me to stop because it's had those > particular functions removed. So it's just a Would-Be-Nice. Yes. Precisely! Thank you. You have expressed it much more clearly than I did. 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 Fri Jul 23 09:30:31 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11152; Fri, 23 Jul 93 09:30:31 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA06051; Fri, 23 Jul 93 09:09:43 -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 AA06045; Fri, 23 Jul 93 09:09:41 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12190; Fri, 23 Jul 93 09:09:30 -0700 Date: Fri, 23 Jul 1993 09:03:30 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: Problems with setting default editor To: Philip Hazel Cc: Ian Dunkin , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII What precisely do you want the behavior to be? Would this be correct? 1. Compose/forward: Start header editor. When cursor down is hit from last header line, alternate editor is entered on body of message. 2. Reply: Start Alternate editor on body of message. 3. Exit alternate editor: Start header editor. When cursor down is hit from last header line, alternate editor is entered on body of message. -- |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA On Fri, 23 Jul 1993, Philip Hazel wrote: > > The natural thing to do is to start typing away madly as soon as you get > > into the text area, and it's easy to forget which editor you're in. MY > > alternative editor of choice for Pine is actually MicroEMACS (our own > > slightly extended version). So pico is similar enough to feel familiar, > > and I _always_ pitch into word operations, marks, &c, till I realise > > that pico is beeping madly at me to stop because it's had those > > particular functions removed. So it's just a Would-Be-Nice. > > Yes. Precisely! Thank you. You have expressed it much more clearly than I > did. > > 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 Fri Jul 23 09:33:49 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11624; Fri, 23 Jul 93 09:33:49 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10325; Fri, 23 Jul 93 09:12:50 -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 AA10319; Fri, 23 Jul 93 09:12:45 -0700 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #86) id m0oJPjf-00003FC; Fri, 23 Jul 93 17:12 BST Date: Fri, 23 Jul 1993 17:11:36 +0100 (BST) From: Philip Hazel Subject: Re: Problems with setting default editor To: David L Miller Cc: Ian Dunkin , Viswanath Gopalakrishnan , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > What precisely do you want the behavior to be? Would this be correct? > > 1. Compose/forward: Start header editor. When cursor down is hit from last > header line, alternate editor is entered on body of message. > > 2. Reply: Start Alternate editor on body of message. > > 3. Exit alternate editor: Start header editor. When cursor down is hit from > last header line, alternate editor is entered on body of message. Yes, please. Thank you for thinking about it. 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 Fri Jul 23 10:18:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15426; Fri, 23 Jul 93 10:18:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08067; Fri, 23 Jul 93 10:00:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08061; Fri, 23 Jul 93 10:00:21 -0700 Received: by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA25560; Fri, 23 Jul 93 10:00:20 -0700 Date: Fri, 23 Jul 1993 09:53:41 -0700 (PDT) From: Laurence Lundblade Subject: Re: Problems with setting default editor To: David L Miller Cc: Philip Hazel , Ian Dunkin , Viswanath Gopalakrishnan , pine-info@cac.washington.edu, Corey Satten In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When we were looking at making this work we looked pretty close at the way Elm works and seriously considered it. The main reason it was rejected was because you can't easily edit a header line longer than the screen was wide. Ian's rational really makes sense and Dave's solution proposed here looks pretty good. I've talked to Corey (Cc's here and not a Pine user) about this and he's always suggested that Pine be extended to actually edit the headers with an arbitrary editor using something something like TCL for Pine to interact with the other editor. I've always thought it was an interesting idea, but it was more than I was up for trying to figure out how to make work. Corey please, correct me if I've said something wrong. LL On 23 Jul 1993, David L Miller wrote: > > What precisely do you want the behavior to be? Would this be correct? > > 1. Compose/forward: Start header editor. When cursor down is hit from last > header line, alternate editor is entered on body of message. > > 2. Reply: Start Alternate editor on body of message. > > 3. Exit alternate editor: Start header editor. When cursor down is hit from > last header line, alternate editor is entered on body of message. > > -- > |\ | |\/| 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 15tn Ave NE, Seattle WA 98105, USA > > > On Fri, 23 Jul 1993, Philip Hazel wrote: > > > > The natural thing to do is to start typing away madly as soon as you get > > > into the text area, and it's easy to forget which editor you're in. MY > > > alternative editor of choice for Pine is actually MicroEMACS (our own > > > slightly extended version). So pico is similar enough to feel familiar, > > > and I _always_ pitch into word operations, marks, &c, till I realise > > > that pico is beeping madly at me to stop because it's had those > > > particular functions removed. So it's just a Would-Be-Nice. > > > > Yes. Precisely! Thank you. You have expressed it much more clearly than I > > did. > > > > 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 Fri Jul 23 10:39:24 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17138; Fri, 23 Jul 93 10:39:24 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10822; Fri, 23 Jul 93 10:23:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from welchgate.welch.jhu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10816; Fri, 23 Jul 93 10:23:42 -0700 Received: by welchgate.welch.jhu.edu (5.65/1.34) id AA11006; Fri, 23 Jul 93 13:22:08 -0400 Date: Fri, 23 Jul 93 13:22:08 -0400 From: keithc@welchgate.welch.jhu.edu (Keith Christopher) Message-Id: <9307231722.AA11006@welchgate.welch.jhu.edu> To: pine-info@cac.washington.edu Subject: pine solaris 2.2 Does pine work under Solaris 2.2 ? If so is there a binary available. Keith From owner-pine-info@cac.washington.edu Fri Jul 23 10:55:44 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18488; Fri, 23 Jul 93 10:55:44 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10950; Fri, 23 Jul 93 10:41:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from camco1.celestial.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10944; Fri, 23 Jul 93 10:41:47 -0700 Received: by camco1.celestial.com (Smail3.1.28.1 #8) id m0oJR7q-00044TC; Fri, 23 Jul 93 10:41 PDT Message-Id: Subject: Re: Pine 3.07 on SCO -- testing help wanted To: pine-info@cac.washington.edu Date: Fri, 23 Jul 93 10:41:44 PDT From: Bill Campbell Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.3 PL11] I've tested quite a bit of pine here including using mailboxes on another internet site and things seem to be working pretty well. One problem I didn't think of is that we're not using mmdf on any of our machines so I haven't had to deal with mmdf style mailboxes. A site with a development system that could deal with that part of the problem would be nice. I'm very new to pine and haven't had time to study the tech notes in detail so bear with me with these questions: 1. Is there a place at cac.washington.edu that we could use as central place to put code and binaries for ftp during testing? We don't have anon-ftp set up on our systems here yet, and it will be at least a week before I have time to do this. 2. I don't see any way to get imapd just from the pine sources so I assume this requires imap-3.0, and this would need to take care of mmdf-style mailboxes on a stock SCO system. 3. There should be a simple way in the pine sources to take the mmdf mailboxes apart, but I haven't figured out where to look yet. Could someone point me in the right direction? I have a couple of questions also about pine usage. It appears that I cannot pipe output of a mail message to a program. Is there a way to include arbitrary headers (most important is Reply-To:) as with the $HOME/.elm/elmheaders file? Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Software UUCP: uunet!camco!bill 8545 SE 68th Street FAX: (206) 232-9186 Mercer Island, WA 98040; (206) 947-5591 From owner-pine-info@cac.washington.edu Fri Jul 23 11:07:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19531; Fri, 23 Jul 93 11:07:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10116; Fri, 23 Jul 93 10:49: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 AA10110; Fri, 23 Jul 93 10:49:38 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16368; Fri, 23 Jul 93 10:49:17 -0700 Date: Fri, 23 Jul 1993 10:48:44 -0700 (PDT) From: David L Miller Subject: Re: pine solaris 2.2 To: Keith Christopher Cc: pine-info@cac.washington.edu In-Reply-To: <9307231722.AA11006@welchgate.welch.jhu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We are currently working on a Solaris port for the 3.85 release next month. -- |\ | |\/| 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, 23 Jul 1993, Keith Christopher wrote: > Does pine work under Solaris 2.2 ? If so is there a binary available. > > > Keith > From owner-pine-info@cac.washington.edu Fri Jul 23 12:17:39 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25552; Fri, 23 Jul 93 12:17:39 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11585; Fri, 23 Jul 93 12:03:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from welchgate.welch.jhu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11579; Fri, 23 Jul 93 12:03:33 -0700 Received: by welchgate.welch.jhu.edu (5.65/1.34) id AA19225; Fri, 23 Jul 93 15:01:58 -0400 Date: Fri, 23 Jul 93 15:01:58 -0400 From: mhorn@welchgate.welch.jhu.edu (Melissa Horn) Message-Id: <9307231901.AA19225@welchgate.welch.jhu.edu> To: pine-info@cac.washington.edu Subject: . subscribe mhorn@welchgate.welch.jhu.edu From owner-pine-info@cac.washington.edu Fri Jul 23 17:33:41 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA20993; Fri, 23 Jul 93 17:33:41 -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 AA20174; Fri, 23 Jul 93 17:23:08 -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 AA20168; Fri, 23 Jul 93 17:23:07 -0700 Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24576; Fri, 23 Jul 93 17:23:06 -0700 Reply-To: Michael Seibel Message-Id: Date: Fri, 23 Jul 1993 17:21:10 -0700 (PDT) From: Michael Seibel To: Pine Announcement Distribution Subject: New PC-Pine for packet-drivers X-Owner: pine-announce-request@cac.washington.edu X-To: pine-announce@cac.washington.edu, pcpine-alpha@cac.washington.edu This note is to announce a new release of the packet-driver compatible version of PC-Pine. This new version, 3.84a, fixes a bug in the underlying TCP/IP library which caused, under certain circumstances, folder opening to fail with a "IMAP connection broken in reply" error. This fix is the only change from 3.84, and the packet-driver compatible version is the only one updated. We're still busy on version 3.85 which will include many of the enhancements and fixes that have been suggested, as well as source. As always, thanks for your interest! The Pine Team University of Washington, Seattle From owner-pine-info@cac.washington.edu Fri Jul 23 19:04:22 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26280; Fri, 23 Jul 93 19:04:22 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27083; Fri, 23 Jul 93 18:53:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27073; Fri, 23 Jul 93 18:53:47 -0700 Received: by digi.syd.deg.csiro.au id AA14821 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Sat, 24 Jul 1993 11:55:42 +1000 Date: Sat, 24 Jul 1993 11:48:00 +1000 (EST) From: Jack Churchill Subject: Re: Problems with setting default editor To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 23 Jul 1993, David L Miller wrote: > Is a single keystroke really that objectionable? No. I think if the alternate editor is made automatic, it should be an option only. The defaults should be the current set up since most pine users I know prefer to use pico than say vi. Actually I use pico for small messages like this one and vi for much larger ones that require fancy cut and paste, etc. I think the current ^_ (or sometimes ^shift_ on some vt100 emulators) is good enough and there are much more important issues that the pine developers should be working on (such as mailcap awareness). Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Fri Jul 23 20:52:40 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02326; Fri, 23 Jul 93 20:52:40 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29938; Fri, 23 Jul 93 20:43:11 -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 AA29932; Fri, 23 Jul 93 20:43:10 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12566; Fri, 23 Jul 93 20:43:00 -0700 Date: Fri, 23 Jul 1993 20:38:05 -0700 (PDT) From: David L Miller Subject: Re: Problems with setting default editor To: Jack Churchill Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We are looking into adding an option to automatically enter the alternate editor. There are some tricky design issues to solve 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 Sat, 24 Jul 1993, Jack Churchill wrote: > On Fri, 23 Jul 1993, David L Miller wrote: > > > Is a single keystroke really that objectionable? > > No. I think if the alternate editor is made automatic, it should be an > option only. The defaults should be the current set up since most pine > users I know prefer to use pico than say vi. Actually I use pico for > small messages like this one and vi for much larger ones that require > fancy cut and paste, etc. I think the current ^_ (or sometimes ^shift_ on > some vt100 emulators) is good enough and there are much more important > issues that the pine developers should be working on (such as mailcap > awareness). > > Jack N. Churchill | Jack.Churchill@dem.csiro.au > CSIRO Division of Exploration and Mining | churchill@decus.com.au > PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 > Australia | Fax: +61 2 887 8921 > > From owner-pine-info@cac.washington.edu Sat Jul 24 14:03:16 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01333; Sat, 24 Jul 93 14:03:16 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26516; Sat, 24 Jul 93 13:27:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from waldorf.cc.wwu.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26508; Sat, 24 Jul 93 13:26:57 -0700 Received: by waldorf.cc.wwu.edu (5.65/WWU-M1.0/UW-NDC Revision: 2.26 ) id AA06698; Sat, 24 Jul 1993 13:25:23 -0700 Date: Sat, 24 Jul 1993 13:25:23 -0700 From: Iain And Info Net Message-Id: <9307242025.AA06698@waldorf.cc.wwu.edu> To: pine-info@cac.washington.edu Subject: Is there a Pine for WIndows? If so , is it ftp able? thanks, -iain From owner-pine-info@cac.washington.edu Sun Jul 25 02:44:18 1993 Received: by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14196; Sun, 25 Jul 93 02:44:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from pail.rain.com by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14167; Sun, 25 Jul 93 02:44:14 -0700 Received: by pail.rain.com (/\==/\ Smail3.1.21.1 #21.2) id ; Sun, 25 Jul 93 02:44 PDT Received: from bachelor.cascorp.com by mazama.cascorp.com with SMTP (1.37.109.4/4.0 Server UUCP) id AA25736; Sat, 24 Jul 93 10:27:17 -0700 From: David Bradford Date: Sat, 24 Jul 1993 10:19:58 +0800 (PST) Subject: Re: Problems with setting default editor To: PINE Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 24 Jul 1993, Jack Churchill wrote: > No. I think if the alternate editor is made automatic, it should be an > option only. The defaults should be the current set up since most pine > users I know prefer to use pico than say vi. pico is easily the most important reason we implemented pine here. Most of our users couldn't use vi to save their lives. - Dave zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz David Bradford CAD/CAM Tech Support "The world's leading __ | Cascade Corporation, Portland, OR, USA producer of lift |__\_| Telephone...............(503) 669 6285 truck attachments" @--@|__ --------------------------------------------------------------------------- UUCP: uunet!pail!cascorp!dbradfor Internet: cascorp!dbradfor@pail.rain.com zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz From owner-pine-info@cac.washington.edu Mon Jul 26 01:38:45 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01263; Mon, 26 Jul 93 01:38:45 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22512; Mon, 26 Jul 93 01:21:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [144.32.128.13] by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22504; Mon, 26 Jul 93 01:21:55 -0700 Received: from tower.york.ac.uk by leeman.york.ac.uk with SMTP (PP) id <12146-0@leeman.york.ac.uk>; Mon, 26 Jul 1993 09:22:56 +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 AA21133; Mon, 26 Jul 93 09:24:03 +0100 Date: Mon, 26 Jul 93 09:24:03 +0000 From: Mike Brudenell To: pine-info@cac.washington.edu Subject: Re: Problems with setting default editor Message-Id: In-Reply-To: Your message of Sat, 24 Jul 1993 11:48:00 +1000 (EST) Content-Type: TEXT/plain; charset=US-ASCII > I think the current ^_ (or > sometimes ^shift_ on some vt100 emulators) is good > enough It is intriguing to note that some of our terminals (Wyse-85's) don't send anything to the host for the ^_ keystroke! I initially hacked the Pine code to use ^/ instead, only to find that some terminal emulators on our PCs wouldn't cope with this either! In the end I disabled the suspend facility and nabbed ^Z for the Alternate Editor keystroke. Sigh. Mike B-) From owner-pine-info@cac.washington.edu Mon Jul 26 06:04:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA17747; Mon, 26 Jul 93 06:04:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA29729; Mon, 26 Jul 93 05:48:35 -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 AA29723; Mon, 26 Jul 93 05:48:33 -0700 Via: uk.co.ggr; Mon, 26 Jul 1993 13:48:09 +0100 Received: from uk0x04.ggr.co.uk by uk0x08.ggr.co.uk; Mon, 26 Jul 93 13:49:07 BST Received: from uk0x04.ggr.co.uk by mailhub.ggr.co.uk (5.59/imd-070593) id AA07441; Mon, 26 Jul 93 13:40:54 BST Received: by uk0x04.ggr.co.uk (4.1/imd110593) id AA12831; Mon, 26 Jul 93 13:45:06 BST Date: Mon, 26 Jul 1993 13:37:01 +0100 (BST) From: Ian Dunkin Subject: Re: Problems with setting default editor To: Jack Churchill Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 24 Jul 1993, Jack Churchill wrote: > No. I think if the alternate editor is made automatic, it should be an > option only. Jack, Oh yes, I think everyone has agreed about that. > there are much more important > issues that the pine developers should be working on (such as mailcap > awareness). Agreed again. I added my vote to the case for automatic entry of the alternat editor, but I certainly wouldn't disagree that many things (like mailcap) are more deserving of the Pine developers' time. I. (I'm agreeing even _though_ you're in the .au domain, and England are currently 279-8) From owner-pine-info@cac.washington.edu Mon Jul 26 07:21:54 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22419; Mon, 26 Jul 93 07:21:54 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02260; Mon, 26 Jul 93 07:14:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from joline.mcdata.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02254; Mon, 26 Jul 93 07:14:13 -0700 Received: by joline.mcdata.com (4.1/SMI-4.1) id AA27011; Mon, 26 Jul 93 08:14:00 MDT Date: Mon, 26 Jul 93 08:14:00 MDT From: mark@joline.mcdata.com (Mark A. Carlson) Message-Id: <9307261414.AA27011@joline.mcdata.com> To: pine-info@cac.washington.edu Subject: Info on Pine Please send info on pine email system From owner-pine-info@cac.washington.edu Mon Jul 26 08:37:18 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27752; Mon, 26 Jul 93 08:37:18 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04343; Mon, 26 Jul 93 08:20:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04337; Mon, 26 Jul 93 08:20:13 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08049; Mon, 26 Jul 93 08:20:06 -0700 Date: Mon, 26 Jul 1993 08:17:47 -0700 (PDT) From: David L Miller Subject: Re: Problems with setting default editor To: Ian Dunkin Cc: Jack Churchill , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Support for mailcap is definately scheduled for pine 4.0. Changing the alternate editor behavior is merely being "considered." -- |\ | |\/| 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, 26 Jul 1993, Ian Dunkin wrote: > On Sat, 24 Jul 1993, Jack Churchill wrote: > > > No. I think if the alternate editor is made automatic, it should be an > > option only. > > Jack, > > Oh yes, I think everyone has agreed about that. > > > there are much more important > > issues that the pine developers should be working on (such as mailcap > > awareness). > > Agreed again. I added my vote to the case for automatic entry of the > alternat editor, but I certainly wouldn't disagree that many things (like > mailcap) are more deserving of the Pine developers' time. > > I. > > (I'm agreeing even _though_ you're in the .au domain, and England are > currently 279-8) > > > From owner-pine-info@cac.washington.edu Mon Jul 26 08:50:38 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA28860; Mon, 26 Jul 93 08:50:38 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04833; Mon, 26 Jul 93 08:32: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 AA04827; Mon, 26 Jul 93 08:32:36 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08286; Mon, 26 Jul 93 08:32:31 -0700 Date: Mon, 26 Jul 1993 08:29:52 -0700 (PDT) From: David L Miller Subject: Re: Info on Pine To: "Mark A. Carlson" Cc: pine-info@cac.washington.edu In-Reply-To: <9307261414.AA27011@joline.mcdata.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII PINE ELECTRONIC MAIL BACKGROUND Pine is a mailer designed specifically for ease-of-use with the novice computer user in mind. It is based on Internet mail protocols (e.g. RFC-822, SMTP, IMAP, and MIME) and currently runs on a variety of UNIX platforms. The guiding principles for achieving ease-of-use in Pine were: careful limitation of features, one-character mnemonic commands, always-present command menus, immediate user feedback, and high tolerance for user mistakes. It is intended that Pine can be learned by exploration rather than reading manuals. Feedback from the University of Washington community and a growing number of Internet sites has been encouraging. A stand-alone version of Pico, Pine's message composition editor, is also available. It is a very simple and easy to use text editor with text justification and a spelling checker. FEATURES - Mail index showing a message summary which includes the status, sender, size, date and subject of messages. - View and process mail with the following commands: forward, reply, save, export, print, delete, capture address and search. - Address book for saving long complex addresses and personal distribution lists under a nickname. - Multiple folders and folder management screen for filing messages. - Message composer with easy-to-use editor and spelling checker. The message composer also assists entering and formatting addresses and provides direct access to the address book. - Online help specific to each screen and context. - Supports access to remote mail repositories via the IMAP2 protocol defined in RFC-1176. - Support for multipart mail conforming to proposed MIME (RFC-1341) Internet standard. This allows attachments to mail messages such as graphices (GIF, TIFF...), sounds, and other files such as spread sheets and binary files. - Work is well underway to port Pine to MS-DOS. (Stanford's Mailstrom is recommended for Macs). AVAILABILITY Pine and Pico, including source code, are freely available via anonymous FTP from ftp.cac.washington.edu on the Internet. Other provisions for distribution have not been made. From the Internet, you may try out Pine and leave comments by telneting to "demo.cac.washington.edu" and logging in as "pinedemo". To join the Pine mailing list for announcements send a request to "pine-announce-request@cac.washington.edu". To join the list which includes discussion as well as announcements send a request to "pine-info-request@cac.washington.edu". Pine is very portable and runs on a variety of UNIX machines including DECstations, NeXT's, Sequents, and Suns. Pine was originally based on Elm, but it has evolved much since, ("Pine Is No-longer Elm"). For further information send e-mail to pine@cac.washington.edu. Pine is the work of Mike Seibel, Mark Crispin, and Laurence Lundblade at the University of Washington Office of Computing and Communications. 92.7.13 -- |\ | |\/| 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, 26 Jul 1993, Mark A. Carlson wrote: > Please send info on pine email system > From owner-pine-info@cac.washington.edu Mon Jul 26 10:06:06 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04774; Mon, 26 Jul 93 10:06:06 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00716; Mon, 26 Jul 93 09:52:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from emoryu1.cc.emory.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00712; Mon, 26 Jul 93 09:52:01 -0700 Received: by emoryu1.cc.emory.edu (5.65/Emory_cc.3.4.6) via MAILPROG id AA24753 ; Mon, 26 Jul 93 12:51:56 -0400 Return-Path: usmf@unix.cc.emory.edu Date: Mon, 26 Jul 1993 12:49:39 -0400 (EDT) From: Mahbuba Ferdousi Subject: Pine on RISK 6000 To: pine-info@cac.washington.edu, lgl@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! Do you know if Pine can be installed on an IBM RISK 6000? If so which pine should I get??? Thanks in advance, M. Ferdousi Consultant Academic Computing Emory University From owner-pine-info@cac.washington.edu Mon Jul 26 10:44:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08463; Mon, 26 Jul 93 10:44:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00992; Mon, 26 Jul 93 10:35:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ormail.intel.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00986; Mon, 26 Jul 93 10:35:43 -0700 Received: from intelhf.intel.com by ormail.intel.com with smtp (Smail3.1.28.1 #2) id m0oKWTU-000MObC; Mon, 26 Jul 93 10:36 PDT Received: from ccm by intelhf.intel.com with uucp (Smail3.1.28.1 #1) id m0oKWX7-0001beC; Mon, 26 Jul 93 10:40 PDT Received: by ccm.hf.intel.com (ccmgate) Mon, 26 Jul 93 10:40:21 PST Date: Mon, 26 Jul 93 10:40:21 PST From: David B Andersen Message-Id: <930726104021_2@ccm.hf.intel.com> To: pine-info@cac.washington.edu Subject: Info please Please send info on pine email software for windows From owner-pine-info@cac.washington.edu Mon Jul 26 12:46:19 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18473; Mon, 26 Jul 93 12:46:19 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13955; Mon, 26 Jul 93 12:37:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from farallon.farallon.com by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA13949; Mon, 26 Jul 93 12:37:53 -0700 Received: from miracle.farallon.com by farallon.com (4.1/SMI-4.1) id AA21787; Mon, 26 Jul 93 12:37:49 PDT Received: by miracle.farallon.com (4.1/SMI-4.1) id AA26252; Mon, 26 Jul 93 12:37:39 PDT Date: Mon, 26 Jul 93 12:37:39 PDT From: jnice@farallon.com (John Nice) Message-Id: <9307261937.AA26252@miracle.farallon.com> To: pine-info@cac.washington.edu Subject: Pine Information Cc: jnice@farallon.com I am a developer working on sending binary email attachments over the Internet. Could you send me the information you have on Pine email. Thx, John Nuce From owner-pine-info@cac.washington.edu Mon Jul 26 12:57:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19086; Mon, 26 Jul 93 12:57:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14292; Mon, 26 Jul 93 12:49:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14286; Mon, 26 Jul 93 12:49:19 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18505; Mon, 26 Jul 93 12:49:13 -0700 Date: Mon, 26 Jul 1993 12:47:52 -0700 (PDT) From: David L Miller Subject: Re: Pine on RISK 6000 To: Mahbuba Ferdousi Cc: pine-info@cac.washington.edu, lgl@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine 3.85 will be released in a couple weeks and will include a fully functional port for the RS/6000. -- |\ | |\/| 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, 26 Jul 1993, Mahbuba Ferdousi wrote: > Hi! > > Do you know if Pine can be installed on an IBM RISK 6000? If so which pine > should I get??? > > Thanks in advance, > M. Ferdousi > Consultant > Academic Computing > Emory University > > > > From owner-pine-info@cac.washington.edu Mon Jul 26 13:00:58 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19363; Mon, 26 Jul 93 13:00:58 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14396; Mon, 26 Jul 93 12:52: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 AA14390; Mon, 26 Jul 93 12:52:53 -0700 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18650; Mon, 26 Jul 93 12:52:42 -0700 Date: Mon, 26 Jul 1993 12:50:51 -0700 (PDT) From: David L Miller Subject: Re: Info please To: David B Andersen Cc: pine-info@cac.washington.edu In-Reply-To: <930726104021_2@ccm.hf.intel.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII PC-pine will run in a DOS window under Windows with the PC-TCP, Novell LWP, or WATTCP stacks. We are also working on a Winsock 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 Mon, 26 Jul 1993, David B Andersen wrote: > Please send info on pine email software for windows > From owner-pine-info@cac.washington.edu Mon Jul 26 13:58:32 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23937; Mon, 26 Jul 93 13:58:32 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02384; Mon, 26 Jul 93 13:51:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mozart.csc.wsu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02378; Mon, 26 Jul 93 13:51:05 -0700 Received: by mozart.csc.wsu.edu (5.65/DEC-Ultrix/4.3) id AA00646; Mon, 26 Jul 1993 13:49:16 -0700 Date: Mon, 26 Jul 1993 13:47:33 -0700 (PDT) From: Diane Dickinson Subject: News Reader To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Excuse a simple question, but how do I configure Pc-pine and Unix pine to read Usenet news? From owner-pine-info@cac.washington.edu Mon Jul 26 14:06:37 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24717; Mon, 26 Jul 93 14:06:37 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16947; Mon, 26 Jul 93 13:57:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from eis.CalState.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16941; Mon, 26 Jul 93 13:57:36 -0700 Received: by eis.calstate.edu (4.1/KNMods2.1) id AA13250; Mon, 26 Jul 93 13:56:51 PDT Date: Mon, 26 Jul 1993 13:55:34 -0700 (PDT) From: Pete Kaplan Subject: Pine & Solaris 2.2 To: pine-info@cac.washington.edu Cc: Mark Crother , Chanh Nguyen Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Has the port to Solaris 2.2 been tested? Pete Kaplan Sys Adm (310)985-9446 pete@eis.calstate.edu From owner-pine-info@cac.washington.edu Mon Jul 26 15:18:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00438; Mon, 26 Jul 93 15:18:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19638; Mon, 26 Jul 93 15:11:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19632; Mon, 26 Jul 93 15:11:19 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14528; Mon, 26 Jul 93 15:11:16 -0700 Date: Mon, 26 Jul 1993 15:08:40 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: Pine & Solaris 2.2 To: Pete Kaplan Cc: pine-info@cac.washington.edu, Mark Crother , Chanh Nguyen In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We are getting pretty close, just a few little problems to track down... -- |\ | |\/| 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, 26 Jul 1993, Pete Kaplan wrote: > > Has the port to Solaris 2.2 been tested? > > Pete Kaplan Sys Adm > (310)985-9446 pete@eis.calstate.edu > > > From owner-pine-info@cac.washington.edu Mon Jul 26 15:32:39 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA01723; Mon, 26 Jul 93 15:32:39 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19990; Mon, 26 Jul 93 15:20:15 -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 AA19984; Mon, 26 Jul 93 15:20:14 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA14817; Mon, 26 Jul 93 15:20:02 -0700 Date: Mon, 26 Jul 1993 15:19:13 -0700 (PDT) From: David L Miller Reply-To: David L Miller Subject: Re: News Reader To: Diane Dickinson Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII For PC-pine, set the news-collections variable in your PINERC file to point to your NNTP server (for WSU, news-collections=*{serval.net/nntp}[] should work). For Unix pine, wait for version 3.85 to come out next month. -- |\ | |\/| 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, 26 Jul 1993, Diane Dickinson wrote: > Excuse a simple question, but how do I configure Pc-pine and Unix pine > to read Usenet news? > > From owner-pine-info@cac.washington.edu Tue Jul 27 12:46:07 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27640; Tue, 27 Jul 93 12:46:07 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09724; Tue, 27 Jul 93 12:27:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from wsuaix.csc.wsu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09718; Tue, 27 Jul 93 12:27:57 -0700 Received: by wsuaix.csc.wsu.edu (5.61-AIX-1.2/1.0) id AA195246 (for pine-info@cac.washington.edu, from coxg/coxg@wsuaix.csc.wsu.edu); Tue, 27 Jul 93 12:27:51 -0700 Date: Tue, 27 Jul 1993 12:07:35 -0800 (PDT) From: "greg cox;WR3058" Subject: Internet FAX via MIME To: The Pine List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I read something somewhere about a new way to send FAXes across the Internet, using MIME. WIll this be possible with PINE as the mail agent? Does anyone know what other software / hardware is required to create such a system? Any information or clarifications would be appreciated. Thanks ***************************************** * Greg Cox * Washington State Univ. * coxg@wsuaix.csc.wsu.edu * From owner-pine-info@cac.washington.edu Tue Jul 27 14:09:57 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04794; Tue, 27 Jul 93 14:09:57 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10165; Tue, 27 Jul 93 13:29:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from camco1.celestial.com by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10159; Tue, 27 Jul 93 13:29:46 -0700 Received: by camco1.celestial.com (Smail3.1.28.1 #8) id m0oKvd7-00041hC; Tue, 27 Jul 93 13:28 PDT Message-Id: Subject: Re: Internet FAX via MIME To: coxg@wsuaix.csc.wsu.edu (greg cox;WR3058) Date: Tue, 27 Jul 93 13:28:11 PDT From: Bill Campbell Cc: pine-info@cac.washington.edu In-Reply-To: ; from "greg cox;WR3058" at Jul 27, 93 12:07 pm Reply-To: bill@Celestial.COM Organization: Celestial Software, Mercer Island, WA 98040 X-Mailer: ELM [version 2.3 PL11] > > I read something somewhere about a new way to send FAXes across the > Internet, using MIME. > This would be pretty easy since faxes are typically tiff/f format. The MIME enclosure then could be processed by a tiff->printer routine or image viewer. > WIll this be possible with PINE as the mail agent? Does anyone know what > other software / hardware is required to create such a system? > We send faxes out using our MTA to divert faxes to the fax delivery software which renders ascii->tiff before faxing, by adding an Action: header it will take the body of the e-mail as troff input typesetting it before sending the fax. The troff solution works quite nicely either from Elm where we can specify the Action or other user-defined headers, but I don't know how this would be done with pine (I haven't figured out how to get a Reply-To: header yet :-). Bill -- INTERNET: bill@Celestial.COM Bill Campbell; Celestial Software UUCP: uunet!camco!bill 8545 SE 68th Street FAX: (206) 232-9186 Mercer Island, WA 98040; (206) 947-5591 From owner-pine-info@cac.washington.edu Tue Jul 27 17:52:36 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22278; Tue, 27 Jul 93 17:52:36 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11875; Tue, 27 Jul 93 17:44:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from henson.cc.wwu.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11869; Tue, 27 Jul 93 17:44:42 -0700 Received: by henson.cc.wwu.edu (5.65/WWU-H1.2/UW-NDC Revision: 2.26 ) id AA07663; Tue, 27 Jul 1993 17:43:13 -0700 Date: Tue, 27 Jul 1993 17:43:13 -0700 From: J. Scott Williams Message-Id: <9307280043.AA07663@henson.cc.wwu.edu> To: pine-info@cac.washington.edu Subject: PC-PINE Questions: IMAPD3.0/"full login"/Winsock date? Dear pine-info People: We at WWU like and use Ultrix Pine and are starting to test out PC-PINE and like what we see so far. Some PC-PINE questions: 1) Does IMAPD 3.x need to be running for PC-PINE 3.84 remote folder collections to operate? 2) Will PC-PINE ever have "full login" capability? i.e. login ID *and* password. (Yes, I understand the security concerns.) 3) Is it possible to get an approximate target date for the implemention of the Winsock version of PC-PINE? -jscott- -------- |J. Scott Williams Ph: (206) 650-2868 FAX: (206) 650-6548 | |Academic Tech. User Services Internet: scott@henson.cc.wwu.edu | |Western Washington Univ. "Internet--Talking across the electronic| |Bellingham, WA 98225-9094 back fence of the world."-JSW| From owner-pine-info@cac.washington.edu Tue Jul 27 21:03:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03653; Tue, 27 Jul 93 21:03:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15521; Tue, 27 Jul 93 20:51:32 -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 AA15513; Tue, 27 Jul 93 20:51:30 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07965; Tue, 27 Jul 93 20:51:20 -0700 Date: Tue, 27 Jul 1993 20:43:49 -0700 (PDT) From: David L Miller Subject: Re: PC-PINE Questions: IMAPD3.0/"full login"/Winsock date? To: "J. Scott Williams" Cc: pine-info@cac.washington.edu In-Reply-To: <9307280043.AA07663@henson.cc.wwu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 27 Jul 1993, J. Scott Williams wrote: > Dear pine-info People: > > We at WWU like and use Ultrix Pine and are starting to test out PC-PINE > and like what we see so far. Some PC-PINE questions: > > 1) Does IMAPD 3.x need to be running for PC-PINE 3.84 remote > folder collections to operate? > Yes. > 2) Will PC-PINE ever have "full login" capability? i.e. > login ID *and* password. (Yes, I understand the security > concerns.) > You already have to login to the IMAP server to access your folders. The assumption with PC pine is that all folders will be kept on the server. Actually, one of the biggest "enhancement" requests we have recieved is for the ability to keep passwords on the PC! > 3) Is it possible to get an approximate target date for the > implemention of the Winsock version of PC-PINE? > Nope. We have a Winsock 1.1 stack available, but we have not started the port yet. > -jscott- > -------- > |J. Scott Williams Ph: (206) 650-2868 FAX: (206) 650-6548 | > |Academic Tech. User Services Internet: scott@henson.cc.wwu.edu | > |Western Washington Univ. "Internet--Talking across the electronic| > |Bellingham, WA 98225-9094 back fence of the world."-JSW| > -- |\ | |\/| 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 Thu Jul 29 06:36:30 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19663; Thu, 29 Jul 93 06:36:30 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23844; Thu, 29 Jul 93 06:19:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from munnari.OZ.AU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23838; Thu, 29 Jul 93 06:19:24 -0700 Received: from msl.msl.oz (via sol) by munnari.oz.au with SunIII (5.83--+1.3.1+0.50) id AA19933; Thu, 29 Jul 1993 23:18:32 +1000 (from isb_mtf@msl.msl.oz.au) Received: by msl (4.1) id AA03410; Thu, 29 Jul 93 23:08:29 EST Date: Thu, 29 Jul 93 23:08:29 EST From: isb_mtf@msl.oz.au (Michael Fox) Message-Id: <9307291308.AA03410@msl> To: pine-info@cac.washington.edu Subject: 2 pine/imap questions - shared folders; remote authentication Background: We are running pine3.07 (hacked, see below), imapd 3.0, and testing ECSmail 1.0, in the process of converting from a home grown mail system on a Prime. We have a Sun 670 (thumper) as a mailbox server running imapd with the /etc/rimapd link for remote pre-authentication. We also have a Sun Sparc 2 as an nntp server, running INN, and use trn as the client news reader. A number of other Suns and PCs access these services, and all the Suns run Sunos 4.1.3. The Pine hack is to emulate "noticeboards" as we new them on the Prime system, which are really shared folders. To make them visible to users in the normal folder menu, 2 extra entries are displayed, and which in reality point to {thumper}/var/spool/mail/postnotices and {thumper}/var/spool/mail/ postparcels. This works OK for pine, but not for ECSmail. Question 1: We have noticed extended BBOARD functionality in imapd, will this be used in Pine 3.85, and how? Is it just for NNTP type services, or can it be used like we are trying to do, pointing to shared folders somewhere? Question 2: Remote authentication works for some users but not others, who seem to us to have identical configurations - same home system, same unix groups and netgroups, same .pinerc, and all can use rlogin and rsh OK. We cannot pick the problem - anyone have any pointers or procedures we could follow to try and solve this ( the same problem existed with imap 2 as imap 3, and with the original unhacked pine) Thanks - Michael Fox, Department of Conservation and Natural Resources Victoria, Australia From owner-pine-info@cac.washington.edu Thu Jul 29 09:50:38 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04244; Thu, 29 Jul 93 09:50:38 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24996; Thu, 29 Jul 93 09:35:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ULTRIX.UOR.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA24990; Thu, 29 Jul 93 09:35:32 -0700 Received: by ultrix.uor.edu (5.57/Ultrix3.0-C) id AA26931; Thu, 29 Jul 93 09:38:13 -0700 Date: Thu, 29 Jul 1993 09:15:38 -0700 (PDT) From: Sharon Deng Subject: Mail Disappeared To: Pine Info Group Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, Pine: I usually have big mail list for several groups. When I sent a mail to one account which I used to make sure the mail got delivered, then blind copy to several groups that have a big mail listing. For some reason, the entire mail disappeared. I couldn't even find any error in mailq or syslog. Then I did it again with smaller groups. It worked. Anybody knows why? Does Pine have any restriction for the number of blind copy or the number of mails? Sharon Deng Assistant Director Internet: deng@ultrix.uor.edu Academic Computer Center deng@jccvms.uor.edu University of Redlands Phone: (909)793-2121 x.4963 From owner-pine-info@cac.washington.edu Thu Jul 29 11:43:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11576; Thu, 29 Jul 93 11:43:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00301; Thu, 29 Jul 93 11:30:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00295; Thu, 29 Jul 93 11:30:22 -0700 Date: Thu, 29 Jul 1993 11:20:49 -0700 (PDT) From: Michael Seibel Subject: Re: Mail Disappeared To: Sharon Deng Cc: Pine Info Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sounds like you're getting bit by the non-wrapping-bcc bug in pine 3.05. Your unsuspecting sendmail is probably not even getting the chance to write syslog. The good news is that this bug, among other annoyances (though not all!), is fixed in the maintenance release, version 3.07, so you might want to think about upgrading. An ultrix binary of 3.07 is available via anonymous ftp from ftp.cac.washington.edu. Hope this helps! Michael Seibel Networks and Distributed Computing mikes@cac.washington.edu University of Washington, Seattle (206) 543 - 0359 On Thu, 29 Jul 1993, Sharon Deng wrote: > Hi, Pine: > > I usually have big mail list for several groups. When I sent a mail to > one account which I used to make sure the mail got delivered, then blind > copy to several groups that have a big mail listing. For some reason, > the entire mail disappeared. I couldn't even find any error in mailq or > syslog. Then I did it again with smaller groups. It worked. Anybody > knows why? Does Pine have any restriction for the number of blind copy or > the number of mails? > > > > Sharon Deng > Assistant Director Internet: deng@ultrix.uor.edu > Academic Computer Center deng@jccvms.uor.edu > University of Redlands Phone: (909)793-2121 x.4963 From owner-pine-info@cac.washington.edu Thu Jul 29 11:53:00 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12093; Thu, 29 Jul 93 11:53:00 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA25776; Thu, 29 Jul 93 11:34:01 -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 AA25770; Thu, 29 Jul 93 11:33:59 -0700 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA20753; Thu, 29 Jul 93 11:33:51 -0700 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA24316; Thu, 29 Jul 93 11:33:44 -0700 Date: Thu, 29 Jul 1993 11:30:41 -0700 (PDT) From: Mark Crispin Subject: re: 2 pine/imap questions - shared folders; remote authentication To: Michael Fox Cc: pine-info@cac.washington.edu In-Reply-To: <9307291308.AA03410@msl> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 29 Jul 93 23:08:29 EST, Michael Fox wrote: > Question 1: We have noticed extended BBOARD functionality in imapd, > will this be used in Pine 3.85, and how? Yes. > Is it just for NNTP type > services, or can it be used like we are trying to do, pointing to > shared folders somewhere? Shared folder such as you describe are also under development. We're doing it a bit differently, but I think that the new stuff in 3.85 will lay down a lot of the groundwork to make noticeboards a lot easier to do. > Question 2: Remote authentication works for some users but not others, > who seem to us to have identical configurations - same home system, > same unix groups and netgroups, same .pinerc, and all can use rlogin > and rsh OK. We cannot pick the problem - anyone have any pointers > or procedures we could follow to try and solve this ( the same > problem existed with imap 2 as imap 3, and with the original > unhacked pine) Check their .cshrc, etc. file to make sure that no extraneous output is coming out when an rsh is done. Such output would confuse the rimap opening code in c-client/imap2.c and make it conclude that it can't use rimap. Remember, rimap is simply an exec() of ``rsh serverhost /etc/rimapd''; the IMAP client runs with no privileges. From owner-pine-info@cac.washington.edu Thu Jul 29 13:41:29 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA16366; Thu, 29 Jul 93 13:41:29 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA26491; Thu, 29 Jul 93 13:28:08 -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 AA26485; Thu, 29 Jul 93 13:28:07 -0700 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA27336; Thu, 29 Jul 93 16:28:03 -0400 Received: from merint.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 162636.25219; Thu, 29 Jul 1993 16:26:36 EDT Received: by merint (AIX 3.2/UCB 5.64/4.03) id AA08528; Thu, 29 Jul 1993 12:35:26 -0600 From: merint!alexc@uunet.UU.NET (Alex Chan - Admin) Message-Id: <9307291835.AA08528@merint> To: uunet!cac.washington.edu!pine-info@uunet.UU.NET Cc: alexc%merint@uunet.UU.NET Subject: Quick question .. In-Reply-To: (Your message of Thu, 29 Jul 93 09:15:38 MST.) Date: Thu, 29 Jul 93 12:35:25 -0700 We have just inherited 20 wyse50 technology terminals, and the cursor keys do not work on those terminals. How could one adjust pine to allow the usage of the cursor keys ? /usr/bin/vi works fine with those wyse50 terminals. I guess that the termcap and terminfo entries on our IBM RS6000 is correct. Thanks for your help. From owner-pine-info@cac.washington.edu Fri Jul 30 06:32:33 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09243; Fri, 30 Jul 93 06:32:33 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00778; Fri, 30 Jul 93 06:23:18 -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 AA00774; Fri, 30 Jul 93 06:23:07 -0700 Return-Path: Date: Fri, 30 Jul 1993 16:12:13 +0300 (IDT) From: Eran Lachs Subject: forwarding with full headers To: Pine Info List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Old-growth let's you view the message's full headers. Any way to forward a message with it's full headers ? Eran Lachs (eran@bgumail.bgu.ac.il) System Group Ben Gurion University Computation Center Beer Sheva, Israel From owner-pine-info@cac.washington.edu Fri Jul 30 06:55:55 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA09703; Fri, 30 Jul 93 06:55:55 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00856; Fri, 30 Jul 93 06:46:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from rainier.lib.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA00850; Fri, 30 Jul 93 06:46:51 -0700 Received: by rainier.lib.washington.edu (5.65/UW-NDC Revision: 2.24 ) id AA07492; Fri, 30 Jul 93 06:46:37 -0700 Date: Fri, 30 Jul 1993 06:45:31 -0700 (PDT) From: Adam Garrett Reply-To: Adam Garrett Subject: Re: forwarding with full headers To: Eran Lachs Cc: Pine Info List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Eran, I usually use the 'save to folder' command (not export) to save message as a file in my home directory, then I just forward message as an attachment. This way the full headers will be included. Adam R. Garrett University of Washington Libraries INTERNET: garrett@lib.washington.edu 352 Suzzallo Library, FM-25 PHONE: (206) 543-8843 Seattle, WA 98195 FAX: (206) 685-8049 On Fri, 30 Jul 1993, Eran Lachs wrote: > > Old-growth let's you view the message's full headers. Any way to forward > a message with it's full headers ? > > Eran Lachs (eran@bgumail.bgu.ac.il) > System Group > Ben Gurion University Computation Center > Beer Sheva, Israel From owner-pine-info@cac.washington.edu Fri Jul 30 07:20:44 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10399; Fri, 30 Jul 93 07:20:44 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11820; Fri, 30 Jul 93 07:11:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from QUCDN.QueensU.CA by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11814; Fri, 30 Jul 93 07:11:46 -0700 Message-Id: <9307301411.AA11814@mx1.cac.washington.edu> Received: from QUCDN.QUEENSU.CA by QUCDN.QueensU.CA (IBM VM SMTP V2R2) with BSMTP id 0487; Fri, 30 Jul 93 10:11:09 EDT Received: from QUCDN.QUEENSU.CA (NJE origin HOLNESSI@QUCDN) by QUCDN.QUEENSU.CA (LMail V1.1d/1.7f) with RFC822 id 2568; Fri, 30 Jul 1993 10:11:09 -0400 Date: Fri, 30 Jul 1993 10:06 EDT From: Iain D. Holness To: pine-info@cac.washington.edu Subject: The appearance of the interface for Pine under DOS and Unix I am writing our university's basic primer for using Pine, and will be incorporating some screen dumped graphics for the step-by-step approach I am taking in explaining the features. My question therefore is a simple but important one: Will Pine 3.85 for Unix have the same menus and look as PC-Pine 3.85? Iain /=======================================================\ Iain D. Holness Office Systems and Information Technology Group Queen's Univerity Computing and Communications Services Kingston, Ontario Dupuis Hall G-254 (613) 545-6614 From owner-pine-info@cac.washington.edu Fri Jul 30 08:39:14 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12542; Fri, 30 Jul 93 08:39:14 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA12531; Fri, 30 Jul 93 08:13:37 -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 AA12525; Fri, 30 Jul 93 08:13:36 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA11451; Fri, 30 Jul 93 08:13:31 -0700 Date: Fri, 30 Jul 1993 08:13:17 -0700 (PDT) From: David L Miller Subject: Re: The appearance of the interface for Pine under DOS and Unix To: "Iain D. Holness" Cc: pine-info@cac.washington.edu In-Reply-To: <9307301411.AA11814@mx1.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes. -- |\ | |\/| 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, 30 Jul 1993, Iain D. Holness wrote: > I am writing our university's basic primer for using Pine, and will > be incorporating some screen dumped graphics for the step-by-step > approach I am taking in explaining the features. > > My question therefore is a simple but important one: > > Will Pine 3.85 for Unix have the same menus and look as PC-Pine 3.85? > > Iain > /=======================================================\ > Iain D. Holness > Office Systems and Information Technology Group > Queen's Univerity Computing and Communications Services > Kingston, Ontario Dupuis Hall G-254 (613) 545-6614 > From owner-pine-info@cac.washington.edu Fri Jul 30 10:28:59 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18205; Fri, 30 Jul 93 10:28:59 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15118; Fri, 30 Jul 93 10:13:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15112; Fri, 30 Jul 93 10:13:44 -0700 Received: by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA29263; Fri, 30 Jul 93 10:12:45 -0700 Date: Fri, 30 Jul 1993 10:06:03 -0700 (PDT) From: Laurence Lundblade Subject: Re: forwarding with full headers To: Eran Lachs Cc: Pine Info List In-Reply-To: Message-Id: References: <0909099009@09090909> <878787878@87878787> <3343434@2323232> <12121212@1212121> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII There's a really neat way to do this! If you put Pine in old-growth mode, that is set feature-level=old-growth in your .pinerc, then when you forward mail you will be asked if you want to forward in MIME format. If you say yes then the message will be forwarded as a MIME attachment with full headers. What's really nice is that when the message is received it is displayed without the full headers showing, but you can give the "h" command (also activated in old-growth mode) and see the full header of the included message. In the future we expect that you'll be able to reply to, forward and save in a folder the *forward* message itself. LL On 30 Jul 1993, Eran Lachs wrote: > > Old-growth let's you view the message's full headers. Any way to forward > a message with it's full headers ? > > Eran Lachs (eran@bgumail.bgu.ac.il) > System Group > Ben Gurion University Computation Center > Beer Sheva, Israel > > > From owner-pine-info@cac.washington.edu Fri Jul 30 10:45:41 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA19253; Fri, 30 Jul 93 10:45:41 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15556; Fri, 30 Jul 93 10:34:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from usc.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA15550; Fri, 30 Jul 93 10:34:46 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA27025; Fri, 30 Jul 93 10:34:45 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA14576; Fri, 30 Jul 93 10:34:43 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA11985; Fri, 30 Jul 93 10:34:42 PDT Date: Fri, 30 Jul 93 10:34:42 PDT From: ekurgpol@Law.USC.EDU (Elmar Kurgpold) Message-Id: <9307301734.AA11985@develop.Law.USC.EDU> To: pine-info@cac.washington.edu Subject: Del key Sorry to waste bandwidth with such a lame question, although my teachers always used to say there was no such thing as a lame question, just lame answers. (Well, it was something like that <|:-) So here's your chance! This question comes from a user: Boy do I like this so much better! ... Is there a way I can set my keyboard to make the delete key work like the delete key. Right now it works like the backspace! I'd like to do that too! She is using PC-NFS 4.0a and telnetting into a Sun4. Can someone tell me how to map the ^D function to the delete key? ------------------------- | Elmar Kurgpold | | Network Administrator | | USC Law Center | | ekurgpol@Law.USC.EDU | | (213)740-5709 | | (213)740-5502 FAX | ------------------------- From owner-pine-info@cac.washington.edu Fri Jul 30 11:37:56 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA21865; Fri, 30 Jul 93 11:37:56 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02495; Fri, 30 Jul 93 11:29:22 -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 AA02489; Fri, 30 Jul 93 11:29:21 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA08357 sendmail 5.67/UCSD-2.2-sun via SMTP Fri, 30 Jul 93 11:29:19 -0700 for pine-info@cac.washington.edu Received: from localhost (localhost [127.0.0.1]) by weber.ucsd.edu (8.5/UCSDGENERIC.4c) with SMTP id LAA29334; Fri, 30 Jul 1993 11:29:17 -0700 Message-Id: <199307301829.LAA29334@weber.ucsd.edu> To: pine-info@cac.washington.edu Subject: Re: Del key In-Reply-To: Your message of "Fri, 30 Jul 1993 10:34:42 -0700." <9307301734.AA11985@develop.Law.USC.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 30 Jul 1993 11:29:16 -0700 From: "Michael J. Corrigan" Is there a way I can set my keyboard to make the delete key work like the delete key. Right now it works like the backspace! One way might be: "stty erase ^Vdelete" i.e. type control-V and then the delete key. If that works then put that in her ".login" (for csh) or in her .profile (for sh or ksh) I'd like to do that too! She is using PC-NFS 4.0a and telnetting into a S un4. Can someone tell me how to map the ^D function to the delete key? Do you know that control-D already has a purpose in Unix ? If you don't mind losing that usage that then try "stty erase ^V^D" i.e. type control-V and then control-D. -Mike Corrigan From owner-pine-info@cac.washington.edu Fri Jul 30 11:48:37 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22365; Fri, 30 Jul 93 11:48:37 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02553; Fri, 30 Jul 93 11:38:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ULTRIX.UOR.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA02547; Fri, 30 Jul 93 11:38:57 -0700 Received: by ultrix.uor.edu (5.57/Ultrix3.0-C) id AA03998; Fri, 30 Jul 93 11:41:54 -0700 Date: Fri, 30 Jul 1993 11:31:01 -0700 (PDT) From: Sharon Deng Subject: Strange Charater in Pico To: Pine Info Group Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, Dear Pine Group: The following is part of our interactive menu for general users to use Pico as editor. ls -1F echo "Enter the file name you want ot edit : " echo " (hit return to create a new file) " set filename = $< pico "${filename}" If the user type a file name to edit a existing file, it works normal. But if the user hit return to create a new file, the Pico brings some strange characters to the screen. The strange characters are different every time to the different users. Could anybody tell me why it happened and how to solve the problem? Thank you very much. Sharon Deng Assistant Director Internet: deng@ultrix.uor.edu Academic Computer Center deng@jccvms.uor.edu University of Redlands Phone: (909)793-2121 x.4963 From owner-pine-info@cac.washington.edu Fri Jul 30 13:20:50 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27079; Fri, 30 Jul 93 13:20:50 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18324; Fri, 30 Jul 93 13:10:06 -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 AA18318; Fri, 30 Jul 93 13:10:03 -0700 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA02344; Fri, 30 Jul 93 13:09:56 PDT Received: from develop.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA15416; Fri, 30 Jul 93 13:09:55 PDT Received: from hal.usc.edu by develop.Law.USC.EDU (4.1/SMI-4.1) id AA12473; Fri, 30 Jul 93 13:09:54 PDT Date: Fri, 30 Jul 93 13:09:54 PDT From: ekurgpol@Law.USC.EDU (Elmar Kurgpold) Message-Id: <9307302009.AA12473@develop.Law.USC.EDU> To: pine-info@cac.washington.edu, corrigan@weber.ucsd.edu Subject: Re: Del key Original question: > Is there a way I can set my keyboard to make the > delete key work like the delete key. Right now it > works like the backspace! Response: > > One way might be: > "stty erase ^Vdelete" i.e. type control-V and then the delete key. > If that works then put that in her ".login" (for csh) or in her > .profile (for sh or ksh) > > I'd like to do that too! She is using PC-NFS 4.0a and telnetting into a S > un4. > Can someone tell me how to map the ^D function to the delete key? > > Do you know that control-D already has a purpose in Unix ? If you don't > mind losing that usage that then try > "stty erase ^V^D" i.e. type control-V and then control-D. > > -Mike Corrigan > Thanks for the suggestion Mike, but I was already aware of those settings. I have the habit of not being explicit in my first post of a question! The control-D function I was speaking of is specifically how it works in the default compose mode in Pine. The stty settings don't seem to affect this. Anyway, the control-D erases characters to the right of the cursor, as opposed to both the backspace and delete keys, which erase to the left. So what we would like to do is use the delete key in the compose mode to erase characters to the the right instead of the left. Hows that? Elmar In the technical notes there is some information about remapping keys within Pine From owner-pine-info@cac.washington.edu Fri Jul 30 13:37:57 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA27972; Fri, 30 Jul 93 13:37:57 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA18633; Fri, 30 Jul 93 13:28:51 -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 AA18627; Fri, 30 Jul 93 13:28:50 -0700 Received: by shiva2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA23771; Fri, 30 Jul 93 13:28:46 -0700 Date: Fri, 30 Jul 1993 13:24:01 -0700 (PDT) From: David L Miller Subject: Re: Strange Charater in Pico To: Sharon Deng Cc: Pine Info Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I am unable to duplicate this with any version of pico... -- |\ | |\/| 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, 30 Jul 1993, Sharon Deng wrote: > > Hi, Dear Pine Group: > > The following is part of our interactive menu for general users to use > Pico as editor. > > ls -1F > echo "Enter the file name you want ot edit : " > echo " (hit return to create a new file) " > set filename = $< > pico "${filename}" > > If the user type a file name to edit a existing file, it works normal. But > if the user hit return to create a new file, the Pico brings some strange > characters to the screen. The strange characters are different every time > to the different users. Could anybody tell me why it happened and how to > solve the problem? Thank you very much. > > > > Sharon Deng > Assistant Director Internet: deng@ultrix.uor.edu > Academic Computer Center deng@jccvms.uor.edu > University of Redlands Phone: (909)793-2121 x.4963 > > > From owner-pine-info@cac.washington.edu Fri Jul 30 15:37:37 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04749; Fri, 30 Jul 93 15:37:37 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03805; Fri, 30 Jul 93 15:22:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from [132.248.10.4] by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03799; Fri, 30 Jul 93 15:22:28 -0700 Received: by redvax1.dgsca.unam.mx (5.57/Ultrix3.0-C) id AA05915; Fri, 30 Jul 93 16:18:08 -0500 Date: Fri, 30 Jul 1993 16:13:48 -0500 (CDT) From: "Isaias Callejas Mancilla." Reply-To: "Isaias Callejas Mancilla." Subject: Re: Strange Charater in Pico To: Sharon Deng Cc: Pine Info Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 30 Jul 1993, Sharon Deng wrote: > > Hi, Dear Pine Group: > > The following is part of our interactive menu for general users to use > Pico as editor. > > ls -1F > echo "Enter the file name you want ot edit : " > echo " (hit return to create a new file) " > set filename = $< > pico "${filename}" > > If the user type a file name to edit a existing file, it works normal. But > if the user hit return to create a new file, the Pico brings some strange > characters to the screen. The strange characters are different every time > to the different users. Could anybody tell me why it happened and how to > solve the problem? Thank you very much. > Hi Sharon, I did change the program to cshell and work very good.. look.. # <<<===== Line 1, Column 1. ls -1F echo "Enter the file name you want ot edit : " echo " (hit return to create a new file) " set filename = $< pico $filename <<<== variable changed I hope to solution you'r problem... === Ernesto Isaias Callejas Mancilla. Miembro del Grupo de Administradores del equipo Microvax 3400. Departamento de Soporte a Sistemas IBM-DEC. Coordinacion de Servicios de Computo. Direccion General de Servicios de Computo Academico. Universidad Nacional Autonoma de Mexico. Telefono : 6 22 85 22 Internet : isma@redvax1.dgsca.unam.mx Bitnet : isma@redvax1.bitnet From owner-pine-info@cac.washington.edu Fri Jul 30 16:07:09 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07203; Fri, 30 Jul 93 16:07:09 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03996; Fri, 30 Jul 93 15:56:15 -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 AA03990; Fri, 30 Jul 93 15:56:13 -0700 Received: from weber.ucsd.edu by ucsd.edu; id AA04886 sendmail 5.67/UCSD-2.2-sun via SMTP Fri, 30 Jul 93 15:56:12 -0700 for pine-info@cac.washington.edu Received: from localhost (localhost [127.0.0.1]) by weber.ucsd.edu (8.5/UCSDGENERIC.4c) with SMTP id PAA12945; Fri, 30 Jul 1993 15:56:11 -0700 Message-Id: <199307302256.PAA12945@weber.ucsd.edu> To: pine-info@cac.washington.edu Subject: Re: Del key In-Reply-To: Your message of "Fri, 30 Jul 1993 13:09:54 -0700." <9307302009.AA12473@develop.Law.USC.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 30 Jul 1993 15:56:09 -0700 From: "Michael J. Corrigan" Oh. Hmm. What I read in the technical notes is that pine/pico does not provide the kind of key binding reconfigurability required to do what you are asking. The only way it can be done is within "the terminal" i.e. by causing the key you want to use to actually emit the character that pine/pico expects. You have to bind the delete key so it emits a control-D. Only in some terminal situations is this possible. Two common situations where I think it is possible are when using an X-terminal (keymodmap? or something) and with MS-Kermit. Possibly NCSA telnet can rebind your keyboard also. If you are using PC-NFS as a telnet client then it would be up to PC-NFS to give this ability - about which I know nothing. Telnet itself does not normally give this ability - although it could conceivably. Possibly somewhere in DOS. -Mike Thanks for the suggestion Mike, but I was already aware of those settings. I have the habit of not being explicit in my first post of a question! The control-D function I was speaking of is specifically how it works in the default compose mode in Pine. The stty settings don't seem to affect this . Anyway, the control-D erases characters to the right of the cursor, as opp osed to both the backspace and delete keys, which erase to the left. So what w e would like to do is use the delete key in the compose mode to erase charac ters to the the right instead of the left. Hows that? Elmar In the technical notes there is some information about remapping keys with in Pine From owner-pine-info@cac.washington.edu Fri Jul 30 16:36:35 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA08702; Fri, 30 Jul 93 16:36:35 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04179; Fri, 30 Jul 93 16:26:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ULTRIX.UOR.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA04173; Fri, 30 Jul 93 16:26:52 -0700 Received: by ultrix.uor.edu (5.57/Ultrix3.0-C) id AA06110; Fri, 30 Jul 93 16:29:32 -0700 Date: Fri, 30 Jul 1993 16:15:03 -0700 (PDT) From: Sharon Deng Subject: Re: Strange Charater in Pico To: "Isaias Callejas Mancilla." Cc: Pine Info Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 30 Jul 1993, Isaias Callejas Mancilla. wrote: > On Fri, 30 Jul 1993, Sharon Deng wrote: > > > > > Hi, Dear Pine Group: > > > > The following is part of our interactive menu (in C Shell)for general > > users to use Pico as editor. > > > > # > > ls -1F > > echo "Enter the file name you want ot edit : " > > echo " (hit return to create a new file) " > > set filename = $< > > pico "${filename}" > > > > If the user type a file name to edit a existing file, it works normal. But > > if the user hit return to create a new file, the Pico brings some strange > > characters to the screen. The strange characters are different every time > > to the different users. Could anybody tell me why it happened and how to > > solve the problem? Thank you very much. > > > Hi Sharon, > I did change the program to cshell and work very good.. > look.. > > # <<<===== Line 1, Column 1. > ls -1F > echo "Enter the file name you want ot edit : " > echo " (hit return to create a new file) " > set filename = $< > pico $filename <<<== variable changed > > I hope to solution you'r problem... > > === > > Ernesto Isaias Callejas Mancilla. > > Miembro del Grupo de Administradores del equipo Microvax 3400. > Departamento de Soporte a Sistemas IBM-DEC. > Coordinacion de Servicios de Computo. > Direccion General de Servicios de Computo Academico. > Universidad Nacional Autonoma de Mexico. > Telefono : 6 22 85 22 > > Internet : isma@redvax1.dgsca.unam.mx > Bitnet : isma@redvax1.bitnet > > Hi, Ernesto Isaias Callejas Mancilla: Thank you for your solution. It works only when the file name has no space between. Our users like to have long name with spaces between. I change my code to the following ( it is a C Shell code). Hope it will help somebody has the same problem. # ls -1F echo "" echo "Enter the file name you want to edit : " echo " (hit return to create a new file) " set filename = $< if "${filename}" == "" then pico else pico "${filename}" endif Thank you very much. Sharon Deng Assistant Director Internet: deng@ultrix.uor.edu Academic Computer Center deng@jccvms.uor.edu University of Redlands Phone: (909)793-2121 x.4963 From owner-pine-info@cac.washington.edu Fri Jul 30 17:21:35 1993 Received: from mx1.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA10805; Fri, 30 Jul 93 17:21:35 -0700 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22279; Fri, 30 Jul 93 17:10:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from norman.nwnet.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA22271; Fri, 30 Jul 93 17:10:50 -0700 Received: by norman.nwnet.net (5.65/UW-NDC Revision: 2.27 ) id AA18938; Fri, 30 Jul 93 17:10:47 -0700 Date: Fri, 30 Jul 1993 17:09:22 -0700 (PDT) From: Laurence Lundblade Subject: Re: Del key To: "Michael J. Corrigan" Cc: pine-info@cac.washington.edu In-Reply-To: <199307302256.PAA12945@weber.ucsd.edu> Message-Id: References: <0909099009@09090909> <878787878@87878787> <3343434@2323232> <12121212@1212121> <199307302256.PAA12945@weber.ucsd.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Here's something send to me as a possible solution for PC's some time ago: LL ---------- Forwarded Message --------- Date: 11 Jun 1993 16:00:16 0400 From: Barbara Vaughan To: Laurence Lundblade Subject: Re: Keyboard and Richer Header Wanted (Return-Receipt-To:) There is a solution on the PC side that may work. A tsr program called newkey, I think, will remap any DOS key to any other key sequence. It's shareware and can be found on the Simtel archive. If you want these keys to function in Pico and have no other Unix applications where you want them to function, you can run a .bat file that remaps the keys to their Pico equivalent, establishes the Unix connection, and when the connection ends, resets the keys to their DOS settings. I got this program and had it working fine with telnet connections, but the asking price of (I think) $25 per PC was too steep for our budget, so we dropped the idea. Basically, you made a little file containing English-like commands telling newkey that you wanted "home" remapped to "cntrla", which meant that when you were in pico, home went to the beginning of the line. Unlike other remapping programs, it's independent of your comm program. As far as your comm program knows, you really just hit cntrl-a, not home. With regard to cntrl-arrow keys, these functions don't exist in pine, so there's nothing to remap them to. From owner-pine-info@cac.washington.edu Sat Jul 31 06:44:46 1993 Received: from mx2.cac.washington.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA03614; Sat, 31 Jul 93 06:44:46 -0700 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.28 ) id AA07073; Sat, 31 Jul 93 06:28:07 -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 AA07067; Sat, 31 Jul 93 06:28:05 -0700 Received: from spool.uu.net (via LOCALHOST) by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA11773; Sat, 31 Jul 93 09:28:03 -0400 Received: from merint.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 092645.28290; Sat, 31 Jul 1993 09:26:45 EDT Received: by merint (AIX 3.2/UCB 5.64/4.03) id AA30757; Sat, 31 Jul 1993 06:35:11 -0600 From: merint!alexc@uunet.UU.NET (Alex Chan - Admin) Message-Id: <9307311235.AA30757@merint> To: uunet!pine-info%cac.washington.edu@uunet.UU.NET Cc: alexc%merint@uunet.UU.NET Subject: Arrow Keys and Pine ... Date: Sat, 31 Jul 93 06:35:11 -0700 We have just inherited 20 wyse50 technology terminals, and the cursor keys do not work on those terminals. How could one adjust pine to allow the usage of the cursor keys ? Or adjust the terminfo or termcap file to get the right settings. But the odd thing is that /usr/bin/vi works fine with those wyse50 terminals with those arrow keys. I guess the termcap and terminfo entries on our IBM RS6000 is correct. Thanks for your help.