From owner-pine-info@cac.washington.edu Fri Sep 30 16:37:52 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00209; Fri, 30 Sep 94 16:37:52 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00523; Fri, 30 Sep 94 16:31:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00517; Fri, 30 Sep 94 16:31:19 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA24631; Fri, 30 Sep 1994 19:28:13 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA24524; Fri, 30 Sep 94 18:31:16 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA12886; Fri, 30 Sep 94 18:31:16 CDT Date: Fri, 30 Sep 1994 18:31:15 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: Daniel Cc: pine-info@cac.washington.edu Subject: Re: specifying mail headers In-Reply-To: <36i207$h2k@batman.tamu.edu> Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1044 On 30 Sep 1994, Daniel wrote: > How would one specify a "hard-coded" mail header in Pine. For > example, if I wanted all my outgoing mail to have a "Reply-To:" > field of "abc@tamu.edu", how would I do it? > Go to the configuration form and find the line 'customized-hdrs'. Add or change the information you want. For example add: Reply-To: abc@tamu.edu or Reply-To: abc@tamu.edu, Organization: ACME Help Services Note that a comma(,) separate each customized header. Hope this helps, --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Fri Sep 30 17:52:58 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03569; Fri, 30 Sep 94 17:52:58 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02207; Fri, 30 Sep 94 17:45:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02201; Fri, 30 Sep 94 17:45:50 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qqsHk-00000IC; Fri, 30 Sep 94 17:26 PDT To: pine-info@cac.washington.edu From: ralphs@halcyon.halcyon.com (Ralph Sims) Subject: 3.90 - possible bug in 'postpone' Date: 30 Sep 1994 23:37:32 GMT Message-Id: <36i7fs$679@news.halcyon.com> Scenario: user starts composing a message and decides to use the ^O option to postpone writing. User then attempts to re-access the message, and sucessfully is allowed to continue editing the file. User then attempts to postpone editing again, and an endless loop occurs, filling the drive with a .pine-debug1 file (the first we caught was 75 megs in size, and the second was 53 megs). Reproducible problem. I have a debug file a couple of megs in size if someone wants to take a whack at the problem. From owner-pine-info@cac.washington.edu Fri Sep 30 18:07:46 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03937; Fri, 30 Sep 94 18:07:46 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08750; Fri, 30 Sep 94 18:01:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08744; Fri, 30 Sep 94 18:01:55 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qqsXI-00000iC; Fri, 30 Sep 94 17:42 PDT To: pine-info@cac.washington.edu From: clive@erase (E. Clive Bard) Subject: Will somebody please teach Pine 3.90 to FORK? Date: 30 Sep 1994 15:42:36 GMT Message-Id: <36hblc$ck9@maelstrom.acton.timeplex.com> Greetings, I like pine very much, but I don't like waiting for it to do stuff that it could be doing in the background while I'm doing something else. Case in point: When I post news with Pine, and I'm in the Newsgroups: header, pine starts to synchronize either its list of newsgroups, or update its idea of whats in them... The result, since my nntp-server is 17 hops away at the moment, is that I wait about 90 seconds to be able to move the cursor to the next field. And woe to the poor schmuck who happens to drop back into the Newsgroups: header as the entire situation occurs all over again... Now I don't mind if Pine wants to be up-to-date on all of its news information, but honestly, why cant it do it in the background? _______________________________________________________________ Clive Bard, Network Administrator E-Mail: clive@nda.com Net Daemons Associates, Inc. `Computer Networking Solutions' 400 West Cummings Park, Suite 4250 (617) 937-3338 Woburn, MA 02108 Beeper: (508) 426-7114 From owner-pine-info@cac.washington.edu Fri Sep 30 18:08:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03972; Fri, 30 Sep 94 18:08:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02453; Fri, 30 Sep 94 18:02:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02447; Fri, 30 Sep 94 18:02:02 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qqsYp-00000hC; Fri, 30 Sep 94 17:44 PDT To: pine-info@cac.washington.edu From: clive@erase (E. Clive Bard) Subject: Pine 3.90 - No Save in Editor Date: 30 Sep 1994 15:48:44 GMT Message-Id: <36hc0s$ck9@maelstrom.acton.timeplex.com> Greetings, I like Pico fine as an editor, but there are time when I would like to use an alternate like vi. No problem you say, because I can set my alternate editor in my configuration and use it whenever I want... However, since sometimes, in an effort to do one keystroke I do another, like CTRL-Z, which causes Pine to crash if I'm Composing new mail with the internal editor, I would like to be able to save mail that I am composing periodically. Unfortunately, Pine doesn't allow you to save mail you are in the process of composing in the Internal editor. One solution might be to set my alternate editor to pico (cause I like the word-wrap) and set the enable alternate editor implicit switch, however, that precludes me from getting at vi with a handy CTRL-_. Pine should be more cautious about mail you are in the state of composing; if it won't autosave it, it should allow you to save it periodically. _______________________________________________________________ Clive Bard, Network Administrator E-Mail: clive@nda.com Net Daemons Associates, Inc. `Computer Networking Solutions' 400 West Cummings Park, Suite 4250 (617) 937-3338 Woburn, MA 02108 Beeper: (508) 426-7114 From owner-pine-info@cac.washington.edu Fri Sep 30 20:44:51 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07208; Fri, 30 Sep 94 20:44:51 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11044; Fri, 30 Sep 94 20:41:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11038; Fri, 30 Sep 94 20:41:08 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qqv3e-00000iC; Fri, 30 Sep 94 20:24 PDT To: pine-info@cac.washington.edu From: hribnak@nucleus.com (Jim Hribnak) Subject: Incoming-folders= Message-Id: Date: Fri, 30 Sep 1994 18:02:44 GMT WHen I set this to: incoming-folders=bsdi, procmail, news, root etc Pine has these list up above with INBOX but yet when I hit return on them it says file or directory how come? if I go below to the collective folders I think, and I can read the messages areas there. What have I done in the .pinerc that I should do or not do? PLease email me at hribnak@nucleus.com Jim From owner-pine-info@cac.washington.edu Fri Sep 30 22:40:18 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09343; Fri, 30 Sep 94 22:40:18 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06103; Fri, 30 Sep 94 22:34:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rigel.infinet.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06097; Fri, 30 Sep 94 22:34:27 -0700 Received: by mail.infinet.com (Smail3.1.28.1 #9) id m0qqx5S-000DNwC; Sat, 1 Oct 94 01:34 EDT Date: Sat, 1 Oct 1994 01:34:22 -0400 (EDT) From: "David M. Harvey I" Subject: Unsubscribe To: Pine-info@cac.washington.edu In-Reply-To: <36hc0s$ck9@maelstrom.acton.timeplex.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Unsubscribe Pine-info ___ **************************************************************************** |No Guts, No Glory, No Honor, No Victory, Pillage, Plunder, and Take Heads!| **************************************************************************** | Dave M. Harvey PGP 2.61 Public Key available. | | PO Box 151311 Finger warrior@infinet.com.us | | Columbus, OH 43215-8311 dharvey@freenet.columbus.oh.us | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-== From owner-pine-info@cac.washington.edu Sat Oct 1 01:28:57 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12529; Sat, 1 Oct 94 01:28:57 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08413; Sat, 1 Oct 94 01:18:31 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08405; Sat, 1 Oct 94 01:18:28 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qqzKI-00000sC; Sat, 1 Oct 94 00:57 PDT To: pine-info@cac.washington.edu From: gillman@almaak.usc.edu ([Howard Gillman]) Subject: Re: Ctrl-^ to block for the kill Date: 1 Oct 1994 00:19:00 -0700 Message-Id: <36j2h4$v4@almaak.usc.edu> References: <368g3f$ds5@garuda.csulb.edu> <36g0us$cka@garuda.csulb.edu> <36htli$rvd@apakabar.cc.columbia.edu> Try control-. Sounds weird, but something suggested it to me and it worked. From owner-pine-info@cac.washington.edu Sat Oct 1 02:24:27 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13918; Sat, 1 Oct 94 02:24:27 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15546; Sat, 1 Oct 94 02:12:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15540; Sat, 1 Oct 94 02:12:16 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qr0Cc-00000LC; Sat, 1 Oct 94 01:53 PDT To: pine-info@cac.washington.edu From: gbgf@netcom.com (GBGF) Subject: Re: Can't use paste in Windows with Pine: why? Message-Id: References: Date: Fri, 30 Sep 1994 21:12:53 GMT Howard Altschuler (altschh@iia.org) wrote: : > On 27 Sep 1994, Howard Altschuler wrote: : > : > > I use pine 3.90. When I try to paste text from a windows app to pine (via : > > crosstalk), it takes about a minute per line! : > : > Yes. In windows pine paste works by inserting the characters as if you : > were typing them. This is a little slower than if we just droped them : > into the buffer, but I've never seen or heard of it taking a minute per : > line. A more detailed description of your system and what other : > applications are running may help me identify the problem. Specifically, : > I'm looking for other applications that may in some way slow down the rate : > at which pine receives events. : > : I have a 386-40 with 8 megs of memory, windows 3.1, dos 6.21, and the : problem occurs even if I only run crosstalk for windows. I have a Pentium 60mhz and Crosstalk for Windows. I experience the same thing -- i.e., if I use Ctrl-^ and block and paste text, it works fine, but if I use the Copy and Paste from Crosstalk, for each line of text the cursor blinks for 20-45 seconds before the text appears on the screen. sometimes it takes so long that my net provider, netcom, drops my connection. -- 68% of all statistics are misleading gbgf@netcom.com (Jerry Stein) From owner-pine-info@cac.washington.edu Sat Oct 1 10:06:00 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22637; Sat, 1 Oct 94 10:06:00 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14863; Sat, 1 Oct 94 09:57:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14857; Sat, 1 Oct 94 09:57:05 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qr7Mu-00000LC; Sat, 1 Oct 94 09:33 PDT To: pine-info@cac.washington.edu From: L.G.Cuthbert@qmw.ac.uk (Laurie Cuthbert) Subject: Re: PC Pine v3.90 for Winsock won't send mail Date: Sat, 1 Oct 1994 17:15:21 GMT Message-Id: References: <9409111531.AA05801@raindrop.seaslug.org> <35uabu$s7h@alpha.cisi.unige.it> <369jht$gic@tribune.usask.ca> In article <369jht$gic@tribune.usask.ca> Keele@Duke.Usask.CA (A. Ross Keele) writes: >From: Keele@Duke.Usask.CA (A. Ross Keele) >Subject: Re: PC Pine v3.90 for Winsock won't send mail >Date: 27 Sep 1994 17:08:13 GMT >In article <35uabu$s7h@alpha.cisi.unige.it>, root@news.unige.it (system >PRIVILEGED account) says: >> >>George A. Theall (theall1@tju.edu) wrote: >>: > >However, whenever I try to *send* mail, the hourglass comes up and stays >up. >>: > >I left my machine along for 20 minutes once before using the >three-fingered >>: > >salute to shutdown the window. >> >>Also I have the same problem, all work wpine don't send , I use Trumpet Winsock >1beta6 and IDA Sendmail on a SGI as SMTP server >And I as well. Same symptoms. All other apps work fine with the IMAP server >and SMTP. I'm using MS TCP/IP stack (and have also tried Trumpet beta 15). I have exactly the same thing with Trumbet beta 15 over SLIP. The debug file gives the following trace: IMAP 16:59 10/1 mm_log babble: Find of mailbox outside context: C:\intruptd IMAP mm_notify NIL : {osprey} : osprey IMAP2bis Service 7.5(72) at Sat, 1 Oct 1994 16:59:37 +0100 (BST) IMAP mm_notify bye : {osprey.elec.qmw.ac.uk} : osprey IMAP2bis server terminating connection === send called === Addres Regards Laurie Cuthbert From owner-pine-info@cac.washington.edu Sat Oct 1 13:43:35 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26008; Sat, 1 Oct 94 13:43:35 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17504; Sat, 1 Oct 94 13:33:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17498; Sat, 1 Oct 94 13:33:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrAsl-00000LC; Sat, 1 Oct 94 13:18 PDT To: pine-info@cac.washington.edu From: aevinck@wheel.ucdavis.edu (Aaron Vinck) Subject: Re: Printing to local Mac printer. Date: 1 Oct 1994 20:10:29 GMT Message-Id: <36kfnl$6sd@mark.ucdavis.edu> References: <35je5i$4tq@mark.ucdavis.edu> Daniel Akst (akst@netcom.com) wrote: : I think it's software. I can print to my laser just fine using Windows : Terminal, the old shareware Procomm for DOS, whatever, but WinComm : agsolutely won't do it, and I get the same sequence of pointless : questions and error messages, more or less, that Aaron does. Delrina says : that after investigating, they can state that winComm won't accept the Y : print command from Pine. I think and hope it's software. I wonder, though, if it's because the Deskwriter uses a print spooler -- that this somehow complicates things. : John Piekarski (jonpi@eskimo.com) wrote: : : There doesn't seem to be. I have problems doing just about anything else : : Unix-related on my Mac, but I can easily print to my Laserwriter. I just : : followed the instructions in Pine's SETUP menu and everything worked : : fine. I have Microphone Pro, so I know Microphone products can do this. : : Perhaps there is a problem in your Microphone transfer settings. What, specifically, did you have to do in PINE's SETUP menu? I looked at it, but didn't find anything that looked like it needed adjusting. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Aaron Vinck aevinck@wheel.ucdavis.edu -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ----------------[ New DCN Folks...]------------------ | If I happen to mention anything that is foreign, | | strange, or mystical to you (issues, technology, | | acronyms, DCN history, etc.), please ask me. | | I know what it's like being new and not knowing | | what people are taking about! | ----------------------------------------------------- From owner-pine-info@cac.washington.edu Sat Oct 1 16:22:22 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28771; Sat, 1 Oct 94 16:22:22 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25878; Sat, 1 Oct 94 16:11:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25872; Sat, 1 Oct 94 16:11:40 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrDEz-00000jC; Sat, 1 Oct 94 15:49 PDT To: pine-info@cac.washington.edu From: galt@csulb.edu (Charles Galt) Subject: Re: Ctrl-^ to block for the kill Date: 30 Sep 1994 03:33:48 GMT Message-Id: <36g0us$cka@garuda.csulb.edu> References: <368g3f$ds5@garuda.csulb.edu> : > On 27 Sep 1994, Charles Galt wrote: : > : > > I can no longer (using PINE 3.88 here) make the Control-^ key work : > > to block text that can then be Killed by ^K (rather than doing it a line : > > at a time). When I do it line by line, PINE (and PICO) responds with "You : > > can block the text with Ctrl-^ and then Kill", but it doesn't work. I : > > used to be able to do this, but don't know what's different now. : > > Anyone know what's up? I'm using VT100 emulation (as always) with our : > > system PINE on Unix mainframe. : > > Thanks... Chuck Forgot to mention that MY problem is on a PC keyboard; still no luck, even with PINE 3.90 now installed here... chuck |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | Charles Galt, Professor Tel: 310-985-4808 | | Department of Biological Sciences Fax: 310-985-2315 | | California State University Internet: galt@csulb.edu | | 1250 Bellflower Boulevard Omnet: c.galt | | Long Beach, CA 90840-3702, USA Finger: galt@beach.csulb.edu| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Sat Oct 1 17:52:47 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00437; Sat, 1 Oct 94 17:52:47 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27189; Sat, 1 Oct 94 17:44:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from pacific.centre.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27183; Sat, 1 Oct 94 17:44:49 -0700 Received: by pacific.centre.edu (1.37.109.4/16.2) id AA01260; Sat, 1 Oct 94 20:43:42 -0400 Date: Sat, 1 Oct 1994 20:43:41 -0400 (EDT) From: "Ben T. Feese" To: Howard@pacific.centre.edu Cc: pine-info@cac.washington.edu Subject: Re: Can't use paste in Windows with Pine: why? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > On 27 Sep 1994, Howard Altschuler wrote: > I use pine 3.90. When I try to paste text from a windows app to pine (via > crosstalk), it takes about a minute per line! ========= CLIP ======= CLIP ======= CLIP ========= CLIP ======== CLIP ====== I use cut&paste from the Windows clipboard as my mainstay for moving text around from msg. to msg. I am accessing pine (on a unix server) via a tnvt220 (telnet) connection via a remote node dialin to a Novell LAN. This is the only way I know of on a barebones telnet access of moving text around (given that pine can't copy a marked text block out to a file that can be read back into to another msg.). For me the Windows clipboard is not exactly fast, but it's much much faster than I could ever type it in (my dial in link is operating at 19200 bps). Such clipboard service is the main reason I stick with windows (since most of my apps, like the Novell tnvt200, are DOS programs). It is possible that your slow windows clipboard performance is due to your windows system.ini file not being optimized. Sorry I can't help you there---maybe somebody else on the net can suggest how they optimized their windows comm settings for such a situation. ============================================================================= Ben T. Feese Professor of Biology Biochemistry/Molecular Biology Program Centre College, Danville, KY 40422 (USA) Internet: feeseb@centre.edu Phone: (606) 238-5318 FAX: (606) 236-7925 From owner-pine-info@cac.washington.edu Sat Oct 1 18:29:35 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01086; Sat, 1 Oct 94 18:29:35 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20997; Sat, 1 Oct 94 18:21:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20991; Sat, 1 Oct 94 18:21:09 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrFI7-000008C; Sat, 1 Oct 94 18:00 PDT To: pine-info@cac.washington.edu From: mauricio@tezcat.com (Mauricio Araujo) Subject: Re: Including Uploaded Articles in Mail...HOW? Date: 29 Sep 1994 23:59:49 -0500 Message-Id: <36g605$ktp@xochi.tezcat.com> References: Have you saved the article that you upload as text only (i.e. ascii)? This is the problem that I had when I first tried to do this. You can check to see if it is the article by opening it in pico. It will show you exactly what the other person will receive. lindae@netcom.com wrote: : I create documents on a PC in MicroSoft Word and need to upload them : to my NET directory and then e-mail them off to another user. Does : anyone know the most effective way of doing this. : Here's the problem...I've been able to successfully upload the articles : using ProComm Plus and include them in my mail, but the person on the : other end receives my document with all kinds of weird line wrapping, : making it virtually unreadable. I've tried uuencoding the document : online before I send it, but that doesn't seem to work either. : Any helpful, step by step instructions would be most appreciated! : Please e-mail to lindae@netcom.com : Thanks : Linda : lindae@netcom.com -- ============================================================================= Opinions not necessarily those of the author ;) _____________________________________________________________________________ From owner-pine-info@cac.washington.edu Sun Oct 2 04:01:04 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10794; Sun, 2 Oct 94 04:01:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04516; Sun, 2 Oct 94 03:52:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04510; Sun, 2 Oct 94 03:52:18 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrO3M-00000OC; Sun, 2 Oct 94 03:22 PDT To: pine-info@cac.washington.edu From: Brad Subject: Re: Ctrl-^ to block for the kill Date: Sun, 2 Oct 1994 11:15:26 +0100 (BST) Message-Id: References: <368g3f$ds5@garuda.csulb.edu> <36g0us$cka@garuda.csulb.edu> <36htli$rvd@apakabar.cc.columbia.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36htli$rvd@apakabar.cc.columbia.edu> On 30 Sep 1994, Yee Chang Lee wrote: > |Forgot to mention that MY problem is on a PC keyboard; still no > |luck, even with PINE 3.90 now installed here... chuck I also cannot get ^_ to work... any more. We used to use Rainbow here, but we have recently moved to an all-Windows environment, so we now use KEAterm 420. Does anybody know why ^_ might not work in this case? Thanks! --Simon. From owner-pine-info@cac.washington.edu Sun Oct 2 05:06:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12478; Sun, 2 Oct 94 05:06:50 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28568; Sun, 2 Oct 94 04:58:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28562; Sun, 2 Oct 94 04:58:18 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrP4S-00000PC; Sun, 2 Oct 94 04:27 PDT To: pine-info@cac.washington.edu From: ccsas@humus.ucc.hull.ac.uk (Alex Sharaz) Subject: Address book patches to pine 3.90 Message-Id: Date: 30 Sep 94 15:57:45 GMT Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi all, I'm trying to get hold of the 3.90 source patches for the addressbook bug. I know I had them at one point, but unfortunately I seem to have deleted that message without saving the patches. Can anyone tell me where to get hold of them ? alex RFC-822: A.Sharaz@computer-centre.hull.ac.uk X.400: I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB X.500: c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz Tel: +44 482-465700 Fax: +44 482-466441 From owner-pine-info@cac.washington.edu Sun Oct 2 10:26:29 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17326; Sun, 2 Oct 94 10:26:29 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08925; Sun, 2 Oct 94 10:19:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08919; Sun, 2 Oct 94 10:19:25 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrTzH-000019C; Sun, 2 Oct 94 09:42 PDT To: pine-info@cac.washington.edu From: ddc1@jaguar.uofs.edu Subject: Re: Signature *after* quoted text in replies? Date: 2 Oct 94 12:14:17 EST Message-Id: <1994Oct2.121417.1@jaguar.uofs.edu> References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> In article <367hhc$bd6@crcnis1.unl.edu>, jgraham@herbie.unl.edu (John Graham) writes: > I know that pine 3.9 has that option in the Configure section of it > but what I can't get it to do is to put the sig file after a fowarded > file. I delete it from the top and read it in with Control R at the bottom. I haven't figured out an automatic way yet... -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dave D. Cawley | Where a social revolution is pending and, University Of Scranton | for whatever reason, is not accomplished, ddc1@jaguar.uofs.edu | reaction is the alternative. ddc1@SCRANTON | -Daniel De Leon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Sun Oct 2 11:06:14 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17927; Sun, 2 Oct 94 11:06:14 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02675; Sun, 2 Oct 94 11:00:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02669; Sun, 2 Oct 94 11:00:17 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrUqw-00000BC; Sun, 2 Oct 94 10:37 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: PINE Date: 2 Oct 1994 16:47:46 GMT Message-Id: <36mo7i$m2d@news.halcyon.com> References: <36im0q$3ok@merlion.singnet.com.sg> bobclark@merlion.singnet.com.sg (Bob Clark) writes: >My internet provider uses the Pine mail program. I'd like to find out >how/if I can write programs for auto-answering mail, forwarding mail if >it's from a specific street talk name etc... The local help line people >are unable to provide any information on the suject. Could someone point >me to some ref sources...... You can do these things with a filtering program like Elm's filter, procmail, or deliver. The filtering happens as the mail is delivered so it's independent of the mail user agent you're using. Pine has an incoming-folders variable which you can use to list all your incoming folders at the top of your folder list. I've written some instructions for using filter which are at ftp://ftp.ii.com/pub/ii/Internet/filtering_mail (I'm planning to update this soon so please send me suggestions for improvement!). For specific questions about... See... =============================== ====== Pine comp.mail.pine Elm's filter program comp.mail.elm procmail, deliver, etc comp.mail.misc Hope this helps, Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Sun Oct 2 11:58:28 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18758; Sun, 2 Oct 94 11:58:28 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10029; Sun, 2 Oct 94 11:52:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10023; Sun, 2 Oct 94 11:52:50 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrVkL-000008C; Sun, 2 Oct 94 11:34 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: Signature *after* quoted text in replies? Date: 2 Oct 1994 17:57:48 GMT Message-Id: <36msas$nub@news.halcyon.com> References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> <1994Oct2.121417.1@jaguar.uofs.edu> >In article <367hhc$bd6@crcnis1.unl.edu>, jgraham@herbie.unl.edu (John Graham) writes: >> I know that pine 3.9 has that option in the Configure section of it >> but what I can't get it to do is to put the sig file after a fowarded >> file. ddc1@jaguar.uofs.edu writes: > I delete it from the top and read it in with Control R at the bottom. >I haven't figured out an automatic way yet... I also haven't figured out a way to automate this, but I think I'm coming around to liking this behaviour. To me it makes sense that the message that you're forwarding is the only thing after this line: ---------- Forwarded message ---------- And all your info, including your sig, is above this line. But for people who want their sig to be the last thing in the message it would be nice if this were configurable. Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Sun Oct 2 13:24:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20313; Sun, 2 Oct 94 13:24:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04250; Sun, 2 Oct 94 13:19:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04244; Sun, 2 Oct 94 13:19:11 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrX3N-000008C; Sun, 2 Oct 94 12:58 PDT To: pine-info@cac.washington.edu From: millerdg@it.uwp.edu (Gabriel Millerd) Subject: Sendmail variants Date: 2 Oct 1994 19:56:10 GMT Message-Id: <36n38q$rl1@cs.uwp.edu> Hello all, The object of the program is to shuffle my signature files around as frequently as possible. I am trying to write a program that will shuffle all the files in $HOME/.sig directory and copy one to $HOME/.signature. Also I want the program to pass all of its arguments to "sendmail" so the actual mesasge will be sent. This will work GREAT with pine, since pine allows you to specify your sendmail program in the $HOME/.pinerc file. Can anyone help me? Thanks {please respond in email as i cannot read news often} From owner-pine-info@cac.washington.edu Sun Oct 2 13:41:38 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20644; Sun, 2 Oct 94 13:41:38 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11227; Sun, 2 Oct 94 13:35:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from hoss.vgi.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11221; Sun, 2 Oct 94 13:35:44 -0700 Received: from hawkeye.vgi.com ([1.0.2.103]) by vgi.com (4.1/SMI-4.1) id AA08289; Sun, 2 Oct 94 16:43:32 EDT Received: by hawkeye.vgi.com (1.37.109.4/SMI-4.1) id AA03841; Sun, 2 Oct 94 16:34:59 -0400 Date: Sun, 2 Oct 1994 16:34:59 -0400 (EDT) From: Alex Lewin X-Sender: lewin@hawkeye To: Gabriel Millerd Cc: pine-info@cac.washington.edu Subject: Re: Sendmail variants In-Reply-To: <36n38q$rl1@cs.uwp.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 2 Oct 1994, Gabriel Millerd wrote: > Hello all, > > The object of the program is to shuffle my signature files around as > frequently as possible. > > I am trying to write a program that will shuffle all the files in > $HOME/.sig directory and copy one to $HOME/.signature. Also I want the > program to pass all of its arguments to "sendmail" so the actual mesasge > will be sent. Instead of doing that, why don't you make .signature into a named pipe instead of a regular file, and run a program which writes to it? For example (bournish shell): [512]$ mknod FOO p [513]$ (while [ 1 ] ; do fortune > FOO ; done) & [1] 24116 [514]$ cat FOO "The C Programming Language -- A language which combines the flexibility of assembly language with the power of assembly language." [515]$ cat FOO If I had any humility I would be perfect. -- Ted Turner etc. Alex > This will work GREAT with pine, since pine allows you to specify your > sendmail program in the $HOME/.pinerc file. > > Can anyone help me? > > Thanks {please respond in email as i cannot read news often} > From owner-pine-info@cac.washington.edu Sun Oct 2 14:01:03 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21050; Sun, 2 Oct 94 14:01:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04708; Sun, 2 Oct 94 13:55:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04702; Sun, 2 Oct 94 13:55:14 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrXbO-00000FC; Sun, 2 Oct 94 13:33 PDT To: pine-info@cac.washington.edu From: ez017400@chip.ucdavis.edu (Hemang Patel) Subject: Re: Signature *after* quoted text in replies? Date: 2 Oct 1994 20:30:11 GMT Message-Id: <36n58j$rks@mark.ucdavis.edu> References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> <1994Oct2.121417.1@jaguar.uofs.edu> <36msas$nub@news.halcyon.com> Nancy McGough (nancym@ii.com) wrote: : >In article <367hhc$bd6@crcnis1.unl.edu>, jgraham@herbie.unl.edu (John Graham) writes: : >> I know that pine 3.9 has that option in the Configure section of it : >> but what I can't get it to do is to put the sig file after a fowarded : >> file. : ddc1@jaguar.uofs.edu writes: : > I delete it from the top and read it in with Control R at the bottom. : >I haven't figured out an automatic way yet... : I also haven't figured out a way to automate this, but I think I'm coming : around to liking this behaviour. To me it makes sense that the message : that you're forwarding is the only thing after this line: : ---------- Forwarded message ---------- : And all your info, including your sig, is above this line. But for people : who want their sig to be the last thing in the message it would be nice : if this were configurable. : Nancy : -- : ** ** Nancy McGough | "No one suspects the : * ** * Infinite Ink | days to be gods." : ** ** ftp://ftp.ii.com/pub/ii | -Emerson If you are using pine 3.90, go to "Setup" and choose Configure. Scroll down the list until "Signature at bottom". Put an x in this box, exit setup and restart PINE. That's it. -- _______________________________________ hcpatel@dale.ucdavis.edu From owner-pine-info@cac.washington.edu Sun Oct 2 18:30:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25913; Sun, 2 Oct 94 18:30:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14894; Sun, 2 Oct 94 18:23:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14888; Sun, 2 Oct 94 18:23:04 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrbpF-00000HC; Sun, 2 Oct 94 18:04 PDT To: pine-info@cac.washington.edu From: jkb@pipeline.com (John Belfiore) Subject: Receiving mail on my PC from my shell account. Date: 2 Oct 1994 20:53:49 -0400 Message-Id: <36nkmt$ehe@pipe1.pipeline.com> Hello. In pine, how do I download mail to my PC. I am using an internet gateway shell account. Any help would be greatly appreciated. Thank you. John (jkb@pipeline.com) From owner-pine-info@cac.washington.edu Mon Oct 3 00:13:22 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02003; Mon, 3 Oct 94 00:13:22 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13501; Mon, 3 Oct 94 00:05:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13495; Mon, 3 Oct 94 00:05:25 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrh7H-000008C; Sun, 2 Oct 94 23:43 PDT To: pine-info@cac.washington.edu From: earl@tyrell.net (Nick Danger) Subject: Re: Signature *after* quoted text in replies? Message-Id: References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> <1994Oct2.121417.1@jaguar.uofs.edu> <36msas$nub@news.halcyon.com> <36n58j$rks@mark.ucdavis.edu> Date: Mon, 3 Oct 1994 06:33:46 GMT : : ddc1@jaguar.uofs.edu writes: : : > I delete it from the top and read it in with Control R at the bottom. : : >I haven't figured out an automatic way yet... : : I also haven't figured out a way to automate this, but I think I'm coming : : around to liking this behaviour. To me it makes sense that the message : : that you're forwarding is the only thing after this line: : : ---------- Forwarded message ---------- : : And all your info, including your sig, is above this line. But for people : : who want their sig to be the last thing in the message it would be nice : : if this were configurable. : If you are using pine 3.90, go to "Setup" and choose Configure. Scroll : down the list until "Signature at bottom". Put an x in this box, exit : setup and restart PINE. That's it. I wonder why the author has this backwards. Wouldn't it make much more sense to have the signature default to the bottom and have a configuration option to have it at the top? It sure would elimininate a LOT of confusion. Earl ---------------------------------------------------------------------------- "That may have been one small step for Neil, but it was a heck of a big one for me." -- Pete Conrad ---------------------------------------------------------------------------- < earl@tyrell.net > From owner-pine-info@cac.washington.edu Mon Oct 3 01:24:10 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03555; Mon, 3 Oct 94 01:24:10 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21063; Mon, 3 Oct 94 01:20:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21051; Mon, 3 Oct 94 01:20:51 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qriIV-000008C; Mon, 3 Oct 94 00:58 PDT To: pine-info@cac.washington.edu From: mdavis@cts.com (Morgan Davis) Subject: Re: Printing to local Mac printer. Date: Mon, 3 Oct 1994 06:54:04 GMT Message-Id: References: <35je5i$4tq@mark.ucdavis.edu> In article , akst@netcom.com (Daniel Akst) wrote: > I think it's software. I can print to my laser just fine using Windows > Terminal, the old shareware Procomm for DOS, whatever, but WinComm > agsolutely won't do it, and I get the same sequence of pointless > questions and error messages, more or less, that Aaron does. Delrina says > that after investigating, they can state that winComm won't accept the Y > print command from Pine. We experience the same problem on our system. Under PINE 3.87 printing worked fine. Under 3.90, lots of subscribers now claim that printing doesn't work as it used to. Something changed between the these versions. From owner-pine-info@cac.washington.edu Mon Oct 3 02:19:06 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04663; Mon, 3 Oct 94 02:19:06 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15257; Mon, 3 Oct 94 02:15:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15251; Mon, 3 Oct 94 02:15:52 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrjD2-000008C; Mon, 3 Oct 94 01:57 PDT To: pine-info@cac.washington.edu From: Alex Sharaz Subject: Re: Problems with Lan Workplace winsock and PC-PINE for windows Date: Mon, 3 Oct 1994 09:50:47 +0100 (BST) Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: On Thu, 29 Sep 1994, Barry Landy wrote: > On Wed, 28 Sep 1994, Alex Sharaz wrote: > > > Hi all, > > > > I've noticed some messages on this group about the windows version of > > PC-PINE not working with certain flavours of winsocket. I'm running Lan > > workplace Vsn 4.2 and although I can look at myIMAP folders o.k. whenever > > I try to send a message, the PINE process "stops communicating". > > I'm running windows 3.11 on a 486/33Mhz with 8 M ram. Did somebody post a > > solution to this problem that I missed or are there still problems > > running the Windows version of PC-PINE? > > > > Alex > > > > > > RFC-822: A.Sharaz@computer-centre.hull.ac.uk > > X.400: I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB > > X.500: c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz > > Tel: +44 482-465700 Fax: +44 482-466441 > > > > Interestingly enough I have the same problem trying to run WinPine under > OS/2's TCP/IP interface (and OS/2's windows, of course). > Even odder, it has worked OK just twice! > I also get a stuck state when trying to postpone (^-O). > > I have so far been prepared to be convinced that this is an > incompatibility between OS/2 windows and "real" windows, but I am > encouraged by your finding (and others in this group) to think that it > may be bug(s) in winpine after all. > > > ======================================================================= > Barry Landy, Head of Systems and Development, > University of Cambridge Computing Service > Barry.Landy@ucs.cam.ac.uk 0-1223-334713 +44-1223-334713 > > > I've solved my problem with WinPine thanks to some messages from other people on this group. I have a number of PC Mail clients set up on my PC and one of them requires a TZ (timezone) varialbe to be set up. Once I'd removed this variable from my autoexec.bat file, everything worked o.k. alex RFC-822: A.Sharaz@computer-centre.hull.ac.uk X.400: I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB X.500: c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz Tel: +44 482-465700 Fax: +44 482-466441 From owner-pine-info@cac.washington.edu Mon Oct 3 04:04:35 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07006; Mon, 3 Oct 94 04:04:35 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22883; Mon, 3 Oct 94 04:00:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from inet-gw-1.pa.dec.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22875; Mon, 3 Oct 94 04:00:31 -0700 Received: from pobox1.pa.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA29698; Mon, 3 Oct 94 03:56:28 -0700 Received: by pobox1.pa.dec.com; id AA22740; Mon, 3 Oct 94 03:56:26 -0700 Received: by new.dec.com (5.65/DEC-Ultrix/4.3) id AA12091; Mon, 3 Oct 1994 11:56:52 +0100 Received: by ds3100.new.dec.com (5.65/DEC-Ultrix/4.3) id AA06835; Mon, 3 Oct 1994 11:57:14 +0100 Date: Mon, 3 Oct 1994 11:57:14 +0100 From: stuart@ds3100.new.dec.com (Stuart Broderick) Message-Id: <9410031057.AA06835@ds3100.new.dec.com> To: pine-info@cac.washington.edu Subject: unsubscribe pine-info unsubscribe pine-info From owner-pine-info@cac.washington.edu Mon Oct 3 05:11:58 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08457; Mon, 3 Oct 94 05:11:58 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23844; Mon, 3 Oct 94 05:06:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23838; Mon, 3 Oct 94 05:06:45 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrlqN-00000JC; Mon, 3 Oct 94 04:46 PDT To: pine-info@cac.washington.edu From: igbf@osf01.cc.rl.ac.uk (Mr I G B Fabian) Subject: "Metamal" in pine Date: 3 Oct 1994 11:17:33 GMT Message-Id: <36op8d$1p8p@unixfe.rl.ac.uk> Has anyone built a version of pine that uses metamail? I really like pine but the multimedia support is quite limited (compared to what metamail should provide). Any help or advice on this would be appreciated. Ivan Fabian From owner-pine-info@cac.washington.edu Mon Oct 3 06:26:57 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09846; Mon, 3 Oct 94 06:26:57 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18432; Mon, 3 Oct 94 06:23:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18426; Mon, 3 Oct 94 06:23:31 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrn1q-000008C; Mon, 3 Oct 94 06:02 PDT To: pine-info@cac.washington.edu From: Cary Orange Subject: Re: Problems with Lan Workplace winsock and PC-PINE for windows Date: Mon, 03 Oct 94 08:32:08 PDT Message-Id: <36otlv$jja@gazoo.sdd.comsat.com> References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > I've solved my problem with WinPine thanks to some messages from other > people on this group. I have a number of PC Mail clients set up on my PC > and one of them requires a TZ (timezone) varialbe to be set up. Once I'd > removed this variable from my autoexec.bat file, everything worked o.k. > > alex > Thanks for the tip. I too had a TZ variable defined in my environment and after taking it out, my PC-PINE 3.90 now sends mail. BTW, I'm using the NetManage winsock. Cary From owner-pine-info@cac.washington.edu Mon Oct 3 07:02:07 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10536; Mon, 3 Oct 94 07:02:07 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25167; Mon, 3 Oct 94 06:57:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25161; Mon, 3 Oct 94 06:57:44 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrnWL-00000MC; Mon, 3 Oct 94 06:33 PDT To: pine-info@cac.washington.edu From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Subject: Way to set pine/pico tmp directory Date: 3 Oct 94 13:26:39 GMT Message-Id: <3737@jagubox.gsfc.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit It seems that pine/pico don't honor (or, at least, aren't aware) of TMPDIR as the location of what users want their temp.scratch directory to be. Any way to have pine/pico use something other than /tmp? -- #include | Jim Jagielski | jim@jagubox.gsfc.nasa.gov | V: 301 286-5964 | | NASA/GSFC, Code 734.4 | Greenbelt, MD 20771 | F: 301 286-1719 | << Hey! Your karma just ran over my dogma! >> From owner-pine-info@cac.washington.edu Mon Oct 3 07:35:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11285; Mon, 3 Oct 94 07:35:10 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19407; Mon, 3 Oct 94 07:31:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19401; Mon, 3 Oct 94 07:31:26 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qro7a-00000JC; Mon, 3 Oct 94 07:12 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: Signature *after* quoted text in replies? Date: 3 Oct 1994 12:55:01 GMT Message-Id: <36ouv5$nfj@news.halcyon.com> References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> <1994Oct2.121417.1@jaguar.uofs.edu> <36msas$nub@news.halcyon.com> <36n58j$rks@mark.ucdavis.edu> >: >In article <367hhc$bd6@crcnis1.unl.edu>, jgraham@herbie.unl.edu (John Graham) writes: >: >> I know that pine 3.9 has that option in the Configure section of it >: >> but what I can't get it to do is to put the sig file after a fowarded >: >> file. ez017400@chip.ucdavis.edu (Hemang Patel) writes: >If you are using pine 3.90, go to "Setup" and choose Configure. Scroll >down the list until "Signature at bottom". Put an x in this box, exit >setup and restart PINE. That's it. For me the signature-at-bottom variable only works on original messages and replies. For forwarded messages it puts my sig below my message but before the forwarded message, so it's not at the bottom of the whole message. Are you able to get it to automatically go below the forwarded message? Thanks, Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Mon Oct 3 08:01:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12013; Mon, 3 Oct 94 08:01:02 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26069; Mon, 3 Oct 94 07:56:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26063; Mon, 3 Oct 94 07:56:52 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qroWI-00000mC; Mon, 3 Oct 94 07:37 PDT To: pine-info@cac.washington.edu From: lewin@vgi.com (Alex Lewin) Subject: Re: Sendmail variants Date: 3 Oct 1994 09:18:46 -0500 Message-Id: References: <199410030237.AA20127@it.uwp.edu> On Sun, 2 Oct 1994, Gabriel Millerd wrote: > interesting, great. prblem is that it runs the script too much. > shouldn't there be a wait in there somewhere?? I am thinking that the > second script should have something like a wait in it. i have a sleep > there for now but it is just a poor fix > > -cut here- > #this is run by user > mknod $HOME/.signature p > (while [ 1 ]; do $HOME/bin/sigchanger; done) & The redirection needs to go here ^ so that you have (while [ 1 ]; do $HOME/bin/sigchanger >$HOME/.signature; done) & > -cut here- > > -cut here- > #this is run by program > cd $HOME/.sig > cat `ls -utr | head -1` >$HOME/.signature and you can remove it from here cat `ls -utr | head -1` > sleep 5 #???? > -cut here- As it stood, the pair of scripts would spawn sigchangers until you hit your per-user process limit or the process table filled up. With the change, the while loop forks a sigchanger, which tries to write to $HOME/.signature and blocks, since no one is reading the other end of the pipe. This keeps the while loop from running away. The shell does indeed issue a wait, same as if you had said: (while [ 1 ]; do $HOME/bin/sigchanger >$HOME/.signature & wait; done) & Hope this helps. Alex From owner-pine-info@cac.washington.edu Mon Oct 3 08:06:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12159; Mon, 3 Oct 94 08:06:50 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19895; Mon, 3 Oct 94 08:01:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19889; Mon, 3 Oct 94 08:01:31 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qroZ1-00000nC; Mon, 3 Oct 94 07:40 PDT To: pine-info@cac.washington.edu From: brookhge@ucunix.san.uc.edu (G.E.Brookhart) Subject: Hiding Addresses in Pine 3.89 Date: 3 Oct 1994 09:52:13 -0400 Message-Id: <36p2ad$sb6@ucunix.san.uc.edu> Hello, I tried to find the answer to my question in the docs but failed there so I turn to the group for help. I am running a small mailing list through Pine 3.89 using a group alias. Currently, I simply input the address alias into the To: field. Works fine but as the list grows we are getting a really phenomenal header and some of my subscribers have asked that the header not identify them so that they can preserve their lurker anonymity. Going to a Bcc: field seems to be one option but it is another step right now. I don't want to configure a new header for a variety of reasons and was hoping that there was a way to set things up so that group aliases simply don't spit out into the whole net. Oh yes, one other rub here, the sysadmins in their power are not giving me much access to ways to configure Pine there. Is that them or is it Pine 3.89? I have access to Pine 3.90 on another account and really do prefer that version. This list is growing by leaps and bounds and so I am really locked into solving this Pine problem in a hurry. TIA, Gail Brookhart Cincinnati, Ohio brookhge@ucunix.san.uc.edu -- or -- gail@iac.net From owner-pine-info@cac.washington.edu Mon Oct 3 08:39:12 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14465; Mon, 3 Oct 94 08:39:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20782; Mon, 3 Oct 94 08:35:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20776; Mon, 3 Oct 94 08:35:08 -0700 Received: by shiva2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20123; Mon, 3 Oct 94 08:35:07 -0700 Return-Path: Date: Sun, 2 Oct 1994 18:22:03 -0700 (PDT) From: Ann Whitehead Subject: MIME To: pine-info-approval@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Resent-Date: Mon, 3 Oct 1994 08:35:03 -0700 (PDT) Resent-From: David L Miller Resent-To: pine-info@cac.washington.edu Resent-Message-Id: When I send files by Pine they arrive in MIME and receivers of my mail need a way to decode them. Is there any simple MIME software to which you could refer me so files I send via Pine could be translated by my relatively non-technical friends? Suggestions would be much appreciated! Thanks. Ann Whitehead From owner-pine-info@cac.washington.edu Mon Oct 3 10:01:56 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18471; Mon, 3 Oct 94 10:01:56 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28902; Mon, 3 Oct 94 09:56:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28896; Mon, 3 Oct 94 09:56:06 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrqKd-00000AC; Mon, 3 Oct 94 09:33 PDT To: pine-info@cac.washington.edu From: Barry Landy Subject: Re: Problems with Lan Workplace winsock and PC-PINE for windows Date: Mon, 3 Oct 1994 17:29:21 +0100 (BST) Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: On Mon, 3 Oct 1994, Alex Sharaz wrote: > On Thu, 29 Sep 1994, Barry Landy wrote: > > > On Wed, 28 Sep 1994, Alex Sharaz wrote: > > > > > Hi all, > > > > > > I've noticed some messages on this group about the windows version of > > > PC-PINE not working with certain flavours of winsocket. I'm running Lan > > > workplace Vsn 4.2 and although I can look at myIMAP folders o.k. whenever > > > I try to send a message, the PINE process "stops communicating". > > > I'm running windows 3.11 on a 486/33Mhz with 8 M ram. Did somebody post a > > > solution to this problem that I missed or are there still problems > > > running the Windows version of PC-PINE? > > > > > > Alex > > > > > > > > > RFC-822: A.Sharaz@computer-centre.hull.ac.uk > > > X.400: I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB > > > X.500: c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz > > > Tel: +44 482-465700 Fax: +44 482-466441 > > > > > > > Interestingly enough I have the same problem trying to run WinPine under > > OS/2's TCP/IP interface (and OS/2's windows, of course). > > Even odder, it has worked OK just twice! > > I also get a stuck state when trying to postpone (^-O). > > > > I have so far been prepared to be convinced that this is an > > incompatibility between OS/2 windows and "real" windows, but I am > > encouraged by your finding (and others in this group) to think that it > > may be bug(s) in winpine after all. > > > > > > ======================================================================= > > Barry Landy, Head of Systems and Development, > > University of Cambridge Computing Service > > Barry.Landy@ucs.cam.ac.uk 0-1223-334713 +44-1223-334713 > > > > > > > I've solved my problem with WinPine thanks to some messages from other > people on this group. I have a number of PC Mail clients set up on my PC > and one of them requires a TZ (timezone) varialbe to be set up. Once I'd > removed this variable from my autoexec.bat file, everything worked o.k. > > Wow - what a wierd and wonderful idea - how on earth did you come to try that. Believe it or not, removing the SET TZ=value from the AUTOEXEC.BAT solved my problems also! I have emailed pine-bugs with the good news. Of course, this is not a solution, as we do actually need to set the timezone (the piece of email I sent myself from Windows Pine under OS/2 said it came from the PDT timezone, which is Pine's default). ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0-1223-334713 +44-1223-334713 From owner-pine-info@cac.washington.edu Mon Oct 3 11:42:20 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24012; Mon, 3 Oct 94 11:42:20 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25556; Mon, 3 Oct 94 11:36:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25550; Mon, 3 Oct 94 11:36:12 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrrtZ-00000PC; Mon, 3 Oct 94 11:13 PDT To: pine-info@cac.washington.edu From: Wayne Wilson Subject: PEM or PGP Date: Mon, 3 Oct 1994 13:50:53 -0700 (PDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The readme for future enhancements lists PEM or PGP support. Can anyone summarize what the leanings are for one or the other, i.e. which one is likely to be included and why? I know why one would want either system, I am just trying to gauge sentiment favoring PEM or PGP over the other in the pine community. From owner-pine-info@cac.washington.edu Mon Oct 3 12:50:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27069; Mon, 3 Oct 94 12:50:08 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03386; Mon, 3 Oct 94 12:42:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from ilium.troy.msen.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03380; Mon, 3 Oct 94 12:42:22 -0700 Received: from boozsh by ilium.troy.msen.com with uucp (Smail3.1.28.1 #1) id m0qrtFk-0002naC; Mon, 3 Oct 94 15:40 EDT Received: from fugu.frc.com by boozsh.frc.com with smtp (Smail3.1.27.1 #2) id m0qrtDh-0006zfC; Mon, 3 Oct 94 15:38 EDT Received: by fugu.frc.com (4.1/SMI-3.2) id AA14840; Mon, 3 Oct 94 15:38:43 EDT Date: Mon, 3 Oct 1994 15:38:41 -0400 (EDT) From: "Syed A. Nabi" X-Sender: nabisa@fugu To: pine-info@cac.washington.edu Subject: unsubscribe In-Reply-To: Message-Id: Organization: FANUC Robotics North America Inc. Reply_To: nabisa@frc.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From owner-pine-info@cac.washington.edu Mon Oct 3 12:59:04 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27358; Mon, 3 Oct 94 12:59:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03928; Mon, 3 Oct 94 12:50:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03916; Mon, 3 Oct 94 12:50:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrt3r-00000QC; Mon, 3 Oct 94 12:28 PDT To: pine-info@cac.washington.edu From: georgel@starbase.neosoft.com (George Livsey) Subject: Local News Only Possible with Pine3.90 under FreeBSD 1.1.5.1? Date: 3 Oct 1994 18:59:03 GMT Message-Id: <36pk9n$etf@uuneo.neosoft.com> I have pine 3.90 installed on a box running FreeBSD 1.1.5.1 and I can read the news just fine but cannot post. I am running c-news and only have local news. Pine complains that it cannot find an nntp server. I tried localhost and the host name to no avail. Is it possible to post to local news only under Pine 3.90? George Livsey georgel@starbase.neosoft.com From owner-pine-info@cac.washington.edu Mon Oct 3 16:01:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05099; Mon, 3 Oct 94 16:01:05 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10659; Mon, 3 Oct 94 15:55:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10651; Mon, 3 Oct 94 15:55:23 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrvzy-000008C; Mon, 3 Oct 94 15:36 PDT To: pine-info@cac.washington.edu From: Stephen Sheldon Subject: Very Sloww response on ptx Date: Mon, 03 Oct 94 15:14:02 PDT Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When I first installed pine 3.90 on a Sequent with ptx 2.1, Pine ran very fast with very little wait at all. Three weeks later, I run pine and it will take 3 minutes to go into menu screen, and another three mintues to go into folders screen. When I run top it show very little cpu time. Running elm is still very quick. Any ideas what to check on as to why it is running so slow. From owner-pine-info@cac.washington.edu Mon Oct 3 18:10:07 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10573; Mon, 3 Oct 94 18:10:07 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08339; Mon, 3 Oct 94 18:05:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08333; Mon, 3 Oct 94 18:05:54 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qry3T-00000AC; Mon, 3 Oct 94 17:48 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: "Metamal" in pine Date: Mon, 3 Oct 1994 16:09:36 -0700 Message-Id: References: <36op8d$1p8p@unixfe.rl.ac.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36op8d$1p8p@unixfe.rl.ac.uk> Pine 3.90 has .mailcap support that was originally derived from metamail... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 3 Oct 1994, Mr I G B Fabian wrote: > Has anyone built a version of pine that uses metamail? I really like pine but > the multimedia support is quite limited (compared to what metamail should > provide). Any help or advice on this would be appreciated. > > Ivan Fabian > > > From owner-pine-info@cac.washington.edu Mon Oct 3 18:21:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11077; Mon, 3 Oct 94 18:21:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13691; Mon, 3 Oct 94 18:17:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13683; Mon, 3 Oct 94 18:17:01 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qryBA-00000MC; Mon, 3 Oct 94 17:56 PDT To: pine-info@cac.washington.edu From: sow@cad.luth.se (Sven-Ove Westberg) Subject: Pine 3.90 and MH folders. Date: 3 Oct 1994 20:21:39 +0100 Message-Id: <36plk3$rpn@orme1.mt.luth.se> Why can not pine read the MH folders? I have set the #mh infront of the folder in .pinerc. Pine say that the folder is empty but i have messages stored in MH format in them (eg a separate file for each message). Regards, Sven-Ove Westberg, CAD, University of Lulea, S-971 87 Lulea, Sweden. From owner-pine-info@cac.washington.edu Mon Oct 3 19:19:19 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12124; Mon, 3 Oct 94 19:19:19 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09338; Mon, 3 Oct 94 19:15:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09332; Mon, 3 Oct 94 19:15:48 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrz9c-000008C; Mon, 3 Oct 94 18:58 PDT To: pine-info@cac.washington.edu From: vanhoose@cl-next4.cl.msu.edu (Todd E. Van Hoosear) Subject: HEADERS: Activating ^T Date: 4 Oct 1994 01:54:26 GMT Message-Id: <36qcki$gsc@msuinfo.cl.msu.edu> pine390-DocServer@docserver.cac.washington.edu told me: > o You can now control which headers show up by default in the composer. > This is done by using the Setup/Config screen to set the > "default-composer-hdrs" option. You would specify a list of headers > you wish to be visible immediately when you enter the Composer. Other > headers are still accessible via the "^R Rich Header" command. Is there any way to activate your address book (using ^T) on a header line that you have custom created? (I have a long personal mailing list that I would rather keep local and not stick into /etc/sendmail/aliases but I _don't_ want people to have to flip through pages of headers if they've a decent mail program. So I added a custom line "Apparently To:" that works fine except for the address book.) Any suggestions, comments would be very welcome! Thanks, - Todd -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - T o d d E. V a n H o o s e a r - ``'''vanhoose@gdl.msu.edu - vanhoose@msu.edu - vanhoose@sparhawk.cl.msu.edu (._.) Michigan State University - East Lansing, MI USA (_) Computer Laboratory - Department of Communication `---' My Home Page PGP-aware: finger vanhoose@gdl.msu.edu for my public key ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Mon Oct 3 19:29:49 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12300; Mon, 3 Oct 94 19:29:49 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14583; Mon, 3 Oct 94 19:26:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14577; Mon, 3 Oct 94 19:26:14 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qrzIM-00000HC; Mon, 3 Oct 94 19:07 PDT To: pine-info@cac.washington.edu From: anto@inn.bppt.go.id (Anto Daryanto) Subject: Spool mail in BSDI Date: 3 Oct 1994 21:02:15 -0500 Message-Id: Hi, I have compiled Pine 3.90 for BSDI v1.1. With default configuration pine can not see user mail spool. The mail spool directory is in /usr/var/mail. So I've made a change in pine/pine-use.c to reflect the machine user mail spool directory. But still, pine can't see spool directory. Any idea? -anto =============================================================== | Antonius Daryanto | Direktorat TEI OS/2 | | a.daryanto@inn.bppt.go.id | BPPT Teknologi & | | | Jakarta, INDONESIA Linux | =============================================================== disclaimer: My opinion does not represent my employer's opinion From owner-pine-info@cac.washington.edu Mon Oct 3 20:19:31 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13367; Mon, 3 Oct 94 20:19:31 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10195; Mon, 3 Oct 94 20:16:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10188; Mon, 3 Oct 94 20:15:59 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs04l-00000AC; Mon, 3 Oct 94 19:57 PDT To: pine-info@cac.washington.edu From: noel@wfu.edu (Noel Hunter) Subject: Re: How do I download to my PC? Date: 4 Oct 1994 02:44:14 GMT Message-Id: <36qfhu$meq@eis.wfunet.wfu.edu> References: <36d6q9$33r@pipe4.pipeline.com> Try using the new ansi printing feature to "print" messages to your terminal program. If you configure the terminal program printer to print to a file... you can essentially "download" on the fly. -- * Noel Hunter, Academic Systems Administrator, Wake Forest University * * email: noel@wfu.edu http://www.wfu.edu/~noel * From owner-pine-info@cac.washington.edu Mon Oct 3 20:19:41 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13388; Mon, 3 Oct 94 20:19:41 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15301; Mon, 3 Oct 94 20:16:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15295; Mon, 3 Oct 94 20:16:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs04m-00000HC; Mon, 3 Oct 94 19:58 PDT To: pine-info@cac.washington.edu From: noel@wfu.edu (Noel Hunter) Subject: Re: [Q] Problem running PINE in a HPTERM Date: 4 Oct 1994 02:46:29 GMT Message-Id: <36qfm5$meq@eis.wfunet.wfu.edu> References: Urs Kradolfer (kradi@seismo.ifg.ethz.ch) wrote: : Dear colleagues, : scanning through the last 2 weeks of messages in the news-group : comp.mail.pine did not give me an answer to my queston, which is: : - running 'pine' in a hp-terminal (workstation HP/9000 series) using : TERM either 'hp' of 'hpterm' causes problems with the position of the : cursor and the 'highlighted text' in menus. : does anyone know a solution? on a vt100-terminal (or xterm) pine runs GREAT! Many hp terminals can do ansi or vt100 emulation. We send the escape sequence to switch to ansi mode beroe launching pine, then switch back after exiting. Sophisticated users may prefer to switch manually. -- * Noel Hunter, Academic Systems Administrator, Wake Forest University * * email: noel@wfu.edu http://www.wfu.edu/~noel * From owner-pine-info@cac.washington.edu Mon Oct 3 21:09:19 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14637; Mon, 3 Oct 94 21:09:19 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10982; Mon, 3 Oct 94 21:06:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10976; Mon, 3 Oct 94 21:06:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs0r9-00000AC; Mon, 3 Oct 94 20:47 PDT To: pine-info@cac.washington.edu From: Urs Kradolfer Subject: [Q] Problem running PINE in a HPTERM Date: Tue, 4 Oct 1994 01:31:36 +0100 (MEZ) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear colleagues, scanning through the last 2 weeks of messages in the news-group comp.mail.pine did not give me an answer to my queston, which is: - running 'pine' in a hp-terminal (workstation HP/9000 series) using TERM either 'hp' of 'hpterm' causes problems with the position of the cursor and the 'highlighted text' in menus. does anyone know a solution? on a vt100-terminal (or xterm) pine runs GREAT! Thanks for your help, Urs Kradolfer, Switzerland From owner-pine-info@cac.washington.edu Mon Oct 3 21:09:26 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14663; Mon, 3 Oct 94 21:09:26 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16093; Mon, 3 Oct 94 21:06:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16087; Mon, 3 Oct 94 21:06:07 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs0rC-00000IC; Mon, 3 Oct 94 20:48 PDT To: pine-info@cac.washington.edu From: Urs Kradolfer Subject: [Q] pine and 80 characters per line Date: Tue, 4 Oct 1994 01:35:14 +0100 (MEZ) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thinking 'pine' is a great tool (really!), I was somewhat disappointed that mails having 80 characters on some lines were truncated: although the used terminal/window had 80 characters per line, lines with 80 characters were truncated to a next line... Does anyone have a solution on how to overcome this problem? by the way: 'elm' does not have this problem... Best regards and thanks for any response, Urs From owner-pine-info@cac.washington.edu Tue Oct 4 00:40:47 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18939; Tue, 4 Oct 94 00:40:47 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13647; Tue, 4 Oct 94 00:36:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13641; Tue, 4 Oct 94 00:36:38 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs49S-00000nC; Tue, 4 Oct 94 00:19 PDT To: pine-info@cac.washington.edu From: Ken Weaverling Subject: Bug In Pine, hopping between newsgroups Date: Mon, 3 Oct 1994 23:16:32 -0400 (EDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: A user of mine reported a bug in pine. I've been able to reproduce the bug sucessfully on a D-G and a SV4 build (latter being on a Solaris system). I have been able to reproduce the bug by doing the following: LIST Folders Open news collection Goto (G command) to a specific group name Delete a few articles List folders (L command) Open news collection G specific group name Top status line still says old group line Bottom status line says Opening "new group name" Bombs with... Bug in Pine detected: "Received abort signal". Exiting pine. > Ken, I have noticed, especially today in going through the newsgroups > that as I use the Go To Command (it usually happens after the first GoTo) > that I get a "Bug in Pine Detected. Aborting Pine. and then I am sent > back to the shell prompt. Is this something that I am doing or is this a bug> > > Usually what happens is this. I will use GoTo and go to a newsgroup. I > will go down the list deleting the various posts. When I am finished, I > hit L for going back to the newsgroups, hit G for Goto again, type the > name of the newsgroup and then the above message appears and I find > myself at the shell prompt. > > From there, I can type Pine.New again; get back to the news groups; type > goto again, get to the first news group successfully; type L and goto > again, followed by the name of the newsgroup I want and then the bug > message again. From owner-pine-info@cac.washington.edu Tue Oct 4 05:41:07 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26399; Tue, 4 Oct 94 05:41:07 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23084; Tue, 4 Oct 94 05:27:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23078; Tue, 4 Oct 94 05:27:00 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs8h3-00000YC; Tue, 4 Oct 94 05:10 PDT To: pine-info@cac.washington.edu From: sadistic@yar.cs.wisc.edu (Beelzebub Belial) Subject: Can I Pnews through any mail program? Date: 4 Oct 1994 03:27:53 GMT Message-Id: <36qi3p$en5@spool.cs.wisc.edu> Hi all netters, I have a question, can I Pnews through any mail programs? (e.g. elm, pine...) Any help will be appreciated! Thanx very much! Beelzebub Belial. From owner-pine-info@cac.washington.edu Tue Oct 4 05:49:32 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26525; Tue, 4 Oct 94 05:49:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17847; Tue, 4 Oct 94 05:38:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17841; Tue, 4 Oct 94 05:38:12 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs8mr-00000iC; Tue, 4 Oct 94 05:16 PDT To: pine-info@cac.washington.edu From: snurmela@utu.fi (Sami Tapani Nurmela) Subject: PC-Pine 3.90 won't send mail: problem found Message-Id: Date: Tue, 4 Oct 1994 07:14:48 GMT A while ago I wondered why my updated PC-Pine 3.90 (with FTP Software's PC/TCP 2.31) won't send mail. After contacting my system management, we were able to locate the problem why PC-Pine 3.90 cannot contact our SMTP server (Zmailer). >From the log of our SMTP-server when I tried to send mail: 24682r HELO [ëN] 24682w 500- ^ 24682w 500 Illegal input characters: 8-bit char on SMTP input So, is this a bug in Pine ? Or is it just our server being too picky ? -- Sami Nurmela - snurmela@utu.fi From owner-pine-info@cac.washington.edu Tue Oct 4 05:50:04 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26546; Tue, 4 Oct 94 05:50:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23233; Tue, 4 Oct 94 05:38:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23221; Tue, 4 Oct 94 05:38:20 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs8pE-00000bC; Tue, 4 Oct 94 05:18 PDT To: pine-info@cac.washington.edu From: robbee@crl.com (Rob Bidleman) Subject: Folder Config Date: 4 Oct 1994 00:23:39 -0700 Message-Id: <36qvtr$i3d@crl3.crl.com> I have seen this thread before without an answer. I belong to a very busy list and receive close to 100 posts a day from it. I attempted to have it filtered to a folder but -- no go. Someone said earlier that it was not possible but I have seen it done by others without scripts or additional software. Huh? Robbee ---------------------------------------------===robbee@crl.com===---------- From owner-pine-info@cac.washington.edu Tue Oct 4 06:02:40 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26813; Tue, 4 Oct 94 06:02:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18027; Tue, 4 Oct 94 05:52:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18021; Tue, 4 Oct 94 05:52:20 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs92X-00000YC; Tue, 4 Oct 94 05:32 PDT To: pine-info@cac.washington.edu From: cormack@fisonssurf.co.uk (Alec Cormack) Subject: Re: Pine manual Date: 4 Oct 1994 07:50:29 GMT Message-Id: <36r1g5$7a4@netserver.fisonssurf.co.uk> References: <36cmf6$1jfb@unix1.sncc.lsu.edu> In article <36cmf6$1jfb@unix1.sncc.lsu.edu>, hammer@unix1.sncc.lsu.edu (John Edgar Johnston) says: > >I'm a new user of pine, and am impressed with it so far, but I need to >get a manual so that I can figure out how to set the options in my >.pinerc file (LSU's pine doesn't support the setup options method). Can >someone let me know where to FTP or buy a manual from? Thanks. > >John E. Johnston III >U.S. Civil War Center >Louisiana State University Try FTPing to ftp.cac.washington.edu and looking in /pine/docs directory Alec Cormack MIS Manager, Fisons Surface Science email: acormack@surface.fisons.co.uk Tel: +44 (0)1342 327211 Fax: +44 (0)1342 315074 From owner-pine-info@cac.washington.edu Tue Oct 4 06:13:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27059; Tue, 4 Oct 94 06:13:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23609; Tue, 4 Oct 94 06:07:07 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23603; Tue, 4 Oct 94 06:07:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs9GP-00000fC; Tue, 4 Oct 94 05:46 PDT To: pine-info@cac.washington.edu From: francis@moe.ac.sg (Francis Ho) Subject: Registered Mail? Date: 4 Oct 1994 06:11:45 GMT Message-Id: <36qrn1$60b@piaget.moe.ac.sg> Is it possible to send REGISTERED mail in pine or for that matter in unix? -- Francis Ho Internet: francis@moe.ac.sg Education Data Centre, MOE Tel : (65) - 4713949 " Doing without thinking, is as good as thinking without doing " From owner-pine-info@cac.washington.edu Tue Oct 4 06:56:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28206; Tue, 4 Oct 94 06:56:10 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18853; Tue, 4 Oct 94 06:47:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18847; Tue, 4 Oct 94 06:47:23 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qs9uH-00000fC; Tue, 4 Oct 94 06:27 PDT To: pine-info@cac.washington.edu From: guimond@IRO.UMontreal.CA (Alexandre Guimond) Subject: saved-msg-name-rule Message-Id: Date: Tue, 4 Oct 1994 12:08:11 GMT Hello, Just wondering if it is possible to put a the file-name instead of the options specified. I'd like to put something like: saved-msg-name-rule=saved instead of saved-msg-name-rule=default-folder that saves to saved-messages. The thing is I automatically save all my read mail in saved but with the s command I have to specify a name each time because I can't ``redefine'' default-folder. thanks. -- - Alex From owner-pine-info@cac.washington.edu Tue Oct 4 08:07:07 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00484; Tue, 4 Oct 94 08:07:07 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25407; Tue, 4 Oct 94 08:01:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from uvaarpa.Virginia.EDU by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25401; Tue, 4 Oct 94 08:01:08 -0700 Received: from elvis.med.virginia.edu by uvaarpa.virginia.edu id aa03254; 4 Oct 94 11:01 EDT Received: by elvis.med.Virginia.EDU (5.65c/1.34) id AA25138; Tue, 4 Oct 1994 11:01:01 -0400 Date: Tue, 4 Oct 1994 11:01:01 -0400 (EDT) From: "Steven D. Majewski" X-Sender: sdm7g@elvis.med.Virginia.EDU To: Rob Bidleman Cc: pine-info@cac.washington.edu Subject: Re: Folder Config In-Reply-To: <36qvtr$i3d@crl3.crl.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 4 Oct 1994, Rob Bidleman wrote: > I have seen this thread before without an answer. I belong to a very busy > list and receive close to 100 posts a day from it. I attempted to have it > filtered to a folder but -- no go. Someone said earlier that it was not > possible but I have seen it done by others without scripts or additional > software. Huh? > It's possible, but just not possible with Pine alone, which is the Mail User Agent, and has no control over delivery. There are several programs, filter (part of the elm distribution), procmail, deliver, and others that can do delivery filtering for you. Some of them can be run, installed as root, as a partial replacement for sendmail, but most can be run unpriviledged by a single user by using the .forward file to direct all mail to this filtering program. The feature that Pine has that makes it useful when used with a delivery filter, but which often confuses people into thinking that it can do that filtering, is the ability to be configured to notify you of new mail delivered to a set of several folders other than the default INBOX. So, if you have some mail redirected to another folder, you will still get a new-mail from ... message. If you don't need *delivery* filtering, mush, and the latest version of Pine (also probably MH, and others I'm not familiar with) both let you apply a command to a whole series of messages. For example, in Pine you can select all messages addressed To: a particular mailing list, and then either Zoom in on them ( show only those messages in the display ) or Apply a Save to another folder command to them. ) -- Steve Majewski (804-982-0831) -- -- UVA Department of Molecular Physiology and Biological Physics -- -- Box 449 Health Science Center Charlottesville,VA 22908 -- [ "Cheese is more macho?" ] From owner-pine-info@cac.washington.edu Tue Oct 4 08:27:39 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01216; Tue, 4 Oct 94 08:27:39 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25857; Tue, 4 Oct 94 08:22:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25851; Tue, 4 Oct 94 08:22:13 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsBPG-00000VC; Tue, 4 Oct 94 08:03 PDT To: pine-info@cac.washington.edu From: melander@msus1.moorhead.msus.edu (eRikmELanDeR) Subject: pine 3.89 support PGP? Message-Id: <1994Oct3.231541.2265@msus1.msus.edu> Date: 3 Oct 94 23:15:41 -0500 Does PINE version 3.89 support PGP data encryption? If so, how would one go about installing the program to encrypt mail "on the fly"? If PINE version 3.89 does not support PGP data encryption, does version 3.90 or do I have to wait for later versions to receive PGP support? Please reply either via e-mail or post. If you choose e-mail my mailing address is: melander@mhd1.moorhead.msus.edu Thanks in advance. EEM M From owner-pine-info@cac.washington.edu Tue Oct 4 08:41:36 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01972; Tue, 4 Oct 94 08:41:36 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26167; Tue, 4 Oct 94 08:35:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26161; Tue, 4 Oct 94 08:35:47 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17530; Tue, 4 Oct 94 08:35:41 -0700 Date: Tue, 4 Oct 1994 08:35:40 -0700 (PDT) From: Terry Gray To: "Steven D. Majewski" Cc: Rob Bidleman , pine-info@cac.washington.edu Subject: Re: Folder Config In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > The feature that Pine has that makes it useful when used with a > delivery filter, but which often confuses people into thinking > that it can do that filtering, is the ability to be configured > to notify you of new mail delivered to a set of several folders > other than the default INBOX. So, if you have some mail redirected > to another folder, you will still get a new-mail from ... message. Steve et al: This isn't quite correct. Due to performance concerns, Pine only keeps the "current" and "inbox" folders open, so those are the only two you will get "immediate" (i.e. within 2.5 min) new mail notification in. In the future we will be investigating ways to improve this. For now, I think the main virtue of Pine's "Incoming Msg folders" is that you can press TAB at the end of the Index and Pine will see if there are any Recent messages in each of the listed folders. This *reduces* the "out of sight, out of mind" problem that delivery to multiple folders sometimes causes. -teg From owner-pine-info@cac.washington.edu Tue Oct 4 08:52:44 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02358; Tue, 4 Oct 94 08:52:44 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21002; Tue, 4 Oct 94 08:44:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20996; Tue, 4 Oct 94 08:44:37 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA15974; Tue, 4 Oct 1994 11:41:29 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA17951; Tue, 4 Oct 94 10:44:33 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA00500; Tue, 4 Oct 94 10:44:33 CDT Date: Tue, 4 Oct 1994 10:44:32 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: Alexandre Guimond Cc: pine-info@cac.washington.edu Subject: Re: saved-msg-name-rule In-Reply-To: Message-Id: Organization: Teradyne Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1381 On Tue, 4 Oct 1994, Alexandre Guimond wrote: > Hello, > > Just wondering if it is possible to put a the file-name instead of the > options specified. I'd like to put something like: > > saved-msg-name-rule=saved > > instead of > > saved-msg-name-rule=default-folder I am guessing, but I don't think the above will work. (Maybe if you edit .pinerc directly, but I have my doubts.) > > that saves to saved-messages. The thing is I automatically save all my > read mail in saved but with the s command I have to specify a name each > time because I can't ``redefine'' default-folder. > I don't know if this is acceptable or not, but you could try setting 'read-message-folder'. This saves all read messages into a folder and can be done automatically. For more info, go to the configuration screen and press F1. --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Tue Oct 4 08:57:03 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02573; Tue, 4 Oct 94 08:57:03 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26497; Tue, 4 Oct 94 08:52:13 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from saguenay.IRO.UMontreal.CA by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26491; Tue, 4 Oct 94 08:52:10 -0700 Received: from brisay.IRO.UMontreal.CA by saguenay.IRO.UMontreal.CA (8.6.9) with ESMTP id LAA16057; Tue, 4 Oct 1994 11:52:03 -0400 Date: Tue, 4 Oct 1994 11:52:00 -0400 (EDT) From: guimond@IRO.UMontreal.CA Subject: Re: saved-msg-name-rule To: kenny@ttd.teradyne.com Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 4 Oct 1994 kenny@ttd.teradyne.com wrote: > I don't know if this is acceptable or not, but you could try setting > 'read-message-folder'. This saves all read messages into a folder and > can be done automatically. I've done this to automaticly save my read messages to my ``saved'' folder. But if I try to use the S command, it saves to ``saved-messages'' and not to ``saved''. Thanks for the help thought. - Alex From owner-pine-info@cac.washington.edu Tue Oct 4 08:57:21 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02598; Tue, 4 Oct 94 08:57:21 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21206; Tue, 4 Oct 94 08:52:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21200; Tue, 4 Oct 94 08:52:18 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsBrn-00000AC; Tue, 4 Oct 94 08:33 PDT To: pine-info@cac.washington.edu From: chapmand@candu.aecl.ca (Dawn Chapman) Subject: Re: Can I Pnews through any mail program? Date: 4 Oct 1994 13:36:17 GMT Message-Id: <36rloh$b3f@newton.candu.aecl.ca> References: <36qi3p$en5@spool.cs.wisc.edu> Beelzebub Belial (sadistic@yar.cs.wisc.edu) wrote: : Hi all netters, : I have a question, can I Pnews through any mail programs? : (e.g. elm, pine...) : Any help will be appreciated! : Thanx very much! : : Beelzebub Belial. -- Dawn Chapman UNIX System Support (905)823-9060 x2087 email: chapmand@candu.aecl.ca From owner-pine-info@cac.washington.edu Tue Oct 4 09:27:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04760; Tue, 4 Oct 94 09:27:05 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27275; Tue, 4 Oct 94 09:18:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27269; Tue, 4 Oct 94 09:18:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsCGv-00000NC; Tue, 4 Oct 94 08:59 PDT To: pine-info@cac.washington.edu From: mmord@batman.bmd.trw.com Subject: Re: MIME Message-Id: <1994Oct4.093846.670@batman> Date: 4 Oct 94 09:38:46 MST References: In article , whist@crl.com (Ann Whitehead) writes: > When I send files by Pine they arrive in MIME and receivers of my mail > need a way to decode them. Is there any simple MIME software to which > you could refer me so files I send via Pine could be translated by my > relatively non-technical friends? Suggestions would be much appreciated! > Thanks. Ann Whitehead > I have the same frustrating problem. I read the faq and pulled down mpak for the mac and it kinda seems to works sometimes..when sending mail to my work address but now I've lost the site with all that stuff and I have friends dos/windoze types who need mpak or similar so we can send attached files. Please, somebody help us, Please! Many thanks, Bret From owner-pine-info@cac.washington.edu Tue Oct 4 09:40:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05324; Tue, 4 Oct 94 09:40:02 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27615; Tue, 4 Oct 94 09:34:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27609; Tue, 4 Oct 94 09:34:22 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsCU1-00000MC; Tue, 4 Oct 94 09:12 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Spool mail in BSDI Date: Tue, 4 Oct 1994 08:58:29 -0700 Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: Pine-use is a standalone utility to check on Pine usage and is not compiled into Pine itself. The place you need to make the change is in c-client (imap/ANSI/c-client/os_bsi.h)... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 3 Oct 1994, Anto Daryanto wrote: > Hi, > I have compiled Pine 3.90 for BSDI v1.1. With default configuration pine > can not see user mail spool. The mail spool directory is in /usr/var/mail. > So I've made a change in pine/pine-use.c to reflect the machine user mail > spool directory. But still, pine can't see spool directory. > > Any idea? > -anto > > =============================================================== > | Antonius Daryanto | Direktorat TEI OS/2 | > | a.daryanto@inn.bppt.go.id | BPPT Teknologi & | > | | Jakarta, INDONESIA Linux | > =============================================================== > disclaimer: > My opinion does not represent my employer's opinion > > > > > From owner-pine-info@cac.washington.edu Tue Oct 4 09:40:35 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05353; Tue, 4 Oct 94 09:40:35 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22402; Tue, 4 Oct 94 09:34:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22396; Tue, 4 Oct 94 09:34:16 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsCTu-00000AC; Tue, 4 Oct 94 09:12 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: HEADERS: Activating ^T Date: Tue, 4 Oct 1994 08:53:56 -0700 Message-Id: References: <36qcki$gsc@msuinfo.cl.msu.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36qcki$gsc@msuinfo.cl.msu.edu> Why don't you just use Bcc? |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 4 Oct 1994, Todd E. Van Hoosear wrote: > > pine390-DocServer@docserver.cac.washington.edu told me: > > > o You can now control which headers show up by default in the composer. > > This is done by using the Setup/Config screen to set the > > "default-composer-hdrs" option. You would specify a list of headers > > you wish to be visible immediately when you enter the Composer. Other > > headers are still accessible via the "^R Rich Header" command. > > Is there any way to activate your address book (using ^T) on a header > line that you have custom created? (I have a long personal mailing list > that I would rather keep local and not stick into /etc/sendmail/aliases > but I _don't_ want people to have to flip through pages of headers if > they've a decent mail program. So I added a custom line "Apparently To:" > that works fine except for the address book.) Any suggestions, comments > would be very welcome! > > Thanks, > > - Todd > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > - T o d d E. V a n H o o s e a r - > ``'''vanhoose@gdl.msu.edu - vanhoose@msu.edu - vanhoose@sparhawk.cl.msu.edu > (._.) Michigan State University - East Lansing, MI USA > (_) Computer Laboratory - Department of Communication > `---' My Home Page > PGP-aware: finger vanhoose@gdl.msu.edu for my public key > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > From owner-pine-info@cac.washington.edu Tue Oct 4 09:50:06 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05994; Tue, 4 Oct 94 09:50:06 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22583; Tue, 4 Oct 94 09:42:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22577; Tue, 4 Oct 94 09:42:20 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsCdw-00000QC; Tue, 4 Oct 94 09:23 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: PC-Pine 3.90 won't send mail: problem found Date: Tue, 4 Oct 1994 09:08:02 -0700 Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE In-Reply-To: Well, I'm not sure whose bug this is... PC/TCP is returning garbage on som= e versions and we have not found all of the workarounds to make it work consistently :( Pine 3.91 will atleast have a filter to prevent the 8bit characters, but it still may not work completely as we would like...=20 |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 4 Oct 1994, Sami Tapani Nurmela wrote: > A while ago I wondered why my updated PC-Pine 3.90 (with FTP Software's= =20 > PC/TCP 2.31) won't send mail. After contacting my system management, we > were able to locate the problem why PC-Pine 3.90 cannot contact our SMTP > server (Zmailer). >=20 > From the log of our SMTP-server when I tried to send mail: > 24682r HELO [=EBN] > 24682w 500- ^ > 24682w 500 Illegal input characters: 8-bit char on SMTP input >=20 > So, is this a bug in Pine ? Or is it just our server being too picky ? > -- > Sami Nurmela - snurmela@utu.fi >=20 >=20 From owner-pine-info@cac.washington.edu Tue Oct 4 11:20:27 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09721; Tue, 4 Oct 94 11:20:27 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29907; Tue, 4 Oct 94 11:12:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29901; Tue, 4 Oct 94 11:12:36 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsE2J-00000WC; Tue, 4 Oct 94 10:52 PDT To: pine-info@cac.washington.edu From: kjetil@troll.eee.strath.ac.uk (Kjetil Rossavik) Subject: /usr/bin/uuname: No such file or directory Date: 04 Oct 1994 10:34:35 GMT Message-Id: Hi, When I am trying to email to certain addresses, my machine (running Linux) complains that: Command: /bin/sh: /usr/bin/uuname: No such file or directory sendmail: etoib@etobi.eua.ericsson.se ... deferred: (ERR_127) router uucp_neighbors: command `/usr/bin/uuname' returned exit status EX_32256 sendmail: mail moved to /var/spool/smail/error/0qs74C-0001fmC Am I missing a file? Why doesn't this happen every time I mail something? Regards, Kjetil. -- Kjetil Rossavik Tel. +44-41-552 4400 Signal Processing Division ext. 2686 Dept. of Electronic and Electrical Eng. Fax +44-41-552 2487 University of Strathclyde Glasgow G1 1XQ From owner-pine-info@cac.washington.edu Tue Oct 4 11:20:30 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09727; Tue, 4 Oct 94 11:20:30 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24709; Tue, 4 Oct 94 11:12:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24702; Tue, 4 Oct 94 11:12:48 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsE30-00000aC; Tue, 4 Oct 94 10:53 PDT To: pine-info@cac.washington.edu From: dlfoster@vespucci.iquest.com (Dayna Foster) Subject: Editing Headers in Reply Date: 4 Oct 1994 17:21:43 GMT Message-Id: <36s2v7$i6u@polo.iquest.com> How do I edit the header when I reply to a message if I want to add addressees? I have checked the on-line help and the printed information I have and cannot find the answer in either place. Thanks! Dayna Foster From owner-pine-info@cac.washington.edu Tue Oct 4 11:44:11 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10993; Tue, 4 Oct 94 11:44:11 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25263; Tue, 4 Oct 94 11:35:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25255; Tue, 4 Oct 94 11:35:38 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23502; Tue, 4 Oct 94 11:35:29 -0700 Date: Tue, 4 Oct 1994 11:35:28 -0700 (PDT) From: Terry Gray To: mmord@batman.bmd.trw.com Cc: pine-info@cac.washington.edu Subject: Re: MIME In-Reply-To: <1994Oct4.093846.670@batman> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've excerpted a MIME doc we have around here that contains the following pointer: There are a number of stand-alone programs that can interpret a MIME message. One of the more versatile is called "munpack". It was developed at Carnegie Mellon University and is available via anonymous FTP from the host ftp.andrew.cmu.edu in the directory pub/mpack/. There are versions available for Unix, PC, Mac and Amiga systems. For compabibility with older forms of transferring binary files, the munpack program can also decode messages in split-uuencoded format. See the FAQ on comp.mail.mime for other alternatives. -teg On 4 Oct 1994 mmord@batman.bmd.trw.com wrote: > In article , whist@crl.com (Ann Whitehead) writes: > > When I send files by Pine they arrive in MIME and receivers of my mail > > need a way to decode them. Is there any simple MIME software to which > > you could refer me so files I send via Pine could be translated by my > > relatively non-technical friends? Suggestions would be much appreciated! > > Thanks. Ann Whitehead > > > > I have the same frustrating problem. I read the faq and pulled down > mpak for the mac and it kinda seems to works sometimes..when sending > mail to my work address but now I've lost the site with all that > stuff and I have friends dos/windoze types who need mpak or similar > so we can send attached files. > Please, somebody help us, Please! > Many thanks, > Bret > From owner-pine-info@cac.washington.edu Tue Oct 4 12:09:37 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12367; Tue, 4 Oct 94 12:09:37 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01262; Tue, 4 Oct 94 12:02:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01255; Tue, 4 Oct 94 12:02:36 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsEoI-00000AC; Tue, 4 Oct 94 11:41 PDT To: pine-info@cac.washington.edu From: vanhoose@cl-next4.cl.msu.edu (Todd E. Van Hoosear) Subject: Re: HEADERS: Activating ^T Date: 4 Oct 1994 18:25:58 GMT Message-Id: <36s6nm$ooo@msuinfo.cl.msu.edu> References: <36qcki$gsc@msuinfo.cl.msu.edu> On Tue, 4 Oct 1994 08:53:56 -0700, David L Miller (dlm@cac.washington.edu) wrote: : Why don't you just use Bcc? I wouldn't mind using it, but I would still like people to be able to see the whole list if they _want_ to. - Todd -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - T o d d E. V a n H o o s e a r - ``'''vanhoose@gdl.msu.edu - vanhoose@msu.edu - vanhoose@sparhawk.cl.msu.edu (._.) Michigan State University - East Lansing, MI USA (_) Computer Laboratory - Department of Communication `---' My Home Page PGP-aware: finger vanhoose@gdl.msu.edu for my public key ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Tue Oct 4 12:14:11 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12497; Tue, 4 Oct 94 12:14:11 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26106; Tue, 4 Oct 94 12:06:34 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from jade.saintmarys.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26100; Tue, 4 Oct 94 12:06:32 -0700 Received: by jade.saintmarys.edu (1.37.109.11/16.2) id AA257977832; Tue, 4 Oct 1994 14:10:32 -0500 Date: Tue, 4 Oct 1994 14:10:31 -0500 (EST) From: Dan Mandell To: "pine-info@cac.washington.edu" Subject: unintelligible letter from russia (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: BASE64 SSBoYXZlIHNlZW4gZGlzY3Vzc2lvbnMgb2YgYWx0ZXJuYXRlIGNoYXJhY3Rl ciBzZXRzLCBidXQgaGF2ZSBuZXZlciANCmVuY291bnRlcmVkIGFueXRoaW5n IGJ1dCBzdHJhaWdodCBhc2NpaSwgdW50aWwgdGhpcyBtZXNzYWdlIGFycml2 ZWQgZnJvbSANCnNvbWV3aGVyZSBpbiBSdXNzaWEuLi4NCg0KQW55IHN1Z2dl c3Rpb25zPw0KDQpEYW4NCiAtLQ0KPT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PQ0KRGFuIE1hbmRlbGwsIENvbXB1dGVyIFNlcnZpY2Vz LCBTYWludCBNYXJ5J3MgQ29sbGVnZSAgICAgIA0KSW50ZXJuZXQ6IGRtYW5k ZWxsQHNhaW50bWFyeXMuZWR1DQoNCiJPdGhlcnMgcHJvbWlzZSB5b3UgdGhl IFdvcmxkLiBXZSBkZWxpdmVyISI6ICBOZXcgWW9yayBUaW1lcw0KDQoNCg0K 7ef1LCDo6e3m4essIOvBxsXE0sEgxsnayd7F08vPyiDIyc3JyQ0Kyy7ILs4u 8+Hm7+7v9/Ug9y7hLg0KICAgICAgICAgICAgIPXXwdbBxc3ZyiD3ycvUz9Ig 4czFy9PFxdfJ3iwNCiAgICAgICDQ0s/Tyc0g0M/E1NfF0sTJ1Ngg98HbxSDT z8fMwdPJxSDC2dTYIM/Q0M/Oxc7Uz80NCtDPIMTJ09PF0tTBw8nJIOvV3tXL wsHF18Eg6C7nLi73xdLP0dTOz8Ug19LFzdEg2sHdydTZIC0NCtMgMjQuMTAg 0M8gMTQuMTEgMTk5NCDHz8TBLiDzz8/C3cnUxSzQz9bBzNXK09TBLMvBy8nF IMTOyQ0KxMzRIPfB0yDCz8zFxSDVxM/CztkuIPDSz9PJzSD3wdMg08/Pwt3J 1NggzsHNINfB28k6DQrV3sXO1cAg09TF0MXO2Cwg1d7Fzs/FINrXwc7JxSwg xM/M1s7P09TYLCDBxNLF0y4NCiAgICAgICDkydPTxdLUwcPJwCDQ0snXxdrF zSDXIMvPzsPFINPFztTRwtLRwA0KICAgICAgIPrB0sHOxcUgwszBx8/EwdLJ zSwNCiAgICAgICDzINXXwdbFzsnFzSwg69Xe1cvCwcXXIOgu5y4NCiAgICAg ICBlLW1haWwgYWRkcmVzczogYWJhc2hldkBuc2lwc3UucGVybS5zdQ0KDQo= From owner-pine-info@cac.washington.edu Tue Oct 4 13:23:32 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15832; Tue, 4 Oct 94 13:23:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27786; Tue, 4 Oct 94 13:18:06 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27772; Tue, 4 Oct 94 13:17:56 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsG2H-00000LC; Tue, 4 Oct 94 13:00 PDT To: pine-info@cac.washington.edu From: dlinford@trance.helix.net (D. Linford) Subject: Re: WARNING FOR PINE 3.90 USERS!!!!! Date: 4 Oct 1994 12:17:21 -0700 Message-Id: <36s9o1$153@trance.helix.net> References: <368sbk$3mp@bushwire.apana.org.au> In article , R. Stewart Ellis wrote: > >Please make it configurable, and make the default to treat mail as private. >I can think of almost no case where it is appropriate to post back to news >something that I have received in private mail. There many times when someone posts a message to a group which they don't follow. They request responses via email. Many times it would be appropriate to initially send to the newsgroup as well. I wonder if the problems is that there is insuficient information in the headers for the pine to determine if the message was posted, as well as mailed. d -- ---- D.Linford ----- Van.BC ---- ---- dlinford@helix.net -------- From owner-pine-info@cac.washington.edu Tue Oct 4 13:59:45 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17535; Tue, 4 Oct 94 13:59:45 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03950; Tue, 4 Oct 94 13:54:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03944; Tue, 4 Oct 94 13:54:13 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsGYF-00000NC; Tue, 4 Oct 94 13:33 PDT To: pine-info@cac.washington.edu From: tkraft@teleport.com (Tim Kraft) Subject: MIME Date: 4 Oct 1994 13:20:51 -0700 Message-Id: <36sdf3$kgk@linda.teleport.com> >I've excerpted a MIME doc we have around here that contains the following >pointer: > > There are a number of stand-alone programs that can interpret a MIME > message. One of the more versatile is called "munpack". It was developed > at Carnegie Mellon University and is available via anonymous FTP from the > host ftp.andrew.cmu.edu in the directory pub/mpack/. I don't know what the problem is, but I haven't been able to get Munpack to decode any attached messages sent with Pine. Munpack gives me the message "Nothing to unpack." Yet when I look at the file with a text editor it says it's encoded with the MIME format. Anyone know what the problem is?? -- _____ | TBK |_______________ | tkraft@teleport.com | ----------------------- -- _____ | TBK |_______________ | tkraft@teleport.com | ----------------------- From owner-pine-info@cac.washington.edu Tue Oct 4 14:00:06 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17591; Tue, 4 Oct 94 14:00:06 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28480; Tue, 4 Oct 94 13:54:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28474; Tue, 4 Oct 94 13:54:18 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsGYR-00000OC; Tue, 4 Oct 94 13:33 PDT To: pine-info@cac.washington.edu From: morrowd@candu.aecl.ca (Dave Morrow) Subject: Full Name in Pine 3.90 Date: 4 Oct 1994 18:53:16 GMT Message-Id: <36s8as$flc@newton.candu.aecl.ca> Why does Pine 3.90 not always pull the full name of a user from /etc/passwd? -- David A. Morrow AECL Candu Tel: (905) 823-9060 Fax: 823-2302 Email: morrowd@candu.aecl.ca From owner-pine-info@cac.washington.edu Tue Oct 4 14:02:19 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17752; Tue, 4 Oct 94 14:02:19 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04032; Tue, 4 Oct 94 13:57:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04026; Tue, 4 Oct 94 13:57:56 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsGct-00000PC; Tue, 4 Oct 94 13:38 PDT To: pine-info@cac.washington.edu From: kamk@ccsun.tuke.sk (Kamil Kukura) Subject: Re: Disconnected use of wpine..??? Date: 4 Oct 1994 15:24:24 GMT Message-Id: <36rs38$3d6@ccnews.ke.sanet.sk> References: <35kl1a$t0f@jethro.Corp.Sun.COM> : Exactly this mode of operation is one of our goals, but we have quite a long : road to get there yet............. At compose mode; the pine could simply recognize it's not connected any longer and save the message into special a folder for instance TO_SEND This shouldn't be very hard. Worse is, how to process this folder as a dozens of waiting messages to be sent. As the format of folder is straightforward some third-party program could take over this job. -- -- Kamil.Kukura@tuke.sk -- -------------------- -- MIME, ISO-Latin-2 From owner-pine-info@cac.washington.edu Tue Oct 4 14:22:56 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18649; Tue, 4 Oct 94 14:22:56 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28989; Tue, 4 Oct 94 14:18:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28981; Tue, 4 Oct 94 14:18:29 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsGww-00000AC; Tue, 4 Oct 94 13:59 PDT To: pine-info@cac.washington.edu From: rkgupta@zeus.cac.washington.edu (Raman Gupta) Subject: Bug in pine? IOT Trap? Message-Id: Date: Tue, 4 Oct 1994 18:11:31 GMT I am using pine on a NeXT machine and am receiving the following error message when I try to exit from pine. Bug in Pine detected: "Received abort signal". Exiting pine. IOT trap This message only occurs when I have mail in my inbox. If I do not have any mail in my inbox (for example, if I have expunged it), the message still shows up the first time I exit pine, but then disappears if I go into and exit pine again. If I simply delete my messages without expunging them and then exit pine, and answer yes to the prompt "expunge messages?", I get the above error and my messages never get expunged. Can anyone help me? From owner-pine-info@cac.washington.edu Tue Oct 4 15:08:55 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20803; Tue, 4 Oct 94 15:08:55 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05607; Tue, 4 Oct 94 15:03:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05601; Tue, 4 Oct 94 15:03:01 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsHdJ-00000JC; Tue, 4 Oct 94 14:42 PDT To: pine-info@cac.washington.edu From: long@vax.ox.ac.uk (NEIL J LONG) Subject: pine3.90 and hpterm anyone? Message-Id: <1994Oct4.221408.26448@oxvaxd> Date: 4 Oct 94 22:14:08 BST Hello Has anyone got a diff to pine 3.90 so that it will work in a HP-UX hpterm window? It works for an xterm but the cursor keys are messed up - guess it is HP's curses that is the problem. Thanks Neil From owner-pine-info@cac.washington.edu Tue Oct 4 16:36:03 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24574; Tue, 4 Oct 94 16:36:03 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07622; Tue, 4 Oct 94 16:28:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07616; Tue, 4 Oct 94 16:28:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsIwz-00000BC; Tue, 4 Oct 94 16:07 PDT To: pine-info@cac.washington.edu From: lillqvis@cc.Helsinki.FI (Holger Lillqvist) Subject: Wanted: copy msg replied-to into buffer Date: 4 Oct 1994 14:25:27 GMT Message-Id: <36rokn$5p1@hybrid27.Helsinki.FI> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Many terminal programs allow you to scroll backwards in a screen buffer, and even copy material from the buffer. However, pine (unlike elm) does not copy the replied-to msg into buffer, so you can't glance at the msg, should you want to check something there while responding - or copy a detail from it etc. Is it possible to add such a feature in coming versions of pine? If not permanent, it could be an option you could choose in setup/configure. From owner-pine-info@cac.washington.edu Tue Oct 4 17:18:34 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26529; Tue, 4 Oct 94 17:18:34 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03345; Tue, 4 Oct 94 17:08:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03339; Tue, 4 Oct 94 17:08:27 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsJdm-00000BC; Tue, 4 Oct 94 16:51 PDT To: pine-info@cac.washington.edu From: ben@chinook.uoregon.edu (Ben Marcotte) Subject: Turn off pruning? (Fearing the end of each month) Date: 4 Oct 1994 23:23:31 GMT Message-Id: <36so5j$oec@pith.uoregon.edu> Is there a way to turn off the "feature" of monthly pruning- the process of pine asking you at the begining of each month: Disk space is limited. Delete "sent-mail-MMM-YYYY" ? I have looked through pine.conf, .pinerc, man pine and the help in Setup for any configuration or feature switch that might apply but I can find nothing. What am I missing? I find this to be the most agrivating part of an otherwise friendly program. Ben Marcotte ============================================================================== Ben Marcotte ben@chinook.uoregon.edu (503) 346-4592 ============================================================================== From owner-pine-info@cac.washington.edu Tue Oct 4 18:42:28 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28743; Tue, 4 Oct 94 18:42:28 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10256; Tue, 4 Oct 94 18:38:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10250; Tue, 4 Oct 94 18:38:26 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsL0q-00000AC; Tue, 4 Oct 94 18:19 PDT To: pine-info@cac.washington.edu From: latzer@aludra.usc.edu (Christina E. Latzer) Subject: Probably just FAQ, but....help me please?? Date: 4 Oct 1994 18:10:51 -0700 Message-Id: <36suer$4ig@aludra.usc.edu> Please forgive me if I've messed up or made other major errors, but this is the first time I've tried to post anything. What I'd like to know is if there is any way to save letters from pine to my hard drive instead of to the network, so that I can access the letters from my word processor. Conversely, I'd like to know how to send word processor files as part of my letters in pine. Thanks in advance. :) From owner-pine-info@cac.washington.edu Tue Oct 4 22:25:57 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03846; Tue, 4 Oct 94 22:25:57 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07967; Tue, 4 Oct 94 22:19:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07961; Tue, 4 Oct 94 22:19:02 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsORc-00000AC; Tue, 4 Oct 94 21:59 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: WARNING FOR PINE 3.90 USERS!!!!! Date: Tue, 4 Oct 1994 20:11:32 -0700 (PDT) Message-Id: References: <368sbk$3mp@bushwire.apana.org.au> <36s9o1$153@trance.helix.net> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36s9o1$153@trance.helix.net> It seems from discussions with other users that the problem is that some (many?) newsreaders supply too much information when replying via mail. That is, they include a Newsgroups: header even though the message was not posted to the newsgroup! Pine sees the Newsgroups: header and assumes that the message was posted as well as mailed. AFAIK, there is nothing that Pine can do to tell that the Newsgroups: header is a lie... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 4 Oct 1994, D. Linford wrote: > In article , > R. Stewart Ellis wrote: > > > >Please make it configurable, and make the default to treat mail as private. > >I can think of almost no case where it is appropriate to post back to news > >something that I have received in private mail. > > There many times when someone posts a message to a group which > they don't follow. They request responses via email. Many times it > would be appropriate to initially send to the newsgroup as well. I > wonder if the problems is that there is insuficient information in the > headers for the pine to determine if the message was posted, as well > as mailed. > > d > -- > ---- D.Linford ----- Van.BC ---- > ---- dlinford@helix.net -------- > > From owner-pine-info@cac.washington.edu Wed Oct 5 00:34:53 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06885; Wed, 5 Oct 94 00:34:53 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15572; Wed, 5 Oct 94 00:29:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15566; Wed, 5 Oct 94 00:29:48 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsQWi-00000BC; Wed, 5 Oct 94 00:12 PDT To: pine-info@cac.washington.edu From: galt@csulb.edu (Charles Galt) Subject: Folder Modification Time But... Date: 5 Oct 1994 07:12:10 GMT Message-Id: <36tjka$6bg@garuda.csulb.edu> I repeatedly get the msg *beep* [Folder modification time but apparently no changes] since we installed 3.90; any way to stop this? Thanks... chuck -- |~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| | Charles Galt, Professor Tel: 310-985-4808 | | Department of Biological Sciences Fax: 310-985-2315 | | California State University Internet: galt@csulb.edu | | 1250 Bellflower Boulevard Omnet: c.galt | | Long Beach, CA 90840-3702, USA Finger: galt@beach.csulb.edu| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-pine-info@cac.washington.edu Wed Oct 5 02:14:36 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09794; Wed, 5 Oct 94 02:14:36 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11366; Wed, 5 Oct 94 02:08:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11360; Wed, 5 Oct 94 02:08:35 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsRwr-00000AC; Wed, 5 Oct 94 01:43 PDT To: pine-info@cac.washington.edu From: sadistic@yar.cs.wisc.edu (Ah! My Goddess) Subject: === How to set nntp in .pinerc in order to read news? === Date: 5 Oct 1994 08:14:43 GMT Message-Id: <36tn9k$fi8@spool.cs.wisc.edu> Hi netters, Just wondering how to set up nntp server in the .pinerc in order to read and post news through the pine? Any help is being appreciated. Thanx very much! P.S. Please feel free to mail me directly. --------------------------------------------------------------------------- _||___ _||___ _||___ _||_ ||_ __||__ _||___ ||__ ||__ || : / :|| : || _||__ /||, \ /||, \ ===. || : ,||.+||-+ __|| _||__ ===. : ||, : ||, ) : \' || :||_: : : || : : \|/ / \|/ / --' / \ || || `---- \|' ' --' =========================================================================== kchan@mondrian.csufresno.edu sadistic@picard.cs.wisc.edu sadistic@yar.cs.wisc.edu --------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Wed Oct 5 03:16:09 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11181; Wed, 5 Oct 94 03:16:09 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17740; Wed, 5 Oct 94 03:09:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17728; Wed, 5 Oct 94 03:09:38 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsSyc-000008C; Wed, 5 Oct 94 02:49 PDT To: pine-info@cac.washington.edu From: chermesh@techunix.technion.ac.il (Chermesh Ran) Subject: Can't define fcc on pine PC Date: Wed, 5 Oct 1994 09:26:56 GMT Message-Id: Hi, All my efforts to define my fcc folder on my PC version of pine failed and I wonder why. I tried defining it on my pc, specifying default-fcc sentmail and on my remote unix machine by typing default-fcc: chermesh {bgumail.bgu.ac.il}sent_mail In both cases, the response I get is: CREATE failed: Can't create mailbox mail/savemail: no such file or directory Well, the problem is that both my sent_mail folder exists on my unix account and on my mail directory on my pc. Ran p.s. Funny as it may sound, the pc folders were operative on version 3.89 I've never tried the remote directory mode on 3.89. R.C. -- Ran Chermesh E - M A I L Behavioral Sciences Dept. =========== Ben-Gurion University Internet: CHERMESH@BGUVM.BGU.AC.IL Beer-Sheva 84105 CHERMESH@BGUMAIL.BGU.AC.IL Israel Bitnet : CHERMESH@BGUVM.BITNET Phone: 972-7-472-057 Fax: 972-7-232-766 URL: gopher://gopher.bgu.ac.il:70/00/Ben/res/hum/beh/CHERMESH%2c%20RAN From owner-pine-info@cac.washington.edu Wed Oct 5 06:12:11 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16799; Wed, 5 Oct 94 06:12:11 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14750; Wed, 5 Oct 94 06:05:21 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14738; Wed, 5 Oct 94 06:05:18 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA24829; Wed, 5 Oct 1994 09:02:10 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA19874; Wed, 5 Oct 94 08:05:16 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA00611; Wed, 5 Oct 94 08:05:15 CDT Date: Wed, 5 Oct 1994 08:05:14 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: Ah! My Goddess Cc: pine-info@cac.washington.edu Subject: Re: === How to set nntp in .pinerc in order to read news? === In-Reply-To: <36tn9k$fi8@spool.cs.wisc.edu> Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1238 On 5 Oct 1994, Ah! My Goddess wrote: > Hi netters, > Just wondering how to set up nntp server in the .pinerc in order to read and > post news through the pine? > Any help is being appreciated. Hi, You need to set these two lines in your .pinerc (either through editing or through the configuration screen. (One note: I think you only supply *{ttd1.ttd.teradyne.com/nntp}[] on the news-collection line and pine fills in the subscribed groups.) Also, to state the obvious, you must change ttd1.ttd.teradyne.com to whatever you nntp server is. nntp-server = ttd1.ttd.teradyne.com news-collections = Subscribed-Groups *{ttd1.ttd.teradyne.com/nntp}[] Hope this helps, --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Wed Oct 5 06:42:51 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17814; Wed, 5 Oct 94 06:42:51 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15150; Wed, 5 Oct 94 06:29:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15144; Wed, 5 Oct 94 06:29:00 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsW45-00000nC; Wed, 5 Oct 94 06:07 PDT To: pine-info@cac.washington.edu From: schliesk@sos.sos.net (Jay Schlieske) Subject: Re: Local News Only Possible with Pine3.90 under FreeBSD 1.1.5.1? Date: 5 Oct 1994 09:56:50 GMT Message-Id: <36tt92$3vj@cleese.nas.com> References: <36pk9n$etf@uuneo.neosoft.com> George Livsey (georgel@starbase.neosoft.com) wrote: : I have pine 3.90 installed on a box running FreeBSD 1.1.5.1 and I can : read the news just fine but cannot post. I am running c-news and only : have local news. Pine complains that it cannot find an nntp server. : I tried localhost and the host name to no avail. Is it possible to post : to local news only under Pine 3.90? I use pine3.90, can read and post to localhost with a port redirected to my remote nntpserver and works with a term connection. This is with Linux 1.1.50. Pine thinks it's posting to localhost, even in actuality, its not. This is due to the NNTPSERVER environment variable being set as localhost. Hope this helps. : George Livsey : georgel@starbase.neosoft.com -- schliesk@sos.sos.net - Jay o Jay Schlieske <#< " Above all.... have fun. " +*+ Credits: smartmail__>^>__by * Linux+Pine3.90+Smail+Term-2.1.4+PoP +*+ ---------- #include ------------------------------- From owner-pine-info@cac.washington.edu Wed Oct 5 06:43:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17841; Wed, 5 Oct 94 06:43:05 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20848; Wed, 5 Oct 94 06:30:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20842; Wed, 5 Oct 94 06:30:20 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsW8a-00000hC; Wed, 5 Oct 94 06:12 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: WARNING FOR PINE 3.90 USERS!!!!! Date: 4 Oct 1994 23:06:44 -0500 Message-Id: <36t8ok$n8h@mp.cs.niu.edu> References: <36s9o1$153@trance.helix.net> In David L Miller writes: >It seems from discussions with other users that the problem is that some >(many?) newsreaders supply too much information when replying via mail. That >is, they include a Newsgroups: header even though the message was not posted >to the newsgroup! This is not "too much information." The newsgroups header on email is informative, and what else is the purpose of information but to be informative. > Pine sees the Newsgroups: header and assumes that the >message was posted as well as mailed. Then Pine is stupid for making such an assumption. > AFAIK, there is nothing that Pine can >do to tell that the Newsgroups: header is a lie... The "Newsgroups:" header is not a lie. There is nothing in RFC822 which forbids a "Newsgroups:" header in email. The header informs the email recipient as to the origin of the discussion. From owner-pine-info@cac.washington.edu Wed Oct 5 06:51:03 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18079; Wed, 5 Oct 94 06:51:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15370; Wed, 5 Oct 94 06:40:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15364; Wed, 5 Oct 94 06:40:31 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsWHS-00001UC; Wed, 5 Oct 94 06:21 PDT To: pine-info@cac.washington.edu From: klau@falcon.cc.ukans.edu (Allan Jay Lau Kim Wah) Subject: Using Bcc Field In PINE 3.89 Message-Id: <1994Oct4.183454.74070@kuhub.cc.ukans.edu> Date: 4 Oct 94 18:34:54 CDT I have a problem using Bcc field to hide a list of addresses. When I tried to hide a few addresses, it worked okay. But when I tried to hide an extensive list of addresses, the list showed up in the receivers' mails. Can anyone tell me why and help me solve this problem? Need a fast answer. Thanks. From owner-pine-info@cac.washington.edu Wed Oct 5 07:07:44 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18635; Wed, 5 Oct 94 07:07:44 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15729; Wed, 5 Oct 94 07:00:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15723; Wed, 5 Oct 94 07:00:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsWck-00001BC; Wed, 5 Oct 94 06:43 PDT To: pine-info@cac.washington.edu From: pkean@gti.gti.net (Peter Kean) Subject: Pine/Pico question Date: 5 Oct 1994 07:03:05 -0400 Message-Id: <36u159$4k0@gti.gti.net> I have a couple of access accounts, but want all email replys to posts to come here. How can I change the return domain name in a usenet post using pico as my editor? Please email reply. From owner-pine-info@cac.washington.edu Wed Oct 5 07:07:49 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18653; Wed, 5 Oct 94 07:07:49 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21319; Wed, 5 Oct 94 06:59:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21309; Wed, 5 Oct 94 06:59:53 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsWPt-00000nC; Wed, 5 Oct 94 06:29 PDT To: pine-info@cac.washington.edu From: schliesk@sos.sos.net (Jay Schlieske) Subject: Re: 3.90 - possible bug in 'postpone' Date: 5 Oct 1994 10:48:17 GMT Message-Id: <36u09h$3vj@cleese.nas.com> References: <36i7fs$679@news.halcyon.com> Ralph Sims (ralphs@halcyon.halcyon.com) wrote: : Scenario: user starts composing a message and decides to : use the ^O option to postpone writing. User then attempts : to re-access the message, and sucessfully is allowed to : continue editing the file. User then attempts to postpone : editing again, and an endless loop occurs, filling the : drive with a .pine-debug1 file (the first we caught was 75 : megs in size, and the second was 53 megs). Reproducible : problem. Might be an os dependent problem? I constantly postpone and re-edit, repostpone up to 5 messages (the most I've had in the queue) and have had no problems. This as a regular user. In fact, I think this is one of the best new features they in- corporated in pine, to allow a queue of postponed messages. I recently tried to compile for a BSD/386 BSDI 1.1 0 os and pico kept failing at alt_editor (osdep.c from os_unix.c) and pine kept failing at sstrcasecmp [(pipe) appended to os-bsi.c]. Did you get any warnings during the make ? -- schliesk@sos.sos.net - Jay o Jay Schlieske <#< " Above all.... have fun. " +*+ Credits: smartmail__>^>__by * Linux+Pine3.90+Smail+Term-2.1.4+PoP +*+ ---------- #include ------------------------------- From owner-pine-info@cac.washington.edu Wed Oct 5 07:17:25 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19035; Wed, 5 Oct 94 07:17:25 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21446; Wed, 5 Oct 94 07:06:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21434; Wed, 5 Oct 94 07:06:46 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsWgM-00001CC; Wed, 5 Oct 94 06:46 PDT To: pine-info@cac.washington.edu From: keithc@gx2.uk.mdis.com (Keith Cordon) Subject: New user requires help. Date: Wed, 5 Oct 1994 12:07:12 GMT Message-Id: I have only just discovered PINE so please bear with me. Can someone please email me with information on how to stop the creation of enourmous .pine-debug files everytime I use pine. Also is there a FAQ for pine users? I've managed to get to grips with most of it but I have a few questions.... Many Thanks |\ Keith Cordon. Email:kcordon@uk.mdis.com /| | \ MDIS Tel : +44 602 490614 / | ------ \ Nottingham UK Fax : +44 602 497939 / ------ > < ______ / All comments are mine and mine alone! \ ______ | / All spelling and grammatical mistakes are deliberate \ | |/ and designed to annoy the pedantic. \| Is this a blessing or is it a curse? Does it get any better, could it get any worse? J.S. From owner-pine-info@cac.washington.edu Wed Oct 5 07:45:00 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20028; Wed, 5 Oct 94 07:45:00 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15988; Wed, 5 Oct 94 07:15:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15982; Wed, 5 Oct 94 07:15:25 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsWiH-00001EC; Wed, 5 Oct 94 06:48 PDT To: pine-info@cac.washington.edu From: Ken Weaverling Subject: Pine c-client patch for DG/UX: utime() problem Date: Wed, 5 Oct 1994 07:13:46 -0400 (EDT) Message-Id: Mime-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1971628816-2078917053-781353965=:11174" Content-Id: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1971628816-2078917053-781353965=:11174 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Pine 3.90 has a problem on DG/UX systems when using utime() to modify folder access and mod times. The result, folders getting weird modification dates, especially after an expunge operation. The folders most often were set to Dec 31, 1969 (epoch) or some other strange date. The problem is, the code defines... time_t tp[2]; ... and then passes tp into utime(). On DG/UX, utime actually is looking for four doubles. Each time is actually two time_t's, the second being in microseconds!!! If the struct utimbuf is used, it will work on DG/UX. I checked a SunOS and Solaris system and they both define utimbuf with members actime and modtime as well. The patch that is mime-attached to this message just patches the files to use utimbuf and does NOT put #ifdefs around anything. If this is a bad thing, then this patch will break some other system out there. I, and other DG users who told me they seen the same problem at other sites, would appreciate it if some type of fix for this could be folded into future releases ... and we all really appreciate the d-g build option in there already! Compiling was a breeze! -- Ken Weaverling weave@dtcc.edu |*| Wilmington: +1 302 573-5460 Manager of Computer Services |*| Stanton: +1 302 454-3978 Stanton/Wilmington Campuses of |*| WHOIS: KJW Delaware Technical & Community College |*| ---1971628816-2078917053-781353965=:11174 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=ChangesByWeave Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Patch for DG/UX utime bug VGhpcyBwYXRjaCBjaGFuZ2VzIHRoZSB1dGltZSgpIGNhbGxzIHRvIHVzZSBh IHV0aW1idWYgc3RydWN0IGluc3RlYWQgb2YNCmFzc3VtaW5nIHV0aW1lIGV4 cGVjdHMgdXRpbWJ1ZiB0byBiZSBhIHN0cnVjdCBvZiB0d28gdGltZV90IHZh cmlhYmxlcy4gVGhpcw0KYnJlYWtzIHRoZSBjYWxsIG9uIERHL1VYIHNpbmNl IHV0aW1idWYgYWN0dWFsbHkgaXMgZm91ciBsb25ncyBpbiBsZW5ndGggYW5k DQppbmNsdWRlcyBsb25ncyB0byBtZWFzdXJlIG1pY3Jvc2Vjb25kcy4gVGhl IHJlc3VsdCB3YXMgdGhhdCB0aGUgbW9kdGltZSB3YXMNCnVzdWFsbHkgc2V0 IHRvIDAgb3Igc29tZSBvdGhlciByYW5kb20gdmFsdWUsIHNvIGlmIHV0aW1l IHdhcyBldmVyIGNhbGxlZCwgDQptdGltZSdzIG9uIHRoZSBmb2xkZXJzIHdl cmUgYWx3YXlzIGJvdGNoZWQgdXAsIGJ1dCB1c3VhbGx5IHRoZSBiZWdpbm5p bmcNCm9mICh1bml4KSB0aW1lLiAgICAgKHdlYXZlQGR0Y2MuZWR1KQ0KDQoN CkZpcnN0LCBhZGQgdGhlIGxpbmUNCg0KI2luY2x1ZGUgPHV0aW1lLmg+DQoN Ci4uLiBzb21ld2hlcmUuIEkgYWRkZWQgaXQgdG8gb3NfZC1nLmggaW4gdGhl IGMtY2xpZW50IGRpcmVjdG9yeSwgb3IgSSBndWVzcw0KaXQgY291bGQgYmUg YWRkZWQgdG8gZWFjaCBvZiB0aGUgZm91ciBmaWxlcyBwYXRjaGVkIGJlbG93 Lg0KDQpBcHBseSB0aGUgYmVsb3cgcGF0Y2hlcyB0byB0aGUgZmlsZXMgdGVu ZXgyLmMgbW1kZi5jIG10eC5jIGFuZCBiZXplcmsuYy4NCg0KDQoNCg0KKioq IHRlbmV4Mi5jLm9yaWcJV2VkIE9jdCAgNSAwNTo1MjozOCAxOTk0DQotLS0g dGVuZXgyLmMJV2VkIE9jdCAgNSAwNTo0NzoxOSAxOTk0DQoqKioqKioqKioq KioqKioNCioqKiAxMTcsMTIxICoqKioNCiAgICBjaGFyICpzLGZpbGVbTUFJ TFRNUExFTl07DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICB0aW1lX3Qg dHBbMl07DQogICAgZXJybm8gPSBFSU5WQUw7CQkvKiBhc3N1bWUgaW52YWxp ZCBhcmd1bWVudCAqLw0KICAJCQkJLyogaWYgZmlsZSwgZ2V0IGl0cyBzdGF0 dXMgKi8NCi0tLSAxMTcsMTIxIC0tLS0NCiAgICBjaGFyICpzLGZpbGVbTUFJ TFRNUExFTl07DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICBzdHJ1Y3Qg dXRpbWJ1ZiB0cDsNCiAgICBlcnJubyA9IEVJTlZBTDsJCS8qIGFzc3VtZSBp bnZhbGlkIGFyZ3VtZW50ICovDQogIAkJCQkvKiBpZiBmaWxlLCBnZXQgaXRz IHN0YXR1cyAqLw0KKioqKioqKioqKioqKioqDQoqKiogMTMzLDEzOSAqKioq DQogIAkgICAgICAgKHMgPSBzdHJjaHIgKHRtcCsyMCwnLCcpKSAmJiBzdHJj aHIgKHMrMiwnOycpKSA/IFQgOiBOSUw7DQogICAgICAgIH0NCiEgICAgICAg dHBbMF0gPSBzYnVmLnN0X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSBhbmQg bXRpbWUgKi8NCiEgICAgICAgdHBbMV0gPSBzYnVmLnN0X210aW1lOw0KISAg ICAgICB1dGltZSAoZmlsZSx0cCk7CQkvKiBzZXQgdGhlIHRpbWVzICovDQog ICAgICB9DQogIAkJCQkvKiBhbGxvdyBlbXB0eSBmaWxlIGlmIElOQk9YICov DQotLS0gMTMzLDEzOSAtLS0tDQogIAkgICAgICAgKHMgPSBzdHJjaHIgKHRt cCsyMCwnLCcpKSAmJiBzdHJjaHIgKHMrMiwnOycpKSA/IFQgOiBOSUw7DQog ICAgICAgIH0NCiEgICAgICAgdHAuYWN0aW1lID0gc2J1Zi5zdF9hdGltZTsJ LyogcHJlc2VydmUgYXRpbWUgYW5kIG10aW1lICovDQohICAgICAgIHRwLm1v ZHRpbWUgPSBzYnVmLnN0X210aW1lOw0KISAgICAgICB1dGltZSAoZmlsZSwm dHApOwkJLyogc2V0IHRoZSB0aW1lcyAqLw0KICAgICAgfQ0KICAJCQkJLyog YWxsb3cgZW1wdHkgZmlsZSBpZiBJTkJPWCAqLw0KKioqKioqKioqKioqKioq DQoqKiogMTA1NSwxMDU5ICoqKioNCiAgICBpbnQgZmQsbGQ7DQogICAgY2hh ciBjLCpzLCp0LHRtcFtNQUlMVE1QTEVOXSxmaWxlW01BSUxUTVBMRU5dLGxv Y2tbTUFJTFRNUExFTl07DQohICAgdGltZV90IHRwWzJdOw0KICAgIE1FU1NB R0VDQUNIRSBlbHQ7DQogICAgbG9uZyBpID0gU0laRSAobWVzc2FnZSk7DQot LS0gMTA1NSwxMDU5IC0tLS0NCiAgICBpbnQgZmQsbGQ7DQogICAgY2hhciBj LCpzLCp0LHRtcFtNQUlMVE1QTEVOXSxmaWxlW01BSUxUTVBMRU5dLGxvY2tb TUFJTFRNUExFTl07DQohICAgc3RydWN0IHV0aW1idWYgdHA7DQogICAgTUVT U0FHRUNBQ0hFIGVsdDsNCiAgICBsb25nIGkgPSBTSVpFIChtZXNzYWdlKTsN CioqKioqKioqKioqKioqKg0KKioqIDExMjgsMTEzNCAqKioqDQogICAgfQ0K ICAgIGZzeW5jIChmZCk7CQkJLyogZm9yY2Ugb3V0IHRoZSB1cGRhdGUgKi8N CiEgICB0cFswXSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNlcnZlIGF0aW1l IGFuZCBtdGltZSAqLw0KISAgIHRwWzFdID0gc2J1Zi5zdF9tdGltZTsNCiEg ICB1dGltZSAoZmlsZSx0cCk7CQkvKiBzZXQgdGhlIHRpbWVzICovDQogICAg dGVuZXhfdW5sb2NrIChsZCxsb2NrKTsJLyogcmVsZWFzZSBleGNsdXNpdmUg cGFyc2UvYXBwZW5kIHBlcm1pc3Npb24gKi8NCiAgICBjbG9zZSAoZmQpOwkJ CS8qIGNsb3NlIHRoZSBmaWxlICovDQotLS0gMTEyOCwxMTM0IC0tLS0NCiAg ICB9DQogICAgZnN5bmMgKGZkKTsJCQkvKiBmb3JjZSBvdXQgdGhlIHVwZGF0 ZSAqLw0KISAgIHRwLmFjdGltZSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNl cnZlIGF0aW1lIGFuZCBtdGltZSAqLw0KISAgIHRwLm1vZHRpbWUgPSBzYnVm LnN0X210aW1lOw0KISAgIHV0aW1lIChmaWxlLCZ0cCk7CQkvKiBzZXQgdGhl IHRpbWVzICovDQogICAgdGVuZXhfdW5sb2NrIChsZCxsb2NrKTsJLyogcmVs ZWFzZSBleGNsdXNpdmUgcGFyc2UvYXBwZW5kIHBlcm1pc3Npb24gKi8NCiAg ICBjbG9zZSAoZmQpOwkJCS8qIGNsb3NlIHRoZSBmaWxlICovDQoqKioqKioq KioqKioqKioNCioqKiAxMzk3LDE0MDEgKioqKg0KICB7DQogICAgc3RydWN0 IHN0YXQgc2J1ZjsNCiEgICB0aW1lX3QgdHBbMl07DQogICAgTUVTU0FHRUNB Q0hFICplbHQ7DQogICAgdW5zaWduZWQgbG9uZyBpLGosazsNCi0tLSAxMzk3 LDE0MDEgLS0tLQ0KICB7DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICBz dHJ1Y3QgdXRpbWJ1ZiB0cDsNCiAgICBNRVNTQUdFQ0FDSEUgKmVsdDsNCiAg ICB1bnNpZ25lZCBsb25nIGksaixrOw0KKioqKioqKioqKioqKioqDQoqKiog MTQ1NCwxNDYwICoqKioNCiAgICAgIH0NCiAgICBmc3luYyAoZmQpOwkJCS8q IGZvcmNlIG91dCB0aGUgdXBkYXRlICovDQohICAgdHBbMF0gPSBzYnVmLnN0 X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSBhbmQgbXRpbWUgKi8NCiEgICB0 cFsxXSA9IHNidWYuc3RfbXRpbWU7DQohICAgdXRpbWUgKGZpbGUsdHApOwkJ Lyogc2V0IHRoZSB0aW1lcyAqLw0KICAgIHRlbmV4X3VubG9jayAobGQsbG9j ayk7CS8qIHJlbGVhc2UgZXhjbHVzaXZlIHBhcnNlL2FwcGVuZCBwZXJtaXNz aW9uICovDQogICAgY2xvc2UgKGZkKTsJCQkvKiBjbG9zZSB0aGUgZmlsZSAq Lw0KLS0tIDE0NTQsMTQ2MCAtLS0tDQogICAgICB9DQogICAgZnN5bmMgKGZk KTsJCQkvKiBmb3JjZSBvdXQgdGhlIHVwZGF0ZSAqLw0KISAgIHRwLmFjdGlt ZSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNlcnZlIGF0aW1lIGFuZCBtdGlt ZSAqLw0KISAgIHRwLm1vZHRpbWUgPSBzYnVmLnN0X210aW1lOw0KISAgIHV0 aW1lIChmaWxlLCZ0cCk7CQkvKiBzZXQgdGhlIHRpbWVzICovDQogICAgdGVu ZXhfdW5sb2NrIChsZCxsb2NrKTsJLyogcmVsZWFzZSBleGNsdXNpdmUgcGFy c2UvYXBwZW5kIHBlcm1pc3Npb24gKi8NCiAgICBjbG9zZSAoZmQpOwkJCS8q IGNsb3NlIHRoZSBmaWxlICovDQoqKiogbXR4LmMub3JpZwlXZWQgT2N0ICA1 IDA0OjU3OjA2IDE5OTQNCi0tLSBtdHguYwlXZWQgT2N0ICA1IDA1OjUwOjA3 IDE5OTQNCioqKioqKioqKioqKioqKg0KKioqIDExNywxMjEgKioqKg0KICAg IGNoYXIgKnMsZmlsZVtNQUlMVE1QTEVOXTsNCiAgICBzdHJ1Y3Qgc3RhdCBz YnVmOw0KISAgIHRpbWVfdCB0cFsyXTsNCiAgICBlcnJubyA9IEVJTlZBTDsJ CS8qIGFzc3VtZSBpbnZhbGlkIGFyZ3VtZW50ICovDQogIAkJCQkvKiBpZiBm aWxlLCBnZXQgaXRzIHN0YXR1cyAqLw0KLS0tIDExNywxMjEgLS0tLQ0KICAg IGNoYXIgKnMsZmlsZVtNQUlMVE1QTEVOXTsNCiAgICBzdHJ1Y3Qgc3RhdCBz YnVmOw0KISAgIHN0cnVjdCB1dGltYnVmIHRwOw0KICAgIGVycm5vID0gRUlO VkFMOwkJLyogYXNzdW1lIGludmFsaWQgYXJndW1lbnQgKi8NCiAgCQkJCS8q IGlmIGZpbGUsIGdldCBpdHMgc3RhdHVzICovDQoqKioqKioqKioqKioqKioN CioqKiAxMzMsMTM5ICoqKioNCiAgCSAgICAgICAocyA9IHN0cmNociAodG1w KzIwLCcsJykpICYmIHN0cmNociAocysyLCc7JykpID8gVCA6IE5JTDsNCiAg ICAgICAgfQ0KISAgICAgICB0cFswXSA9IHNidWYuc3RfYXRpbWU7CS8qIHBy ZXNlcnZlIGF0aW1lIGFuZCBtdGltZSAqLw0KISAgICAgICB0cFsxXSA9IHNi dWYuc3RfbXRpbWU7DQohICAgICAgIHV0aW1lIChmaWxlLHRwKTsJCS8qIHNl dCB0aGUgdGltZXMgKi8NCiAgICAgIH0NCiAgCQkJCS8qIGFsbG93IGVtcHR5 IGZpbGUgaWYgSU5CT1ggKi8NCi0tLSAxMzMsMTM5IC0tLS0NCiAgCSAgICAg ICAocyA9IHN0cmNociAodG1wKzIwLCcsJykpICYmIHN0cmNociAocysyLCc7 JykpID8gVCA6IE5JTDsNCiAgICAgICAgfQ0KISAgICAgICB0cC5hY3RpbWUg PSBzYnVmLnN0X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSBhbmQgbXRpbWUg Ki8NCiEgICAgICAgdHAubW9kdGltZSA9IHNidWYuc3RfbXRpbWU7DQohICAg ICAgIHV0aW1lIChmaWxlLCZ0cCk7CQkvKiBzZXQgdGhlIHRpbWVzICovDQog ICAgICB9DQogIAkJCQkvKiBhbGxvdyBlbXB0eSBmaWxlIGlmIElOQk9YICov DQoqKioqKioqKioqKioqKioNCioqKiAxMDgwLDEwODQgKioqKg0KICAgIGlu dCBmZCxsZDsNCiAgICBjaGFyICpzLCp0LHRtcFtNQUlMVE1QTEVOXSxmaWxl W01BSUxUTVBMRU5dLGxvY2tbTUFJTFRNUExFTl07DQohICAgdGltZV90IHRw WzJdOw0KICAgIE1FU1NBR0VDQUNIRSBlbHQ7DQogICAgbG9uZyBpOw0KLS0t IDEwODAsMTA4NCAtLS0tDQogICAgaW50IGZkLGxkOw0KICAgIGNoYXIgKnMs KnQsdG1wW01BSUxUTVBMRU5dLGZpbGVbTUFJTFRNUExFTl0sbG9ja1tNQUlM VE1QTEVOXTsNCiEgICBzdHJ1Y3QgdXRpbWJ1ZiB0cDsNCiAgICBNRVNTQUdF Q0FDSEUgZWx0Ow0KICAgIGxvbmcgaTsNCioqKioqKioqKioqKioqKg0KKioq IDExNTIsMTE1OCAqKioqDQogICAgfQ0KICAgIGZzeW5jIChmZCk7CQkJLyog Zm9yY2Ugb3V0IHRoZSB1cGRhdGUgKi8NCiEgICB0cFswXSA9IHNidWYuc3Rf YXRpbWU7CS8qIHByZXNlcnZlIGF0aW1lIGFuZCBtdGltZSAqLw0KISAgIHRw WzFdID0gc2J1Zi5zdF9tdGltZTsNCiEgICB1dGltZSAoZmlsZSx0cCk7CQkv KiBzZXQgdGhlIHRpbWVzICovDQogICAgbXR4X3VubG9jayAobGQsbG9jayk7 CQkvKiByZWxlYXNlIGV4Y2x1c2l2ZSBwYXJzZS9hcHBlbmQgcGVybWlzc2lv biAqLw0KICAgIGNsb3NlIChmZCk7CQkJLyogY2xvc2UgdGhlIGZpbGUgKi8N Ci0tLSAxMTUyLDExNTggLS0tLQ0KICAgIH0NCiAgICBmc3luYyAoZmQpOwkJ CS8qIGZvcmNlIG91dCB0aGUgdXBkYXRlICovDQohICAgdHAuYWN0aW1lID0g c2J1Zi5zdF9hdGltZTsJLyogcHJlc2VydmUgYXRpbWUgYW5kIG10aW1lICov DQohICAgdHAubW9kdGltZSA9IHNidWYuc3RfbXRpbWU7DQohICAgdXRpbWUg KGZpbGUsJnRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICBtdHhfdW5s b2NrIChsZCxsb2NrKTsJCS8qIHJlbGVhc2UgZXhjbHVzaXZlIHBhcnNlL2Fw cGVuZCBwZXJtaXNzaW9uICovDQogICAgY2xvc2UgKGZkKTsJCQkvKiBjbG9z ZSB0aGUgZmlsZSAqLw0KKioqKioqKioqKioqKioqDQoqKiogMTQxMCwxNDE0 ICoqKioNCiAgew0KICAgIHN0cnVjdCBzdGF0IHNidWY7DQohICAgdGltZV90 IHRwWzJdOw0KICAgIE1FU1NBR0VDQUNIRSAqZWx0Ow0KICAgIHVuc2lnbmVk IGxvbmcgaSxqLGs7DQotLS0gMTQxMCwxNDE0IC0tLS0NCiAgew0KICAgIHN0 cnVjdCBzdGF0IHNidWY7DQohICAgc3RydWN0IHV0aW1idWYgdHA7DQogICAg TUVTU0FHRUNBQ0hFICplbHQ7DQogICAgdW5zaWduZWQgbG9uZyBpLGosazsN CioqKioqKioqKioqKioqKg0KKioqIDE0NjcsMTQ3MyAqKioqDQogICAgICB9 DQogICAgZnN5bmMgKGZkKTsJCQkvKiBmb3JjZSBvdXQgdGhlIHVwZGF0ZSAq Lw0KISAgIHRwWzBdID0gc2J1Zi5zdF9hdGltZTsJLyogcHJlc2VydmUgYXRp bWUgYW5kIG10aW1lICovDQohICAgdHBbMV0gPSBzYnVmLnN0X210aW1lOw0K ISAgIHV0aW1lIChmaWxlLHRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAg ICBtdHhfdW5sb2NrIChsZCxsb2NrKTsJCS8qIHJlbGVhc2UgZXhjbHVzaXZl IHBhcnNlL2FwcGVuZCBwZXJtaXNzaW9uICovDQogICAgY2xvc2UgKGZkKTsJ CQkvKiBjbG9zZSB0aGUgZmlsZSAqLw0KLS0tIDE0NjcsMTQ3MyAtLS0tDQog ICAgICB9DQogICAgZnN5bmMgKGZkKTsJCQkvKiBmb3JjZSBvdXQgdGhlIHVw ZGF0ZSAqLw0KISAgIHRwLmFjdGltZSA9IHNidWYuc3RfYXRpbWU7CS8qIHBy ZXNlcnZlIGF0aW1lIGFuZCBtdGltZSAqLw0KISAgIHRwLm1vZHRpbWUgPSBz YnVmLnN0X210aW1lOw0KISAgIHV0aW1lIChmaWxlLCZ0cCk7CQkvKiBzZXQg dGhlIHRpbWVzICovDQogICAgbXR4X3VubG9jayAobGQsbG9jayk7CQkvKiBy ZWxlYXNlIGV4Y2x1c2l2ZSBwYXJzZS9hcHBlbmQgcGVybWlzc2lvbiAqLw0K ICAgIGNsb3NlIChmZCk7CQkJLyogY2xvc2UgdGhlIGZpbGUgKi8NCioqKiBt bWRmLmMub3JpZwlXZWQgT2N0ICA1IDA0OjU3OjQ1IDE5OTQNCi0tLSBtbWRm LmMJV2VkIE9jdCAgNSAwNTo1MTo0NCAxOTk0DQoqKioqKioqKioqKioqKioN CioqKiAxMTksMTIzICoqKioNCiAgICBjaGFyICpzID0gdG1wLCp0LGZpbGVb TUFJTFRNUExFTl07DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICB0aW1l X3QgdHBbMl07DQogICAgZXJybm8gPSBFSU5WQUw7CQkvKiBhc3N1bWUgaW52 YWxpZCBhcmd1bWVudCAqLw0KICAJCQkJLyogbXVzdCBiZSBub24tZW1wdHkg ZmlsZSAqLw0KLS0tIDExOSwxMjMgLS0tLQ0KICAgIGNoYXIgKnMgPSB0bXAs KnQsZmlsZVtNQUlMVE1QTEVOXTsNCiAgICBzdHJ1Y3Qgc3RhdCBzYnVmOw0K ISAgIHN0cnVjdCB1dGltYnVmIHRwOw0KICAgIGVycm5vID0gRUlOVkFMOwkJ LyogYXNzdW1lIGludmFsaWQgYXJndW1lbnQgKi8NCiAgCQkJCS8qIG11c3Qg YmUgbm9uLWVtcHR5IGZpbGUgKi8NCioqKioqKioqKioqKioqKg0KKioqIDEy NywxMzMgKioqKg0KICAgICAgcmV0ID0gKChzYnVmLnN0X3NpemUgPiAwKSAm JiAocmVhZCAoZmQsdG1wLE1BSUxUTVBMRU4tMSkgPj0gMCkgJiYNCiAgCSAg IElTTU1ERiAodG1wKSkgPyBUIDogTklMOw0KISAgICAgdHBbMF0gPSBzYnVm LnN0X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSBhbmQgbXRpbWUgKi8NCiEg ICAgIHRwWzFdID0gc2J1Zi5zdF9tdGltZTsNCiEgICAgIHV0aW1lIChmaWxl LHRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICAgIGNsb3NlIChmZCk7 CQkJLyogY2xvc2UgdGhlIGZpbGUgKi8NCiAgCQkJCS8qIG5vIGVycm9yIGlm IGZpbGUgZW1wdHkgKi8NCi0tLSAxMjcsMTMzIC0tLS0NCiAgICAgIHJldCA9 ICgoc2J1Zi5zdF9zaXplID4gMCkgJiYgKHJlYWQgKGZkLHRtcCxNQUlMVE1Q TEVOLTEpID49IDApICYmDQogIAkgICBJU01NREYgKHRtcCkpID8gVCA6IE5J TDsNCiEgICAgIHRwLmFjdGltZSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNl cnZlIGF0aW1lIGFuZCBtdGltZSAqLw0KISAgICAgdHAubW9kdGltZSA9IHNi dWYuc3RfbXRpbWU7DQohICAgICB1dGltZSAoZmlsZSwmdHApOwkJLyogc2V0 IHRoZSB0aW1lcyAqLw0KICAgICAgY2xvc2UgKGZkKTsJCQkvKiBjbG9zZSB0 aGUgZmlsZSAqLw0KICAJCQkJLyogbm8gZXJyb3IgaWYgZmlsZSBlbXB0eSAq Lw0KKioqKioqKioqKioqKioqDQoqKiogOTE3LDkyMSAqKioqDQogICAgaW50 IGZkLG9rID0gVDsNCiAgICBjaGFyIGMsYnVmW01BSUxUTVBMRU5dLGZpbGVb TUFJTFRNUExFTl0sbG9ja1tNQUlMVE1QTEVOXTsNCiEgICB0aW1lX3QgdHBb Ml07DQogICAgTUVTU0FHRUNBQ0hFIGVsdDsNCiAgICBpbnQgaSA9IDA7DQot LS0gOTE3LDkyMSAtLS0tDQogICAgaW50IGZkLG9rID0gVDsNCiAgICBjaGFy IGMsYnVmW01BSUxUTVBMRU5dLGZpbGVbTUFJTFRNUExFTl0sbG9ja1tNQUlM VE1QTEVOXTsNCiEgICBzdHJ1Y3QgdXRpbWJ1ZiB0cDsNCiAgICBNRVNTQUdF Q0FDSEUgZWx0Ow0KICAgIGludCBpID0gMDsNCioqKioqKioqKioqKioqKg0K KioqIDk5MCw5OTYgKioqKg0KICAgICAgb2sgPSBOSUw7DQogICAgfQ0KISAg IHRwWzBdID0gc2J1Zi5zdF9hdGltZTsJLyogcHJlc2VydmUgYXRpbWUgKi8N CiEgICB0cFsxXSA9IHRpbWUgKDApOwkJLyogc2V0IG10aW1lIHRvIG5vdyAq Lw0KISAgIHV0aW1lIChmaWxlLHRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8N CiAgICBtbWRmX3VubG9jayAoZmQsTklMLGxvY2spOwkvKiB1bmxvY2sgYW5k IGNsb3NlIG1haWxib3ggKi8NCiAgICBtbV9ub2NyaXRpY2FsIChzdHJlYW0p OwkvKiByZWxlYXNlIGNyaXRpY2FsICovDQotLS0gOTkwLDk5NiAtLS0tDQog ICAgICBvayA9IE5JTDsNCiAgICB9DQohICAgdHAuYWN0aW1lID0gc2J1Zi5z dF9hdGltZTsJLyogcHJlc2VydmUgYXRpbWUgKi8NCiEgICB0cC5tb2R0aW1l ID0gdGltZSAoMCk7CQkvKiBzZXQgbXRpbWUgdG8gbm93ICovDQohICAgdXRp bWUgKGZpbGUsJnRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICBtbWRm X3VubG9jayAoZmQsTklMLGxvY2spOwkvKiB1bmxvY2sgYW5kIGNsb3NlIG1h aWxib3ggKi8NCiAgICBtbV9ub2NyaXRpY2FsIChzdHJlYW0pOwkvKiByZWxl YXNlIGNyaXRpY2FsICovDQoqKioqKioqKioqKioqKioNCioqKiAxMTQ4LDEx NjAgKioqKg0KICB7DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICB0aW1l X3QgdHBbMl07DQogICAgZnN0YXQgKGZkLCZzYnVmKTsJCS8qIGdldCBmaWxl IHRpbWVzICovDQogIAkJCQkvKiBpZiBzdHJlYW0gYW5kIGNzaCB3b3VsZCB0 aGluayBuZXcgbWFpbCAqLw0KICAgIGlmIChzdHJlYW0gJiYgKHNidWYuc3Rf YXRpbWUgPD0gc2J1Zi5zdF9tdGltZSkpIHsNCiEgICAgIHRwWzBdID0gdGlt ZSAoMCk7CQkvKiBzZXQgYXRpbWUgdG8gbm93ICovDQogIAkJCQkvKiBzZXQg bXRpbWUgdG8gKG5vdyAtIDEpIGlmIG5lY2Vzc2FyeSAqLw0KISAgICAgdHBb MV0gPSB0cFswXSA+IHNidWYuc3RfbXRpbWUgPyBzYnVmLnN0X210aW1lIDog dHBbMF0gLSAxOw0KICAJCQkJLyogc2V0IHRoZSB0aW1lcywgbm90ZSBjaGFu Z2UgKi8NCiEgICAgIGlmICghdXRpbWUgKExPQ0FMLT5uYW1lLHRwKSkgTE9D QUwtPmZpbGV0aW1lID0gdHBbMV07DQogICAgfQ0KICAgIGZsb2NrIChmZCxM T0NLX1VOKTsJCS8qIHJlbGVhc2UgZmxvY2snZXJzICovDQotLS0gMTE0OCwx MTYwIC0tLS0NCiAgew0KICAgIHN0cnVjdCBzdGF0IHNidWY7DQohICAgc3Ry dWN0IHV0aW1idWYgdHA7DQogICAgZnN0YXQgKGZkLCZzYnVmKTsJCS8qIGdl dCBmaWxlIHRpbWVzICovDQogIAkJCQkvKiBpZiBzdHJlYW0gYW5kIGNzaCB3 b3VsZCB0aGluayBuZXcgbWFpbCAqLw0KICAgIGlmIChzdHJlYW0gJiYgKHNi dWYuc3RfYXRpbWUgPD0gc2J1Zi5zdF9tdGltZSkpIHsNCiEgICAgIHRwLmFj dGltZSA9IHRpbWUgKDApOwkJLyogc2V0IGF0aW1lIHRvIG5vdyAqLw0KICAJ CQkJLyogc2V0IG10aW1lIHRvIChub3cgLSAxKSBpZiBuZWNlc3NhcnkgKi8N CiEgICAgIHRwLm1vZHRpbWUgPSB0cC5hY3RpbWUgPiBzYnVmLnN0X210aW1l ID8gc2J1Zi5zdF9tdGltZSA6IHRwLmFjdGltZSAtIDE7DQogIAkJCQkvKiBz ZXQgdGhlIHRpbWVzLCBub3RlIGNoYW5nZSAqLw0KISAgICAgaWYgKCF1dGlt ZSAoTE9DQUwtPm5hbWUsJnRwKSkgTE9DQUwtPmZpbGV0aW1lID0gdHAubW9k dGltZTsNCiAgICB9DQogICAgZmxvY2sgKGZkLExPQ0tfVU4pOwkJLyogcmVs ZWFzZSBmbG9jaydlcnMgKi8NCioqKioqKioqKioqKioqKg0KKioqIDE2MDks MTYxMyAqKioqDQogICAgaW50IGZkOw0KICAgIHN0cnVjdCBzdGF0IHNidWY7 DQohICAgdGltZV90IHRwWzJdOw0KICAgIGxvbmcgaTsNCiAgICBpbnQgb2sg PSBUOw0KLS0tIDE2MDksMTYxMyAtLS0tDQogICAgaW50IGZkOw0KICAgIHN0 cnVjdCBzdGF0IHNidWY7DQohICAgc3RydWN0IHV0aW1idWYgdHA7DQogICAg bG9uZyBpOw0KICAgIGludCBvayA9IFQ7DQoqKioqKioqKioqKioqKioNCioq KiAxNjUzLDE2NTkgKioqKg0KICAgICAgb2sgPSBOSUw7CQkJLyogb29wcyAq Lw0KICAgIH0NCiEgICB0cFswXSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNl cnZlIGF0aW1lICovDQohICAgdHBbMV0gPSB0aW1lICgwKTsJCS8qIHNldCBt dGltZSB0byBub3cgKi8NCiEgICB1dGltZSAoZmlsZSx0cCk7CQkvKiBzZXQg dGhlIHRpbWVzICovDQogICAgbW1kZl91bmxvY2sgKGZkLE5JTCxsb2NrKTsJ LyogdW5sb2NrIGFuZCBjbG9zZSBtYWlsYm94ICovDQogICAgbW1fbm9jcml0 aWNhbCAoc3RyZWFtKTsJLyogcmVsZWFzZSBjcml0aWNhbCAqLw0KLS0tIDE2 NTMsMTY1OSAtLS0tDQogICAgICBvayA9IE5JTDsJCQkvKiBvb3BzICovDQog ICAgfQ0KISAgIHRwLmFjdGltZSA9IHNidWYuc3RfYXRpbWU7CS8qIHByZXNl cnZlIGF0aW1lICovDQohICAgdHAubW9kdGltZSA9IHRpbWUgKDApOwkvKiBz ZXQgbXRpbWUgdG8gbm93ICovDQohICAgdXRpbWUgKGZpbGUsJnRwKTsJCS8q IHNldCB0aGUgdGltZXMgKi8NCiAgICBtbWRmX3VubG9jayAoZmQsTklMLGxv Y2spOwkvKiB1bmxvY2sgYW5kIGNsb3NlIG1haWxib3ggKi8NCiAgICBtbV9u b2NyaXRpY2FsIChzdHJlYW0pOwkvKiByZWxlYXNlIGNyaXRpY2FsICovDQoq KiogYmV6ZXJrLmMub3JpZwlXZWQgT2N0ICA1IDA0OjQ4OjAwIDE5OTQNCi0t LSBiZXplcmsuYwlXZWQgT2N0ICA1IDA1OjE0OjQzIDE5OTQNCioqKioqKioq KioqKioqKg0KKioqIDEzMSwxMzUgKioqKg0KICAgIGNoYXIgKnMgPSB0bXAs KnQsZmlsZVtNQUlMVE1QTEVOXTsNCiAgICBzdHJ1Y3Qgc3RhdCBzYnVmOw0K ISAgIHRpbWVfdCB0cFsyXTsNCiAgICBlcnJubyA9IEVJTlZBTDsJCS8qIGFz c3VtZSBpbnZhbGlkIGFyZ3VtZW50ICovDQogIAkJCQkvKiBtdXN0IGJlIG5v bi1lbXB0eSBmaWxlICovDQotLS0gMTMxLDEzNSAtLS0tDQogICAgY2hhciAq cyA9IHRtcCwqdCxmaWxlW01BSUxUTVBMRU5dOw0KICAgIHN0cnVjdCBzdGF0 IHNidWY7DQohICAgc3RydWN0IHV0aW1idWYgdHA7DQogICAgZXJybm8gPSBF SU5WQUw7CQkvKiBhc3N1bWUgaW52YWxpZCBhcmd1bWVudCAqLw0KICAJCQkJ LyogbXVzdCBiZSBub24tZW1wdHkgZmlsZSAqLw0KKioqKioqKioqKioqKioq DQoqKiogMTM5LDE0NSAqKioqDQogICAgICBpZiAoKHNidWYuc3Rfc2l6ZSA+ IDApICYmIChyZWFkIChmZCx0bXAsTUFJTFRNUExFTi0xKSA+PSAwKSkNCiAg ICAgICAgVkFMSUQgKHMsdCxyZXQsem4pOw0KISAgICAgdHBbMF0gPSBzYnVm LnN0X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSBhbmQgbXRpbWUgKi8NCiEg ICAgIHRwWzFdID0gc2J1Zi5zdF9tdGltZTsNCiEgICAgIHV0aW1lIChmaWxl LHRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICAgIGNsb3NlIChmZCk7 CQkJLyogY2xvc2UgdGhlIGZpbGUgKi8NCiAgCQkJCS8qIG5vIGVycm9yIGlm IGZpbGUgZW1wdHkgKi8NCi0tLSAxMzksMTQ1IC0tLS0NCiAgICAgIGlmICgo c2J1Zi5zdF9zaXplID4gMCkgJiYgKHJlYWQgKGZkLHRtcCxNQUlMVE1QTEVO LTEpID49IDApKQ0KICAgICAgICBWQUxJRCAocyx0LHJldCx6bik7DQohICAg ICB0cC5hY3RpbWUgPSBzYnVmLnN0X2F0aW1lOwkvKiBwcmVzZXJ2ZSBhdGlt ZSBhbmQgbXRpbWUgKi8NCiEgICAgIHRwLm1vZHRpbWUgPSBzYnVmLnN0X210 aW1lOw0KISAgICAgdXRpbWUgKGZpbGUsJnRwKTsJCS8qIHNldCB0aGUgdGlt ZXMgKi8NCiAgICAgIGNsb3NlIChmZCk7CQkJLyogY2xvc2UgdGhlIGZpbGUg Ki8NCiAgCQkJCS8qIG5vIGVycm9yIGlmIGZpbGUgZW1wdHkgKi8NCioqKioq KioqKioqKioqKg0KKioqIDk2Nyw5NzEgKioqKg0KICAgIGludCBpLGZkLHRp LHpuOw0KICAgIGNoYXIgKnMsKngsYnVmW0JVRkxFTl0sZmlsZVtNQUlMVE1Q TEVOXSxsb2NrW01BSUxUTVBMRU5dOw0KISAgIHRpbWVfdCB0cFsyXTsNCiAg ICBNRVNTQUdFQ0FDSEUgZWx0Ow0KICAgIGNoYXIgYyA9ICdcbic7DQotLS0g OTY3LDk3MSAtLS0tDQogICAgaW50IGksZmQsdGksem47DQogICAgY2hhciAq cywqeCxidWZbQlVGTEVOXSxmaWxlW01BSUxUTVBMRU5dLGxvY2tbTUFJTFRN UExFTl07DQohICAgc3RydWN0IHV0aW1idWYgdHA7DQogICAgTUVTU0FHRUNB Q0hFIGVsdDsNCiAgICBjaGFyIGMgPSAnXG4nOw0KKioqKioqKioqKioqKioq DQoqKiogMTA0OSwxMDU1ICoqKioNCiAgICAgIGZ0cnVuY2F0ZSAoZmQsc2J1 Zi5zdF9zaXplKTsNCiAgICB9DQohICAgdHBbMF0gPSBzYnVmLnN0X2F0aW1l OwkvKiBwcmVzZXJ2ZSBhdGltZSAqLw0KISAgIHRwWzFdID0gdGltZSAoMCk7 CQkvKiBzZXQgbXRpbWUgdG8gbm93ICovDQohICAgdXRpbWUgKGZpbGUsdHAp OwkJLyogc2V0IHRoZSB0aW1lcyAqLw0KICAgIGJlemVya191bmxvY2sgKGZk LE5JTCxsb2NrKTsJLyogdW5sb2NrIGFuZCBjbG9zZSBtYWlsYm94ICovDQog ICAgbW1fbm9jcml0aWNhbCAoc3RyZWFtKTsJLyogcmVsZWFzZSBjcml0aWNh bCAqLw0KLS0tIDEwNDksMTA1NSAtLS0tDQogICAgICBmdHJ1bmNhdGUgKGZk LHNidWYuc3Rfc2l6ZSk7DQogICAgfQ0KISAgIHRwLmFjdGltZSA9IHNidWYu c3RfYXRpbWU7CS8qIHByZXNlcnZlIGF0aW1lICovDQohICAgdHAubW9kdGlt ZSA9IHRpbWUgKDApOwkvKiBzZXQgbXRpbWUgdG8gbm93ICovDQohICAgdXRp bWUgKGZpbGUsJnRwKTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICBiZXpl cmtfdW5sb2NrIChmZCxOSUwsbG9jayk7CS8qIHVubG9jayBhbmQgY2xvc2Ug bWFpbGJveCAqLw0KICAgIG1tX25vY3JpdGljYWwgKHN0cmVhbSk7CS8qIHJl bGVhc2UgY3JpdGljYWwgKi8NCioqKioqKioqKioqKioqKg0KKioqIDEyMjUs MTIzNyAqKioqDQogIHsNCiAgICBzdHJ1Y3Qgc3RhdCBzYnVmOw0KISAgIHRp bWVfdCB0cFsyXTsNCiAgICBmc3RhdCAoZmQsJnNidWYpOwkJLyogZ2V0IGZp bGUgdGltZXMgKi8NCiAgCQkJCS8qIGlmIHN0cmVhbSBhbmQgY3NoIHdvdWxk IHRoaW5rIG5ldyBtYWlsICovDQogICAgaWYgKHN0cmVhbSAmJiAoc2J1Zi5z dF9hdGltZSA8PSBzYnVmLnN0X210aW1lKSkgew0KISAgICAgdHBbMF0gPSB0 aW1lICgwKTsJCS8qIHNldCBhdGltZSB0byBub3cgKi8NCiAgCQkJCS8qIHNl dCBtdGltZSB0byAobm93IC0gMSkgaWYgbmVjZXNzYXJ5ICovDQohICAgICB0 cFsxXSA9IHRwWzBdID4gc2J1Zi5zdF9tdGltZSA/IHNidWYuc3RfbXRpbWUg OiB0cFswXSAtIDE7DQogIAkJCQkvKiBzZXQgdGhlIHRpbWVzLCBub3RlIGNo YW5nZSAqLw0KISAgICAgaWYgKCF1dGltZSAoTE9DQUwtPm5hbWUsdHApKSBM T0NBTC0+ZmlsZXRpbWUgPSB0cFsxXTsNCiAgICB9DQogICAgZmxvY2sgKGZk LExPQ0tfVU4pOwkJLyogcmVsZWFzZSBmbG9jaydlcnMgKi8NCi0tLSAxMjI1 LDEyMzcgLS0tLQ0KICB7DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICBz dHJ1Y3QgdXRpbWJ1ZiB0cDsNCiAgICBmc3RhdCAoZmQsJnNidWYpOwkJLyog Z2V0IGZpbGUgdGltZXMgKi8NCiAgCQkJCS8qIGlmIHN0cmVhbSBhbmQgY3No IHdvdWxkIHRoaW5rIG5ldyBtYWlsICovDQogICAgaWYgKHN0cmVhbSAmJiAo c2J1Zi5zdF9hdGltZSA8PSBzYnVmLnN0X210aW1lKSkgew0KISAgICAgdHAu YWN0aW1lID0gdGltZSAoMCk7CS8qIHNldCBhdGltZSB0byBub3cgKi8NCiAg CQkJCS8qIHNldCBtdGltZSB0byAobm93IC0gMSkgaWYgbmVjZXNzYXJ5ICov DQohICAgICB0cC5tb2R0aW1lID0gdHAuYWN0aW1lID4gc2J1Zi5zdF9tdGlt ZSA/IHNidWYuc3RfbXRpbWUgOiB0cC5hY3RpbWUgLSAxOw0KICAJCQkJLyog c2V0IHRoZSB0aW1lcywgbm90ZSBjaGFuZ2UgKi8NCiEgICAgIGlmICghdXRp bWUgKExPQ0FMLT5uYW1lLCZ0cCkpIExPQ0FMLT5maWxldGltZSA9IHRwLm1v ZHRpbWU7DQogICAgfQ0KICAgIGZsb2NrIChmZCxMT0NLX1VOKTsJCS8qIHJl bGVhc2UgZmxvY2snZXJzICovDQoqKioqKioqKioqKioqKioNCioqKiAxNzA4 LDE3MTIgKioqKg0KICAgIGludCBmZCxpb3ZjOw0KICAgIHN0cnVjdCBzdGF0 IHNidWY7DQohICAgdGltZV90IHRwWzJdOw0KICAgIGxvbmcgaTsNCiAgICBp bnQgb2sgPSBUOw0KLS0tIDE3MDgsMTcxMiAtLS0tDQogICAgaW50IGZkLGlv dmM7DQogICAgc3RydWN0IHN0YXQgc2J1ZjsNCiEgICBzdHJ1Y3QgdXRpbWJ1 ZiB0cDsNCiAgICBsb25nIGk7DQogICAgaW50IG9rID0gVDsNCioqKioqKioq KioqKioqKg0KKioqIDE3NTcsMTc2MyAqKioqDQogICAgICBvayA9IE5JTDsJ CQkvKiBvb3BzICovDQogICAgfQ0KISAgIHRwWzBdID0gc2J1Zi5zdF9hdGlt ZTsJLyogcHJlc2VydmUgYXRpbWUgKi8NCiEgICB0cFsxXSA9IHRpbWUgKDAp OwkJLyogc2V0IG10aW1lIHRvIG5vdyAqLw0KISAgIHV0aW1lIChmaWxlLHRw KTsJCS8qIHNldCB0aGUgdGltZXMgKi8NCiAgICBiZXplcmtfdW5sb2NrIChm ZCxOSUwsbG9jayk7CS8qIHVubG9jayBhbmQgY2xvc2UgbWFpbGJveCAqLw0K ICAgIG1tX25vY3JpdGljYWwgKHN0cmVhbSk7CS8qIHJlbGVhc2UgY3JpdGlj YWwgKi8NCi0tLSAxNzU3LDE3NjMgLS0tLQ0KICAgICAgb2sgPSBOSUw7CQkJ Lyogb29wcyAqLw0KICAgIH0NCiEgICB0cC5hY3RpbWUgPSBzYnVmLnN0X2F0 aW1lOwkvKiBwcmVzZXJ2ZSBhdGltZSAqLw0KISAgIHRwLm1vZHRpbWUgPSB0 aW1lICgwKTsJLyogc2V0IG10aW1lIHRvIG5vdyAqLw0KISAgIHV0aW1lIChm aWxlLCZ0cCk7CQkvKiBzZXQgdGhlIHRpbWVzICovDQogICAgYmV6ZXJrX3Vu bG9jayAoZmQsTklMLGxvY2spOwkvKiB1bmxvY2sgYW5kIGNsb3NlIG1haWxi b3ggKi8NCiAgICBtbV9ub2NyaXRpY2FsIChzdHJlYW0pOwkvKiByZWxlYXNl IGNyaXRpY2FsICovDQo= ---1971628816-2078917053-781353965=:11174-- From owner-pine-info@cac.washington.edu Wed Oct 5 08:02:51 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20625; Wed, 5 Oct 94 08:02:51 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16709; Wed, 5 Oct 94 07:55:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16703; Wed, 5 Oct 94 07:55:15 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AB25711; Wed, 5 Oct 1994 10:52:07 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA25157; Wed, 5 Oct 94 09:55:13 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA00635; Wed, 5 Oct 94 09:55:13 CDT Date: Wed, 5 Oct 1994 09:55:12 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: "Christina E. Latzer" Cc: pine-info@cac.washington.edu Subject: Re: Probably just FAQ, but....help me please?? In-Reply-To: <36suer$4ig@aludra.usc.edu> Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1369 On 4 Oct 1994, Christina E. Latzer wrote: > Please forgive me if I've messed up or made other major errors, but this is the first time I've tried to post anything. > What I'd like to know is if there is any way to save letters from pine to my hard drive instead of to the network, so that I can access the letters from my word processor. Conversely, I'd like to know how to send word processor files as part of my letters in pine. > Thanks in advance. :) > Hi, There are 2 options here, first you can setup a folder (folder-collection) through the configuration screen. With this, you can save messages to folders locally on you PC's hard drive. If you are just trying to save a message to your hard drive, then use 'E' to export the message and specify the filename(and path if desired). Hope this helps... --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Wed Oct 5 08:46:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22196; Wed, 5 Oct 94 08:46:05 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23052; Wed, 5 Oct 94 08:34:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23046; Wed, 5 Oct 94 08:34:46 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsXzR-00001IC; Wed, 5 Oct 94 08:10 PDT To: pine-info@cac.washington.edu From: weave@hopi.dtcc.edu (Ken Weaverling) Subject: Re: Folder Modification Time But... Date: 5 Oct 1994 09:21:08 -0400 Message-Id: <36u984$ean@hopi.dtcc.edu> References: <36tjka$6bg@garuda.csulb.edu> In article <36tjka$6bg@garuda.csulb.edu>, Charles Galt wrote: >I repeatedly get the msg *beep* [Folder modification time but apparently >no changes] since we installed 3.90; any way to stop this? Thanks... chuck What is your system type? We had that exact same problem. I *just* posted patches to fix this problem for DG/UX systems. The utime() call should have a utimbuf struct passed to it on all systems that I've checked on instead of assuming it is a two-element array of time_t vars (longs). Maybe the patch will fix your problem as well, even if you don't have DG/UX. -- Ken Weaverling weave@dtcc.edu |*| My opinions .NEQ. college's position From owner-pine-info@cac.washington.edu Wed Oct 5 10:01:03 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26869; Wed, 5 Oct 94 10:01:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19442; Wed, 5 Oct 94 09:46:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19436; Wed, 5 Oct 94 09:46:16 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsZB3-00000aC; Wed, 5 Oct 94 09:26 PDT To: pine-info@cac.washington.edu From: daveh@vax.ox.ac.uk (Dave Hastings, OUCS) Subject: Pine 3.90 on VAX/VMS Message-Id: <1994Oct5.155656.26464@oxvaxd> Date: 5 Oct 94 15:56:56 BST Hi, Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I tried today I got lots of warnings of the form %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters Comments anyone? Dave -- David Hastings | "Life's too short to waste time VAX Systems Programmer | chitchatting with machines for Oxford University Computing Services | no good reason" - JM daveh@vax.oxford.ac.uk | From owner-pine-info@cac.washington.edu Wed Oct 5 10:06:46 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27348; Wed, 5 Oct 94 10:06:46 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25432; Wed, 5 Oct 94 09:54:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from asl-labs.bc.ca by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25422; Wed, 5 Oct 94 09:54:32 -0700 Received: by asl3.asl-labs.bc.ca (5.4R3.00/200.2.1.5) id AA22646; Wed, 5 Oct 1994 09:52:01 -0700 Date: Wed, 5 Oct 1994 09:51:59 -0700 (PDT) From: "Brian P. Hampson" Subject: Restricted Pine To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We're looking for a way in which pine can only be used to mail to LOCAL users. We wish to make the easy interface available to our clients, but do not wish them using our system as a sending point for mail to the world. Ideally a config option along the line of: local-only Which would disallow the "@" sign in an address. Any suggestions for workarounds with the present format? B. ------------------------------------------------------------------------ |Brian P. Hampson Internet: brian@asl-labs.bc.ca | |System Administration, | |Analytical Service Labs Fidonet : Brian Hampson 1:153/733 | |Vancouver, BC | | | | Specialists in Environmental Chemistry | | | ------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Wed Oct 5 10:24:34 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28373; Wed, 5 Oct 94 10:24:34 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20376; Wed, 5 Oct 94 10:15:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20370; Wed, 5 Oct 94 10:15:48 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsZc9-00000BC; Wed, 5 Oct 94 09:54 PDT To: pine-info@cac.washington.edu From: lachlan@dmp.csiro.au (Lachlan Cranswick) Subject: Possible remote .sig and addressbook? Message-Id: <1994Oct4.124625.22240@dmp.csiro.au> Date: Tue, 4 Oct 1994 12:46:25 GMT Hi All, In the help given with Pine for Windows, it mentions that presently a local signature file and local addressbook has to be used. We would like to get pine for Windows going with IMAP such that it doesn't matter which PC or terminal a users runs pine from. However, with the requirement for a local sig file and local addressbook, this is harder to achieve. Two main queries :- Is (and when) it planned that a future version of pine (and IMAP?) will be able to use remote addressbooks and signature files. How do people use the IMAP pine from different PCs and terminals semi transparently. (i.e., do users download a central addressbook file and sig file?). Ideas and comments appreciated. Lachlan. -- Lachlan Cranswick - CSIRO _--_|\ lachlan@dmp.CSIRO.AU Division of Mineral Products / \ tel +61 3 647 0367 PO Box 124, Port Melbourne \_.--._/ fax +61 3 646 3223 3207 AUSTRALIA v From owner-pine-info@cac.washington.edu Wed Oct 5 10:25:48 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28533; Wed, 5 Oct 94 10:25:48 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26208; Wed, 5 Oct 94 10:14:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26202; Wed, 5 Oct 94 10:14:21 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsZbC-00000IC; Wed, 5 Oct 94 09:53 PDT To: pine-info@cac.washington.edu From: Brad Subject: Unaligned access pid=26005 va=14008a174 pc=1200752f4 ra=1200752e8 type=stq Date: Wed, 5 Oct 1994 16:42:00 +0100 (BST) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is the message I get when using Pine in a DECterm which is sized at something other than the default 24 x 80: Unaligned access pid=26005 va=14008a174 pc=1200752f4 ra=1200752e8 type=stq When I go into an index (and this is the only time it occurs), with the setup different to the default (such as now, it is 48 x 132), this is what I get, and the longer the index, the more I get; sometimes pages of these messages (arranged rather messily, not one per line or anything), if I enter a large index. Does anyone have any idea what may be causing this? Thanks. --Simon. (Well, at least ^_ works in a DECterm!) From owner-pine-info@cac.washington.edu Wed Oct 5 10:56:12 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00768; Wed, 5 Oct 94 10:56:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21307; Wed, 5 Oct 94 10:49:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from THOR.INNOSOFT.COM by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21301; Wed, 5 Oct 94 10:49:30 -0700 Received: from INNOSOFT.COM by INNOSOFT.COM (PMDF V4.3-11 #2001) id <01HHWXGYO02AIRHXJD@INNOSOFT.COM>; Wed, 05 Oct 1994 10:40:22 -0700 (PDT) Date: Wed, 05 Oct 1994 10:40:22 -0700 (PDT) From: Portia Shao Subject: Re: Pine 3.90 on VAX/VMS In-Reply-To: <1994Oct5.155656.26464@oxvaxd> To: daveh@vax.ox.ac.uk Cc: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT On Wed, 5 Oct 1994 daveh@vax.ox.ac.uk wrote: > Hi, > > Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I > tried today I got lots of warnings of the form > > %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters > > Comments anyone? well, this happens on the DEC C compiler too. You have two choices, 1. change the identifier to be shorter everywhere 2. use a #define to define it in os-vms.h It would be nice if they don't show up in the source at all, this is just one of many issues when porting Pine to VMS. > > Dave > -- > > David Hastings | "Life's too short to waste time > VAX Systems Programmer | chitchatting with machines for > Oxford University Computing Services | no good reason" - JM > daveh@vax.oxford.ac.uk | > > /portia portia@innosoft.com Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax 1050 East Garvey Ave South, West Covina, CA 91790 From owner-pine-info@cac.washington.edu Wed Oct 5 11:11:46 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01656; Wed, 5 Oct 94 11:11:46 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27425; Wed, 5 Oct 94 11:00:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27419; Wed, 5 Oct 94 11:00:33 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsaMY-00000bC; Wed, 5 Oct 94 10:42 PDT To: pine-info@cac.washington.edu From: Mike Roch Subject: Invoking pine for newsreading Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: Mime-Version: 1.0 Date: Wed, 5 Oct 1994 16:34:26 GMT In Pine 3.07 I could open a session on a newsgroup from the command line quite concisely: pine -if \*comp.mail.pine The tersest I can manage with 3.90 is pine -if \*\{news/nntp\}comp.mail.pine Am I overlooking something obvious? Mike ============================================================================== Mike Roch, Computer Services Centre, Tel: 0734 318430 The University, Whiteknights, Reading, RG6 2AF Fax: 0734 753094 From owner-pine-info@cac.washington.edu Wed Oct 5 11:26:39 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02574; Wed, 5 Oct 94 11:26:39 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21954; Wed, 5 Oct 94 11:15:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21948; Wed, 5 Oct 94 11:15:41 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsaZE-00000YC; Wed, 5 Oct 94 10:55 PDT To: pine-info@cac.washington.edu From: lmiller@cibnor.cibnor.conacyt.mx (Larry Miller [DT]) Subject: Re: Probably just FAQ, but....help me please?? Date: 5 Oct 1994 09:51:26 -0600 Message-Id: <36ui1u$3p1@cibnor.cibnor.conacyt.mx> References: <36suer$4ig@aludra.usc.edu> Christina E. Latzer (latzer@aludra.usc.edu) wrote: > Please forgive me if I've messed up or made other major errors, but this > is the first time I've tried to post anything. What I'd like to know is > if there is any way to save letters from pine to my hard drive instead of > to the network, so that I can access the letters from my word processor. > Conversely, I'd like to know how to send word processor files as part of > my letters in pine. Assuming you are using Unix pine (?), you need to save the messages in a folder within your directory, then transfer the file to your PC where you can work with it. The transfer procedure depends which terminal program you are using-- give us more details or ask for local help. Sending a message prepared on your local is the reverse procedure-- transfer the file to your unix directory, then (R)ead it into your pine message buffer. Make sure you save the file from your word processor in generic ASCII format. Regards-- Larry Miller Network Administrator Centro de Investigaciones Biologicas del Noroeste, La Paz, BCS Mexico lmiller@cibnor.conacyt.mx lmiller@netcom.com From owner-pine-info@cac.washington.edu Wed Oct 5 11:56:19 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04827; Wed, 5 Oct 94 11:56:19 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28747; Wed, 5 Oct 94 11:45:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shivafs.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28741; Wed, 5 Oct 94 11:45:42 -0700 Received: from admin.kcc.edu by shivafs.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11566; Wed, 5 Oct 94 11:45:40 -0700 Received: from AD99267.kcc.edu by admin.kcc.edu (AIX 3.2/UCB 5.64/4.03) id AA36114; Wed, 5 Oct 1994 14:47:33 -0400 Date: Wed, 5 Oct 1994 14:46:04 -0700 (PDT) From: Greg Richardson To: pine-info@cac.washington.edu Subject: Hazeltine 1500 terminal emulation. X-Sender: ad99267@admin.kcc.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello everyone, I have not found any information concerning this, however please excuse me if I have overlooked it. My question is does Unix Pine support Hazeltine 1500 emulation? Any help would be greatly appreciated. Greg * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * | Greg Richardson | | | Kentucky Christian College ---|--- | | Grayson, KY 41143 | | | USA | | | (606) 474-3000 | | * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * From owner-pine-info@cac.washington.edu Wed Oct 5 12:06:51 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05374; Wed, 5 Oct 94 12:06:51 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23006; Wed, 5 Oct 94 11:53:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22991; Wed, 5 Oct 94 11:53:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsb8K-00000hC; Wed, 5 Oct 94 11:32 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Unaligned access pid=26005 va=14008a174 pc=1200752f4 ra=1200752e8 type=stq Date: Wed, 5 Oct 1994 10:23:53 -0700 Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: Fixed in Pine 3.91... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 5 Oct 1994, Brad wrote: > Date: Wed, 5 OCT 1994 16:42:00 +0100 (BST) > From: Brad > Newgroups: comp.mail.pine > Subject: Unaligned access pid=26005 va=14008a174 pc=1200752f4 ra=1200752e8 type=stq > > This is the message I get when using Pine in a DECterm which is sized > at something other than the default 24 x 80: > > Unaligned access pid=26005 va=14008a174 pc=1200752f4 > ra=1200752e8 type=stq > > When I go into an index (and this is the only time it occurs), with > the setup different to the default (such as now, it is 48 x 132), this is > what I get, and the longer the index, the more I get; sometimes pages of > these messages (arranged rather messily, not one per line or anything), if I > enter a large index. Does anyone have any idea what may be causing this? > Thanks. > > --Simon. > > (Well, at least ^_ works in a DECterm!) > > From owner-pine-info@cac.washington.edu Wed Oct 5 12:11:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05557; Wed, 5 Oct 94 12:11:05 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28969; Wed, 5 Oct 94 11:53:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28961; Wed, 5 Oct 94 11:53:38 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsb8j-00000iC; Wed, 5 Oct 94 11:32 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Possible remote .sig and addressbook? Date: Wed, 5 Oct 1994 10:25:44 -0700 Message-Id: References: <1994Oct4.124625.22240@dmp.csiro.au> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <1994Oct4.124625.22240@dmp.csiro.au> Remote sig and addressbook access is planned, but I can't say for sure when... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 4 Oct 1994, Lachlan Cranswick wrote: > Date: Tue, 4 OCT 1994 12:46:25 GMT > From: Lachlan Cranswick > Newgroups: comp.mail.pine > Subject: Possible remote .sig and addressbook? > > > Hi All, > > In the help given with Pine for Windows, it mentions > that presently a local signature file and local > addressbook has to be used. We would like to get > pine for Windows going with IMAP such that it > doesn't matter which PC or terminal a users runs > pine from. > > However, with the requirement for a local sig file > and local addressbook, this is harder to achieve. > > Two main queries :- > > Is (and when) it planned that a future version of > pine (and IMAP?) will be able to use remote > addressbooks and signature files. > > How do people use the IMAP pine from different > PCs and terminals semi transparently. (i.e., > do users download a central addressbook file and > sig file?). > > Ideas and comments appreciated. > > Lachlan. > > > -- > Lachlan Cranswick - CSIRO _--_|\ lachlan@dmp.CSIRO.AU > Division of Mineral Products / \ tel +61 3 647 0367 > PO Box 124, Port Melbourne \_.--._/ fax +61 3 646 3223 > 3207 AUSTRALIA v > > From owner-pine-info@cac.washington.edu Wed Oct 5 13:22:43 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08969; Wed, 5 Oct 94 13:22:43 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01231; Wed, 5 Oct 94 13:15:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01219; Wed, 5 Oct 94 13:15:52 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qscQM-00000aC; Wed, 5 Oct 94 12:54 PDT To: pine-info@cac.washington.edu From: Xander.Jansen@SURFnet.nl Subject: Re: Pine 3.90 and MH folders. In-Reply-To: <36plk3$rpn@orme1.mt.luth.se> Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: References: <36plk3$rpn@orme1.mt.luth.se> Mime-Version: 1.0 Date: Wed, 5 Oct 1994 10:26:23 GMT Sven et al, On 3 Oct 1994, Sven-Ove Westberg wrote: > Why can not pine read the MH folders? Pine can (I and others use the MH-folder format with Pine for some time now). > I have set the #mh infront of the folder in .pinerc. Some excerpts from my .pinerc: # Path of (local or remote) INBOX, e.g. ={mail.somewhere.edu}inbox # Normal Unix default is the local INBOX (usually /usr/spool/mail/$USER). inbox-path=#mh/inbox (Note that you can also use inbox-path=#MHINBOX) # List of directories where saved-message folders may be. First one is # the default for Saves. Example: Main {host1}mail/[], Desktop mail\[] # Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[] folder-collections="My Mail" #mh/[] > Pine say that the folder is empty but i have messages stored in MH > format in them (eg a separate file for each message). There is this small bug (which will be fixed in 3.91) in the MH-driver that might affect you. If you have your MH-folders somewhere else then in ~/Mail try moving the Path: setting in ~/.mh_profile to the first line in the file. Regards, Xander From owner-pine-info@cac.washington.edu Wed Oct 5 13:43:32 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09627; Wed, 5 Oct 94 13:43:32 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25527; Wed, 5 Oct 94 13:37:27 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25521; Wed, 5 Oct 94 13:37:26 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28013; Wed, 5 Oct 94 13:37:18 -0700 Date: Wed, 5 Oct 1994 13:37:16 -0700 (PDT) From: Terry Gray To: Ben Marcotte Cc: pine-info@cac.washington.edu Subject: Re: Turn off pruning? (Fearing the end of each month) In-Reply-To: <36so5j$oec@pith.uoregon.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Look for an entry in your .pinerc that looks something like this: last-time-prune-questioned=94.10 Then edit the date to be sometime far in the future... -teg On 4 Oct 1994, Ben Marcotte wrote: > Is there a way to turn off the "feature" of monthly pruning- the process of > pine asking you at the begining of each month: > > > Disk space is limited. Delete "sent-mail-MMM-YYYY" ? > > I have looked through pine.conf, .pinerc, man pine and the help in Setup > for any configuration or feature switch that might apply but I can find > nothing. What am I missing? I find this to be the most agrivating part > of an otherwise friendly program. > > Ben Marcotte > > ============================================================================== > Ben Marcotte ben@chinook.uoregon.edu (503) 346-4592 > ============================================================================== > > From owner-pine-info@cac.washington.edu Wed Oct 5 13:52:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10075; Wed, 5 Oct 94 13:52:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01709; Wed, 5 Oct 94 13:40:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01703; Wed, 5 Oct 94 13:39:59 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28050; Wed, 5 Oct 94 13:39:54 -0700 Date: Wed, 5 Oct 1994 13:39:53 -0700 (PDT) From: Terry Gray To: "Kenny Wickstrom (x2349)" Cc: Ah! My Goddess , pine-info@cac.washington.edu Subject: Re: === How to set nntp in .pinerc in order to read news? === In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII FYI: For the normal nntp situation, you can actually omit setting the news-collections variable explicity. If you just set "nntp-server" then Pine will infer the typical news-collections entry. -teg On Wed, 5 Oct 1994, Kenny Wickstrom (x2349) wrote: > On 5 Oct 1994, Ah! My Goddess wrote: > > > Hi netters, > > Just wondering how to set up nntp server in the .pinerc in order to read and > > post news through the pine? > > Any help is being appreciated. > > Hi, > > You need to set these two lines in your .pinerc (either through editing > or through the configuration screen. (One note: I think you only supply > *{ttd1.ttd.teradyne.com/nntp}[] on the news-collection line and pine > fills in the subscribed groups.) Also, to state the obvious, you must > change ttd1.ttd.teradyne.com to whatever you nntp server is. > > nntp-server = ttd1.ttd.teradyne.com > news-collections = Subscribed-Groups *{ttd1.ttd.teradyne.com/nntp}[] > > Hope this helps, > --------------------------------------------------------------------------- > |/ | | > |\enny |/\|ickstrom (kenny@ttd.teradyne.com) > ======== > // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. > // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 > // ===== || // || // || \\// || || ===== (708)940-9000 > // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) > Telecommunications Division // > _// > > From owner-pine-info@cac.washington.edu Wed Oct 5 16:02:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16000; Wed, 5 Oct 94 16:02:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28562; Wed, 5 Oct 94 15:51:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28555; Wed, 5 Oct 94 15:51:10 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsetP-000008C; Wed, 5 Oct 94 15:32 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Procmail and Pine3.90 Date: Wed, 05 Oct 1994 23:18:06 +0100 Message-Id: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > I'm running procmail but I'm getting lots of lock file errors. > Can anyone help? Questions relating to procmail are usually answered a lot faster if you direct them to the list You were probably trying to create lockfiles in a spool directory lacking the privilege to do so. You should deliver to your home directory. Use the inbox-path variable to teach Pine about it. From owner-pine-info@cac.washington.edu Wed Oct 5 16:23:40 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16666; Wed, 5 Oct 94 16:23:40 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29186; Wed, 5 Oct 94 16:15:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29180; Wed, 5 Oct 94 16:15:08 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsfDa-00000AC; Wed, 5 Oct 94 15:53 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: does mbox driver work in 3.90 Date: Wed, 5 Oct 1994 15:33:18 -0700 Message-Id: References: <36uqva$lb7@CUBoulder.Colorado.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36uqva$lb7@CUBoulder.Colorado.EDU> Mail is only pulled into ~/mbox if the file already exists, i.e. you need to "touch ~/mbox" or some similar... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 5 Oct 1994, Jeff Scarborough wrote: > Date: 5 OCT 1994 18:23:38 GMT > From: Jeff Scarborough > Newgroups: comp.mail.pine > Subject: does mbox driver work in 3.90 > > > According to the faq you can force all new mail to be pulled into ~/mbox > by linking in the "mbox" driver when you build pine. I executed the > following: > > ./build EXTRADRIVERS=mbox a32 > > It seems to have added the mboxdriver to linkage.[ch] and it built fine, > but it seems to have had no effect. Mail does not get pulled into ~/mbox > ever. Am I missing a step? Does it even work? > > -- > Jeff Scarborough Jeff.Scarborough@Colorado.EDU > University of Colorado Computing & Network Services > Campus Box 455 Boulder, Colorado 80309-0455 > > From owner-pine-info@cac.washington.edu Wed Oct 5 16:23:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16664; Wed, 5 Oct 94 16:23:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05143; Wed, 5 Oct 94 16:15:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05137; Wed, 5 Oct 94 16:15:00 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsfBQ-000008C; Wed, 5 Oct 94 15:51 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: ...filters [FAQ] Date: Wed, 05 Oct 1994 23:34:40 +0100 Message-Id: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Marcos Rubinstein wrote on Aug 29: > Yes, as an end user of pine, with limmited knowledge of Unix, I will > love ONE program that would let me do all of my mail houskeeping. > But, alas, I can understand the point raised by those who consider > pine an inapropiate (and inefective) way to filter mail. What we > need is somebody that will take procmail and make it as user > friendly as pine is... Procmail is an efficient mail thrower with its own concise language and very complex capabilities. You don't realize what a magnitude of tasks its users have been delegating to procmail. For the simplest applications like sorting out list mails the syntax is very easy and documented in the manual. But even here you will have to fine-tune the regular expressions to fit your needs. Also the .forward/.maildelivery setup is quite different from site to site. Therefore I would say, a comprehensive (y/n)?-frontend would require artificial intelligence. From owner-pine-info@cac.washington.edu Wed Oct 5 16:33:22 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17010; Wed, 5 Oct 94 16:33:22 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05296; Wed, 5 Oct 94 16:21:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05290; Wed, 5 Oct 94 16:21:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsfJz-00000BC; Wed, 5 Oct 94 16:00 PDT To: pine-info@cac.washington.edu From: sadistic@yar.cs.wisc.edu (Ah! My Goddess) Subject: Hey, how to find out the local nntp server? Date: 5 Oct 1994 22:31:40 GMT Message-Id: <36v9gc$43t@spool.cs.wisc.edu> Hey how to find out where is the local nntp server for pine? Ant help will be appreciated. ano hohoemi wo wasurenaide Don't forget that smile! -------------------------- ------------------------ ano hohoemi wo wasurenaide Don't forget that smile! "Forget your worries and ... gimme your smile" ... kokoro no fuyu ni sayonarashite Say goodbye to the winter of your heart hashiridasoo atarashiashita he Let's start running to a new tomorrow 25 ji suna no ue ni We stopped at 1:00 am kuruma wo tomete on the beach... katariakashita ano natsu We talked all night that summer... nurui KOORA shikanakute mo Even though we had only warm cola, yume dake de tanoshikatta I enjoyed that dream. omoidashite... Please remember... tsumazuita toki niha So whenever you stumble, den'wa wo shite ne give me a call, okay? * "Open you heart" Open your heart, kaze wo kan'jite feel the wind akirame wo te ni shinaide Don't take up despair! toukai ga kureta POOKAA "face" Throw the poker face the city has given umi ni suteteshimaou you into the sea. ano hohoemi wo wasurenaide Don't forget that smile! itsumo kagayaitetai I want us to always be shining kokoro no fuyu ni sayonarashite Say goodbye to the winter of your heart hashiridasoo atarashiashita he Let's start running to a new tomorrow RENGA iro no sora We looked up at an angle and saw wo nanamenimiagete a brick-red sky. kuchibue fuita "my home town" We went whistling through my home town. yaritai koto hoshiimono mo There are many things that I want, and kakaekirenaihodode things I want to do, that can't be held on setsunasa no HAADORU koerareta ne to. You have overcome Depression's hurdles ima mo dekiru yo before. You can do it now. "Open your heart" hitamukina Open your heart anata no hitomi (me) ga sukidatta I loved your intense pupils (eyes) kodoku na jikan dakishimete Embrace me in your hour of loneliness. hito ha otona ni naru kara Just because people become adults... ano hohoemi wo wasurenaide Don't forget that smile! itsumo kagayaitetai I want us to always be shining mou nanimo mayoukoto naku You shouldn't have any doubts hashiridasoo atarashiashita he Let's start running to a new tomorrow "You've got to open your heart" ... "When ever you feel blue" ... "Forget your worries and ... gimme your smile" ... kokoro no fuyu ni sayanarashite Say goodby to the winter of your heart hashiridasoo atarashiashita he Let's start running to a new tomorrow * Repeat From owner-pine-info@cac.washington.edu Wed Oct 5 17:43:20 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19823; Wed, 5 Oct 94 17:43:20 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01159; Wed, 5 Oct 94 17:36:26 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01153; Wed, 5 Oct 94 17:36:23 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsgUd-000008C; Wed, 5 Oct 94 17:15 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Sendmail variants Date: Thu, 06 Oct 1994 00:59:26 +0100 Message-Id: References: <36n38q$rl1@cs.uwp.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Gabriel Millerd wrote on October 2: > This will work GREAT with pine, since pine allows you to specify > your sendmail program in the $HOME/.pinerc file. I am afraid you confused this with Mail's ~/.mailrc. As far as I know neither Pine nor Elm allow by default every user to customize the sendmail program to use. Often it is desirable for Unix virtuosos to plug in their own sendmail wrapper that does some additional postprocessing on the composed message before sending it out. For Pine (and similarly for Elm) this can be achieved by compiling in "${SENDMAIL=/usr/lib/sendmail}" instead of /usr/lib/sendmail. Now, if I setenv SENDMAIL mysendmail and have such a script in my path it will be used. This is exploiting a feature of sh's. Such a script can do all sorts of fancy stuff. Gabriel Millerd: The object of the program is to shuffle my signature > files around as frequently as possible. Nick Sushkin: In pine 3.90, is it possible to disable content encoding > of 8-bit characters? Paulo Magalhaes: I would like to run a script everytime that pine > sends a message. Using default-fcc= seemed > like a good idea, but I don't seem to be able to do this... Here is a sample script to do all of this #!/usr/local/bin/procmail -m # No QP-encoding for certain recipients :2 fbw ^Content-Transfer-Encoding: quoted-printable ^To:.*(cs.tu|zib|fu|hu)-berlin.de | mmencode -undo -quoted-printable :a fhw | formail -I 'Content-Transfer-Encoding: 8bit' # Append one of my ten signatures :0 fbw | gawk 'BEGIN { ARGV[2] = "sig" systime() % 10 } /^/' - sig # Send out the mail :0c ! -oi -t # And file a copy :B: pine pine-mail DEFAULT=sent From owner-pine-info@cac.washington.edu Wed Oct 5 18:19:14 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21017; Wed, 5 Oct 94 18:19:14 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07697; Wed, 5 Oct 94 18:12:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07691; Wed, 5 Oct 94 18:12:40 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsh2c-000008C; Wed, 5 Oct 94 17:50 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Registered Mail? Date: Thu, 06 Oct 1994 01:41:21 +0100 Message-Id: References: <36qrn1$60b@piaget.moe.ac.sg> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Is it possible to send REGISTERED mail in pine or for that matter in > unix? Not really. In S)etup C)onfig you can add Return-Receipt-To to the customized-hdrs and then while composing a message you can enter your name in the ^R)eturn-R: line to request a delivery notification which is about as close as you can get. This return receipt has no legal value and from many sites it will not even be sent to you. From owner-pine-info@cac.washington.edu Wed Oct 5 18:30:09 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21327; Wed, 5 Oct 94 18:30:09 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01944; Wed, 5 Oct 94 18:21:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01938; Wed, 5 Oct 94 18:21:31 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qshC6-00000IC; Wed, 5 Oct 94 18:00 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Sendmail variants Date: Thu, 06 Oct 1994 01:44:29 +0100 Message-Id: References: <36n38q$rl1@cs.uwp.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > This will work GREAT with pine, since pine allows you to specify > your sendmail program in the $HOME/.pinerc file. I am afraid you confused this with Mail's ~/.mailrc. As far as I know neither Pine nor Elm allow by default every user to customize the sendmail program to use. Often it is desirable for Unix virtuosos to plug in their own sendmail wrapper that does some additional postprocessing on the composed message before sending it out. For Pine (and similarly for Elm) this can be achieved by compiling in "${SENDMAIL=/usr/lib/sendmail}" instead of /usr/lib/sendmail. Now, if I setenv SENDMAIL mysendmail and have such a script in my path it will be used. This is exploiting a feature of sh's. Such a script can do all sorts of fancy stuff. Gabriel Millerd: The object of the program is to shuffle my signature > files around as frequently as possible. Nick Sushkin: In pine 3.90, is it possible to disable content encoding > of 8-bit characters? Paulo Magalhaes: I would like to run a script everytime that pine > sends a message. Using default-fcc= seemed > like a good idea, but I don't seem to be able to do this... Here is a sample script to do all of this #!/usr/local/bin/procmail -m # No QP-encoding for certain recipients :2 fbw ^Content-Transfer-Encoding: quoted-printable ^To:.*(cs.tu|zib|fu|hu)-berlin.de | mmencode -undo -quoted-printable :a fhw | formail -I 'Content-Transfer-Encoding: 8bit' # Append one of my ten signatures :0 fbw | gawk 'BEGIN { ARGV[2] = "sig" systime() % 10 } /^/' - sig # Send out the mail :0c ! "$@" # And file a copy :B: pine pine-mail DEFAULT=sent From owner-pine-info@cac.washington.edu Wed Oct 5 18:41:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21610; Wed, 5 Oct 94 18:41:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07990; Wed, 5 Oct 94 18:31:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07983; Wed, 5 Oct 94 18:31:34 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qshMf-00000JC; Wed, 5 Oct 94 18:11 PDT To: pine-info@cac.washington.edu From: nancym@chinook.halcyon.com (Nancy McGough) Subject: cmsg cancel <36ut98$mh4@news.halcyon.com> Control: cancel <36ut98$mh4@news.halcyon.com> Date: 5 Oct 1994 23:30:56 GMT Message-Id: <36vcvg$11v@news.halcyon.com> cancel <36ut98$mh4@news.halcyon.com> in newsgroup comp.mail.pine -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Wed Oct 5 18:50:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21797; Wed, 5 Oct 94 18:50:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02248; Wed, 5 Oct 94 18:42:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02242; Wed, 5 Oct 94 18:42:49 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qshZf-00000AC; Wed, 5 Oct 94 18:24 PDT To: pine-info@cac.washington.edu From: ben@chinook.uoregon.edu (Ben Marcotte) Subject: Re: Turn off pruning? (Fearing the end of each month) Date: 6 Oct 1994 01:12:12 GMT Message-Id: <36vitc$l8d@pith.uoregon.edu> References: <36so5j$oec@pith.uoregon.edu> Terry Gray (gray@cac.washington.edu) wrote: : Look for an entry in your .pinerc that looks something like this: : last-time-prune-questioned=94.10 : Then edit the date to be sometime far in the future... : -teg : On 4 Oct 1994, Ben Marcotte wrote: : > Is there a way to turn off the "feature" of monthly pruning- the process of : > pine asking you at the begining of each month: : > : > : > Disk space is limited. Delete "sent-mail-MMM-YYYY" ? : > : > I have looked through pine.conf, .pinerc, man pine and the help in Setup : > for any configuration or feature switch that might apply but I can find : > nothing. What am I missing? I find this to be the most agrivating part : > of an otherwise friendly program. : > : > Ben Marcotte While that would probably work for one user, I was looking for a config flag to put in the system /usr/local/lib/pine.conf, if possible. I don't want any of our users to have to put up with the prune prompting. Thanks, Ben Marcotte ============================================================================== Ben Marcotte ben@chinook.uoregon.edu (503) 346-4592 ============================================================================== From owner-pine-info@cac.washington.edu Wed Oct 5 19:39:16 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23017; Wed, 5 Oct 94 19:39:16 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09016; Wed, 5 Oct 94 19:32:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09010; Wed, 5 Oct 94 19:32:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsiKk-000008C; Wed, 5 Oct 94 19:13 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 00:59:53 GMT Message-Id: <36vi69$3aa@news.halcyon.com> References: <36s9o1$153@trance.helix.net> <36t8ok$n8h@mp.cs.niu.edu> Since Pine 3.90 is the first widely used Mailer-and-Newsreader-in-one, it makes sense that it's dealing with header issues that haven't been an issue before. Ideally when a message is received in mail you would be able to tell whether it was mailed only or both posted and mailed. That way when you reply you would know whether it is appropriate to reply by posting as well as mailing. (Proper netiquette is to not post private mail.) Currently I don't think there's any uniform way to determine this from the headers (please let me know if there is). It would be nice if there were standard headers for both mail and news messages which told: [1] where the message was mailed (except Bcc) [2] where the message was posted [3] where the message originated, i.e., if it's a reply or forwarded message where the message that is being replied to or forwarded was (newsgroup(s), mailing list(s), non-mailing-list mail) To:_ and Cc:_ mean [1] most of the time, but some posted messages might have these headers and not actually have been mailed to the folks on the To:_ and/or Cc:_ lines. This would happen with a newsreader that doesn't honor To:_ and/or Cc:_ lines and doesn't strip them out. For posted messages Newsgroups:_ satisfies [2]. For mailed messages Newsgroups:_ sometimes means [2] only, sometimes means [3] only, and sometimes means [2] and [3]. For the future it might be a good to have standard headers for both mail and news for [2] and [3]. What do people think? Of course anything adopted would have to be backward compatible with existing RFCs. Looking forward to a discussion, Nancy (not affiliated with the pine team; ex newsreader designer) In comp.mail.pine rickert@cs.niu.edu (Neil Rickert) writes: >In David L Miller writes: > >>It seems from discussions with other users that the problem is that some >>(many?) newsreaders supply too much information when replying via mail. That >>is, they include a Newsgroups: header even though the message was not posted >>to the newsgroup! > >This is not "too much information." The newsgroups header on email >is informative, and what else is the purpose of information but to >be informative. > >> Pine sees the Newsgroups: header and assumes that the >>message was posted as well as mailed. > >Then Pine is stupid for making such an assumption. > >> AFAIK, there is nothing that Pine can >>do to tell that the Newsgroups: header is a lie... > >The "Newsgroups:" header is not a lie. There is nothing in RFC822 which >forbids a "Newsgroups:" header in email. The header informs the email >recipient as to the origin of the discussion. -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Wed Oct 5 19:55:24 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23305; Wed, 5 Oct 94 19:55:24 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03258; Wed, 5 Oct 94 19:47:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03252; Wed, 5 Oct 94 19:47:09 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsiZR-00000BC; Wed, 5 Oct 94 19:28 PDT To: pine-info@cac.washington.edu From: r02kar@einstein.desy.de (Karsten Kuenne) Subject: Re: Pine 3.90 and MH folders. Date: 05 Oct 1994 20:04:25 GMT Message-Id: References: <36plk3$rpn@orme1.mt.luth.se> In-Reply-To: Xander.Jansen@SURFnet.nl's message of Wed, 5 Oct 1994 10:26:23 GMT >>>>> "Xander" == Xander Jansen writes: Xander> Sven et al, On 3 Oct 1994, Sven-Ove Westberg wrote: >> Why can not pine read the MH folders? Xander> Pine can (I and others use the MH-folder format with Pine for Xander> some time now). >> I have set the #mh infront of the folder in .pinerc. Xander> Some excerpts from my .pinerc: Xander> # Path of (local or remote) INBOX, Xander> e.g. ={mail.somewhere.edu}inbox # Normal Unix default is the Xander> local INBOX (usually /usr/spool/mail/$USER). Xander> inbox-path=#mh/inbox Xander> (Note that you can also use inbox-path=#MHINBOX) Xander> # List of directories where saved-message folders may Xander> be. First one is # the default for Saves. Example: Main Xander> {host1}mail/[], Desktop mail\[] # Syntax: optnl-label Xander> {optnl-imap-hostname}optnl-directory-path[] Xander> folder-collections="My Mail" #mh/[] >> Pine say that the folder is empty but i have messages stored in MH >> format in them (eg a separate file for each message). Xander> There is this small bug (which will be fixed in 3.91) in the Xander> MH-driver that might affect you. If you have your MH-folders Xander> somewhere else then in ~/Mail try moving the Path: setting in Xander> ~/.mh_profile to the first line in the file. And also take care that there is only ONE space between "Path:" and the value. Otherwise the MH driver won't accept the setting. (Another small bug in the MH driver parsing routine for .mh_profile) Karsten. -- //////////////////////////////////////////////////////////////////// Karsten Kuenne, DESY (-R2-), Notkestr. 85, 22607 Hamburg, Germany phone: +49-40-8998-3315 fax: +49-40-8998-4429 e-mail: , From owner-pine-info@cac.washington.edu Wed Oct 5 20:26:16 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23963; Wed, 5 Oct 94 20:26:16 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09627; Wed, 5 Oct 94 20:19:05 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09621; Wed, 5 Oct 94 20:19:03 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsj3n-00000IC; Wed, 5 Oct 94 19:59 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 5 Oct 1994 21:48:41 -0500 Message-Id: <36voi9$rmq@mp.cs.niu.edu> References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> In article <36vi69$3aa@news.halcyon.com> Nancy McGough writes: >Since Pine 3.90 is the first widely used Mailer-and-Newsreader-in-one, >it makes sense that it's dealing with header issues that haven't been >an issue before. The particular issue should not be an issue now. It is because of a design flaw in pine. Let's not try to reinvent the world just to avoid admitting that this is a design flaw. >Ideally when a message is received in mail you would be able to tell >whether it was mailed only or both posted and mailed. If you received the message in mail, then it was mailed. If you want to know whether the originator of the message also posted it in a public forum somewhere -- then you are asking for the ability to read minds of people you have never met. That is impossible. > That way when >you reply you would know whether it is appropriate to reply by posting >as well as mailing. (Proper netiquette is to not post private mail.) If you received the message by mail, and there is no indication that it was also posted, proper netiquette is to assume that it was mail. You do not need any special headers for that. >Currently I don't think there's any uniform way to determine this from >the headers (please let me know if there is). One can make intelligent guesses. Cnews and INN have distinctive message IDs which strongly suggest that the message originated in news. But it would be unwise to count on this. >It would be nice if there were standard headers for both mail and news >messages which told: >[1] where the message was mailed (except Bcc) Why not consider usenet posting as equivalent to "Bcc: everybody". That way you can treat it as mail, and your ignorance that it was posted completely conforms to your desired ignorance as to the content of the Bcc: addresses. >[3] where the message originated, i.e., if it's a reply or forwarded > message where the message that is being replied to or forwarded > was (newsgroup(s), mailing list(s), non-mailing-list mail) Usually the "Received:" header in mail and the "Path:" header in usenet news can give you this information. >To:_ and Cc:_ mean [1] most of the time, but some posted messages >might have these headers and not actually have been mailed to the >folks on the To:_ and/or Cc:_ lines. This would happen with a >newsreader that doesn't honor To:_ and/or Cc:_ lines and doesn't strip >them out. That happens. It can also happen with email. It is quite easy to create an email message with "To:" and "Cc:" headers which do not correspond to actual recipients. I suppose this is no worse than a person sending a paper letter addressed to his lawyer with a "Cc:" to another person, but the letter is only sent to the other person and not to the lawyer. >For posted messages Newsgroups:_ satisfies [2]. For mailed messages >Newsgroups:_ sometimes means [2] only, sometimes means [3] only, >and sometimes means [2] and [3]. "Newsgroups:" has a defined meaning for usenet, but has no defined meaning for email. As a result, people are allowed to use it for whatever they like. I prefer to retain the "Newsgroups:" header in email replies to postings, and sometimes even in email replies to email that has a "Newsgroups:" headers, and presumably originated on usenet. >For the future it might be a good to have standard headers for both >mail and news for [2] and [3]. What do people think? Of course anything >adopted would have to be backward compatible with existing RFCs. Perhaps. But you will probably never get it adopted. There are too many existing products which do not honor these to-be-invented headers, and most people are satisfied with things the way they are. From owner-pine-info@cac.washington.edu Wed Oct 5 20:38:22 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24205; Wed, 5 Oct 94 20:38:22 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03845; Wed, 5 Oct 94 20:32:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03839; Wed, 5 Oct 94 20:32:01 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsjEs-00000JC; Wed, 5 Oct 94 20:11 PDT To: pine-info@cac.washington.edu From: stevezim@crl.com (Steve Zimmerman) Subject: Re: === How to set nntp in .pinerc in order to read news? === Date: 5 Oct 1994 19:58:38 -0700 Message-Id: <36vp4u$j9v@crl7.crl.com> References: <36tn9k$fi8@spool.cs.wisc.edu> "Handles" are for CB & Ham radio. How about supplying a name along with the kana? Steve Zimmerman From owner-pine-info@cac.washington.edu Wed Oct 5 20:45:15 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24315; Wed, 5 Oct 94 20:45:15 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09912; Wed, 5 Oct 94 20:36:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09906; Wed, 5 Oct 94 20:36:50 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsjN5-000008C; Wed, 5 Oct 94 20:19 PDT To: pine-info@cac.washington.edu From: Mark Crispin Subject: Re: WARNING FOR PINE 3.90 USERS!!!!! Date: Wed, 5 Oct 1994 20:04:24 -0700 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36t8ok$n8h@mp.cs.niu.edu> On 4 Oct 1994, Neil Rickert wrote: > The "Newsgroups:" header is not a lie. There is nothing in RFC822 which > forbids a "Newsgroups:" header in email. The header informs the email > recipient as to the origin of the discussion. Strictly speaking, headers which are not specified defined by RFC822 are either a ``extension-field'' or ``user-defined-field''. There are two differences between these two: 1) extension-field is one that is officially registered, and never begins with X-. 2) user-defined-field is any name that is not an RFC822 field or an extension-field, and may begin with X-. Any user-defined-field which does not begin with X- may be preempted by an extension-field definition at any time. By definition, a user-defined-field is private and may be interpreted by each implementation as it wishes. There is no definition of an extension-field of Newsgroups: in the RFC822 context. It is defined as a *news* field, but that is a separate context from RFC822 and in fact an entirely different protocol specification. Consequently, in the RFC822 context it is a user-defined-field. An RFC822 implementation can do whatever it pleases with any user-defined-field! Pine treats the RFC822 context user-defined-field of Newsgroups: as being identical to the news context field of Newsgroups:. Your claim is that the interpretation of Newsgroups: is different in mail than it is in news. There is nothing in the protocol specifications to support your position or, for that matter, Pine's position; it is up to each implementation. This does not mean that the *suggestion* to treat Newsgroups: differently when reading mail than when reading news is rejected. I am not aware of any decision being made either way. However, whether it is accepted or rejected will be on its own merits, and not by virtue of a claim that the specifications say something that they don't. From owner-pine-info@cac.washington.edu Wed Oct 5 20:54:33 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24485; Wed, 5 Oct 94 20:54:33 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04041; Wed, 5 Oct 94 20:47:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04035; Wed, 5 Oct 94 20:47:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsjVv-00000MC; Wed, 5 Oct 94 20:29 PDT To: pine-info@cac.washington.edu From: Mark Crispin Subject: Re: does mbox driver work in 3.90 Date: Wed, 5 Oct 1994 20:08:47 -0700 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36uqva$lb7@CUBoulder.Colorado.EDU> There is a bug in the mbox driver of 3.90 that *empty* ~/mbox files are ignored. As a workaround, put a single message into it and it will start working. The fix is in the latest IMAP toolkit on ftp.cac.washington.edu, file mail/imap.tar.Z, and will also be in Pine 3.91 which is coming soon!!!! -- Mark -- On 5 Oct 1994, Jeff Scarborough wrote: > > > According to the faq you can force all new mail to be pulled into ~/mbox > by linking in the "mbox" driver when you build pine. I executed the > following: > > ./build EXTRADRIVERS=mbox a32 > > It seems to have added the mboxdriver to linkage.[ch] and it built fine, > but it seems to have had no effect. Mail does not get pulled into ~/mbox > ever. Am I missing a step? Does it even work? > > -- > Jeff Scarborough Jeff.Scarborough@Colorado.EDU > University of Colorado Computing & Network Services > Campus Box 455 Boulder, Colorado 80309-0455 > From owner-pine-info@cac.washington.edu Wed Oct 5 21:18:39 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25053; Wed, 5 Oct 94 21:18:39 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10334; Wed, 5 Oct 94 21:07:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10318; Wed, 5 Oct 94 21:06:59 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsjoL-000008C; Wed, 5 Oct 94 20:48 PDT To: pine-info@cac.washington.edu From: John Gardiner Myers Subject: Re: MIME Date: Wed, 5 Oct 1994 23:11:36 -0400 Message-Id: References: <36sdf3$kgk@linda.teleport.com> In-Reply-To: Roman Czyborra writes: > You need to pipe to munpack -t to decode text attachments also. > I think the -t option was introduced in mpack-1.3. Starting with version 1.4, mpack can detect and decode Pine attachments without being given the -t switch. From owner-pine-info@cac.washington.edu Wed Oct 5 21:35:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25449; Wed, 5 Oct 94 21:35:04 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04633; Wed, 5 Oct 94 21:28:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04627; Wed, 5 Oct 94 21:28:10 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsk9H-000008C; Wed, 5 Oct 94 21:09 PDT To: pine-info@cac.washington.edu From: ez017400@dale.ucdavis.edu (Hemang Patel) Subject: Custom Headers Date: 6 Oct 1994 00:20:15 GMT Message-Id: <36vfrv$9vs@mark.ucdavis.edu> For a while now, I have been trying to define custom headers in PINE 3.90 to no avail. Can anyone please help me? The help built into pine is no help. TIA. -- _________________________________________ Hemang Patel hcpatel@dale.ucdavis.edu From owner-pine-info@cac.washington.edu Wed Oct 5 22:04:03 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25978; Wed, 5 Oct 94 22:04:03 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10996; Wed, 5 Oct 94 21:58:16 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10990; Wed, 5 Oct 94 21:58:13 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qskc8-000008C; Wed, 5 Oct 94 21:39 PDT To: pine-info@cac.washington.edu From: scarboro@quit.Colorado.EDU (Jeff Scarborough) Subject: does mbox driver work in 3.90 Date: 5 Oct 1994 18:23:38 GMT Message-Id: <36uqva$lb7@CUBoulder.Colorado.EDU> According to the faq you can force all new mail to be pulled into ~/mbox by linking in the "mbox" driver when you build pine. I executed the following: ./build EXTRADRIVERS=mbox a32 It seems to have added the mboxdriver to linkage.[ch] and it built fine, but it seems to have had no effect. Mail does not get pulled into ~/mbox ever. Am I missing a step? Does it even work? -- Jeff Scarborough Jeff.Scarborough@Colorado.EDU University of Colorado Computing & Network Services Campus Box 455 Boulder, Colorado 80309-0455 From owner-pine-info@cac.washington.edu Wed Oct 5 22:07:08 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26045; Wed, 5 Oct 94 22:07:08 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05131; Wed, 5 Oct 94 22:02:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05125; Wed, 5 Oct 94 22:02:00 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qske1-00000AC; Wed, 5 Oct 94 21:41 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: New user requires help. Date: 5 Oct 1994 17:52:10 GMT Message-Id: <36up4a$kha@news.halcyon.com> References: keithc@gx2.uk.mdis.com (Keith Cordon) writes: >Can someone please email me with information on how to stop the creation >of enourmous .pine-debug files everytime I use pine. Start pine with the -d0 flag which means turn debugging off. I have the following alias in my ~/.cshrc file so it automatically happens each time I type pine. alias pine "\pine -d0" Hope this helps, Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Wed Oct 5 22:54:13 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26928; Wed, 5 Oct 94 22:54:13 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11606; Wed, 5 Oct 94 22:47:12 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11600; Wed, 5 Oct 94 22:47:09 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qslOn-00000IC; Wed, 5 Oct 94 22:29 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: WARNING FOR PINE 3.90 USERS!!!!! Date: 6 Oct 1994 00:10:38 -0500 Message-Id: <3700se$2p3@mp.cs.niu.edu> References: In Mark Crispin writes: >On 4 Oct 1994, Neil Rickert wrote: >> The "Newsgroups:" header is not a lie. There is nothing in RFC822 which >> forbids a "Newsgroups:" header in email. The header informs the email >> recipient as to the origin of the discussion. >Strictly speaking, headers which are not specified defined by RFC822 are >either a ``extension-field'' or ``user-defined-field''. There are two >differences between these two: > 1) extension-field is one that is officially registered, and never begins > with X-. > 2) user-defined-field is any name that is not an RFC822 field or an > extension-field, and may begin with X-. Any user-defined-field which > does not begin with X- may be preempted by an extension-field > definition at any time. By definition, a user-defined-field is > private and may be interpreted by each implementation as it wishes. Agreed. >There is no definition of an extension-field of Newsgroups: in the RFC822 >context. It is defined as a *news* field, but that is a separate context >from RFC822 and in fact an entirely different protocol specification. >Consequently, in the RFC822 context it is a user-defined-field. An RFC822 >implementation can do whatever it pleases with any user-defined-field! >Pine treats the RFC822 context user-defined-field of Newsgroups: as being >identical to the news context field of Newsgroups:. No, that is not correct. The RFC1036 (news context) only supplies an interpretation of "Newsgroups:" when it appears in a news article. RFC1036 does not provide any interpretation of "Newsgroups:" when it appears in an email message. If Pine assigns an interpretation to "Newsgroups:" in an email message, that is Pine's own invention, and it is not in any way taking the RFC1036 interpretation. Now perhaps you can say that Pine treats "Newsgroups:" in mail as analogous to its use in usenet, but you cannot say that it treats it identically. > Your claim is that >the interpretation of Newsgroups: is different in mail than it is in news. Yes, of course the interpretation is different. There is an interpretation in news, and there is no interpretation in mail. If you don't think that is different, then your way of thinking is quite strange. >There is nothing in the protocol specifications to support your position >or, for that matter, Pine's position; it is up to each implementation. I agree that the protocol does not specify. That is why it was wrong of a previous author to say that the Newsgroups: line in mail was a lie. >This does not mean that the *suggestion* to treat Newsgroups: differently >when reading mail than when reading news is rejected. I am not aware of If the author's of Pine want to treat "Newsgroups:" the way they do - that is their choice. I have no particular position for or against this. I object to them labelling the appearance of "Newsgroups:" in mail as a lie. Generally speaking, when there is no rule, one goes by the common practice, and the common practice for some time has been for email responses to news to include the "Newsgroups:" header. Thus the header has a meaning by an analogue of common law. If the Pine author's wish to change this, they should ideally go the RFC route to do so. I think such an attempt would fail, but they have the right to try. Right now the Pine authors are in the position of the soldier marching out of step with the rest of the brigade, but declaring that he is in step and everybody else is out of step. If the Pine authors can persuade the rest of the world to fall in step with them -- good luck to them. But let's not distort the picture. They made an unwise design decision which has embarrassed several users, and they should not try to shift the blame. Personally, I don't care very much. I install Pine because some of my users ask for it. Except for testing the installation, I do not use Pine. I consider it to be one of the biggest pieces of junk software and poor design that I have encountered. From owner-pine-info@cac.washington.edu Thu Oct 6 01:07:38 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29716; Thu, 6 Oct 94 01:07:38 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07395; Thu, 6 Oct 94 01:02:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from leeman.york.ac.uk by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07389; Thu, 6 Oct 94 01:02:30 -0700 Received: from tower.york.ac.uk by leeman.york.ac.uk with SMTP (PP) id <15499-0@leeman.york.ac.uk>; Thu, 6 Oct 1994 08:48:38 +0100 Received: by tower.york.ac.uk (940715.SGI.52/931108.SGI.ANONFTP) for @leeman.york.ac.uk:pine-info@cac.washington.edu id AA20480; Thu, 6 Oct 94 09:02:21 +0100 Date: Thu, 6 Oct 1994 09:02:20 +0100 From: Mike Brudenell X-Sender: pmb1@tower.york.ac.uk To: pine-info@cac.washington.edu Subject: Re: does mbox driver work in 3.90 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII And if you're not afraid of getting your hands dirty by touching the source code you can even make the mbox driver create the "mbox" file if it doesn't already exist :-) ------------------------------------------------------------------------------ Mike Brudenell E-mail: pmb1@unix.york.ac.uk The Computing Service Phone: (+44) 1904 433811 University of York FAX: (+44) 1904 432767 Heslington York YO1 5DD U.K. On Wed, 5 Oct 1994, David L Miller wrote: > > Mail is only pulled into ~/mbox if the file already exists, i.e. you need to > "touch ~/mbox" or some similar... > > |\ | |\/| 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, JE-20 > 4545 15th Ave NE, Seattle WA 98105, USA > > On 5 Oct 1994, Jeff Scarborough wrote: > > > Date: 5 OCT 1994 18:23:38 GMT > > From: Jeff Scarborough > > Newgroups: comp.mail.pine > > Subject: does mbox driver work in 3.90 > > > > > > According to the faq you can force all new mail to be pulled into ~/mbox > > by linking in the "mbox" driver when you build pine. I executed the > > following: > > > > ./build EXTRADRIVERS=mbox a32 > > > > It seems to have added the mboxdriver to linkage.[ch] and it built fine, > > but it seems to have had no effect. Mail does not get pulled into ~/mbox > > ever. Am I missing a step? Does it even work? > > > > -- > > Jeff Scarborough Jeff.Scarborough@Colorado.EDU > > University of Colorado Computing & Network Services > > Campus Box 455 Boulder, Colorado 80309-0455 > > > > > From owner-pine-info@cac.washington.edu Thu Oct 6 02:28:48 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01646; Thu, 6 Oct 94 02:28:48 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14314; Thu, 6 Oct 94 02:20:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from oxmail2.ox.ac.uk by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14308; Thu, 6 Oct 94 02:20:27 -0700 Received: from vax.ox.ac.uk by oxmail2.ox.ac.uk. with SMTP (PP) id <07940-0@oxmail2.ox.ac.uk.>; Thu, 6 Oct 1994 10:17:07 +0100 Received: by vax.ox.ac.uk (MX V4.1 VAX) id 3; Thu, 06 Oct 1994 10:19:27 +0100 Date: Thu, 06 Oct 1994 10:19:26 +0100 From: "Dave Hastings, OUCS" To: PORTIA@INNOSOFT.COM Cc: PINE-INFO@CAC.WASHINGTON.EDU Message-Id: <0098588C.34CB0A49.3@vax.ox.ac.uk> Subject: Re: Pine 3.90 on VAX/VMS > On Wed, 5 Oct 1994 daveh@vax.ox.ac.uk wrote: > > > Hi, > > > > Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I > > tried today I got lots of warnings of the form > > > > %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters > > > > Comments anyone? > > well, this happens on the DEC C compiler too. You have two choices, > 1. change the identifier to be shorter everywhere > 2. use a #define to define it in os-vms.h > > It would be nice if they don't show up in the source at all, this is just > one of many issues when porting Pine to VMS. > > /portia portia@innosoft.com > Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax > 1050 East Garvey Ave South, West Covina, CA 91790 > Thanks for your reply. I would just like to make a couple of point: 1. This 'feature' was not in the beta-test versions of VMS Pine 2. I thought that the whole point of porting software is to make it work in the target environment. A 'port' which won't compile is not much use to anyone. I suppose I'll have to go through the whole code and fix these long identifier names. And then when 3.91 is released I'll have to do it again. Or maybe I'll just stick with the 3.89 beta version. At least it works. Dave -- David Hastings | "Life's too short to waste time VAX Systems Programmer | chitchatting with machines for Oxford University Computing Services | no good reason" - JM daveh@vax.oxford.ac.uk | From owner-pine-info@cac.washington.edu Thu Oct 6 02:36:24 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01784; Thu, 6 Oct 94 02:36:24 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08526; Thu, 6 Oct 94 02:27:52 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA08520; Thu, 6 Oct 94 02:27:50 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsomS-00000JC; Thu, 6 Oct 94 02:06 PDT To: pine-info@cac.washington.edu From: kjetil@troll.eee.strath.ac.uk (Kjetil Rossavik) Subject: From: not shown for local mail Date: 06 Oct 1994 09:41:06 GMT Message-Id: Hi, I have just started using Pine. When I receive mail from local users, Pine shows the To: address instead of the From: address in the index. For external mail it works correctly. Is there some configuration variable which would remedy this? Regards, Kjetil. -- Kjetil Rossavik Tel. +44-41-552 4400 Signal Processing Division ext. 2686 Dept. of Electronic and Electrical Eng. Fax +44-41-552 2487 University of Strathclyde Glasgow G1 1XQ -- Kjetil Rossavik Tel. +44-41-552 4400 Signal Processing Division ext. 2686 Dept. of Electronic and Electrical Eng. Fax +44-41-552 2487 University of Strathclyde Glasgow G1 1XQ From owner-pine-info@cac.washington.edu Thu Oct 6 03:30:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02922; Thu, 6 Oct 94 03:30:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09163; Thu, 6 Oct 94 03:23:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09157; Thu, 6 Oct 94 03:23:01 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsphM-00000ZC; Thu, 6 Oct 94 03:05 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: mailcap file Date: Wed, 05 Oct 1994 23:04:50 +0100 Message-Id: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Can someone please send be an example mailcap file? The image viewer I > want to use is 'xv'. Pine's mailcap support isn't up to its task yet. But for viewing images you don't need a mailcap. Your best bet is to enter xv as the image-viewer on the last page of Pine's S)etup C)onfig. From owner-pine-info@cac.washington.edu Thu Oct 6 03:31:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03106; Thu, 6 Oct 94 03:31:00 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15028; Thu, 6 Oct 94 03:22:59 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15022; Thu, 6 Oct 94 03:22:56 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsphH-00000YC; Thu, 6 Oct 94 03:05 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Question on Alternate Editor Specification Date: Wed, 05 Oct 1994 22:59:55 +0100 Message-Id: References: <34q12e$48o@universe.digex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > I'd like to specify emacs (without X) as my alternate editor. I've > tried setting my default editor as: unset DISPLAY; emacs You forgot to export the unset DISPLAY. Try emacs -nw From owner-pine-info@cac.washington.edu Thu Oct 6 07:54:47 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09180; Thu, 6 Oct 94 07:54:47 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18773; Thu, 6 Oct 94 07:41:11 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18767; Thu, 6 Oct 94 07:41:09 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qstX2-00001IC; Thu, 6 Oct 94 07:10 PDT To: pine-info@cac.washington.edu From: czyborra@cs.tu-berlin.de (Roman Czyborra) Subject: Re: unintelligible letter from russia (fwd) Message-Id: Date: 5 Oct 94 19:02:19 GMT References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE In-Reply-To: > =F5=D7=C1=D6=C1=C5=CD=D9=CA =F7=C9=CB=D4=CF=D2 =E1=CC=C5=CB=D3=C5=C5=D7= =C9=DE, This is a personal letter to Viktor Alekseyevich, it looks like it was sent to the wrong address. It is in the KOI8-R charset documented in RFC 1489, the original header should have said so, you did not share it with us. Your posting was mislabeled as US-ASCII, I guess that's due to an imperfection of Pine's.=20 We ought to be thankful to Pine for encoding the text so that it arrived without any damage.=20 From owner-pine-info@cac.washington.edu Thu Oct 6 08:31:23 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10734; Thu, 6 Oct 94 08:31:23 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13149; Thu, 6 Oct 94 07:59:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13143; Thu, 6 Oct 94 07:59:53 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qstu5-00000mC; Thu, 6 Oct 94 07:34 PDT To: pine-info@cac.washington.edu From: syb3@aber.ac.uk (Brad) Subject: Re: Spool mail in BSDI Message-Id: Date: 5 Oct 94 19:07:09 GMT References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: On 3 Oct 1994, Anto Daryanto wrote: > I have compiled Pine 3.90 for BSDI v1.1. With default configuration pine > can not see user mail spool. The mail spool directory is in /usr/var/mail. > So I've made a change in pine/pine-use.c to reflect the machine user mail > spool directory. But still, pine can't see spool directory. Couldn't you just set the inbox in .pine-conf? I think you could put: inbox-path=/usr/var/mail/$USER in there, and then Pine should be able to see a user's inbox. --Simon. From owner-pine-info@cac.washington.edu Thu Oct 6 08:40:24 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11235; Thu, 6 Oct 94 08:40:24 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19630; Thu, 6 Oct 94 08:29:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19624; Thu, 6 Oct 94 08:29:27 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsuOf-00000JC; Thu, 6 Oct 94 08:06 PDT To: pine-info@cac.washington.edu From: dmacrae@hocomms.demon.co.uk (David MacRae) Subject: Wanted: Windows/PC version of Pine binary Date: Thu, 6 Oct 1994 14:36:05 +0000 Message-Id: <53541345wnr@hocomms.demon.co.uk> Could someone point me at an ftp site that would have the Windows and/or PC version of Pine. I don't have access to a compiler on my PC. I require this to work with FTP Software PC/TCP Version 3. Regards -- Dave MacRae |The views expressed here are mine and Edinburgh |mine alone and do not reflect the views Scotland |of my employers in any way. From owner-pine-info@cac.washington.edu Thu Oct 6 08:56:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12006; Thu, 6 Oct 94 08:56:50 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14300; Thu, 6 Oct 94 08:50:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14294; Thu, 6 Oct 94 08:50:14 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsuk1-000012C; Thu, 6 Oct 94 08:28 PDT To: pine-info@cac.washington.edu From: stanley@skyking.OCE.ORST.EDU (John Stanley) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 15:06:08 GMT Message-Id: <3713p0$5j7@gaia.ucs.orst.edu> References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> In article <36vi69$3aa@news.halcyon.com>, Nancy McGough wrote: >To:_ and Cc:_ mean [1] most of the time, but some posted messages >might have these headers and not actually have been mailed to the >folks on the To:_ and/or Cc:_ lines. This would happen with a >newsreader that doesn't honor To:_ and/or Cc:_ lines and doesn't strip >them out. Proper newsreader [sic] behaviour is to ignore To: and CC: headers. They are undefined and thus should be ignored. >For mailed messages >Newsgroups:_ sometimes means [2] only, sometimes means [3] only, >and sometimes means [2] and [3]. Proper mailer behaviour is to ignore Newsgroups: headers. The fact that brain damaged newsreaders leave them in when composing mailed replies is not reason to change the current definitions of mail. >For the future it might be a good to have standard headers for both >mail and news for [2] and [3]. What do people think? Of course anything >adopted would have to be backward compatible with existing RFCs. The proper course of action is to modify the newsreader software to include a "post and mail" command. The mailed copies get mail headers, the posted ones get news headers. In no case should a user wind up surprised that his mail got posted by some intermediate site just because there was an undefined Newsgroups: header in it, nor should the opposite surprise exist (a copy mailed when a posted article has an undefined To: header in it.) (In case you want to claim that that would never happen, I can tell you of at least one case where in-transit mail was processed by a mailer which noticed a user name of the form usenet.group.name, and, ignoring the small detail that it was not the host to whom the mail was addressed, went ahead and posted the mail. In most cases, this is the intended result, but in my case it was not. This intermediate mailer had been in operation for a long time before I caught it doing this; how many others are there that haven't been?) This rules out suddenly defining the To: header in news, or the Newsgroups: header for mail, to mean "inject this package into the other type of stream". At best, it means the originating newsreader inserting an "X-Also-Mailed-To:" or "X-Also-Posted-To:" header in the generated packages. From owner-pine-info@cac.washington.edu Thu Oct 6 09:18:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13618; Thu, 6 Oct 94 09:18:08 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20368; Thu, 6 Oct 94 09:00:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20358; Thu, 6 Oct 94 09:00:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsusQ-00000PC; Thu, 6 Oct 94 08:37 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 15:08:56 GMT Message-Id: <3713u8$phs@news.halcyon.com> References: <3700se$2p3@mp.cs.niu.edu> rickert@cs.niu.edu (Neil Rickert) writes: >I install Pine because some of >my users ask for it. Except for testing the installation, I do not >use Pine. I consider it to be one of the biggest pieces of junk >software and poor design that I have encountered. I'm curious why you think this. Could you please post at least 3 features (other than the Newsgroups:_ header in a mail message) which you think were poorly designed and mailers that do each of these 3 features better. Thanks, Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Thu Oct 6 09:41:46 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14778; Thu, 6 Oct 94 09:41:46 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15541; Thu, 6 Oct 94 09:35:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15533; Thu, 6 Oct 94 09:35:16 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsvSu-00000DC; Thu, 6 Oct 94 09:14 PDT To: pine-info@cac.washington.edu From: "James M. Cameron" Subject: Re: Wanted: Windows/PC version of Pine binary Date: Thu, 6 Oct 1994 11:57:07 -0700 (PDT) Message-Id: References: <53541345wnr@hocomms.demon.co.uk> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <53541345wnr@hocomms.demon.co.uk> You can obtain the software from the /pine/pcpine directory at ftp.cac.washington.edu. On Thu, 6 Oct 1994, David MacRae wrote: > Could someone point me at an ftp site that would have the Windows > and/or PC version of Pine. I don't have access to a compiler on my > PC. > > I require this to work with FTP Software PC/TCP Version 3. > > Regards > -- > Dave MacRae |The views expressed here are mine and > Edinburgh |mine alone and do not reflect the views > Scotland |of my employers in any way. > > > > From owner-pine-info@cac.washington.edu Thu Oct 6 09:56:44 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15293; Thu, 6 Oct 94 09:56:44 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21623; Thu, 6 Oct 94 09:47:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21617; Thu, 6 Oct 94 09:47:52 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsviM-00000XC; Thu, 6 Oct 94 09:30 PDT To: pine-info@cac.washington.edu From: Alex Sharaz Subject: PC-PINE reading DOS Environment variables Date: Thu, 6 Oct 1994 17:11:09 +0100 (BST) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, Does anyone know if PC-PINE will read dos environment variables. I want to set up PINE on our Netware Servers and it would be nive if I could have a default pinerc file that uses Dos ENVs for things like FULLNAME and USERID. Alex RFC-822: A.Sharaz@computer-centre.hull.ac.uk X.400: I=A;S=Sharaz;OU=Computer-Centre;O=Hull;PRMD=UK.AC;c=GB X.500: c=GB@o=University of Hull@ou=computer Centre@cn=Alexander Sharaz Tel: +44 482-465700 Fax: +44 482-466441 From owner-pine-info@cac.washington.edu Thu Oct 6 10:39:14 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17042; Thu, 6 Oct 94 10:39:14 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22533; Thu, 6 Oct 94 10:29:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22525; Thu, 6 Oct 94 10:28:59 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21765; Thu, 6 Oct 94 10:28:41 -0700 Date: Thu, 6 Oct 1994 10:28:41 -0700 (PDT) From: Steve Hubert To: daveh@vax.ox.ac.uk, Portia Shao Cc: pine-info@cac.washington.edu Subject: Re: Pine 3.90 on VAX/VMS In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII If you can give us a list of identifiers exceeding 31 characters (do we really have some of those?) maybe we can shorten them in our source. Thanks. Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On Wed, 5 Oct 1994, Portia Shao wrote: > On Wed, 5 Oct 1994 daveh@vax.ox.ac.uk wrote: > > > Hi, > > > > Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I > > tried today I got lots of warnings of the form > > > > %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters > > > > Comments anyone? > > well, this happens on the DEC C compiler too. You have two choices, > 1. change the identifier to be shorter everywhere > 2. use a #define to define it in os-vms.h > > It would be nice if they don't show up in the source at all, this is just > one of many issues when porting Pine to VMS. > > > > > Dave > > -- > > > > David Hastings | "Life's too short to waste time > > VAX Systems Programmer | chitchatting with machines for > > Oxford University Computing Services | no good reason" - JM > > daveh@vax.oxford.ac.uk | > > > > > > > /portia portia@innosoft.com > Innosoft International Inc. (818)919-3600 voice, (818)919-3614 fax > 1050 East Garvey Ave South, West Covina, CA 91790 > > From owner-pine-info@cac.washington.edu Thu Oct 6 11:39:23 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19362; Thu, 6 Oct 94 11:39:23 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18089; Thu, 6 Oct 94 11:29:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18083; Thu, 6 Oct 94 11:28:57 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsxFy-00000IC; Thu, 6 Oct 94 11:09 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Custom Headers Date: Thu, 6 Oct 1994 10:43:02 -0700 Message-Id: References: <36vfrv$9vs@mark.ucdavis.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <36vfrv$9vs@mark.ucdavis.edu> Go to the Setup/Config screen and set the customized-hdrs variable... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On 6 Oct 1994, Hemang Patel wrote: > Date: 6 OCT 1994 00:20:15 GMT > From: Hemang Patel > Newgroups: comp.mail.pine > Subject: Custom Headers > > For a while now, I have been trying to define custom headers in PINE 3.90 > to no avail. Can anyone please help me? The help built into pine is no > help. TIA. > > -- > _________________________________________ > Hemang Patel hcpatel@dale.ucdavis.edu > > From owner-pine-info@cac.washington.edu Thu Oct 6 11:55:03 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20290; Thu, 6 Oct 94 11:55:03 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18707; Thu, 6 Oct 94 11:49:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18701; Thu, 6 Oct 94 11:49:11 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsxXf-00000OC; Thu, 6 Oct 94 11:27 PDT To: pine-info@cac.washington.edu From: nancym@chinook.halcyon.com (Nancy McGough) Subject: cmsg cancel <36ur0r$lhp@news.halcyon.com> Control: cancel <36ur0r$lhp@news.halcyon.com> Date: 5 Oct 1994 18:54:30 GMT Message-Id: <36usp6$m8t@news.halcyon.com> cancel <36ur0r$lhp@news.halcyon.com> in newsgroup comp.mail.pine -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Thu Oct 6 11:56:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20382; Thu, 6 Oct 94 11:56:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24302; Thu, 6 Oct 94 11:49:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24292; Thu, 6 Oct 94 11:49:05 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsxb8-00000XC; Thu, 6 Oct 94 11:31 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 13:06:22 -0500 Message-Id: <371eau$h4l@mp.cs.niu.edu> References: <3700se$2p3@mp.cs.niu.edu> <3713u8$phs@news.halcyon.com> In <3713u8$phs@news.halcyon.com> Nancy McGough writes: >rickert@cs.niu.edu (Neil Rickert) writes: >>I install Pine because some of >>my users ask for it. Except for testing the installation, I do not >>use Pine. I consider it to be one of the biggest pieces of junk >>software and poor design that I have encountered. >I'm curious why you think this. Could you please post at least 3 features >(other than the Newsgroups:_ header in a mail message) which you think were >poorly designed and mailers that do each of these 3 features better. 1: It is a bitch to install. Read the instructions. Select the configuration for your system, using the 'gcc' compiler. Run the build script. Discover that it doesn't use the 'gcc' compiler. Read and understand the build script, so that you can really use 'gcc', by adding a keyword argument CC=gcc on the command line. Discover that it does a half-baked job, using 'gcc' part of the time, and 'cc' part of the time. Use a 'find' to locate all of the 'Makefile's to find what has to be changed to really use gcc. Compile. Have the thing crap out in the middle because a system include file is included twice, the first time with 'const' as itself, and the second time with 'const' redefined as ''. Build it. Discover that it makes incorrect assumptions about where various things are in your system (such as the news active file). Grep through every directory till you find what has to be changed. etc. 2: It is excessively obese. The stripped binary is significantly in excess of 1 meg in size. Much of this is due to the inclusion of help text within the binary instead of in a separate help file. This means that an experience user who need no help must nevertheless load the help information into memory whenever she uses the software. 3: It screws up message status of the default mailbox. It always opens my default mailbox, whether I want it to or not. The status of messages in that mailbox changes from New to Unread, even though I have not asked to read the mailbox, and have not seen the list of messages in that mailbox. 4: The menu interface is tedious and unintuitive. When reading news, it displays a humongous list of newsgroups for me to select from. I have to actually select each in turn to discover that there are no unread messages in that newsgroup. After reading one newsgroup, if I want to select another I must go back and re-select the news collection, and have it redisplay the menu, then I must page through the menu to about where I was. Perhaps I am missing some shortcut here, but the keypresses indicated on the screen display do not provide a shorter alternative. 5: Poorly timed user unfriendly prompts. If I read my mail, then spend some time reading usenet, at the end it asks me if I really wanted to delete those messages from my mailbox. But that might be so long after I asked to delete them that I have forgotten the details. If the program wants to second guess and ask for confirmation, it should do it much earlier, perhaps as soon as a different folder is selected. Sorry, but there is no point in my listing other mail programs which do not have these faults. I am not aware of any other mail programs which do have these faults. From owner-pine-info@cac.washington.edu Thu Oct 6 12:04:29 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20836; Thu, 6 Oct 94 12:04:29 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18805; Thu, 6 Oct 94 11:52:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18799; Thu, 6 Oct 94 11:52:43 -0700 Received: from localhost (hayden@localhost) by krypton.mankato.msus.edu (8.6.4/8.6.4) id NAA12848; Thu, 6 Oct 1994 13:51:36 -0500 Date: Thu, 6 Oct 1994 13:51:36 -0500 (CDT) From: "Robert A. Hayden" Subject: 3.91? To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I know I'm goona get smacked for this, but any idea on when 3.91 will be coming out? I think our local admin is delaying installing 3.9x until the bug fixes are made... ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> I do not necessarily speak for the \/ Finger for PGP Public Key <=> City of Mankato or anyone else -=-=-=-=-=-=-=- (GEEK CODE 2.1) GJ/CM d- H-- s-:++>s-:+ g+ p? au+ a- w++ v* C++(++++) UL++++$ P+>++ L++$ 3- E---- N+++ K+++ W M+ V-- -po+(---)>$ Y++ t+ 5+++ j R+++$ G- tv+ b+ D+ B--- e+>++(*) u** h* f r-->+++ !n y++** From owner-pine-info@cac.washington.edu Thu Oct 6 12:17:52 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21303; Thu, 6 Oct 94 12:17:52 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24871; Thu, 6 Oct 94 12:09:23 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24859; Thu, 6 Oct 94 12:09:10 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsxuP-00000DC; Thu, 6 Oct 94 11:51 PDT To: pine-info@cac.washington.edu From: eks@vki68.aar-vki.dk (Eigil Krogh Sorensen) Subject: PC/Win pine "offline" how ??? Date: 6 Oct 1994 18:11:53 GMT Message-Id: <371el9$c79@belfort.daimi.aau.dk> Is it possible to have PC/Win pine work "offline". It is so that our central e-mail server is a UNIX machine (SCO). Our PCs pine then fetches e-mails from INBOX and stores mails in mail- folders on that machine via imap. When the PC's pine send mails they send it to the UNIX machine with smtp. This works fine as long as the PC are connected to our Ethernet LAN. But if the PC's are placed outside the department, telephone connections has to be used, and that costs a lot of money if the line (e.g. slip or ppp) has to be open all the time pine is running. Therefor my question is if it is possible in one or another way to get pine to "download" the total INBOX to the PC at once, so the telephone connection can be closed, and then the user on the PC can read the mails (local on the pc), reply, Compose etc. and when finished the telephone line is opened again and the outgoing mails are sent. All in all to reduce the time the telephone line is open as much as possible. The SCO UNIX both has imap(d), ipop and ipop3. I never used other than imap(d). Can ipop? be used to do what I want ? How is it done then ? Hints, advices and suggestions are wellcome Thanks in advance -- Eigil Krogh Sorensen ------------------------------------------------------------------------- VKI ! ! Water Quality Institute !Phone: !E-mail: Science Park Aarhus ! +45 86 20 20 00 or ! 10, Gustav Wieds Vej ! +45 86 20 20 11 local 2114 ! eks@aar-vki.dk DK-8000 Aarhus C !Fax: ! DENMARK. ! +45 86 19 75 11 ! ------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Oct 6 12:29:54 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21742; Thu, 6 Oct 94 12:29:54 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19505; Thu, 6 Oct 94 12:24:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19499; Thu, 6 Oct 94 12:24:00 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsy6d-00000IC; Thu, 6 Oct 94 12:03 PDT To: pine-info@cac.washington.edu From: morrowd@candu.aecl.ca (Dave Morrow) Subject: Customizing Pine Date: 6 Oct 1994 14:32:52 GMT Message-Id: <3711qk$r8p@newton.candu.aecl.ca> I was just wondering.....Pine 3.90 running on an HP automatically recognizes attachments that are images and spawns an external viewer (XView in my case) to view the image. Q. Is there a way to customize Pine to automatically recognize other types of attachments and call a program to view them? ie. Call emacs for text files? WP for .doc files ? -- David A. Morrow AECL Candu Tel: (905) 823-9060 Fax: 823-2302 Email: morrowd@candu.aecl.ca From owner-pine-info@cac.washington.edu Thu Oct 6 13:28:31 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24526; Thu, 6 Oct 94 13:28:31 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26488; Thu, 6 Oct 94 13:15:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26481; Thu, 6 Oct 94 13:15:38 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qsytE-00000PC; Thu, 6 Oct 94 12:54 PDT To: pine-info@cac.washington.edu From: yehavi@vms.huji.ac.il (Yehavi Bourvine (58-4279)) Subject: Re: Pine 3.90 on VAX/VMS Message-Id: <1994Oct6.210023.173@vms.huji.ac.il> Date: 6 Oct 94 21:00:23 GMT References: <1994Oct5.155656.26464@oxvaxd> > Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I > tried today I got lots of warnings of the form > > %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters This is only a warnning message... Ignore it and continue. __Yehavi: From owner-pine-info@cac.washington.edu Thu Oct 6 14:08:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26338; Thu, 6 Oct 94 14:08:00 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27492; Thu, 6 Oct 94 14:02:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from edison.eng.auburn.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27486; Thu, 6 Oct 94 14:02:08 -0700 Received: from netman.eng.auburn.edu (netman.eng.auburn.edu [131.204.12.24]) by edison.eng.auburn.edu (8.6.9/8.6.4) with ESMTP id QAA12460 for ; Thu, 6 Oct 1994 16:02:06 -0500 From: Doug Hughes Received: from localhost (doug@localhost) by netman.eng.auburn.edu (8.6.4/8.6.4) id QAA11999 for pine-info@cac.washington.edu; Thu, 6 Oct 1994 16:02:05 -0500 Date: Thu, 6 Oct 1994 16:02:05 -0500 Message-Id: <199410062102.QAA11999@netman.eng.auburn.edu> To: pine-info@cac.washington.edu Subject: trouble with fcc in 3.90 Content-Length: 729 New member of the list here.. Having trouble with the PC version of the DOS sunpc client of pine.. the Fcc field is perplexing.. Is there a way to disable this? If I use default fcc, it asks me if I want to create \mail\sentmail since it doesn't exist. if I say yes, it tells me file already exists, can't create it.. If I say no, it puts me back in edit. if I change FCC to be by-user, it puts fcc in header.. Only by deleting FCC as it is created in the header can I get mail to be sent. Also, I have gotten: Bug in Pine detected: "Append Validity Confusion" several times when sending mail. Haven't found that documented anywhere. Doug Hughes Engineering Network Services doug@eng.auburn.edu Auburn University From owner-pine-info@cac.washington.edu Thu Oct 6 14:21:25 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26772; Thu, 6 Oct 94 14:21:25 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21924; Thu, 6 Oct 94 14:09:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21918; Thu, 6 Oct 94 14:09:24 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qszkv-00000DC; Thu, 6 Oct 94 13:49 PDT To: pine-info@cac.washington.edu From: czyborra@cs.tu-berlin.de (Roman Czyborra) Subject: Re: MIME Message-Id: Date: 5 Oct 94 21:38:39 GMT References: <36sdf3$kgk@linda.teleport.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > I don't know what the problem is, but I haven't been able to get > Munpack to decode any attached messages sent with Pine. Munpack > gives me the message "Nothing to unpack." You need to pipe to munpack -t to decode text attachments also. I think the -t option was introduced in mpack-1.3. ftp://ftp.andrew.cmu.edu/pub/mpack From owner-pine-info@cac.washington.edu Thu Oct 6 14:25:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27040; Thu, 6 Oct 94 14:25:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27974; Thu, 6 Oct 94 14:20:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rainbow.uta.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27968; Thu, 6 Oct 94 14:20:00 -0700 Received: by rainbow.uta.edu (4.1/SMI-4.1) id AA01524; Thu, 6 Oct 94 16:23:04 CDT Date: Thu, 6 Oct 1994 16:22:45 -0500 (CDT) From: Abdelsalam Helal Subject: covert from elm to pine To: pine-info@cac.washington.edu Cc: "Prof. Dr. Behrooz A. Shirazi" Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello there! Could anybody please give me a pointer of a program that could translate from elm's alias file to pine's addressbook. Thanks, A. 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 Oct 6 15:00:53 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28697; Thu, 6 Oct 94 15:00:53 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22968; Thu, 6 Oct 94 14:54:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22962; Thu, 6 Oct 94 14:53:59 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA11681; Thu, 6 Oct 1994 17:50:50 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA25687; Thu, 6 Oct 94 16:53:58 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA01033; Thu, 6 Oct 94 16:53:58 CDT Date: Thu, 6 Oct 1994 16:53:57 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: Hemang Patel Cc: pine-info@cac.washington.edu Subject: Re: Custom Headers In-Reply-To: <36vfrv$9vs@mark.ucdavis.edu> Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1152 On 6 Oct 1994, Hemang Patel wrote: > For a while now, I have been trying to define custom headers in PINE 3.90 > to no avail. Can anyone please help me? The help built into pine is no > help. TIA. > I'll expand DLM's answer a little. Like he said, go to Setup/Configure and select Add with Customized-hdrs highlighted. If you want to add an organization name your input should be: Organization: UCDAVIS Educational Center You can have more than one custom header by separating them by commas. Note, that since you separate your headers by commas, you cannot have commas in the header itself. --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Thu Oct 6 15:06:46 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28998; Thu, 6 Oct 94 15:06:46 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23130; Thu, 6 Oct 94 15:01:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23119; Thu, 6 Oct 94 15:00:58 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA11758; Thu, 6 Oct 1994 17:57:47 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA26007; Thu, 6 Oct 94 17:00:54 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA01037; Thu, 6 Oct 94 17:00:54 CDT Date: Thu, 6 Oct 1994 17:00:53 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: "Robert A. Hayden" Cc: Pine Info Subject: Re: 3.91? In-Reply-To: Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1002 On Thu, 6 Oct 1994, Robert A. Hayden wrote: > I know I'm goona get smacked for this, but any idea on when 3.91 will be > coming out? I think our local admin is delaying installing 3.9x until > the bug fixes are made... > If I remember correctly from 3.90, it is tenantively set for in a couple of weeks.:-) (Isn't this right DLM?) More seriously, I don't know and I have a feeling the pine developers would hate to make any commitment right now. --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Thu Oct 6 15:14:06 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29244; Thu, 6 Oct 94 15:14:06 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23295; Thu, 6 Oct 94 15:05:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from steadfast.teradyne.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23289; Thu, 6 Oct 94 15:05:19 -0700 Received: from gollum.ttd.teradyne.com by steadfast.teradyne.com (5.0/SMI-4.1/jxh940509) id AA11805; Thu, 6 Oct 1994 18:02:09 -0400 Received: from bard.ttd.teradyne.com by gollum.ttd.teradyne.com (4.1/SMI-4.1/TER-1.47/gollum-1.1) id AA26221; Thu, 6 Oct 94 17:05:14 CDT Received: by bard.ttd.teradyne.com (4.1/SMI-4.1) id AA01041; Thu, 6 Oct 94 17:05:13 CDT Date: Thu, 6 Oct 1994 17:05:13 -0500 (CDT) From: "Kenny Wickstrom (x2349)" X-Sender: kenny@bard To: Abdelsalam Helal Cc: pine-info@cac.washington.edu, "Prof. Dr. Behrooz A. Shirazi" Subject: Re: covert from elm to pine In-Reply-To: Message-Id: Organization: Teradyne Telecommunications Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1091 On Thu, 6 Oct 1994, Abdelsalam Helal wrote: > Hello there! Could anybody please give me a pointer of a program that > could translate from elm's alias file to pine's addressbook. > When I converted, my alias file was relatively small (<200 aliases) and I just copied my alias.txt(I think) to addressbook. The only real difference I believe was that Pine want the Real Name in Last, First format and Elm doesn't. So over time, I just corrected mine alittle at a time. There may be more elegant ways of doing this, but I was too lazy. --------------------------------------------------------------------------- |/ | | |\enny |/\|ickstrom (kenny@ttd.teradyne.com) ======== // ___ \\___ ==\\ || \\__ ___ 1405 Lake Cook Rd. // // \\ ||---\ _|| _|| \\ // ||--\\ // \\ Deerfield, IL 60015 // ===== || // || // || \\// || || ===== (708)940-9000 // \\___ || \\_/\_ \\_/\_ // || || \\___ (708)940-0344(FAX) Telecommunications Division // _// From owner-pine-info@cac.washington.edu Thu Oct 6 15:39:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00768; Thu, 6 Oct 94 15:39:08 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29674; Thu, 6 Oct 94 15:23:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from sol.cwsl.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29668; Thu, 6 Oct 94 15:23:47 -0700 Received: from [204.94.57.11] (ram.cwsl.edu [204.94.57.11]) by sol.cwsl.edu (8.6.9/8.6.9) with SMTP id PAA00455 for ; Thu, 6 Oct 1994 15:22:36 -0700 Date: Thu, 6 Oct 1994 15:23:13 -0700 (PDT) From: "Raleigh Moody (raleigh@cwsl.edu)" To: Pine List Subject: PC-Pine 3.90 aborts and exits X-Sender: ram@cwsl.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We recently installed PC-Pine 3.90 for the users on our Novell LAN. We use the LanWorkgroup 4.2 TCP/IP stack. We are having an intermittent problem with Pine suddenly aborting and exiting to DOS, displaying the message: Bug in Pine detected: "Bad msgno in mail_fetchtext" Exiting Pine. It will most often do this when attempting to save a message to a folder, but has also happened when a user simply tries to delete a message, forward a message, or even read a message from the inbox list. I at first thought it might be an incorrect imap version problem, so I downloaded imapd-bin.solaris from ftp.cac.washington.edu, then installed it on our Sparc5 mail/domain server (yes, I did a "kill -1 " to restart the daemon...I know some of you will ask). This didn't solve the problem. The curious thing about this problem is that it surfaces intermittently, and happens to different users at different times. It might work fine for a week or so, with the user saving and deleting files at will, with no problems at all, then one day start acting up. So, 90% of the time Pine works flawlessly, it's just that 10% that becomes very annoying, because it kicks you out without warning. When this happens, Pine of course generates 4 or 5 debug files. Has anybody experienced a similar problem? I've followed the messages on this list for several weeks without spotting any problems that sound similar. I've also looked through the the tech-notes, FAQ, and even the August mail list archive, and found no hints or reports of similar problems. Advice, anyone? ----------------------------------------------------------------------- Raleigh Moody Network Specialist email raleigh@cwsl.edu California Western School of Law phone 619-525-1406 San Diego, CA fax 619-685-2916 ----------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Oct 6 15:51:28 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01271; Thu, 6 Oct 94 15:51:28 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00265; Thu, 6 Oct 94 15:43:32 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00259; Thu, 6 Oct 94 15:43:29 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt1BM-00000DC; Thu, 6 Oct 94 15:21 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 21:17:19 GMT Message-Id: <371pgv$730@news.halcyon.com> References: <36ut98$mh4@news.halcyon.com> The suggestions for new headers came from me (an avid news and mail user who years ago designed a newsreader that was never developed) so it's not so much that Pine cares about these things, it's that I care and I thought others might too.... For the sake of discussion suppose the headers are called: X-Posted-To: X-Response-To-Message-In: And suppose I receive a message with these headers (plus some other headers) in my mailbox: From: abrahamp To: nancym Cc: peterg Subject: Re: How Experiments End Newsgroups: soc.history.science X-Posted-To: soc.history.science X-Response-To-Message-In: soc.history.science,sci.philosophy.tech Because of the X-Posted-To: header I know that abrahamp both posted and mailed his message so it is ok (acceptable netiquette) for me to both mail and post my response. Because of the X-Response-To-Message-In: header I know that he is responding to a message that was crossposted to soc.history.science and sci.philosophy.tech so I can go take a look at both these newsgroups to read the discussion. Since crossposted discussions often bifurcate its useful to know all the newsgroups the message that's being replied to was in. Does this seem useful to anyone else? Also, I'm curious which other mailers allow users to simultaneously mail and post. Thanks much, Nancy PS to people reading this on the header-people mailing list (which is linked to comp.mail.headers): If possible could you post your response to all the newsgroups that are participating in this discussion. Thanks. In comp.mail.headers Craig_Everhart@transarc.COM writes: >The Andrew Message System has been dealing with netnews and mailings >since about 1987. We've had no problems with the concept of one message >reader dealing with both. > >On the face of it, I have to wonder what Pine cares about where a >message was read or posted. What difference does it make to the reader? > (``Disclaimer: the displayed message came from NetNews; read at your >own risk'' in a red border around the screen?) > >If Pine is all that worried, it could in principle use >out-of-incoming-header information to decide how a message got into its >hands, like whether it's reading from a folder of filed mail, from an >in-box, or from a newsgroup repository. AMS installations that deal in >netnews usually add a special message header to tell the reader to what >address ``wide replies'' (e.g. reply-to-all) should be directed, but a >simpler alternative would be for there to be tags in the AMS reader >configuration, or in the folder tree itself, indicating what parts of >the message database hold netnews messages as distinct from mailed >messages. > >The argument is similar to that of the Content-Length: one, in that if a >mail reader is going to rely on some non-standard (possibly >non-standardizeable) features of incoming mail, then it should itself >assure that it will be able to use those non-standard features. > >Thus, I vote against amending the standards to restrict what can be said >in a mail header. > > Craig -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Thu Oct 6 15:53:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01402; Thu, 6 Oct 94 15:53:54 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00330; Thu, 6 Oct 94 15:46:03 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mail.crl.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00324; Thu, 6 Oct 94 15:46:00 -0700 Received: from crl7.crl.com by mail.crl.com with SMTP id AA06038 (5.65c/IDA-1.5 for ); Thu, 6 Oct 1994 15:44:09 -0700 Received: by crl7.crl.com id AA21050 (5.65c/IDA-1.5 for pine-info@cac.washington.edu); Thu, 6 Oct 1994 15:44:21 -0700 Date: Thu, 6 Oct 1994 15:43:25 -0700 (PDT) From: Ann Whitehead Subject: Unsubscribe, please. To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From owner-pine-info@cac.washington.edu Thu Oct 6 16:40:22 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03992; Thu, 6 Oct 94 16:40:22 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25361; Thu, 6 Oct 94 16:34:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25355; Thu, 6 Oct 94 16:34:50 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt1y3-00000cC; Thu, 6 Oct 94 16:11 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Hey, how to find out the local nntp server? Date: Thu, 06 Oct 1994 23:21:45 +0100 Message-Id: References: <36v9gc$43t@spool.cs.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Hey how to find out where is the local nntp server for pine? If you get a connection with telnet news nntp, your nntp-server is called news. If it isn't you can look at the headers of your own postings for clues or ask your news administrator. Your nearest NNTP server seems to be spool.cs.wisc.edu. From owner-pine-info@cac.washington.edu Thu Oct 6 16:48:37 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04402; Thu, 6 Oct 94 16:48:37 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01809; Thu, 6 Oct 94 16:44:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01801; Thu, 6 Oct 94 16:44:46 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt25i-00000DC; Thu, 6 Oct 94 16:19 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Pine: No domain name on From: line Date: Thu, 06 Oct 1994 23:55:07 +0100 Message-Id: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Pine 3.90 creates an unreplyable From line lacking the domain name, > like this: From: Allen Sonafrank Set user-domain= fuzzy.math.nau.edu in your .pinerc or pine.conf. From owner-pine-info@cac.washington.edu Thu Oct 6 17:01:35 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05285; Thu, 6 Oct 94 17:01:35 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01947; Thu, 6 Oct 94 16:49:51 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01939; Thu, 6 Oct 94 16:49:48 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt2Dn-00000fC; Thu, 6 Oct 94 16:27 PDT To: pine-info@cac.washington.edu From: Nancy McGough Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 6 Oct 1994 22:57:31 GMT Message-Id: <371vcr$9rq@news.halcyon.com> References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> <3713p0$5j7@gaia.ucs.orst.edu> stanley@skyking.OCE.ORST.EDU (John Stanley) writes: >Proper mailer behaviour is to ignore Newsgroups: headers. The fact that >brain damaged newsreaders leave them in when composing mailed replies is >not reason to change the current definitions of mail. I just tested TRN 3.5, TIN 1.2 PL2, NN 6.4.18, and PINE 3.90 by using the r command to respond in mail to a USENET article. TRN, TIN, and NN all included a Newsgroups: header in a mailed response to a news article. Pine 3.90 did not include a Newsgroups: header when the response was mailed only. Do you really think that TRN, TIN, and NN are brain damaged? It seems clear that if there is going to be a standard header that means that a mail message was simultaneously mailed and posted it will have to be something other than the Newsgroups: header. What do people think of Posted-To:? Thanks, Nancy -- ** ** Nancy McGough | "No one suspects the * ** * Infinite Ink | days to be gods." ** ** ftp://ftp.ii.com/pub/ii | -Emerson From owner-pine-info@cac.washington.edu Thu Oct 6 17:15:05 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06452; Thu, 6 Oct 94 17:15:05 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25796; Thu, 6 Oct 94 16:49:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25790; Thu, 6 Oct 94 16:49:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt2CU-00000dC; Thu, 6 Oct 94 16:26 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Incoming-folders= Date: Fri, 07 Oct 1994 00:05:04 +0100 Message-Id: References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > incoming-folders=bsdi, procmail, news, root Perhaps you mean incoming-folders=mail/bsdi, mail/procmail...? From owner-pine-info@cac.washington.edu Thu Oct 6 17:27:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07212; Thu, 6 Oct 94 17:27:04 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26507; Thu, 6 Oct 94 17:08:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26501; Thu, 6 Oct 94 17:08:44 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt2Tb-00000VC; Thu, 6 Oct 94 16:43 PDT To: pine-info@cac.washington.edu From: raleigh@cwsl.edu (Raleigh Moody) Subject: PC Pine 3.90 aborts and exits Date: 6 Oct 1994 22:41:41 GMT Message-Id: <371uf5$dde@softserv.solsource.com> References: We recently installed PC-Pine 3.90 for the users on our Novell LAN. We use the LanWorkgroup 4.2 TCP/IP stack. We are having an intermittent problem with Pine suddenly aborting and exiting to DOS, displaying the message: Bug in Pine detected: "Bad msgno in mail_fetchtext" Exiting Pine. It will most often do this when attempting to save a message to a folder, but has also happened when a user simply tries to delete a message, forward a message, or even read a message from the inbox list. I at first thought it might be an incorrect imap version problem, so I downloaded imapd-bin.solaris from ftp.cac.washington.edu, then installed it on our Sparc5 mail/domain server (yes, I did a "kill -1 " to restart the daemon...I know some of you will ask). This didn't solve the problem. The curious thing about this problem is that it surfaces intermittently, and happens to different users at different times. It might work fine for a week or so, with the user saving and deleting files at will, with no problems at all, then one day start acting up. So, 90% of the time Pine works flawlessly, it's just that 10% that becomes very annoying, because it kicks you out without warning. When this happens, Pine of course generates 4 or 5 debug files. Has anybody experienced a similar problem? I've followed the messages on this group for several weeks without spotting any problems that sound similar. I've also looked through the the tech-notes, FAQ, and even the August mail list archive, and found no hints or reports of similar problems. Advice, anyone? ----------------------------------------------------------------------- Raleigh Moody Network Specialist email raleigh@cwsl.edu California Western School of Law phone 619-525-1406 San Diego, CA fax 619-685-2916 ----------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Oct 6 18:17:58 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09348; Thu, 6 Oct 94 18:17:58 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27691; Thu, 6 Oct 94 18:07:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from faxon.ca by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27685; Thu, 6 Oct 94 18:07:45 -0700 Received: by faxon.ca (5.4R2.01/192.139.186.253) id AA28368; Thu, 6 Oct 1994 21:06:51 -0400 Date: Thu, 6 Oct 1994 21:06:50 -0400 (EDT) From: Dion Vansevenant To: Pine Messages Subject: IMAP doesn't seem to work Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'm still loving 3.90, although I can't access newsgroups. Here is what I get: When booting system (DG/UX 5.4.201): Oct 1 18:05:50 faxon inetd[3505]: bad configuration line inetd.conf file (relevant lines only): # # IMAP (Pine) server configuration # pop stream tcp nowait root /usr/etc/ipop2d ipop2d pop3 stream tcp nowait root /usr/etc/ipop3d ipop3d imap stream tcp nowait root /usr/etc/imapd imapd Did I miss something somewhere? When I do try to access news (news.cac.washington.edu) I _can_ see the groups, but I can't subscribe to them. Any help would be appreciated. TIA Dion *----------------------------------------------* | Dion Vansevenant stu2@faxon.ca | | Faxon/SMS Canada Ltd. (519) 472-1006 voice | | London, ON Canada (519) 472-1072 fax | *----------------------------------------------* From owner-pine-info@cac.washington.edu Thu Oct 6 18:20:34 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09399; Thu, 6 Oct 94 18:20:34 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03799; Thu, 6 Oct 94 18:13:43 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03793; Thu, 6 Oct 94 18:13:41 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt3Wr-00000DC; Thu, 6 Oct 94 17:51 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Headers of Simultaneous Mail & News Date: Fri, 07 Oct 1994 01:11:20 +0100 Message-Id: References: <36t8ok$n8h@mp.cs.niu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > The particular issue should not be an issue now. It is because of a > design flaw in pine. I disagree, I'd call rn's reply behavior ignorant of RFC 1036. > If you received the message in mail, then it was mailed. If you want to > know whether the originator of the message also posted it in a public > forum somewhere -- then you are asking for the ability to read minds > of people you have never met. I have had one person get mad at me once: I mailed him a copy of my followup on his posting and he replied privately. Later he saw that I had also posted my message so he had to go back into his archive and manually post the answer he had sent to me. Consequently I renamed Newsgroups: to Also-Posted-To: for a while. The Also- prefix was inspired by the son-of-rfc1036 draft. Now that I've seen Pine use Newsgroups: as an indicator for postings I've returned to sending out that header. Sam Tardieu uses To-Newsgroups. Instead of reading minds, one could of course query the NNTP server for the message-id, but postings may not arrive there soon enough. > If you received the message by mail, and there is no indication that > it was also posted, proper netiquette is to assume that it was mail. > You do not need any special headers for that. If you want to automatize things, you need a standardized label which indicates a public posting. The same problem arises for newsgroup moderators who have to decide whether a message con Newsgroups: was meant as a private reply or a public submission. > Usually the "Received:" header in mail and the "Path:" header in > usenet news can give you this information. Many mailers and newsreaders consider Path: and Received: clutter and do not include it in forwarded messages. Anyway, these lines tell you how the message made it to you, not where it originated. I've been using Old-Newsgroups: and Old-To: to indicate the origin of a conversation occasionally, that prefix was inspired by formail. > "Newsgroups:" has a defined meaning for usenet, but has no defined > meaning for email. You also believe that Content-Type: is undefined in news just because RFC 1521 doesn't mention Usenet? > But you will probably never get it adopted. There are too many > existing products which do not honor these to-be-invented headers Yes, unfortunately Newsgroups in replies has become very common and Pine3.90 alone does not produce enough pressure on people who want to keep their replies private to fix their newsreaders. From owner-pine-info@cac.washington.edu Thu Oct 6 18:25:34 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09511; Thu, 6 Oct 94 18:25:34 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27775; Thu, 6 Oct 94 18:13:48 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27769; Thu, 6 Oct 94 18:13:45 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt3X4-00000PC; Thu, 6 Oct 94 17:51 PDT To: pine-info@cac.washington.edu From: adambcox@tucson.princeton.edu (Adam Cox) Subject: Re: New user requires help. Message-Id: <1994Oct5.210722.13290@Princeton.EDU> References: Date: Wed, 5 Oct 1994 21:07:22 GMT In article , Keith Cordon wrote: >I have only just discovered PINE so please bear with me. >Can someone please email me with information on how to stop the creation >of enourmous .pine-debug files everytime I use pine. >Also is there a FAQ for pine users? I've managed to get to grips with >most of it but I have a few questions.... >Many Thanks i get the same pine-debug files. four of them build up and then they stop (i don't know f they are rewriting to those four or not - haven't checked). anyone know what the cause of it is? adam - i could post one of the files to be examined... From owner-pine-info@cac.washington.edu Thu Oct 6 18:28:09 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09567; Thu, 6 Oct 94 18:28:09 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03934; Thu, 6 Oct 94 18:19:58 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03928; Thu, 6 Oct 94 18:19:55 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt3aU-00000QC; Thu, 6 Oct 94 17:55 PDT To: pine-info@cac.washington.edu From: eks@vki68.aar-vki.dk (Eigil Krogh Sorensen) Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 7 Oct 1994 00:20:29 GMT Message-Id: <37248d$iti@belfort.daimi.aau.dk> References: <3700se$2p3@mp.cs.niu.edu> <3713u8$phs@news.halcyon.com> <371eau$h4l@mp.cs.niu.edu> Thus spake rickert@cs.niu.edu (Neil Rickert): >In <3713u8$phs@news.halcyon.com> Nancy McGough writes: >>rickert@cs.niu.edu (Neil Rickert) writes: >>>I install Pine because some of >>>my users ask for it. Except for testing the installation, I do not >>>use Pine. I consider it to be one of the biggest pieces of junk >>>software and poor design that I have encountered. >>I'm curious why you think this. Could you please post at least 3 features >>(other than the Newsgroups:_ header in a mail message) which you think were >>poorly designed and mailers that do each of these 3 features better. > 1: It is a bitch to install. > Read the instructions. Select the configuration for > your system, using the 'gcc' compiler. > Run the build script. Discover that it doesn't > use the 'gcc' compiler. > Read and understand the build script, so that you can > really use 'gcc', by adding a keyword argument CC=gcc > on the command line. Discover that it does a half-baked > job, using 'gcc' part of the time, and 'cc' part of the > time. > Use a 'find' to locate all of the 'Makefile's to find what > has to be changed to really use gcc. > Compile. Have the thing crap out in the middle because a > system include file is included twice, the first time with > 'const' as itself, and the second time with 'const' redefined > as ''. > Build it. Discover that it makes incorrect assumptions > about where various things are in your system (such as > the news active file). Grep through every directory till > you find what has to be changed. > etc. > 2: It is excessively obese. > The stripped binary is significantly in excess of 1 meg in > size. Much of this is due to the inclusion of help text > within the binary instead of in a separate help file. This > means that an experience user who need no help must > nevertheless load the help information into memory whenever > she uses the software. > 3: It screws up message status of the default mailbox. > It always opens my default mailbox, whether I want it to > or not. The status of messages in that mailbox changes > from New to Unread, even though I have not asked to > read the mailbox, and have not seen the list of messages > in that mailbox. > 4: The menu interface is tedious and unintuitive. > When reading news, it displays a humongous list of newsgroups > for me to select from. I have to actually select each in turn > to discover that there are no unread messages in that newsgroup. > After reading one newsgroup, if I want to select another I > must go back and re-select the news collection, and have it > redisplay the menu, then I must page through the menu to > about where I was. Perhaps I am missing some shortcut here, > but the keypresses indicated on the screen display do not > provide a shorter alternative. > 5: Poorly timed user unfriendly prompts. > If I read my mail, then spend some time reading usenet, at > the end it asks me if I really wanted to delete those > messages from my mailbox. But that might be so long after I > asked to delete them that I have forgotten the details. If > the program wants to second guess and ask for confirmation, > it should do it much earlier, perhaps as soon as a different > folder is selected. >Sorry, but there is no point in my listing other mail programs which >do not have these faults. I am not aware of any other mail programs >which do have these faults. Well, try to write danish charaters in those other mail programs you mean are so good and send that mail from unix and read it on a PC :-) Do the same with one or another kind of document made by one or another programme. Then after that please tell me which of your mail programs I can get for free and that can do the same that easy :-) Eigil From owner-pine-info@cac.washington.edu Thu Oct 6 20:21:55 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11977; Thu, 6 Oct 94 20:21:55 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05381; Thu, 6 Oct 94 20:10:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05366; Thu, 6 Oct 94 20:10:06 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt5Iu-00000NC; Thu, 6 Oct 94 19:45 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: "junk software and poor design" Date: Fri, 07 Oct 1994 03:06:14 +0100 Message-Id: References: <3700se$2p3@mp.cs.niu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Neil> I consider it to be one of the biggest pieces of junk Neil> software and poor design that I have encountered. > I'm curious why you think this. The UW folks have implemented many neat features, some a tad overbearing, but most of them are safe and easy to use and well documented, both for beginners and experienced users. Pine definitely excels in this area. However, when you look at the monstrous sources, you will find a lot of debatable clutter making pine larger and slower than necessary and hard to overview and maintain. Once you need to make some adaptations to your local environment you start to wonder why things like the path to your news spool or the newmail poll time aren't organized in one single config.h for all architectures or at least all flavors of Unix. From owner-pine-info@cac.washington.edu Thu Oct 6 21:41:30 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13706; Thu, 6 Oct 94 21:41:30 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06813; Thu, 6 Oct 94 21:35:24 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06807; Thu, 6 Oct 94 21:35:21 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qt6dR-00000MC; Thu, 6 Oct 94 21:10 PDT To: pine-info@cac.washington.edu From: jemorti@relay.nswc.navy.mil (Jack Mortimer - E81) Subject: Re: Signature *after* quoted text in replies? Message-Id: <1994Oct5.173226.29279@relay.nswc.navy.mil> References: <366vp2$5mq@explorer.clark.net> <367hhc$bd6@crcnis1.unl.edu> <1994Oct2.121417.1@jaguar.uofs.edu> <36msas$nub@news.halcyon.com> <36n58j$rks@mark.ucdavis.edu> Date: Wed, 5 Oct 1994 17:32:26 GMT In article , earl@tyrell.net (Nick Danger) writes: |> |> : If you are using pine 3.90, go to "Setup" and choose Configure. Scroll |> : down the list until "Signature at bottom". Put an x in this box, exit |> : setup and restart PINE. That's it. |> |> I wonder why the author has this backwards. Wouldn't it make much more |> sense to have the signature default to the bottom and have a |> configuration option to have it at the top? It sure would elimininate a |> LOT of confusion. |> It seems to me that you are signing the message, not the attachment. So having the .sig file after your message, but before the attachment, makes lots of sense. Maybe we have lost/gained something by dealing so much with electronic communications. Perhaps we can benefit from some traditional correspondance training. I know it would help me. Jack From owner-pine-info@cac.washington.edu Fri Oct 7 01:51:59 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18833; Fri, 7 Oct 94 01:51:59 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04046; Fri, 7 Oct 94 01:46:14 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04040; Fri, 7 Oct 94 01:46:11 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtAfO-00000fC; Fri, 7 Oct 94 01:28 PDT To: pine-info@cac.washington.edu From: jtbell@presby.edu (J. Alan Alexander) Subject: Re: Hey, how to find out the local nntp server? Message-Id: Date: Fri, 7 Oct 1994 04:16:14 GMT References: <36v9gc$43t@spool.cs.wisc.edu> In article <36v9gc$43t@spool.cs.wisc.edu>, Ah! My Goddess wrote: >Hey how to find out where is the local nntp server for pine? You could call up your computing center on the phone and ask... Really, this is a local-type question which can only be answered locally. -- Jon Bell Presbyterian College Dept. of Physics and Computer Science Clinton, South Carolina USA From owner-pine-info@cac.washington.edu Fri Oct 7 03:16:52 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20621; Fri, 7 Oct 94 03:16:52 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05027; Fri, 7 Oct 94 03:11:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05021; Fri, 7 Oct 94 03:11:39 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtBx7-00000hC; Fri, 7 Oct 94 02:51 PDT To: pine-info@cac.washington.edu From: russell@alpha3.ersys.edmonton.ab.ca (Russell Schulz) Subject: using `reply' to post?!? (was Re: Newsgroups: in mail replies?) Message-Id: <941006.223718.9U6.rusnews.w164w_-_@alpha3.ersys.edmonton.ab.ca> Date: Thu, 6 Oct 1994 22:37:18 -0600 References: David L Miller writes: > with a Newsgroups: header was posted to the list and the user should be > queried about posting the reply as a followup. at no time when a user says they want to reduce traffic should the software encourage them to increase it! -- Russell Schulz russell@alpha3.ersys.edmonton.ab.ca ersys!rschulz Shad 86c From owner-pine-info@cac.washington.edu Fri Oct 7 03:19:09 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20671; Fri, 7 Oct 94 03:19:09 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11143; Fri, 7 Oct 94 03:08:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11137; Fri, 7 Oct 94 03:08:44 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtBvM-00000aC; Fri, 7 Oct 94 02:49 PDT To: pine-info@cac.washington.edu From: russell@alpha3.ersys.edmonton.ab.ca (Russell Schulz) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Message-Id: <941006.213044.9o6.rusnews.w164w@alpha3.ersys.edmonton.ab.ca> Date: Thu, 6 Oct 1994 21:30:44 -0600 References: <36t8ok$n8h@mp.cs.niu.edu> <36ut98$mh4@news.halcyon.com> Nancy McGough writes: > Since Pine 3.90 is the first widely used Mailer-and-Newsreader-in-one, read: `most widely used to date'. Andrew does this. GNUS does this. this (non-widely-used) package does this. > Right now when Pine is viewing a message in a mail folder (i.e., inbox > or save-folder) it assumes that a To:_ header means the message was > mailed and a Newsgroups:_ header means the message was posted, and both > mean the message was both posted and mailed. this is obviously wrong. it should be fixed. -- Russell Schulz russell@alpha3.ersys.edmonton.ab.ca ersys!rschulz Shad 86c From owner-pine-info@cac.washington.edu Fri Oct 7 03:45:36 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21359; Fri, 7 Oct 94 03:45:36 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11556; Fri, 7 Oct 94 03:41:17 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11550; Fri, 7 Oct 94 03:41:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtCTF-000008C; Fri, 7 Oct 94 03:24 PDT To: pine-info@cac.washington.edu From: Xander.Jansen@SURFnet.nl Subject: Re: Custom Headers In-Reply-To: Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: References: <36vfrv$9vs@mark.ucdavis.edu> Mime-Version: 1.0 Date: Fri, 7 Oct 1994 09:37:55 GMT On Thu, 6 Oct 1994, Kenny Wickstrom (x2349) wrote: > I'll expand DLM's answer a little. Like he said, go to Setup/Configure > and select Add with Customized-hdrs highlighted. If you want to add an > organization name your input should be: > Organization: UCDAVIS Educational Center > > You can have more than one custom header by separating them by commas. > Note, that since you separate your headers by commas, you cannot have > commas in the header itself. Actually you can: # Add these customized headers (and possible default values) when composing customized-hdrs=Reply-To, Organization: SURFnet bv, Address: "Cluetinckborch, P.O. Box 19035, 3501 DA Utrecht, NL", Phone: +31 30 310290, Telefax: +31 30 340903 By surrounding the text-with-commas with ""'s you can have commas in a header. Xander From owner-pine-info@cac.washington.edu Fri Oct 7 05:50:30 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24464; Fri, 7 Oct 94 05:50:30 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07157; Fri, 7 Oct 94 05:39:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from beast.Trenton.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07151; Fri, 7 Oct 94 05:39:54 -0700 Received: from roar.Trenton.EDU by beast.Trenton.EDU (5.0/SMI-SVR4) id AA00687; Fri, 7 Oct 1994 08:38:12 +0500 Received: by roar.Trenton.EDU (5.0/SMI-SVR4) id AA12647; Fri, 7 Oct 1994 08:38:35 +0500 Date: Fri, 7 Oct 1994 08:38:34 -0400 (EDT) From: Shawn Sivy X-Sender: ssivy@roar To: pine-info@cac.washington.edu Subject: Monthly moving of folders Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 792 Is there a way to turn off the feature that asks to move your sent-mail and saved mail to a file called sent-mail-"month" then delete the previous months sent-mail and saved mail. I just want to keep my mail in one folder and clean it myself. I also do want to be asked these questions when I really want to quickly get in and read my mail. +-----------------------------------------------------------------------+ | Shawn Sivy, "Certified" Unix Sys. Adm. | E-mail: ssivy@Trenton.EDU | | Academic Computing Support Consultant | Phone: (609) 771-3474 | | Trenton State College | Fax: (609) 771-3484 | | Information Management | "Save a tree, send e-mail!" | +-----------------------------------------------------------------------+ From owner-pine-info@cac.washington.edu Fri Oct 7 09:20:12 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00599; Fri, 7 Oct 94 09:20:12 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10869; Fri, 7 Oct 94 09:12:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10853; Fri, 7 Oct 94 09:12:10 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtHag-000008C; Fri, 7 Oct 94 08:52 PDT To: pine-info@cac.washington.edu From: Leslie Troutman Subject: Network news question Date: Fri, 7 Oct 1994 09:12:41 -0500 (CDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Can anyone tell me if there is a way to remove unread messages from view at one time. Deleting messages one-by-one is time consuming and I have a number of lists where I simply scan the headers and look at only one or two items. Please reply to my email address. Thanks, Leslie =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Leslie Troutman EMAIL: TROUTMAN@UIUC.EDU Music User-Services Coordinator PHONE: 217-244-4071 University of Illinois at Urbana-Champaign FAX: 217-244-0398 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= From owner-pine-info@cac.washington.edu Fri Oct 7 09:46:36 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02096; Fri, 7 Oct 94 09:46:36 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11516; Fri, 7 Oct 94 09:40:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from uvaarpa.Virginia.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11510; Fri, 7 Oct 94 09:40:34 -0700 Received: from elvis.med.virginia.edu by uvaarpa.virginia.edu id aa11520; 7 Oct 94 12:40 EDT Received: by elvis.med.Virginia.EDU (5.65c/1.34) id AA21703; Fri, 7 Oct 1994 12:40:32 -0400 Date: Fri, 7 Oct 1994 12:40:31 -0400 (EDT) From: "Steven D. Majewski" X-Sender: sdm7g@elvis.med.Virginia.EDU To: pine-info@cac.washington.edu Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) In-Reply-To: <36voi9$rmq@mp.cs.niu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Pine is clearly doing (more or less) the "Right Thing" here. Once a message has been moved - from either INBOX (mail) or from the news spool or nntp-server into another folder, all a mail/news-reader has to go on is what's in the header. The scheme Neil Rickert suggest would break under these conditions. ( When I get replies on a query I've posted, I usually save them, whether they were posted replies or mail replies into a topic specific folder. I don't want to have to switch back and forth between folders when I'm working on a summary or other replies. ) How can a program tell if it was a posted or e-mailed reply, other than trying to infer from the headers? Inference isn't perfect, so it does have to ask for confirmation - and maybe that message could be made more clear. I'm not sure what it does to outgoing Newsgroups: header lines in all cases. I think it ought to propagate this info, even if the user doesn't post his reply. However, this will obviously make any inference even less likely to be true. Perhaps there does need to be some new header or convention defined. My newsreaders also allow a Cc: address, and they will mail AND post a reply if that is filled in. If I'm posting a reply to someone, I often CC: them personally as a courtesy. I always appreciate it when someone does the same - I don't always follow news every day, even if I've posted a message, so getting an email-reply of a message that is also posted is quite helpful. But, I have also gotten remarks from folks who don't like this double-reply. They always assume if they get a response in the mail, that it is a non-public response, and they reply by email; then get anoyed when they see also see my message show up in news. There is really no consensus about proper e-mail ettiquite is this matter - so maybe there needs to be a better convention for indicating all these cases clearly. ( and note that this is another case that "breaks" Neil Rickert's scheme. ) -- Steve Majewski (804-982-0831) -- -- UVA Department of Molecular Physiology and Biological Physics -- -- Box 449 Health Science Center Charlottesville,VA 22908 -- [ "Cheese is more macho?" ] From owner-pine-info@cac.washington.edu Fri Oct 7 10:02:27 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02889; Fri, 7 Oct 94 10:02:27 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17822; Fri, 7 Oct 94 09:52:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17816; Fri, 7 Oct 94 09:52:07 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtIDU-00000AC; Fri, 7 Oct 94 09:32 PDT To: pine-info@cac.washington.edu From: stanley@skyking.OCE.ORST.EDU (John Stanley) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 7 Oct 1994 14:45:38 GMT Message-Id: <373mui$65e@gaia.ucs.orst.edu> References: <36vi69$3aa@news.halcyon.com> <3713p0$5j7@gaia.ucs.orst.edu> <371vcr$9rq@news.halcyon.com> In article <371vcr$9rq@news.halcyon.com>, Nancy McGough wrote: >stanley@skyking.OCE.ORST.EDU (John Stanley) writes: >>Proper mailer behaviour is to ignore Newsgroups: headers. The fact that >>brain damaged newsreaders leave them in when composing mailed replies is >>not reason to change the current definitions of mail. > >I just tested TRN 3.5, TIN 1.2 PL2, NN 6.4.18, and PINE 3.90 by using >the r command to respond in mail to a USENET article. TRN, TIN, and NN >all included a Newsgroups: header in a mailed response to a news article. >Pine 3.90 did not include a Newsgroups: header when the response was >mailed only. Do you really think that TRN, TIN, and NN are brain damaged? If they leave Newsgroups: headers in mail they generate, yes. They are inserting undefined headers. >It seems clear that if there is going to be a standard header that means >that a mail message was simultaneously mailed and posted it will have You mean, like, the X-Also-Posted-To: I suggested? From owner-pine-info@cac.washington.edu Fri Oct 7 10:15:48 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03797; Fri, 7 Oct 94 10:15:48 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12194; Fri, 7 Oct 94 10:07:15 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12188; Fri, 7 Oct 94 10:07:12 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtIQl-00000JC; Fri, 7 Oct 94 09:46 PDT To: pine-info@cac.washington.edu From: cbh@vodka.wlo.dec.com (Chris Hedley) Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 7 Oct 1994 13:15:43 +0100 Message-Id: <3739o4$jmp@vodka.wlo.dec.com> References: <3700se$2p3@mp.cs.niu.edu> <3713u8$phs@news.halcyon.com> <371eau$h4l@mp.cs.niu.edu> On 6 Oct 1994 13:06:22 -0500, Neil Rickert (rickert@cs.niu.edu) wrote: > 1: It is a bitch to install. No more so than any other public domain software. In my experience, Pine was one of the easier packages to install that wasn't developed specifically for my type of system. Having to redefine the compiler type does not seem to me to be a major effort, especially bearing in mind some of the far more serious problems I have encountered with other packages; doing some minor tweaking to the makefiles is no big thing when you consider the amount of work that has gone into a program of this scale which is then freely distributed! > 2: It is excessively obese. Not a problem on demand-paged systems such as Unix and VMS, which are the most common platforms for Pine. Your claim that the help information must be loaded into memory whenever the software is used is incorrect. > 3: It screws up message status of the default mailbox. > It always opens my default mailbox, whether I want it to > or not. The status of messages in that mailbox changes > from New to Unread, even though I have not asked to > read the mailbox, and have not seen the list of messages > in that mailbox. I haven't noticed it trying to open the default mailbox if I specify an alternative on the command line. As for changing the status of new messages to unread, every mailer I have used does this (correctly in my opinion). > 4: The menu interface is tedious and unintuitive. > 5: Poorly timed user unfriendly prompts. These are your opinions. Whilst you are entitled to them, please don't use them as reasons to substantiate your claim that the software is "junk". My opinion (which is independant, I have no connection with the Pine development team) is that Pine 3.90 is by far the best character- cell based mailing system available for Unix platforms that I have used, combining a large number of powerful features with an easy to use and pleasant user interface. And it's free. Cheers, Chris. From owner-pine-info@cac.washington.edu Fri Oct 7 10:29:23 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04622; Fri, 7 Oct 94 10:29:23 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18598; Fri, 7 Oct 94 10:22:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18582; Fri, 7 Oct 94 10:22:29 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtIgW-000008C; Fri, 7 Oct 94 10:02 PDT To: pine-info@cac.washington.edu From: mark stephan Subject: pine/.mailrc nickname converter Date: 6 Oct 1994 21:12:00 GMT Message-Id: <371p70$37d@lastactionhero.rs.itd.umich.edu> Do any of you have a convertor that will take pine nicknames and convert them too .mailrc or Eudora format? Thank you markstep@chgdss10.chgd.med.umich.edu From owner-pine-info@cac.washington.edu Fri Oct 7 10:30:07 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04661; Fri, 7 Oct 94 10:30:07 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12605; Fri, 7 Oct 94 10:22:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12593; Fri, 7 Oct 94 10:22:40 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtIhE-00000AC; Fri, 7 Oct 94 10:03 PDT To: pine-info@cac.washington.edu From: oqp@cw-u03.umd.umich.edu (Christopher Bibbs) Subject: Help! Date: 7 Oct 1994 00:40:03 GMT Message-Id: <3725d3$4nf@lastactionhero.rs.itd.umich.edu> Is there any way to allow/make pine run under vt52 emulation? Please let there be a way. -- Christopher Bibbs | Like a baby stillborn chrisbib@umich.edu | Like a beast with his horn http://www.umd.umich.edu/~oqp | I have torn everyone who reached out for me. Ask me about relativity. | -Leonard Cohen Geek Code: GSS d? -p+ c++(+++) l- u+(++) e+ m+ s-/ n+(--) h-- f+@* g+ w+ t++(+++) r@+ y++ From owner-pine-info@cac.washington.edu Fri Oct 7 13:34:06 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14093; Fri, 7 Oct 94 13:34:06 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23020; Fri, 7 Oct 94 13:27:55 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23014; Fri, 7 Oct 94 13:27:53 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtLb1-00000DC; Fri, 7 Oct 94 13:08 PDT To: pine-info@cac.washington.edu From: zagar@chester.cms.udel.edu (Randy Zagar) Subject: Cross-platform Pine/IMAP problem... Date: 7 Oct 1994 17:44:44 GMT Message-Id: <3741ec$7pr@news-4.nss.udel.edu> I haven't tried digging through the code yet, but I think I've identified a problem with Pine and IMAP. From what I can tell, it is Pine that supplies the full pathname of the INBOX when Pine is using the IMAP service This can be a real problem if (as I am) you are dealing with several different operating systems that happen to *NOT* agree on where the users' INBOX is stored SunOS-4.1.3 /var/spool/mail Solaris-2.X /var/mail IRIX-5.x /usr/var/mail This list is not complete, other systems put things in places other than those listed above. I discovered this problem while testing the Solaris version of IMAP with a SunOS Pine client. Pine kept telling me that my mailbox was empty until I created a symbolic link on the Solaris system from /var/spool/mail to /var/mail. I don't think the client (i.e. Pine) should be telling the server (IMAP) where to look for the users' INBOX. -Randy --- ______________________________________________________________________ / \ | Randy Zagar | Voice: 302/831-1139 | | College of Marine Studies | FAX: 302/831-6838 | | University of Delaware | Internet: zagar@Chester.cms.udel.edu | | Newark, DE 19711 | Compu$erve: 73072,1413 | |----------------------------------------------------------------------| | PGP Key available on request, or by 'finger'. | \______________________________________________________________________/ From owner-pine-info@cac.washington.edu Fri Oct 7 13:37:59 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14269; Fri, 7 Oct 94 13:37:59 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17231; Fri, 7 Oct 94 13:32:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17225; Fri, 7 Oct 94 13:32:41 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtLhy-00000LC; Fri, 7 Oct 94 13:16 PDT To: pine-info@cac.washington.edu From: mcdowelt@rintintin.Colorado.EDU (Tim McDowell) Subject: Need help with Pine-Eudora interaction!! Date: 7 Oct 94 17:37:02 GMT Message-Id: Hi: My boss reads his mail using Pine, and leaves it in the in box. Later Iam expected to come into the same account using Eudora and bring the mail up unto my laptop for printing. The trouble is it appears that Eudora picks up on the fact that the mail was marked read by Pine, and does not download it to my laptop. QUESTION: Is there a way to configure Pine so that it does not mark messages as read so that when I come in to the mail under Eudora I get all the mail downloaded to me. I'd greatly appreciate a response to my email at mcdowelt@rintintin.colorado.edu. Tim From owner-pine-info@cac.washington.edu Fri Oct 7 13:47:15 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14860; Fri, 7 Oct 94 13:47:15 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23295; Fri, 7 Oct 94 13:42:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23289; Fri, 7 Oct 94 13:42:51 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtLnL-00000MC; Fri, 7 Oct 94 13:21 PDT To: pine-info@cac.washington.edu From: hribnak@nucleus.com (Jim Hribnak) Subject: Bug in pine 3.90? Message-Id: Date: Fri, 7 Oct 1994 17:28:30 GMT One user on our system (so far) is getting the following: Bug in Pine detected: "Recieved abort signal" He gets this when quitting pine every time and produces a core.pine file (I am on BSDI/386 v1.1) I use pine constantly all day long and I have never encountered this.. Jim Hribnak Nucleus Information Service VP Operations, Nucleus Inc. 55 Lines (403)531-9353 (2400) ----------------------------------------- (403)531-9370 (19200) hribnak@nucleus.com (403)249-9009 (voice) From owner-pine-info@cac.washington.edu Fri Oct 7 13:55:14 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15053; Fri, 7 Oct 94 13:55:14 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17581; Fri, 7 Oct 94 13:49:29 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17575; Fri, 7 Oct 94 13:49:27 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25264; Fri, 7 Oct 94 13:49:23 -0700 Date: Fri, 7 Oct 1994 13:49:20 -0700 (PDT) From: Terry Gray To: Randy Zagar Cc: pine-info@cac.washington.edu Subject: Re: Cross-platform Pine/IMAP problem... In-Reply-To: <3741ec$7pr@news-4.nss.udel.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Randy, If, in your .pinerc or pine.conf, you use the form: inbox-path={imap-host}inbox rather than an explicit path name, then the imapd process will interpret "inbox" in accordance with he convention for the system it was built on. -teg On 7 Oct 1994, Randy Zagar wrote: > I haven't tried digging through the code yet, but I think I've > identified a problem with Pine and IMAP. From what I can tell, > it is Pine that supplies the full pathname of the INBOX when Pine > is using the IMAP service > > This can be a real problem if (as I am) you are dealing with several > different operating systems that happen to *NOT* agree on where the > users' INBOX is stored > > SunOS-4.1.3 /var/spool/mail > Solaris-2.X /var/mail > IRIX-5.x /usr/var/mail > > This list is not complete, other systems put things in places other than > those listed above. > > I discovered this problem while testing the Solaris version of IMAP with > a SunOS Pine client. Pine kept telling me that my mailbox was empty until > I created a symbolic link on the Solaris system from /var/spool/mail > to /var/mail. > > I don't think the client (i.e. Pine) should be telling the server (IMAP) > where to look for the users' INBOX. > > -Randy > > --- > ______________________________________________________________________ > / \ > | Randy Zagar | Voice: 302/831-1139 | > | College of Marine Studies | FAX: 302/831-6838 | > | University of Delaware | Internet: zagar@Chester.cms.udel.edu | > | Newark, DE 19711 | Compu$erve: 73072,1413 | > |----------------------------------------------------------------------| > | PGP Key available on request, or by 'finger'. | > \______________________________________________________________________/ > > > From owner-pine-info@cac.washington.edu Fri Oct 7 14:42:01 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17204; Fri, 7 Oct 94 14:42:01 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24245; Fri, 7 Oct 94 14:24:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva2.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24233; Fri, 7 Oct 94 14:24:43 -0700 Received: by shiva2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13503; Fri, 7 Oct 94 14:24:42 -0700 Date: Fri, 16 sep 94 09:41:16 -0700 From: Pine Development Team Message-Id: <9408241626.AA29044@shiva2.cac.washington.edu> Mime-Version: 1.0 Content-Type: MULTIPART/DIGEST; BOUNDARY="==========" Subject: Pine Frequently Asked Questions Resent-Date: Fri, 7 Oct 1994 14:24:20 -0700 (PDT) Resent-From: David L Miller Resent-To: pine-info@cac.washington.edu Resent-Message-Id: --========== Content-Description: Contents Subject: Contents PINE FREQUENTLY ASKED QUESTIONS The following questions have been compiled from questions asked on the pine-info and pine-bugs mailing lists. General * What is Pine? * What is MIME? * What is IMAP? * How can I get a copy of Pine? * Is there a manual? * What mailing lists and newsgroups are there dealing with Pine? * What are all these funny names in your examples? * How many sites use Pine? Errors and Problems * I have found a bug in Pine 3.05. Could you please fix it? * If I postpone a Reply, there is no 'A' in the index after I resume and send it. * "Folder Format Invalidated (consult an expert), aborted" * What is folder locking and how does it work? * What happens when two Pine sessions access the same mailbox simultaneously? * Why did I get the message "locked, override in XXX sec"? * Why is a charset=US-ASCII attachment sent using BASE64 encoding? Usage * How do I keep all of the names from showing up at the top of the message? * How do I use Ispell with Pine (and Pico)? * How can I have a signature automatically appended to my mail messages? * How do I read News with Pine? * Can I post news with Pine? * How do I "paste" an address from the addressbook into the text of a message? * How can I filter messages into different incoming folders? * Can I define a Reply-To: header? * Can I execute Pine from a shell script so I can use my addressbook? * xbiff lets me know about new mail, but pine doesn't know about it. * How can I read a ROT13 encoded message? Installation and Configuration * Can Kerberos or AFS authentication be used with Pine? * Can PC-Pine be used with a POP server? * What is a Tenex mailbox and why should I use it? * Where does Unix Pine look for configuration information? * Where does PC-Pine look for configuration information? * How do I make Pine work with my older terminal? * How do I configure Pine to not leave mail in /usr/spool/mail? Platform Specific * To what platforms has Pine been ported? * Pine 3.89 on an IBM RS/6000 running AIX 3.2.3 crashes every time I try to open a folder. * What PC comm software works with the "Print to ANSI" print option? * What Mac comm software works with the "Print to ANSI" print option? * What Amiga comm software works with the "Print to ANSI" print option? Conversions * How can someone without a MIME-aware mail program decipher an attachment? * How do I convert a Sun Mailtool attachment to MIME format? * How do I convert Berkeley Mail aliases to Pine Addressbook? * How do I convert Elm aliases to Pine Addressbook? Development Info * What are the current versions of Pine and related software? * What is new in this version of Pine? * When is the next release of Pine (tentatively) scheduled? * What new features will the next release of Pine include? --========== Content-Description: General Questions About Pine Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: General Questions About Pine GENERAL QUESTIONS ABOUT PINE ------------ Content-Description: What is Pine? Subject: What is Pine? Pine(tm) --a Program for Internet News & Email-- is a tool for reading, sending, and managing electronic messages. It was designed specifically with novice computer users in mind, but can be tailored to accommodate the needs of "power users" as well. Pine uses Internet message protocols (e.g. RFC-822, SMTP, MIME, IMAP, NNTP) and runs on Unix and PCs. The guiding principles for Pine's user-interface 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. It has the ability to perform full screen editing of messages, attachments (such as Word or Excel files), and other advanced message system features. Pine uses IMAP for accessing message folders on remote computers and MIME for sending multimedia or other binary files as attachments to normal messages. ------------ Content-Description: What is MIME? Subject: What is MIME? MIME (RFC 1521) stands for "Multipurpose Internet Mail Extensions". It is an Internet standard which allows transfer of binary files (word-processing documents, spreadsheets, images, sounds, etc) between any compliant mailers. You can get technical information about MIME from the RFC. Ongoing discussion on MIME takes place in the newsgroup comp.mail.mime. There is also a Frequently Asked Questions (FAQ) list that is posted regularly to comp.mail.mime and comp.answers. ------------ Content-Description: What is IMAP? Subject: What is IMAP? IMAP stands for "Internet Message Access Protocol". An IMAP client program on any platform at any location on the Internet can access email folders on an IMAP server. While the messages appear to be local, they reside on the server until the client explicitly moves or deletes them. The IMAP protocol is a functional (but incompatible) superset of POP. A principal advantage of IMAP over POP is that it permits using more than one computer to access your mail. Using multiple computers with POP typically results in your mail ending up scattered across all of those computers. Another key advantage is IMAP's ability to selectively access parts of messages, e.g. you don't have to wait for a 2MB audio attachment to be retrieved until you specifically ask for it. This is a big win over low-speed (e.g. dialup) connections. For a detailed comparison of IMAP and POP, see the paper "Comparing Two Approaches to Remote Mailbox Access: IMAP vs. POP." IMAP is what allows Pine (or any other IMAP client) to access email on a remote mail server, usually one that is shared (central or departmental). There is an IETF working group currently defining the IMAP4 revision to the IMAP2 specification (RFC-1176). A copy of the latest IMAP draft may be obtained from ftp.cac.washington.edu in the file imap/latest-imap-draft ------------ Content-Description: How can I get a copy of Pine? Subject: How can I get a copy of Pine? Pine is available via anonymous ftp from the pine directory of ftp.cac.washington.edu. See the Installation Instructions for Pine for more information. ------------ Content-Description: Is there a manual? Subject: Is there a manual? The Pine program itself includes extensive online help. Additional documentation may be found via anonymous FTP or via World-Wide-Web using the following URLs: ftp://ftp.cac.washington.edu/pine http://www.cac.washington.edu/pine The Pine program itself also includes extensive online help. Other forms of access are planned for the future. ------------ Content-Description: What mailing lists and newsgroups are there dealing with Pine? Subject: What mailing lists and newsgroups are there dealing with Pine? The "comp.mail.pine" newsgroup is devoted to Pine. It is bi-directionally gatewayed to the "pine-info" mailing list described below. The following mailing lists deal with Pine and related topics: Pine-Info@cac.washington.edu Pine-Info is a mailing list for the email program Pine. The mailing list includes discussion of Pine features, bugs, tricks, etc. Often technical and installation questions appear on the list. New releases, fixes and version of Pine are announced on the pine-info mailing list. For official announcements only, you may wish to see pine-announce instead of this list. To subscribe to pine-info, send a message to majordomo@cac.washington.edu with subscribe pine-info in the body of the message. Owners of this mailing list can be contacted at owner-pine-info@cac.washington.edu. Pine-Announce@cac.washington.edu Pine-Announce is a announcement list for the email program Pine. When new Pine products are released and old ones updated, a message goes out to this group describing the development. It is a very low volume list and includes no discussion whatsoever. _All messages to this list are automatically forwarded to pine-info, so it is not necessary to subscribe to both lists._ To subscribe to pine-announce, send a message to majordomo@cac.washington.edu with subscribe pine-announce in the body of the message. Owners of this mailing list can be contacted at owner-pine-announce@cac.washington.edu. IMAP@CAC.Washington.EDU This is the official mailing list for the IETF IMAP working group and other interested parties. Discussion of the evolving IMAP standard and related issues is conducted on this list. To subscribe to IMAP, send a message to imap-request@cac.washington.edu. C-Client@CAC.Washington.EDU This list is for discussion of the C-Client library which is used by Pine and various other mail and IMAP clients and servers. ------------ Content-Description: What are all these funny names in your examples? Subject: What are all these funny names in your examples? In an attempt to avoid confusion with real places or services we decided to make up a ficticious user for our examples. This person is John Smith, who is currently an art major at the University of Nowhere (nowhere.edu). He previously attended Elsewhere Community College (elsewhere.edu). His username is jsmith and he uses the following machines: rembrandt.art.nowhere.edu A Unix timesharing machine. picasso.art.nowhere.edu An SMTP server. news.nowhere.edu A Usenet News server which supports both NNTP and IMAP access. davinci.art.nowhere.edu A PC-compatible workstation running MS-DOS. warhol.art.nowhere.edu An IMAP server. fozzie.elsewhere.edu An IMAP server at Elsewhere Community College. ------------ Content-Description: How many sites use Pine? Subject: How many sites use Pine? We don't have a good way to count the number of sites running Pine, but at last count over 4,000 sites in 40 countries had downloaded the Pine 3.89 distribution from ftp.cac.washington.edu. There are also several major archive sites that mirror the distribution, so the actual numbers are probably much higher. -------------- --========== Content-Description: Errors and Problems Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: Errors and Problems ERRORS AND PROBLEMS ------------ Content-Description: I have found a bug in Pine 3.05. Could you please fix it? Subject: I have found a bug in Pine 3.05. Could you please fix it? When a bug is identified in an old release, there is a very strong possibility that the associated code has been re-written to the point that a fix will not apply to the current release. Hence, if we can't reproduce the problem in the current version, our standard response will be to ask you to upgrade. ------------ Content-Description: If I postpone a Reply, there is no 'A' in the index after I resume and send it. Subject: If I postpone a Reply, there is no 'A' in the index after I resume and send it. This is a known limitation of the current release of pine. When you postpone a composition, Pine does not have any way to keep track of which message was being replied to (or that it was a reply at all). This limitation will be removed in a future release of Pine. ------------ Content-Description: "Folder Format Invalidated (consult an expert), aborted" Subject: "Folder Format Invalidated (consult an expert), aborted" The message "Folder Format Invalidated (consult an expert), aborted" means that Pine was reading your mail folder, and at the point in which it expected a start-of-message header line, it found something else. The ``format invalidated'' condition can happen in one of three ways: 1. bad data exists at the beginning of the folder. 2. data was appended to the folder after Pine initially read it, and the new data did not begin with a start-of-message-header. 3. the folder was modified without Pine being aware of it. All three problems are generally caused by software external to Pine. Condition (1) can be determined by whether or not the problem repeats itself after restarting Pine. If restarting Pine does not make the problem go away, then you need to look at the actual file for the folder and see what is wrong with the very first line. In particular, make sure that there are no blank lines at the beginning of the file and that the first character of the folder file is a capital ``F'' , the second an ``r'', the third an ``o'', etc. In the case of an INBOX, you may want to rename the folder so that new mail can be delivered while repairs on the corrupt folder are being done. Condition (2) may be caused by a mail delivery process (e.g. /bin/mail) which writes some characters other than ``From '' at the beginning of the new data. Condition (3) is caused by another program manipulating the mail folder without following the normal folder locking protocols. This is a general problem on UNIX. Conditions (2) and (3) have also been known to occur when accessing folders via NFS, if the information returned by the stat() and read() system calls do not correspond with each other as a result of NFS attribute caching. Restarting Pine on that folder always clears conditions (2) and (3). If the problem is chronic, it may be worth an investigation to determine its cause. Usually, it is due to the misbehavior of some external software. The reason why Pine gives up with conditions (2) and (3) is that it does not want to risk damaging user data by guessing what is right. Pine never writes to the folder unless it is absolutely sure it knows what it is doing. There are some steps which can be taken to reduce the risk of these conditions coming up. Some of these steps may require the assistance of your system adminstrator (or whomever it was that built and installed Pine on your system): 1. Use IMAP instead of NFS to access remote folders. Problems with locking over NFS are perhaps the single most important cause of user difficulties. Using IMAP eliminates this class of problem. 2. Consider enabling the mbox driver in Pine. If the mbox driver is enabled, mail is transferred from the /usr/spool/mail mail into a file called mbox in your home directory, if mbox exists. The home directory mbox file is then your INBOX. This has the advantage that Pine and the mail delivery system are less often in contention for the INBOX, and never both trying to update it. Pine only empties the /usr/spool/mail file, it never tries updating it. 3. Be careful not to run other programs that modify your folders while you are running Pine. Such programs may change the folder out from under Pine, and lead Pine to conclude that there is a problem with its view of the file. ------------ Content-Description: What is folder locking and how does it work? Subject: What is folder locking and how does it work? Locks are used by Pine and other mail programs to prevent damage from occurring to the mail file when multiple programs try to write to the file at the same time. Because there are many different schemes of mail file locking used on UNIX, Pine implements all of them. The result is a lot of complexity. There are several reasons why locking needs to be done: 1. If you want to read the mail file, you want to make sure that no other process will modify the mail file while you are reading it. 2. If you want to write to the mail file, you want to make sure that no other process is accessing the mail file while you are writing it. 3. If you have the mail file open, you want to make sure that no other process can alter any of the internal contents of the mail file that you have read, but it is OK if another process appends new data to the mail file. 4. If you want to alter any of the internal contents of the mail file, you want to make sure that no other process has the mail file open. There are several mechanisms of locking: * The creation of a file which has the same name as the mail file, but with a suffix of ".lock" (for example, this lock for /usr/spool/mail/isma is named /usr/spool/mail/isma.lock). This file accomplishes locks (1) and (2) above. This is an exclusive lock. * The use of an flock() with LOCK_SH on the mail file. This accomplishes lock (1), and prevents lock (2). Multiple processes can do this. * The use of an flock() with LOCK_EX on the mail file. This accomplishes lock (2), and prevents lock (1). This is an exclusive lock. * The use of an flock() with LOCK_EX on a file on /tmp. The file name used depends upon the version of Pine. This accomplishes locks (3) and (4). This is an exclusive lock. On SVR4-based systems, the lockf() subroutine or fcntl() system call it used instead of flock(). It is rumored that this creates a kind of lock file as well, but this has not been directly verified. _NOTE: flock() on BSD systems does not work over NFS, so only the most basic .lock file locking -- locks (1) and (2) happen over NFS. On SVR4 systems, fcntl() locking attempts to work over NFS, but there are known problems in the rpc.lockd daemon which have caused hangs if an application beats on the mechanism too much (and Pine beats on it). All of the above mechanisms work reliably over IMAP connections._ _[MRC]_ ------------ Content-Description: What happens when two Pine sessions access the same mailbox at the same time? Subject: What happens when two Pine sessions access the same mailbox at the same time? This varies depending on what format your folders are stored in. With the default Berkeley format, the last session to open a folder will get full access to the folder and the previous session(s) will be changed to read-only access. When a folder is read-only, you will not see any further updates to that folder until it is reopened with full access. Currently the INBOX cannot be reopened without exiting and restarting Pine. With the Tenex format, any number of sessions can simultaneously have full access to a folder, with the exception that expunging is disabled. See "What is a Tenex mailbox and why should I use it?" for more information. ------------ Content-Description: Why did I get the message "locked, override in _XXX_ sec"? Subject: Why did I get the message "locked, override in _XXX_ sec"? The message "locked, will override in _xxx_ seconds" occurs when Pine has discovered that some other mail program claims to be accessing your mail folder (i.e. _folder_.lock exists). This is a very low-level lock used by programs such as the system mailer in delivering mail, and by certain programs such as mail, elm, babyl, mm, etc. Supposedly, this lock is only to be acquired and held for a very short period of time (less than a second). It starts with 285 seconds, retries every second, and issues that message every 15 seconds. The total period of time, 5 minutes, is the time that it will keep on trying before it concludes that the lock is false -- that is, that whatever program locked the folder forgot to unlock it (perhaps it crashed) -- and Pine will go ahead and claim the lock for itself. This is not due to a conflict between two copies of Pine, since Pine interlocks against itself in a higher-level fashion. _NOTE: On some systems with 14 character filename limits, attempting to open a folder with a 14 character name (e.g. saved-messages) will trigger this sequence. Folder names should be limited to 9 characters or less on those systems._ ------------ Content-Description: Why is a charset=US-ASCII attachment sent using BASE64 encoding? Subject: Why is a charset=US-ASCII attachment sent using BASE64 encoding? Pine BASE64-encodes all attachments, including text, in order to assure that they are not modified in transit. The goal is make sure file attachment in Pine is as dependable as FTP (and BASE64 is safer than Quoted-Printable). A good example of why this is handy is when we recently asked some folks to attach their addressbooks to help us track down problems in 3.90, we didn't have to worry about whether a gateway had modified a tab or trailing blanks, etc, etc. -------------- --========== Content-Description: Usage Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: Usage USAGE ------------ Content-Description: How do I keep all of the names from showing up at the top of the message? Subject: How do I keep all of the names from showing up at the top of the message? Put addresses and/or list from your address book in the Bcc: (blind carbon copy) header field. You will see all the names and addresses as you compose the message, but they are erased before arriving in other people's INBOXes. The Bcc: header is not displayed automatically in the default Pine configuration, so you may need to use the rich headers command (Ctrl-R) while the cursor is in the header to expose it. ------------ Content-Description: How do I use Ispell with Pine (and Pico)? Subject: How do I use Ispell with Pine (and Pico)? Here are a couple ways to use Ispell within Pine: 1. Set your alternate-editor to ispell, then ^_ in the composer invokes ispell. To do this set "editor=/usr/local/bin/ispell" in your .pinerc file. This may be set within Pine via the _OPTIONS_ task of the _SETUP_ command from the main menu. Now, when you press ^_ (Control-Underscore) in Pine, you will execute the ispell program in its native mode. Press ? for help. Press I to insert unknown words into the personal dictionary. You can still press Ctrl-T to use the standard pine spell-checking program (which will -not- use your personal dictionary). See 'man ispell' for more information on the ispell program. 2. Pine already checks the SPELL environment variable so you can create the following script and name it spell. #!/bin/sh ispell -l | sort | uniq To make Ctrl-T in pine use 'ispell' and your '$HOME/.ispell_words' dictionary: + make the above script file 'spell' in your home directory + make it executable: 'chmod u+x spell' + set the environment variable SPELL: 'setenv SPELL $HOME/spell' (you may include this command in your .profile, .cshrc or .login file) Now, when you press Ctrl-T in Pine, you will execute the ispell program, and it will recognize words stored in the private dictionary. The screen display will look like pine is using the standard spell-checking program. Unfortunately, this method does not allow the user to Insert words into the private dictionary. However, this might be useful with a central script file (setenv SPELL ...) and a central private dictionary (ispell -p ...) to provide a common private dictionary for an entire workgroup. The manager could add items to the private dictionary; ordinary pine users would use the private dictionary (Ctrl-T), but they could not change it. To use ispell with pico, implement the 'ispell' program via ^T (CTRL-T) (using the script file) in addition to implementing it via ^_ (CTRL-_) (using the .pinerc file). * Use Ctrl-_ in Pine (it won't work in Pico) for full-featured ispell. * Use Ctrl-T in Pico to use the ispell program and your .ispell_words dictionary (but without the full ispell functionality). You can use Ctrl-T/ispell in Pine also, but why bother when Ctrl-_ works better. _[Mike Ramey ]_ ------------ Content-Description: How can I have a signature automatically appended to my mail messages? Subject: How can I have a signature automatically appended to my mail messages? Using your favorite text editor (e.g. Pico), create a file in your home directory called .signature containing the text you want appended to each message. For more detailed information see The Signature and Finger Frequently Asked Questions list which is posted periodically to the comp.mail.pine and comp.mail.misc newsgroups. PC-Pine users should put their signatures in the file \PINE\PINE.SIG. ------------ Content-Description: How do I read News with Pine? Subject: How do I read News with Pine? Three ways to access news via Pine: 1. Local News. If news is stored on the same machine you run Pine on, you can specify: news-collections=News *[*] 2. Via NNTP. Your .newsrc file must be on the machine where Pine is running. Assuming news is stored on the machine news.nowhere.edu, a typical .pinerc entry would be: news-collections=News *{news.nowhere.edu/nntp}[*] Alternatively, if the nntp-server variable is set, your news-collections will default to NNTP access from the same server. 3. Via IMAP. Your .newsrc file must be on the machine where news is stored. Assuming news is stored on the machine news.nowhere.edu, a typical .pinerc entry would be: news-collections=News *{news.nowhere.edu}[*] The advantage of option #3 is that the same .newsrc can be used for both Unix Pine and PC-Pine. The disadvantage is that you must have an account on the machine that stores the news and runs the NNTP server. ------------ Content-Description: Can I post news with Pine? Subject: Can I post news with Pine? Versions of Pine prior to Pine 3.90 do not support posting. In Pine 3.90 and later you can enter a list of newsgroups on the newsgrps: header to post a message. ------------ Content-Description: How do I "paste" an address from the addressbook into the text of a message? Subject: How do I "paste" an address from the addressbook into the text of a message? Pine does not currently support this directly, but here is a work-around: 1. Move the cursor to the Cc: line. 2. Enter the nickname or press Ctrl-T to search the addressbook and select the entry. 3. Use Ctrl-K to delete that address from the Cc: line. 4. Move the cursor where you want it in the body of the message. 5. Press Ctrl-U to insert the address. This is kind of a round-about way to get the job done, but it works... ------------ Content-Description: How can I filter messages into different incoming folders? Subject: How can I filter messages into different incoming folders? Pine does not do delivery filtering. That function is done by other programs, such as "procmail", or "filter" or "deliver". Once you have set-up your delivery filtering, e.g. via the "filter" program, then you will have new mail arriving in several different mailboxes/folders, in addition to your INBOX. So then the question becomes, how do you access those new "incoming message" folders that your favorite delivery filter program has created? Pine's answer is to let you specify them in your .pinerc, as in the example: incoming-folders=Art151 {warhol.art.nowhere.edu}filter/to-art151, Art-L {warhol.art.nowhere.edu}filter/to-Art-L, Old-Student-Acct {fozzie.elsewhere.edu}INBOX In this case, the pinerc entries presume that your delivery filtering program has been configured to put mail relating to the Art151 class into the folder "filter/to-art151" and mail relating to the Art-L mailing list into "filter/to-Art-L". From the Folders List screen, you can then easily access those folders. Eventually we will have a way to indicate which of these may have new mail waiting for you, so that you don't "forget" that you have more than one place to look for new mail... ------------ Content-Description: Can I define a Reply-To: header? Subject: Can I define a Reply-To: header? Yes. This is a new feature of Pine 3.90. It is handled as a "custom header" and can be added into that field via Pine's new configuration screen. ------------ Content-Description: Can I execute Pine from a shell script so I can use my addressbook? Subject: Can I execute Pine from a shell script so I can use my addressbook? Not currently. ------------ Content-Description: When I get new mail, xbiff lets me know about it, but pine doesn't know about it. Subject: When I get new mail, xbiff lets me know about it, but pine doesn't know about it. There are currently two ways to force a new mail check. * At the last message in a folder, press 'N' 4-5 times. * Press `Ctrl-L' (Refresh Display). ------------ Content-Description: How can I read a ROT13 encoded message? Subject: How can I read a ROT13 encoded message? When viewing the message, use the '|' (Pipe) command and give it the following: tr '[A-Za-z]' '[N-ZA-Mn-za-m]' -------------- --========== Content-Description: Installation and Configuration Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: Installation and Configuration INSTALLATION AND CONFIGURATION ------------ Content-Description: Can Kerberos or AFS authentication be used with Pine? Subject: Can Kerberos or AFS authentication be used with Pine? Not yet, but Kerberos support is planned for a future release of Pine. If you have access to Kerberos or AFS compatible IMAP clients already, the following information may be useful. The current version of imapd does not support AFS or Kerberos authentication. However, the routine which validates authentication is designed as a drop-in module, to allow you to replace with alternative authentication schemes such as AFS, Kerberos, S/Key, etc. This routine is server_login(). Depending upon which version of c-client you have, it is either in the os__xxx_.c (where _xxx_ is the name of your port) or it is in a file named log__yyy_.c which is included by the os_xxx.c file. The log__yyy_.c is usually log_std.c (std for "standard UNIX"), but it may be log_sv4.c (SVR4) or a couple of other variants. This file only contains that one routine, so it should be a simple matter to modify that file and rebuild imapd. ------------ Content-Description: Can PC-Pine be used with a POP server? Subject: Can PC-Pine be used with a POP server? No. Neither Pine nor PC-Pine currently support POP's offline mail model (wherein pending mail is pulled from the mail server to the local machine and deleted from the server). However, it is likely that this model will be supported, with a choice of either IMAP or POP as the access protocol, in a future release. ------------ Content-Description: What is a Tenex mailbox and why should I use it? Subject: What is a Tenex mailbox and why should I use it? Using the Tenex format for INBOXes allows multiple sessions (or mulitple users, subject to the usual access controls) to have *almost* full Read-Write access to the INBOX. The only limitation on full RW access is that if there are multiple sessions at a given moment, no one can do an Expunge. However, message state changes (e.g. marking a msg as deleted) *can* be done, and this state is preserved across sessions. If an explicit Expunge cmd fails, it will say so and tell you that the mailbox is in use by another process. When there is only one session left using that mailbox, expunge will resume working again. In contrast: the normal Berkeley style folders can have only one RW client at a time, so _given the current software_ the latest session steals the RW lock away from any previous session, with the earlier session becoming RO. ------------ Content-Description: Where does Unix Pine look for configuration information? Subject: Where does Unix Pine look for configuration information? In Pine 3.90, the Release Notes (Press "R" on the Main Menu) contain a section on Configuration, including default file names and environment variables. In brief, Unix Pine uses three configuration files: a system-wide file /usr/local/lib/pine.conf, a system-wide non-overridable file /usr/local/lib/pine.fixed, and a personal configuration file ~/.pinerc. There are certain options which are only found in system wide configurations, others only found in personal configurations, and still others found in both. For settings found in both pine.conf and .pinerc, values in .pinerc take precedence over those in pine.conf, and settings in pine.conf.fixed take precedence over everything. If you need to generate a "blank" copy of the system wide configuration files, run "pine -conf > /usr/local/lib ". Pine automatically generates a .pinerc when a user starts Pine for the first time. Starting with Pine 3.90, almost all personal configuration can be accomplished through the _SETUP_ command from the main menu. ------------ Content-Description: Where does PC-Pine look for configuration information? Subject: Where does PC-Pine look for configuration information? In Pine 3.90, the Release Notes (Press "R" on the Main Menu) contain a section on Configuration, including default file names and environment variables. In brief, PC-Pine uses the following rules for finding config and support files: 1. The location of the PINERC is searched for in the following order of precedence: 1. File pointed to by PINERC environment variable 2. $HOME\PINE\PINERC 3. A file named PINERC in the same directory as PINE.EXE 2. The HOME environment variable, if not set, defaults to root of the current working drive. 3. The default for external files (PINE.SIG and ADDRBOOK) is the same directory as the PINERC file. 4. The support files (PINE.HLP and PINE.NDX) are searched for in the same directory as PINE.EXE. Starting with Pine 3.90, almost all personal configuration can be accomplished through the _SETUP_ command from the main menu. ------------ Content-Description: How do I make Pine work with my older terminal? Subject: How do I make Pine work with my older terminal? Pine does not support some older terminals (e.g. tvi925, WYSE-60) very well. Some problems can be overcome with a proper termcap entry, but others, such as handling cursor keys, do not have a good solution. ------------ Content-Description: How do I configure Pine to not leave mail in /usr/spool/mail? Subject: How do I configure Pine to not leave mail in /usr/spool/mail? You have several options: 1. Leave inbox in /usr/spool/mail, but turn on the Pine option to prompt users to move read messages to a folder in their home directory upon exiting Pine. 2. Modify your mail delivery program to deliver mail directly into the user's home directory, and specify that inbox-path in your global pine.conf (See the "tmail" program on ftp.cac.washington.edu for an example.) 3. "touch mail.txt" in each home directory, which will cause Pine (upon startup) to pull mail from /usr/spool/mail into ~/mail.txt -- however, mail.txt will be a Tenex-format, rather than Berkeley mail format folder (faster, but non-standard). 4. Link in the "mbox" driver when you build Pine. This driver will (upon Pine startup) pull mail from /usr/spool/mail into ~/mbox, which will be a Bky-format folder. -------------- --========== Content-Description: Conversions Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: Conversions CONVERSIONS ------------ Content-Description: How can someone without a MIME-aware mail program decipher an attachment? Subject: How can someone without a MIME-aware mail program decipher an attachment? Regarding attachments: Pine uses the MIME Internet standard for this. MIME (Multipurpose Internet Mail Extensions) uses "Base64" encoding rather than uuencode, because uuencode uses characters that are transformed by some email gateways, and there are also several incompatible versions of uuencode. However, you can certainly uuencode a file outside of pine, then use the Composer's Ctrl-R (file inclusion) command to insert the encoded file in the message. If you use Pine's attachment feature, your recipient does need to have MIME-capable software. Fortunately, this is not hard to find. Even the major proprietary mail vendors have committed to MIME support, but some of their upgraded products are still some months away. One product which can decipher a MIME attachment is munpack from Carnegie Mellon. It is available from ftp.andrew.cmu.edu in the /pub/mpack directory. ------------ Content-Description: How do I convert a Sun Mailtool attachment to MIME format? Subject: How do I convert a Sun Mailtool attachment to MIME format? A perl script (and conversion to C of same) that converts OpenWindows mail to MIME. Body parts currently supported are: text, gif, Sun rasterfile (converted to image/gif), postscript, and audio. Other types default to application/octet-stream. It's easy to extend the set of types supported and to add conversions, if necessary. The script requires uuencode, uudecode, zcat (aka uncompress), and the "convert" program from ImageMagick. If you don't have ImageMagick you can probably substitute the pbm stuff with little fuss. The program is available via ftp from cs.utk.edu in pub/MIME/sun-to-mime.perl or pub/MIME/sun-to-mime.c _[Keith Moore ]_ ------------ Content-Description: How do I convert Berkeley Mail aliases to Pine Addressbook? Subject: How do I convert Berkeley Mail aliases to Pine Addressbook? The Pine source distribution includes a shell script to do this in the contrib/utils directory. It is called brk2pine.sh. ------------ Content-Description: How do I convert Elm aliases to Pine Addressbook? Subject: How do I convert Elm aliases to Pine Addressbook? Here's a little script one of our UNIX folks worked up to handle conversion of elm aliases to pine alias form (pretty simple syntax substitution). If you execute it multiple times it will keep adding another set of your elm aliases to your pine addressbook. #!/bin/csh #!/bin/csh -vx # convert elm aliases.text to pine addressbook # Greg Gustafson # UMD Information Services # January 1993 # if -r $HOME/.elm/aliases.text then if -e $HOME/.addressbook then set n=1 while (-e $HOME/.addressbook$n) @ n++ end mv $HOME/.addressbook $HOME/.addressbook$n endif ex - $HOME/.elm/aliases.text _[Joel Ness ]_ -------------- --========== Content-Description: Development Info Content-Type: MULTIPART/DIGEST; BOUNDARY="----------" Subject: Development Info DEVELOPMENT INFO ------------ Content-Description: What are the current versions of Pine and related software? Subject: What are the current versions of Pine and related software? The current version of Pine is 3.90. The current version of Pico is 2.4. ------------ Content-Description: What is new in this version of Pine? Subject: What is new in this version of Pine? These are the changes and improvements since Pine 3.89: * Finished all the "Not implemented yet" commands: + Bounce (Remail) + Flag (Set message status) + Pipe (Pipe msg to external cmd; Unix only) + Select,Apply,Zoom (Aggregate operations) + Setup/Config (Pinerc configuration screen) * News posting * News subscription/unsubscription * Multiple address books * Postpone multiple messages * Customizable headers for Composer * Mailcap support * Improved support for multiple incoming message folders * enable-alternate-editor-implicitly feature (except for editing headers) * All .pinerc features now settable from command line * Way to control which options are user-configurable (Unix only) * Way to have Save *not* implicitly delete * Way to use current-working-directory for Export, Read File, etc. * A _preliminary_ version of PC-Pine for Windows/Winsock (but not OS/2) ------------ Content-Description: When is the next release of Pine (tentatively) scheduled? Subject: When is the next release of Pine (tentatively) scheduled? We don't know right now, we just released this version. Besides, our track-record on meeting projected release schedules is terrible, so you shouldn't believe any dates we are foolish enough to suggest anyway. ------------ Content-Description: What new features will the future releases of Pine include? Subject: What new features will the future releases of Pine include? * Additional MIME support, esp. controlling file TYPING * PEM and/or PGP support * External directory services access * Kerberos support * RFC 1522 header encoding for 8bit character sets * Location independence of support files * Offline support * Hierarchy support (awaits IMAP4) * Answered flag not set if Reply is postponed (awaits IMAP4) * Faster detection of folders with Recent messages (awaits IMAP4) * Faster fetching of headers (awaits IMAP4) * Determination of which flags are permanent (awaits IMAP4) -------------- --==========-- From owner-pine-info@cac.washington.edu Fri Oct 7 15:09:49 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18670; Fri, 7 Oct 94 15:09:49 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19383; Fri, 7 Oct 94 15:02:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19377; Fri, 7 Oct 94 15:02:52 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtN2t-00000AC; Fri, 7 Oct 94 14:41 PDT To: pine-info@cac.washington.edu From: fredf@aps.org (Fred Firestine) Subject: Pine 3.90: Hostname included incorrecty when replying Date: 7 Oct 1994 14:46:24 -0500 Message-Id: Hi, First of all, let me say I am impressed with the enhancements made coming from the previous version. My only problem is this: I have been trying to make sense of the "user-domain" and "use-only-domain-name" fields. When someone at host A (using Pine 3.90) receives a message from someone at host B (using mailx), with *no domain name* in the From: field, and then the person at host A tries to reply, Pine 3.90 generates the following address: user@A.domain.name In short, it seems we can't get rid of the default use of our hostname in replies to folks who are in our domain, but on another host. Is there a configuration variable or compile option I am missing here? Thanks for your help. Because I have no direct Usenet access, I would appreciate a direct reply. Fred Firestine From owner-pine-info@cac.washington.edu Fri Oct 7 15:48:12 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20422; Fri, 7 Oct 94 15:48:12 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26008; Fri, 7 Oct 94 15:43:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26002; Fri, 7 Oct 94 15:43:07 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtNiC-000008C; Fri, 7 Oct 94 15:24 PDT To: pine-info@cac.washington.edu From: Roman Czyborra Subject: Re: Headers of Simultaneous Mail & News Date: Fri, 07 Oct 1994 21:32:50 +0100 Message-Id: References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> <3713p0$5j7@gaia.ucs.orst.edu> <371vcr$9rq@news.halcyon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > >The fact that brain damaged newsreaders leave them in when > >composing mailed replies is not reason to change the current > >definitions of mail. > Do you really think that TRN, TIN, and NN are brain damaged? In TRN it is only the default $MAILHEADER format which can be changed real easy. So chalk trn up with pine and xrn and the brain damage prevalence drops to 50 %. > It seems clear that if there is going to be a standard header that means > that a mail message was simultaneously mailed and posted it will have > to be something other than the Newsgroups: header. What do people think > of Posted-To:? Unlike Newsgroups Posted-To has the disadvantage that most of the currently existing integrated mail and news readers would ignore it. I also find it more beautiful for the same information to have the same name in news and mail. After all, you do not have to rename From, Subject, Date & Co. either when gating between mail and news. From owner-pine-info@cac.washington.edu Fri Oct 7 16:24:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22934; Fri, 7 Oct 94 16:24:10 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21164; Fri, 7 Oct 94 16:18:00 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21155; Fri, 7 Oct 94 16:17:57 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtOFs-000008C; Fri, 7 Oct 94 15:59 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 7 Oct 1994 16:29:51 -0500 Message-Id: <374ekf$8dc@mp.cs.niu.edu> References: <36voi9$rmq@mp.cs.niu.edu> In sdm7g@virginia.edu ("Steven D. Majewski") writes: >Pine is clearly doing (more or less) the "Right Thing" here. >Once a message has been moved - from either INBOX (mail) or >from the news spool or nntp-server into another folder, all >a mail/news-reader has to go on is what's in the header. The saved messages are separated by a "From " line. News articles have no "From " line. Therefore Pine must create that line. It could easily create it in a special format which Pine recognizes as indicating a news article. From owner-pine-info@cac.washington.edu Fri Oct 7 18:09:06 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27533; Fri, 7 Oct 94 18:09:06 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29324; Fri, 7 Oct 94 18:03:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29318; Fri, 7 Oct 94 18:03:14 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtPsd-00000DC; Fri, 7 Oct 94 17:43 PDT To: pine-info@cac.washington.edu From: edwin@cs.ruu.nl (Edwin Kremer) Subject: Re: covert from elm to pine Message-Id: References: Date: Fri, 7 Oct 1994 22:17:25 GMT In helal@cse.uta.edu (Abdelsalam Helal) writes: | Hello there! Could anybody please give me a pointer of a program that | could translate from elm's alias file to pine's addressbook. I quickly punched a Perl program to do exactly this to please the users at our site. It is not polished, not documented, but it worked for me and I haven't heard any complaints from the users. It's small, so I just appened it below. 'elm2pine' in a shar file. If it helps you, use it, change it, just don't sell it :-) Good luck. --[ Edwin ]-- -- Edwin H. Kremer, systems- and network administrator. Dept. of Computer Science, Utrecht University, The Netherlands [WHOIS: ehk3] ----------------------- http://www.cs.ruu.nl/~edwin --------------------------- #!/bin/sh # This is a shell archive (shar 3.32) # made 10/07/1994 22:12 UTC by edwin@cs.ruu.nl # # existing files WILL be overwritten # # This shar contains: # length mode name # ------ ---------- ------------------------------------------ # 3564 -rwxr-xr-x elm2pine # if touch 2>&1 | fgrep 'amc' > /dev/null then TOUCH=touch else TOUCH=true fi # ============= elm2pine ============== echo "x - extracting elm2pine (Text)" sed 's/^X//' << 'SHAR_EOF' > elm2pine && X#!/net/bin/perl X#--------------------------------------------------------------------------- X# elm2pine - convert Elm-2.4 aliases file to Pine 3.90 format X# (writes result to standard-output) X# X# 1.0 EHK 02-Sep-94 from scratch X# 1.1 EHK 03-Sep-94 fix continuation-line parsing bug, resulting in X# duplicate partial distribution-lists. Actually, I X# got the documentation wrong at first glance, so this X# is more of a major rewrite than just a bug fix... X#--------------------------------------------------------------------------- X X$P = 'elm2pine' ; X X$home = $ENV{'HOME'} || die "Can't find your HOME directory: $!" ; X$elm = "$home/.elm/aliases.text" ; X Xopen(ELM, "< $elm") || die "You don't have Elm aliases in your ~/.elm directory: $!" ; X X#--------------------------------------------------------------------------- X# Pass 1 : read the entire alias file in core; do some minimal processing X#--------------------------------------------------------------------------- Xprint STDERR "$P: Pass 1 -- reading aliases '$elm'...\n" ; Xwhile ( ) { X chop ; X next if ( /^$/ || /^#/ ) ; # skip comment and blank lines X X # delete blanks around the Elm aliases field-seperator '=' X # and around the Elm-specials ',' and ';' X s/\s*([=,;])\s*/\1/g ; X X # if we have leading blanks, this must be a continuation line X if ( /^[\t\s]/ ) { X # which we can only have if we've seen a nickname already X if ( ! defined($nickname) ) { X print STDERR "$P: ERROR: continuation line without prefix ignored: '$_' \n" ; X next ; X } X X s/^\s+// ; # get rid of the leading blanks X $alias{$nickname} .= "$_" ; X $clines++ ; X } X else { X if ( $clines ) { X print STDERR "$P: [OK] $clines continuation-line(s) joined.\n" ; X $clines = 0 ; X } X undef($nickname); X ($nickname, $fullname, $address) = split(/=/) ; X $fullname = "*none-given*" if ( $fullname eq '' ) ; X X # Elm has multiple-nicknames, so we have to duplicated X # them for Pine to maintain the same information X @nnames = split(/,/, $nickname) ; X if ( $#nnames > 0 ) { X $multi_aliases = $#nnames + 1 ; X print STDERR "$P: [OK] $multi_aliases multiple-aliases duplicated.\n" ; X } X foreach $nname ( @nnames ) { X $alias{$nname} = "$fullname#$address" ; X } X } X} Xclose(ELM) ; X X#--------------------------------------------------------------------------- X# Pass 2 : convert to Pine format. Add default Fcc-field, optional comment X# and apply Pine semantics to Elm-special chars ';' and ',' X#--------------------------------------------------------------------------- Xprint STDERR "$P: Pass 2 -- converting Elm aliases to Pine format...\n" ; X$aliasc = 0 ; Xforeach $nickname (sort keys(%alias)) { X $_ = $alias{$nickname} ; X $aliasc++ ; X X ( $fullname, $addrlist ) = split(/\#/) ; X X # anything after a ',' in the fullname is optional comment X if ( $fullname =~ /,/ ) { X $fullname =~ s/(.*),(.*)/\1/ ; X $comment = "$2" ; X } X else { X $comment = '' ; X } X X # a ';' in the fullname for Elm, must be a ',' for Pine X $fullname =~ s/;/, / ; X X # distribution-list aliases need brackets X $addrlist = "(" . "$addrlist" . ")" if ( $addrlist =~ /,/ ) ; X X # output as Pine aliases now: X # TABTAB
TABTAB X # [Aaaaaaaaaarrrrggggggggggggghhhhhh.... why the !&^@#$^$% `TAB' :--( X X $, = "\t" ; X print $nickname, $fullname, $addrlist ; X X # if we have a comment-field, we will put in a Fcc-field as well X print "\t$nickname\t$comment" if ($comment ne '') ; X print "\n" ; X} X Xprint STDERR "$P: [OK] successfully converted $aliasc aliases.\n" ; X Xexit 0 ; X X__END__ SHAR_EOF $TOUCH -am 0903221994 elm2pine && chmod 0755 elm2pine || echo "restore of elm2pine failed" set `wc -c elm2pine`;Wc_c=$1 if test "$Wc_c" != "3564"; then echo original size 3564, current size $Wc_c fi exit 0 From owner-pine-info@cac.washington.edu Fri Oct 7 18:57:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29114; Fri, 7 Oct 94 18:57:10 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24140; Fri, 7 Oct 94 18:52:02 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24134; Fri, 7 Oct 94 18:52:01 -0700 Received: by shiva2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19964; Fri, 7 Oct 94 18:52:00 -0700 Date: Fri, 7 Oct 1994 18:51:55 -0700 (PDT) From: Terry Gray To: pine-info@cac.washington.edu Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) In-Reply-To: <374ekf$8dc@mp.cs.niu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 7 Oct 1994, Neil Rickert wrote: > > >"Steven D. Majewski" writes: > >Pine is clearly doing (more or less) the "Right Thing" here. > >Once a message has been moved - from either INBOX (mail) or > >from the news spool or nntp-server into another folder, all > >a mail/news-reader has to go on is what's in the header. > > The saved messages are separated by a "From " line. Depends on the folder format. The "From " separator line of course is not part of the message. > News articles have no "From " line. They may, in the same sense that mail messages do. All of the newsreaders I use (rn, trn, etc) save in mbox format and have "From " separator lines. You obviously prefer a different configuration. > Therefore Pine must create that line. The tool that stored the message created that line. This may or may not have been Pine. > It could easily create it in a > special format which Pine recognizes as indicating a news article. Sorry, but there is no dependable context for making any such assumption, especially when the same message might really have been both mailed and posted. Pine gets whatever it is given, and that may be a message in any of a dozen different mailbox formats, created by any one of many different tools. As was said previously: you have only the message headers to go on. But let's talk about *assumptions*. A lot of this thread contains strong criticism of Pine that is based on *assumptions* (not facts) about whether Pine is making unwarranted *assumptions* about what to do with messages containing a newsgroups header. In fact, Pine does not assume anything in this situation. It asks the user what they want to do. More than once. Here's exactly what happens when I Reply to a message that contains a Newsgroups header: 1. Pine prompts me with: "Post follow-up message to news group(s)? " (the default is NO) 2. If I say Yes, then it clearly shows all the newsgroups in the composer. 3. If I then ^X to send, Pine makes sure that the headers are visible on the screen so I can re-check where the msg is going, then it asks for confirmation... If I confirm, and there is a Newsgroups header, I then get an ADDITIONAL prompt: 4. "Posted message may go to thousands of readers. Really post?" (the default is NO) Given that it is impossible to correctly *assume* the correct action in such situations, what would you have Pine do differently? -teg From owner-pine-info@cac.washington.edu Fri Oct 7 20:10:14 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00767; Fri, 7 Oct 94 20:10:14 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25024; Fri, 7 Oct 94 20:03:40 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25018; Fri, 7 Oct 94 20:03:38 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtRmz-00000DC; Fri, 7 Oct 94 19:45 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: New user requires help. Date: Fri, 7 Oct 1994 12:52:08 -0700 Message-Id: References: <1994Oct5.210722.13290@Princeton.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <1994Oct5.210722.13290@Princeton.EDU> .pine-debug files are normal. The last one is .pine-debug1 and the oldest is .pine-debug4. They do come in handy when trying to track down certain problems, so we keep them on by default.... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 5 Oct 1994, Adam Cox wrote: > Date: Wed, 5 OCT 1994 21:07:22 GMT > From: Adam Cox > Newgroups: comp.mail.pine > Subject: Re: New user requires help. > > In article , Keith Cordon wrote: > >I have only just discovered PINE so please bear with me. > >Can someone please email me with information on how to stop the creation > >of enourmous .pine-debug files everytime I use pine. > >Also is there a FAQ for pine users? I've managed to get to grips with > >most of it but I have a few questions.... > >Many Thanks > > i get the same pine-debug files. four of them build up and then they stop > (i don't know f they are rewriting to those four or not - haven't > checked). anyone know what the cause of it is? > > adam > > - i could post one of the files to be examined... > > > > From owner-pine-info@cac.washington.edu Fri Oct 7 20:10:20 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00769; Fri, 7 Oct 94 20:10:20 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01189; Fri, 7 Oct 94 20:03:36 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01183; Fri, 7 Oct 94 20:03:34 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtRmy-00000AC; Fri, 7 Oct 94 19:45 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Bug in pine 3.90? Date: Fri, 7 Oct 1994 12:44:22 -0700 Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: Check for a read-message-folder in the user's .pinerc and delete it if present... |\ | |\/| 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, JE-20 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 7 Oct 1994, Jim Hribnak wrote: > Date: Fri, 7 OCT 1994 17:28:30 GMT > From: Jim Hribnak > Newgroups: comp.mail.pine > Subject: Bug in pine 3.90? > > > One user on our system (so far) is getting the following: > > Bug in Pine detected: "Recieved abort signal" > > > He gets this when quitting pine every time and produces a core.pine file > (I am on BSDI/386 v1.1) > > I use pine constantly all day long and I have never encountered this.. > > > Jim Hribnak Nucleus Information Service > VP Operations, Nucleus Inc. 55 Lines (403)531-9353 (2400) > ----------------------------------------- (403)531-9370 (19200) > hribnak@nucleus.com (403)249-9009 (voice) > > > > > > From owner-pine-info@cac.washington.edu Fri Oct 7 20:28:57 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01111; Fri, 7 Oct 94 20:28:57 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01451; Fri, 7 Oct 94 20:23:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01443; Fri, 7 Oct 94 20:23:34 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtS4a-000008C; Fri, 7 Oct 94 20:03 PDT To: pine-info@cac.washington.edu From: David L Miller Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: Fri, 7 Oct 1994 16:27:19 -0700 Message-Id: References: <36voi9$rmq@mp.cs.niu.edu> <374ekf$8dc@mp.cs.niu.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <374ekf$8dc@mp.cs.niu.edu> On 7 Oct 1994, Neil Rickert wrote: > Date: 7 OCT 1994 16:29:51 -0500 > From: Neil Rickert > Newgroups: comp.mail.pine > Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) > > In sdm7g@virginia.edu ("Steven D. Majewski") writes: > > >Pine is clearly doing (more or less) the "Right Thing" here. > > >Once a message has been moved - from either INBOX (mail) or > >from the news spool or nntp-server into another folder, all > >a mail/news-reader has to go on is what's in the header. > > The saved messages are separated by a "From " line. News articles > have no "From " line. Therefore Pine must create that line. It > could easily create it in a special format which Pine recognizes as > indicating a news article. > That is only in one mailbox format, and besides, what if it is saved from TRN? It doesn't know this magic incantation... From owner-pine-info@cac.washington.edu Fri Oct 7 21:24:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01990; Fri, 7 Oct 94 21:24:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25890; Fri, 7 Oct 94 21:18:44 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25884; Fri, 7 Oct 94 21:18:42 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtSvh-00000DC; Fri, 7 Oct 94 20:58 PDT To: pine-info@cac.washington.edu From: Terry Gray Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: Fri, 7 Oct 1994 20:50:00 -0700 Message-Id: References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> <3713p0$5j7@gaia.ucs.orst.edu> <374std$htv@crl8.crl.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <374std$htv@crl8.crl.com> On 7 Oct 1994, Neil Rickert wrote: > > >"Steven D. Majewski" writes: > >Pine is clearly doing (more or less) the "Right Thing" here. > >Once a message has been moved - from either INBOX (mail) or > >from the news spool or nntp-server into another folder, all > >a mail/news-reader has to go on is what's in the header. > > The saved messages are separated by a "From " line. Depends on the folder format. The "From " separator line of course is not part of the message. > News articles have no "From " line. They may, in the same sense that mail messages do. All of the newsreaders I use (rn, trn, etc) save in mbox format and have "From " separator lines. You obviously prefer a different configuration. > Therefore Pine must create that line. The tool that stored the message created that line. This may or may not have been Pine. > It could easily create it in a > special format which Pine recognizes as indicating a news article. Sorry, but there is no dependable context for making any such assumption, especially when the same message might really have been both mailed and posted. Pine gets whatever it is given, and that may be a message in any of a dozen different mailbox formats, created by any one of many different tools. As was said previously: you have only the message headers to go on. But let's talk about *assumptions*. A lot of this thread contains strong criticism of Pine that is based on *assumptions* (not facts) about whether Pine is making unwarranted *assumptions* about what to do with messages containing a newsgroups header. In fact, Pine does not assume anything in this situation. It asks the user what they want to do. More than once. Here's exactly what happens when I Reply to a message that contains a Newsgroups header: 1. Pine prompts me with: "Post follow-up message to news group(s)? " (the default is NO) 2. If I say Yes, then it clearly shows all the newsgroups in the composer. 3. If I then ^X to send, Pine makes sure that the headers are visible on the screen so I can re-check where the msg is going, then it asks for confirmation... If I confirm, and there is a Newsgroups header, I then get an ADDITIONAL prompt: 4. "Posted message may go to thousands of readers. Really post?" (the default is NO) Given that it is impossible to correctly *assume* the correct action in such situations, what would you have Pine do differently? -teg From owner-pine-info@cac.washington.edu Fri Oct 7 22:16:49 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03003; Fri, 7 Oct 94 22:16:49 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26510; Fri, 7 Oct 94 22:09:39 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26504; Fri, 7 Oct 94 22:09:37 -0700 Received: by shiva2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA22912; Fri, 7 Oct 94 22:09:27 -0700 Date: Fri, 7 Oct 1994 22:09:26 -0700 (PDT) From: Terry Gray To: Fred Firestine Cc: pine-info@cac.washington.edu Subject: Re: Pine 3.90: Hostname included incorrecty when replying In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Fred, There are some rough edges in this area in 3.90. In 3.91, if "user-domain" is set, it will be used to complete "local" or unqualified names. -teg On 7 Oct 1994, Fred Firestine wrote: > Hi, > > First of all, let me say I am impressed with the enhancements made coming > from the previous version. My only problem is this: I have been trying to > make sense of the "user-domain" and "use-only-domain-name" fields. When > someone at host A (using Pine 3.90) receives a message from someone at > host B (using mailx), with *no domain name* in the From: field, and then > the person at host A tries to reply, Pine 3.90 generates the following > address: > > user@A.domain.name > > In short, it seems we can't get rid of the default use of our hostname in > replies to folks who are in our domain, but on another host. Is there a > configuration variable or compile option I am missing here? > > Thanks for your help. Because I have no direct Usenet access, I would > appreciate a direct reply. > > Fred Firestine > > From owner-pine-info@cac.washington.edu Fri Oct 7 22:16:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03014; Fri, 7 Oct 94 22:16:54 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02796; Fri, 7 Oct 94 22:10:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02790; Fri, 7 Oct 94 22:10:05 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtThh-00000JC; Fri, 7 Oct 94 21:48 PDT To: pine-info@cac.washington.edu From: davison@borland.com (Wayne Davison) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Message-Id: References: <36ut98$mh4@news.halcyon.com> <371pgv$730@news.halcyon.com> Date: Sat, 8 Oct 1994 04:05:30 GMT According to Nancy McGough : > Because of the X-Response-To-Message-In: header I know that he is > responding to a message that was crossposted to soc.history.science > and sci.philosophy.tech so I can go take a look at both these newsgroups > to read the discussion. In my mind this is the existing function of the Newsgroups header in a mailed newsarticle (where was the discussion occurring that prompted this message), thus your Newsgroups header could have been set to the two newsgroups, the X-Response-To-Message-In header eliminated, and the X-Posted-To (or Also-Posted-To would be nice) providing the information that it is ok to reply via mail and newsgroup. -- Wayne Davison davison@borland.com From owner-pine-info@cac.washington.edu Fri Oct 7 22:50:42 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03657; Fri, 7 Oct 94 22:50:42 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26936; Fri, 7 Oct 94 22:45:20 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26930; Fri, 7 Oct 94 22:45:18 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtUGW-00000DC; Fri, 7 Oct 94 22:24 PDT To: pine-info@cac.washington.edu From: st93kbtb@dunx1.ocs.drexel.edu (Jatzen Boke) Subject: Porting Pine/Pico Date: 8 Oct 1994 01:06:41 -0400 Message-Id: <3759d1$n8p@dunx1.ocs.drexel.edu> Does anyone out there have or know of a ported version of either pine or pico for a pyramid computer. The computer is running BSD 4.3 but pine will not compile under the system(at least not so it will run). I can rewrite the code as a last resort, but it's been a long time since I've programmed in unix for machine incompatibilites. Any help would be appreciated. -John D. Riley jatzen@hellfire.dusers.drexel.edu st93kbtb@dunx1.ocs.drexel.edu From owner-pine-info@cac.washington.edu Fri Oct 7 23:16:22 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04169; Fri, 7 Oct 94 23:16:22 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03517; Fri, 7 Oct 94 23:11:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03511; Fri, 7 Oct 94 23:11:43 -0700 Received: by shiva1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07021; Fri, 7 Oct 94 23:11:41 -0700 Date: Fri, 7 Oct 1994 23:11:41 -0700 (PDT) From: Steve Hubert To: Tim McDowell Cc: pine-info@cac.washington.edu Subject: Re: Need help with Pine-Eudora interaction!! In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You can open the INBOX readonly with "pine -o". Steve Hubert Networks and Distributed Computing, Univ. of Washington, Seattle On 7 Oct 1994, Tim McDowell wrote: > Hi: > My boss reads his mail using Pine, and leaves it in the in box. Later Iam expected to come into the same account using Eudora and bring the mail up unto my laptop for printing. The trouble is it appears that Eudora picks up on > the fact that the mail was marked read by Pine, and does not download it to my > laptop. QUESTION: Is there a way to configure Pine so that it does not mark > messages as read so that when I come in to the mail under Eudora I get all the > mail downloaded to me. I'd greatly appreciate a response to my email at > mcdowelt@rintintin.colorado.edu. > > Tim > From owner-pine-info@cac.washington.edu Fri Oct 7 23:48:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04692; Fri, 7 Oct 94 23:48:59 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03873; Fri, 7 Oct 94 23:44:22 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03867; Fri, 7 Oct 94 23:44:19 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtVCq-00000DC; Fri, 7 Oct 94 23:24 PDT To: pine-info@cac.washington.edu From: davidh@crl.com (David Herron) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Message-Id: <374std$htv@crl8.crl.com> Date: 8 Oct 94 01:33:33 GMT References: <36t8ok$n8h@mp.cs.niu.edu> <36vi69$3aa@news.halcyon.com> <3713p0$5j7@gaia.ucs.orst.edu> Oh yeah .. a couple details: In PathWay Access/Mail (not technically the right name for the product) when "replying" to a message the action taken varied depending on which folder you were in. i.e. whether it was a News message or Mail message. News: Ask whether to post followup or send mail. If sending mail whether to reply to everybody or just sender. Ask whether/how to include text in reply. Mail: Ask whether to reply to everybody or just sender. Ask whether/how to include text in reply. David From owner-pine-info@cac.washington.edu Sat Oct 8 07:20:56 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14150; Sat, 8 Oct 94 07:20:56 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03260; Sat, 8 Oct 94 07:15:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03254; Sat, 8 Oct 94 07:15:06 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtcDx-00000BC; Sat, 8 Oct 94 06:54 PDT To: pine-info@cac.washington.edu From: yehavi@vms.huji.ac.il (Yehavi Bourvine (58-4279)) Subject: RE: Pine 3.90 on VMS Message-Id: <1994Oct8.095656.184@vms.huji.ac.il> Date: 8 Oct 94 09:56:56 GMT References: <0098588C.34CB0A49.3@vax.ox.ac.uk> >> > Pine 3.90 doesn't want to compile on VAX/VMS with the VAX C compiler - when I >> > tried today I got lots of warnings of the form >> > >> > %CC-W-EXTERNNAMELONG, The external identifier name exceeds 31 characters > ... > 1. This 'feature' was not in the beta-test versions of VMS Pine > > 2. I thought that the whole point of porting software is to make it work in the > target environment. A 'port' which won't compile is not much use to anyone. Once again: This is a warnning and not a fatal error, so simply ignore it. Instead of modifying all PINE sources and make them totally incompatible with the original release I've decided to live with the warnnings. __Yehavi: From owner-pine-info@cac.washington.edu Sat Oct 8 09:34:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16484; Sat, 8 Oct 94 09:34:15 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04894; Sat, 8 Oct 94 09:30:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04888; Sat, 8 Oct 94 09:30:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qteMW-00000JC; Sat, 8 Oct 94 09:11 PDT To: pine-info@cac.washington.edu From: Don Fnordlioni Subject: Super Newbie question. (newsreading) Date: Wed, 5 Oct 1994 19:16:03 -0500 (CDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yep, I'm a real newbie, and this is a real newbie question. I can't, for the life of me, find where the 'mark as read' command is, re: reading usenet news. I'd hate to have to delete everything, in case I did end up wanting to backtrack. Any suggestions? (e-mail preferred, as I don't keep up on this newsgroup.) Thanks, Tod From owner-pine-info@cac.washington.edu Sat Oct 8 09:34:24 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA16505; Sat, 8 Oct 94 09:34:24 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11231; Sat, 8 Oct 94 09:30:41 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11225; Sat, 8 Oct 94 09:30:39 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qteMf-00000LC; Sat, 8 Oct 94 09:11 PDT To: pine-info@cac.washington.edu From: siberia@usis.com (Kimberly Long) Subject: Re: Can't use paste in Windows with Pine: why? Date: 6 Oct 1994 03:36:53 GMT Message-Id: <36vrcl$hr6@news.usis.com> References: Howard Altschuler (altschh@iia.org) wrote: : > On 27 Sep 1994, Howard Altschuler wrote: : > : > > I use pine 3.90. When I try to paste text from a windows app to pine (via : > > crosstalk), it takes about a minute per line! : > [snip] I am having the same problem. I use crosstalk as well. I made the mistake of trying to paste a two page article into email. It took about 40 minutes. If you get an answer to this question please share. :) Namaste' Kimberly Long siberia@usis.com From owner-pine-info@cac.washington.edu Sat Oct 8 10:16:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17224; Sat, 8 Oct 94 10:16:40 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11572; Sat, 8 Oct 94 10:01:45 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA11566; Sat, 8 Oct 94 10:01:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtenu-00000BC; Sat, 8 Oct 94 09:39 PDT To: pine-info@cac.washington.edu From: Chris Newman Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: Sat, 8 Oct 1994 12:10:04 -0400 Message-Id: <781632604.29505.0@nifty.andrew.cmu.edu> References: <36ut98$mh4@news.halcyon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: davison@borland.com (Wayne Davison) writes: > According to Nancy McGough : > > Because of the X-Response-To-Message-In: header I know that he is > > responding to a message that was crossposted to soc.history.science > > and sci.philosophy.tech so I can go take a look at both these newsgroups > > to read the discussion. > > In my mind this is the existing function of the Newsgroups header in > a mailed newsarticle (where was the discussion occurring that prompted > this message) Please point to a formal specification which defines "Newsgroups" with such a meaning. The only specification I know of defines the "Newsgroups" header as a list of newsgroups to which the message was posted. Any other use of that header is a violation of that spec and is misleading in situations where news & mail can't be distinguished. Besides, it's obviously bad practice to have the same header have two different meanings. - Chris Newman Carnegie Mellon University Computing Services From owner-pine-info@cac.washington.edu Sat Oct 8 10:49:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA17869; Sat, 8 Oct 94 10:49:50 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05834; Sat, 8 Oct 94 10:45:37 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA05828; Sat, 8 Oct 94 10:45:33 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtfXZ-00000BC; Sat, 8 Oct 94 10:26 PDT To: pine-info@cac.washington.edu From: Michael Seibel Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: Fri, 7 Oct 1994 22:27:56 -0700 Message-Id: References: <3700se$2p3@mp.cs.niu.edu> <3713u8$phs@news.halcyon.com> <371eau$h4l@mp.cs.niu.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <371eau$h4l@mp.cs.niu.edu> Neil, Thanks for the thoughtful clarification; you bring up some valid points. Specific comments such as these go a long way toward making Pine a better product. I'll not try to duplicate other's comments from this thread, but to provide some word from the Pine Team on the underlying motivation for what you found. It's unfortunate that your initial Pine experience was in an environment Pine was not specifically designed to fit. We don't actively develop under SunOS or Solaris, but when work is done, it's based on the native compilers. Our goal is, of course, to keep the scripts, makefiles, and code as portable and general as possible, but, as always, there is room for improvement. We will do our best, as time permits, to remedy this situation. What Pine *is* designed to be is as equally non-threatening to *both* the neophyte user and the neophyte system administrator. With the latter in mind, it is deemed more useful to group configuration data requiring local modification, both OS-dependent and not, in a single location rather than require an unfamiliar sys-admin to scan several files before becoming confident (OK, semi-confident) that Pine will behave in a desired way. We hold that the sophisticated sys-admin in a heterogenous environment already has the tools to deal with this case. Of course, it's clear we've not completely tackled the single-config challenge, as there are pieces of the Pine puzzle that were initially and continue to be developed independent of Pine. Likewise, with this goal in mind, it isn't clear to us that the problems self-configuring tools can introduce offset their usefulness in our situation. Thus, this avenue was also not taken. Furthermore, we feel ease of configuration should extend to installation as well. That's why Pine on Unix is obese. The fewer auxiliary files an unfamiliar sys-admin is required to position in just the right place the better. This is key during both the initial installation and subsequent upgrades. Another reason is that we distribute pre-compiled copies of each release. A single binary is much simpler to fetch and install than a tar'd package of several files to, in turn, get deposited throughout the system. As for your other points, I'll concede that, for a seasoned, knowledgeable user, some of Pine's behavior may seem less than efficient. However, very few user interface decisions are considered outside the context of the fundamentals we see as requisite of a tool intended for the novice user. In short, this means fewer commands, more prompts, more verbose feedback, and more menus than you might see in a tool targeted at users interested in or familiar with the computing-end of electronic communication. I'm not saying Pine's completely achieved it's ease of use goals. There are certainly some rough edges due to poor decisions early in development, underlying technological limits and such, but we're always trying to improve. That said, thank's again for your comments, and if you have any other specific concerns, please feel free to make them known to the Pine Team . And now back to preparing for 3.91... (due RSN) Michael Seibel Networks and Distributed Computing University of Washington, Seattle From owner-pine-info@cac.washington.edu Sat Oct 8 11:13:04 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18249; Sat, 8 Oct 94 11:13:04 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12352; Sat, 8 Oct 94 11:08:08 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA12346; Sat, 8 Oct 94 11:08:06 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtfpi-00000IC; Sat, 8 Oct 94 10:45 PDT To: pine-info@cac.washington.edu From: fuzzy@fuzzy.dialup.access.net (Fuzzy) Subject: can PINE 3.89 block incoming mail.. Date: 8 Oct 1994 17:19:17 GMT Message-Id: <376kal$kh7@news.panix.com> is there a way to block (killfile) email from a specific "userid@machine.domain.name" ? thanks in advance ... Your Friend, _____ __ __ ____ ____ __ __ / ___// // //__ )/__ )\ \/ / / __/ / // / / /__ / /__\ / (_/ (____/ <____/<____//_/ Email: fuzzy@fuzzy.dialup.access.net (non-anon) an72289@anon.penet.fi (true anon) wi.687@wizvax.com (true anon) anon-2986@twwells.com (true anon) ================================================================= -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.1 mQCNAi4RAFMAAAEEANX2Ag3Tpif6YQMcB380Fb4azUfD6Me+eLYen62KT+IOPRby Sv8znFUT6UDNV7/YYVa8WpnGaDh2mry5UmoqvNkWZ1ngcl2x6wbOvJnunohDpEG8 gqxZ7mGP6G+ejRyT/kULNV96G9q/zlcJMCJD9La6KRlwo/U6s4TbvzdMEt9NAAUR tCVGdXp6eSA8ZnV6enlAZnV6enkuZGlhbHVwLmFjY2Vzcy5uZXQ+ =W71C ----END PGP PUBLIC KEY BLOCK----- From owner-pine-info@cac.washington.edu Sat Oct 8 12:03:23 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19283; Sat, 8 Oct 94 12:03:23 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06809; Sat, 8 Oct 94 11:59:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06803; Sat, 8 Oct 94 11:59:36 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtgbE-00000BC; Sat, 8 Oct 94 11:34 PDT To: pine-info@cac.washington.edu From: stanley@skyking.oce.orst.edu (John Stanley) Subject: Re: Headers of Simultaneous Mail & News Date: 8 Oct 1994 18:30:16 GMT Message-Id: <781625255.AA12345@oce.orst.edu> References: <3713p0$5j7@gaia.ucs.orst.edu> <371vcr$9rq@news.halcyon.com> In article , Roman Czyborra wrote: >Unlike Newsgroups Posted-To has the disadvantage that most of the >currently existing integrated mail and news readers would ignore it. This is an advantage. It will prevent some "helpful" intermediate mailer from redirecting a message someplace it wasn't wanted. Using current systems, it is quite common for "Newsgroups:" to appear in a header of something intended for mail only. It would be a violation of ethics for a "helpful" intermediate mailer to take the existance of that header as meaning "post this to the newsgroups listed." >I also find it more beautiful for the same information to have the >same name in news and mail. It doesn't mean the same thing, it should be named differently. >After all, you do not have to rename >From, Subject, Date & Co. either when gating between mail and news. Those mean the same thing. From owner-pine-info@cac.washington.edu Sat Oct 8 14:07:12 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21565; Sat, 8 Oct 94 14:07:12 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14408; Sat, 8 Oct 94 14:03:35 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14402; Sat, 8 Oct 94 14:03:33 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qticI-00000iC; Sat, 8 Oct 94 13:43 PDT To: pine-info@cac.washington.edu From: rickert@cs.niu.edu (Neil Rickert) Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: 8 Oct 1994 15:33:23 -0500 Message-Id: <376vmj$12a@mp.cs.niu.edu> References: <36ut98$mh4@news.halcyon.com> <371pgv$730@news.halcyon.com> <781632604.29505.0@nifty.andrew.cmu.edu> In <781632604.29505.0@nifty.andrew.cmu.edu> Chris Newman writes: > davison@borland.com (Wayne Davison) writes: >> In my mind this is the existing function of the Newsgroups header in >> a mailed newsarticle (where was the discussion occurring that prompted >> this message) >Please point to a formal specification which defines "Newsgroups" with >such a meaning. The only specification I know of defines the >"Newsgroups" header as a list of newsgroups to which the message was >posted. Any other use of that header is a violation of that spec and >is misleading in situations where news & mail can't be distinguished. That is plain wrong. The "Newsgroups:" header is defined for news in RFC1036. The use of "Newsgroups" in email is not a violation of RFC1036. It cannot be a violation of RFC1036, since that document does not apply to mail. The definition of headers for mail is given in RFC882. The use of "Newsgroups:" in an email message, for any reason at all, does not contradict or violate anything in RFC882. It has become common practice to use "Newsgroups:" as an email header in replies to news articles. If we were to disallow the development of common practice and insist that no technological innovation occur until after the RFC has been approved, we would probably still be back in the dark ages. >Besides, it's obviously bad practice to have the same header have two >different meanings. As commonly used, the "Newsgroups:" header has only one context-sensitive meaning. That meaning is: when used for usenet postings, it lists the groups to which the message is posted; when used in email, it lists the usenet groups in which the discussion originated. From owner-pine-info@cac.washington.edu Sat Oct 8 15:49:43 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23554; Sat, 8 Oct 94 15:49:43 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09602; Sat, 8 Oct 94 15:40:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from uvaarpa.Virginia.EDU by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA09596; Sat, 8 Oct 94 15:40:48 -0700 Received: from elvis.med.virginia.edu by uvaarpa.virginia.edu id aa01183; 8 Oct 94 18:40 EDT Received: by elvis.med.Virginia.EDU (5.65c/1.34) id AA13182; Sat, 8 Oct 1994 18:40:45 -0400 Date: Sat, 8 Oct 1994 18:40:44 -0400 (EDT) From: "Steven D. Majewski" X-Sender: sdm7g@elvis.med.Virginia.EDU To: Neil Rickert Cc: pine-info@cac.washington.edu Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) In-Reply-To: <374ekf$8dc@mp.cs.niu.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 7 Oct 1994, Neil Rickert wrote: > In sdm7g@virginia.edu ("Steven D. Majewski") writes: > > >Pine is clearly doing (more or less) the "Right Thing" here. > > >Once a message has been moved - from either INBOX (mail) or > >from the news spool or nntp-server into another folder, all > >a mail/news-reader has to go on is what's in the header. > > The saved messages are separated by a "From " line. News articles > have no "From " line. Therefore Pine must create that line. It > could easily create it in a special format which Pine recognizes as > indicating a news article. > Not (always) true. ( All my messages from [t]rn and tin are saved in mbox format. ) -- Steve Majewski (804-982-0831) -- -- UVA Department of Molecular Physiology and Biological Physics -- -- Box 449 Health Science Center Charlottesville,VA 22908 -- [ "Cheese is more macho?" ] From owner-pine-info@cac.washington.edu Sat Oct 8 16:59:29 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24859; Sat, 8 Oct 94 16:59:29 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10491; Sat, 8 Oct 94 16:52:50 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from [198.209.19.1] by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA10479; Sat, 8 Oct 94 16:52:46 -0700 Received: by library.sbuniv.edu (5.65/DEC-Ultrix/4.3) id AA01551; Sat, 8 Oct 1994 18:53:11 -0500 Date: Sat, 8 Oct 1994 18:53:11 -0500 (CDT) From: Rick Nebel To: pine-info@cac.washington.edu Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) In-Reply-To: <3739o4$jmp@vodka.wlo.dec.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII My $.02. I for one agree with Chris. Of course if Mr. Rickert can write a better mail package and provide on-going enhancements and support free of charge I'm sure that everyone would be happy to move over to it. Rick Nebel On 7 Oct 1994, Chris Hedley wrote: > On 6 Oct 1994 13:06:22 -0500, Neil Rickert (rickert@cs.niu.edu) wrote: > > 1: It is a bitch to install. > > No more so than any other public domain software. In my experience, Pine > was one of the easier packages to install that wasn't developed specifically > for my type of system. Having to redefine the compiler type does not > seem to me to be a major effort, especially bearing in mind some of the > far more serious problems I have encountered with other packages; doing > some minor tweaking to the makefiles is no big thing when you > consider the amount of work that has gone into a program of this scale > which is then freely distributed! > > > 2: It is excessively obese. > > Not a problem on demand-paged systems such as Unix and VMS, which are > the most common platforms for Pine. Your claim that the help information > must be loaded into memory whenever the software is used is incorrect. > > > 3: It screws up message status of the default mailbox. > > > It always opens my default mailbox, whether I want it to > > or not. The status of messages in that mailbox changes > > from New to Unread, even though I have not asked to > > read the mailbox, and have not seen the list of messages > > in that mailbox. > > I haven't noticed it trying to open the default mailbox if I specify an > alternative on the command line. As for changing the status of new messages > to unread, every mailer I have used does this (correctly in my opinion). > > > 4: The menu interface is tedious and unintuitive. > > 5: Poorly timed user unfriendly prompts. > > These are your opinions. Whilst you are entitled to them, please > don't use them as reasons to substantiate your claim that the software > is "junk". My opinion (which is independant, I have no connection with > the Pine development team) is that Pine 3.90 is by far the best character- > cell based mailing system available for Unix platforms that I have used, > combining a large number of powerful features with an easy to use and > pleasant user interface. And it's free. > Cheers, > > Chris. > From owner-pine-info@cac.washington.edu Sat Oct 8 23:06:47 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01838; Sat, 8 Oct 94 23:06:47 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15034; Sat, 8 Oct 94 23:02:19 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15025; Sat, 8 Oct 94 23:02:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qtr1X-00000BC; Sat, 8 Oct 94 22:42 PDT To: pine-info@cac.washington.edu From: rrkarun@umanitoba.ca (Ken Arundell) Subject: Newbie re: Pine Inbox Date: 9 Oct 1994 05:24:58 GMT Message-Id: <377ura$8p5@canopus.cc.umanitoba.ca> I'm using Pine on a PC with Chameleon and having problems establishing INBOX. I have set it for {mail.cc.umanitoba.ca}inbox as per what appears to be the directions supplied. However, every time I load Pine, I get a message like this: "Can't connect to mira.cc.umanitoba.ca,143: Refused (10061)" I have tried all kinds of variations of the {computer.name} without success, and would appreciate suggestions/help/etc. -- Ken Arundell (rrkarun@umanitoba.ca) Red River Community College Portage la Prairie, MB Portage Regional Centre Canada From owner-pine-info@cac.washington.edu Sun Oct 9 09:30:17 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA13397; Sun, 9 Oct 94 09:30:17 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28124; Sun, 9 Oct 94 09:16:10 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from edison.eng.auburn.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28118; Sun, 9 Oct 94 09:16:08 -0700 Received: from netman.eng.auburn.edu (netman.eng.auburn.edu [131.204.12.24]) by edison.eng.auburn.edu (8.6.9/8.6.4) with ESMTP id LAA15513 for ; Sun, 9 Oct 1994 11:16:07 -0500 From: Doug Hughes Received: from localhost (doug@localhost) by netman.eng.auburn.edu (8.6.4/8.6.4) id LAA15345 for pine-info@cac.washington.edu; Sun, 9 Oct 1994 11:16:06 -0500 Date: Sun, 9 Oct 1994 11:16:06 -0500 Message-Id: <199410091616.LAA15345@netman.eng.auburn.edu> To: pine-info@cac.washington.edu Subject: bug in pine: "Append Validity Error" - PC-NFS 5.0 Content-Length: 798 I'm having the above message with PC-NFS5.0 when trying to compose a message. It happens always when trying to write the FCC. I've fooled around with the FCC options, and have figured out a way to send mail, although it's a real hack.. You have to change the FCC in setup from default to by-user.. and then when you compose, when the fcc field pops-up after you enter the To: field, delete everything in the FCC field.. then the message will send.. Also, if there is already a sentmail folder (file).. pine will say sentmail folder does not exist, create it? And if you answer yes it will say, "sentmail already exists, permission denied". Seems kind of funny to contradict itself like that.. Any clues? Doug Hughes Engineering Network Services doug@eng.auburn.edu Auburn University From owner-pine-info@cac.washington.edu Sun Oct 9 10:29:24 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14277; Sun, 9 Oct 94 10:29:24 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28858; Sun, 9 Oct 94 10:23:54 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA28852; Sun, 9 Oct 94 10:23:51 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu1iH-000008C; Sun, 9 Oct 94 10:07 PDT To: pine-info@cac.washington.edu From: Christophe Babilotte Subject: Looking for a mail program Date: Sun, 9 Oct 1994 12:25:04 -0400 (EDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi!! Is there any program that I could retrive from the net and that will do the following: for example say I am on vacation and I would like to send an e-mail back saying that I am on Vacation to incoming mail. so if you know where I can get it you can just reply to my message. thanks!!!! ------------------------------------------------------------------------------ Christophe Babilotte . . ==================== | | cbabil@zeus.towson.edu | _ | cbabil@charm.net ______________|_( )_|______________ s72ucba@toe.towson o +|+ [ ( o ) ] +|+ o http://www.charm.net/~cbabil/ *[_]---[_]* ------------------------------------------------------------------------------ From owner-pine-info@cac.washington.edu Sun Oct 9 10:59:45 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14872; Sun, 9 Oct 94 10:59:45 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29253; Sun, 9 Oct 94 10:54:01 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29247; Sun, 9 Oct 94 10:53:59 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu27h-00000DC; Sun, 9 Oct 94 10:33 PDT To: pine-info@cac.washington.edu From: taishing@access.ods.gulfnet.kw (NOBODY!) Subject: Compiling Pine: libcrypt.a = ouch Date: 9 Oct 1994 17:24:06 GMT Message-Id: <3798vm$577@gulfa.ods.gulfnet.kw> Greetings, I'm trying to compile pine3.90, the platform is an SCO V/386 3.2. Every thing runs fine, pico is nicely built, the problem is in pine. When using gcc first, many errors occured in a file/function called memmove2.c, with cc only a warning is shown and it runs till it reaches "mtest.c" which requiers an encryption library (~/crypt/libcrypt.a). unfortunately removing the " -lcrypt " from the makefiles does not solve the problem, which is: This library is not available. Even in most sites which hold GNU releases, the file "gclib-crypt.tar.gz" does not hold that library. If anybody knows an equivilent or any way to get over this problem, help is really needed. Thank You & Best Regards. Abdalla. -- __________________________________________________________ | taishing@access.ods.gulfnet.kw | | q8@netcom.com | | lzx@universe.digex.net | | Go for the longest! | |_________________________________________________________| From owner-pine-info@cac.washington.edu Sun Oct 9 11:01:19 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA14933; Sun, 9 Oct 94 11:01:19 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23264; Sun, 9 Oct 94 10:53:57 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23258; Sun, 9 Oct 94 10:53:55 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu27D-000008C; Sun, 9 Oct 94 10:32 PDT To: pine-info@cac.washington.edu From: rainbow@news.acns.nwu.edu (Hiroe Tsuru) Subject: Using addressbook from earlier versions in Pine 3.90 Date: 9 Oct 1994 17:28:26 GMT Message-Id: <37997q$lht@news.acns.nwu.edu> From owner-pine-info@cac.washington.edu Sun Oct 9 11:50:55 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA15884; Sun, 9 Oct 94 11:50:55 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23772; Sun, 9 Oct 94 11:39:04 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from edison.eng.auburn.edu by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA23764; Sun, 9 Oct 94 11:38:57 -0700 Received: from xtester (xtester.eng.auburn.edu [131.204.12.130]) by edison.eng.auburn.edu (8.6.9/8.6.4) with SMTP id NAA17261; Sun, 9 Oct 1994 13:38:52 -0500 Date: Sun, 9 Oct 1994 12:35:58 -0500 (CDT) From: Doug Hughes To: pine-info@cac.washington.edu Cc: pine-bugs@cac.washington.edu Subject: winsock pine composing problems X-Sender: doug@mailhost.eng.auburn.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII After composing a message and pressing ctrl-X and pressing Y to confirm delivery, pine hangs.. no response.. This is winsock version of pine using the PCNFS5.0 winsock. Here is pinedebg.txt: (All features have default values) Debug output of the Pine program (at debug level 2). Version 3.90 Sun Oct 09 12:22:04 1994 reading_pinerc "C:\pine\pinerc" Read 6136 characters: ========== Current_val options set ========== user-domain : eng.auburn.edu smtp-server : mailhost inbox-path : {mailhost}INBOX folder-collections : c:\mail\[] default-fcc : sentmail postponed-folder : postpond mail-directory : mail signature-file : pine.sig address-book : addrbook feature-list : signature-at-bottom saved-msg-name-rule : by-sender fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last use-only-domain-name : no printer : attached-to-ansi standard-printer : lpr last-time-prune-ques : 94.10 last-version-used : 3.90 bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no newsrc-path : C:\pine\NEWSRC folder-extension : MTX normal-foreground-co : black normal-background-co : white reverse-foreground-c : cyan reverse-background-c : blue ========== Command_line_val options set ========== ========== User_val (pinerc) options set ========== personal-name : Doug Hughes user-id : doug user-domain : eng.auburn.edu smtp-server : mailhost inbox-path : {mailhost}INBOX folder-collections : c:\mail\[] feature-list : signature-at-bottom saved-msg-name-rule : by-sender fcc-name-rule : default-fcc last-time-prune-ques : 94.10 last-version-used : 3.90 normal-foreground-co : black normal-background-co : white reverse-foreground-c : cyan reverse-background-c : blue ========== Fixed_val (pine.conf.fixed, overrides all) options set ========== Userid: doug Fullname: "Doug Hughes" User domain name being used "eng.auburn.edu" Local Domain name being used "eng.auburn.edu" Host name being used "xtester.eng.auburn.edu" Mail Domain name being used "eng.auburn.edu" MAILCAP: file: "C:\pine\\MAILCAP" MAILCAP: Cannot read file C:\pine\\MAILCAP MAILCAP: file: "C:\WINPINE\\MAILCAP" MAILCAP: Cannot read file C:\WINPINE\\MAILCAP Context c:\mail\[] type: LOCAL About to open folder "INBOX" inbox: "INBOX" IMAP mm_notify NIL : {mailhost}INBOX : edison IMAP2bis Service 7.8(88) at Sun, 9 Oct 1994 13:25:02 -0500 (CDT) Opened folder "{mailhost.eng.auburn.edu}INBOX" with 22 messages Sorting by Arrival IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd ---- MAIN_MENU_SCREEN ---- Want_to read: c (99) ---- COMPOSE SCREEN (not in pico yet) ---- IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: c:\mail\postpond Want_to read: y (121) IMAP 12:22 10/9 mm_log babble: Mailbox is empty ---- MAIN_MENU_SCREEN ---- ---- COMPOSE SCREEN (not in pico yet) ---- IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd IMA From owner-pine-info@cac.washington.edu Sun Oct 9 14:08:47 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18247; Sun, 9 Oct 94 14:08:47 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25395; Sun, 9 Oct 94 14:04:18 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25389; Sun, 9 Oct 94 14:04:15 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu56U-000008C; Sun, 9 Oct 94 13:44 PDT To: pine-info@cac.washington.edu From: Brad Subject: Suggestion re: news Date: Sun, 9 Oct 1994 21:35:20 +0100 (BST) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, Instead of 'No more news groups. Return to "inbox"?' when one has tabbed through all news groups, how about 'No more news groups. Return to "inbox" or start again?' I find that as soon as I've finished reading all the news in my subscribed groups, then there is usually new news to be read, and I would like to be able to go back to the first group in the list and go through them all again if I want to, otherwise go back to "inbox". (I usually read news starting at the first subscribed group, reading or deleting everything here, and then moving onto the next.) --Simon. From owner-pine-info@cac.washington.edu Sun Oct 9 14:27:34 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA18543; Sun, 9 Oct 94 14:27:34 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01704; Sun, 9 Oct 94 14:20:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01698; Sun, 9 Oct 94 14:20:48 -0700 Received: from tomobiki-cho.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27570; Sun, 9 Oct 94 14:20:44 -0700 Date: Sun, 9 Oct 1994 14:20:43 -0700 (PDT) From: Mark Crispin To: Doug Hughes Cc: pine-info@cac.washington.edu, pine-bugs@cac.washington.edu Subject: Re: winsock pine composing problems In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Doug - There is bad news, mediocre news, and good news. The bad news is that this is a known bug in Winsock Pine 3.90. It occurs if your timezone is set to anything other than PST8PDT (the Microsoft default and also where we are located). As I heard it described, it was sampling the current time at two different points and calculating a delta, but one of those samples was in Pacific time instead of local time. This caused the delta to be a matter of hours rather than seconds, and that delta in turn was used as part of a calculation for a wait time. Oops. This problem is specific to Winsock. PC Pine does not have this problem, nor does Unix Pine. Apparently, you have to be really careful where your tzset() calls are on Winsock applications. The mediocre news is that you can work around this problem by leaving your timezone unset or set to PST8PDT. Welcome to the west coast! ;-) The good news is that this bug is fixed in Pine 3.91, which should be coming out imminently. -- Mark -- On Sun, 9 Oct 1994, Doug Hughes wrote: > > After composing a message and pressing ctrl-X and pressing Y to > confirm delivery, pine hangs.. no response.. > This is winsock version of pine using the PCNFS5.0 winsock. > > Here is pinedebg.txt: (All features have default values) > > Debug output of the Pine program (at debug level 2). Version 3.90 > Sun Oct 09 12:22:04 1994 > > reading_pinerc "C:\pine\pinerc" > Read 6136 characters: > ========== Current_val options set ========== > user-domain : eng.auburn.edu > smtp-server : mailhost > inbox-path : {mailhost}INBOX > folder-collections : c:\mail\[] > default-fcc : sentmail > postponed-folder : postpond > mail-directory : mail > signature-file : pine.sig > address-book : addrbook > feature-list : signature-at-bottom > saved-msg-name-rule : by-sender > fcc-name-rule : default-fcc > sort-key : arrival > addrbook-sort-rule : fullname-with-lists-last > use-only-domain-name : no > printer : attached-to-ansi > standard-printer : lpr > last-time-prune-ques : 94.10 > last-version-used : 3.90 > bugs-fullname : Pine Developers > bugs-address : pine-bugs@cac.washington.edu > elm-style-save : no > header-in-reply : no > feature-level : sapling > old-style-reply : no > save-by-sender : no > newsrc-path : C:\pine\NEWSRC > folder-extension : MTX > normal-foreground-co : black > normal-background-co : white > reverse-foreground-c : cyan > reverse-background-c : blue > ========== Command_line_val options set ========== > ========== User_val (pinerc) options set ========== > personal-name : Doug Hughes > user-id : doug > user-domain : eng.auburn.edu > smtp-server : mailhost > inbox-path : {mailhost}INBOX > folder-collections : c:\mail\[] > feature-list : signature-at-bottom > saved-msg-name-rule : by-sender > fcc-name-rule : default-fcc > last-time-prune-ques : 94.10 > last-version-used : 3.90 > normal-foreground-co : black > normal-background-co : white > reverse-foreground-c : cyan > reverse-background-c : blue > ========== Fixed_val (pine.conf.fixed, overrides all) options set ========== > Userid: doug > Fullname: "Doug Hughes" > User domain name being used "eng.auburn.edu" > Local Domain name being used "eng.auburn.edu" > Host name being used "xtester.eng.auburn.edu" > Mail Domain name being used "eng.auburn.edu" > MAILCAP: file: "C:\pine\\MAILCAP" > MAILCAP: Cannot read file C:\pine\\MAILCAP > MAILCAP: file: "C:\WINPINE\\MAILCAP" > MAILCAP: Cannot read file C:\WINPINE\\MAILCAP > Context c:\mail\[] type: LOCAL > About to open folder "INBOX" inbox: "INBOX" > IMAP mm_notify NIL : {mailhost}INBOX : edison IMAP2bis Service 7.8(88) at Sun, 9 Oct 1994 13:25:02 -0500 (CDT) > Opened folder "{mailhost.eng.auburn.edu}INBOX" with 22 messages > Sorting by Arrival > IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd > > > ---- MAIN_MENU_SCREEN ---- > Want_to read: c (99) > > > ---- COMPOSE SCREEN (not in pico yet) ---- > IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd > IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: c:\mail\postpond > Want_to read: y (121) > IMAP 12:22 10/9 mm_log babble: Mailbox is empty > > > ---- MAIN_MENU_SCREEN ---- > > > ---- COMPOSE SCREEN (not in pico yet) ---- > IMAP 12:22 10/9 mm_log babble: Find of mailbox outside context: C:\intruptd > IMA > > From owner-pine-info@cac.washington.edu Sun Oct 9 15:04:22 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19166; Sun, 9 Oct 94 15:04:22 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02169; Sun, 9 Oct 94 15:00:49 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA02163; Sun, 9 Oct 94 15:00:47 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu5yB-00000DC; Sun, 9 Oct 94 14:39 PDT To: pine-info@cac.washington.edu From: errol@io.org (Errol Porter) Subject: Problem with Pine Compose Date: 9 Oct 1994 16:39:24 -0400 Message-Id: <379kds$el1@ionews.io.org> When going into "Compose" a message keeps appearing as follows: "continue interrupted composition (answering 'n' won't erase it)"? However there is no interupted composition. Does anyone know how to get rid of this message? Thanks if you can help. -- Errol Porter HORIZON BOOKS, rare & out-of-print | Voyages, travel & exploration errol@io.org 416 226-4282 | Natural history From owner-pine-info@cac.washington.edu Sun Oct 9 15:51:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA19981; Sun, 9 Oct 94 15:51:15 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26545; Sun, 9 Oct 94 15:45:47 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26539; Sun, 9 Oct 94 15:45:45 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu6gB-00000MC; Sun, 9 Oct 94 15:25 PDT To: pine-info@cac.washington.edu From: Alex Batson Subject: Quick question here.. Date: Sun, 9 Oct 1994 18:18:35 -0400 (EDT) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, all.. I know this is a stupid question, so a quick stupid answer will be appreciated. I'm fresh into using Pine now for newsgroups, I used to use tin.. Tin always used to tell me how many 'responses' there were on the string of the original poster. I cant' redily tell in pine.. I see certain post subjects are listed by themselves, such as 'subject X' and others will say 'Re: SUbject X', are all the 'Re: ' subjects actually responses to the first subject w/o the 'Re: ' looking backawards time-wise? Do you understand my question?? I barely do , what I would like to know, is how I can tell how many 'responses' there are to a certain post, and how to view those replies.. thanks..! --Alex From owner-pine-info@cac.washington.edu Sun Oct 9 16:35:51 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20786; Sun, 9 Oct 94 16:35:51 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03241; Sun, 9 Oct 94 16:30:53 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03235; Sun, 9 Oct 94 16:30:51 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu7Og-000008C; Sun, 9 Oct 94 16:11 PDT To: pine-info@cac.washington.edu From: Urs Kradolfer Subject: [Q] search pattern WITHIN mail Date: Sun, 9 Oct 1994 23:20:10 +0100 (MEZ) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello everybody, the command W searches for a string in the mail-header (if in the index-menu). Question: Is there a command to search for a string WITHIN the body of all mails? 'elm' has the slash (/) as 'pine' has the W command. I did not find anything in 'pine' as the command slash-slash (//) in 'elm', searching for a string anywhere in a mail. Can anybody help me? Best regards, Urs From owner-pine-info@cac.washington.edu Sun Oct 9 16:40:43 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA20911; Sun, 9 Oct 94 16:40:43 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27077; Sun, 9 Oct 94 16:34:38 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27071; Sun, 9 Oct 94 16:34:36 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu7Up-00000IC; Sun, 9 Oct 94 16:17 PDT To: pine-info@cac.washington.edu From: Dave Rindos Subject: Re: Suggestion re: news Date: Mon, 10 Oct 1994 06:55:02 +0800 (WST) Message-Id: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: Assuming I have not missed something in the documentation (and if I have, I would appreciate knowing it!), my little suggestions would be: 1) Reduce the number of keystrokes to Delete All in a group. I think a lot of us scan groups for interesting subjects and read just them. Especially with the recent growth in number of postings, this would be an *exceedingly* desirable amendment. An easy way to implement would be to add a toggle ";" to the Select sub-screen -- hence ; ; would be Select All-Deleted. 2) Implement a Kill/Select file. Probably emulating the kinds of options permitted on (for example) nn would be fine. 3) Permit a default Sort option such that one does not have to choose $ repeatedly. 4) Add a Line-Count to the titles. Again, this is helpful in scanning. Dave, who did NOT think he would like the pine reader, but who has been pleasantly surprised. -- Dave Rindos arkeo4@uniwa.uwa.edu.au 20 Herdsmans Parade Wembley WA 6014 AUSTRALIA Ph:+61 9 387 6281 (GMT+8) FAX:+61 9 386 2760 (USEST+13) [you may also reach me on rindos@perth.dialix.oz.au] >I'm in need of something clever or cute to put here< From owner-pine-info@cac.washington.edu Sun Oct 9 17:23:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA21863; Sun, 9 Oct 94 17:23:54 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA04004; Sun, 9 Oct 94 17:19:42 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA03998; Sun, 9 Oct 94 17:19:40 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0qu8C3-00000DC; Sun, 9 Oct 94 17:02 PDT To: pine-info@cac.washington.edu From: pfaffman@pilot.njin.net (Jay Pfaffman) Subject: Funny characters at top of pico screen Date: 9 Oct 1994 19:48:24 -0400 Message-Id: <379vg8$b8k@pilot.njin.net> I'm using the linux pico binary from ftp.cac.washington.edu & get a "a" with a umlaut (two dots) over it in the first line of the buffer. I experienced a similar problem with an earlier version that i compiled myself. Any ideas? It doesn't seem to be a wrong terminal type & the extra character doesn't appear in the saved file. -- Jay Pfaffman pfaffman@itc.org 802-453-2457 From owner-pine-info@cac.washington.edu Sun Oct 9 20:10:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA24547; Sun, 9 Oct 94 20:10:28 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29449; Sun, 9 Oct 94 19:55:09 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA29443; Sun, 9 Oct 94 19:55:07 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0quAZI-00000LC; Sun, 9 Oct 94 19:34 PDT To: pine-info@cac.washington.edu From: adambcox@tucson.princeton.edu (Adam Cox) Subject: Re: New user requires help. Message-Id: <1994Oct9.193052.4359@Princeton.EDU> References: <1994Oct5.210722.13290@Princeton.EDU> Date: Sun, 9 Oct 1994 19:30:52 GMT In article , David L Miller wrote: > >.pine-debug files are normal. The last one is .pine-debug1 and the oldest is >.pine-debug4. They do come in handy when trying to track down certain >problems, so we keep them on by default.... > this is one of my pine-debug files (sorry that it is so long). it looks like the problem occurs in the first few lines of this file. does anyone know why this would be happening? i checked /usr/local/lib and there are no pine files in it. are there supposed to be? adam Debug output of the Pine program (at debug level 2). Version 3.90 Sun Oct 9 13:12:15 1994 reading_pinerc "/usr/local/lib/pine.conf" Open failed: No such file or directory reading_pinerc "/u/adambcox/.pinerc" Read 9027 characters: reading_pinerc "/usr/local/lib/pine.conf.fixed" Open failed: No such file or directory ========== Current_val options set ========== inbox-path : inbox folder-collections : mail/[] : News/news/[] : mail/sent/[] : News/[] default-fcc : sent/sent-misc postponed-folder : postponed-msgs mail-directory : mail signature-file : .signature address-book : .addressbook feature-list : enable-aggregate-command-set : enable-tab-completion : expanded-view-of-folders : quit-without-confirm : enable-suspend saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : Date addrbook-sort-rule : fullname-with-lists-last use-only-domain-name : no printer : enscript -2rhG personal-print-comma : enscript -2rhG standard-printer : lpr last-time-prune-ques : 94.10 last-version-used : 3.90 bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ========== Command_line_val options set ========== ========== User_val (pinerc) options set ========== personal-name : Adam B. Cox folder-collections : mail/[] : News/news/[] : mail/sent/[] : News/[] default-fcc : sent/sent-misc feature-list : enable-aggregate-command-set : enable-tab-completion : expanded-view-of-folders : quit-without-confirm : enable-suspend saved-msg-name-rule : default-folder sort-key : Date/Reverse printer : enscript -2rhG personal-print-comma : enscript -2rhG last-time-prune-ques : 94.10 last-version-used : 3.90 ========== Global_val (pine.conf) options set ========== inbox-path : inbox default-fcc : sent-mail postponed-folder : postponed-msgs mail-directory : mail signature-file : .signature address-book : .addressbook saved-msg-name-rule : default-folder fcc-name-rule : default-fcc sort-key : arrival addrbook-sort-rule : fullname-with-lists-last use-only-domain-name : no printer : attached-to-ansi standard-printer : lpr bugs-fullname : Pine Developers bugs-address : pine-bugs@cac.washington.edu elm-style-save : no header-in-reply : no feature-level : sapling old-style-reply : no save-by-sender : no ========== Fixed_val (pine.conf.fixed, overrides all) options set ========== ========== Feature settings ========== no-assume-slow-link no-auto-move-read-msgs no-auto-open-next-unread no-compose-sets-newsgroup-without-confirm no-delete-skips-deleted no-disable-config-cmd no-disable-keyboard-lock-cmd no-disable-password-cmd no-disable-update-cmd enable-aggregate-command-set no-enable-alternate-editor-cmd no-enable-alternate-editor-implicitly no-enable-bounce-cmd no-enable-flag-cmd no-enable-full-header-cmd no-enable-incoming-folders no-enable-jump-shortcut no-enable-mail-check-cue enable-suspend enable-tab-completion no-enable-unix-pipe-cmd no-expanded-view-of-addressbooks expanded-view-of-folders no-expunge-without-confirm no-include-attachments-in-reply no-include-header-in-reply no-include-text-in-reply no-news-post-without-validation no-news-read-in-newsrc-order quit-without-confirm no-save-will-quote-leading-froms no-save-will-not-delete no-save-will-advance no-select-without-confirm no-show-selected-in-boldface no-signature-at-bottom no-use-current-dir no-use-function-keys no-user-lookup-even-if-domain-mismatch Userid: adambcox Fullname: "Adam B. Cox" User domain name being used "" Local Domain name being used "princeton.edu" Host name being used "tucson.princeton.edu" Mail Domain name being used "tucson.princeton.edu" MAILCAP: file: "/u/adambcox/.mailcap" MAILCAP: Cannot read file /u/adambcox/.mailcap MAILCAP: file: "/etc/mailcap" MAILCAP: Cannot read file /etc/mailcap new win size -----<42 80>------ Terminal type: xterm Context mail/[] type: LOCAL Context News/news/[] type: LOCAL Context mail/sent/[] type: LOCAL Context News/[] type: LOCAL About to open folder "INBOX" inbox: "INBOX" Opened folder "/usr/spool/mail/adambcox" with 14 messages Sorting by Date/reverse IMAP 13:12 10/9 mm_log babble: Find of mailbox outside context: /u/adambcox/.pine-interrupted-mail ---- MAIL INDEX ---- ---- INDEX MANAGER ---- ----- MAIL VIEW ----- ---- MAIL INDEX ---- ---- INDEX MANAGER ---- ----- MAIL VIEW ----- ---- MAIL INDEX ---- ---- INDEX MANAGER ---- ----- MAIL VIEW ----- ---- MAIL INDEX ---- ---- INDEX MANAGER ---- ----- MAIL VIEW ----- ---- MAIL INDEX ---- ---- INDEX MANAGER ---- ----- MAIL VIEW ----- ---- MAIL INDEX ---- ---- INDEX MANAGER ---- MAIL_CMD: quit ---- QUIT SCREEN ---- expunge and close mail stream "/usr/spool/mail/adambcox" about to end_tty_driver From owner-pine-info@cac.washington.edu Sun Oct 9 20:42:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA25175; Sun, 9 Oct 94 20:42:00 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06293; Sun, 9 Oct 94 20:31:30 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA06287; Sun, 9 Oct 94 20:31:28 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0quB8u-000008C; Sun, 9 Oct 94 20:11 PDT To: pine-info@cac.washington.edu From: lachlan@dmp.csiro.au (Lachlan Cranswick) Subject: Re: "junk software and poor design" (was: WARNING FOR PINE 3.90 USERS!!!!!) Message-Id: <1994Oct9.025434.9551@dmp.csiro.au> References: <3700se$2p3@mp.cs.niu.edu> <3713u8$phs@news.halcyon.com> Date: Sun, 9 Oct 1994 02:54:34 GMT Nancy McGough writes: >rickert@cs.niu.edu (Neil Rickert) writes: >>I install Pine because some of >>my users ask for it. Except for testing the installation, I do not >>use Pine. I consider it to be one of the biggest pieces of junk >>software and poor design that I have encountered. >I'm curious why you think this. Could you please post at least 3 features >(other than the Newsgroups:_ header in a mail message) which you think were >poorly designed and mailers that do each of these 3 features better. While I still use elm for much of my email (matter of habit) - I was very impressed with pine when I first came accross it as our users obtained a user-friendly yet powerful email program free. And it was for our users that pine was installed. That must be saying something about pine when users actually ask for it? While there are now rivals to pine (can anyone name a previous/present UNIX rival to pine?) examples of really good design are :- --- The user-friendly and very powerful address book - including creating lists. --- For the UNIX version - printing to a local PC or MAC printer. --- Prompting and explanations of what the user is about to do and error tolerant. --- For UNIX - very easy and painless to compile - even on a 99% SUN compatable Solbourne computer. --- Availability of UNIX executables to save the hassle of compiling. --- Simple to use default editor. --- For UNIX - stand alone binaries for simple installation. --- Easy mailing and extracting of binary files. --- For UNIX version - Nice file find and selecting procedure. --- Easy access in latest version of pine for "power?" users. ------------------ The main part that confuses new users is :- I FOLDER INDEX - View messages in current folder L FOLDER LIST - Select a folder to view but this is relatively easy to show how to use. ------------------- While we use the latest version of pine for UNIX - we are unsure about the MS-Windows version. Mainly because we would like it to be transparently usable from any PC or telnet session for a user. Because of the requirement that the .sig and .address book have to be located locally - this isn't easy for WinPine. The easiest way to presently make it transparent for users irrespective of what PC/MAC or terminal they are using is to log into the email server via a telnet session and run pine. - -- Lachlan Cranswick - CSIRO _--_|\ lachlan@dmp.CSIRO.AU Division of Mineral Products / \ tel +61 3 647 0367 PO Box 124, Port Melbourne \_.--._/ fax +61 3 646 3223 3207 AUSTRALIA v From owner-pine-info@cac.washington.edu Sun Oct 9 21:33:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26250; Sun, 9 Oct 94 21:33:37 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00602; Sun, 9 Oct 94 21:20:25 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA00596; Sun, 9 Oct 94 21:20:22 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0quBvD-000008C; Sun, 9 Oct 94 21:01 PDT To: pine-info@cac.washington.edu From: Mark Crispin Subject: Re: Headers of Simultaneous Mail & News (was: WARNING FOR PINE 3.90 USERS!!!!!) Date: Sun, 9 Oct 1994 20:48:24 -0700 Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <374ekf$8dc@mp.cs.niu.edu> On 7 Oct 1994, Neil Rickert wrote: > The saved messages are separated by a "From " line. News articles > have no "From " line. Therefore Pine must create that line. It > could easily create it in a special format which Pine recognizes as > indicating a news article. Uh, there are no ``From '' lines separating the messages in my mailbox. You must be thinking about a mailbox format that is used on some other system. From owner-pine-info@cac.washington.edu Sun Oct 9 22:11:39 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA26937; Sun, 9 Oct 94 22:11:39 -0700 Received: by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07520; Sun, 9 Oct 94 22:05:33 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx2.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA07514; Sun, 9 Oct 94 22:05:31 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0quCbr-00000MC; Sun, 9 Oct 94 21:45 PDT To: pine-info@cac.washington.edu From: cort@sphinx.cs.nmt.edu (Cort) Subject: Improper handling of a wyse and wyse50? Date: 10 Oct 1994 03:53:28 GMT Message-Id: <37adro$h5o@chaos.aoc.nrao.edu> I've had trouble getting pine to use a wyse and wyse50 terminal properly. I've looked through the technical notes and documentation and haven't found any references to this problem. I'm having the problem on suns running sunos 4.1.3 (haven't tried our other architectures yet) with a wyse and wyse50. Anyone have any ideas on what might be causing this? Possibly a problem in the sunos termcap? From owner-pine-info@cac.washington.edu Sun Oct 9 22:21:55 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA27101; Sun, 9 Oct 94 22:21:55 -0700 Received: by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01315; Sun, 9 Oct 94 22:16:46 -0700 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rain.psg.com by mx1.cac.washington.edu (5.65+UW94.9/UW-NDC Revision: 2.30 ) id AA01309; Sun, 9 Oct 94 22:16:43 -0700 Received: by rain.psg.com (Smail3.1.28.1 #7) id m0quClI-00000NC; Sun, 9 Oct 94 21:55 PDT To: pine-info@cac.washington.edu From: adambcox@tucson.princeton.edu (Adam Cox) Subject: saved-message rules Message-Id: <1994Oct9.234213.10665@Princeton.EDU> Date: Sun, 9 Oct 1994 23