From owner-pine-info@cac.washington.edu Tue Feb 1 01:47:27 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA23215; Tue, 1 Feb 94 01:47:27 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21413; Tue, 1 Feb 94 01:32:07 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from suma2.rdg.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21407; Tue, 1 Feb 94 01:32:04 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP (PP) id <04213-0@mail.reading.ac.uk>; Tue, 1 Feb 1994 09:31:58 +0000 Date: Tue, 1 Feb 1994 09:34:28 GMT From: John Stumbles Subject: enhancement request To: Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I wrote yesterday that I find myself using ^arrow keys in pico... I also find myself using PgUp to try to get to the top of the index screen, but Pine tells me that I am already on the first page. I think PageUp should take you to the top of the page in this case. Again this is fairly standard for DOS applications. Oh and similarly for Page Down of course! John Stumbles j.d.stumbles@reading.ac.uk Reading University 0734 318435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Tue Feb 1 03:38:11 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA24836; Tue, 1 Feb 94 03:38:11 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22137; Tue, 1 Feb 94 03:22:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dir.bris.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22131; Tue, 1 Feb 94 03:22:11 -0800 Received: from adm1.bristol.ac.uk by dir.bris.ac.uk with SMTP (PP) id <22975-0@dir.bris.ac.uk>; Tue, 1 Feb 1994 11:21:55 +0000 Date: Tue, 1 Feb 1994 11:22:31 +0000 (GMT) From: Dave King Subject: Pine / PTX futures. To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We use Pine 3.89 on DYNIX/ptx 2.0.4 with no problems. Sequent recently told me that ptx version 4 will be released sometime in Q1/Q2 of this year. I'm aware that ptx is a mjor Pine platform, and that Pine runs on ptx at UW, but ... Could someone please advise if Pine will be ported to ptx version 4 when it is released? Thanks, Dave ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) From owner-pine-info@cac.washington.edu Tue Feb 1 06:24:12 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26596; Tue, 1 Feb 94 06:24:12 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23311; Tue, 1 Feb 94 06:03:10 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23305; Tue, 1 Feb 94 06:02:44 -0800 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <00566-0@susssys1.reading.ac.uk>; Tue, 1 Feb 1994 14:02:31 +0000 Date: Tue, 1 Feb 1994 14:05:03 GMT From: John Stumbles Subject: PC Pine under Windows To: Pine User Group , Pine Mission Control X-Sender: suqstmbl@suma1.rdg.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII If I leave PC Pine (3.89) running under MS Windows, when I return to it after a while I get the message [IMAP connection broken in reply]. Is this a bug? I'm not sure what's happening - the 'in reply' bit of the error messsage is a bit confusing (in reply to what?). John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Tue Feb 1 06:59:15 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26896; Tue, 1 Feb 94 06:59:15 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29360; Tue, 1 Feb 94 06:34:00 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29354; Tue, 1 Feb 94 06:33:59 -0800 Received: from perca.umd.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09103; Tue, 1 Feb 94 06:33:57 -0800 Received: by perca.umd.edu (4.1/SMI-4.1) id AA23768; Tue, 1 Feb 94 09:31:28 EST From: jon@perca.umd.edu (Jonathan Kruger) Message-Id: <9402011431.AA23768@perca.umd.edu> Subject: Problems compiling 3.89 on Ultrix 4.3 w/secure passwords To: pine-info@cac.washington.edu Date: Tue, 1 Feb 1994 09:31:27 -0500 (EST) Organization: Chesapeake Biological Laboratory X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2807 For 3.07 someone had to hack on it to get the secure passwords to work with IMAP, but it compiled fine. When I type "build ult" on our DECstation 5000 with ULTRIX 4.3, I get the following: --------------------------- make args are "CC=cc" Making c-client library and mtest rm -f osdep.h ln os_ult.h osdep.h cc -g3 -O2 -Olimit 800 -Dconst= -c mtest.c cpp: error /usr/include/netdb.h:67: Can't find include file sys/bitypes.h cpp: warning /usr/include/sys/cdefs.h:96: const redefined *** Error code 1 Stop. Making Imapd cd ../c-client;make cc -g3 -O2 -Olimit 800 -Dconst= -c mtest.c cpp: error /usr/include/netdb.h:67: Can't find include file sys/bitypes.h cpp: warning /usr/include/sys/cdefs.h:96: const redefined *** Error code 1 Stop. *** Error code 1 Stop. Making Pico rm -f osdep.c cp os_unix.c osdep.c rm -f osdep.h cp os_unix.h osdep.h cc -c -Dult -DJOB_CONTROL -g attach.c cc -c -Dult -DJOB_CONTROL -g ansi.c cc -c -Dult -DJOB_CONTROL -g basic.c cc -c -Dult -DJOB_CONTROL -g bind.c cc -c -Dult -DJOB_CONTROL -g browse.c cc -c -Dult -DJOB_CONTROL -g buffer.c cc -c -Dult -DJOB_CONTROL -g composer.c cc -c -Dult -DJOB_CONTROL -g display.c cc -c -Dult -DJOB_CONTROL -g file.c cc -c -Dult -DJOB_CONTROL -g fileio.c cc -c -Dult -DJOB_CONTROL -g line.c cc -c -Dult -DJOB_CONTROL -g osdep.c cc -c -Dult -DJOB_CONTROL -g pico.c cc -c -Dult -DJOB_CONTROL -g random.c cc -c -Dult -DJOB_CONTROL -g region.c cc -c -Dult -DJOB_CONTROL -g search.c cc -c -Dult -DJOB_CONTROL -g spell.c cc -c -Dult -DJOB_CONTROL -g tcap.c cc -c -Dult -DJOB_CONTROL -g window.c cc -c -Dult -DJOB_CONTROL -g word.c ar ru libpico.a attach.o ansi.o basic.o bind.o browse.o buffer.o composer.o display.o file.o fileio.o line.o osdep.o pico.o random.o region.o search.o spell.o tcap.o window.o word.o ar: Warning: creating libpico.a ranlib libpico.a cc -Dult -DJOB_CONTROL -g main.c libpico.a -ltermcap -lc -o pico Making Pine. rm -f os.h ln -s osdep/os-ult.h os.h ./cmplhlp2.sh < pine.hlp > helptext.h cc -DULT -g -DDEBUG -c addrbook.c cpp: error /usr/include/netdb.h:67: Can't find include file sys/bitypes.h cpp: warning ./headers.h:75: const redefined *** Error code 1 Stop. Links to executables are in bin directory: ldopen: cannot open bin/pine size: cannot open bin/pine ldopen: cannot open bin/mtest size: cannot open bin/mtest ldopen: cannot open bin/imapd size: cannot open bin/imapd text data bss dec hex 217088 36864 30432 284384 456e0 bin/pico Done -------------------------------------- So what's going on? Is ULTRIX 4.3 just plain not supported? ------------------------------------------------------------------------------- Jonathan Kruger - jon@cbl.umd.edu - Computer and Network Systems Coordinator UMCEES/CBL, PO Box 38, Solomons, MD 20688 Phone: 410-326-7306 Fax: 410-326-7361 From owner-pine-info@cac.washington.edu Tue Feb 1 08:39:25 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA29318; Tue, 1 Feb 94 08:39:25 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00277; Tue, 1 Feb 94 08:12:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA00271; Tue, 1 Feb 94 08:12:39 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA26311; Tue, 1 Feb 94 08:12:34 -0800 Date: Tue, 1 Feb 1994 08:05:35 -0800 (PST) From: Mark Crispin Subject: re: Problems compiling 3.89 on Ultrix 4.3 w/secure passwords To: Jonathan Kruger Cc: pine-info@cac.washington.edu In-Reply-To: <9402011431.AA23768@perca.umd.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII This sounds like a problem on your system; specifically, the system C include file /usr/include/netdb.h is attempting to include /usr/include/sys/bitypes.h but that file does not exist. The netdb.h on our ULTRIX system does not reference bitypes.h, and I have no idea what bitypes.h might be. I looked on some of our other systems, and I could not find bitypes.h there either. At this point, I am inclined to say that the problem is a faulty installation of the C compiler on your system. From owner-pine-info@cac.washington.edu Tue Feb 1 09:05:43 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA00812; Tue, 1 Feb 94 09:05:43 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24870; Tue, 1 Feb 94 08:40:53 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA24864; Tue, 1 Feb 94 08:40:48 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22029; Tue, 1 Feb 94 08:39:09 -0800 Date: Tue, 1 Feb 1994 08:39:08 -0800 (PST) From: David L Miller Subject: Re: enhancement request To: John Stumbles Cc: Pine User Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is on the to-do list for one of the next few releases. Thanks for the suggestion! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 1 Feb 1994, John Stumbles wrote: > I wrote yesterday that I find myself using ^arrow keys in pico... > > I also find myself using PgUp to try to get to the top of the index > screen, but Pine tells me that I am already on the first page. I think > PageUp should take you to the top of the page in this case. Again this is > fairly standard for DOS applications. > > Oh and similarly for Page Down of course! > > John Stumbles j.d.stumbles@reading.ac.uk > Reading University 0734 318435 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > From owner-pine-info@cac.washington.edu Tue Feb 1 09:47:41 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02375; Tue, 1 Feb 94 09:47:41 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25581; Tue, 1 Feb 94 09:13:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA25571; Tue, 1 Feb 94 09:13:42 -0800 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <07940-0@susssys1.reading.ac.uk>; Tue, 1 Feb 1994 17:13:17 +0000 Date: Tue, 1 Feb 1994 17:15:49 GMT From: John Stumbles Subject: Re: enhancement request To: David L Miller , Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 1 Feb 1994, David L Miller wrote: > On Tue, 1 Feb 1994, John Stumbles wrote: > > > I wrote yesterday that I find myself using ^arrow keys in pico... > > I also find myself using PgUp to try to get to the top of the index .. > > Oh and similarly for Page Down of course! > > This is on the to-do list for one of the next few releases. Thanks for > the suggestion! Thanks, David - I find Pico VERY useful as a stand-alone editor for installation scripts etc. One other feature I'd like to see is a write-to-file operation (reverse of ^R). It would be useful in Pine for folks to make/modify/maintain their signature files (I just modified mine today and had to go out of Pine to do so - if I'd been able to mark the block and write it out I wouldn't have had to). John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Tue Feb 1 09:54:07 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02606; Tue, 1 Feb 94 09:54:07 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01292; Tue, 1 Feb 94 09:06:51 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01286; Tue, 1 Feb 94 09:06:38 -0800 Received: from perca.umd.edu by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10407; Tue, 1 Feb 94 09:06:33 -0800 Received: by perca.umd.edu (4.1/SMI-4.1) id AA24062; Tue, 1 Feb 94 12:04:10 EST From: jon@perca.umd.edu (Jonathan Kruger) Message-Id: <9402011704.AA24062@perca.umd.edu> Subject: Re: ULTRIX install problem To: pine-info@cac.washington.edu Date: Tue, 1 Feb 1994 12:04:10 -0500 (EST) Organization: Chesapeake Biological Laboratory X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 303 It's a local problem, nevermind. Curse ULTRIX, curse DEC, argh. ------------------------------------------------------------------------------- Jonathan Kruger - jon@cbl.umd.edu - Computer and Network Systems Coordinator UMCEES/CBL, PO Box 38, Solomons, MD 20688 Phone: 410-326-7306 Fax: 410-326-7361 From owner-pine-info@cac.washington.edu Tue Feb 1 11:26:03 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA05492; Tue, 1 Feb 94 11:26:03 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02764; Tue, 1 Feb 94 10:56:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02756; Tue, 1 Feb 94 10:55:58 -0800 Received: from teaching.physics.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <12143-0@oxmail.ox.ac.uk>; Tue, 1 Feb 1994 18:46:00 +0000 Received: from teaching6 by teaching.physics.ox.ac.uk (NX5.67d/NX3.0M) id AA00701; Tue, 1 Feb 94 18:02:05 GMT Received: by teaching6.physics.ox.ac.uk (NX5.67d/NX3.0X) id AA01285; Tue, 1 Feb 94 18:02:04 GMT Date: Tue, 1 Feb 1994 18:02:03 +0000 (GMT) From: The PenMaster Subject: Pine getting address wrong To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, I'm new to this maling list, but I have I problem that I thought that maybe someone could solve for me. Sorry if its been covered before. My e-mail address is edwards@teaching.physics.ox.ac.uk, but there are a quite a few places from which people have tried sending me mail, but have had it bounce due to `unknown domain', etc. I could live with that problem, because I have discovered that if I use my address as edwards%teaching.physics@ox.ac.uk, then it works from everywhere. I used to use Elm as my mailer, and this was fine because it got my return address, etc. correct, but I have now switched to Pine 3.89, and am experiencing problems. Pine uses the first form of my address. I have tried setting the user-domain=%teaching.physics@ox.ac.uk, but Pine puts a `@' inbetween the username and the domain when I post something locally (eg I input `user' and Pine completes it to `user@%teaching.physics@ox.ac.uk'. Has anyone got any idea how I could solve this? I don't know what it is putting in any of the Reply-To: headers or anything. Would it help if I mailed someone so that they could look to see what it is doing? Perhaps the next version of pine could have a variable that we can set which specifies the complete e-mail address of the user, so that it can be sent up manually if neccessary. Anyway, I would be very grateful if someone could help. Charuuba! David Edwards _ _ ==========////==================================================== / //// David Edwards: Welcome to the real world... \ || _ _ //// send mail to: || || \\\\ //// edwards%teaching.physics@ox.ac.uk || \ \\\X/// or u93dwe@ecs.ox.ac.uk / ====\XXX/========================================================= From owner-pine-info@cac.washington.edu Tue Feb 1 13:14:15 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA08316; Tue, 1 Feb 94 13:14:15 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29148; Tue, 1 Feb 94 12:46:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29142; Tue, 1 Feb 94 12:45:56 -0800 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <01346-0@omega.qmw.ac.uk>; Tue, 1 Feb 1994 20:45:42 +0000 Received: by osprey.elec.qmw.ac.uk (Smail3.1-QMWee); id m0pRRyl-00022aC; Tue, 1 Feb 94 20:45 GMT Date: Tue, 1 Feb 1994 20:45:47 +0000 (GMT) Subject: logging mailbox access To: pine-info@cac.washington.edu Cc: C.C.Cock@qmw.ac.uk, A.P.Martin@qmw.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII From: Laurie Cuthbert X-Original-Sender: laurie Now that we have moved student email in the department away from pop to imap-based mailers (mainly pine) we would like to be able to log when they have accessed the mailbox. This is purely so we can see which students have NOT read their mail for some time as it may be a warning that they are having some sort of problems and maybe dropping out - early warning can often solve the problem. With pop we could do that by checking the date stamp on the lock file but there seems no obvious way with imapd. Have I missed something (obvious) ? Regards Laurie Cuthbert From owner-pine-info@cac.washington.edu Tue Feb 1 13:30:49 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA08750; Tue, 1 Feb 94 13:30:49 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29549; Tue, 1 Feb 94 13:05:25 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29541; Tue, 1 Feb 94 13:05:19 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA23641; Tue, 1 Feb 94 13:04:56 -0800 Date: Tue, 1 Feb 1994 13:04:51 -0800 (PST) From: David L Miller Subject: Re: Pine getting address wrong To: The PenMaster Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII David, The next version of Pine will support the Reply-To: header and possibly a mechanism to modify the From: header. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 1 Feb 1994, The PenMaster wrote: > > Greetings, > I'm new to this maling list, but I have I problem that I thought > that maybe someone could solve for me. Sorry if its been covered before. > > My e-mail address is edwards@teaching.physics.ox.ac.uk, but there > are a quite a few places from which people have tried sending me mail, > but have had it bounce due to `unknown domain', etc. I could live with > that problem, because I have discovered that if I use my address as > edwards%teaching.physics@ox.ac.uk, then it works from everywhere. > > I used to use Elm as my mailer, and this was fine because it got > my return address, etc. correct, but I have now switched to Pine 3.89, > and am experiencing problems. Pine uses the first form of my address. > > I have tried setting the user-domain=%teaching.physics@ox.ac.uk, > but Pine puts a `@' inbetween the username and the domain when I post > something locally (eg I input `user' and Pine completes it to > `user@%teaching.physics@ox.ac.uk'. > > Has anyone got any idea how I could solve this? I don't know what > it is putting in any of the Reply-To: headers or anything. Would it help > if I mailed someone so that they could look to see what it is doing? > Perhaps the next version of pine could have a variable that we can set > which specifies the complete e-mail address of the user, so that it can > be sent up manually if neccessary. > > Anyway, I would be very grateful if someone could help. > > Charuuba! > > David Edwards > _ _ > ==========////==================================================== > / //// David Edwards: Welcome to the real world... \ > || _ _ //// send mail to: || > || \\\\ //// edwards%teaching.physics@ox.ac.uk || > \ \\\X/// or u93dwe@ecs.ox.ac.uk / > ====\XXX/========================================================= > From owner-pine-info@cac.washington.edu Tue Feb 1 13:58:52 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA09546; Tue, 1 Feb 94 13:58:52 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29920; Tue, 1 Feb 94 13:27:37 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29914; Tue, 1 Feb 94 13:27:32 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA27085; Tue, 1 Feb 94 13:26:58 -0800 Date: Tue, 1 Feb 1994 13:24:02 -0800 (PST) From: Mark Crispin Subject: re: logging mailbox access To: Laurie Cuthbert Cc: pine-info@cac.washington.edu, C.C.Cock@qmw.ac.uk, A.P.Martin@qmw.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 1 Feb 1994 20:45:47 +0000 (GMT), Laurie Cuthbert wrote: > Now that we have moved student email in the department away from pop to > imap-based mailers (mainly pine) we would like to be able to log when > they have accessed the mailbox. This is purely so we can see which > students have NOT read their mail for some time as it may be a warning > that they are having some sort of problems and maybe dropping out - early > warning can often solve the problem. > > With pop we could do that by checking the date stamp on the lock file but > there seems no obvious way with imapd. Have I missed something (obvious) ? Since you're just interested in last access and not in any access telemetry, have you considered using the file access time? Another possibility is to modify the server_login() routine in imap/c- client/os_???.c to write a timestamp of your choosing; that way, you'll be able to discriminate inactive users specifically. From owner-pine-info@cac.washington.edu Tue Feb 1 15:46:54 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA12819; Tue, 1 Feb 94 15:46:54 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06050; Tue, 1 Feb 94 15:26:38 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06044; Tue, 1 Feb 94 15:26:25 -0800 Received: from apus.cus.cam.ac.uk [131.111.8.2] (TAP id = root) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pRUU7-000BzEC; Tue, 1 Feb 94 23:26 GMT Received: by apus.cus.cam.ac.uk (Smail-3.1.28.1 #110) id m0pRUU6-0004Y7C; Tue, 1 Feb 94 23:26 GMT Date: Tue, 1 Feb 1994 23:26:17 +0000 (GMT) From: Barry Landy Subject: Re: Pine getting address wrong To: The PenMaster Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Without checking, I suspect you are hitting a UK problem here. I suspect that teaching.physics.ox.ac.uk is not registered in the NRS as a mail domain, but is registered in the DNS. This will have the effect that anyone that mails to you directly using smtp will get the mail through; any mail that goes through "official gateways" will not. The Reply-To: feature that is promised for later versions will "cure" the problem; alternatively, registering the teaching. etc in the NRS for mail (though oxford might have other objections to this). On the assumption that physics.ox is properly registered (and that you have a suitable mailbox there) you could get PINE to specify your mail address as edwards@physics.ox.ac.uk (and indeed you could leave your INBOX there as well). On Tue, 1 Feb 1994, The PenMaster wrote: > > Greetings, > I'm new to this maling list, but I have I problem that I thought > that maybe someone could solve for me. Sorry if its been covered before. > > My e-mail address is edwards@teaching.physics.ox.ac.uk, but there > are a quite a few places from which people have tried sending me mail, > but have had it bounce due to `unknown domain', etc. I could live with > that problem, because I have discovered that if I use my address as > edwards%teaching.physics@ox.ac.uk, then it works from everywhere. > > I used to use Elm as my mailer, and this was fine because it got > my return address, etc. correct, but I have now switched to Pine 3.89, > and am experiencing problems. Pine uses the first form of my address. > > I have tried setting the user-domain=%teaching.physics@ox.ac.uk, > but Pine puts a `@' inbetween the username and the domain when I post > something locally (eg I input `user' and Pine completes it to > `user@%teaching.physics@ox.ac.uk'. > > Has anyone got any idea how I could solve this? I don't know what > it is putting in any of the Reply-To: headers or anything. Would it help > if I mailed someone so that they could look to see what it is doing? > Perhaps the next version of pine could have a variable that we can set > which specifies the complete e-mail address of the user, so that it can > be sent up manually if neccessary. > > Anyway, I would be very grateful if someone could help. > > Charuuba! > > David Edwards > _ _ > ==========////==================================================== > / //// David Edwards: Welcome to the real world... \ > || _ _ //// send mail to: || > || \\\\ //// edwards%teaching.physics@ox.ac.uk || > \ \\\X/// or u93dwe@ecs.ox.ac.uk / > ====\XXX/========================================================= > > > ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Tue Feb 1 23:29:55 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA20089; Tue, 1 Feb 94 23:29:55 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06783; Tue, 1 Feb 94 23:07:27 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from castor.cc.utu.fi by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06777; Tue, 1 Feb 94 23:07:24 -0800 Received: by utu.fi via suspension id <165416-2>; Wed, 2 Feb 1994 09:04:24 +0200 Received: by utu.fi id <165417-9>; Wed, 2 Feb 1994 08:48:00 +0200 Date: Wed, 2 Feb 1994 08:47:52 +0200 From: Kari Sutela Subject: Re: logging mailbox access To: Laurie Cuthbert Cc: pine-info@cac.washington.edu, C.C.Cock@qmw.ac.uk, A.P.Martin@qmw.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 1 Feb 1994, Laurie Cuthbert wrote: > With pop we could do that by checking the date stamp on the lock file but > there seems no obvious way with imapd. Have I missed something (obvious) ? Just check the access time on their mailbox file (for example, "ls -lu /var/spool/mail/user" if your mailboxes are located in /var/spool/mail). This is what finger does. /KS From owner-pine-info@cac.washington.edu Wed Feb 2 01:22:18 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA21954; Wed, 2 Feb 94 01:22:18 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10272; Wed, 2 Feb 94 01:06:23 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10266; Wed, 2 Feb 94 01:06:21 -0800 Received: from rs1.jr2.ox.ac.uk by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA17625; Wed, 2 Feb 94 01:06:15 -0800 Received: by rs1.jr2.ox.ac.uk (AIX 3.2/UCB 5.64/4.03) id AA12876; Wed, 2 Feb 1994 09:03:56 GMT Date: Wed, 2 Feb 1994 09:03:55 +0000 (GMT) From: Programmer x 21323 Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII subscribe terry@rs1.jr2.ox.ac.uk From owner-pine-info@cac.washington.edu Wed Feb 2 01:38:54 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA22337; Wed, 2 Feb 94 01:38:54 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10383; Wed, 2 Feb 94 01:19:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10377; Wed, 2 Feb 94 01:19:18 -0800 Received: from imagen.materials.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <09575-0@oxmail.ox.ac.uk>; Wed, 2 Feb 1994 09:18:59 +0000 Received: by imagen.materials.ox.ac.uk (930416.SGI/931108.SGI.AUTO.ANONFTP) for @oxmail.ox.ac.uk:edwards@teaching.physics.ox.ac.uk id AA18021; Wed, 2 Feb 94 09:18:56 GMT Date: Wed, 2 Feb 1994 09:18:53 +0000 (GMT) From: Neil J Long Subject: Re: Pine getting address wrong To: Barry Landy Cc: The PenMaster , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII HI It is a major headache for us all - the only way around it is to edit the sendmail.cf to force it to use %host.dept@ox.ac.uk when it generates a from: address AND ^^^ modify the pine send.c (?) to prevent pine generating a from: line. (There are 2 sections of code which have to be def'd out). The sendmail.cf mods are needed for all mailers unless the machine is registered outside the .ox.ac.uk domain. The pine mods are to prevent pine generating a valid from: line which passes straight through sendmail rules. I have done this for SGI's and HP's here in materials and can offer limited advice. Many people have switched back to using elm and PC/Mac Eudora until Pine comes up with a Reply-To: option. Come on guys, hurry, hurry with the next release - just joking!! __________________________________________________ Dr Neil J Long phone: +44 (0) 865 273656 University of Oxford FAX: +44 (0) 865 273789 Department of Materials __________________________________________________ From owner-pine-info@cac.washington.edu Wed Feb 2 01:40:31 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA22378; Wed, 2 Feb 94 01:40:31 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07877; Wed, 2 Feb 94 01:18:58 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07871; Wed, 2 Feb 94 01:18:52 -0800 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <07173-0@omega.qmw.ac.uk>; Wed, 2 Feb 1994 09:18:20 +0000 Received: from lauriepc by osprey.elec.qmw.ac.uk with SMTP (smail) id ; Wed, 2 Feb 94 09:18 GMT Date: Wed, 2 Feb 1994 09:18:23 GMT From: Laurie Cuthbert Subject: re: logging mailbox access To: Mark Crispin Cc: Laurie Cuthbert , pine-info@cac.washington.edu, C.C.Cock@qmw.ac.uk, A.P.Martin@qmw.ac.uk Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Mark Thanks for the response. I should have explained in the original message that delivering mail with smail, the access time appears to be updated when mail is delivered as well as retrieved, so we can't use that. I was hoping for any easy switch to cause to imapd to write info to syslog but we'll now have to investigate server_login(). Thanks Laurie On Tue, 1 Feb 1994 13:24:02 -0800 (PST) Mark Crispin wrote: > From: Mark Crispin > Date: Tue, 1 Feb 1994 13:24:02 -0800 (PST) > Subject: re: logging mailbox access > To: Laurie Cuthbert > Cc: pine-info@cac.washington.edu, C.C.Cock@qmw.ac.uk, A.P.Martin@qmw.ac.uk > > On Tue, 1 Feb 1994 20:45:47 +0000 (GMT), Laurie Cuthbert wrote: > > Now that we have moved student email in the department away from pop to > > imap-based mailers (mainly pine) we would like to be able to log when > > they have accessed the mailbox. This is purely so we can see which > > students have NOT read their mail for some time as it may be a warning > > that they are having some sort of problems and maybe dropping out - early > > warning can often solve the problem. > > > > With pop we could do that by checking the date stamp on the lock file but > > there seems no obvious way with imapd. Have I missed something (obvious) ? > > Since you're just interested in last access and not in any access telemetry, > have you considered using the file access time? > > Another possibility is to modify the server_login() routine in imap/c- > client/os_???.c to write a timestamp of your choosing; that way, you'll be > able to discriminate inactive users specifically. > From owner-pine-info@cac.washington.edu Wed Feb 2 02:01:58 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA22802; Wed, 2 Feb 94 02:01:58 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10543; Wed, 2 Feb 94 01:38:39 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10537; Wed, 2 Feb 94 01:38:37 -0800 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA17921; Wed, 2 Feb 94 01:38:35 -0800 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 02 Feb 94 10:35:42+0100 Date: 02 Feb 94 10:35:42+0100 From: "Programmer x 21323" Message-Id: <560747*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine User Group From owner-pine-info@cac.washington.edu Wed Feb 2 02:14:10 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA22943; Wed, 2 Feb 94 02:14:10 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08104; Wed, 2 Feb 94 01:51:27 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08068; Wed, 2 Feb 94 01:50:53 -0800 Received: from quinag.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <27756-0@ppsw2.cam.ac.uk>; Wed, 2 Feb 1994 09:50:44 +0000 Date: Wed, 2 Feb 1994 09:48:35 GMT From: Barry Landy Reply-To: Barry Landy Subject: Re: Pine getting address wrong To: The PenMaster <@ox.ac.uk:edwards@teaching.physics> Cc: pine-info@cac.washington.edu X-Sender: bl10@cus.cam.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII We have checked and found a number of problems with mail registration at Oxford (ox.ac.uk) which we are communicating directly with postmaster and hostmaster at Oxford. ------------------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 223 334600 Head of Systems and Development Direct line: +44 223 334713 University of Cambridge Computing Service New Museums Site Email:Barry.Landy@ucs.cam.ac.uk Pembroke Street, Cambridge CB2 3QG From owner-pine-info@cac.washington.edu Wed Feb 2 03:53:45 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA24560; Wed, 2 Feb 94 03:53:45 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11175; Wed, 2 Feb 94 03:34:06 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11169; Wed, 2 Feb 94 03:34:01 -0800 Received: from ursa.cus.cam.ac.uk [131.111.8.6] (TAP id = 1169) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pRfq1-000BzEC; Wed, 2 Feb 94 11:33 GMT Date: Wed, 2 Feb 1994 11:33:09 +0000 (GMT) From: Philip Hazel Subject: Re: Pine getting address wrong To: Neil J Long Cc: Barry Landy , The PenMaster , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 439 > It is a major headache for us all - the only way around it is to edit the > sendmail.cf to force it to use %host.dept@ox.ac.uk when it generates a > from: address Pity, since the % form of source routing is deprecated in the Internet. -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Wed Feb 2 05:05:48 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26149; Wed, 2 Feb 94 05:05:48 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11733; Wed, 2 Feb 94 04:32:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11727; Wed, 2 Feb 94 04:32:37 -0800 Received: from imagen.materials.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <20621-0@oxmail.ox.ac.uk>; Wed, 2 Feb 1994 12:32:12 +0000 Received: by imagen.materials.ox.ac.uk (930416.SGI/931108.SGI.AUTO.ANONFTP) for @oxmail.ox.ac.uk:edwards@teaching.physics.ox.ac.uk id AA18675; Wed, 2 Feb 94 12:31:59 GMT From: long%imagen.materials@ox.ac.uk (Neil J Long) Date: Wed, 2 Feb 1994 12:31:57 +0000 (GMT) Subject: Re: Pine getting address wrong (fwd) To: postmaster@ox.ac.uk Cc: The PenMaster , pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sorry, I used an unhacked version of pine by mistake. This should have the % kludge in the from: line Neil From owner-pine-info@cac.washington.edu Wed Feb 2 05:27:16 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26428; Wed, 2 Feb 94 05:27:16 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09806; Wed, 2 Feb 94 05:05:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from oxmail.ox.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09800; Wed, 2 Feb 94 05:05:39 -0800 Received: from teaching.physics.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <22489-0@oxmail.ox.ac.uk>; Wed, 2 Feb 1994 13:05:00 +0000 Received: from teaching6 by teaching.physics.ox.ac.uk (NX5.67d/NX3.0M) id AA03905; Wed, 2 Feb 94 13:04:45 GMT Received: by teaching6.physics.ox.ac.uk (NX5.67d/NX3.0X) id AA03913; Wed, 2 Feb 94 13:04:43 GMT Date: Wed, 2 Feb 1994 13:04:42 +0000 (GMT) From: The PenMaster Subject: Re: Pine getting address wrong (fwd) To: Neil J Long Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there any chance you can tell me exactly what I need to change to get my address working? Perhaps you could send me the relevent pieces of hacked source code/sendmail.cf files. If you could, I'd be very grateful... Charuuba! David _ _ ==========////==================================================== / //// David Edwards: Welcome to the real world... \ || _ _ //// send mail to: || || \\\\ //// edwards%teaching.physics@ox.ac.uk || \ \\\X/// or u93dwe@ecs.ox.ac.uk / ====\XXX/========================================================= From owner-pine-info@cac.washington.edu Wed Feb 2 06:16:52 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA27153; Wed, 2 Feb 94 06:16:52 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12348; Wed, 2 Feb 94 05:57:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dir.bris.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12342; Wed, 2 Feb 94 05:57:08 -0800 Received: from adm1.bristol.ac.uk by dir.bris.ac.uk with SMTP (PP) id <01925-0@dir.bris.ac.uk>; Wed, 2 Feb 1994 13:56:51 +0000 Date: Wed, 2 Feb 1994 13:57:27 +0000 (GMT) From: Dave King Subject: Tenex format To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Can anyone help with these questions?: 1. It's easy to get Pine's INBOX into tenex format by touch(ing) mail.TxT, but is there an easy way to reverse the process? 2. Is there a technical description of the tenex format so that I can incorporate tenex support in a program I've written (specifically how to determine the start and end of a message, and its status: New, Old, or Unread). I'd like to make use of tenex but am wary about going up a one way street! Thanks in advance, Dave ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) From owner-pine-info@cac.washington.edu Wed Feb 2 09:42:27 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA01558; Wed, 2 Feb 94 09:42:27 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13850; Wed, 2 Feb 94 09:03:32 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13844; Wed, 2 Feb 94 09:03:30 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07223; Wed, 2 Feb 94 09:02:59 -0800 Date: Wed, 2 Feb 1994 09:02:59 -0800 (PST) From: David L Miller Subject: Re: Tenex format To: Dave King Cc: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII No, there is not currently a painless way to reverse the process. A simple copier program would be pretty trivial using c-client, but none of us have gotten around to writing it. I did talk to someone a few weeks ago who was going to write such a beast, but have not heard anything in a while. The Pine Technical Notes include a description of the Tenex format. The easiest way to add Tenex support to your app would be to call the appropriate c-client routines. You might also want to wait for the Unix MTX driver. This is almost identical to Tenex format, but is binary compatible with the MTX format used in PC-Pine. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 2 Feb 1994, Dave King wrote: > Can anyone help with these questions?: > > 1. It's easy to get Pine's INBOX into tenex format by touch(ing) mail.TxT, > but is there an easy way to reverse the process? > > 2. Is there a technical description of the tenex format so that I can > incorporate tenex support in a program I've written (specifically how > to determine the start and end of a message, and its status: New, Old, > or Unread). > > I'd like to make use of tenex but am wary about going up a one way street! > > Thanks in advance, > > > Dave > > ------------------------------------------------------------------- > Dave King, Admin. Computing Services Manager, University of Bristol > Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) > From owner-pine-info@cac.washington.edu Wed Feb 2 09:58:19 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02175; Wed, 2 Feb 94 09:58:19 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12372; Wed, 2 Feb 94 09:26:59 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cs1.bradley.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12366; Wed, 2 Feb 94 09:26:58 -0800 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA01935; Wed, 2 Feb 94 11:26:57 CST Date: Wed, 2 Feb 1994 11:26:56 -0600 (CST) From: Matt Simmons Subject: Pine is greedy To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII When you exit pine, it seems to suck up all of the keystrokes from the time you hit expunge-yes until the prompt returns... Is there any way for pine to not suck up these keystrokes, so I can start typing the next command while it is exitting? I've noticed this problem with other (SunOS 4.1.something) programs... Is it a general UNIXism? Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Thu Feb 3 00:57:03 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA20740; Thu, 3 Feb 94 00:57:03 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22354; Thu, 3 Feb 94 00:42:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from castor.cc.utu.fi by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22348; Thu, 3 Feb 94 00:42:46 -0800 Received: by utu.fi id <165433-5>; Thu, 3 Feb 1994 10:42:34 +0200 Date: Thu, 3 Feb 1994 10:42:26 +0200 From: Kari Sutela Subject: 8-bit characters in the header. To: Pine mailing list Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE I know this can be controversial, but I'd like the option of using 8-bit characters (we use ISO 8859-1, here) in the header part of the message.=20 Our users are especially concerned because they can't use 8-bit characters in the Subject field (=E4 and =F6 are very common letters in Finnish).=20 Could this option be included in a future version of Pine? Perhaps as a compile time option (-DALLOW_8BIT_IN_HEADER_ENTRY)? Perhaps the header fields where 8-bit chars are found could be quoted-printable-encoded?=20 Please. I know this would break some rules but our users would be very delighted.=20 /KS From owner-pine-info@cac.washington.edu Thu Feb 3 09:22:52 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA28258; Thu, 3 Feb 94 09:22:52 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28324; Thu, 3 Feb 94 08:40:14 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28318; Thu, 3 Feb 94 08:40:13 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13578; Thu, 3 Feb 94 08:40:00 -0800 Date: Thu, 3 Feb 1994 08:40:00 -0800 (PST) From: David L Miller Subject: Re: 8-bit characters in the header. To: Kari Sutela Cc: Pine mailing list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Actually it's not that controversial, RFC1522 defines a way to represent non-ASCII characters in headers. Pine will support this eventually, but probably not in the next release. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 3 Feb 1994, Kari Sutela wrote: >=20 > I know this can be controversial, but I'd like the option of using 8-bit > characters (we use ISO 8859-1, here) in the header part of the message.= =20 > Our users are especially concerned because they can't use 8-bit character= s > in the Subject field (=E4 and =F6 are very common letters in Finnish).=20 >=20 > Could this option be included in a future version of Pine? Perhaps as a > compile time option (-DALLOW_8BIT_IN_HEADER_ENTRY)? Perhaps the header > fields where 8-bit chars are found could be quoted-printable-encoded?=20 > Please. I know this would break some rules but our users would be very > delighted.=20 >=20 > /KS From owner-pine-info@cac.washington.edu Thu Feb 3 10:58:13 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA01254; Thu, 3 Feb 94 10:58:13 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29734; Thu, 3 Feb 94 10:08:16 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cheviot.ncl.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29722; Thu, 3 Feb 94 10:08:05 -0800 Received: from (scawdell.ncl.ac.uk) by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Thu, 3 Feb 1994 18:07:55 GMT Date: Thu, 3 Feb 1994 18:07:48 +0000 (GMT) From: "A. Hilborne" Subject: Re: Suggestions To: "Gregory J. Atchity" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 27 Jan 1994, Gregory J. Atchity wrote: > I just joined this group a week ago, and I see a lot of suggestions, > so I guess they are welcomed by the designers. I'll put my two cents > in, let me know if you want any more of my money. > > First, I'd rather see the number of lines in a message in the index > instead of the number of characters it has. I don't receive that much > mime, and so lines is a bit more useful to me. Perhaps that should be an > option. > > Second, why does the 'To:' line require commas between members of a > list? I don't know much about mail programs, but I thought all addresses > had to be one word, and so I'd like to see Pine parse each word regardless > of whether it has a comma after it or not, and insert the commas for me if > I forget. This sounds do-able to me, even if aliases can be multi-word. This message is a good example of how Pine has moved far away from it's principle original design goal--KISS or, "Keep it simple, stupid." The kinds of things Gregory would like to see are options in Mush, VM (almost certainly) and probably several other mailers designed for power users. I started using Pine because it was a solid mailer which did 70 percent of what I wanted to do and did much of it well. Yes, only 70 percent. I always wanted a score or so "enhancements." However I knew that the sum total of all the different enhancements which Pine users the world over wanted numbered a few hundred. I was happy to stick with a simple mailer because it could be used adequately not only by me, but by all users of many different levels of understanding and ability. For the same reason our Computing Service here was happy to offer Pine as our standard UNIX mailer. We wanted to have something that was simple to use, required no user configuration and which (one of early Pine's proud boasts) didn't need paper documentation because it was so small. Use of IMAP and MIME were additional advantages which could simplify and enhance our mail setup here but they were secondary. Now creeping featurism threatens to swallow Pine whole. The present configuration file is a nightmare in some areas, and it continually grows. One may see some of the problems by the number of exchanges on this list which go: Q. Why doesn't pine do "this?" A (several times.) Just put "option77=blah" in your .pinerc file. Pine is now complicated. Don't misunderstand me. There are some wonderful parts of Pine. Pico is pretty good and so are the supplied IMAP daemon and the c-client. Indeed it is because of these, Pine's solid base, that there is such a demand for Pine to do even more. I don't like this idea (although all my wished-for extra features still aren't implemented :-) Equally to the point I know that there are a lot of people who are unhappy at Pine's current development. I'm afraid that I don't have a definitive solution, but I will offer one suggestion: Pine should be frozen at it's current state of development, or preferably a couple of states back, where the config file was simpler and there were no stubs for "coming" features visible to the user. This version of Pine can either retain the name, or become, say, "Pinelet." Perhaps someone out there can think of a suitable diminutive name. The version we have now can then move on until it suits all us power users out here. Only bug fixes would be back-grafted onto Pinelet. What do you think? -- Andrew M. Hilborne Andrew.Hilborne@newcastle.ac.uk Computing Service Tel: +44 91 222 8226 (direct) University of Newcastle upon Tyne, UK. +44 91 222 8039 (Comp Service office) From owner-pine-info@cac.washington.edu Thu Feb 3 13:14:24 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05232; Thu, 3 Feb 94 13:14:24 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29743; Thu, 3 Feb 94 12:43:22 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29737; Thu, 3 Feb 94 12:43:17 -0800 Received: from apus.cus.cam.ac.uk [131.111.8.2] (TAP id = root) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pSAtG-000BzSC; Thu, 3 Feb 94 20:43 GMT Received: by apus.cus.cam.ac.uk (Smail-3.1.28.1 #110) id m0pSAtF-0004Y7C; Thu, 3 Feb 94 20:43 GMT Date: Thu, 3 Feb 1994 20:43:05 +0000 (GMT) From: Barry Landy Subject: Re: Suggestions To: "A. Hilborne" Cc: "Gregory J. Atchity" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII (I have edited the commented original as it is getting v long). I agree strongly with the KISS aim, though I dont arrive at the same conclusion as Andrew, probably because my simple users still find it simple. My replies thus reflect that principle. On Thu, 3 Feb 1994, A. Hilborne wrote: > On Thu, 27 Jan 1994, Gregory J. Atchity wrote: > > First, I'd rather see the number of lines in a message in the index > > instead of the number of characters it has. > > KISS says "please give the users information they understand; a 'random' large number tells them nothing (and since the count includes data in headers, it really *is* random). I personally see no reason for any data of this type, but if there has to be, line count sounds sensible to me (if well defined). > > Second, why does the 'To:' line require commas between members of a > > list? I don't know much about mail programs, but I thought all addresses > > had to be one word, and so I'd like to see Pine parse each word regardless > > of whether it has a comma after it or not, and insert the commas for me if > > I forget. This sounds do-able to me, even if aliases can be multi-word. > This one I cannot agree with; permitting implied separators causes chaos. Separation by commas is well understood even in plain English (apples, oranges, and pears). > This message is a good example of how Pine has moved far away from it's > principle original design goal--KISS or, "Keep it simple, stupid." Lots omitted here............ > Pine should be frozen at it's current state of development, or preferably a > couple of states back, where the config file was simpler and there were no > stubs for "coming" features visible to the user. > > This version of Pine can either retain the name, or become, say, "Pinelet." > Perhaps someone out there can think of a suitable diminutive name. The > version we have now can then move on until it suits all us power users out > here. Only bug fixes would be back-grafted onto Pinelet. > > What do you think? Knowing that a lot of the coming features have been asked for by our users, especially features to make asynch use much more efficient (eg phone use) I cannot support this. I think the critical thing is to keep the simple subset clear (and simple!). ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Thu Feb 3 13:15:14 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05267; Thu, 3 Feb 94 13:15:14 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29517; Thu, 3 Feb 94 12:25:48 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from digi.syd.deg.CSIRO.AU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA29511; Thu, 3 Feb 94 12:25:44 -0800 Received: by digi.syd.deg.csiro.au id AA04349 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Fri, 4 Feb 1994 07:29:57 +1100 Date: Fri, 4 Feb 1994 07:15:41 +1100 (EST) From: Jack Churchill Subject: Re: Suggestions To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 3 Feb 1994, A. Hilborne wrote: > I started using Pine because it was a solid mailer which did 70 percent of what > I wanted to do and did much of it well. Yes, only 70 percent. I always wanted > a score or so "enhancements." However I knew that the sum total of all the > different enhancements which Pine users the world over wanted numbered a few > hundred. Same here. > I was happy to stick with a simple mailer because it could be used adequately > not only by me, but by all users of many different levels of understanding and > ability. For the same reason our Computing Service here was happy to offer > Pine as our standard UNIX mailer. We wanted to have something that was simple > to use, required no user configuration and which (one of early Pine's proud > boasts) didn't need paper documentation because it was so small. Use of IMAP > and MIME were additional advantages which could simplify and enhance our mail > setup here but they were secondary. Same here. > Now creeping featurism threatens to swallow Pine whole. The present > configuration file is a nightmare in some areas, and it continually grows. One > may see some of the problems by the number of exchanges on this list which go: > > Q. Why doesn't pine do "this?" > > A (several times.) Just put "option77=blah" in your .pinerc file. > > Pine is now complicated. > I'm afraid that I don't have a definitive solution, but I will offer one > suggestion: > > Pine should be frozen at it's current state of development, or preferably a > couple of states back, where the config file was simpler and there were no > stubs for "coming" features visible to the user. How about a menu-driven configuration built into pine with documentation to explain what the various options mean. To add spice have special options in the global config file to stop users modifying their own configs. More work I know but it would make pine configuration much simpler for the users. Jack N. Churchill | Jack.Churchill@dem.csiro.au CSIRO Division of Exploration and Mining | churchill@decus.com.au PO Box 136 North Ryde NSW 2113 | Phone: +61 2 887 8884 Australia | Fax: +61 2 887 8921 From owner-pine-info@cac.washington.edu Thu Feb 3 13:46:39 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06065; Thu, 3 Feb 94 13:46:39 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02510; Thu, 3 Feb 94 13:15:04 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cd1.lrz-muenchen.de by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA02501; Thu, 3 Feb 94 13:15:00 -0800 Received: from sunserver.lrz-muenchen.de by cd1.lrz-muenchen.de id SMTP-0012d516950012620; Thu, 3 Feb 94 22:14:56 +0100 Received: from sun3.lrz-muenchen.de by sunserver.lrz-muenchen.de (4.1/SMI-4.1) id AA05666; Thu, 3 Feb 94 22:14:55 +0100 Received: by sun3.lrz-muenchen.de (4.1/SMI-4.1) id AA24114; Thu, 3 Feb 94 22:14:54 +0100 Date: Thu, 3 Feb 1994 22:14:54 +0100 (MET) From: Michael Wolf Reply-To: Michael Wolf Subject: Re: Suggestions To: "A. Hilborne" Cc: "Gregory J. Atchity" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 3 Feb 1994, A. Hilborne wrote: > > Pine is now complicated. > > Don't misunderstand me.There are some wonderful parts of Pine. Pico is > pretty good and so are the supplied IMAP daemon and the c-client.Indeed it is > because of these, Pine's solid base, that there is such a demand for Pine to do > even more.I don't like this idea (although all my wished-for extra features > still aren't implemented :-)Equally to the point I know that there are a lot > of people who are unhappy at Pine's current development. > > I'm afraid that I don't have a definitive solution, but I will offer one > suggestion: > > Pine should be frozen at it's current state of development, or preferably a > couple of states back, where the config file was simpler and there were no > stubs for "coming" features visible to the user. > > This version of Pine can either retain the name, or become, say, "Pinelet." > Perhaps someone out there can think of a suitable diminutive name. The > version we have now can then move on until it suits all us power users out > here. Only bug fixes would be back-grafted onto Pinelet. > > What do you think? > > -- > Andrew M. Hilborne Andrew.Hilborne@newcastle.ac.uk > Computing Service Tel: +44 91 222 8226 (direct) > University of Newcastle upon Tyne, UK. +44 91 222 8039 (Comp Service office) > I am new to this list, I use pine now instead of elm since several weeks and I like it. In order to satisfy both "normal" users and power users I would prefer to have a "User Level" command with options "beginner" and "advanced" and in addition, to have the possibility to generate .pinerc through a dialog. Michael Wolf | email: Dept of Mechanical and Automotive Engineering | michael.wolf@lrz-muenchen.de Fachhochschule Muenchen University | From owner-pine-info@cac.washington.edu Thu Feb 3 14:37:01 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07343; Thu, 3 Feb 94 14:37:01 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03173; Thu, 3 Feb 94 14:04:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03167; Thu, 3 Feb 94 14:04:39 -0800 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <25435-0@susssys1.reading.ac.uk>; Thu, 3 Feb 1994 21:14:03 +0000 Date: Thu, 3 Feb 1994 21:16:30 GMT From: John Stumbles Reply-To: John Stumbles Subject: Re: Suggestions To: "A. Hilborne" Cc: pine-info@cac.washington.edu X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 3 Feb 1994, A. Hilborne wrote: [...in reply to a suggested enhancement...] > I started using Pine because it was a solid mailer which did 70 percent o= f what > I wanted to do and did much of it well.=20 [...] > Now creeping featurism threatens to swallow Pine whole. The present > configuration file is a nightmare in some areas, and it continually grows= .=20 [...] > What do you think? Firstly pardon the severe edits - I'd done a more thorough job on this reply and just got to the end, reformatted the last paragraph, and ... got an error message about failing to allocate 144 bytes or something. Pine could have snipped 144 chars from my message, I wouldn't have cared so much - instead it just hung there 'till I gave the PC the 3-finger salute and then I lost the lot :-( Anyway, I quite agree with you about the config file - it is a nightmare! - but I'd like to separate it from the other sort of enhancement request you were actually replying to which was about "when a user does can Pine be made to treat it as a correct thing to do instead of spitting it out as an error". The example was separating mail aliases by commas or spaces - other examples are showing end-of-file messages when the end has been displayed instead of when the user tries to page down, and the action of various PC cursor keys. These sorts of enhancements do not require extra menu options or setting in the config file, and can make Pine more instinctively natural to use - user friendly - which I believe is the pine philosophy and A Good Thing!=20 Anyway the *%=9C"@#! config file - I suggest: (1) most straightforward options should be settable by the (promised)=20 Setup/Options screen, so the casual user should never have to edit their=20 .pinerc or (PC) PINERC file (2) Pine should come 'out of the box' with a simple config file that can=20 be set by the Options function, and this file can either be expanded by=20 the user adding options manually, or by the user setting an=20 'intermediate' or 'advanced' user setting - in some way that the casual=20 user cannot do accidentally. Maybe by running pine from the command line=20 with some flag like: =09PINE user_options=3Dintermediate [or advanced] whereupon it would read the current config file and write out a new one=20 with extra bells and whistles. (3) documentation! At present there is nothing between the 2-page Readme file and the 180K tech notes (in some wierd MAN-page type of format) which has to be FTPed over separateley. I suggest pine should come with some intermediate level documentation which should explain what you can configure, and give examples in more detail than in the config file (indeed why have any in the config file - particularly in the PC version where RAM is precious - if you can have decent documentation with it?) The point is if you've got documentation you don't have to read it - and the casual user won't - but if you haven't got it you can't!=20 (?) actually I think there could be a case for having two config files - particularly in PC-PINE - one for the user's name, login id etc (which the user could muck about with) and another for system-type settings (like inbox-path=3D{imaphost.domain}inbox etc which are easier to screw up and the casual user unlikely to need to deal with). John Stumbles j.d.stumbles@reading.ac= .uk University of Reading 0734 318= 435 Whiteknights, Reading, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+= -+-+ From owner-pine-info@cac.washington.edu Thu Feb 3 14:38:10 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07376; Thu, 3 Feb 94 14:38:10 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03180; Thu, 3 Feb 94 14:04:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sussdirt.rdg.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03174; Thu, 3 Feb 94 14:04:48 -0800 Received: from reading.ac.uk by susssys1.reading.ac.uk with SMTP (PP) id <25535-0@susssys1.reading.ac.uk>; Thu, 3 Feb 1994 21:32:06 +0000 Date: Thu, 3 Feb 1994 21:32:03 +0000 (GMT) From: Mike Roch Reply-To: Mike Roch Subject: Re: Suggestions Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Length: 1962 On Thu, 3 Feb 1994, A. Hilborne wrote: > ability. For the same reason our Computing Service here was happy to offer > Pine as our standard UNIX mailer. We wanted to have something that was simple > to use, required no user configuration and which (one of early Pine's proud > boasts) didn't need paper documentation because it was so small. Use of IMAP > and MIME were additional advantages which could simplify and enhance our mail > setup here but they were secondary. > > Now creeping featurism threatens to swallow Pine whole. The present > configuration file is a nightmare in some areas, and it continually grows. I'm very conscious that Pine is Washington's property - they made it - they pay for it and so they're entitled to do what they like with it - the rest of us are just free-loading. However, I have to say that I agree wholeheartedly with Andrew on this. (Boring over here aren't we?) We chose Pine because it did most of the things that most people wanted - painlessly. User support gets harder as more arcane features/options are added. Instead of having 20 advisors who know all about Pine 3.0x, we're unlikely to have more than 5 who'll get to grips with all of Pine 3.8x. I do think that you should be conservative about adding features unless they are geared to making life easier for Pine's original constituency. By definition this list is for the people who setup/fix Pine, not its users - contributions are unlikely to be representative of the user base. On the same reasoning it's the ever-growing Pine strand that should have a new name, not the "original". The original joke (PIne's Not Elm) is going to backfire when people start to say that Pine's Not Pine Anymore. 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 Thu Feb 3 16:01:09 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09456; Thu, 3 Feb 94 16:01:09 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01891; Thu, 3 Feb 94 15:05:01 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from emoryu1.cc.emory.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA01873; Thu, 3 Feb 94 15:04:58 -0800 Received: from dooley.cc.emory.edu by emoryu1.cc.emory.edu (5.65/Emory_cc.3.4.16) via SMTP id AA16739 ; Thu, 3 Feb 94 18:04:56 -0500 Return-Path: labsha@unix.cc.emory.edu Date: Thu, 3 Feb 1994 17:48:32 -0500 (EST) From: Shyela Aberman Reply-To: Shyela Aberman Subject: Re: Saving sent mail To: pine-info@cac.washington.edu Cc: answer-l@emuvm1 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hello Folks, Working on a SunOS 5.3 (Sol2) system, I want to keep a copy of all mail I send out. This is easy to do with mail/mush: I add "set record= /home/labsha/mail/record" to my .mailrc. However, I have been having some problems doing the same thing with pine 3.85. I have modified my .pinerc so that "default-fcc=/home/labsha/mail/record", and I have come across some problems when I try to send mail from pine that puzzle me. When I try to send mail I get the following message: Folder "/home/labsha/mail/record" doesn't exist. Create? (y/n) [y]: I get this whether or not ~/mail/record actually exists. If I say No: [Find of folder outside context: /home/labsha/mail/record] [Fcc of message rejected] Pine doesn't send the message, and dumps me back in the compose screen. If I say Yes, and ~/mail/record exists, I get: [Can't create folder /home/labsha/mail/record: folder already exists] Again, pine doesn't send the message, and dumps me back in the compose screen. If I say Yes and ~/mail/ record doesn't exist, I then get: [Find of folder outside context: /home/labsha/mail/record] [Message sent, and copied to "/home/labsha/mail/record".] So, here are my problems: 1) Why can't pine seem to recognize ~/mail/record, even when it exists? a) Is it a problem with incompatible mail formats or something? I wouldn't think so, cuz I can read the same mail file in mail, mush, and pine with no problem, but...? b) What does "out of context" mean within "Find of folder outside context"? I get that when I try to get pine to recognize ~/mail/record without creating a new file. This seems to be the real problem. Any clues? 2) Why does rejecting the Fcc or inability to create ~/mail/record mean that pine cannot send the mail? With the recent/ongoing thread about sent-mail as well as several recent system modifications, it occurred to me that this would be a perfect time to ask Pine-Info and Answer-L. A couple of misc. related things: 1) I don't remember this happening before, so could it be related to the OS or the global pine setup (ie, related to whatever system changes have just happened)? 2) I would prefer that all my outgoing mail be in a single folder (~/mail/record, if possible), but I suppose renaming it sent-mail should theoretically avoid all my current problems. Does anyone know a better way to approach my situation? If someone could explain what pine is doing and why it is doing so, I would appreciate it. Also, if you know something better to do, please tell me. thanx, shy From owner-pine-info@cac.washington.edu Thu Feb 3 20:33:00 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14017; Thu, 3 Feb 94 20:33:00 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07627; Thu, 3 Feb 94 20:17:16 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07621; Thu, 3 Feb 94 20:17:15 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07510; Thu, 3 Feb 94 20:17:10 -0800 Date: Thu, 3 Feb 1994 20:17:10 -0800 (PST) From: David L Miller Subject: Re: Saving sent mail To: Shyela Aberman Cc: pine-info@cac.washington.edu, answer-l@emuvm1 In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Try setting "default-fcc=record". Some versions of pine prior to 3.89 had problems with fully qualified paths for the default-fcc. Your problems should also pretty well go away if you upgrade to Pine 3.89... Thanks for the report! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 3 Feb 1994, Shyela Aberman wrote: > > Hello Folks, > Working on a SunOS 5.3 (Sol2) system, I want to keep a copy of all > mail I send out. This is easy to do with mail/mush: I add "set record= > /home/labsha/mail/record" to my .mailrc. However, I have been having > some problems doing the same thing with pine 3.85. I have modified my > .pinerc so that "default-fcc=/home/labsha/mail/record", and I have > come across some problems when I try to send mail from pine that > puzzle me. When I try to send mail I get the following message: > > Folder "/home/labsha/mail/record" doesn't exist. Create? (y/n) [y]: > > I get this whether or not ~/mail/record actually exists. If I say No: > > [Find of folder outside context: /home/labsha/mail/record] > [Fcc of message rejected] > > Pine doesn't send the message, and dumps me back in the compose screen. > If I say Yes, and ~/mail/record exists, I get: > > [Can't create folder /home/labsha/mail/record: folder already exists] > > Again, pine doesn't send the message, and dumps me back in the compose > screen. If I say Yes and ~/mail/ record doesn't exist, I then get: > > [Find of folder outside context: /home/labsha/mail/record] > [Message sent, and copied to "/home/labsha/mail/record".] > > So, here are my problems: > 1) Why can't pine seem to recognize ~/mail/record, even when it exists? > a) Is it a problem with incompatible mail formats or something? I > wouldn't think so, cuz I can read the same mail file in mail, mush, > and pine with no problem, but...? > b) What does "out of context" mean within "Find of folder outside > context"? I get that when I try to get pine to recognize ~/mail/record > without creating a new file. This seems to be the real problem. Any > clues? > 2) Why does rejecting the Fcc or inability to create ~/mail/record mean > that pine cannot send the mail? > > With the recent/ongoing thread about sent-mail as well as several recent > system modifications, it occurred to me that this would be a perfect time > to ask Pine-Info and Answer-L. A couple of misc. related things: > 1) I don't remember this happening before, so could it be related to the > OS or the global pine setup (ie, related to whatever system changes > have just happened)? > 2) I would prefer that all my outgoing mail be in a single folder > (~/mail/record, if possible), but I suppose renaming it sent-mail > should theoretically avoid all my current problems. Does anyone know > a better way to approach my situation? > > If someone could explain what pine is doing and why it is doing so, I > would appreciate it. Also, if you know something better to do, please > tell me. > > thanx, > shy > > > From owner-pine-info@cac.washington.edu Fri Feb 4 01:32:47 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16971; Fri, 4 Feb 94 01:32:47 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06501; Fri, 4 Feb 94 00:54:55 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shiva1.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06495; Fri, 4 Feb 94 00:54:54 -0800 Received: by shiva1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18355; Fri, 4 Feb 94 00:54:49 -0800 Date: Fri, 4 Feb 1994 00:54:48 -0800 (PST) From: Terry Gray Subject: Re: Suggestions To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Andrew, Barry, Jack, Michael, Mike, John, et al: Here are a few reactions and comments from one of the culprits... > We wanted to have something that was simple to use, required no user > configuration... And it's still true that Pine *requires* no user configuration. Erase your .pinerc (and maybe even your pine.conf) and you can verify this for yourself. In fact, you'll see a Pine that looks remarkably similar to the very earliest versions, except that it has more consistency across screens. Even PC-Pine users never need edit their PINERC if they want a minimalist Pine (or, as suggested, "pinelet"). That's because the first time they run it, PC-Pine will prompt them for the configuration essentials (name, imap server, smtp server). One of the reasons we have not made the "Pine Configuration" screen our highest priority is that it has always been our view that the config options were there primarily for those who were not intimidated by them. > Now creeping featurism threatens to swallow Pine whole. > Pine is now complicated. Note that some of you want the options to be *less* accessible, if not go away altoghether, while others actually want them to be *more* accessible (easier to configure.) We won't talk about those of you who want lots *more* options, but you know who you are! :) Remember, these creeping features that have swallowed Pine are indeed *options*; those who do not explicitly turn them on, do not suffer any added complexity. (Exception: if the system admin turns them on in the pine.conf, well... that's a local policy decision. Also, the new status indicators in the Index, + and A, are not configurable.) > How about a menu-driven configuration built into pine with documentation > to explain what the various options mean. Planned. But I suppose we need to make its presence configurable, in order to keep both the "no features" and "easier features" camps happy :) > In order to satisfy both "normal" users and power users I would prefer > to have a "User Level" command with options "beginner" and "advanced" Old timers will recall that we used to do just that: there was a normal/basic mode and an "old-growth"/advanced mode. However, we found that many options are a question of personal taste, and did not relate to experience level, so this model broke down. There is still a novice mode, of course: it's what you get if you don't turn on any options! > User support gets harder as more arcane features/options are added. > Instead of having 20 advisors who know all about Pine 3.0x, we're unlikely > to have more than 5 who'll get to grips with all of Pine 3.8x. Could we get those 5 to help us with pine-bugs support? :) Mike's point is valid, of course, but on the other hand each site needs to define it's own base configuration and level of support. Suppose that there was a "pinelet"... a base version that had no options. A user asks "How can I do xxx in Pinelet?" The support staff says "Sorry, it can't be done in Pinelet." whereas the corresponding answer for regular Pine might be: "Sorry, that feature is not available in the Pine configuration supported at this site". (Or they could say "RTFM"...) But if folks really want a "pinelet", you can have it right now! Just have "pinelet" be an alias for "pine -p /usr/local/dummy.pinerc" and presto. no personal pinerc and no user-settable options! Just good-old, simple Pine :) (PC users wanting a "pinelet" must simply use some self-discipline and *pretend* they don't have a PINERC...) > ... and which (one of early Pine's proud boasts) didn't need > paper documentation because it was so small. Well, with Pine option configuration disabled as above, that's probably still true, too! (At least as true as it ever was... documentation is a funny thing. Some people will use online but not hard-copy, some are just the opposite, and the vast majority refuse to use either! :) -teg From owner-pine-info@cac.washington.edu Fri Feb 4 01:50:27 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17163; Fri, 4 Feb 94 01:50:27 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06793; Fri, 4 Feb 94 01:27:38 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06787; Fri, 4 Feb 94 01:27:34 -0800 Received: from ursa.cus.cam.ac.uk [131.111.8.6] (TAP id = ph10) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pSMp2-000BzUC; Fri, 4 Feb 94 09:27 GMT Date: Fri, 4 Feb 1994 09:27:52 +0000 (GMT) From: Philip Hazel Subject: Re: Suggestions To: "A. Hilborne" Cc: "Gregory J. Atchity" , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1748 > Pine should be frozen at it's current state of development, or preferably a > couple of states back, where the config file was simpler and there were no > stubs for "coming" features visible to the user. > > This version of Pine can either retain the name, or become, say, "Pinelet." > Perhaps someone out there can think of a suitable diminutive name. The > version we have now can then move on until it suits all us power users out > here. Only bug fixes would be back-grafted onto Pinelet. > > What do you think? I don't think this is a good idea. There would be confusion between the two products, and one wouldn't be able to remember which did what. We already have problems with the "novice" vs "old growth" modes in Pine. Scenario: A user phones up with a problem about the message. Adviser asks "What are the full headers?". User can't see all the headers, of course. Adviser says "press h to see the full headers". Users presses h. Nothing happens, because h is a "power user feature". A messy interchange follows. I see no reason why Pine shouldn't have a number of configurable options, provided that the defaults are all suited for the novice, and there is an easy-to-use configuration screen with lots of explanation for each option, (a paragraph rather than a couple of words), so it is simple to make changes. Users will advance as time progresses. Novices become power users in time. It's simpler if they can just start to use additional features of the same, familiar product. Philip -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Fri Feb 4 03:50:13 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18597; Fri, 4 Feb 94 03:50:13 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10530; Fri, 4 Feb 94 03:34:00 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA10524; Fri, 4 Feb 94 03:33:53 -0800 Received: from localhost by mail.swip.net (8.6.4/2.01) id MAA29168; Fri, 4 Feb 1994 12:33:50 +0100 Received: by datan.sk.uppsala.se (4.1/Uppsala-930825-1) id AA02969; Fri, 4 Feb 94 12:32:41 +0100 Date: Fri, 4 Feb 94 12:32:41 +0100 Message-Id: <9402041132.AA02969@datan.sk.uppsala.se> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE From: Klaus Zeuge To: dlm@cac.washington.edu Cc: sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: David L Miller's message of Thu, 3 Feb 1994 08:40:00 -0800 (PST) Subject: 8-bit characters in the header. >Date: Thu, 3 Feb 1994 08:40:00 -0800 (PST) >From: David L Miller >Actually it's not that controversial, RFC1522 defines a way to represent >non-ASCII characters in headers. Pine will support this eventually, but >probably not in the next release. Too bad. It would make Pine really shine. It's bit hard to explain to someone named Bj=F6rn =E5sberg why he can use his name in the message body, but not in the TO, FROM etc fields. From owner-pine-info@cac.washington.edu Fri Feb 4 03:50:13 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18599; Fri, 4 Feb 94 03:50:13 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07413; Fri, 4 Feb 94 03:30:54 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dir.bris.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07400; Fri, 4 Feb 94 03:30:43 -0800 Received: from adm1.bristol.ac.uk by dir.bris.ac.uk with SMTP (PP) id <03328-0@dir.bris.ac.uk>; Fri, 4 Feb 1994 11:30:10 +0000 Date: Fri, 4 Feb 1994 11:30:48 +0000 (GMT) From: Dave King Reply-To: Dave King Subject: Re: Suggestions To: Philip Hazel Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Apologies for yet another suggestion (which may have been made before), but if "pine.conf" settings (when set) took precendence over ".pinerc" settings this would give sites an opportunity to setup Pine to suit their user community. This would allow sites to: 1. Take advantage of new Pine releases (to overcome possible bugs). 2. Control the release of new features to the user community. 3. Block possibly undesireable features ("Update" and enable-suspend). 4. Fix variables such as "user-domain", and possibly "news-server", etc. If this approach was adopted, Pine would need to clearly inform the user when a user configured option has been disabled if the user sets it in their .pinerc file. As an example, I currently have the bounce and zoom commands disabled in pine.conf to avoid user confusion, but will make them available when they are implemented. Is the "pine.conf takes precedence over .pinerc" the perfect solution? Dave ------------------------------------------------------------------- Dave King, Admin. Computing Services Manager, University of Bristol Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) From owner-pine-info@cac.washington.edu Fri Feb 4 04:25:21 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19195; Fri, 4 Feb 94 04:25:21 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07760; Fri, 4 Feb 94 04:08:13 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from terminus.cs.umb.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07754; Fri, 4 Feb 94 04:08:10 -0800 Received: by terminus.cs.umb.edu id AA05490 (5.65c/IDA-1.4.4); Fri, 4 Feb 1994 07:07:02 -0500 Date: Fri, 4 Feb 1994 07:07:02 -0500 From: Robert Morris Message-Id: <199402041207.AA05490@terminus.cs.umb.edu> To: Klaus.Zeuge@sk.uppsala.se Cc: dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: <9402041132.AA02969@datan.sk.uppsala.se> (message from Klaus Zeuge on Fri, 4 Feb 94 12:32:41 +0100) Subject: Re: 8-bit characters in the header. Reply-To: ram@cs.umb.edu >>>>> "Klaus" == Klaus Zeuge writes: >> Date: Thu, 3 Feb 1994 08:40:00 -0800 (PST) From: David L Miller >> >> Actually it's not that controversial, RFC1522 defines a way to >> represent non-ASCII characters in headers. Pine will support this >> eventually, but probably not in the next release. > Too bad. It would make Pine really shine. It's bit hard to explain > to someone named Bj=F6rn =E5sberg why he can use his name in the > message body, but not in the TO, FROM etc fields. Nah, it's not so hard to explain. RFC822 was written in 1982. The Atlantic Ocean wasn't discovered until 1991, and the Pacific Ocean a year later. Latin America still hasn't been discovered, I think. Hah,hah, only serious. Bob Morris From owner-pine-info@cac.washington.edu Fri Feb 4 04:54:39 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19554; Fri, 4 Feb 94 04:54:39 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11030; Fri, 4 Feb 94 04:33:11 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cheviot.ncl.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11017; Fri, 4 Feb 94 04:31:45 -0800 Received: from (scawdell.ncl.ac.uk) by cheviot.ncl.ac.uk id (5.65cVUW/NCL-CMA.1.35 for ) with SMTP; Fri, 4 Feb 1994 12:31:13 GMT Date: Fri, 4 Feb 1994 12:31:05 +0000 (GMT) From: "A. Hilborne" Subject: Re: Suggestions To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I must say I am impressed by the level of debate which has come about as a result of my previous message. To answer all the messages I have seen so far... 0. I should have started off by thanking the UoW crew for giving us Pine at all. I'd like to make amends by offering a VERY BIG THANKYOU here. 1. I think that a reasonable config/preference screen would remove a lot of the problems with the present config file. 2. The possibility that "Pine-out-of-the-box" should use a simple config file, with a "power-user option" to create and use a more complex one sounds attractive, but would clearly be considerable work. 3. I shall definitely bear in mind the suggestion that "Pinelet" be something like "pine -p ." 4. I accept the argument that Pine and "Pinelet" should not be developed separately. 5. The suggestion that pine.conf override .pinerc also sounds interesting, but there should be a .pinerc option to override the override! Many mature UNIX programs do this sort of thing (UCB Mail, EMACS, nn, ...) but normally it is only a command-line option. This a pain because it makes the user have his own wrapper when he hardly needs one. 6. Documentation. If a reasonable paper manual appears, it should hive off all the advanced options to a _very_ separate section. -- Andrew M. Hilborne Andrew.Hilborne@newcastle.ac.uk Computing Service Tel: +44 91 222 8226 (direct) University of Newcastle upon Tyne, UK. +44 91 222 8039 (Comp Service office) From owner-pine-info@cac.washington.edu Fri Feb 4 07:08:55 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20908; Fri, 4 Feb 94 07:08:55 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12053; Fri, 4 Feb 94 06:49:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12043; Fri, 4 Feb 94 06:49:04 -0800 Received: from quinag.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <16890-0@ppsw2.cam.ac.uk>; Fri, 4 Feb 1994 14:48:40 +0000 Date: Fri, 4 Feb 1994 14:46:32 GMT From: Barry Landy Subject: Re: Suggestions To: Dave King Cc: Philip Hazel , pine-info@cac.washington.edu X-Sender: bl10@cus.cam.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sounds to me like three levels are needed: pine.conf - naive users standard defaults .pinerc - upgrades for less naive users (settable by editor or online config system) pine.absolute - local settings that cannot be over-ridden in any way (and this does not make things more complicated for the simple users, but does allow the system managers to lock out things that they dont want experimented with or altered). On Fri, 4 Feb 1994, Dave King wrote: > Apologies for yet another suggestion (which may have been made before), > but if "pine.conf" settings (when set) took precendence over ".pinerc" > settings this would give sites an opportunity to setup Pine to suit their > user community. This would allow sites to: > > 1. Take advantage of new Pine releases (to overcome possible bugs). > 2. Control the release of new features to the user community. > 3. Block possibly undesireable features ("Update" and enable-suspend). > 4. Fix variables such as "user-domain", and possibly "news-server", etc. > > If this approach was adopted, Pine would need to clearly inform the user > when a user configured option has been disabled if the user sets it in > their .pinerc file. > > As an example, I currently have the bounce and zoom commands disabled in > pine.conf to avoid user confusion, but will make them available when they > are implemented. > > Is the "pine.conf takes precedence over .pinerc" the perfect solution? > ------------------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 223 334600 Head of Systems and Development Direct line: +44 223 334713 University of Cambridge Computing Service New Museums Site Email:Barry.Landy@ucs.cam.ac.uk Pembroke Street, Cambridge CB2 3QG From owner-pine-info@cac.washington.edu Fri Feb 4 11:47:28 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28107; Fri, 4 Feb 94 11:47:28 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16260; Fri, 4 Feb 94 11:28:08 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from Krypton.Mankato.MSUS.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16252; Fri, 4 Feb 94 11:28:05 -0800 Received: from localhost (hayden@localhost) by krypton.mankato.msus.edu (8.6.4/8.6.4) id NAA09831; Fri, 4 Feb 1994 13:32:31 -0600 Date: Fri, 4 Feb 1994 13:32:29 -0600 (CST) From: "Robert A. Hayden" Subject: Re: Suggestions To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 4 Feb 1994, Barry Landy wrote: > Sounds to me like three levels are needed: > > pine.conf - naive users standard defaults > .pinerc - upgrades for less naive users (settable by editor or online > config system) > pine.absolute - local settings that cannot be over-ridden in any way > > (and this does not make things more complicated for the simple users, but > does allow the system managers to lock out things that they dont want > experimented with or altered). I dont' like it. Admins I know are very paranoid. As a matter of fact, when I installed filter and started sorting my mail into different subject-related mailboxes, I had to spend an hour explaining to the admin exactly what it was I was doing, and even then she only grudingly agree to allow me to do it because I get so much mail. All it would take is an unapproachable and uninformed admin and users have all advanced options locked out, which turns around and makes pine useless. I'd simply have it so that pine.conf is the default, and then users who know what they are doing modify their .pinerc for their specific needs. Of course, since I'm not an admin, I'm just reporting on what I;d like as a user (and what I fear as a user). ____ Robert A. Hayden <=> hayden@krypton.mankato.msus.edu \ /__ -=-=-=-=- <=> -=-=-=-=- \/ / Finger for Geek Code Info <=> In the United States, they \/ Finger for PGP 2.3a Public Key <=> first came for us in Colorado... -=-=-=-=-=-=-=- (GEEK CODE 1.0.1) GAT d- -p+(---) c++(++++) l++ u++ e+/* m++(*)@ s-/++ n-(---) h+(*) f+ g+ w++ t++ r++ y+(*) From owner-pine-info@cac.washington.edu Fri Feb 4 12:11:02 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28927; Fri, 4 Feb 94 12:11:02 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12663; Fri, 4 Feb 94 11:53:06 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from senta.top.cis.syr.EDU by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12657; Fri, 4 Feb 94 11:53:04 -0800 Message-Id: <9402041953.AA12657@mx2.cac.washington.edu> Date: Fri, 4 Feb 94 14:51:19 EST From: Leonard@top.cis.syr.edu To: pine-info@cac.washington.edu Subject: pine with MMDF There's a driver for MMDF in the c-client directory and the docs mention support for MMDF, but I can't find anything that indicates how to set this up. Does anyone have any experience with a pine/MMDF combination? Steve Leonard Northeast Parallel Architecture Center at Syracuse University e-mail: leonard@top.cis.syr.edu From owner-pine-info@cac.washington.edu Fri Feb 4 12:29:36 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29334; Fri, 4 Feb 94 12:29:36 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12985; Fri, 4 Feb 94 12:13:53 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12979; Fri, 4 Feb 94 12:13:50 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01464; Fri, 4 Feb 94 12:13:28 -0800 Received: by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA09835; Fri, 4 Feb 94 12:13:18 -0800 Date: Fri, 4 Feb 1994 12:13:17 -0800 (PST) From: Mark Crispin Subject: Re: 8-bit characters in the header. To: Klaus Zeuge Cc: dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: <9402041132.AA02969@datan.sk.uppsala.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-2022-JP Content-Transfer-Encoding: QUOTED-PRINTABLE > Too bad. It would make Pine really shine. It's bit hard to explain to > someone named Bj=F6rn =E5sberg why he can use his name in the message > body, but not in the TO, FROM etc fields. Klaus - Just to sensitize people to the problem, on my screen that name appeared=20 as: "Bj", a filled-in square, "n ", a Chinese character meaning a kind of= =20 shell, and "berg". My screen is set up with the Japanese character set. Fortunately, Pine was able to recognize that it may not display the text=20 properly, and warned me of that fact (hey, it's better than refusing to=20 display it at all, which earlier versions did!). However, it's important= =20 to realize that all the world isn't ISO-8859. Pine *will* support non-ASCII characters in headers, but you should=20 always have a reasonable 7-bit form of your name for the benefit of those= =20 who can't display European characters. From owner-pine-info@cac.washington.edu Fri Feb 4 13:10:11 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00400; Fri, 4 Feb 94 13:10:11 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA17346; Fri, 4 Feb 94 12:43:37 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from emoryu1.cc.emory.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA17342; Fri, 4 Feb 94 12:43:34 -0800 Received: from dooley.cc.emory.edu by emoryu1.cc.emory.edu (5.65/Emory_cc.3.4.16) via SMTP id AA03491 ; Fri, 4 Feb 94 15:43:31 -0500 Return-Path: labsha@unix.cc.emory.edu Date: Fri, 4 Feb 1994 15:37:06 -0500 (EST) From: Shyela Aberman Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Folks, Has anyone tried to compile Pine 3.89 on a SunOS 5.3 machine (sol2)? I have, and have gotten the following compilation errors: Making Pine. cc -DSV4 -g -DDEBUG -c addrbook.c "/usr/include/unistd.h", line 171: identifier redeclared: rename "addrbook.c", line 200: warning: semantics of ">" change in ANSI C; use explicit cast "addrbook.c", line 204: warning: semantics of ">" change in ANSI C; use explicit cast "addrbook.c", line 1349: cannot recover from previous errors cc: acomp failed for addrbook.c *** Error code 1 make: Fatal error: Command failed for target `addrbook.o' The errors about semantics aren't a problem near as I can tell; the c-client, pico, mtest, and imapd have them and compile successfully. What I think the problem is, but can't find where to fix is the "identifier redeclared: rename". I've searched all the source code for declarations of rename that would mess with unistd.h, but pico and the c-client seem to be the only ones. Since I'm not familiar at all with the code, does anyone out there (hello, pine development team! :-) have any idea where to look or what to do to fix this? thanx, and I hope this isn't a FAQ or something, shy P.S. cc doesn't seem to be the usual /usr/bin/cc, but is /opt/SUNWspro/bin/cc and thus the package uses cc5.sol. /----------------------------------+-----------------------------------------\ |Shyela Aberman, Emory University -|- Consultant, Exec. Editor, CS Major, | | 404-712-2229 -|- Martial Artist, and Good Kisser | |----------------------------------+-----------------------------------------| |INTERNET: labsha@emory.edu OTHER: ap466@freenet.hsc.colorado.edu | |BITNET: labsha@emoryu1 UUCP: {rutgers,gatech}!emoryu1!labsha | \----------------------------------------------------------------------------/ From owner-pine-info@cac.washington.edu Fri Feb 4 13:14:32 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00574; Fri, 4 Feb 94 13:14:32 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13339; Fri, 4 Feb 94 12:45:23 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ees1a0.engr.ccny.cuny.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13333; Fri, 4 Feb 94 12:45:19 -0800 Received: by ees1a0.engr.ccny.cuny.edu (4.1/SMI-4.1) id AA04806; Fri, 4 Feb 94 15:44:13 EST Date: Fri, 4 Feb 1994 15:26:37 -0500 (EST) From: Dan Schlitt Subject: Re: Suggestions To: "Robert A. Hayden" Cc: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would suggest to you that there are already the three levels that some folks want. There is the global configuration file, the individual configuration file and there are the compilation options. But the individual ought to be able to override the global configuration on most things. One should remember that on most unix systems MUAs are user level programs that don't require privilege. With docile users (or in a rigid corporate environment) you may be able to impose strict rules. But in many places anyone can bring in their own MUA and use it. This means that restrictions on the configuration of MUAs better have good rationales and that the global configuration is primarily to make it convenient for most users to use the program without having to worry about the configuration. /dan Dan Schlitt School of Engineering Computer Systems dan@ee-mail.engr.ccny.cuny.edu City College of New York (212)650-6760 New York, NY 10031 From owner-pine-info@cac.washington.edu Fri Feb 4 13:38:00 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01077; Fri, 4 Feb 94 13:38:00 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18015; Fri, 4 Feb 94 13:13:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18009; Fri, 4 Feb 94 13:13:02 -0800 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18109; Fri, 4 Feb 94 13:13:00 -0800 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 04 Feb 94 22:12:22+0100 Date: 04 Feb 94 22:12:22+0100 From: Shyela Aberman Message-Id: <564270*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine Info From owner-pine-info@cac.washington.edu Fri Feb 4 13:53:07 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01551; Fri, 4 Feb 94 13:53:07 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18320; Fri, 4 Feb 94 13:33:31 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA18314; Fri, 4 Feb 94 13:33:29 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01548; Fri, 4 Feb 94 13:33:21 -0800 Received: by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA10124; Fri, 4 Feb 94 13:33:13 -0800 Date: Fri, 4 Feb 1994 13:33:11 -0800 (PST) From: Mark Crispin Subject: Re: pine with MMDF To: Leonard@top.cis.syr.edu Cc: pine-info@cac.washington.edu In-Reply-To: <9402041953.AA12657@mx2.cac.washington.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 4 Feb 1994 Leonard@top.cis.syr.edu wrote: > There's a driver for MMDF in the c-client directory and the docs > mention support for MMDF, but I can't find anything that indicates > how to set this up. Does anyone have any experience with a pine/MMDF > combination? Hello. The c-client MMDF support is contributed code, and there are various rumors about whether or not it really works. I think that it needs some hacker attention to knock it into shape. We don't use MMDF here, so it's somewhat difficult for us to fix it. From owner-pine-info@cac.washington.edu Fri Feb 4 16:45:25 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07026; Fri, 4 Feb 94 16:45:25 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21257; Fri, 4 Feb 94 16:21:51 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from UCS.ORST.EDU by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21249; Fri, 4 Feb 94 16:21:48 -0800 Received: by ucs.orst.edu (5.57/fma-120691); id AA12153; Fri, 4 Feb 94 16:21:45 -0800 Message-Id: <9402050021.AA12153@ucs.orst.edu> To: pine-info@cac.washington.edu Cc: crowede@ucs.orst.edu Subject: IMAP or PC-PINE problem? Date: Fri, 04 Feb 94 16:21:45 -0800 From: bellc@ucs.orst.edu X-Mts: smtp We have IMAP 3.2 and PC-PINE 3.89. When trying to save a message to a folder on the mainframe (the IMAP server) is says "IMAP error: APPEND request unknown:" then "Save Request Unknown:". It works fine if you save them on the local PC. I had assumed it was a problem with the IMAP server, however another IMAP client "Mailstrom" (a mac client) will save folders on the mainframe just fine. Anyone have any helpful hints? Randy Bell ---------------------------------------------------------------------- User Services, University Computing Services Email: bellc@ucs.orst.edu Phone: (503) 737-4267 From owner-pine-info@cac.washington.edu Fri Feb 4 17:09:56 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07785; Fri, 4 Feb 94 17:09:56 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21645; Fri, 4 Feb 94 16:49:50 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21639; Fri, 4 Feb 94 16:49:48 -0800 Received: by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA01747; Fri, 4 Feb 94 16:49:43 -0800 Date: Fri, 4 Feb 1994 16:49:43 -0800 (PST) From: Mark Crispin Subject: Re: IMAP or PC-PINE problem? To: bellc@ucs.orst.edu Cc: pine-info@cac.washington.edu, crowede@ucs.orst.edu In-Reply-To: <9402050021.AA12153@ucs.orst.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 4 Feb 1994 bellc@ucs.orst.edu wrote: > We have IMAP 3.2 and PC-PINE 3.89. When trying to save a message to a > folder on the mainframe (the IMAP server) is says "IMAP error: APPEND > request unknown:" then "Save Request Unknown:". It works fine if you > save them on the local PC. I had assumed it was a problem with the > IMAP server, however another IMAP client "Mailstrom" (a mac client) will > save folders on the mainframe just fine. It appears that you are running the old Stanford IMAP2 server which is based on RFC-1064. You need to have an IMAP2bis server, such as the UW IMAP server, in order to save messages on the server from PC Pine. Note that the Stanford IMAP2 server uses the COPY command, and thus can only copy messages from one folder on the server to the other. IMAP2bis servers have the more general APPEND command (which is what PC Pine uses), so the source and destination can be different systems. From owner-pine-info@cac.washington.edu Fri Feb 4 17:18:22 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08050; Fri, 4 Feb 94 17:18:22 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21693; Fri, 4 Feb 94 16:52:23 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cd1.lrz-muenchen.de by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21687; Fri, 4 Feb 94 16:52:17 -0800 Received: from sunserver.lrz-muenchen.de by cd1.lrz-muenchen.de id SMTP-0012d52ee03009951; Sat, 5 Feb 94 01:53:23 +0100 Received: from sun3.lrz-muenchen.de by sunserver.lrz-muenchen.de (4.1/SMI-4.1) id AA14061; Sat, 5 Feb 94 01:52:11 +0100 Received: by sun3.lrz-muenchen.de (4.1/SMI-4.1) id AA02394; Sat, 5 Feb 94 01:52:10 +0100 Date: Sat, 5 Feb 1994 01:52:10 +0100 (MET) From: Michael Wolf Reply-To: Michael Wolf Subject: Re: 8-bit characters in the header. To: Mark Crispin Cc: Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 4 Feb 1994, Mark Crispin wrote: > Klaus - > > ........................................ .However, it's important > to realize that all the world isn't ISO-8859. > >............................................... , but you should >always have a reasonable 7-bit form of your name for the benefit of those > who can't display European characters. > I agree. Klaus may wish to use non ASCII characters only locally. But I also think that we all should try to keep internet messages in *English*. In addition, even many (not all) computer applications should remain in English and restrict themselves to ASCII. Michael From owner-pine-info@cac.washington.edu Fri Feb 4 17:27:40 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08337; Fri, 4 Feb 94 17:27:40 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21994; Fri, 4 Feb 94 17:05:33 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21985; Fri, 4 Feb 94 17:05:29 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12475; Fri, 4 Feb 94 17:04:41 -0800 Date: Fri, 4 Feb 1994 17:04:40 -0800 (PST) From: David L Miller Subject: Re: IMAP or PC-PINE problem? To: bellc@ucs.orst.edu Cc: pine-info@cac.washington.edu, crowede@ucs.orst.edu In-Reply-To: <9402050021.AA12153@ucs.orst.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Randy, IMAP 3.2(85) is a very ancient version of imapd. You should download the latest version from ftp.cac.washington.edu. The source is in the file mail/imap.tar.Z or there are selected binaroes in the mail/unix-bin directory. Thanks for the report! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 4 Feb 1994 bellc@ucs.orst.edu wrote: > > We have IMAP 3.2 and PC-PINE 3.89. When trying to save a message to a > folder on the mainframe (the IMAP server) is says "IMAP error: APPEND > request unknown:" then "Save Request Unknown:". It works fine if you > save them on the local PC. I had assumed it was a problem with the > IMAP server, however another IMAP client "Mailstrom" (a mac client) will > save folders on the mainframe just fine. > > Anyone have any helpful hints? > > Randy Bell > ---------------------------------------------------------------------- > User Services, University Computing Services > Email: bellc@ucs.orst.edu Phone: (503) 737-4267 From owner-pine-info@cac.washington.edu Sat Feb 5 11:23:49 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18691; Sat, 5 Feb 94 11:23:49 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28639; Sat, 5 Feb 94 11:11:45 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bootes.cus.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28633; Sat, 5 Feb 94 11:11:42 -0800 Received: from apus.cus.cam.ac.uk [131.111.8.2] (TAP id = root) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pSs6S-000BzKC; Sat, 5 Feb 94 18:51 GMT Received: by apus.cus.cam.ac.uk (Smail-3.1.28.1 #110) id m0pSs6Q-0004Y0C; Sat, 5 Feb 94 18:51 GMT Date: Sat, 5 Feb 1994 18:51:34 +0000 (GMT) From: Barry Landy Subject: Re: Suggestions To: Dan Schlitt Cc: "Robert A. Hayden" , Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII True on many but not all systems. Some of us (and not just me!) run mail systems on restricted shell unix systems where the usrs do not have the freedom to install their own programs, and where we have to do a lot of work to keep them out of things we dont want them to have (shell busters like calling your own editor, for example). Compilation options are fine when they exist, but if they dont we are down to hacking or nagging the developers. On Fri, 4 Feb 1994, Dan Schlitt wrote: > I would suggest to you that there are already the three levels that some > folks want. There is the global configuration file, the individual > configuration file and there are the compilation options. But the > individual ought to be able to override the global configuration on most > things. > > One should remember that on most unix systems MUAs are user level programs > that don't require privilege. With docile users (or in a rigid corporate > environment) you may be able to impose strict rules. But in many places > anyone can bring in their own MUA and use it. This means that > restrictions on the configuration of MUAs better have good rationales and > that the global configuration is primarily to make it convenient for most > users to use the program without having to worry about the configuration. > > /dan > > Dan Schlitt School of Engineering Computer Systems > dan@ee-mail.engr.ccny.cuny.edu City College of New York > (212)650-6760 New York, NY 10031 > > > > ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Sun Feb 6 17:27:45 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04166; Sun, 6 Feb 94 17:27:45 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03413; Sun, 6 Feb 94 17:13:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sunic.sunet.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03407; Sun, 6 Feb 94 17:13:38 -0800 Received: from Minsk.DoCS.UU.SE by sunic.sunet.se (8.6.4/2.03) id CAA16305; Mon, 7 Feb 1994 02:05:59 +0100 Received: by Minsk.DoCS.UU.SE (Sun-4/630, SunOS 4.1.2) with sendmail 5.61-bind 1.5+ida/ICU/DoCS id AA00124; Mon, 7 Feb 94 02:05:55 +0100 Date: Mon, 7 Feb 94 02:05:55 +0100 Message-Id: <9402070105.AA00124@Minsk.DoCS.UU.SE> X-Zippy-Proclaims: The PINK SOCKS were ORIGINALLY from 1952!! But they went to MARS around 1953!! X-Dogma: 36 >> 32 From: Klaus Zeuge X-Phone: (int) +46-18-271064 X-Fax: (int) +46-18-271031 To: Michael.Wolf@lrz-muenchen.de Cc: mrc@Panda.COM, Klaus.Zeuge@SK.Uppsala.SE, dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Michael Wolf's message of Sat, 5 Feb 1994 01:52:10 +0100 (MET) Subject: 8-bit characters in the header. >Date: Sat, 5 Feb 1994 01:52:10 +0100 (MET) >From: Michael Wolf > > >I agree. Klaus may wish to use non ASCII characters only locally. But I >also think that we all should try to keep internet messages in *English*. >In addition, even many (not all) computer applications should remain in >English and restrict themselves to ASCII. Why? Arent't you supposed to *use* email among actual (physical) *PEOPLE* ? From owner-pine-info@cac.washington.edu Sun Feb 6 17:30:20 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04226; Sun, 6 Feb 94 17:30:20 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08406; Sun, 6 Feb 94 17:09:38 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sunic.sunet.se by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA08400; Sun, 6 Feb 94 17:09:31 -0800 Received: from Minsk.DoCS.UU.SE by sunic.sunet.se (8.6.4/2.03) id CAA16672; Mon, 7 Feb 1994 02:09:29 +0100 Received: by Minsk.DoCS.UU.SE (Sun-4/630, SunOS 4.1.2) with sendmail 5.61-bind 1.5+ida/ICU/DoCS id AA00131; Mon, 7 Feb 94 02:09:28 +0100 Date: Mon, 7 Feb 94 02:09:28 +0100 Message-Id: <9402070109.AA00131@Minsk.DoCS.UU.SE> X-Zippy-Proclaims: UH-OH!! I put on ``GREAT HEAD-ON TRAIN COLLISIONS of the 50's'' by mistake!!! X-Dogma: 36 >> 32 From: Klaus Zeuge X-Phone: (int) +46-18-271064 X-Fax: (int) +46-18-271031 To: mrc@Panda.COM Cc: Klaus.Zeuge@SK.Uppsala.SE, dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Mark Crispin's message of Fri, 4 Feb 1994 12:13:17 -0800 (PST) Subject: 8-bit characters in the header. >Date: Fri, 4 Feb 1994 12:13:17 -0800 (PST) >From: Mark Crispin >shell, and "berg". My screen is set up with the Japanese character set. Hm, my message was encoded using ISO 8859-1. My message SAID so. How come you tried to read it in JAPANESE? I think (while not being SURE) there is a bug somewhere here. From owner-pine-info@cac.washington.edu Sun Feb 6 18:40:03 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04909; Sun, 6 Feb 94 18:40:03 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03747; Sun, 6 Feb 94 18:10:46 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA03741; Sun, 6 Feb 94 18:10:45 -0800 Received: from localhost by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA04353; Sun, 6 Feb 94 18:10:31 -0800 Date: Sun, 6 Feb 1994 18:00:46 -0800 (PST) From: Mark Crispin Subject: re: 8-bit characters in the header. To: Klaus Zeuge Cc: dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: <9402070109.AA00131@Minsk.DoCS.UU.SE> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 7 Feb 94 02:09:28 +0100, Klaus Zeuge wrote: > Hm, my message was encoded using ISO 8859-1. My message SAID so. How > come you tried to read it in JAPANESE? Yes, your message was encoded using 8859-1, and yes, I was warned that it was not likely to be displayed correctly. But my terminal was not capable of displaying 8859-1. It is only capable of displaying Japanese. > I think (while not being SURE) there is a bug somewhere here. Pine had the choice of displaying the 8859-1 in the Japanese character set (and hoping that there would be enough ASCII that I could make some sense of it), or it could refuse to display it at all. I claim that Pine did the right thing by giving me a warning, and then trying to show me something. The point is, not everyone can assume that every terminal in the world has 8859. It is Euro-centric to assume otherwise. Don't forget, there are more people who use East Asian characters than there are Europeans; if it came down to it, they out-number you. This is the underlying fault of the ``8-bit clean is enough'' idea. We all need to be very careful to make sure we have a match in character sets between sender and receiver and not make assumptions. If there is any question about the capabilities of the receiver's terminal, it is best to limit yourself to ASCII. From owner-pine-info@cac.washington.edu Mon Feb 7 04:05:36 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11136; Mon, 7 Feb 94 04:05:36 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06836; Mon, 7 Feb 94 03:44:39 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from sunic.sunet.se by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06830; Mon, 7 Feb 94 03:44:31 -0800 Received: from Minsk.DoCS.UU.SE by sunic.sunet.se (8.6.4/2.03) id MAA03149; Mon, 7 Feb 1994 12:44:29 +0100 Received: by Minsk.DoCS.UU.SE (Sun-4/630, SunOS 4.1.2) with sendmail 5.61-bind 1.5+ida/ICU/DoCS id AA17660; Mon, 7 Feb 94 12:44:27 +0100 Date: Mon, 7 Feb 94 12:44:27 +0100 Message-Id: <9402071144.AA17660@Minsk.DoCS.UU.SE> X-Zippy-Proclaims: I guess it was all a DREAM.. or an episode of HAWAII FIVE-O... X-Dogma: 36 >> 32 From: Klaus Zeuge X-Phone: (int) +46-18-271064 X-Fax: (int) +46-18-271031 To: MRC@CAC.Washington.EDU Cc: dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Mark Crispin's message of Sun, 6 Feb 1994 18:00:46 -0800 (PST) Subject: 8-bit characters in the header. >Date: Sun, 6 Feb 1994 18:00:46 -0800 (PST) >From: Mark Crispin >Yes, your message was encoded using 8859-1, and yes, I was warned that it was >not likely to be displayed correctly. But my terminal was not capable of >displaying 8859-1. It is only capable of displaying Japanese. OK, this is were I misunderstood you. I had gotten the impression you weren't being warned. >it), or it could refuse to display it at all. I claim that Pine did the right >thing by giving me a warning, and then trying to show me something. I agree. Still, I would like this mechanism used in the header also (well, actually I'm content with the real name part in the FROM, TO, CC etc fields). /Klaus From owner-pine-info@cac.washington.edu Mon Feb 7 04:13:51 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11243; Mon, 7 Feb 94 04:13:51 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06879; Mon, 7 Feb 94 03:52:08 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from snow.csi.cam.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA06873; Mon, 7 Feb 94 03:52:03 -0800 Received: from quinag.csi.cam.ac.uk by ppsw2.cam.ac.uk with SMTP-CAM (PP-6.0) as ppsw.cam.ac.uk id <19307-0@ppsw2.cam.ac.uk>; Mon, 7 Feb 1994 11:31:04 +0000 Date: Mon, 7 Feb 1994 11:28:54 GMT From: Barry Landy Subject: re: 8-bit characters in the header. To: Mark Crispin Cc: Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu X-Sender: bl10@cus.cam.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 6 Feb 1994, Mark Crispin wrote: > On Mon, 7 Feb 94 02:09:28 +0100, Klaus Zeuge wrote: > > Hm, my message was encoded using ISO 8859-1. My message SAID so. How > > come you tried to read it in JAPANESE? > > Yes, your message was encoded using 8859-1, and yes, I was warned that it was > not likely to be displayed correctly. But my terminal was not capable of > displaying 8859-1. It is only capable of displaying Japanese. > > > I think (while not being SURE) there is a bug somewhere here. > > Pine had the choice of displaying the 8859-1 in the Japanese character set > (and hoping that there would be enough ASCII that I could make some sense of > it), or it could refuse to display it at all. I claim that Pine did the right > thing by giving me a warning, and then trying to show me something. > > The point is, not everyone can assume that every terminal in the world has > 8859. It is Euro-centric to assume otherwise. > > Don't forget, there are more people who use East Asian characters than there > are Europeans; if it came down to it, they out-number you. This is the > underlying fault of the ``8-bit clean is enough'' idea. While that is true, it is also true that there are more Europeans than Americans, and since 8859 will also cope very well with N America, perhaps it is a better default? > > We all need to be very careful to make sure we have a match in character sets > between sender and receiver and not make assumptions. If there is any > question about the capabilities of the receiver's terminal, it is best to > limit yourself to ASCII. > Well and all but it is hard to know, especially if one is a naive sender of mail typing what to you are normal characters. On the general issue, the problem is not solved until ISOCODE/ISO 90646 comes into effect, but we will then all have to embrace the implications. ------------------------------------------------------------------------------- Barry Landy Computer Laboratory:+44 223 334600 Head of Systems and Development Direct line: +44 223 334713 University of Cambridge Computing Service New Museums Site Email:Barry.Landy@ucs.cam.ac.uk Pembroke Street, Cambridge CB2 3QG From owner-pine-info@cac.washington.edu Mon Feb 7 05:06:59 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11705; Mon, 7 Feb 94 05:06:59 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12219; Mon, 7 Feb 94 04:46:55 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from cd1.lrz-muenchen.de by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA12213; Mon, 7 Feb 94 04:46:26 -0800 Received: from sunserver.lrz-muenchen.de by cd1.lrz-muenchen.de id SMTP-0012d5636e7010634; Mon, 7 Feb 94 13:41:11 +0100 Received: from sun3.lrz-muenchen.de by sunserver.lrz-muenchen.de (4.1/SMI-4.1) id AA11228; Mon, 7 Feb 94 13:41:10 +0100 Received: by sun3.lrz-muenchen.de (4.1/SMI-4.1) id AA03231; Mon, 7 Feb 94 13:41:10 +0100 Date: Mon, 7 Feb 1994 13:41:09 +0100 (MET) From: Michael Wolf Subject: Re: 8-bit characters in the header. To: Klaus Zeuge Cc: pine-info@cac.washington.edu In-Reply-To: <9402070105.AA00124@Minsk.DoCS.UU.SE> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 7 Feb 1994, Klaus Zeuge wrote: > > >Date: Sat, 5 Feb 1994 01:52:10 +0100 (MET) > >From: Michael Wolf > > > > > >I agree. Klaus may wish to use non ASCII characters only locally. But I > >also think that we all should try to keep internet messages in *English*. > >................. > > Why? Arent't you supposed to *use* email among actual (physical) *PEOPLE* ? > Sure. But I would make a difference between local and international communications. It is important for us to understand each other. A good "tool" for this purpose is English. I am happy to have the possibility to communicate all over the world, even if I have some difficulties, with the language or with the character set. Michael From owner-pine-info@cac.washington.edu Mon Feb 7 05:18:34 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11783; Mon, 7 Feb 94 05:18:34 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07386; Mon, 7 Feb 94 04:56:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from dummy1.dur.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA07380; Mon, 7 Feb 94 04:56:34 -0800 Received: from venus.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <28490-0@dummy1.dur.ac.uk>; Mon, 7 Feb 1994 12:56:08 +0000 Received: from vega.dur.ac.uk by venus.dur.ac.uk; Mon, 7 Feb 94 12:56:06 GMT Date: Mon, 7 Feb 1994 12:56:02 +0000 (GMT) From: Barry Cornelius Subject: Re: Suggestions To: Pine Info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1478 On Sat, 5 Feb 1994, Barry Landy wrote: > True on many but not all systems. Some of us (and not just me!) run mail > systems on restricted shell unix systems where the usrs do not have the > freedom to install their own programs, and where we have to do a lot of > work to keep them out of things we dont want them to have (shell busters > like calling your own editor, for example). > > Compilation options are fine when they exist, but if they dont we are > down to hacking or nagging the developers. One change to Pine that we would like is to prevent the user from setting the user-domain and use-only-domain-name variables. It is inappropriate in our environment for users to change these. If they do, they send out messages that can't be replied to by the recipient. To use the terminology introduced above, I have "hacked" the code to give out a message if the user sets either of these variables. I was going ask the Pine development team if they could add a compilation option for this. Or it could instead be done by the third configuration file that others are suggesting. This is the file that overrides the user's settings of some variables. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Mon Feb 7 07:49:38 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13449; Mon, 7 Feb 94 07:49:38 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13115; Mon, 7 Feb 94 07:27:54 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from iris.phar.umich.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA13105; Mon, 7 Feb 94 07:27:42 -0800 Received: from raduga.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA20866; Mon, 7 Feb 94 10:24:50 -0500 Date: Mon, 7 Feb 1994 10:24:49 -0500 (EST) From: Jeff Traigle Reply-To: Jeff Traigle Subject: Pine/imapd and SGI weirdness To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'm having a small problem with the pre-authentication mechanism on my SGI clients and have been unable to determine the cause so far. Hopefully someone out there has some insight. Setup: SGI as mail/imap server, Sun as NIS server Problem: SGI clients insist on login/password to access the mail server. Hints: Suns and SGI mail/imap server have no problems with pre-authentication. Doesn't matter whether or not the passwd info is in NIS or local to machines. Configuration: l--------- 1 root sys 20 Jan 28 13:25 /etc/rimapd@ -> /usr/local/etc/imapd -rwxr-xr-x 1 root sys 549268 Feb 7 09:30 /usr/local/etc/imapd inetd.conf entry imap stream tcp nowait root /usr/local/etc/imapd imapd If anybody has experienced this or has any ideas about what might be causing it, I'd really appreciate the input. Other admins on campus who have similar setups tell me they don't have this problem, but I've been unable to determine differences in setups that would account for the difference in behavior (unless they aren't running 3.89 as I am trying to do). ============================================================================= | Jeff Traigle | Systems Administrator | University of Michigan | ============================================================================= | College of Pharmacy | Biophysics Research Division | ============================================================================= | Masters of Science in Computer Science and Engineering | ============================================================================= | Masters of Information and Library Studies | ============================================================================= From owner-pine-info@cac.washington.edu Mon Feb 7 09:49:25 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16884; Mon, 7 Feb 94 09:49:25 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09732; Mon, 7 Feb 94 09:20:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from castor.cc.utu.fi by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09726; Mon, 7 Feb 94 09:19:56 -0800 Received: from polaris.cc.utu.fi by utu.fi id <165514-2>; Mon, 7 Feb 1994 19:19:45 +0200 Date: Mon, 7 Feb 1994 19:19:43 +0200 From: Kari Sutela Subject: re: 8-bit characters in the header. To: Mark Crispin Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE On Mon, 7 Feb 1994, Mark Crispin wrote: > The point is, not everyone can assume that every terminal in the world ha= s > 8859. It is Euro-centric to assume otherwise. Ok, ok. Let's just change the suggestion to "please, allow pine to=20 use non-ASCII characters in the header by implementing the RFC which=20 describes how to do this without breaking any rules" :-) It has been=20 promised that pine will eventually do this and I'm satisfied. > We all need to be very careful to make sure we have a match in character = sets > between sender and receiver and not make assumptions. If there is any > question about the capabilities of the receiver's terminal, it is best to > limit yourself to ASCII. But I have a very hard job in explaining this to my 3000 users who HAVE a display which supports 8859-1 that they can't user =E4 and =F6 in subjects,= =20 when most of them just exchange email locally. Don't take me wrong, I=20 really appreciate the pine folks and I think that pine is great! This is= =20 just one relatively minor inconvenience. /KS From owner-pine-info@cac.washington.edu Mon Feb 7 09:57:21 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17045; Mon, 7 Feb 94 09:57:21 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14890; Mon, 7 Feb 94 09:39:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from iris.phar.umich.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA14884; Mon, 7 Feb 94 09:39:16 -0800 Received: from raduga.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA22615; Mon, 7 Feb 94 12:38:57 -0500 Date: Mon, 7 Feb 1994 12:38:57 -0500 (EST) From: Jeff Traigle Reply-To: Jeff Traigle Subject: SOLVED Re: Pine/imapd and SGI weirdness To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Seems I found the problem after digging around in the source code. There is a bug in the os_sgi.c code for the c-client in the pine-3.89 distribution. Line 411 of this file reads: execl ("/usr/ucb/rsh","rsh",hostname,"exec",service,0); It should read: execl ("/usr/bsd/rsh","rsh",hostname,"exec",service,0); There is no /usr/ucb directory on SGIs (at least not ones running 4.0.x). Changing this line and recompiling pine seems to have remedied the problem I was having. ============================================================================= | Jeff Traigle | Systems Administrator | University of Michigan | ============================================================================= | College of Pharmacy | Biophysics Research Division | ============================================================================= | Masters of Science in Computer Science and Engineering | ============================================================================= | Masters of Information and Library Studies | ============================================================================= From owner-pine-info@cac.washington.edu Mon Feb 7 11:00:35 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19121; Mon, 7 Feb 94 11:00:35 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11156; Mon, 7 Feb 94 10:36:36 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA11150; Mon, 7 Feb 94 10:36:32 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05434; Mon, 7 Feb 94 10:36:18 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA10910; Mon, 7 Feb 94 10:36:07 -0800 Date: Mon, 7 Feb 1994 10:25:42 -0800 (PST) From: Mark Crispin Subject: re: 8-bit characters in the header. To: Barry Landy Cc: Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Mon, 7 Feb 1994 11:28:54 GMT, Barry Landy wrote: > While that is true, it is also true that there are more Europeans than > Americans, and since 8859 will also cope very well with N America, > perhaps it is a better default? As a data point, inside the US and Canada there are still a great many terminals which do not support 8859. In fact, most *terminals* do not support 8859; it's the small set of lucky people who have X terminals who have 8859 capability by default, plus a few who have the right terminal emulator on their Mac or PC. It is only until very recently that the US was the ``majority'' of the Internet (now, it's merely the ``largest country represented'' on the Internet). Furthermore, you have to consider the looming importance of Asia in the Internet scene. Asia is already more important than Europe in international economy, and there's no reason to believe the steamroller is going to stop at that. All this suggests that it is not safe to assume 8859 as a given except within Europe. 7bit ASCII is the only thing that you can reasonably assume is universal. From owner-pine-info@cac.washington.edu Mon Feb 7 11:07:14 1994 Return-Path: Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19370; Mon, 7 Feb 94 11:07:14 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15945; Mon, 7 Feb 94 10:44:53 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15939; Mon, 7 Feb 94 10:44:51 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05464; Mon, 7 Feb 94 10:44:43 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA10945; Mon, 7 Feb 94 10:44:33 -0800 Date: Mon, 7 Feb 1994 10:40:53 -0800 (PST) From: Mark Crispin Subject: re: Pine/imapd and SGI weirdness To: Jeff Traigle Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hello. There is a bug in Pine 3.89 on SGI systems related to preauthentication. It is fixed in Pine 3.90. In pine/imap/non-ANSI/c-client/os_sgi.c, find the reference to "/usr/ucb/rsh" and replace it with RSHPATH (no quotes). Then rebuild. From owner-pine-info@cac.washington.edu Mon Feb 7 13:49:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23819; Mon, 7 Feb 94 13:49:04 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA18340; Mon, 7 Feb 94 13:30:01 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from bootes.cus.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA18331; Mon, 7 Feb 94 13:29:56 -0800 Received: by bootes.cus.cam.ac.uk (Smail-3.1.28.1 #115) id m0pTdWj-000BzFC; Mon, 7 Feb 94 21:29 GMT Date: Mon, 7 Feb 1994 21:29:52 +0000 (GMT) From: Barry Landy Subject: re: 8-bit characters in the header. To: Mark Crispin Cc: Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 7 Feb 1994, Mark Crispin wrote: > On Mon, 7 Feb 1994 11:28:54 GMT, Barry Landy wrote: > > While that is true, it is also true that there are more Europeans than > > Americans, and since 8859 will also cope very well with N America, > > perhaps it is a better default? > > As a data point, inside the US and Canada there are still a great many > terminals which do not support 8859. In fact, most *terminals* do not support > 8859; it's the small set of lucky people who have X terminals who have 8859 > capability by default, plus a few who have the right terminal emulator on > their Mac or PC. Well, I very naively just set ISO-8859-1 in my PINERC and got the magic characters from that Finnish name loud and clear; I then set codepage 850 and keyboard uk, and my whole world worked normally. What's the point? I have a bog standard PC with no requested special language support. I have a French Canadian friend who would take strong issue with you on the underlying point, which he calls linguistic and cultural fasciscm (yea, he is really hot on this point!) basically, it is bad enough that most computer applications assume that people *speak* English, but for heavens sake let them *write* other languages, and especially their names! > > It is only until very recently that the US was the ``majority'' of the > Internet (now, it's merely the ``largest country represented'' on the > Internet). Furthermore, you have to consider the looming importance of Asia I assumed we were talking about the total computing economy - just because Europe has been slow in taking up internet, doesnt mean it can be ignored, especially as the solutions are already there, and just need to be used. > in the Internet scene. Asia is already more important than Europe in > international economy, and there's no reason to believe the steamroller is > going to stop at that. As I said in my earlier message, the linguistic problem is wider than Europe and not just confined to Asia (Hebrew, Arabic, Turkish, Greek, are European in scope these days); the problem solution to that is "in the wings" and no one will be able to ignore it. > > All this suggests that it is not safe to assume 8859 as a given except within > Europe. 7bit ASCII is the only thing that you can reasonably assume is > universal. All very well, but you will find that you cannot then write some people's names in messages. Sorry to go on a bit (it always helps oneself perhaps more than the readers) but it is an issue on which Europeans (and other people world wide who do not have the English alphabet as their first written language) feel very strongly, and on one which US based computing has historically been very blind to. ======================================================================= Barry Landy, Head of Systems and Development, University of Cambridge Computing Service Barry.Landy@ucs.cam.ac.uk 0223-334713 +44-223-334713 From owner-pine-info@cac.washington.edu Mon Feb 7 15:43:07 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26503; Mon, 7 Feb 94 15:43:07 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA19961; Mon, 7 Feb 94 15:15:07 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA19953; Mon, 7 Feb 94 15:15:02 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA05776; Mon, 7 Feb 94 15:14:51 -0800 Received: from localhost by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA11968; Mon, 7 Feb 94 15:14:40 -0800 Date: Mon, 7 Feb 1994 14:35:00 -0800 (PST) From: Mark Crispin Subject: re: 8-bit characters in the header. To: Barry Landy Cc: Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Barry - It is important to understand that when one waves the banner of ``linguistic and cultural fascism'' one should be sure that one's own house is in order. 8859 is not universal. It is a regional character set. It may be recognized outside that region. But -- and this is important -- there are other regional character sets, and they use an overlapping space with 8859. I doubt very much that EDCfB@O: displays as anything sensible on your terminal, yet that is a standard representation of a person's name in that person's language. It's just not 8859. This is not a simple problem to solve. If it were simple, we would have solved it by now! Americans are not immune from the problem either; they just are closer to the subset and don't have to worry about losing any letters. Backslash is yen-sign in Japan. Sharp-sign is the British currency symbol in the UK. Dollar sign, at-sign, and other familiar characters (to us) are also different in various national variants of ASCII. In other words, the lingua franca of Internet email is a *subset* of 7bit ASCII. To be safe, you have to stay within that subset unless you are communicating within your region. Even after Pine supports RFC-1522 header encoding, it'll still be advisable to have an acceptable 7bit representation of your name along with the 8859 version. -- Mark -- From owner-pine-info@cac.washington.edu Mon Feb 7 16:14:55 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27144; Mon, 7 Feb 94 16:14:55 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15860; Mon, 7 Feb 94 15:50:54 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from zow13.desy.de by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA15844; Mon, 7 Feb 94 15:50:48 -0800 Received: by zow13.desy.de id AA02575 (5.67a8/IDA-1.5 for pine-info@cac.washington.edu); Tue, 8 Feb 1994 00:48:27 +0100 Date: Tue, 8 Feb 1994 00:48:19 +0100 (MET) From: Wojtek Bogusz Reply-To: Wojtek Bogusz Subject: 3 questions To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Charset: US-ASCII X-Char-Esc: 29 Hello ! I have to say I am not very experienced user of pine. But all are starting one day :-) So instead of digging in manuals or in archives of this mailing list I have decided to ask those probably easy questions: 1. When you open your INBOX you have mails sorted from newest (top) to oldest (bottom) that comes to you. Is there a way to have mails permanently sorted from oldest (top) to newest, just like in any other folders ? 2. When pine is running and new mail comes (you can see in on you xbiff, which checks mailbox once in 10 s.) you have to wait really long time until pine will realize that there is some thing new in mailbox. It is very irritating. And most of the time it is quicker to quit pine and re-run it again. Is there a way to force pine to reopen INBOX ? Or to customize time beatweane checking mailbox ? 3. Is there a plane to write Xwindows interface to pine ? Or may be there is written one ... ? If it is a FAQ or it is well explained on one of the page of the manual just please give me the pointer :-) Thanks Wojtek Bogusz From owner-pine-info@cac.washington.edu Mon Feb 7 16:27:26 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27493; Mon, 7 Feb 94 16:27:26 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16084; Mon, 7 Feb 94 16:07:18 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from bohemia.med.utah.edu by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA16078; Mon, 7 Feb 94 16:07:16 -0800 Received: from comet.med.utah.edu by bohemia.med.utah.edu (4.1/SMI-4.0 [uucc-nhj/15FEB1991]) id AA27866; Mon, 7 Feb 94 17:06:44 MST Received: by comet.med.utah.edu (5.57/Ultrix3.0-C) id AA11633; Mon, 7 Feb 94 17:07:14 -0700 Date: Mon, 7 Feb 1994 17:07:12 -0700 (MST) From: "Paul G. Leo Jr." Subject: pine v3.89 hanging when sending mail (solaris version -- home directory on ultrix box) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I've just noticed this behavior of pine v3.89 ( & v3.88 ). User on a solaris box, with his/her home directory on an ultrix 4.2a box, fires up pine, composes a message, and sends the message. The message is sent (and correctly received to another individual), but -- pine hangs with the "Sending mail" message. I am unable to break out of pine -- I basically have to kill the process. If a solaris user with home directory on solaris box, or ultrix user with home directory on ultrix box fires up pine, pine works as I would expect, great... Paul Leo e-mail paulleo@comet.med.utah.edu University of Utah Medical School paulleo@utahmed.bitnet Eccles Institute of Human Genetics Building 533 Room 2100 phone 801-585-3653 Salt Lake City, Utah 84106 fax 801-585-3910 From owner-pine-info@cac.washington.edu Mon Feb 7 17:24:06 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29429; Mon, 7 Feb 94 17:24:06 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA21825; Mon, 7 Feb 94 17:05:45 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA21819; Mon, 7 Feb 94 17:05:43 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA09219; Mon, 7 Feb 94 17:05:32 -0800 Date: Mon, 7 Feb 1994 17:05:31 -0800 (PST) From: David L Miller Subject: Re: 3 questions To: Wojtek Bogusz Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Wojtek, You can set the default sort ordering by changing the "sort-key" variable in your ".pinerc" file. If you press "N" several times at the bottom of the index or press "^L" in the index, that will force pine to recheck your inbox. We have no immediate plans to write an X interface for Pine, but we have heard reports of someone else doing their own conversion. --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 8 Feb 1994, Wojtek Bogusz wrote: > > Hello ! > > I have to say I am not very experienced user of pine. But all are > starting one day :-) So instead of digging in manuals or in archives of > this mailing list I have decided to ask those probably easy questions: > > 1. When you open your INBOX you have mails sorted from newest (top) > to oldest (bottom) that comes to you. Is there a way to have mails > permanently sorted from oldest (top) to newest, just like in any other > folders ? > > 2. When pine is running and new mail comes (you can see in on you xbiff, > which checks mailbox once in 10 s.) you have to wait really long time > until pine will realize that there is some thing new in mailbox. It is > very irritating. And most of the time it is quicker to quit pine and > re-run it again. Is there a way to force pine to reopen INBOX ? Or to > customize time beatweane checking mailbox ? > > 3. Is there a plane to write Xwindows interface to pine ? Or may be there > is written one ... ? > > If it is a FAQ or it is well explained on one of the page of the manual > just please give me the pointer :-) > > Thanks > > Wojtek Bogusz > From owner-pine-info@cac.washington.edu Tue Feb 8 00:46:53 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04936; Tue, 8 Feb 94 00:46:53 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20222; Tue, 8 Feb 94 00:02:27 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from omega.qmw.ac.uk by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA20216; Tue, 8 Feb 94 00:02:24 -0800 Received: from osprey.elec.qmw.ac.uk by omega.qmw.ac.uk with SMTP-DNS (PP) id <17577-0@omega.qmw.ac.uk>; Tue, 8 Feb 1994 08:01:43 +0000 Received: from slip246.slip.qmw.ac.uk by osprey.elec.qmw.ac.uk with SMTP (smail) id ; Tue, 8 Feb 94 08:02 GMT Date: Tue, 8 Feb 1994 08:03:21 GMT From: Laurie Cuthbert Subject: re: 8-bit characters in the header. To: Mark Crispin Cc: Barry Landy , Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I must say I agree with Mark. I'm quite happy to write "pds" (or even "UK pds") instead of the pound symbol as I know that character may not display as intended; also to address one of my German colleagues as Guenther to avoid the ^^ u-umlaut. The whole point about communication is that we should be certain that it can be read reliably at the other end wherever that may be, and the only sure way to do that is to use the lowest common denominator - as Mark says, a subset of 7-bit ASCII. It would be much worse to have to think about what sort of alphabet the other end might be using before composing a message. Regards Laurie Cuthbert On Mon, 7 Feb 1994 14:35:00 -0800 (PST) Mark Crispin wrote: > From: Mark Crispin > Date: Mon, 7 Feb 1994 14:35:00 -0800 (PST) > Subject: re: 8-bit characters in the header. > To: Barry Landy > Cc: Klaus Zeuge , dlm@cac.washington.edu, > sutela@utu.fi, pine-info@cac.washington.edu > > Barry - > > It is important to understand that when one waves the banner of > ``linguistic and cultural fascism'' one should be sure that one's own house is > in order. 8859 is not universal. It is a regional character set. It may be > recognized outside that region. But -- and this is important -- there are > other regional character sets, and they use an overlapping space with 8859. > > I doubt very much that EDCfB@O: displays as anything sensible on your > terminal, yet that is a standard representation of a person's name in that > person's language. It's just not 8859. > > This is not a simple problem to solve. If it were simple, we would have > solved it by now! > > Americans are not immune from the problem either; they just are closer > to the subset and don't have to worry about losing any letters. Backslash is > yen-sign in Japan. Sharp-sign is the British currency symbol in the UK. > Dollar sign, at-sign, and other familiar characters (to us) are also different > in various national variants of ASCII. > > In other words, the lingua franca of Internet email is a *subset* of 7bit > ASCII. To be safe, you have to stay within that subset unless you are > communicating within your region. Even after Pine supports RFC-1522 header > encoding, it'll still be advisable to have an acceptable 7bit representation > of your name along with the 8859 version. > > -- Mark -- > From owner-pine-info@cac.washington.edu Tue Feb 8 02:23:01 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06414; Tue, 8 Feb 94 02:23:01 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA26243; Tue, 8 Feb 94 01:52:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from bootes.cus.cam.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA26237; Tue, 8 Feb 94 01:52:34 -0800 Received: from ursa.cus.cam.ac.uk [131.111.8.6] (TAP id = ph10) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pTp75-000BzFC; Tue, 8 Feb 94 09:52 GMT Date: Tue, 8 Feb 1994 09:52:35 +0000 (GMT) From: Philip Hazel Subject: re: 8-bit characters in the header. To: Laurie Cuthbert Cc: Mark Crispin , Barry Landy , Klaus Zeuge , dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 797 > I must say I agree with Mark. I'm quite happy to write "pds" (or even "UK pds") > instead of the pound symbol as I know that character may not display as Even within one country there are differences. I'm in the UK, but my X terminal does not show a pound sterling symbol for ASCII character 35 - it shows a hash (= "sharp sign"). There are standard TLAs for the world's currencies, used by banks, airlines, etc. I don't know if they are a formal ISO standard. Anyway, for pounds sterling, you should use GBP, and for U.S. dollars, USD. No doubt there is a list somewhere on the Internet... -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Tue Feb 8 02:46:36 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06636; Tue, 8 Feb 94 02:46:36 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21054; Tue, 8 Feb 94 02:16:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay2.UU.NET by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA21048; Tue, 8 Feb 94 02:16:38 -0800 Received: from spool.uu.net (via LOCALHOST) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwcir29987; Tue, 8 Feb 94 05:16:36 -0500 Received: from verifone.UUCP by uucp6.uu.net with UUCP/RMAIL (queueing-rmail) id 051547.14215; Tue, 8 Feb 1994 05:15:47 EST Received: by verifone.com with UUCP/PMDF (DECUS UUCP); Mon, 7 Feb 1994 19:10:47 -1000 Received: from verifone.com by verifone.com (PMDF V4.2-11 #2386) id <01H8M59DQWUO8WWA02@verifone.com>; Mon, 7 Feb 1994 19:10:43 -1000 Date: Mon, 07 Feb 1994 19:10:43 -1000 From: "James H. Thompson - HNL" Subject: Question on address parsing To: pine-info@cac.washington.edu Message-Id: <01H8M59DSIPU8WWA02@verifone.com> Organization: VeriFone X-Ps-Qualifiers: /FONT=Courier-Bold/LINES=66/LEFT_MARGIN=36/CALCULATE/TOP_MARGIN=36/BOTTOM_MARGIN=36 X-Envelope-To: cac.washington.edu!pine-info X-Vms-To: IN%"pine-info@cac.washington.edu" X-Vms-Cc: JIMMY_T Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT When a from line contains a personal name that contains commas PINE seems to have problems extracting the correct reply address. Example of a from line that causes problems: From:"Laura, Veglac, .... lots, of, junk" Is there an easy fix for this? Thanks. Jim +------------------------------------+--------------------------------------+ | James H. Thompson | jimmy_t@verifone.com (Internet) | | VeriFone Inc. | uunet!verifone!jimmy_t (UUCP) | | 100 Kahelu Avenue | 808-623-2911 (Phone) | | Mililani, HI 96789 | 808-625-3201 (FAX) | +------------------------------------+--------------------------------------+ From owner-pine-info@cac.washington.edu Tue Feb 8 04:05:17 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07996; Tue, 8 Feb 94 04:05:17 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA27062; Tue, 8 Feb 94 03:44:42 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mail.swip.net by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA27056; Tue, 8 Feb 94 03:44:30 -0800 Received: from localhost by mail.swip.net (8.6.4/2.01) id LAA21385; Tue, 8 Feb 1994 11:59:56 +0100 Received: from angler.abalon.se by abalon.se (4.1/SMI-4.1) id AA04559; Tue, 8 Feb 94 11:57:20 +0100 Date: Tue, 8 Feb 94 11:57:20 +0100 From: clindh@abalon.se (Christer Lindh) Message-Id: <9402081057.AA04559@abalon.se> Received: by angler.abalon.se (4.1/SMI-4.1) id AA06502; Tue, 8 Feb 94 11:57:18 +0100 To: L.G.Cuthbert@qmw.ac.uk Cc: MRC@Panda.COM, bl10@cus.cam.ac.uk, Klaus.Zeuge@Minsk.DoCS.UU.SE, dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Laurie Cuthbert's message of Tue, 8 Feb 1994 08:03:21 GMT Subject: Re: 8-bit characters in the header. Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > The whole point about communication is that we should be certain > that it can be read reliably at the other end wherever that may be, > and the only sure way to do that is to use the lowest common > denominator - as Mark says, a subset of 7-bit ASCII. = Using a common *language* like English when communicating in a forum like this makes total sense. All words in english use characters available in ASCII. But sometimes it is necessary to refer to names, places etc in countries that use extended alphabets. And why should't people with capable MIME-readers be able to see then "=C5ke =D6st=E4ng"'s or some Asi= ans name like it was intended to be viewed, if at all possible? And when it can't be viewed properly, the MUA should do it's best. What's the difference beteen seeing that name as "Ake Ostang", "]ke \st{ng", "_ke _st_ng", "Eke Vostdng" or whatever your MIME-reader decides on showing when the charset is missing? All of these are obfuscations of the guys real name, equally "useless". In this particular example the first alternative is the best approximation and could be achieved by using mapping tables between some character sets. There is existing code and "standard" for this available in the public domain (forgot wo wrote it though). But if the name was in Hebrew (8859-9?) or some Asian language it just can't be mapped properly on a 7bit terminal. So what? If the writer wanted everyone on the world top see it he should supply an alternate view (MIME supports that, does Pine?). In earlies version Pine could map 8bit-chars in the wrong charset to "_" or something, and that's an option the user that's afraid that odd 8bit characters in an unavailable charset may screw up the terminal, should use. = (BTW, are we talking about 8bit in pine-list or in general here? Of course we should talk in English here but a little non-ASCII doesn't hurt anyone...) A big point about MIME IMHO is that the user writing a mail shouldn't have to worry about the capabilities of the receivers MUA. MIME tags everything that's in your mail and then it's up to the receivers MUA to do whatever's appropriate. Using ISO vs Unicode/Asian charsets are irrelevant, a good MUA should be able to adopt new registred MIME-charsets and types. Pine is great in many respects but has some way to go before it becomes a good MIME-reader for other languages, for example it should support character mapping tables and viewing attachments in other charsets by switching the terminals charset (for xterm for example). The "metamail" package can do things like this. This discussion went the wrong track somewhere; the original question was why MIME was not supported in the header when it is so in the message body? These two types of encodings are described in the same RFC. The answer was that it WILL be, and we applause that (and eagerly wait for it). >> in order. 8859 is not universal. It is a regional character set. >> So is ASCII... -- :: clindh@abalon.se :: o/ :: ::= :: Abalon AB, Stockholm, Sweden :: /@ :: Earth. ::= :: (MIME compliant) :: /!> :: Love it or leave it. ::= :: * All disclaimers apply * :: ! climb! :: ::= From owner-pine-info@cac.washington.edu Tue Feb 8 05:53:41 1994 Return-Path: Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09065; Tue, 8 Feb 94 05:53:41 -0800 Received: by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22320; Tue, 8 Feb 94 05:36:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from mail.swip.net by mx2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA22314; Tue, 8 Feb 94 05:36:51 -0800 Received: from localhost by mail.swip.net (8.6.4/2.01) id OAA00680; Tue, 8 Feb 1994 14:36:32 +0100 Received: by datan.sk.uppsala.se (4.1/Uppsala-930825-1) id AA22211; Tue, 8 Feb 94 14:19:32 +0100 Date: Tue, 8 Feb 94 14:19:32 +0100 Message-Id: <9402081319.AA22211@datan.sk.uppsala.se> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE From: Klaus Zeuge To: Klaus.Zeuge@Minsk.DoCS.UU.SE Cc: Michael.Wolf@lrz-muenchen.de, mrc@Panda.COM, dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: Klaus Zeuge's message of Mon, 7 Feb 94 02:05:55 +0100 <9402070105.AA00124@Minsk.DoCS.UU.SE> Subject: 8-bit characters in the header. >Date: Mon, 7 Feb 94 02:05:55 +0100 >From: Klaus Zeuge >Sender: sojge@Minsk.DoCS.UU.SE >X-Phone: (int) +46-18-271064 >X-Fax: (int) +46-18-271031 > > >>Date: Sat, 5 Feb 1994 01:52:10 +0100 (MET) >>From: Michael Wolf >> >> >>I agree. Klaus may wish to use non ASCII characters only locally. But I >>also think that we all should try to keep internet messages in *English*. Ah, I see here a misunderstanding. To me an internet message might be to the guy in the next room, or to the gal accross te Atlantic ocean. The guy might understand just english, while the gal prefers swedish. Whatever. Both are internet messages. I do agree in english being the lingua franca in todays computer related world, and that it's wise giving a version of ones written name using just A to Z -- but I still think it's plus non good NOT being able to write once native name TOO, especially as the technical means exist. Yes, I'd still like to see Pine starting to cope with this. >>In addition, even many (not all) computer applications should remain in >>English and restrict themselves to ASCII. >Why? Arent't you supposed to *use* email among actual (physical) *PEOPLE* ? Here I clearly over reacted, sorry for my bad handling of english. From owner-pine-info@cac.washington.edu Tue Feb 8 09:19:30 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13161; Tue, 8 Feb 94 09:19:30 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA00240; Tue, 8 Feb 94 09:00:45 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA00234; Tue, 8 Feb 94 09:00:44 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65/UW-NDC Revision: 2.29 ) id AA28719; Tue, 8 Feb 94 09:00:35 -0800 Date: Tue, 8 Feb 1994 09:00:34 -0800 (PST) From: David L Miller Subject: Re: Question on address parsing To: "James H. Thompson - HNL" Cc: pine-info@cac.washington.edu In-Reply-To: <01H8M59DSIPU8WWA02@verifone.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is a known problem with the display routines in the composer. Pine will still interpret it correctly though. We will fix it as soon as one of us gets up the nerve to dig into the bowels of Pico ;) Thanks for the report! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 7 Feb 1994, James H. Thompson - HNL wrote: > When a from line contains a personal name that contains commas > PINE seems to have problems extracting the correct reply address. > > Example of a from line that causes problems: > > From:"Laura, Veglac, .... lots, of, junk" > > Is there an easy fix for this? > > Thanks. > > Jim > +------------------------------------+--------------------------------------+ > | James H. Thompson | jimmy_t@verifone.com (Internet) | > | VeriFone Inc. | uunet!verifone!jimmy_t (UUCP) | > | 100 Kahelu Avenue | 808-623-2911 (Phone) | > | Mililani, HI 96789 | 808-625-3201 (FAX) | > +------------------------------------+--------------------------------------+ > From owner-pine-info@cac.washington.edu Tue Feb 8 09:21:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13255; Tue, 8 Feb 94 09:21:15 -0800 Received: by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA29858; Tue, 8 Feb 94 08:46:15 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65/UW-NDC Revision: 2.30 ) id AA29852; Tue, 8 Feb 94 08:46:08 -0800 Received: from venus.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <11432-0@dummy1.dur.ac.uk>; Tue, 8 Feb 1994 16:45:27 +0000 Received: from vega.dur.ac.uk by venus.dur.ac.uk; Tue, 8 Feb 94 16:45:18 GMT Date: Tue, 8 Feb 1994 16:45:11 +0000 (GMT) From: Barry Cornelius Subject: one rsh left around after Pine finishes To: Pine Info Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 1124 We run three variants of Pine 3.89: sun for computers running SunOS 4.1.2 and SunOS 4.1.3 sol for computers running SunOS 5.2 and SunOS 5.3 hpp for computers running HP-UX 9.01 All uses of Pine on these machines use IMAP to access the user's inbox. The IMAP daemons run on a SunOS 4.1.3 computer called venus. We are using the version supplied with Pine 3.89, namely IMAP2bis Version 7.5(72). When Pine is run, it sets up two rsh processes to venus: rsh venus exec /etc/rimapd When Pine 3.89 (or 3.88) is run on a SunOS 5.2 machine, sometimes one of the two rsh processes still remains after the user has left Pine. This happens quite often during the day. But I haven't worked out why it happens on some occasions and not on others. Is this a known problem? Has anyone else seen this? -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Wed Feb 9 10:35:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13218; Wed, 9 Feb 94 10:35:10 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14718; Wed, 9 Feb 94 10:01:17 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rubb.rz.ruhr-uni-bochum.de by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12485; Wed, 9 Feb 94 06:53:30 -0800 Received: from localhost (x920031@localhost) by rubb.rz.ruhr-uni-bochum.de (8.5/8.5) id PAA23190; Wed, 9 Feb 1994 15:53:05 +0100 Date: Wed, 9 Feb 1994 15:53:05 +0100 From: Jost Krieger Message-Id: <199402091453.PAA23190@rubb.rz.ruhr-uni-bochum.de> To: pine-info@cac.washington.edu Subject: Problem with PC-PINE and SLIP Comments: Hyperbole mail buttons accepted, v3.09. We have the following problem: Across SLIP (with the packet driver implementation) PC-PINE 3.89 seems not to work. Is this known or intended ? Thank you Jost Krieger -- Jost Krieger, Rechenzentrum der Ruhr-Universitaet Bochum Jost.Krieger@rz.ruhr-uni-bochum.de g=Jost;s=Krieger;ou=ruba;ou=rz;pd=ruhr-uni-bochum;ad=dbp;c=de From owner-pine-info@cac.washington.edu Wed Feb 9 17:12:36 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24686; Wed, 9 Feb 94 17:12:36 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20898; Wed, 9 Feb 94 16:45:08 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from cd1.lrz-muenchen.de by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20892; Wed, 9 Feb 94 16:45:02 -0800 Received: from sunserver.lrz-muenchen.de by cd1.lrz-muenchen.de id SMTP-0012d59837a005353; Thu, 10 Feb 94 01:44:42 +0100 Received: from sun3.lrz-muenchen.de by sunserver.lrz-muenchen.de (4.1/SMI-4.1) id AA13541; Thu, 10 Feb 94 01:44:40 +0100 Received: by sun3.lrz-muenchen.de (4.1/SMI-4.1) id AA10456; Thu, 10 Feb 94 01:44:40 +0100 Date: Thu, 10 Feb 1994 01:44:39 +0100 (MET) From: Michael Wolf Reply-To: Michael Wolf Subject: Re: 8-bit characters in the header. To: Klaus Zeuge Cc: Klaus.Zeuge@Minsk.DoCS.UU.SE, mrc@Panda.COM, dlm@cac.washington.edu, sutela@utu.fi, pine-info@cac.washington.edu In-Reply-To: <9402081319.AA22211@datan.sk.uppsala.se> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 8 Feb 1994, Klaus Zeuge wrote: > > > > > > >>Date: Sat, 5 Feb 1994 01:52:10 +0100 (MET) > >>From: Michael Wolf > >> > >> > >>I agree. Klaus may wish to use non ASCII characters only locally. But I > >>also think that we all should try to keep internet messages in *English*. > > Ah, I see here a misunderstanding. To me an internet message might be > to the guy in the next room, or to the gal accross te Atlantic ocean. > The guy might understand just english, while the gal prefers swedish. > Whatever. Both are internet messages. Perhaps I should have said "international messages", or "messages to an international audience". > > I do agree in english being the lingua franca in todays computer > related world, and that it's wise giving a version of ones written > name using just A to Z -- but I still think it's plus non good NOT > being able to write once native name TOO, especially as the technical > means exist. > > Yes, I'd still like to see Pine starting to cope with this. Wishing to display your name in your language via e-mail to people that understand your language is legitimate. But I would use non-ASCII only for well defined targets and with care. Certainly an international mailing list or an international news group would not be an adequate audience. Receiving a name in a Japanese font, for example, would make no sense for me, even if my computer would be able to display it correctly. :-) Michael From owner-pine-info@cac.washington.edu Wed Feb 9 22:13:38 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28030; Wed, 9 Feb 94 22:13:38 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23579; Wed, 9 Feb 94 21:49:46 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from usage.csd.unsw.OZ.AU by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23573; Wed, 9 Feb 94 21:49:41 -0800 Received: from cfd.mech.unsw.OZ.AU by usage.csd.unsw.OZ.AU with SMTP id AA13264 (5.65c/IDA-1.4.4 for ); Thu, 10 Feb 1994 16:49:51 +1100 Received: by cfd.mech.unsw.OZ.AU (AIX 3.2/UCB 5.64/4.03) id AA09281; Thu, 10 Feb 1994 16:49:16 +1000 Date: Thu, 10 Feb 1994 16:49:16 +1000 (EET) From: Eddie Leonardi Subject: Various To: Pine-info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! I have two quick questions about Pine. If anyone can help please let eddie@cfd.mech.unsw.oz.au know. 1. How do you switch off the debug mode in pine i.e. so that debug files are not printed. 2. When using the basic unix mail command it is possible to put it into verbose mode so that you can see it sending the mail and if it actually got there or not. Is it possible to do the same thing in pine? I.e. put it in a verbose mode? Thanks Eddie *--------------------------------------------------------* | Associate Professor Eddie Leonardi | | School of Mechanical and Manufacturing Engineering | | The University of New South Wales | | P.O. Box 1, Kensington, N.S.W., AUSTRALIA 2033 | | | | E-mail: E.Leonardi@unsw.edu.au ; Fax: (+61 2) 663 1222 | | Phone: Work: (+61 2) 697 4252 ; Home: (+61 2) 646 2568 | *--------------------------------------------------------* From owner-pine-info@cac.washington.edu Wed Feb 9 23:17:25 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28958; Wed, 9 Feb 94 23:17:25 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17799; Wed, 9 Feb 94 22:49:34 -0800 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/UW-NDC Revision: 2.30 ) id AA17791; Wed, 9 Feb 94 22:49:32 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA08803; Wed, 9 Feb 94 22:49:20 -0800 Date: Wed, 9 Feb 1994 22:49:19 -0800 (PST) From: David L Miller Subject: Re: Various To: Eddie Leonardi Cc: Pine-info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Eddie, To switch off debugging, use the -d0 command line option. Pine does not yet have a verbose send mode, but we are considering making it an option. --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 10 Feb 1994, Eddie Leonardi wrote: > Hi! > > I have two quick questions about Pine. If anyone can help please let > eddie@cfd.mech.unsw.oz.au know. > > 1. How do you switch off the debug mode in pine i.e. so that debug files > are not printed. > > 2. When using the basic unix mail command it is possible to put it into > verbose mode so that you can see it sending the mail and if it actually > got there or not. Is it possible to do the same thing in pine? I.e. > put it in a verbose mode? > > > Thanks > Eddie > > *--------------------------------------------------------* > | Associate Professor Eddie Leonardi | > | School of Mechanical and Manufacturing Engineering | > | The University of New South Wales | > | P.O. Box 1, Kensington, N.S.W., AUSTRALIA 2033 | > | | > | E-mail: E.Leonardi@unsw.edu.au ; Fax: (+61 2) 663 1222 | > | Phone: Work: (+61 2) 697 4252 ; Home: (+61 2) 646 2568 | > *--------------------------------------------------------* > From owner-pine-info@cac.washington.edu Thu Feb 10 03:01:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01925; Thu, 10 Feb 94 03:01:15 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25748; Thu, 10 Feb 94 02:47:39 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rye.city.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25742; Thu, 10 Feb 94 02:47:35 -0800 Received: from hove.city.ac.uk by Rye.city.ac.uk with SMTP (PP) id <18500-0@Rye.city.ac.uk>; Thu, 10 Feb 1994 10:35:00 +0000 Date: Thu, 10 Feb 1994 10:42:51 +0000 (GMT) From: David Brownlee Subject: Verbose send mode To: Pine-Info Maillist Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Could I add a vote for this to be an option! David D.K.Brownlee@city.ac.uk. Network Analyst. Postmaster. Hostmaster. <_.-^-._> Telephone: (+44) 71 477 8000 Ext:3757. <_.-^-._> Snailmail:E308, City University, Northampton Sq, Islington, London EC1V 0HB. From owner-pine-info@cac.washington.edu Thu Feb 10 06:05:41 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04544; Thu, 10 Feb 94 06:05:41 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20720; Thu, 10 Feb 94 05:40:37 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20714; Thu, 10 Feb 94 05:40:32 -0800 Received: from ursa.cus.cam.ac.uk [131.111.8.6] (TAP id = ph10) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pUbd8-000BzOC; Thu, 10 Feb 94 13:40 GMT Date: Thu, 10 Feb 1994 13:40:55 +0000 (GMT) From: Philip Hazel Subject: Replying without attachments To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 797 I received a message with a MIME attachment, to which I wanted to reply. Having been caught once before, I checked carefully before sending the reply, and noticed that Pine 3.89 had added the attachment to the reply, which doesn't seem right to me. One would rarely want to send an attachment back to its sender, I feel. However, I was able to delete the attachment before sending the message, which saved some embarrassment, but the recipient tells me that the message was nevertheless sent as MIME MULTIPART/Mixed, despite having no attachments. This must be a minor bug... Regards, Philip -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Thu Feb 10 10:34:48 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10796; Thu, 10 Feb 94 10:34:48 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23831; Thu, 10 Feb 94 10:09:33 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23825; Thu, 10 Feb 94 10:09:31 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26120; Thu, 10 Feb 94 10:09:09 -0800 Date: Thu, 10 Feb 1994 10:09:09 -0800 (PST) From: David L Miller Subject: Re: Replying without attachments To: Philip Hazel Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Yes, this is a known problem. Thanks for the report! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 10 Feb 1994, Philip Hazel wrote: > I received a message with a MIME attachment, to which I wanted to reply. > Having been caught once before, I checked carefully before sending the > reply, and noticed that Pine 3.89 had added the attachment to the reply, > which doesn't seem right to me. One would rarely want to send an attachment > back to its sender, I feel. > > However, I was able to delete the attachment before sending the message, > which saved some embarrassment, but the recipient tells me that the message > was nevertheless sent as MIME MULTIPART/Mixed, despite having no > attachments. This must be a minor bug... > > Regards, > Philip > > -- > Philip Hazel University Computing Service, > ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, > P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 > > From owner-pine-info@cac.washington.edu Thu Feb 10 11:04:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12010; Thu, 10 Feb 94 11:04:54 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24211; Thu, 10 Feb 94 10:34:53 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from dshp04.trs.ntc.nokia.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24205; Thu, 10 Feb 94 10:34:42 -0800 Received: from dshp02.trs.ntc.nokia.com by dshp04.trs.ntc.nokia.com with SMTP (1.37.109.4/16.2) id AA14883; Thu, 10 Feb 94 20:34:36 +0200 Received: by dshp02.trs.ntc.nokia.com (1.37.109.4/16.2) id AA25328; Thu, 10 Feb 94 20:36:53 +0200 Date: Thu, 10 Feb 1994 20:36:53 +0300 (EETDST) From: Ian Leiman Subject: Problems starting pine from HP Vue Frontpanel and menus To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This is a problem that has bothered me a long time, but I haven't had any luck in finding a nice solution. Perhaps someone in this mailing list has figured it out?? We use HP9000/730 hosts with HP/UX 9.01 and from 700/RX X-terminals configured to use HP-Vue. PINE does not of course work properly with the default HpTerm terminal windows, you must use Xterm. In HpTerm cursors keys won't work etc. weird things happen. Modifying ttyin.c would surely fix this, but that's not my idea of having fun :-) Even when you use xterm, you must start pine from a shell. Starting pine by using 'xterm -e pine', which starts pine directly without invoking any shell first, does not work properly. Something goes wrong with the tty-driver and the screen becomes messy. This would work however: 'xterm -e csh -c pine' but executing the shell in between is really a waste of CPU time and system resources. The shell shouldn't really be needed. Then you could of course make a shell script (say eg. 'exec.pine') that contains #!/bin/csh exec pine executed by 'xterm -e exec.pine', to get rid of the shell after pine starts. This isn't very elegant either. Also, pine won't start from tcsh or zsh properly, you must use csh. This is the only program that I know of, that behaves like this. Answer may be found from ttyout.c's 2000 lines of code, or maybe it's HPs fault? The standard way to put something like pine into Vue Workspace Menu is modifying your ~/.vue/vuewmrc (or system-wide '/usr/vue/config/sys.vuewmrc') in the following manner: Menu VueRootMenu { "Workspace Menu" f.title pine _P MetaF11 f.exec "xterm -e pine" ...etc... } Can somebody explain why doesn't this work, and I really must use the ugly: pine _P MetaF11 f.exec "xterm -e csh -c pine" Equivalently, adding PINE to Front Panel goes like this. To a file called '/usr/vue/config/panels/fp.mail' you add (included in vuewmrc): CONTROL Pine { TYPE button IMAGE mail LABEL "Pine" PUSH_ACTION f.exec "xterm -e /usr/local/bin/pine" } ...etc... BOX Bottom { TYPE secondary CONTROL Pine } ... which of course doesn't work, you must make it PUSH_ACTION f.exec "xterm -e /bin/csh -c /usr/local/bin/pine" ************************ Note, that you can also replace PINE as your MAILER action, which means that you could have PINE start from the standard mail button of Front Panel. You need a file called '/usr/vue/config/types/pine.vf', that contains: ACTION Pine DESCRIPTION Pine mailer action TYPE COMMAND EXEC-STRING /usr/local/bin/pine WINDOW-TYPE TERMINAL END then in your '~/.vue/types/user-prefs.vf' OR '/usr/vue/types/user-prefs.vf': # To use a mailer other than elm, define an action for your mailer and # substitute it for Elm. ACTION Mailer TYPE MAP Pine END The problem here is that Vue absolutely refuses to use Xterm disregarding that I have defined personally and system-wide TERMINAL action as Xterm. Vue persistently uses Hpterm and Pine thus won't work. A less elegant work-around is to have a script start the xterm, which would start the shell and then pine. But that's too desperate... -- Ian Leiman, M.Sc. phone +358 0 5104 4453, fax +358 0 5104 4764 From owner-pine-info@cac.washington.edu Thu Feb 10 11:47:12 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13684; Thu, 10 Feb 94 11:47:12 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24961; Thu, 10 Feb 94 11:20:33 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from kenya.isu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24955; Thu, 10 Feb 94 11:20:31 -0800 Message-Id: <9402101920.AA24955@mx2.cac.washington.edu> Received: by kenya.isu.edu (1.37.109.8/16.2) id AA02439; Thu, 10 Feb 1994 12:19:53 -0700 Date: Thu, 10 Feb 1994 12:19:53 -0700 From: Daniel Simmons To: pine-info@cac.washington.edu Cc: leiman@dshp.ntc.nokia.com Subject: Re: Problems starting pine from HP Vue Frontpanel and menus In-Reply-To: <2jdvnb$25n@kenya.isu.edu> Organization: Idaho State University, Pocatello Cc: In article <2jdvnb$25n@kenya.isu.edu> you write: >We use HP9000/730 hosts with HP/UX 9.01 and from 700/RX X-terminals >configured to use HP-Vue. PINE does not of course work properly with >the default HpTerm terminal windows, you must use Xterm. In HpTerm >cursors keys won't work etc. weird things happen. Modifying ttyin.c >would surely fix this, but that's not my idea of having fun :-) This doesn't "exactly" answer your question, but... I have a patch for pine version 3.87 (I haven't updated it to 3.89 yet) which makes it work properly in an hpterm (I had to because a number of our users actually use hp dumb terminals--not under x windows). There are still a few small problems, but they are basically little reverse video buglets that don't amount to much (99% of everything works correctly). I've also talked with the pine maintainers about some more hardcore changes to their terminal i/o library which would fix the rest of the problems. We may work together to integrate the changes in some future release of pine. Anyway, if you want the patch, let me know. Danny -- Daniel Simmons electronic mail : simmdan@isu.edu Idaho State University voice mail : (208) 236-3199 Computer Center snail mail : Box 8037, Pocatello From owner-pine-info@cac.washington.edu Thu Feb 10 12:29:39 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14531; Thu, 10 Feb 94 12:29:39 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02306; Thu, 10 Feb 94 12:06:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from h141-206-15-5.NCR.COM by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02300; Thu, 10 Feb 94 12:06:01 -0800 Received: from tecsrv12.ElSegundoCA.NCR.COM by tdat.ElSegundoCA.NCR.COM (4.1/SMI-4.1) id AA04147; Thu, 10 Feb 94 12:06:01 PST Received: by tecsrv12.ElSegundoCA.NCR.COM (4.1/SMI-4.1) id AA09037; Thu, 10 Feb 94 12:05:59 PST Date: Thu, 10 Feb 1994 12:05:58 -0800 (PST) From: Burzin Engineer Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII A few questions: (I moved from elm to pine, my questions might reflect that) 1. anyway in pine for having a local signature file v/s remote signature file? 2. anyway of saving outgoing message by to-field default and if folder does not exist then put it in sent-mail? 3. How do you stop pine from adding the domainname to internal messages. i.e. If I leave it blank in .pinerc then it recognizes internal mail and expands userid to username BUT my external mail does not have my correct return address, so people cannot reply back to me. If I add the domainname it appends it to internal addresses also which I would prefer not to. Any solutions? Thanks -- Burzin N. Engineer Teradata Database Development Center | Phone (310) 524-7513 Decision Enabling Systems Division | Fax (310) 524-5511 AT&T Global Information Solutions | E-Mail bne@elsegundoca.ncr.com From owner-pine-info@cac.washington.edu Thu Feb 10 13:15:47 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15975; Thu, 10 Feb 94 13:15:47 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25956; Thu, 10 Feb 94 12:45:57 -0800 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/UW-NDC Revision: 2.30 ) id AA25950; Thu, 10 Feb 94 12:45:55 -0800 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA27523; Thu, 10 Feb 94 12:45:52 -0800 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 10 Feb 94 21:35:08+0100 Date: 10 Feb 94 21:35:08+0100 From: Burzin Engineer Message-Id: <571428*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine Info From owner-pine-info@cac.washington.edu Thu Feb 10 14:08:20 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17446; Thu, 10 Feb 94 14:08:20 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26903; Thu, 10 Feb 94 13:42:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from phar.umich.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26897; Thu, 10 Feb 94 13:42:44 -0800 Received: from sun4.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA22402; Thu, 10 Feb 94 16:42:21 -0500 Date: Thu, 10 Feb 1994 16:42:22 -0500 (EST) From: Jeff Traigle Subject: alias conversions To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Does anybody happen to have conversion tools already written? I'm attempting to migrate one of my sites to IMAP, but I can see that I might meet with some resistence since the aliases aren't in compatible formats. Particular conversions would need to be from .mailrc and from elm formats. -- +-----------------------------------------------------------------------------+ | Jeff Traigle | | Systems Administrator | +-----------------------------------------------------------------------------+ | University of Michigan University of Michigan | | College of Pharmacy Biophysics Research Division | | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | | Ann Arbor MI 48109 Ann Arbor MI 48109 | +-----------------------------------------------------------------------------+ | traigle@umich.edu Pager: (313) 617-8793 | +-----------------------------------------------------------------------------+ From owner-pine-info@cac.washington.edu Thu Feb 10 16:34:40 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA21244; Thu, 10 Feb 94 16:34:40 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06203; Thu, 10 Feb 94 16:09:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from nic-nac.CSU.net by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06197; Thu, 10 Feb 94 16:09:19 -0800 Received: by nis.CalState.EDU (4.1/NIS 1.0) id AA25522; Thu, 10 Feb 94 16:08:26 PST Date: Thu, 10 Feb 1994 16:08:26 -0800 (PST) From: Pete Kaplan Subject: Word wrap To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII How do I keep pico from word wrapping? Occasionally, there is a need to write a unix command that must be on a continued line. Peter Kaplan Sys Adm Cal. St. Univ. Chanc. Office (310) 985-9446 From owner-pine-info@cac.washington.edu Thu Feb 10 19:43:42 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24723; Thu, 10 Feb 94 19:43:42 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08451; Thu, 10 Feb 94 19:13:27 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08445; Thu, 10 Feb 94 19:13:25 -0800 Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA29889; Thu, 10 Feb 94 19:12:09 -0800 Date: Thu, 10 Feb 1994 19:12:09 -0800 (PST) From: David L Miller Subject: Re: Word wrap To: Pete Kaplan Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The "-w" command line option will disable word-wrap in Pico. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 10 Feb 1994, Pete Kaplan wrote: > How do I keep pico from word wrapping? Occasionally, there is a need to > write a unix command that must be on a continued line. > > Peter Kaplan Sys Adm > Cal. St. Univ. Chanc. Office > (310) 985-9446 > From owner-pine-info@cac.washington.edu Fri Feb 11 01:37:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28879; Fri, 11 Feb 94 01:37:15 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10820; Fri, 11 Feb 94 01:22:59 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10812; Fri, 11 Feb 94 01:22:57 -0800 Received: from rs1.jr2.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <03762-0@oxmail.ox.ac.uk>; Fri, 11 Feb 1994 09:22:08 +0000 Date: Fri, 11 Feb 1994 09:19:38 +0000 (GMT) From: Terry Campton Analyst/Programmer NDM Subject: Running Pine under AIX v 3.2 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dear Pine Team, We seem to have a problem running pine under AIX v 3.2, I cannot run pine with any options, I can't even do a -conf, to see what is what. We are using pine 3.89 the m/c is an IBM RS600 Model 320 running AIX v3.2. We are also using pine 3.89 on a DEC 5000/240 running ULTRIX v 4.3 and pine is running fine there, so we would like to get the IBM up to scratch. Any suggestions ? Terry Campton University Data Centre University of Oxford John Radcliffe Hospital Oxford From owner-pine-info@cac.washington.edu Fri Feb 11 01:39:41 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28906; Fri, 11 Feb 94 01:39:41 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03336; Fri, 11 Feb 94 01:23:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03330; Fri, 11 Feb 94 01:22:58 -0800 Received: from ursa.cus.cam.ac.uk [131.111.8.6] (TAP id = ph10) by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pUu5R-000BzMC; Fri, 11 Feb 94 09:22 GMT Date: Fri, 11 Feb 1994 09:23:10 +0000 (GMT) From: Philip Hazel Subject: Commas To: maillist Pine Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 364 Why won't pine accept commas in file names? They are relatively common in file names on Unix... Is there a quoting mechanism that I have overlooked? Regards, Philip -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Fri Feb 11 01:55:52 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29040; Fri, 11 Feb 94 01:55:52 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03450; Fri, 11 Feb 94 01:39:44 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from comserv.zdv.uni-tuebingen.de by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03444; Fri, 11 Feb 94 01:39:42 -0800 Received: by comserv.zdv.uni-tuebingen.de (4.1/ZDV-Uni-Tuebingen-1.0) id AA28360; Fri, 11 Feb 94 10:39:33 +0100 Date: Fri, 11 Feb 94 10:39:33 +0100 From: spohn@zdv.uni-tuebingen.de (Martin Spohn) Message-Id: <9402110939.AA28360@comserv.zdv.uni-tuebingen.de> To: pine-info@cac.washington.edu Subject: user-id for UNIX-Pine Hello all, is there an equivalent for the PC-PINE variable user-id in UNIX-Pine? Thanks Martin Spohn Zentrum fuer Datenverarbeitung Telefon: +49 7071 29-6970 (Fax: -5912) Abteilung Netze E-Mail: Universitaet Tuebingen SMTP: spohn@zdv.uni-tuebingen.de Brunnenstrasse 27 X.400: C=de;A=d400;P=uni-tuebingen;O=zdv;S=spohn D-72074 Tuebingen From owner-pine-info@cac.washington.edu Fri Feb 11 03:24:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00191; Fri, 11 Feb 94 03:24:04 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11389; Fri, 11 Feb 94 03:06:04 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from livbird.liv.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11383; Fri, 11 Feb 94 03:06:02 -0800 Received: from liverbird.liverpool.ac.uk by liverbird.liverpool.ac.uk via Local channel id <20100-0@liverbird.liverpool.ac.uk>; Fri, 11 Feb 1994 11:02:16 +0000 Subject: imapd version with pine 3.89 To: pine-info@cac.washington.edu Date: Fri, 11 Feb 1994 11:02:15 +0000 (GMT) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 290 From: Alan Thew Message-Id: <"liverbird..102:11.01.94.11.02.17"@liverbird.liverpool.ac.uk> The source says that it's version 7.5(72). How does this correspond to the imapd version number listed on the ftp site e.g. 3.1 ? Thanks -- Alan Thew alan.thew@liv.ac.uk ...!uknet!liv!alan.thew Tel: +44 51 794-3735 University of Liverpool, Computing Services Fax: +44 51 794-3759 From owner-pine-info@cac.washington.edu Fri Feb 11 05:04:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01746; Fri, 11 Feb 94 05:04:40 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04819; Fri, 11 Feb 94 04:43:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from relay1.UU.NET by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04813; Fri, 11 Feb 94 04:42:58 -0800 Received: from uucp5.uu.net by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwcuc26322; Fri, 11 Feb 94 07:42:57 -0500 Received: from sangam.UUCP by uucp5.uu.net with UUCP/RMAIL ; Fri, 11 Feb 1994 07:42:56 -0500 Received: by sangam.ncst.ernet.in (4.1/SMI-4.2-ERNET-relay) with UUCP id AA14737; Fri, 11 Feb 94 18:00:20+0530 Received: by ern.doe.ernet.in (4.1/SMI-4.1-MHS-7.0) id AA26029; Fri, 11 Feb 94 14:49:48+0530 Message-Id: <9402110919.AA26029@ern.doe.ernet.in> Return-Path: Subject: help ? To: pine-info@cac.washington.edu Date: Fri, 11 Feb 94 14:46:20 GMT+5:30 Generate-Delivery-Report: From: SANJEEV SINGH Hello! pine group How can I execute *ftp* command from message body (or some where else ? ) of pine to fetch data from remote M/C in case message body is large enough. can someone help me ? thanx in advance. -sanjeev From owner-pine-info@cac.washington.edu Fri Feb 11 05:15:31 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01824; Fri, 11 Feb 94 05:15:31 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04890; Fri, 11 Feb 94 04:58:53 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from hermes.acs.ryerson.ca by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04884; Fri, 11 Feb 94 04:58:51 -0800 Received: by hermes.acs.ryerson.ca (AIX 3.2/UCB 5.64/4.03) id AA22313; Fri, 11 Feb 1994 07:58:18 -0500 Date: Fri, 11 Feb 1994 07:58:18 -0500 (EST) From: Paul Ribeiro Subject: Spool Cleanup To: Info Pine Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII This isn't a pine question but I'm interested in how mail managers deal with end of semester cleanups and people who love to keep all their mail in their inbox. Do you run a nightly job to remove mail that is more than xx days old? many thanks, /P From owner-pine-info@cac.washington.edu Fri Feb 11 06:40:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02730; Fri, 11 Feb 94 06:40:40 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05431; Fri, 11 Feb 94 06:15:20 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from ua.d.umn.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05425; Fri, 11 Feb 94 06:15:18 -0800 Received: from jness.d.umn.edu by ua.d.umn.edu with SMTP id AA16923 (5.65c/IDA-1.4.4 for ); Fri, 11 Feb 1994 08:15:08 -0600 Date: Fri, 11 Feb 94 08:15:12 -0600 From: Joel Ness To: Jeff Traigle Subject: Re: alias conversions Cc: Pine Information Message-Id: In-Reply-To: Your message of Thu, 10 Feb 1994 16:42:22 -0500 (EST) Content-Type: TEXT/plain; charset=US-ASCII > Does anybody happen to have conversion tools already > written? I'm attempting to migrate one of my sites to > IMAP, but I can see that I might meet with some > resistence since the aliases aren't in compatible > formats. Particular conversions would need to be from > .mailrc and from elm formats. > > -- > +--------------------------------------------------------- > --------------------+ > | Jeff Traigle > | 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, but Pine seems to handle that all right. #!/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 << --- %s/ = / / %s/ = / ( %s/\$/)/ :w $HOME/.addressbook --- set n=`cat $HOME/.addressbook | wc -l` echo $n elm aliases converted to pine addresses else echo no Elm aliases found endif _________________________ Joel Ness UMD Information Services jness@ua.d.umn.edu (218) 726-8841 From owner-pine-info@cac.washington.edu Fri Feb 11 07:06:45 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03004; Fri, 11 Feb 94 07:06:45 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12865; Fri, 11 Feb 94 06:39:17 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12859; Fri, 11 Feb 94 06:39:09 -0800 Received: from teaching.physics.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <19728-0@oxmail.ox.ac.uk>; Fri, 11 Feb 1994 14:10:56 +0000 Received: from teaching6 by teaching.physics.ox.ac.uk (NX5.67d/NX3.0M) id AA27465; Fri, 11 Feb 94 14:10:51 GMT Received: by teaching6.physics.ox.ac.uk (NX5.67d/NX3.0X) id AA08732; Fri, 11 Feb 94 14:10:47 GMT Date: Fri, 11 Feb 1994 14:10:45 +0000 (GMT) From: The PenMaster Subject: Vt100 & ANSI codes To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hwi there, Really sorry to post a non-Pine question (sort of), but no-one on the Usenet seems to be willing to help me... I need some documentation on VT100 and ANSI escape codes including curur positioning and colours, etc, and would be very grateful if someone could mail me any info that they have. Thanks. Secondly; Pine and ANSI. Is there any way of getting Pine to display messages with something like More, for example so that messages including cursor postioning information could be displyed correctly (e.g. for ANSI animations). I know that you can save out the message, stip off the headers and then view it with More, but it would be nice to be able to do it all from within Pine... Charuuba! David Edwards _ _ ==========////==================================================== / //// David Edwards: Welcome to the real world... \ || _ _ //// send mail to: || || \\\\ //// edwards%teaching.physics@ox.ac.uk || \ \\\X/// or u93dwe@ecs.ox.ac.uk / ====\XXX/========================================================= From owner-pine-info@cac.washington.edu Fri Feb 11 07:44:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03596; Fri, 11 Feb 94 07:44:02 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05793; Fri, 11 Feb 94 07:24:24 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from INDIV-GW.CENT.NET by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05787; Fri, 11 Feb 94 07:24:22 -0800 Received: by individual.com (5.65c/Spike-2.1) id AA01429; Fri, 11 Feb 1994 10:19:50 -0500 Date: Fri, 11 Feb 1994 10:16:05 -0500 (EST) From: Adam J Weitzman Reply-To: Adam J Weitzman Subject: Re: Commas To: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 11 Feb 1994, Philip Hazel wrote: > Why won't pine accept commas in file names? They are relatively common in > file names on Unix... Is there a quoting mechanism that I have overlooked? This is news to me. I have been around UNIX for almost 8 years and I have maybe once or twice only ever seen a filename with a comma in it. But if you really need to include it, you can always go "To files" after the "Read File" part and bring it in that way. I don't know why Pine won't let you tyoe it in, though. - Adam J Weitzman INDIVIDUAL, Inc. weitzman@individual.com From owner-pine-info@cac.washington.edu Fri Feb 11 08:55:03 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05498; Fri, 11 Feb 94 08:55:03 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13738; Fri, 11 Feb 94 08:35:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13713; Fri, 11 Feb 94 08:35:00 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02639; Fri, 11 Feb 94 08:34:44 -0800 Date: Fri, 11 Feb 1994 08:34:44 -0800 (PST) From: David L Miller Subject: Re: Running Pine under AIX v 3.2 To: Terry Campton Analyst/Programmer NDM Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Did you compile Pine from the source distribution or are you using our pre-compiled binaries? A number of AIX 3.2 sites have had trouble building from source, but had no trouble with the pre-compiled version. We would like to isolate the problem, but so far have not been able to get access to any of the problem systems... The pre-compiled binaries are available from ftp.cac.washington.edu in the mail/unix-bin directory. Thanks for the report! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 11 Feb 1994, Terry Campton Analyst/Programmer NDM wrote: > Dear Pine Team, > > We seem to have a problem running pine under AIX v 3.2, I cannot run pine > with any options, I can't even do a -conf, to see what is what. > > We are using pine 3.89 the m/c is an IBM RS600 Model 320 running AIX > v3.2. We are also using pine 3.89 on a DEC 5000/240 running ULTRIX v 4.3 > and pine is running fine there, so we would like to get the IBM up to > scratch. > > Any suggestions ? > > > Terry Campton > University Data Centre > University of Oxford > John Radcliffe Hospital > Oxford From owner-pine-info@cac.washington.edu Fri Feb 11 08:57:05 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05712; Fri, 11 Feb 94 08:57:05 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06482; Fri, 11 Feb 94 08:37:52 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06476; Fri, 11 Feb 94 08:37:50 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02663; Fri, 11 Feb 94 08:37:35 -0800 Date: Fri, 11 Feb 1994 08:37:35 -0800 (PST) From: David L Miller Subject: Re: user-id for UNIX-Pine To: Martin Spohn Cc: pine-info@cac.washington.edu In-Reply-To: <9402110939.AA28360@comserv.zdv.uni-tuebingen.de> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Martin, No. We are considering adding it or something similar though. In the mean time, the next version of Pine (due late spring) will include the Reply-To: header, which might help solve your problem. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 11 Feb 1994, Martin Spohn wrote: > Hello all, > > is there an equivalent for the PC-PINE variable user-id in UNIX-Pine? > > Thanks > > Martin Spohn > Zentrum fuer Datenverarbeitung Telefon: +49 7071 29-6970 (Fax: -5912) > Abteilung Netze E-Mail: > Universitaet Tuebingen SMTP: spohn@zdv.uni-tuebingen.de > Brunnenstrasse 27 X.400: C=de;A=d400;P=uni-tuebingen;O=zdv;S=spohn > D-72074 Tuebingen From owner-pine-info@cac.washington.edu Fri Feb 11 09:27:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07030; Fri, 11 Feb 94 09:27:08 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06850; Fri, 11 Feb 94 09:03:24 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from alpha.itu.br by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06844; Fri, 11 Feb 94 09:03:06 -0800 Received: from urutu.itu.br by alpha.itu.br id aa07309; 11 Feb 94 15:02 BST Message-Id: Date: Fri, 11 Feb 94 15:00:48 PST From: andries@urutu.itu.br Subject: Pine on SCO UNIX System V/386, Release 3.2 To: pine-info@cac.washington.edu Reply-To: algera@itu.br Mime-Version: 1.0 Content-Type: Text/Plain; Charset=US-ASCII Hi folks, Could you inform me in how far Pine is usable on a SCO UNIX System. From a pine-ports document that comes with Version 3.87 of Pine, I understand that some work has been done by Ken Bobey. By the way, do you have his e-mail address? I would also like to know whether there is a binary version of pine for SCO Unix 3.2, version 4.2. ( I am without a compiler on my system.) Before hand thanks for your help Andries Algera ITU Americas Office Brasilia - Brazil ph: +5561 212 7377 fax: +5561 226 5061 Internet: algera@itu.br From owner-pine-info@cac.washington.edu Fri Feb 11 09:28:40 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07092; Fri, 11 Feb 94 09:28:40 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14197; Fri, 11 Feb 94 09:02:18 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from stimpy.acofi.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14191; Fri, 11 Feb 94 09:02:13 -0800 Received: by stimpy.acofi.edu (1.37.109.7/16.2) id AA27510; Fri, 11 Feb 94 09:59:22 -0700 Date: Fri, 11 Feb 1994 09:57:30 -0600 (MDT) From: Eldon Cutlip Subject: Please Unsubscribe me To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I tried to unsubscribe and got the response that there was no pine-info list. Please unsubcribe me. Thanks. From owner-pine-info@cac.washington.edu Fri Feb 11 10:11:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08554; Fri, 11 Feb 94 10:11:02 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07731; Fri, 11 Feb 94 09:52:11 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from unamvm1.dgsca.unam.mx by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07725; Fri, 11 Feb 94 09:52:08 -0800 Received: by unamvm1.dgsca.unam.mx (5.57/Ultrix3.0-C) id AA15813; Fri, 11 Feb 94 11:48:21 -0600 Date: Fri, 11 Feb 1994 11:39:04 -0600 (CST) From: "Isaias Callejas Mancilla." Reply-To: "Isaias Callejas Mancilla." Subject: Re: Spool Cleanup To: Paul Ribeiro Cc: Info Pine In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 11 Feb 1994, Paul Ribeiro wrote: > This isn't a pine question but I'm interested in how mail managers > deal with end of semester cleanups and people who love to keep all > their mail in their inbox. Do you run a nightly job to remove mail > that is more than xx days old? > many thanks, > /P > Hi Paul, type "man find" on your UNIX System and you can use instructions as: find /usr/spool/mail -atime +7 -exec rm {} \; and found solution to you problem.. NOTE: Remember as good administrator to back before of delete... Later.. /#### E. Isaias Callejas M. /# /######## Electronic Mail System Administration /## /########## Coordination of Computing Services ### /## ### Academic Computing, National University of Mexico ### ######### ### ================================================== ### ##/ ### University City, Mexico D.F. ##########/ ##/ E-mail : isma@redvax1.dgsca.unam.mx ########/ #/ Phone : (5)6 22 85 22 << MIME is Welcome!!! >> ####/ From owner-pine-info@cac.washington.edu Fri Feb 11 10:56:55 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09981; Fri, 11 Feb 94 10:56:55 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15940; Fri, 11 Feb 94 10:35:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from cs1.bradley.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15925; Fri, 11 Feb 94 10:34:59 -0800 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA07952; Fri, 11 Feb 94 12:34:50 CST Date: Fri, 11 Feb 1994 12:34:49 -0600 (CST) From: Matt Simmons Subject: Re: Commas To: Adam J Weitzman Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, Adam J Weitzman wrote: > On Fri, 11 Feb 1994, Philip Hazel wrote: > > Why won't pine accept commas in file names? They are relatively common in > > file names on Unix... Is there a quoting mechanism that I have overlooked? > This is news to me. I have been around UNIX for almost 8 years and I have > maybe once or twice only ever seen a filename with a comma in it. But if Have you/do you use RCS? > you really need to include it, you can always go "To files" after the > "Read File" part and bring it in that way. > I don't know why Pine won't let you tyoe it in, though. Because pine uses the , as a delimeter between files to be included. Thus it thinks input.c,v (the RCS file for input.c) is really a request to include input.c and v. Devoted _n______________________________________________ _________________ Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| =========\ Walt Disney World Monorail System || LCA _____\________________________________________________||_________________ __/ This highway's in perfect shape. Quick! Thank god I'm not a _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) From owner-pine-info@cac.washington.edu Fri Feb 11 11:33:36 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11287; Fri, 11 Feb 94 11:33:36 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09034; Fri, 11 Feb 94 11:12:10 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from tomobiki-cho.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09028; Fri, 11 Feb 94 11:12:08 -0800 Received: from Ikkoku-Kan.Panda.COM by Tomobiki-Cho.CAC.Washington.EDU (NX5.67d/UW-NDC Revision: 2.27.MRC ) id AA12461; Fri, 11 Feb 94 11:11:59 -0800 Received: by Ikkoku-Kan.Panda.COM (NX5.67c/UW-NDC/Panda Revision: 2.27.MRC ) id AA28154; Fri, 11 Feb 94 11:11:53 -0800 Date: Fri, 11 Feb 1994 11:11:52 -0800 (PST) From: Mark Crispin Subject: Re: imapd version with pine 3.89 To: Alan Thew Cc: pine-info@cac.washington.edu In-Reply-To: <"liverbird..102:11.01.94.11.02.17"@liverbird.liverpool.ac.uk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, Alan Thew wrote: > The source says that it's version 7.5(72). How does this correspond > to the imapd version number listed on the ftp site e.g. 3.1 ? The 3.1 version number is the version of the IMAP toolkit, which includes many components besides imapd, each with its own version number. 3.1 is the last frozen release; 3.2 is the current development version (and changes regularly). From owner-pine-info@cac.washington.edu Fri Feb 11 11:37:40 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11456; Fri, 11 Feb 94 11:37:40 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09022; Fri, 11 Feb 94 11:11:23 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from flipper.pvv.unit.no by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09016; Fri, 11 Feb 94 11:11:19 -0800 Received: from localhost (agulbra@localhost) by flipper.pvv.unit.no (8.6.5/8.6.5) id UAA24430; Fri, 11 Feb 1994 20:09:23 +0100 From: Arnt Gulbrandsen Message-Id: <199402111909.UAA24430@flipper.pvv.unit.no> Subject: Re: Spool Cleanup To: isma@redvax1.dgsca.unam.mx Date: Fri, 11 Feb 1994 20:09:21 +0100 (MET) Cc: pribeiro@hermes.acs.ryerson.ca, pine-info@cac.washington.edu In-Reply-To: from "Isaias Callejas Mancilla." at Feb 11, 94 11:39:04 am X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 302 > > Do you run a nightly job to remove mail > > that is more than xx days old? > > find /usr/spool/mail -atime +7 -exec rm {} \; > > and found solution to you problem.. And delete even new messages? Not a good idea. Ask archie about a program called mailclean, that's a better solution. --Arnt From owner-pine-info@cac.washington.edu Fri Feb 11 12:29:02 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13307; Fri, 11 Feb 94 12:29:02 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17545; Fri, 11 Feb 94 12:11:52 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from saturn.soils.umn.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17539; Fri, 11 Feb 94 12:11:46 -0800 Received: by saturn.soils.umn.edu (4.1) id AA22554; Fri, 11 Feb 94 14:10:06 CST Date: Fri, 11 Feb 94 14:10:06 CST From: "John Ladwig" Message-Id: <9402112010.AA22554@saturn.soils.umn.edu> To: Matt Simmons Cc: Adam J Weitzman , Pine Mailing List Subject: Re: Commas In-Reply-To: Matt Simmons's message of 11 February 1994 References: >>>>> On Fri, 11 Feb 1994 12:34:49 -0600 (CST), Matt Simmons said: Matt> On Fri, 11 Feb 1994, Adam J Weitzman wrote: >> On Fri, 11 Feb 1994, Philip Hazel wrote: >> > Why won't pine accept commas in file names? Matt> Have you/do you use RCS? *There's* the right question... >> I don't know why Pine won't let you type it in, though. Matt> Because pine uses the , as a delimeter between files to be included. Matt> Thus it thinks input.c,v (the RCS file for input.c) is really a request Matt> to include input.c and v. Mmm... Seems a reasonable choice for those *not* used to *NIX, since it follows mailer recipient semantics, but shell semantics would suggest whitespace as a delimiter. What thinkest thou, O Pine developers? -jml From owner-pine-info@cac.washington.edu Fri Feb 11 13:31:06 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15522; Fri, 11 Feb 94 13:31:06 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11003; Fri, 11 Feb 94 13:14:25 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from turtle.mcc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10997; Fri, 11 Feb 94 13:14:23 -0800 Received: from avarice.mcc.com by turtle.mcc.com (4.1/isd-master_921116_15:19) id AA22151; Fri, 11 Feb 94 15:14:12 CST Received: by avarice.mcc.com (4.1/isd-other_920825_17:05) id AA19894; Fri, 11 Feb 94 15:14:09 CST Date: Fri, 11 Feb 1994 15:14:08 -0600 (CST) From: Chris Garrigues Subject: Re: Commas To: John Ladwig Cc: Matt Simmons , Adam J Weitzman , Pine Mailing List In-Reply-To: <9402112010.AA22554@saturn.soils.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, John Ladwig wrote: > >>>>> On Fri, 11 Feb 1994 12:34:49 -0600 (CST), Matt Simmons said: > Mmm... Seems a reasonable choice for those *not* used to *NIX, since > it follows mailer recipient semantics, but shell semantics would > suggest whitespace as a delimiter. > > What thinkest thou, O Pine developers? I'm not a pine developer, but my vote is to require the comma be quoted, probably with a backslash. This way non-Unix geeks won't get screwed by trying to use a comma in a place that is perfectly reasonable, and Unix geeks will be able to figure out that a backslash is a good idea. Chris -- Chris Garrigues (MIME capable) cwg@mcc.com Microelectronics and Computer Technology Corporation +1 512 338 3328 3500 West Balcones Center Drive Fax +1 512 338 3838 Austin, TX 78759-6509 USA From owner-pine-info@cac.washington.edu Fri Feb 11 13:42:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16018; Fri, 11 Feb 94 13:42:54 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11136; Fri, 11 Feb 94 13:25:00 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from turtle.mcc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11130; Fri, 11 Feb 94 13:24:57 -0800 Received: from avarice.mcc.com by turtle.mcc.com (4.1/isd-master_921116_15:19) id AA22262; Fri, 11 Feb 94 15:24:55 CST Received: by avarice.mcc.com (4.1/isd-other_920825_17:05) id AA19911; Fri, 11 Feb 94 15:24:54 CST Date: Fri, 11 Feb 1994 15:24:53 -0600 (CST) From: Chris Garrigues Subject: Pico is not quite emacs To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Am I the only one who has a problem with editors which are *almost* emacs, but not quite? One problem I have with pine is that it's very common for me to ^P into a message that I'm replying to and insert text in the middle. I always want to use ^O for this because I've been doing it that way for ten years. Needless to say, when I type ^O, I am surprised every time. Also, as I was editing the above paragraph, three (count them) three times, I tried to use ^K as if I were in emacs. Was there a decision made that the added difficutly of typing ^A^K over simply ^K was sufficient to warrant disallowing the functionality of emacs's ^K? The minor frustration I feel every time I type ^K expands when I try to clean up by typing ^Y. And, as long as I'm picking nits, I'd like ^L to center the current line rather than do a simple refresh. Any thoughts? Chris -- Chris Garrigues (MIME capable) cwg@mcc.com Microelectronics and Computer Technology Corporation +1 512 338 3328 3500 West Balcones Center Drive Fax +1 512 338 3838 Austin, TX 78759-6509 USA From owner-pine-info@cac.washington.edu Fri Feb 11 15:21:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19727; Fri, 11 Feb 94 15:21:50 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20634; Fri, 11 Feb 94 15:07:26 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from yarrina.connect.com.au by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20628; Fri, 11 Feb 94 15:07:22 -0800 Received: from werple.apana.org.au by yarrina.connect.com.au with SMTP id AA04572 (5.67b8/IDA-1.5 for ); Sat, 12 Feb 1994 10:06:55 +1100 Received: from bushwire.apana.org.au (markd@bushwire.apana.org.au [192.188.107.58]) by werple.apana.org.au (8.6.5/8.6.5) with ESMTP id KAA10903 for ; Sat, 12 Feb 1994 10:06:42 +1100 Received: (from markd@localhost) by bushwire.apana.org.au (8.6.6.Beta5/8.6.6.Beta5-bw1) id KAA26399; Sat, 12 Feb 1994 10:06:39 +1100 To: apana-lists-mail-pine@apana.org.au Path: not-for-mail From: markd@bushwire.apana.org.au (Mark Delany) Newsgroups: apana.lists.mail.pine Subject: Re: Pico is not quite emacs Date: 12 Feb 1994 10:06:37 +1100 Organization: APANA regional feed site - Melbourne, Australia. Lines: 15 Message-Id: <2jh31t$pos@bushwire.apana.org.au> References: In cwg@mcc.com (Chris Garrigues) writes: >Am I the only one who has a problem with editors which are *almost* >emacs, but not quite? I tend to agree with the original poster. Though I suspect that changing it now is way too late as you'll hit all those pico users. Certainly I get hit by ^K and ^Y an awful lot, especially as I use pico for small mails and switch to emacs for larger ones. Oh well. M. From owner-pine-info@cac.washington.edu Fri Feb 11 15:28:55 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20130; Fri, 11 Feb 94 15:28:55 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20716; Fri, 11 Feb 94 15:11:04 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20708; Fri, 11 Feb 94 15:11:02 -0800 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA19313; Fri, 11 Feb 94 15:10:59 -0800 Date: Fri, 11 Feb 1994 15:10:58 -0800 (PST) From: David L Miller Subject: Re: FAQ Available To: Sherry Lake Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Not yet, but we are working on one. Thanks for the request! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 10 Jan 1994, Sherry Lake wrote: > Is there a FAQ available for pine? > > Thanks > > ----- > Sherry H. Lake slake@gmu.edu > Electronic Mail Consultant > George Mason University > From owner-pine-info@cac.washington.edu Fri Feb 11 16:27:53 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22226; Fri, 11 Feb 94 16:27:53 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13613; Fri, 11 Feb 94 16:12:02 -0800 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/UW-NDC Revision: 2.30 ) id AA13606; Fri, 11 Feb 94 16:12:01 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA08697; Fri, 11 Feb 94 16:11:58 -0800 Date: Fri, 11 Feb 1994 16:11:55 -0800 (PST) From: Terry Gray Subject: Re: Pico is not quite emacs To: Chris Garrigues Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Chris, As a part-time emacs user, I am sympathetic to your frustration. Remember, however, that emacs has a semi-infinite number of commands that can be bound to a large set of keystrokes (because of ESCape... or the META key, if there are any of those keyboards still around.) In Pico we needed to live within the constraint of single control-key commands. We couldn't even use ESCape as an escape option, because we wanted arrow keys to work. We actually started with ^K being like emacs, but feedback from some of our early users suggested that this was not intuitively obvious behavior for our (original) target audience. So we changed. It has occurred to some of us that we could add an option that restored emacs-style Ctl-K behavior, and this is on the list. Ctl-O and Ctl-Y are much more difficult to deal with, because we just don't have sufficient key space. I suspect we could reduce your cognitive dissonance a bit by making it easier for emacs to be your default editor (e.g. having cursor motion into the body of the message trigger the alternate editor.) That way you'd only have to re-map your fingers when in the message header :) There are some issues in trying to do this, but we will be investigating the feasibility. We welcome all suggestions, save perhaps "Make all keybindings user-configurable..." -teg On Fri, 11 Feb 1994, Chris Garrigues wrote: > Am I the only one who has a problem with editors which are *almost* > emacs, but not quite? > > One problem I have with pine is that it's very common for me to ^P into a > message that I'm replying to and insert text in the middle. I always > want to use ^O for this because I've been doing it that way for ten > years. Needless to say, when I type ^O, I am surprised every time. > > Also, as I was editing the above paragraph, three (count them) three > times, I tried to use ^K as if I were in emacs. Was there a decision > made that the added difficutly of typing ^A^K over simply ^K was > sufficient to warrant disallowing the functionality of emacs's ^K? The > minor frustration I feel every time I type ^K expands when I try to clean > up by typing ^Y. > > And, as long as I'm picking nits, I'd like ^L to center the current line > rather than do a simple refresh. > > Any thoughts? > > Chris > > > -- > Chris Garrigues (MIME capable) cwg@mcc.com > Microelectronics and Computer Technology Corporation +1 512 338 3328 > 3500 West Balcones Center Drive Fax +1 512 338 3838 > Austin, TX 78759-6509 > USA > > From owner-pine-info@cac.washington.edu Sat Feb 12 22:22:29 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10243; Sat, 12 Feb 94 22:22:29 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01917; Sat, 12 Feb 94 21:57:36 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from soda.Berkeley.EDU by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01911; Sat, 12 Feb 94 21:57:35 -0800 Received: from localhost (hkuo@localhost) by soda.berkeley.edu (8.6.5/PHILMAIL-1.10) id VAA15124; Sat, 12 Feb 1994 21:57:30 -0800 Date: Sat, 12 Feb 1994 21:54:49 -0800 (PST) From: Henry Kuo Subject: Compile Problem on Dynix V3.2.0 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi! Everyone: I got some compile problem on Dynix V3.2.0. I don't know how to correct them. I hope I can get some help! Thanks!! ---------------------------------------------------- make args are "CC=cc" Making c-client library and mtest `mtest' is up to date. Making Imapd cd ../c-client;make `mtest' is up to date. cc -I../c-client `cat ../c-client/CFLAGS` -o imapd imapd.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` Making Pico Making Pine. cc -DDYN -O -c addrbook.c &13946 cc -DDYN -O -c addrutil.c &13948 cc -DDYN -O -c adrbklib.c &13950 13948: *** Error code 1 13946: *** Error code 1 13950: *** Error code 1 Links to executables are in bin directory: size: bin/pine not found text data bss dec hex 221184 32768 13364 267316 41434 bin/mtest 212992 32768 21524 267284 41414 bin/imapd 131072 28672 20668 180412 2c0bc bin/pico Done From owner-pine-info@cac.washington.edu Sat Feb 12 23:06:57 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10708; Sat, 12 Feb 94 23:06:57 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02196; Sat, 12 Feb 94 22:43:56 -0800 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/UW-NDC Revision: 2.30 ) id AA02190; Sat, 12 Feb 94 22:43:53 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA20514; Sat, 12 Feb 94 22:43:48 -0800 Date: Sat, 12 Feb 1994 22:43:46 -0800 (PST) From: Terry Gray Subject: Re: PC Pine under Windows To: John Stumbles Cc: Pine User Group , Pine Mission Control In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, Apologies for the delay in responding. Does this happen when PC-Pine is in the foreground, or only when it is in the background? -teg On Tue, 1 Feb 1994, John Stumbles wrote: > If I leave PC Pine (3.89) running under MS Windows, when I return to it > after a while I get the message [IMAP connection broken in reply]. > > Is this a bug? > > I'm not sure what's happening - the 'in reply' bit of the error messsage > is a bit confusing (in reply to what?). > > > John Stumbles j.d.stumbles@reading.ac.uk > University of Reading 0734 318435 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > From owner-pine-info@cac.washington.edu Sun Feb 13 03:48:21 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14079; Sun, 13 Feb 94 03:48:21 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25986; Sun, 13 Feb 94 03:36:42 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Received: from ccsg.tau.ac.il by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25982; Sun, 13 Feb 94 03:36:37 -0800 Return-Path: Date: Sun, 13 Feb 1994 13:36:23 +0200 (IST) From: Einat Bielopolski Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please, unsubscribe me ! Einat Bielopolski Computation Center Tel-Aviv University Tel_Aviv Israel From owner-pine-info@cac.washington.edu Sun Feb 13 04:01:55 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14183; Sun, 13 Feb 94 04:01:55 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03716; Sun, 13 Feb 94 03:53:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03710; Sun, 13 Feb 94 03:53:39 -0800 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA01072; Sun, 13 Feb 94 03:53:38 -0800 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 13 Feb 94 12:51:37+0100 Date: 13 Feb 94 12:51:37+0100 From: Einat Bielopolski Message-Id: <573783*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine User Group From owner-pine-info@cac.washington.edu Sun Feb 13 07:20:11 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15813; Sun, 13 Feb 94 07:20:11 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27124; Sun, 13 Feb 94 07:11:16 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shamash.cdc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27118; Sun, 13 Feb 94 07:11:13 -0800 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA25580; Sun, 13 Feb 94 09:10:28 CST Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA20104; Sun, 13 Feb 94 22:56:14 +0800 Date: Sun, 13 Feb 1994 22:56:13 +0800 (TPE) From: Ed Greshko Subject: Re: Commas To: Adam J Weitzman Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, Adam J Weitzman wrote: > This is news to me. I have been around UNIX for almost 8 years and I have > maybe once or twice only ever seen a filename with a comma in it. But if > you really need to include it, you can always go "To files" after the > "Read File" part and bring it in that way. By now you know one of the reason's for a comma in a filename. The next question. Do you try the "To files" suggestion you made? It doesn't work either. I agee with an earlier post that the comma should be quoted via backslash for us *NIX geeks. Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Sun Feb 13 07:21:56 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15869; Sun, 13 Feb 94 07:21:56 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27132; Sun, 13 Feb 94 07:11:43 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shamash.cdc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27126; Sun, 13 Feb 94 07:11:41 -0800 Received: by shamash.cdc.com (4.1/SMI-4.0/CDC1.1) id AA25584; Sun, 13 Feb 94 09:10:55 CST Received: by cosmo.twntpe.cdc.com (5.61/1.34) id AA20171; Sun, 13 Feb 94 23:07:25 +0800 Date: Sun, 13 Feb 1994 23:07:25 +0800 (TPE) From: Ed Greshko Subject: Re: Pico is not quite emacs To: Chris Garrigues Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, Chris Garrigues wrote: > Any thoughts? Yes, I know what you mean. I have the same problem when I get into a Ford Fiesta in Australia. Everything is almost the same...but there are enough differences that I get confused. I was tempted to ask Ford Australia to change their design so that it would make it easier for me. However, someone pointed out that if I wanted to use a Ford Fiesta manufactured in Australia I should get used to it and not expect Ford to change it for me...when everyone in Australia is perfectly happy with that model. :-) :-) But to be serious...if you like emacs, and are happy with emacs, then why don't you configure emacs as your alternate editor and use emacs? It would be better than trying to change pico to be like emacs...which I'm sure was never the intention. Edward M. Greshko Control Data Taiwan Voice: +886-2-715-2222 x287 6/F, 131 Nanking East Road, Section 3 FAX : +886-2-712-9197 Taipei, Taiwan R.O.C From owner-pine-info@cac.washington.edu Sun Feb 13 08:47:57 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16405; Sun, 13 Feb 94 08:47:57 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27453; Sun, 13 Feb 94 08:36:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from aau.dk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27446; Sun, 13 Feb 94 08:36:16 -0800 Received: from slam.aar-vki.dk by aau.dk with SMTP id AA09376 (5.67a8/IDA-1.4.4); Sun, 13 Feb 1994 17:36:12 +0100 Received: from vkipc22.aar-vki.dk by slam.aar-vki.dk id aa20271; 13 Feb 94 17:34 MEZ Date: Sun, 13 Feb 1994 17:34:32 PST From: Eigil Krogh Sorensen Subject: Re: PC Pine under Windows To: Terry Gray Cc: John Stumbles , Pine User Group , Pine Mission Control X-Sender: eks@slam.aar-vki.dk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I was just about to reply that I'd never seen the problem described here. Next thing that happend was I got the same errormessage [IMAP connection broken in reply] after having read a couple of e-mails more. That happend while PC-Pine was in the foreground- - Eigil On Sat, 12 Feb 1994, Terry Gray wrote: > John, > Apologies for the delay in responding. > > Does this happen when PC-Pine is in the foreground, or only when it is in > the background? > > -teg > > On Tue, 1 Feb 1994, John Stumbles wrote: > > > If I leave PC Pine (3.89) running under MS Windows, when I return to it > > after a while I get the message [IMAP connection broken in reply]. > > > > Is this a bug? > > > > I'm not sure what's happening - the 'in reply' bit of the error messsage > > is a bit confusing (in reply to what?). > > > > > > John Stumbles j.d.stumbles@reading.ac.uk > > University of Reading 0734 318435 > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > > From owner-pine-info@cac.washington.edu Sun Feb 13 09:24:33 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16708; Sun, 13 Feb 94 09:24:33 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27647; Sun, 13 Feb 94 09:15:30 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from optima.CS.Arizona.EDU by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27641; Sun, 13 Feb 94 09:15:28 -0800 Received: from wolf.CS.Arizona.EDU by optima.CS.Arizona.EDU (5.65c/15) via SMTP id AA17488; Sun, 13 Feb 1994 10:15:26 MST Received: from localhost (jdavis@localhost) by wolf.cs.arizona.edu (8.6.4/8.6.4) id KAA05094; Sun, 13 Feb 1994 10:15:25 -0700 Date: Sun, 13 Feb 1994 10:15:24 -0700 (MST) From: Jim Davis Subject: Re: Compile Problem on Dynix V3.2.0 To: Henry Kuo Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sat, 12 Feb 1994, Henry Kuo wrote: > I got some compile problem on Dynix V3.2.0. I don't know how to correct > them. I hope I can get some help! Thanks!! There were a lot of compilation problems when I tried building 3.89 on our 3.2.0 system. Since 3.07 (or thereabouts) compiled and ran fine I assume that 3.89 should be okay without too much work. I was hoping to have done it myself by now, but for my sins I've been stuck with Solaris support and haven't had time to work on it. -- Jim Davis | "He can eat an entire case of pudding cups." jdavis@cs.arizona.edu | -- Clifford Spleenhurfer From owner-pine-info@cac.washington.edu Sun Feb 13 10:58:17 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17381; Sun, 13 Feb 94 10:58:17 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05746; Sun, 13 Feb 94 10:43:36 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from soda.Berkeley.EDU by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05740; Sun, 13 Feb 94 10:43:34 -0800 Received: from localhost (hkuo@localhost) by soda.berkeley.edu (8.6.5/PHILMAIL-1.10) id KAA22337; Sun, 13 Feb 1994 10:43:29 -0800 Date: Sun, 13 Feb 1994 10:42:07 -0800 (PST) From: Henry Kuo Reply-To: Henry Kuo Subject: Dynix V3.2.0 To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Hi! Everyone, Has anyone ever compiled pine3.89 for Dynix v3.2.0? Will that be legal and ok to give me a copy? Staff in my site is not interesting in pine except users. If you could give me a copy, please send it to me and use MINE format. (I can run pine3.07 here.) Thank you very much!! =Henry= From owner-pine-info@cac.washington.edu Sun Feb 13 11:06:21 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17467; Sun, 13 Feb 94 11:06:21 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05791; Sun, 13 Feb 94 10:53:52 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from soda.Berkeley.EDU by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05785; Sun, 13 Feb 94 10:53:50 -0800 Received: from localhost (hkuo@localhost) by soda.berkeley.edu (8.6.5/PHILMAIL-1.10) id KAA22851; Sun, 13 Feb 1994 10:53:38 -0800 Date: Sun, 13 Feb 1994 10:51:33 -0800 (PST) From: Henry Kuo Reply-To: Henry Kuo Subject: Re: Compile Problem on Dynix V3.2.0 To: Jim Davis Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Sun, 13 Feb 1994, Jim Davis wrote: > There were a lot of compilation problems when I tried building 3.89 on our > 3.2.0 system. Since 3.07 (or thereabouts) compiled and ran fine I assume > that 3.89 should be okay without too much work. I was hoping to have done > it myself by now, but for my sins I've been stuck with Solaris support and > haven't had time to work on it. I don't have problem to get imapd, mtest, and pico. I got my first compile error on pine. I added /usr/types.h in os-dyn.h and the program ran thourgh. Then the second problem is the fpos_t was undefined. I added typedef unsigned long fpos_t; in the source which needed this variable. Afterwards, I got something like redeclaration of formal parameter, ptr. I don't quite understand that. Finally I gave up! I hope some one could give me a hand. ------------------------------------------------------------- Making c-client library and mtest `mtest' is up to date. Making Imapd cd ../c-client;make `mtest' is up to date. cc -I../c-client `cat ../c-client/CFLAGS` -o imapd imapd.o ../c-client/c-client.a `cat ../c-client/LDFLAGS` Making Pico Making Pine. cc -DDYN -O -c os.c &22592 "os.c", line 615: warning: illegal pointer combination, op = "os.c", line 644: warning: illegal pointer/integer combination, op = "os.c", line 680: warning: illegal pointer combination, op = "os.c", line 1181: syntax error "os.c", line 1183: redeclaration of formal parameter, ptr "os.c", line 1183: incomplete or misplaced function definition "os.c", line 1184: syntax error "os.c", line 1190: redeclaration of formal parameter, stream "os.c", line 1190: redeclaration of formal parameter, ptr "os.c", line 1192: syntax error "os.c", line 1194: redeclaration of formal parameter, ptr "os.c", line 1194: incomplete or misplaced function definition "os.c", line 1195: syntax error 22592: *** Error code 1 Make: . Stop. From owner-pine-info@cac.washington.edu Sun Feb 13 23:23:57 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24557; Sun, 13 Feb 94 23:23:57 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02365; Sun, 13 Feb 94 23:07:18 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from yarrina.connect.com.au by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02359; Sun, 13 Feb 94 23:07:15 -0800 Received: from werple.apana.org.au by yarrina.connect.com.au with SMTP id AA04340 (5.67b8/IDA-1.5 for ); Mon, 14 Feb 1994 18:06:39 +1100 Received: from localhost (eccles@localhost) by werple.apana.org.au (8.6.5/8.6.5) id SAA17083; Mon, 14 Feb 1994 18:06:23 +1100 To: apana-lists-mail-pine@apana.org.au Path: news From: eccles@werple.apana.org.au (Jon Etkins) Newsgroups: apana.lists.mail.pine Subject: Using a full 50-line screen Date: 14 Feb 1994 18:06:20 +1100 Organization: werple public-access unix, Melbourne Lines: 11 Message-Id: <2jn7tc$gln@werple.apana.org.au> Summary: PINE only uses the first 24 lines Keywords: terminal size I have changed my terminal definition to an 80x50 variant of vt100. Most things (MAN, HELP, NN, etc) now use the whole screen, but PINE and PICO steadfastly refuse to use the bottom half at all. How can I get these two to use the whole screen? -- -------------------------------------------------------------------------- Jon Etkins | "I do not avoid women, Mandrake, | but I do deny them my essence" eccles@werple.apana.org.au | - General Ripper, "Dr. Strangelove" From owner-pine-info@cac.washington.edu Sun Feb 13 23:42:16 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24784; Sun, 13 Feb 94 23:42:16 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10091; Sun, 13 Feb 94 23:27:46 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from sunstel.asu.cas.cz by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10085; Sun, 13 Feb 94 23:27:39 -0800 Received: by sunstel.asu.cas.cz (4.1/SMI-4.1) id AA06265; Mon, 14 Feb 94 08:27:27 +0100 Date: Mon, 14 Feb 1994 08:27:25 +0100 (MET) From: Petr Skoda Subject: Compression in PINE ? To: pine-info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, PINE-wizards, I was just stroken by an crazy idea, so don't take me serious, but maybe it is not crazy enough... ;-)) As the PINE has been used mostly for the processing AND SAVING of text mail and the lot of text messages in folder may become very large, what about a built-in compression and decompression routines ( I know, that the decompression can be very fast opposite to compression -- e.g ARJ). I mean by that a compressed folders (switchable by some option in .pinerc) would be used. Whole folder would be decompressed at once to some temporary file (or virtual memory) so all operations would be unaffected. Regards, ************************************************************************* * Petr Skoda Phone : +42-204-85201, ext. 361 * * Stellar Department +42-2-724525 * * Astronomical Institute CAS Fax : +42-2-881611 * * 251 65 Ondrejov e-mail: skoda@sunstel.asu.cas.cz * * Czech Republic aststel@csearn.bitnet * ************************************************************************* From owner-pine-info@cac.washington.edu Mon Feb 14 01:47:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26447; Mon, 14 Feb 94 01:47:54 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03178; Mon, 14 Feb 94 01:36:09 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from bootes.cus.cam.ac.uk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03172; Mon, 14 Feb 94 01:36:06 -0800 Received: from argala.csi.cam.ac.uk [131.111.10.23] by bootes.cus.cam.ac.uk with smtp (Smail-3.1.28.1 #115) id m0pVzib-000BzLC; Mon, 14 Feb 94 09:35 GMT Message-Id: Date: Mon, 14 Feb 1994 09:35:51 +0000 (GMT) From: Philip Hazel Subject: Re: Commas To: Chris Garrigues Cc: Matt Simmons , Adam J Weitzman , Pine Mailing List Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII X-Organisation: Computer Laboratory, Cambridge University, UK. X-Mailer: RISCOS feMail [ver 0.20-alpha] > On Fri, 11 Feb 1994, John Ladwig wrote: > I'm not a pine developer, but my vote is to require the comma be > quoted, probably with a backslash. This way non-Unix geeks won't get > screwed by trying to use a comma in a place that is perfectly > reasonable, and Unix geeks will be able to figure out that a backslash > is a good idea. If this is done, Pine should itself quote commas when suggesting file names. I started this thread after receiving a MIME-attached file, whose suggested name contained a comma. Pine put up the suggested name, but when I pressed RETURN, complained about it! Philip -- Philip Hazel University Computing Service, ph10@cus.cam.ac.uk New Museums Site, Cambridge CB2 3QG, P.Hazel@ucs.cam.ac.uk England. Phone: +44 223 334714 From owner-pine-info@cac.washington.edu Mon Feb 14 06:42:39 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29740; Mon, 14 Feb 94 06:42:39 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04802; Mon, 14 Feb 94 06:18:09 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from relay1.pipex.net by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04796; Mon, 14 Feb 94 06:18:06 -0800 Received: from Q.icl.co.uk by relay1.pipex.net with SMTP (PP) id <15117-0@relay1.pipex.net>; Mon, 14 Feb 1994 14:17:46 +0000 Received: from ming.oasis.icl.co.uk by Q.icl.co.uk (4.1/icl-2.12-server) id AA02991; Mon, 14 Feb 94 14:19:44 GMT Received: from ozz.oasis.icl.co.uk on ming.oasis.icl.co.uk id AA02866; Mon, 14 Feb 94 14:16:53 GMT Received: on ozz.oasis.icl.co.uk id AA19235; Mon, 14 Feb 94 14:19:22 GMT Date: Mon, 14 Feb 1994 14:15:30 +0000 (GMT) From: Marcus Collard Subject: Please unsubscribe. To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please unsubscribe me from the list. Regards mc@oasis.icl.co.uk From owner-pine-info@cac.washington.edu Mon Feb 14 06:46:15 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29770; Mon, 14 Feb 94 06:46:15 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12516; Mon, 14 Feb 94 06:15:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12506; Mon, 14 Feb 94 06:15:49 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <26389-0@mail.reading.ac.uk>; Mon, 14 Feb 1994 14:15:22 +0000 Date: Mon, 14 Feb 1994 14:17:41 GMT From: John Stumbles Subject: Re: Commas To: Adam J Weitzman Cc: Pine Mailing List X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 11 Feb 1994, Adam J Weitzman wrote: > On Fri, 11 Feb 1994, Philip Hazel wrote: > > > Why won't pine accept commas in file names? They are relatively common in > > file names on Unix... Is there a quoting mechanism that I have overlooked? > > This is news to me. I have been around UNIX for almost 8 years and I have > maybe once or twice only ever seen a filename with a comma in it. But if > you really need to include it, you can always go "To files" after the > "Read File" part and bring it in that way. Whilst we're on the subject (well, sort of...) why doesn't PC-PINE understand that # is legal in DOS filenames? John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Mon Feb 14 06:54:12 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29869; Mon, 14 Feb 94 06:54:12 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12562; Mon, 14 Feb 94 06:23:58 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mason1.gmu.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12556; Mon, 14 Feb 94 06:23:56 -0800 Received: by mason1.gmu.edu (5.65/DEC-Ultrix/4.3/GMUv3) id AA09497; Mon, 14 Feb 1994 09:23:54 -0500 Date: Mon, 14 Feb 1994 09:23:54 -0500 (EST) From: Sherry Lake Subject: Reading News Question To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Can you read news from pine? If not, are there any plans to do this? Thanks. --- Sherry H. Lake slake@gmu.edu Electronic Mail Consultant George Mason University From owner-pine-info@cac.washington.edu Mon Feb 14 07:01:46 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00153; Mon, 14 Feb 94 07:01:46 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12656; Mon, 14 Feb 94 06:38:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12650; Mon, 14 Feb 94 06:38:38 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <28401-0@mail.reading.ac.uk>; Mon, 14 Feb 1994 14:38:20 +0000 Date: Mon, 14 Feb 1994 14:40:41 GMT From: John Stumbles Subject: Re: Pico is not quite emacs To: Mark Delany Cc: Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: <2jh31t$pos@bushwire.apana.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On 12 Feb 1994, Mark Delany wrote: > In cwg@mcc.com (Chris Garrigues) writes: > > >Am I the only one who has a problem with editors which are *almost* > >emacs, but not quite? > > I tend to agree with the original poster. Though I suspect that > changing it now is way too late as you'll hit all those pico users. > > Certainly I get hit by ^K and ^Y an awful lot, especially as I use > pico for small mails and switch to emacs for larger ones. It's not quite WordStar either. I switch between Pico in PC-Pine and other PC editors, many of which have WS keymapping. I can get used to ^K = delete line/block, and ^U to undelete is exact WS, but then I find myself going ^X to go down a line .... But I do agree that it shouldn't be changed - that way lies madness! John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Mon Feb 14 07:30:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00409; Mon, 14 Feb 94 07:30:02 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05052; Mon, 14 Feb 94 07:04:45 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from INDIV-GW.CENT.NET by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05046; Mon, 14 Feb 94 07:04:43 -0800 Received: by individual.com (5.65c/Spike-2.1) id AA28745; Mon, 14 Feb 1994 09:59:57 -0500 Date: Mon, 14 Feb 1994 09:57:49 -0500 (EST) From: Adam J Weitzman Subject: Re: Commas To: Ed Greshko Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 13 Feb 1994, Ed Greshko wrote: > By now you know one of the reason's for a comma in a filename. And boy is my face red! > The next question. Do you try the "To files" suggestion you > made? It doesn't work either. Funny, I tried it, and it did work. I used emacs to create a short test file called hello,goodbye and was successfully able to include it into a mailing using ^R^T and cursoring to that filename. - Adam J Weitzman INDIVIDUAL, Inc. weitzman@individual.com From owner-pine-info@cac.washington.edu Mon Feb 14 08:33:27 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01941; Mon, 14 Feb 94 08:33:27 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05494; Mon, 14 Feb 94 07:57:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from turtle.mcc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05486; Mon, 14 Feb 94 07:56:54 -0800 Received: from avarice.mcc.com by turtle.mcc.com (4.1/isd-master_921116_15:19) id AA11794; Mon, 14 Feb 94 09:56:49 CST Received: by avarice.mcc.com (4.1/isd-other_920825_17:05) id AA00292; Mon, 14 Feb 94 09:56:46 CST Date: Mon, 14 Feb 1994 09:56:45 -0600 (CST) From: Chris Garrigues Reply-To: Chris Garrigues Subject: Re: Pico is not quite emacs To: Terry Gray Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Fri, 11 Feb 1994, Terry Gray wrote: > Chris, > As a part-time emacs user, I am sympathetic to your frustration. > Remember, however, that emacs has a semi-infinite number of commands that > can be bound to a large set of keystrokes (because of ESCape... or the > META key, if there are any of those keyboards still around.) > > In Pico we needed to live within the constraint of single control-key > commands. We couldn't even use ESCape as an escape option, because we > wanted arrow keys to work. I certainly understand the above issues and it would be absurd to ask for the full functionality of gnu emacs. After all, I'd love to have things like meta-C available, that I know that would be asking too much. I actually adapt fairly well to missing functionality, I just don't adapt well to different functionality. > We actually started with ^K being like emacs, but feedback from some of > our early users suggested that this was not intuitively obvious behavior > for our (original) target audience. So we changed. It has occurred to > some of us that we could add an option that restored emacs-style Ctl-K > behavior, and this is on the list. Ctl-O and Ctl-Y are much more > difficult to deal with, because we just don't have sufficient key space. > > I suspect we could reduce your cognitive dissonance a bit by making it > easier for emacs to be your default editor (e.g. having cursor motion > into the body of the message trigger the alternate editor.) That way > you'd only have to re-map your fingers when in the message header :) > There are some issues in trying to do this, but we will be investigating > the feasibility. The problem is that the functionality in the headers is very useful, so I don't really want to give that up. I think mostly I just felt like grousing a little. After all, this isn't the only "cognitive dissonance" that I suffer from: since I also use a Mac a lot, whenever I'm in gnu emacs 19, I keep expecting that if I mark a region and start typing that the marked region will magically be deleted. I don't suppose you can solve this for me. (There was a time that I was using three editors and had a problem with the escape key: One of them was teco where hitting the escape key twice executed my commands, so I got used to doing that often. Another one had escape toggle into a help screen so I kept having my screen refreshed needlessly. A third one was the real problem: in the UCSD Pascal editor escape aborted the current insertion. In short; things have been worse in the past, so I shouldn't complain too much.) > We welcome all suggestions, save perhaps "Make all keybindings > user-configurable..." > > -teg > On a more useful note: I've loaded the mime tools for emacs (available from wnoc-fuk.wide.ad.jp:pub/GNU/etc/emacs-mime-tools.shar) into my system, and it would be nice if it worked when I escaped into my alternate editor (emacs); put it in mime mode; inserted some mime stuff; and returned to pine. Chris -- Chris Garrigues (MIME capable) cwg@mcc.com Microelectronics and Computer Technology Corporation +1 512 338 3328 3500 West Balcones Center Drive Fax +1 512 338 3838 Austin, TX 78759-6509 USA From owner-pine-info@cac.washington.edu Mon Feb 14 08:39:49 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02149; Mon, 14 Feb 94 08:39:49 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05607; Mon, 14 Feb 94 08:04:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from yarrina.connect.com.au by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05601; Mon, 14 Feb 94 08:04:37 -0800 Received: from werple.apana.org.au by yarrina.connect.com.au with SMTP id AA01452 (5.67b8/IDA-1.5 for ); Tue, 15 Feb 1994 03:04:25 +1100 Received: from yarrina.connect.com.au (yarrina.connect.com.au [192.189.54.17]) by werple.apana.org.au (8.6.5/8.6.5) with SMTP id DAA28797 for ; Tue, 15 Feb 1994 03:03:47 +1100 Received: from mailhost2.cac.washington.edu by yarrina.connect.com.au with SMTP id AA01425 (5.67b8/IDA-1.5 for ); Tue, 15 Feb 1994 03:03:34 +1100 Received: from shiva2.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA29636; Mon, 14 Feb 94 08:03:18 -0800 Date: Mon, 14 Feb 1994 08:02:54 -0800 (PST) From: David L Miller Subject: Re: Using a full 50-line screen To: Jon Etkins Cc: apana-lists-mail-pine@apana.org.au In-Reply-To: <2jn7tc$gln@werple.apana.org.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jon, Try "stty rows 50 cols 80" before entering Pine. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On 14 Feb 1994, Jon Etkins wrote: > > I have changed my terminal definition to an 80x50 variant of vt100. Most > things (MAN, HELP, NN, etc) now use the whole screen, but PINE and PICO > steadfastly refuse to use the bottom half at all. > > How can I get these two to use the whole screen? > -- > -------------------------------------------------------------------------- > Jon Etkins | "I do not avoid women, Mandrake, > | but I do deny them my essence" > eccles@werple.apana.org.au | - General Ripper, "Dr. Strangelove" > From owner-pine-info@cac.washington.edu Mon Feb 14 08:51:19 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02565; Mon, 14 Feb 94 08:51:19 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05824; Mon, 14 Feb 94 08:23:13 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from aau.dk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05818; Mon, 14 Feb 94 08:23:10 -0800 Received: from slam.aar-vki.dk by aau.dk with SMTP id AA10388 (5.67a8/IDA-1.4.4 for ); Mon, 14 Feb 1994 17:23:07 +0100 Received: from vkipc22.aar-vki.dk by slam.aar-vki.dk id aa09590; 14 Feb 94 17:22 MEZ Date: Mon, 14 Feb 1994 17:21:21 PST From: Eigil Krogh Sorensen Subject: Re: Pico is not quite emacs To: Pine User Group X-Sender: eks@slam.aar-vki.dk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 14 Feb 1994, John Stumbles wrote: > On 12 Feb 1994, Mark Delany wrote: > > > In cwg@mcc.com (Chris Garrigues) writes: > > > > >Am I the only one who has a problem with editors which are *almost* > > >emacs, but not quite? > > > > I tend to agree with the original poster. Though I suspect that > > changing it now is way too late as you'll hit all those pico users. > > > > Certainly I get hit by ^K and ^Y an awful lot, especially as I use > > pico for small mails and switch to emacs for larger ones. > > > It's not quite WordStar either. I switch between Pico in PC-Pine and > other PC editors, many of which have WS keymapping. I can get used to ^K = > delete line/block, and ^U to undelete is exact WS, but then I find myself > going ^X to go down a line .... > > > But I do agree that it shouldn't be changed - that way lies madness! > > > John Stumbles j.d.stumbles@reading.ac.uk > University of Reading 0734 318435 > Whiteknights, Reading, RG6 2AF, UK > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > Add this as one more reason why not to change pico: I'm used to use elm on UNIX with vi as the editor. Please change pine to act just as vi ;-) Eigil Krogh Sorensen --------------------------------------------------------------------- Address: Water Quality Institute Science Park Aarhus 10, Gustav Wieds Vej DK-8000 Aarhus C DENMARK. Phone: +45 86 20 20 00 or +45 86 20 20 11 local 2114 Fax: +45 86 19 75 11 E-mail: eks@aar-vki.dk ---------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Mon Feb 14 09:35:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04759; Mon, 14 Feb 94 09:35:04 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14078; Mon, 14 Feb 94 08:57:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14072; Mon, 14 Feb 94 08:57:55 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA18638; Mon, 14 Feb 94 08:57:49 -0800 Date: Mon, 14 Feb 1994 08:57:48 -0800 (PST) From: David L Miller Subject: Re: Dynix V3.2.0 To: Henry Kuo Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We only have Dynix/PTX systems here, so we must depend on outside contributions for non-PTX systems. If someone will send us diffs to make Pine 3.89 run on Dynix (non-PTX) we will make every effort to roll those changes into Pine 3.90. Sorry I don't have any better news! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Sun, 13 Feb 1994, Henry Kuo wrote: > > > On Sun, 13 Feb 1994, David L Miller wrote: > > > Henry, > > > > Are you running Dynix or Dynix/PTX? They are two very different > > Dynix only. > > > operating systems with different Pine ports. If you are running PTX, use > > the "ptx" port... > > Then what can I do? > > =Henry= > > From owner-pine-info@cac.washington.edu Mon Feb 14 09:51:35 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05314; Mon, 14 Feb 94 09:51:35 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06813; Mon, 14 Feb 94 09:17:11 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06807; Mon, 14 Feb 94 09:17:09 -0800 Received: from shiva2.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA18852; Mon, 14 Feb 94 09:15:50 -0800 Date: Mon, 14 Feb 1994 09:15:50 -0800 (PST) From: David L Miller Subject: Re: Compression in PINE ? To: Petr Skoda Cc: pine-info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Petr, This has been suggested before. Our basic opinion is that disk space is cheaper than the extra CPUs we would have to buy to support compression for a given amount of raw data. If you would like to write a c-client driver for compressed mailboxes, we can probably incorporate it into the distribution. Look in c-client/mbox.c for a template you might want to start from. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 14 Feb 1994, Petr Skoda wrote: > Hi, PINE-wizards, > > I was just stroken by an crazy idea, so don't take me serious, but maybe > it is not crazy enough... ;-)) > > As the PINE has been used mostly for the processing AND SAVING of text mail > and the lot of text messages in folder may become very large, what about > a built-in compression and decompression routines ( I know, that the > decompression can be very fast opposite to compression -- e.g ARJ). > I mean by that a compressed folders (switchable by some option in .pinerc) > would be used. Whole folder would be decompressed at once to some temporary > file (or virtual memory) so all operations would be unaffected. > > Regards, > > > > > ************************************************************************* > * Petr Skoda Phone : +42-204-85201, ext. 361 * > * Stellar Department +42-2-724525 * > * Astronomical Institute CAS Fax : +42-2-881611 * > * 251 65 Ondrejov e-mail: skoda@sunstel.asu.cas.cz * > * Czech Republic aststel@csearn.bitnet * > ************************************************************************* > From owner-pine-info@cac.washington.edu Mon Feb 14 11:00:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07663; Mon, 14 Feb 94 11:00:37 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15475; Mon, 14 Feb 94 10:25:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15469; Mon, 14 Feb 94 10:25:19 -0800 Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA19321; Mon, 14 Feb 94 10:24:03 -0800 Date: Mon, 14 Feb 1994 10:24:02 -0800 (PST) From: David L Miller Subject: Re: Please unsubscribe. To: Marcus Collard Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To unsubscribe from pine-info, send a message to majordomo@cac.washington.edu containing: unsubscribe pine-info Thank you! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 14 Feb 1994, Marcus Collard wrote: > > Please unsubscribe me from the list. > > Regards > > mc@oasis.icl.co.uk > From owner-pine-info@cac.washington.edu Mon Feb 14 11:14:04 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08288; Mon, 14 Feb 94 11:14:04 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15823; Mon, 14 Feb 94 10:41:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost1.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15817; Mon, 14 Feb 94 10:41:40 -0800 Received: from shiva1.cac.washington.edu by mailhost1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA19453; Mon, 14 Feb 94 10:41:35 -0800 Date: Mon, 14 Feb 1994 10:41:34 -0800 (PST) From: David L Miller Subject: Re: Reading News Question To: Sherry Lake Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sherry, Yes, in Pine 3.89 you can *read* news, assuming you already have a .pinerc file created by another newsreader. Just set the news-collections variable in your .pinerc file to point to your NNTP server(s). The next release of Pine will include support for subscription, unsubscription, posting, etc. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 14 Feb 1994, Sherry Lake wrote: > Can you read news from pine? If not, are there any plans to do this? > > Thanks. > --- > Sherry H. Lake slake@gmu.edu > Electronic Mail Consultant > George Mason University > From owner-pine-info@cac.washington.edu Mon Feb 14 12:33:39 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10953; Mon, 14 Feb 94 12:33:39 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09516; Mon, 14 Feb 94 12:08:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from oxmail.ox.ac.uk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09510; Mon, 14 Feb 94 12:08:44 -0800 Received: from teaching.physics.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <24857-0@oxmail.ox.ac.uk>; Mon, 14 Feb 1994 20:08:20 +0000 Received: from teaching6 by teaching.physics.ox.ac.uk (NX5.67d/NX3.0M) id AA14388; Mon, 14 Feb 94 20:08:17 GMT Received: by teaching6.physics.ox.ac.uk (NX5.67d/NX3.0X) id AA04659; Mon, 14 Feb 94 20:08:15 GMT Date: Mon, 14 Feb 1994 20:08:14 +0000 (GMT) From: The PenMaster Subject: Headers To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Greetings, I have a small request to make for Pine; I know about the Reply-To: header is going to be introduced, but can we please have an option to allow us to specify our own headers (and what goes in them; whether it is always the same, or editable at the time of message composition), and whether they are included in a message or not (like bcc: in the rich header...). Also, I wholeheartedly approve of any plans to include proper News handling. If it could be based on a similar system to rtin 1.2 then that would be even better... Thanks for listening, David _ _ ==========////==================================================== / //// David Edwards: Welcome to the real world... \ || _ _ //// send mail to: || || \\\\ //// edwards%teaching.physics@ox.ac.uk || \ \\\X/// or u93dwe@ecs.ox.ac.uk / ====\XXX/========================================================= From owner-pine-info@cac.washington.edu Mon Feb 14 12:43:18 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11229; Mon, 14 Feb 94 12:43:18 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17191; Mon, 14 Feb 94 12:03:07 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from unamvm1.dgsca.unam.mx by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17185; Mon, 14 Feb 94 12:02:56 -0800 Received: by unamvm1.dgsca.unam.mx (5.57/Ultrix3.0-C) id AA14094; Mon, 14 Feb 94 13:59:47 -0600 Date: Mon, 14 Feb 1994 13:47:35 -0600 (CST) From: "Isaias Callejas Mancilla." Subject: Re: Using a full 50-line screen To: David L Miller Cc: Jon Etkins , The PINE List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 14 Feb 1994, David L Miller wrote: > Jon, > > Try "stty rows 50 cols 80" before entering Pine. > > Thanks for the request! > > --DLM > > |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 > |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) > University of Washington, Networks & Distributed Computing > 4545 15th Ave NE, Seattle WA 98105, USA > > On 14 Feb 1994, Jon Etkins wrote: > > > > > I have changed my terminal definition to an 80x50 variant of vt100. Most > > things (MAN, HELP, NN, etc) now use the whole screen, but PINE and PICO > > steadfastly refuse to use the bottom half at all. > > > > How can I get these two to use the whole screen? > > -- > > -------------------------------------------------------------------------- > > Jon Etkins | "I do not avoid women, Mandrake, > > | but I do deny them my essence" > > eccles@werple.apana.org.au | - General Ripper, "Dr. Strangelove" > > > Hi, But, then in the "pine/osdep/os-xxx.h file : =================os-xxx.h======================== /*-- Max screen pine will display on. Used to define some array sizes --*/ define MAX_SCREEN_COLS (170) define MAX_SCREEN_ROWS (200) /*---- When no screen size can be discovered this is the size used -----*/ define DEFAULT_LINES_ON_TERMINAL (24) define DEFAULT_COLUMNS_ON_TERMINAL (80) ======================================================== Do not solution the problem ??? I have this over screen more large on DECWindows emulating vt100 terminal and it's fine... Later... /#### E. Isaias Callejas M. /# /######## Electronic Mail System Administration /## /########## Coordination of Computing Services ### /## ### Academic Computing, National University of Mexico ### ######### ### ================================================== ### ##/ ### University City, Mexico D.F. ##########/ ##/ E-mail : isma@redvax1.dgsca.unam.mx ########/ #/ Phone : (5)6 22 85 22 << MIME is Welcome!!! >> ####/ From owner-pine-info@cac.washington.edu Mon Feb 14 12:48:46 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11323; Mon, 14 Feb 94 12:48:46 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17412; Mon, 14 Feb 94 12:12:45 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17402; Mon, 14 Feb 94 12:12:38 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <26541-0@mail.reading.ac.uk>; Mon, 14 Feb 1994 20:12:08 +0000 Date: Mon, 14 Feb 1994 20:14:28 GMT From: John Stumbles Subject: Re: Pico is not quite emacs To: Eigil Krogh Sorensen Cc: Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 14 Feb 1994, Eigil Krogh Sorensen wrote: > On Mon, 14 Feb 1994, John Stumbles wrote: > > > On 12 Feb 1994, Mark Delany wrote: > > > > > In cwg@mcc.com (Chris Garrigues) writes: > > > > > > >Am I the only one who has a problem with editors which are *almost* > > > >emacs, but not quite? > > > > > It's not quite WordStar either. I switch between Pico in PC-Pine and > I'm used to use elm on UNIX with vi as the editor. Please change pine to > act just as vi ;-) Now let's hear it for EDLIN! .... 8^) John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Mon Feb 14 13:54:16 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13546; Mon, 14 Feb 94 13:54:16 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18359; Mon, 14 Feb 94 13:18:59 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailhost2.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18353; Mon, 14 Feb 94 13:18:58 -0800 Received: from shiva1.cac.washington.edu by mailhost2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA01713; Mon, 14 Feb 94 13:18:40 -0800 Date: Mon, 14 Feb 1994 13:18:40 -0800 (PST) From: David L Miller Subject: Re: Headers To: The PenMaster Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII David, We are working on a way to specify extension headers, but have not come to any firm design decisions yet. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA Amiga makes it possible! On Mon, 14 Feb 1994, The PenMaster wrote: > Greetings, > I have a small request to make for Pine; I know about the > Reply-To: header is going to be introduced, but can we please have an > option to allow us to specify our own headers (and what goes in them; > whether it is always the same, or editable at the time of message > composition), and whether they are included in a message or not (like > bcc: in the rich header...). > > Also, I wholeheartedly approve of any plans to include proper > News handling. If it could be based on a similar system to rtin 1.2 then > that would be even better... > > Thanks for listening, > > David > > _ _ > ==========////==================================================== > / //// David Edwards: Welcome to the real world... \ > || _ _ //// send mail to: || > || \\\\ //// edwards%teaching.physics@ox.ac.uk || > \ \\\X/// or u93dwe@ecs.ox.ac.uk / > ====\XXX/========================================================= > From owner-pine-info@cac.washington.edu Mon Feb 14 14:36:43 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15421; Mon, 14 Feb 94 14:36:43 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11037; Mon, 14 Feb 94 14:02:41 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from aau.dk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11031; Mon, 14 Feb 94 14:02:39 -0800 Received: from slam.aar-vki.dk by aau.dk with SMTP id AA17361 (5.67a8/IDA-1.4.4 for ); Mon, 14 Feb 1994 23:02:35 +0100 Received: from vkipc22.aar-vki.dk by slam.aar-vki.dk id aa12408; 14 Feb 94 23:02 MEZ Date: Mon, 14 Feb 1994 23:00:47 PST From: Eigil Krogh Sorensen Subject: Saved mail read on PC-Pine and SCO with elm. Good ideas ? To: Pine User Group X-Sender: eks@slam.aar-vki.dk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII We are using PC-Pine with an SCO UNIX as mailserver. The mailer program on SCO is mmdf. On the SCO UNIX system we use elm as the mail reader/poster. Now it is so that PC-Pine can understand and read mails saved with elm on the SCO but elm can't understand and read mails saved with PC-Pine. The reason is that mmdf and elm saves mails in folders with a line with 4 CTRL-As before and after each mail in the folder. If these CTRL-A's are not there elm declares the folder corrupt. Does someone have a good idea about hov to solve that problem ? Of course we could read the mails in the folders with PC-Pine and resend it to ourselves and then read the incoming mail with elm. But that is a bit to crazy. Eigil Krogh Sorensen --------------------------------------------------------------------- Address: Water Quality Institute Science Park Aarhus 10, Gustav Wieds Vej DK-8000 Aarhus C DENMARK. Phone: +45 86 20 20 00 or +45 86 20 20 11 local 2114 Fax: +45 86 19 75 11 E-mail: eks@aar-vki.dk ---------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Mon Feb 14 15:48:59 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18195; Mon, 14 Feb 94 15:48:59 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12354; Mon, 14 Feb 94 15:28:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from turtle.mcc.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12348; Mon, 14 Feb 94 15:28:47 -0800 Received: from avarice.mcc.com by turtle.mcc.com (4.1/isd-master_921116_15:19) id AA18843; Mon, 14 Feb 94 17:28:46 CST Received: by avarice.mcc.com (4.1/isd-other_920825_17:05) id AA03098; Mon, 14 Feb 94 17:28:45 CST Date: Mon, 14 Feb 1994 17:28:44 -0600 (CST) From: Chris Garrigues Subject: text/enriched To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII According to the FAQ, text/enriched supersedes text/richtext, but pine only appears to support text/richtext while exmh is generating text/enriched. Can I assume that the next patch to pine will include the support of text/enriched to the same limited extent that text/richtext is currently supported? Chris Chris Garrigues (MIME capable) cwg@mcc.com Microelectronics and Computer Technology Corporation +1 512 338 3328 3500 West Balcones Center Drive Fax +1 512 338 3838 Austin, TX 78759-6509 USA From owner-pine-info@cac.washington.edu Mon Feb 14 16:16:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19018; Mon, 14 Feb 94 16:16:50 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20682; Mon, 14 Feb 94 15:56:56 -0800 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/UW-NDC Revision: 2.30 ) id AA20674; Mon, 14 Feb 94 15:56:46 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA16494; Mon, 14 Feb 94 15:55:29 -0800 Date: Mon, 14 Feb 1994 15:55:29 -0800 (PST) From: David L Miller Subject: Re: your mail To: Burzin Engineer Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Burzin, Pine does not currently have an option for alternate signatures. We are considering the addition of a "FCC-folder-name-rule" similar to the saved-msg-name-rule. If the user-domain variable in your .pinerc file is blank, Pine should use whatever is returned by your system. The issue of when to use it is kind of a hot topic, but we find it to be much safer and more predictable to always fully qualify addresses. Thanks for the requests! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 10 Feb 1994, Burzin Engineer wrote: > A few questions: > (I moved from elm to pine, my questions might reflect that) > > 1. anyway in pine for having a local signature file v/s remote signature > file? > > 2. anyway of saving outgoing message by to-field default and if folder > does not exist then put it in sent-mail? > > 3. How do you stop pine from adding the domainname to internal messages. > i.e. If I leave it blank in .pinerc then it recognizes internal mail and > expands userid to username BUT my external mail does not have my correct > return address, so people cannot reply back to me. If I add the domainname > it appends it to internal addresses also which I would prefer not to. > Any solutions? > > Thanks > > -- > Burzin N. Engineer > Teradata Database Development Center | Phone (310) 524-7513 > Decision Enabling Systems Division | Fax (310) 524-5511 > AT&T Global Information Solutions | E-Mail bne@elsegundoca.ncr.com > > > From owner-pine-info@cac.washington.edu Tue Feb 15 02:30:41 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27126; Tue, 15 Feb 94 02:30:41 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17414; Tue, 15 Feb 94 02:10:47 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from post.demon.co.uk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17408; Tue, 15 Feb 94 02:10:40 -0800 Received: from compcg.demon.co.uk by post.demon.co.uk id aa01732; 15 Feb 94 10:02 GMT Received: from compass.unity by compcg.demon.co.uk (4.1/SMI-4.1) id AA23421; Tue, 15 Feb 94 09:18:40 GMT Received: by compass.unity (5.61/1.35) id AA06071; Tue, 15 Feb 94 09:18:39 GMT Date: Tue, 15 Feb 1994 09:16:37 +0000 (WET) From: Martin Beenham Subject: Re: Reading News Question To: David L Miller Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 14 Feb 1994, David L Miller wrote: > Yes, in Pine 3.89 you can *read* news, assuming you already have a .pinerc > file created by another newsreader. Just set the news-collections > variable in your .pinerc file to point to your NNTP server(s). The next > release of Pine will include support for subscription, unsubscription, > posting, etc. And threading???...Please :) Regards, -- Martin G. Beenham "IT - what's that?" (martin@compass)|Tel +44 635 550660 Compass Computer Group, Newbury, Berks, UK RG14 5PX |Fax +44 635 521268 Internet: martin@compcg.demon.co.uk (@work) martin@aman.demon.co.uk (@home) From owner-pine-info@cac.washington.edu Tue Feb 15 06:13:00 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00474; Tue, 15 Feb 94 06:13:00 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27119; Tue, 15 Feb 94 05:51:23 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27113; Tue, 15 Feb 94 05:51:21 -0800 Received: from red.ariel.cs.yorku.ca by shivafs.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA26136; Tue, 15 Feb 94 05:51:20 -0800 Received: from green (green-srv) by ariel.cs.yorku.ca (4.1/SMI-4.1) id AA25130; Tue, 15 Feb 94 08:51:19 EST Received: by green (4.1/SMI-4.1.1) id AA27728; Tue, 15 Feb 94 08:51:18 EST Date: Tue, 15 Feb 1994 08:29:24 -0500 (EST) From: ILAN GRAIFER Subject: Re: Reading News Question To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 15 Feb 1994, Martin Beenham wrote: > On Mon, 14 Feb 1994, David L Miller wrote: > > Yes, in Pine 3.89 you can *read* news, assuming you already have a .pinerc > > file created by another newsreader. Just set the news-collections > > variable in your .pinerc file to point to your NNTP server(s). The next > > release of Pine will include support for subscription, unsubscription, > > posting, etc. > > And threading???...Please :) > I don't think pine should become a full news-reader. There are many readers that are both powerful and easy to use and which are easily obtainable on the net. I would prefer to see pine as a mail agent only, which does what it is supposed to do and doesn't try to be an all in one package. I would like to suggest adding an option of making an uuencoded attachment in addition to the MIME attachments. Many people don't have MIME, and it will be nice if it was possible to send a uuencoded file to those people from within pine. An automatic decoding would be nice as well :) Ilan -- _==| Ilan Graifer _==| )__) | )_) )___) )) cs922080@ariel.cs.yorku.ca )___) )____))_) yku00401@cawc.yorku.ca _ )____)_____))__)\ an41635@anon.penet.fi \---__|____/|___|___-\\--- ^^^^^^^^^\ oo oo oo oo /~~^^^^^^^ ~^^^^ ~~~~^^~~~~^^~~^^~~~~~ ~~^^ ~^^~ ~^~ ~^ ~^ ~^~~ ~~~^^~ From owner-pine-info@cac.washington.edu Tue Feb 15 10:44:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06600; Tue, 15 Feb 94 10:44:00 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22006; Tue, 15 Feb 94 10:12:09 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22000; Tue, 15 Feb 94 10:12:01 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pWUFX-000DQbC; Tue, 15 Feb 94 10:11 PST Date: Tue, 15 Feb 1994 10:11:54 -0700 (PDT) From: "Gayland G. Gump" Subject: Addressbooks for PINE To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I'd like to express our appreciation for the work you are doing with PINE. I believe it is of great benefit to the Internet Community. Not to appear ungreatful, but we understand that you are planning on providing multiple personal and shared addressbook capabilities in a future release of PINE. We are trying to move to an electronic office and would greatly appreciate if these capabilities were made available ASAP. In addition, we are looking for scheduling/calendar capabilities which would ideally be integrated into our mail system. We understand that these may be on you "long list". It would be great if these capabilities were given more attention sooner than later if possible. Thanks. Gayland G. Gump One of the Good Guys! From owner-pine-info@cac.washington.edu Tue Feb 15 10:45:12 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06637; Tue, 15 Feb 94 10:45:12 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22055; Tue, 15 Feb 94 10:16:37 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from cs1.bradley.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22049; Tue, 15 Feb 94 10:16:35 -0800 Received: by cs1.bradley.edu (4.1/SMI-4.1) id AA20235; Tue, 15 Feb 94 12:16:34 CST Date: Tue, 15 Feb 1994 12:16:33 -0600 (CST) From: Matt Simmons Subject: Control-D To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Would it be possible to define Control-D on the index screen and main menu as an alias to Quit? Many UNIX programs do this (ftp, lynx, Bourne shell, C-Shell) and it's become a habit to exit... zarthac@cs1.bradley.edu Matt Simmons Bradley University, Peoria, IL Found in the BU Scout Personals: "Jane--I don't want to be alone again for Valentine's Day. I want to work this out. I was just hurt that you would sleep with my best friend ... repeatedly ... in my bed. Actually, never mind. Go to hell. John" From owner-pine-info@cac.washington.edu Tue Feb 15 11:14:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07263; Tue, 15 Feb 94 11:14:08 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22433; Tue, 15 Feb 94 10:44:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22427; Tue, 15 Feb 94 10:44:11 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pWUkg-000DQZC; Tue, 15 Feb 94 10:44 PST Date: Tue, 15 Feb 1994 10:44:06 -0700 (PDT) From: John Trimble Subject: Multiple Personal and Shared Addressbooks To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to see multiple personal and shared addressbooks in the next version of pine. **************************************************************************** John Trimble VOICE: (206) 737-2039 Washington State University FAX: (206) 690-4611 1812 E. McLoughlin Blvd. Vancouver, WA 98663-3597 INTERNET: trimble@vancouver.wsu.edu **************************************************************************** From owner-pine-info@cac.washington.edu Tue Feb 15 11:40:15 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07945; Tue, 15 Feb 94 11:40:15 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22880; Tue, 15 Feb 94 11:19:24 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22874; Tue, 15 Feb 94 11:19:21 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pWVIm-000DQZC; Tue, 15 Feb 94 11:19 PST Date: Tue, 15 Feb 1994 11:19:20 -0700 (PDT) From: Laurel Cunningham Subject: To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII It would be most helpful to have multiple personal and shared addressbooks included in the next release of pine. From owner-pine-info@cac.washington.edu Tue Feb 15 12:02:45 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08549; Tue, 15 Feb 94 12:02:45 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23090; Tue, 15 Feb 94 11:35:30 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from aau.dk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23083; Tue, 15 Feb 94 11:35:27 -0800 Received: from slam.aar-vki.dk by aau.dk with SMTP id AA18317 (5.67a8/IDA-1.4.4 for ); Tue, 15 Feb 1994 20:35:23 +0100 Received: from vkipc22.aar-vki.dk by slam.aar-vki.dk id aa28113; 15 Feb 94 20:35 MEZ Date: Tue, 15 Feb 1994 20:33:28 PST From: Eigil Krogh Sorensen Subject: Announcement of new versions of Pine To: Pine User Group X-Sender: eks@slam.aar-vki.dk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Will release of new versions of pine be announced in this group ? In the docs. following pine it says that a pine version for Windows is=20 under way. I would very much like to be informed as soon as this Windows=20 pine is available. Eigil Krogh S=F8rensen --------------------------------------------------------------------- =09Address: Water Quality Institute =09=09=09Science Park Aarhus =09=09=0910, Gustav Wieds Vej =09=09=09DK-8000 Aarhus C =09=09=09DENMARK. =09Phone: +45 86 20 20 00 or =09=09=09+45 86 20 20 11 local 2114 =09Fax: +45 86 19 75 11 =09E-mail: eks@aar-vki.dk ---------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Tue Feb 15 12:28:31 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09224; Tue, 15 Feb 94 12:28:31 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01787; Tue, 15 Feb 94 11:59:15 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shivafs.cac.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01781; Tue, 15 Feb 94 11:59:13 -0800 Received: from ester.dsv.su.se by shivafs.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA28888; Tue, 15 Feb 94 11:59:12 -0800 X400-Received: by /PRMD=SUNET/ADMD=_/C=SE/; Relayed; 15 Feb 94 20:53:11+0100 Date: 15 Feb 94 20:53:11+0100 From: Laurel Cunningham Message-Id: <577275*@su-kom.dsv.su.se> To: "Pine mailer discussions group (pine-infoEcac.washington.edu)" , Pine Mailing List From owner-pine-info@cac.washington.edu Tue Feb 15 12:35:07 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09411; Tue, 15 Feb 94 12:35:07 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01960; Tue, 15 Feb 94 12:06:58 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01954; Tue, 15 Feb 94 12:06:48 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <09110-0@mail.reading.ac.uk>; Tue, 15 Feb 1994 20:06:41 +0000 Date: Tue, 15 Feb 1994 20:06:36 +0000 (GMT) From: John Stumbles Reply-To: John Stumbles Subject: Re: PC Pine under Windows To: Terry Gray Cc: Pine User Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Length: 3564 On Mon, 14 Feb 1994, Terry Gray wrote: > We've seen cases where, with certain PC configurations, PC-Pine will fail > with this error [IMAP connection broken in reply] even when in the > foreground, but in the background case, > one thing to check is the "PIF" file and how much of the CPU Pine is > allocated while in the background. I think I have mine set to 50% > (PC-Pine will try to "wake up" and check for new mail periodically, even > when in the background. If it doesn't get any cycles, I think the error > you saw would be expected.) OK, I have PCPINE running from a PIF, and it now seems not to lose its IMAP connection! Thanks for your help. For the FAQ my PIF settings are as follows (386 enhanced mode, BTW) Prog filename C:\PINE\PINE.EXE Window title Pine Optional params Startup dir C:\PINE Video memory (.) Text ( ) Low graphics ( ) High graphics Memory reqirements KB required 128 KB desired 640 EMS memory ... 0 KB limit 0 XMS memory ... 0 .... 0 Display usage (.) Full screen Execution [x] Background ( ) Windowed [ ] Exclusive [x] Close window on exit ----------------------------Advanced Settings------------------------------- Multitasking options-------------------------------------------------------- Background priority 100 Foreground priority 100 [ ] Detect Idle time Memory Options-------------------------------------------------------------- [ ] EMS memory locked [ ] XMS memory locked [ ] Uses High memory area [ ] Lock application memory Display options------------------------------------------------------------- Monitor ports [ ] text [ ] Low graphics [ ] High Graphics [x] Emulate text mode [ ] Retain Video memory Other options---------------------------------------------------------------- [x] Allow fast paste [ ] Allow close when active Reserve shortcut keys (none - I can't be bothered typing all the boxes!) Application shortcut key [None ] I did have Background priority set to 50 (not 50% BTW - 50 out of 10000) but increased it the first time PINE lost its IMAP connection (when in the background). However at the time I didn't have the Background execution box checked, which meant that PINE didn't get any time when in the background anyway (and of course it lost its connection), so I can probably put it back to 50 again. I understand that if any other application is set for Execution: Exclusive flag then it will hog the processor and prevent PINE getting timeslices, so there's still no guarantee that PINE will never lose its connection when in the background, but at least it won't do so when nothing else is happening. I'm not sure about the memory requirements - I'm pretty sure PINE doesn't use XMS or EMS, but I guess it does want 640K if it can get it...? I switched off Detect idle time as I understand (from good old Windows Secrets) that Windows can cut off the app thinking it's not doing anything if this setting is on. I wonder if PINE is Windows-aware and tells windows when it's not doing anything anyway? Maybe some Windows guru out there can suggest further tweaks. John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Tue Feb 15 14:12:21 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12994; Tue, 15 Feb 94 14:12:21 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25394; Tue, 15 Feb 94 13:50:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25380; Tue, 15 Feb 94 13:50:05 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pWXeb-000DQdC; Tue, 15 Feb 94 13:50 PST Date: Tue, 15 Feb 1994 13:50:01 -0700 (PDT) From: "Ellen C. Franklin" Subject: address book request To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Please add the capacity for multiple personal (or personnel) and shared address books to Pine. Thank you. From owner-pine-info@cac.washington.edu Tue Feb 15 14:50:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13934; Tue, 15 Feb 94 14:50:50 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04319; Tue, 15 Feb 94 14:29:38 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from turtle.mcc.com by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04313; Tue, 15 Feb 94 14:29:36 -0800 Received: from avarice.mcc.com by turtle.mcc.com (4.1/isd-master_921116_15:19) id AA01132; Tue, 15 Feb 94 16:29:34 CST Received: by avarice.mcc.com (4.1/isd-other_920825_17:05) id AA07646; Tue, 15 Feb 94 16:29:33 CST Date: Tue, 15 Feb 1994 16:29:33 -0600 (CST) From: Chris Garrigues Subject: File references To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII At our site, everybody has access to pretty much the same file system so it would actually be preferable to use Content-type: message/external-body; access-type=local-file over actually attaching the file. I'd like to be able to specify that a file is either attached or referenced under user control and also be able to set the default at our site to use references instead of attachments as it does at present. (Of course, it would be nice if this default depended on wether or not there were off-site addresses in the to list, but that's hard to do reliably due to mailing lists, etc.) Chris Chris Garrigues (MIME capable) cwg@mcc.com Microelectronics and Computer Technology Corporation +1 512 338 3328 3500 West Balcones Center Drive Fax +1 512 338 3838 Austin, TX 78759-6509 USA From owner-pine-info@cac.washington.edu Tue Feb 15 15:32:23 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15515; Tue, 15 Feb 94 15:32:23 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26661; Tue, 15 Feb 94 15:12:35 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mailgate.prod.aol.net by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA26655; Tue, 15 Feb 94 15:12:33 -0800 Received: by mailgate.prod.aol.net (1.37.109.4/16.2) id AA00173; Tue, 15 Feb 94 18:17:51 -0500 From: markgil537@aol.com X-Mailer: America Online Mailer Message-Id: <9402151817.tn213898@aol.com> To: pine-info@cac.washington.edu Date: Tue, 15 Feb 94 18:17:47 EST Subject: Wishes for Pine Improvements I love Pine! It isn't as flexible as Elm or as Mac-like as the Mac-Eudora client. Nor does it act as a client that will phone my account periodically like AOL does. Still it is a wonderful product. My students, who are local teachers, have found ways to circumvent their VMS account, which doesn't use Pine, to telnet to WSUV, which does. That's proof of its ease of use. I would like to see Pine as a Mac POP client that uses the communications toolbox, much as Eudora does. There are many advantages to reading and writing mail offline. The first is that I can't get online. there just aren't enough dialups anymore. The second is that when I do get on, the net is too slow to think and write at the same time. This is why I've started forwarding my mail to AOL from my UNIX account. I can't check my mail several times per day automatically and read and write offline. When the dialups are busy, I don't worry because I know they will eventually be free and I don't have to keep trying to get on manually. I'd also like to see multiple personal and shared addressbooks. This would help me organize my lists (e.g., class, committee, department, professional, etc.). Keep up the good work. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ | Mark G. Gillingham | Gillingh@Vancouver.WSU.edu | | WSU Vancouver | Voice- 206 737-2010 | | 1812 E McLoughlin Blvd | FAX- 206 690-4611 | | Vancouver WA 98663 | 503-228-6307 (home & FAX) | +++++++++++++++++++++++++++++++++++++++++++++ ++++++++++++ From owner-pine-info@cac.washington.edu Tue Feb 15 16:29:06 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17276; Tue, 15 Feb 94 16:29:06 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27360; Tue, 15 Feb 94 16:05:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27324; Tue, 15 Feb 94 16:04:15 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pWZkJ-000DQZC; Tue, 15 Feb 94 16:04 PST Date: Tue, 15 Feb 1994 16:04:03 -0700 (PDT) From: Raymond Pendergast Reply-To: Raymond Pendergast Subject: new release of pine To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I'd like to see multiple personal and shared address books in the new release of pine. thanks. From owner-pine-info@cac.washington.edu Tue Feb 15 16:29:14 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17290; Tue, 15 Feb 94 16:29:14 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA27025; Tue, 15 Feb 94 15:35:30 -0800 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/UW-NDC Revision: 2.30 ) id AA27019; Tue, 15 Feb 94 15:35:29 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA01791; Tue, 15 Feb 94 15:35:23 -0800 Date: Tue, 15 Feb 1994 15:35:23 -0800 (PST) From: David L Miller Subject: Re: Announcement of new versions of Pine To: Eigil Krogh Sorensen Cc: Pine User Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Yes, all new version announcements go to both pine-info and pine-announce= =20 mailing lists. |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Eigil Krogh Sorensen wrote: > Will release of new versions of pine be announced in this group ? >=20 > In the docs. following pine it says that a pine version for Windows is=20 > under way. I would very much like to be informed as soon as this Windows= =20 > pine is available. >=20 >=20 > Eigil Krogh S=F8rensen > --------------------------------------------------------------------- > =09Address: Water Quality Institute > =09=09=09Science Park Aarhus > =09=09=0910, Gustav Wieds Vej > =09=09=09DK-8000 Aarhus C > =09=09=09DENMARK. >=20 > =09Phone: +45 86 20 20 00 or > =09=09=09+45 86 20 20 11 local 2114 >=20 > =09Fax: +45 86 19 75 11 >=20 > =09E-mail: eks@aar-vki.dk > ---------------------------------------------------------------------- >=20 From owner-pine-info@cac.washington.edu Tue Feb 15 16:31:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17391; Tue, 15 Feb 94 16:31:37 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05726; Tue, 15 Feb 94 16:00:26 -0800 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/UW-NDC Revision: 2.30 ) id AA05711; Tue, 15 Feb 94 15:59:40 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.29 ) id AA02293; Tue, 15 Feb 94 15:57:44 -0800 Date: Tue, 15 Feb 1994 15:57:43 -0800 (PST) From: David L Miller Subject: Re: File references To: Chris Garrigues Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Chris, We plan to add support for message/external-body in a future release of Pine. Thanks for the suggestion! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Chris Garrigues wrote: > At our site, everybody has access to pretty much the same file system so > it would actually be preferable to use > > Content-type: message/external-body; access-type=local-file > > over actually attaching the file. I'd like to be able to specify that a > file is either attached or referenced under user control and also be able > to set the default at our site to use references instead of attachments > as it does at present. (Of course, it would be nice if this default > depended on wether or not there were off-site addresses in the to list, > but that's hard to do reliably due to mailing lists, etc.) > > Chris > > > Chris Garrigues (MIME capable) cwg@mcc.com > Microelectronics and Computer Technology Corporation +1 512 338 3328 > 3500 West Balcones Center Drive Fax +1 512 338 3838 > Austin, TX 78759-6509 USA > From owner-pine-info@cac.washington.edu Tue Feb 15 16:47:50 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17843; Tue, 15 Feb 94 16:47:50 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06311; Tue, 15 Feb 94 16:32:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from ciao.trail.bc.ca by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06305; Tue, 15 Feb 94 16:31:59 -0800 Received: from [142.231.5.102] by ciao (4.1/SMI-4.1) id AA01802; Tue, 15 Feb 94 16:33:29 PST Date: Tue, 15 Feb 94 16:33:24 PST Message-Id: <9402160033.AA01802@ciao> To: pine-info@cac.washington.edu From: mshowers@ciao.trail.bc.ca (Michael Showers) Subject: File Access How can I stop users from move about in our file system? They can use the "attach" feature to "go to files", and roam freely. Granted, they can't do much, but one student just tried to mail a "core". All ideas freely accepted. Michael Showers | 2079-Columbia Ave. Computer Systems Manager | Trail, British Columbia School District No. 11 (Trail) | CANADA V1R-1K7 mshowers@CIAO.trail.bc.ca | voice: (604) 368-2234 -- A.K.A. The Technical Connection for the CIAO! Free-Net -- /\ /\ /\ / \^^^/\/ /^^^^\ ^^^^^^ It's great in the Kootenays. ---------------------------------------------------- From owner-pine-info@cac.washington.edu Tue Feb 15 17:18:17 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19272; Tue, 15 Feb 94 17:18:17 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28035; Tue, 15 Feb 94 16:59:14 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mhc.mtholyoke.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28029; Tue, 15 Feb 94 16:59:12 -0800 Received: by mhc.mtholyoke.edu (5.65/Ultrix4.3a_931226.03) id AA09847; Tue, 15 Feb 1994 19:59:03 -0500 Date: Tue, 15 Feb 1994 19:59:02 -0500 (EST) From: "Michael A. Crowley" Subject: Re: File Access To: Michael Showers Cc: pine-info@cac.washington.edu In-Reply-To: <9402160033.AA01802@ciao> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 15 Feb 1994, Michael Showers wrote: > Date: Tue, 15 Feb 94 16:33:24 PST > From: Michael Showers > To: pine-info@cac.washington.edu > Subject: File Access > > How can I stop users from move about in our file system? > > They can use the "attach" feature to "go to files", and roam freely. > Granted, they can't do much, but one student just tried to mail a "core". > > All ideas freely accepted. Seems like if someone has read permissions, they should be able to move there. Don't try to overcontrol for the low probability event. mike From owner-pine-info@cac.washington.edu Tue Feb 15 17:19:18 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19329; Tue, 15 Feb 94 17:19:18 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28060; Tue, 15 Feb 94 17:00:37 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from hopi.dtcc.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28054; Tue, 15 Feb 94 17:00:33 -0800 Received: by hopi.dtcc.edu (5.4R2.10/200.1.1.4) id AA14927; Tue, 15 Feb 1994 20:00:30 -0500 Date: Tue, 15 Feb 1994 19:52:11 -0500 (EST) From: Ken Weaverling Subject: Security enhancement request... To: Pine Mailing List Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I have just been the victim of a very troubling problem. My mail directory was set to 755 permissions and many of my saved mail folders were set to 644. I also found evidence that my mail was read by others since this hole opened up. Being the sys administrator here, this is a real bad problem. I now have to go through 5 megs of saved messages, look for compromising information and correct it. To settle some fears, No, Pine was not responsible for this. Also created in my mail directory was a subdir used by Macintosh file serving software that I installed on Unix months ago. Apparently, it changed the permissions, probably based on the "Privileges" menu item on the Mac that I had checked incorrectly. Yes, this is a stupid user mistake of the highest order, especially since I should know better. But what I am suggesting is the following. Since Pine is geared towards novices (and idiots like myself), can it be made to double check access rights when opening a folder for world-read permissions and perhaps warn the user in the status window ("Warning: Your folder is set to be readable by everyone on the system")? On one hand, a MUA shouldn't have to worry about double-checking for stupid luser mistakes, but on the other hand, it might make a nice public service feature! I can't really think of many reasons why people's mail should be publically readable. If it is to be shared, it should be in a public type newsgroup or bbs type thingamajig. From owner-pine-info@cac.washington.edu Tue Feb 15 18:45:53 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20490; Tue, 15 Feb 94 18:45:53 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29083; Tue, 15 Feb 94 18:23:49 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from relay1.UU.NET by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29077; Tue, 15 Feb 94 18:23:47 -0800 Received: from world.std.com by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwdkz01966; Tue, 15 Feb 94 21:23:46 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA24645; Tue, 15 Feb 1994 21:23:43 -0500 Date: Tue, 15 Feb 1994 21:23:43 -0500 From: bzs@world.std.com (Barry Shein) Message-Id: <199402160223.AA24645@world.std.com> To: weave@hopi.dtcc.edu Cc: pine-info@cac.washington.edu In-Reply-To: Ken Weaverling's message of Tue, 15 Feb 1994 19:52:11 -0500 (EST) Subject: Security enhancement request... It would seem that a better solution to the problem you describe would be the option to save folders encrypted with some password. Then it wouldn't matter a lot if file security were compromised. Obviously it raises the issue of people forgetting their encryption keys, but I think that only argues for this not being the default. This sort of thing is becoming a more and more commonplace option in all sorts of utilities so I think people basically knows what it means and whether they want it or not (or understand in a sentence.) The only other problem it raises is the whole export regs spectre, but perhaps the right approach is the sysadmin or someone enters the command to be run on the file to encrypt or some such thing. -Barry Shein Software Tool & Die | bzs@world.std.com | uunet!world!bzs Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD From owner-pine-info@cac.washington.edu Tue Feb 15 19:13:44 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20778; Tue, 15 Feb 94 19:13:44 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29341; Tue, 15 Feb 94 18:53:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from ericir.syr.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29335; Tue, 15 Feb 94 18:53:35 -0800 Received: by ericir.syr.edu (NX5.67d/NX3.0M) id AA05486; Tue, 15 Feb 94 21:52:14 -0500 Date: Tue, 15 Feb 1994 21:52:12 -0500 (EST) From: Virtual Dave Lankes Subject: Multiple Delete/Jump to top To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I remember some mention of a multiple delete in coming versions of Pine. This is a VERY useful feature I'd like to see implemented. The ability to tag messages 1-30 for deletion. Thi might work as a command line option or like Pico's multiple line selection. Another feature that is standard in other mail programs and would make a lot of sense to me...the ability to jump to the top or bottom of a message (or file in Pico). ........................................................... : "Virtual" Dave Lankes rdlankes@ericir.syr.edu : : AskERIC Researcher "This is not your father's Internet" : : School of Information Studies Syracuse University : ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ From owner-pine-info@cac.washington.edu Tue Feb 15 19:29:09 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20931; Tue, 15 Feb 94 19:29:09 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08176; Tue, 15 Feb 94 19:13:47 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from wren.acs.csulb.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08170; Tue, 15 Feb 94 19:13:45 -0800 Received: by wren.acs.csulb.edu id AA05987 (5.65c/IDA-1.5 for pine-info@cac.washington.edu); Tue, 15 Feb 1994 19:13:39 -0800 Date: Tue, 15 Feb 1994 19:13:38 -0800 (PST) From: VampLestat Subject: Re: Security enhancement request... To: Barry Shein Cc: weave@hopi.dtcc.edu, pine-info@cac.washington.edu In-Reply-To: <199402160223.AA24645@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 15 Feb 1994, Barry Shein wrote: > It would seem that a better solution to the problem you describe would > be the option to save folders encrypted with some password. Then it > wouldn't matter a lot if file security were compromised. I think that existing utilities for secure email, namely PGP, are a better way to go that creating Yet Another Format for encryption. PGP has a number of features that make it much more secure than what the pine developers would be able to whip up. I would prefer that Pine be developed to make it easier to integrate PGP encryption and decryption by allowing the user to pipe the contents of the current message thru a filter. > The only other problem it raises is the whole export regs spectre, but > perhaps the right approach is the sysadmin or someone enters the > command to be run on the file to encrypt or some such thing. Which brings up the topic of the Clipper chip. The US governement wants to make Clipper the standard because it will be able to hold the keys to decrypt anything it wants to see. _O_ Ryan L. Watkins vamp@csulb.edu | Academic Computing Services Cal State Long Beach - Network Support | pgp key available via 'finger vamp@beach.csulb.edu' or key server From owner-pine-info@cac.washington.edu Tue Feb 15 19:45:02 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA21211; Tue, 15 Feb 94 19:45:02 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29576; Tue, 15 Feb 94 19:29:30 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from relay1.UU.NET by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29570; Tue, 15 Feb 94 19:29:26 -0800 Received: from world.std.com by relay1.UU.NET with SMTP (5.61/UUNET-internet-primary) id AAwdld21829; Tue, 15 Feb 94 22:29:15 -0500 Received: by world.std.com (5.65c/Spike-2.0) id AA15816; Tue, 15 Feb 1994 22:29:13 -0500 Date: Tue, 15 Feb 1994 22:29:13 -0500 From: bzs@world.std.com (Barry Shein) Message-Id: <199402160329.AA15816@world.std.com> To: vamp@csulb.edu Cc: weave@hopi.dtcc.edu, pine-info@cac.washington.edu In-Reply-To: VampLestat's message of Tue, 15 Feb 1994 19:13:38 -0800 (PST) Subject: Security enhancement request... From: VampLestat >I think that existing utilities for secure email, namely PGP, are a >better way to go that creating Yet Another Format for encryption. PGP >has a number of features that make it much more secure than what the pine >developers would be able to whip up. >I would prefer that Pine be developed to make it easier to integrate PGP >encryption and decryption by allowing the user to pipe the contents of >the current message thru a filter. Yes, had you read my whole note before responding you would have seen this is precisely what I said and could have saved us all this follow-up. As to PGP specifically last I heard it was still claimed to be in violation of the RSA patent. I assume, however, you are an officer of your university with fidiciary responsibilities so are able to make the determination of potential liabilities for yourself. I am such an officer of my company and have made my own decision. >Which brings up the topic of the Clipper chip. The US governement >wants to make Clipper the standard because it will be able to hold the >keys to decrypt anything it wants to see. No, actually it does not bring up the topic of the Clipper chip since this has nothing to do with Pine development except perhaps in the distant future (does Pine use any chips explicitly? Is it likely to?) My suggestion about export regs was meant only as an argument for a site-configurable command to encrypt so sites which do not have something like DES can use something else without trouble, and the pine folks don't have to worry about complying with export regulations since they wouldn't be shipping any cryptography software, only a method for incorporating your own. That would be a proper devpt issue. -Barry Shein Software Tool & Die | bzs@world.std.com | uunet!world!bzs Purveyors to the Trade | Voice: 617-739-0202 | Login: 617-739-WRLD From owner-pine-info@cac.washington.edu Tue Feb 15 20:00:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA21413; Tue, 15 Feb 94 20:00:54 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29747; Tue, 15 Feb 94 19:46:28 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from gothic.acs.csulb.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29741; Tue, 15 Feb 94 19:46:26 -0800 Received: by gothic.acs.csulb.edu id AA01794 (5.65c/IDA-1.5 for Pine Info List ); Tue, 15 Feb 1994 19:46:22 -0800 Date: Tue, 15 Feb 1994 19:46:20 -0800 (GMT-0800) From: VampLestat Subject: Re: Security enhancement request... To: Barry Shein Cc: Pine Info List In-Reply-To: <199402160329.AA15816@world.std.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 15 Feb 1994, Barry Shein wrote: > Yes, had you read my whole note before responding you would have seen > this is precisely what I said and could have saved us all this > follow-up. Excuse me, but I did indeed read your entire article. If you look back at my reply, I quoted your last section, so I had obviously read it. > As to PGP specifically last I heard it was still claimed to be in > violation of the RSA patent. Regardless of legal issues, all I'm asking is that pine be configured to allow people to use filters of thier own creation, be they PGP or just crypt. I think creating the option to pipe out the current message would be a heck of alot more useful than simple encryption of a folder. > I assume, however, you are an officer of > your university with fidiciary responsibilities so are able to make > the determination of potential liabilities for yourself. I'm a student here that happens to work as a student consultant doing network support. > No, actually it does not bring up the topic of the Clipper chip since > this has nothing to do with Pine development except perhaps in the > distant future (does Pine use any chips explicitly? Is it likely to?) I think the whole topic of encryption in the US leads to discussion of clipper. I'd rather know that my mail is indeed secure, and not able to be opened when the government feels like snooping around in it, or when someone else manages to get the keys. I'd rather hold the keys to my own mail box, thank you. > My suggestion about export regs was meant only as an argument for a > site-configurable command to encrypt so sites which do not have > something like DES can use something else without trouble, and the > pine folks don't have to worry about complying with export regulations > since they wouldn't be shipping any cryptography software, only a > method for incorporating your own. I wasnt asking that the pine developers ship copies of PGP with Pine, just that the ability to pipe the current message out to a filter program defined by the user. _O_ Ryan L. Watkins vamp@csulb.edu | Academic Computing Services Cal State Long Beach - Network Support | pgp key available via 'finger vamp@beach.csulb.edu' or key server From owner-pine-info@cac.washington.edu Wed Feb 16 03:51:07 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28220; Wed, 16 Feb 94 03:51:07 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11827; Wed, 16 Feb 94 03:26:28 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11821; Wed, 16 Feb 94 03:26:22 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <22323-0@mail.reading.ac.uk>; Wed, 16 Feb 1994 11:26:14 +0000 Date: Wed, 16 Feb 1994 11:28:49 GMT From: John Stumbles Reply-To: John Stumbles Subject: enhancement req re postponed composition To: Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I just tried to postpone composition of a message so that I could get back to my mail folder and refer to another message. I was told that another message composition had also been postponed and so I couldn't postpone the current one. I didn't know I had another one postponed, and that raises this enhancement request. I think what would be useful would be for Pine to remind me at some point that I have already postponed a composition. Not just when I start it up, because now that I can run it in a Window I leave it running, but also when I Reply to or Forward a message that puts me into the composer Alternatively, or in addition, maybe Pine could allow multiple postponed compositions (would this tie in with the proposed /Unsent flag in imap?)? John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Wed Feb 16 05:06:25 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29626; Wed, 16 Feb 94 05:06:25 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03615; Wed, 16 Feb 94 04:39:57 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from terminus.cs.umb.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03609; Wed, 16 Feb 94 04:39:55 -0800 Received: by terminus.cs.umb.edu id AA21151 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 16 Feb 1994 07:39:51 -0500 Date: Wed, 16 Feb 1994 07:39:51 -0500 From: Robert Morris Message-Id: <199402161239.AA21151@terminus.cs.umb.edu> To: vamp@csulb.edu Cc: bzs@world.std.com, weave@hopi.dtcc.edu, pine-info@cac.washington.edu In-Reply-To: (message from VampLestat on Tue, 15 Feb 1994 19:13:38 -0800 (PST)) Subject: Re: Security enhancement request... Reply-To: ram@cs.umb.edu [ Omitted: Violent agreement between vamp and bzs about encryption support in Pine ...] >> Which brings up the topic of the Clipper chip. The US governement >> wants to make Clipper the standard because it will be able to hold the >> keys to decrypt anything it wants to see. Clipper refers only to digital telephony cryptography. The computer system implementation is called Capstone. The secret NSA/NIST algorithm is Skipjack. Nothing (yet) in the current U.S. government proposals prohibits private citizens from using any encryption schemes they wish in their electronic mail or file transfers. There are plenty of good reasons for opposing the key escrow, secret algorithm and special chip proposals widely mis-referred to as the "Clipper initiative", as well as for opposing the restrictions on encryption software exports, but threat to software email encryption is probably not among them. See the Risks forum 15.47 and following, for a good discussion of the current state or peruse documents on the gopher and ftp servers of the Electronic Frontier Foundation, gopher.eff.org and ftp.eff.org. User agent support for viewing encrypted mail deserves a little more thought than simply providing hooks to external filters---which in my opinion is a Good Thing on its own. For example, automatic reply to an encrypted message should possibly be encrypted by default, with key options that permit the use of the same key or one-time key generation. Already viewed mail should possibly remain encrypted for storage, etc. etc. Of course, the best thing would be to embed a Lisp interpreter in Pine with access to messages and other internal objects. Then we could use the 20 years worth of emacs lisp contribiutions out there, including ones which deal with encryption..... Hah, hah, only serious. Bob Morris ram@cs.umb.edu From owner-pine-info@cac.washington.edu Wed Feb 16 07:24:53 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01762; Wed, 16 Feb 94 07:24:53 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04826; Wed, 16 Feb 94 07:05:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from uafhp.uark.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04806; Wed, 16 Feb 94 07:04:59 -0800 Received: from comp.uark.edu by uafhp.uark.edu with SMTP (1.37.109.4/15.6) id AA04913; Wed, 16 Feb 94 09:05:57 -0600 Received: by (5.0/SMI-SVR4) id AA16211; Wed, 16 Feb 94 09:05:15 CST Date: Wed, 16 Feb 1994 09:05:14 -0600 (CST) From: Richard Lee Subject: Re: Security enhancement request... To: Ken Weaverling Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2180 Can't the people who give out accounts on your system make sure that the .profile or .login file or whatever sets the default permissions appropriately. That's where the responsibility lies. Sure some of us who don't know what we're doing may override that (change it), but then it's our fault if our mail is readable by the world. This is not, in my view, pine's job. On Tue, 15 Feb 1994, Ken Weaverling wrote: > I have just been the victim of a very troubling problem. My mail directory > was set to 755 permissions and many of my saved mail folders were set to > 644. I also found evidence that my mail was read by others since this > hole opened up. Being the sys administrator here, this is a real bad > problem. I now have to go through 5 megs of saved messages, look for > compromising information and correct it. > > To settle some fears, No, Pine was not responsible for this. Also created > in my mail directory was a subdir used by Macintosh file serving software > that I installed on Unix months ago. Apparently, it changed the permissions, > probably based on the "Privileges" menu item on the Mac that I had checked > incorrectly. > > Yes, this is a stupid user mistake of the highest order, especially since > I should know better. > > But what I am suggesting is the following. Since Pine is geared towards > novices (and idiots like myself), can it be made to double check access > rights when opening a folder for world-read permissions and perhaps warn > the user in the status window ("Warning: Your folder is set to be readable > by everyone on the system")? > > On one hand, a MUA shouldn't have to worry about double-checking for > stupid luser mistakes, but on the other hand, it might make a nice public > service feature! I can't really think of many reasons why people's mail > should be publically readable. If it is to be shared, it should be in a > public type newsgroup or bbs type thingamajig. > > > -- Dr. Richard Lee rlee@comp.uark.edu Department of Philosophy Old Main 318 rlee@uafsysb.BITNET University of Arkansas phone: 501-575-5826 Fayetteville, AR 72701 From owner-pine-info@cac.washington.edu Wed Feb 16 07:27:21 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01805; Wed, 16 Feb 94 07:27:21 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13680; Wed, 16 Feb 94 07:03:12 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from utsw.swmed.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13674; Wed, 16 Feb 94 07:03:10 -0800 Received: from iliad.swmed.edu by UTSW.SWMED.EDU (PMDF V4.2-14 #3937) id <01H8Y4RFQI8G9EEGVY@UTSW.SWMED.EDU>; Wed, 16 Feb 1994 09:03:00 CDT Received: by iliad.swmed.edu (920330.SGI/911001.SGI) for @utsw.swmed.edu:pine-info@cac.washington.edu id AA28525; Wed, 16 Feb 94 09:10:23 -0600 Date: Wed, 16 Feb 1994 09:10:22 -0600 (CST) From: "Daniel P. Joy" Subject: Pine, IMAP with VMS and MVS? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: QUOTED-PRINTABLE Sorry if this question has been asked before - I'm new to this mailing list. I'm working on setting up a mail system for our computer center. We have Unix, Macs, and VAX's. Unix and Macs are not a problem - but can a VAX=A0act as a IMAP client and use Pine or even VMS Mail? It=20 would be nice to just use Pine. Sometime in the future this mail system might include an IBM mainframe running MVS/ESA. Is it possible to run IMAP on the IBM? (please don't laugh :) Thank you, Daniel=A0Joy Systems Manager Howard Hughes Medical Institute, UT Southwestern Medical School joy@howie.swmed.edu=09(214)648-5034 From owner-pine-info@cac.washington.edu Wed Feb 16 07:52:04 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02506; Wed, 16 Feb 94 07:52:04 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05006; Wed, 16 Feb 94 07:24:52 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from offsv1.cis.McMaster.CA by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05000; Wed, 16 Feb 94 07:24:41 -0800 Received: by offsv1.cis.mcmaster.ca id AA02166 (5.65c/IDA-1.4.4 for pine-info@cac.washington.edu); Wed, 16 Feb 1994 10:15:21 -0500 Date: Wed, 16 Feb 1994 10:15:20 -0500 (EST) From: "Carolynn Seeley ( Spring )" Subject: Pine on Solaris (fwd) To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I installed PINE 3.88 on our MUSS System in Dec. 93. MUSS is running SunOS 5.2 Generic on a SUN Sparc. Our System Analyst reports the problem below. Has anyone had a similar problem? I remember seeing dialogue on the read/write lock/unlock but don't recall the details. Thank you in advance. Your help is really appreciated. ------------------------------------------------------------------------------- Carolynn Seeley email: cseeley@mcmaster.ca Consultant, Desktop Computing Support cseeley@mcmail.cis.mcmaster.ca PINE Administrator cseeley@offsv1.cis.mcmaster.ca Computing and Information Services McMaster University, JHE-122, Hamilton, Ontario, CANADA (905) 525-9140 x27090 ------------------------------------------------------------------------------ ---------- Forwarded message ---------- Date: Wed, 16 Feb 1994 09:45:40 -0500 (EST) From: Brian Beckberger To: "Carolynn E Seeley ( Spring )" Subject: Pine on Solaris Carolynn:- There seems to be a problem using PINE on MUSS. I am not sure if the problem is with the students or a coding problem or a combination. I have a large number of defunct processes. This in itself is unusual. I have been having MUSS re-booted to clear these up once a week. Unfortunately, the occurance of these defunct processes is increasing more rapidly than before. I have traced these defunct processes back to running PINE. My request is this: Would you ask the question of the PINE support group (or the interest group) if anyone else is experiencing this problem. It looks like the process has the mail box open and another Pine process can't get control of the inbox to open for read-write. Thanks. Brian Beckberger Voice: (905) 525-9140 Ext. 24159 Software Analyst FAX: (905) 528-3773 Computing & Information Services E-Mail: brian@mcmaster.ca McMaster University, Hamilton, Ontario, Canada From owner-pine-info@cac.washington.edu Wed Feb 16 09:22:11 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05041; Wed, 16 Feb 94 09:22:11 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06066; Wed, 16 Feb 94 08:57:54 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from iris.phar.umich.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06060; Wed, 16 Feb 94 08:57:48 -0800 Received: from sun4.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA15534; Wed, 16 Feb 94 11:57:14 -0500 Date: Wed, 16 Feb 1994 11:57:15 -0500 (EST) From: Jeff Traigle Subject: Creating .pinerc for new users To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is Pine supposed to copy the system pine.conf file to the user's .pinerc file the first time it is run? If so, it doesn't appear to be doing so at my sight for some reason. Anyone care to comment? What would be really nice if there was a system pine.conf file and then a copy of a .pinerc file that can be copied to a user's directory on the first startup. That way, an admin can only put those parameters that he/she feels the user should be messing with in the user's file. Also, I just got through tracking down a problem with pre-authentication. Seems one of my users runs a small program from his .cshrc file. This apparently causes him to have to authenticate himself to the mail server. Rather annoying little quirk. I have another user who is also being required to authenticate, but I haven't tracked down the culprit in his case. I'll let you know when I do. These are both people running from SGIs in case anyone wants to know. -- +-----------------------------------------------------------------------------+ | Jeff Traigle | | Systems Administrator | +-----------------------------------------------------------------------------+ | University of Michigan University of Michigan | | College of Pharmacy Biophysics Research Division | | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | | Ann Arbor MI 48109 Ann Arbor MI 48109 | +-----------------------------------------------------------------------------+ | traigle@umich.edu Pager: (313) 617-8793 | +-----------------------------------------------------------------------------+ From owner-pine-info@cac.washington.edu Wed Feb 16 09:34:24 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05594; Wed, 16 Feb 94 09:34:24 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15049; Wed, 16 Feb 94 08:55:08 -0800 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/UW-NDC Revision: 2.30 ) id AA15043; Wed, 16 Feb 94 08:55:07 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12260; Wed, 16 Feb 94 08:54:31 -0800 Date: Wed, 16 Feb 1994 08:54:31 -0800 (PST) From: David L Miller Subject: Re: enhancement req re postponed composition To: John Stumbles Cc: Pine User Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, Currently, Pine reminds you when you enter the composer for an original composition. I think it would be terribly distracting to be prompted to resume a postponed composition on reply or forward. We do plan to implement multiple postponed compositions in the future. I don't know how or if it will tie in with the /UNSENT proposal. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 16 Feb 1994, John Stumbles wrote: > I just tried to postpone composition of a message so that I could get > back to my mail folder and refer to another message. I was told that > another message composition had also been postponed and so I couldn't > postpone the current one. I didn't know I had another one postponed, and > that raises this enhancement request. > > I think what would be useful would be for Pine to remind me at some point > that I have already postponed a composition. Not just when I start it up, > because now that I can run it in a Window I leave it running, but also > when I Reply to or Forward a message that puts me into the composer > > Alternatively, or in addition, maybe Pine could allow multiple postponed > compositions (would this tie in with the proposed /Unsent flag in imap?)? > > John Stumbles j.d.stumbles@reading.ac.uk > University of Reading 0734 318435 > Whiteknights, Reading, RG6 2AF, UK > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > From owner-pine-info@cac.washington.edu Wed Feb 16 10:15:45 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07071; Wed, 16 Feb 94 10:15:45 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06997; Wed, 16 Feb 94 09:45:52 -0800 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/UW-NDC Revision: 2.30 ) id AA06991; Wed, 16 Feb 94 09:45:51 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13653; Wed, 16 Feb 94 09:45:39 -0800 Date: Wed, 16 Feb 1994 09:45:38 -0800 (PST) From: David L Miller Subject: Re: Creating .pinerc for new users To: Jeff Traigle Cc: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jeff, Pine generates a new .pinerc from internal defaults for new users and automatically adds any entries that were not found in the original. This is to make sure that all new variables are added after upgrades. It sounds like you are on the right track with the authentication problem. Manually issuing the "rsh host /etc/rimapd" can give some clues if you are not already using that. Thanks for the report! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 16 Feb 1994, Jeff Traigle wrote: > > Is Pine supposed to copy the system pine.conf file to the user's .pinerc > file the first time it is run? If so, it doesn't appear to be doing so at > my sight for some reason. Anyone care to comment? What would be really > nice if there was a system pine.conf file and then a copy of a .pinerc > file that can be copied to a user's directory on the first startup. That > way, an admin can only put those parameters that he/she feels the user > should be messing with in the user's file. > > Also, I just got through tracking down a problem with pre-authentication. > Seems one of my users runs a small program from his .cshrc file. This > apparently causes him to have to authenticate himself to the mail server. > Rather annoying little quirk. I have another user who is also being > required to authenticate, but I haven't tracked down the culprit in his > case. I'll let you know when I do. These are both people running from > SGIs in case anyone wants to know. > -- > +-----------------------------------------------------------------------------+ > | Jeff Traigle | > | Systems Administrator | > +-----------------------------------------------------------------------------+ > | University of Michigan University of Michigan | > | College of Pharmacy Biophysics Research Division | > | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | > | Ann Arbor MI 48109 Ann Arbor MI 48109 | > +-----------------------------------------------------------------------------+ > | traigle@umich.edu Pager: (313) 617-8793 | > +-----------------------------------------------------------------------------+ > > From owner-pine-info@cac.washington.edu Wed Feb 16 10:15:49 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07081; Wed, 16 Feb 94 10:15:49 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16119; Wed, 16 Feb 94 09:53:11 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16113; Wed, 16 Feb 94 09:53:01 -0800 Received: from venus.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <20552-0@dummy1.dur.ac.uk>; Wed, 16 Feb 1994 17:52:42 +0000 Received: from vega.dur.ac.uk by venus.dur.ac.uk; Wed, 16 Feb 94 17:52:37 GMT Date: Wed, 16 Feb 1994 17:52:32 +0000 (GMT) From: Barry Cornelius Reply-To: Barry Cornelius Subject: Re: Creating .pinerc for new users To: Jeff Traigle Cc: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Length: 2208 > Also, I just got through tracking down a problem with pre-authentication. > Seems one of my users runs a small program from his .cshrc file. This > apparently causes him to have to authenticate himself to the mail server. > Rather annoying little quirk. I have another user who is also being > required to authenticate, but I haven't tracked down the culprit in his > case. I'll let you know when I do. These are both people running from > SGIs in case anyone wants to know. There are a number of reasons why the user has to type their username and password each time that they use Pine. I have tracked down the following: (1) The .cshrc file does output to the screen, e.g., it uses the echo command. The user will need to remove the appropriate command(s) from the .cshrc file. (2) The .cshrc file contains one or more of the Unix commands biff, mesg, stty. Probably the command can be moved to the .login file. The problem also occurs if the file /etc/rimapd has not been set up on the IMAP machine. This would affect all users that IMAP into that machine. The problem will also occur if the Pine code executes the wrong command when it wants to set up a remote shell from the machine running Pine to the IMAP machine. For example, if the code says that the remote shell command is /usr/bin/rsh when in fact the command on the machine running Pine is /usr/ucb/rsh or /usr/bin/remsh. Note that both of these would affect all users of Pine on the machine running Pine. If other people know of any more reasons, then I would be interested to see them. I also think it would be useful if this information were included in the intended FAQ. I think some of our users believe that user-authentication is a part of the way in which Pine works, because it has always done that whenever they use Pine. It would be nice to have more ammunition to dispel this rumour. -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Wed Feb 16 10:36:07 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07765; Wed, 16 Feb 94 10:36:07 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07512; Wed, 16 Feb 94 10:13:28 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from phar.umich.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07502; Wed, 16 Feb 94 10:13:23 -0800 Received: from sun4.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA16321; Wed, 16 Feb 94 13:12:54 -0500 Date: Wed, 16 Feb 1994 13:12:54 -0500 (EST) From: Jeff Traigle Subject: Re: Creating .pinerc for new users To: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Just found the problem with the other user's setup. His .cshrc file was missing an endif. Found it by trying to manually run rimapd with rsh as suggested earlier. -- +-----------------------------------------------------------------------------+ | Jeff Traigle | | Systems Administrator | +-----------------------------------------------------------------------------+ | University of Michigan University of Michigan | | College of Pharmacy Biophysics Research Division | | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | | Ann Arbor MI 48109 Ann Arbor MI 48109 | +-----------------------------------------------------------------------------+ | traigle@umich.edu Pager: (313) 617-8793 | +-----------------------------------------------------------------------------+ From owner-pine-info@cac.washington.edu Wed Feb 16 10:42:47 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07971; Wed, 16 Feb 94 10:42:47 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16348; Wed, 16 Feb 94 10:06:24 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from dummy1.dur.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16342; Wed, 16 Feb 94 10:06:19 -0800 Received: from venus.dur.ac.uk by dummy1.dur.ac.uk with SMTP (PP) id <21378-0@dummy1.dur.ac.uk>; Wed, 16 Feb 1994 18:05:12 +0000 Received: from vega.dur.ac.uk by venus.dur.ac.uk; Wed, 16 Feb 94 18:05:08 GMT Date: Wed, 16 Feb 1994 18:05:04 +0000 (GMT) From: Barry Cornelius Subject: Re: Pine on Solaris To: "Carolynn Seeley ( Spring )" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 2657 On Wed, 16 Feb 1994, Carolynn Seeley ( Spring ) wrote: > I installed PINE 3.88 on our MUSS System in Dec. 93. MUSS is running > SunOS 5.2 Generic on a SUN Sparc. Our System Analyst reports the problem > below. Has anyone had a similar problem? ... > ... There seems to be a problem using PINE on MUSS. I am not sure if > the problem is with the students or a coding problem or a combination. I > have a large number of defunct processes. This in itself is unusual. I > have been having MUSS re-booted to clear these up once a week. > Unfortunately, the occurance of these defunct processes is increasing > more rapidly than before. I have traced these defunct processes back to > running PINE. > My request is this: Would you ask the question of the PINE > support group (or the interest group) if anyone else is experiencing this > problem. It looks like the process has the mail box open and another > Pine process can't get control of the inbox to open for read-write. I reported a problem to the pine-info mailing list last week, but got no response. Each day I am having to delete about 10 processes left around by uses of Pine. Help! Anybody got any ideas of what's going on. The message is repeated below. Reading your description above, it would appear that my problem is different to yours. Date: Tue, 8 Feb 1994 16:45:11 +0000 (GMT) From: Barry Cornelius To: Pine Info Mailing List Subject: one rsh left around after Pine finishes We run three variants of Pine 3.89: sun for computers running SunOS 4.1.2 and SunOS 4.1.3 sol for computers running SunOS 5.2 and SunOS 5.3 hpp for computers running HP-UX 9.01 All uses of Pine on these machines use IMAP to access the user's inbox. The IMAP daemons run on a SunOS 4.1.3 computer called venus. We are using the version supplied with Pine 3.89, namely IMAP2bis Version 7.5(72). When Pine is run, it sets up two rsh processes to venus: rsh venus exec /etc/rimapd When Pine 3.89 (or 3.88) is run on a SunOS 5.2 machine, sometimes one of the two rsh processes still remains after the user has left Pine. This happens quite often during the day. But I haven't worked out why it happens on some occasions and not on others. Is this a known problem? Has anyone else seen this? -- Barry Cornelius Durham (091 or +44 91) 374 4717 Information Technology Service, IT Service Office: 374 2892 University of Durham, Durham. Fax: 374 3741 DH1 3LE, UK E-mail: Barry.Cornelius@durham.ac.uk From owner-pine-info@cac.washington.edu Wed Feb 16 10:56:14 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08446; Wed, 16 Feb 94 10:56:14 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16620; Wed, 16 Feb 94 10:28:38 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16614; Wed, 16 Feb 94 10:28:29 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <10021-0@mail.reading.ac.uk>; Wed, 16 Feb 1994 18:28:17 +0000 Date: Wed, 16 Feb 1994 18:30:35 GMT From: John Stumbles Subject: PC Pine crashes To: Pine User Group , Pine Mission Control X-Sender: suqstmbl@suma1.rdg.ac.uk Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Aargh! Just had another Pine crash - 3.89, running under windows. It did warn me that there might not be enough memory to send the message I was composing, but then it bombed out without (as far as I know) saving the message anywhere! Grrr! John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ From owner-pine-info@cac.washington.edu Wed Feb 16 11:17:57 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09420; Wed, 16 Feb 94 11:17:57 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08040; Wed, 16 Feb 94 10:53:03 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from gmlink.gmeds.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08034; Wed, 16 Feb 94 10:53:00 -0800 Received: from earth.ae.eds.com (earth.troy.eng.eds.com) by gmlink.gmeds.com with SMTP id AA19571 (InterLock SMTP Gateway 1.1 for ); Wed, 16 Feb 1994 13:52:25 -0500 Received: from majorca (majorca.troy.eng.eds.com) by earth.ae.eds.com (4.1/AE-1.0) id AA09251; Wed, 16 Feb 94 13:52:24 EST Date: Wed, 16 Feb 1994 13:53:50 -0500 (EST) From: Jason Cross Subject: Mime decoder To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there a mime decoder available for those users who receive messages with mime attachments, yet do not have a mime mailer? ciao, Jason Cross EDS Troy, Mi. From owner-pine-info@cac.washington.edu Wed Feb 16 11:18:19 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09466; Wed, 16 Feb 94 11:18:19 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17013; Wed, 16 Feb 94 10:51:28 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from suma2.rdg.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17007; Wed, 16 Feb 94 10:51:25 -0800 Received: from reading.ac.uk by mail.reading.ac.uk with SMTP - Local (PP) id <11118-0@mail.reading.ac.uk>; Wed, 16 Feb 1994 18:51:07 +0000 Date: Wed, 16 Feb 1994 18:53:25 GMT From: John Stumbles Subject: Re: enhancement req re postponed composition To: David L Miller Cc: John Stumbles , Pine User Group X-Sender: suqstmbl@suma1.rdg.ac.uk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Feb 1994, David L Miller wrote: > Currently, Pine reminds you when you enter the composer for an original > composition. I think it would be terribly distracting to be prompted to > resume a postponed composition on reply or forward. We do plan to implement > multiple postponed compositions in the future. I don't know how or if it > will tie in with the /UNSENT proposal. Thanks for the request! Thanks, I think multiple postponed composition is the way to go. Funnily enough, in composing this reply (or rather the version before, 'coz Pine crashed out and lost that message :-( - see my earlier bug report) I got a flash that I had new mail from David L Miller re: postponed composition, so I postponed and went to see your mail (it was just the other copy of this message which you'd sent to me and to the list) and then returned. Really it's all a workaround for not having a true Windows Pine, in which the index, received message viewer and composer are separate windows with multiple instances which the user can swap between. I'm not hassling you guys - I'm sure you have lives outside work :-) - just making a (wishful) observation! John Stumbles j.d.stumbles@reading.ac.uk University of Reading 0734 318435 Whiteknights, Reading, RG6 2AF, UK +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > On Wed, 16 Feb 1994, I (John Stumbles) wrote: > > > I think what would be useful would be for Pine to remind me at some point > > that I have already postponed a composition. Not just when I start it up, > > ... but also > > when I Reply to or Forward a message that puts me into the composer > > > > Alternatively, or in addition, maybe Pine could allow multiple postponed > > compositions (would this tie in with the proposed /Unsent flag in imap?)? From owner-pine-info@cac.washington.edu Wed Feb 16 11:27:03 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09764; Wed, 16 Feb 94 11:27:03 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08125; Wed, 16 Feb 94 10:59:57 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from zow44.desy.de by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08119; Wed, 16 Feb 94 10:59:52 -0800 Received: by zow44.desy.de id AA06657 (5.67a8/IDA-1.5 for Pine Information ); Wed, 16 Feb 1994 19:57:35 +0100 Date: Wed, 16 Feb 1994 19:57:34 +0100 (MET) From: Wojtek Bogusz Subject: Local sending mails To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Charset: US-ASCII X-Char-Esc: 29 Hello ! I thought it would be nice if pine would add information read from passwd when you mail to local user (with out domain name). You could have a switch in pinerc telling if you would like pine to behave in that way or not. It would be nice too having a switch for adding a domain name to the addresses. Best regards ! Wojtek From owner-pine-info@cac.washington.edu Wed Feb 16 11:30:52 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09866; Wed, 16 Feb 94 11:30:52 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08176; Wed, 16 Feb 94 11:01:17 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mojo.ots.utexas.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08170; Wed, 16 Feb 94 11:01:15 -0800 Received: by mojo.ots.utexas.edu id AA27928 (5.65+/IDA-1.3.5 for pine-info@cac.washington.edu); Wed, 16 Feb 94 13:01:14 -0600 Date: Wed, 16 Feb 94 13:01:14 -0600 From: Johnny Kwan Message-Id: <9402161901.AA27928@mojo.ots.utexas.edu> To: pine-info@cac.washington.edu Subject: move mail spool file to home directory On our network the users' incoming mail is spooled in /var/spool/mail which is NFS mounted on all client hosts. To reduce the mail server load, we would like to move the user's mail spool file to the user's home directory when the user invokes pine. I set up the mail_link with the mbox driver in building pine. But it still doesn't do what we want. Anyone knows how to accomplish that? Johnny Kwan Office of Telecommunication Services University of Texas System kwan@utexas.edu From owner-pine-info@cac.washington.edu Wed Feb 16 11:30:55 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09874; Wed, 16 Feb 94 11:30:55 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08186; Wed, 16 Feb 94 11:01:59 -0800 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/UW-NDC Revision: 2.30 ) id AA08180; Wed, 16 Feb 94 11:01:58 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15173; Wed, 16 Feb 94 11:01:51 -0800 Date: Wed, 16 Feb 1994 11:01:51 -0800 (PST) From: David L Miller Subject: Re: your mail To: Laurel Cunningham Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Laurel, Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Laurel Cunningham wrote: > It would be most helpful to have multiple personal and shared > addressbooks included in the next release of pine. > From owner-pine-info@cac.washington.edu Wed Feb 16 11:36:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10219; Wed, 16 Feb 94 11:36:08 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08355; Wed, 16 Feb 94 11:08:22 -0800 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/UW-NDC Revision: 2.30 ) id AA08349; Wed, 16 Feb 94 11:08:21 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15297; Wed, 16 Feb 94 11:08:17 -0800 Date: Wed, 16 Feb 1994 11:08:16 -0800 (PST) From: David L Miller Subject: Re: address book request To: "Ellen C. Franklin" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ellen, Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Ellen C. Franklin wrote: > Please add the capacity for multiple personal (or personnel) and shared > address books to Pine. Thank you. > From owner-pine-info@cac.washington.edu Wed Feb 16 11:39:35 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10365; Wed, 16 Feb 94 11:39:35 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17378; Wed, 16 Feb 94 11:10:25 -0800 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/UW-NDC Revision: 2.30 ) id AA17372; Wed, 16 Feb 94 11:10:24 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15342; Wed, 16 Feb 94 11:10:21 -0800 Date: Wed, 16 Feb 1994 11:10:20 -0800 (PST) From: David L Miller Subject: Re: Addressbooks for PINE To: "Gayland G. Gump" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Gayland, Thanks for the kind words! As I mentioned in a separate message, we will do our best to get multiple addressbooks implemented soon. --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Gayland G. Gump wrote: > I'd like to express our appreciation for the work you are doing with > PINE. I believe it is of great benefit to the Internet Community. Not > to appear ungreatful, but we understand that you are planning on > providing multiple personal and shared addressbook capabilities in a > future release of PINE. We are trying to move to an electronic office > and would greatly appreciate if these capabilities were made available > ASAP. In addition, we are looking for scheduling/calendar capabilities > which would ideally be integrated into our mail system. We understand > that these may be on you "long list". It would be great if these > capabilities were given more attention sooner than later if possible. > Thanks. > > Gayland G. Gump > One of the Good Guys! > From owner-pine-info@cac.washington.edu Wed Feb 16 11:41:53 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10485; Wed, 16 Feb 94 11:41:53 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17445; Wed, 16 Feb 94 11:14:22 -0800 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/UW-NDC Revision: 2.30 ) id AA17435; Wed, 16 Feb 94 11:14:19 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15464; Wed, 16 Feb 94 11:14:14 -0800 Date: Wed, 16 Feb 1994 11:14:13 -0800 (PST) From: David L Miller Subject: Re: Another place for ^C To: Richard Lee Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Richard, If you press 'V' in this situation, you will go back to the message view. With the current design of the top level screens, ^C is not really a meaningful operation. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Sun, 23 Jan 1994, Richard Lee wrote: > Sometimes ^C would be welcome where it is not available. I was > reading a letter in my inbox and wanted to print it. I don't often do > that, so I forgot what letter of the alphabet is used to print mail this > week. I remembered it wasn't "P". So I tried "L." Naturally I got into > a screen allowing me to change folders. I didn't want to be there. I > wanted to return to what I was. But no, ^C wouldn't let me do that. I > had to return to the main menu, go from there to the index, then down to > the message I was reading, then read that. A simple ^C would have been > easier. > > -- > > Dr. Richard Lee rlee@comp.uark.edu > Department of Philosophy Old Main 318 rlee@uafsysb.BITNET > University of Arkansas phone: 501-575-5826 > Fayetteville, AR 72701 > From owner-pine-info@cac.washington.edu Wed Feb 16 11:50:08 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10713; Wed, 16 Feb 94 11:50:08 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08602; Wed, 16 Feb 94 11:21:40 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mojo.ots.utexas.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08596; Wed, 16 Feb 94 11:21:38 -0800 Received: by mojo.ots.utexas.edu id AA28134 (5.65+/IDA-1.3.5 for pine-info@cac.washington.edu); Wed, 16 Feb 94 13:21:37 -0600 Date: Wed, 16 Feb 94 13:21:37 -0600 From: Johnny Kwan Message-Id: <9402161921.AA28134@mojo.ots.utexas.edu> To: pine-info@cac.washington.edu Subject: Re: move spool mail file to user home directory Regarding my previous message asking info to have pine to move the user's mail spool file to the user's home directory, after I did a "make clean" and make pine again, it works. Now the mail spool file is moved to ~/mbox after pine is run. Johnny Kwan From owner-pine-info@cac.washington.edu Wed Feb 16 12:17:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11729; Wed, 16 Feb 94 12:17:28 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18068; Wed, 16 Feb 94 11:50:50 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from gothic.acs.csulb.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18062; Wed, 16 Feb 94 11:50:48 -0800 Received: by gothic.acs.csulb.edu id AA04971 (5.65c/IDA-1.5 for Pine Info List ); Wed, 16 Feb 1994 11:50:40 -0800 Date: Wed, 16 Feb 1994 11:50:37 -0800 (GMT-0800) From: VampLestat Subject: Re: move mail spool file to home directory To: Johnny Kwan Cc: Pine Info List In-Reply-To: <9402161901.AA27928@mojo.ots.utexas.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Feb 1994, Johnny Kwan wrote: > On our network the users' incoming mail is spooled in /var/spool/mail > which is NFS mounted on all client hosts. To reduce the mail server > load, we would like to move the user's mail spool file to the user's > home directory when the user invokes pine. I set up the mail_link with > the mbox driver in building pine. But it still doesn't do what we > want. Anyone knows how to accomplish that? The must have an existing ~/mbox before pine will start moving over the mail. I accomplished this by creating an empty ~/mbox for every user with a .pinerc file and then adding an empty one to the default skeleton given to new accounts. _O_ Ryan L. Watkins vamp@csulb.edu | Academic Computing Services Cal State Long Beach - Network Support | pgp key available via 'finger vamp@beach.csulb.edu' or key server From owner-pine-info@cac.washington.edu Wed Feb 16 12:18:18 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11758; Wed, 16 Feb 94 12:18:18 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18171; Wed, 16 Feb 94 11:55:32 -0800 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/UW-NDC Revision: 2.30 ) id AA18165; Wed, 16 Feb 94 11:55:30 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16263; Wed, 16 Feb 94 11:55:27 -0800 Date: Wed, 16 Feb 1994 11:55:26 -0800 (PST) From: David L Miller Subject: Re: Control-D To: Matt Simmons Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Matt, Thanks for the suggestion! We'll put it on the list... --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Matt Simmons wrote: > Would it be possible to define Control-D on the index screen and main > menu as an alias to Quit? Many UNIX programs do this (ftp, lynx, Bourne > shell, C-Shell) and it's become a habit to exit... > > zarthac@cs1.bradley.edu Matt Simmons Bradley University, Peoria, IL > Found in the BU Scout Personals: > "Jane--I don't want to be alone again for Valentine's Day. I want to work > this out. I was just hurt that you would sleep with my best friend ... > repeatedly ... in my bed. Actually, never mind. Go to hell. John" > > From owner-pine-info@cac.washington.edu Wed Feb 16 12:20:17 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11821; Wed, 16 Feb 94 12:20:17 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09185; Wed, 16 Feb 94 11:56:47 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from optima.CS.Arizona.EDU by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09179; Wed, 16 Feb 94 11:56:45 -0800 Received: from wolf.CS.Arizona.EDU by optima.CS.Arizona.EDU (5.65c/15) via SMTP id AA08514; Wed, 16 Feb 1994 12:56:43 MST Received: from localhost (jdavis@localhost) by wolf.cs.arizona.edu (8.6.4/8.6.4) id MAA13362; Wed, 16 Feb 1994 12:56:42 -0700 Date: Wed, 16 Feb 1994 12:56:41 -0700 (MST) From: Jim Davis Reply-To: Jim Davis Subject: Re: Pine on Solaris To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Wed, 16 Feb 1994, Barry Cornelius wrote: > When Pine is run, it sets up two rsh processes to venus: > > rsh venus exec /etc/rimapd > > When Pine 3.89 (or 3.88) is run on a SunOS 5.2 machine, sometimes one of > the two rsh processes still remains after the user has left Pine. This > happens quite often during the day. But I haven't worked out why it > happens on some occasions and not on others. > > Is this a known problem? Has anyone else seen this? I've seen what might be a related problem with the 2.3 rshd. If you run truss on the stuck process and see it spinning in a 'wait() Err#10 ECHILD' loop then it's the same problem. Haven't seen anything about rshd in the Solaris patch database; maybe one of this week's socket/tcp/kernel patches will fix it. Then again, maybe not. -- Jim Davis | "I fire up the bulk eraser." jdavis@cs.arizona.edu | -- BOfH From owner-pine-info@cac.washington.edu Wed Feb 16 12:57:36 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12924; Wed, 16 Feb 94 12:57:36 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09772; Wed, 16 Feb 94 12:33:36 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from daisy.ee.und.ac.za by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09762; Wed, 16 Feb 94 12:33:28 -0800 Received: by daisy.ee.und.ac.za (/\==/\ Smail3.1.22.1 #22+apb920812.178) id m0pWsv2-0000OZC; Wed, 16 Feb 1994 22:32:24 +0200 (SAST) Date: Wed, 16 Feb 1994 22:32:16 +0200 (SAST) From: Alan Barrett Subject: Re: Mime decoder To: Jason Cross Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Is there a mime decoder available for those users who receive > messages with mime attachments, yet do not have a mime mailer? Since breaking a MIME multipart message into its component parts is very easy to do with a text editor (just look for the "--boundary" lines), I suspect that you are really looking for a base64 decoder. I have written a perl package (available from ftp://ftp.ee.und.ac.za/pub/unix/base64.pl) that includes functions for converting in all six possible directions between base64, uuencode and pure binary formats; using these functions, a simple base64 decoder is a one-line perl program: require 'base64.pl'; undef $/; $_ = <>; print &base64'b64decode($_); --apb Alan Barrett, Dept. of Electronic Eng., Univ. of Natal, Durban, South Africa RFC822: barrett@ee.und.ac.za From owner-pine-info@cac.washington.edu Wed Feb 16 13:15:29 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13821; Wed, 16 Feb 94 13:15:29 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10005; Wed, 16 Feb 94 12:48:32 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from saturn.soils.umn.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09999; Wed, 16 Feb 94 12:48:30 -0800 Received: by saturn.soils.umn.edu (4.1) id AA13025; Wed, 16 Feb 94 14:46:32 CST Date: Wed, 16 Feb 94 14:46:32 CST From: "John Ladwig" Message-Id: <9402162046.AA13025@saturn.soils.umn.edu> To: Jason Cross Cc: pine-info@cac.washington.edu Subject: Re: Mime decoder In-Reply-To: Jason Cross's message of 16 February 1994 References: >>>>> On Wed, 16 Feb 1994 13:53:50 -0500 (EST), Jason Cross said: Jason> Is there a mime decoder available for those users who receive Jason> messages with mime attachments, yet do not have a mime mailer? Metamail for *NIX or DOS, current version 2.6 to my knowledge, contains most all the program necessary to deal with MIME. This does not include graphic viewers and the like, but will create and chop up all MIME messages. Metamail is available at: ftp://thumper.bellcore.com//pub/nsb -jml From owner-pine-info@cac.washington.edu Wed Feb 16 13:38:46 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14632; Wed, 16 Feb 94 13:38:46 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10602; Wed, 16 Feb 94 13:13:21 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from iris.phar.umich.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10596; Wed, 16 Feb 94 13:13:16 -0800 Received: from sun4.phar.umich.edu by phar.umich.edu (931110.SGI.ANONFTP/2.2) id AA17759; Wed, 16 Feb 94 16:12:46 -0500 Date: Wed, 16 Feb 1994 16:12:47 -0500 (EST) From: Jeff Traigle Subject: Another pine request To: Pine Information Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Just tried using pine under a new account and noticed something else that I'd like to see come in an upcoming version. Pine currently creates the mail directory for postponed and interrupted messages. It doesn't create the directory(ies) defined by folder-collections in the .pinerc file if they don't already exist. It would be a welcome additional feature, I think. Enlightenment is appreciated on the matter. Regarding the earlier problem with the user running a program from his .cshrc file and being forced to authenticate, the person who suggested the interactive shell check was on the mark. Works like a charm now. -- +-----------------------------------------------------------------------------+ | Jeff Traigle | | Systems Administrator | +-----------------------------------------------------------------------------+ | University of Michigan University of Michigan | | College of Pharmacy Biophysics Research Division | | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | | Ann Arbor MI 48109 Ann Arbor MI 48109 | +-----------------------------------------------------------------------------+ | traigle@umich.edu Pager: (313) 617-8793 | +-----------------------------------------------------------------------------+ From owner-pine-info@cac.washington.edu Wed Feb 16 13:42:59 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14846; Wed, 16 Feb 94 13:42:59 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19820; Wed, 16 Feb 94 13:16:36 -0800 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/UW-NDC Revision: 2.30 ) id AA19812; Wed, 16 Feb 94 13:16:33 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17716; Wed, 16 Feb 94 13:16:22 -0800 Date: Wed, 16 Feb 1994 13:16:21 -0800 (PST) From: David L Miller Subject: Re: Default Folder Name Selection (PC-Pine) To: "Bill Ouchark, Networks Group, (617) 495-1271" Cc: pine-info@cac.washington.edu, ouchark@HUSC15.HARVARD.EDU In-Reply-To: <01H84ERTDGH491VSW5@HUSC15.HARVARD.EDU> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Bill, Sorry about the slow reply! This is on our to-do list for an upcoming version of Pine. Thanks for the suggestion! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 26 Jan 1994, Bill Ouchark, Networks Group, (617) 495-1271 wrote: > Is there a way in PC-Pine 3.89 to set the name of the folder > used by default for Saves? It defaults to "savemail", but as > I have a remote folder collection used as the default I would > prefer to use "saved-messages". I did notice the > "saved-msg-name-rule=" option in NEWSRC, but it doesn't appear > to have the option of choosing a specific name. > > -Bill Ouchark- From owner-pine-info@cac.washington.edu Wed Feb 16 14:20:17 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16156; Wed, 16 Feb 94 14:20:17 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20292; Wed, 16 Feb 94 13:47:33 -0800 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/UW-NDC Revision: 2.30 ) id AA20286; Wed, 16 Feb 94 13:47:32 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18208; Wed, 16 Feb 94 13:47:22 -0800 Date: Wed, 16 Feb 1994 13:47:21 -0800 (PST) From: David L Miller Subject: Re: Another pine request To: Jeff Traigle Cc: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jeff, Thanks for the suggestion! I'm not sure how quickly we will pursue this though, since we consider folder-collections to be a power-user feature, and power-users should know how to create directories ;) --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 16 Feb 1994, Jeff Traigle wrote: > > Just tried using pine under a new account and noticed something else that > I'd like to see come in an upcoming version. Pine currently creates the > mail directory for postponed and interrupted messages. It doesn't create > the directory(ies) defined by folder-collections in the .pinerc file if > they don't already exist. It would be a welcome additional feature, I > think. Enlightenment is appreciated on the matter. > > Regarding the earlier problem with the user running a program from his > .cshrc file and being forced to authenticate, the person who suggested > the interactive shell check was on the mark. Works like a charm now. > > -- > +-----------------------------------------------------------------------------+ > | Jeff Traigle | > | Systems Administrator | > +-----------------------------------------------------------------------------+ > | University of Michigan University of Michigan | > | College of Pharmacy Biophysics Research Division | > | Pharmacy Building, Room 1033 Chemistry Building, Room 3080 | > | Ann Arbor MI 48109 Ann Arbor MI 48109 | > +-----------------------------------------------------------------------------+ > | traigle@umich.edu Pager: (313) 617-8793 | > +-----------------------------------------------------------------------------+ > > From owner-pine-info@cac.washington.edu Wed Feb 16 18:34:00 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22460; Wed, 16 Feb 94 18:34:00 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24028; Wed, 16 Feb 94 18:08:01 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from shark.mel.dit.CSIRO.AU by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24022; Wed, 16 Feb 94 18:07:59 -0800 Received: by shark.mel.dit.csiro.au id AA01505 (5.65c/IDA-1.4.4/DIT-1.3 for pine-info@cac.washington.edu); Thu, 17 Feb 1994 13:08:12 +1100 Date: Thu, 17 Feb 1994 13:08:11 +1100 (DST) From: Simon McClenahan Subject: How to make pine more elm-like? To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I was a happy user of elm until I became a happier user with pine. I have elm-style-save=yes in my .pinerc , but there are other things that I miss from elm. 1) the ability to sort-tag-save messages from one mailbox to another 2) a feature that I found most desirable and is probably possible with pine but I haven't figure it out, is the automatic saving of composed or reply messages in the mailbox corresponding with the To: address, i.e. this is the line in .elm/elmrc (I think) # save messages, incoming and outbound, by login name of sender/recipient? savename = ON Any thoughts on an X interface to pine as well? :) When is the next version coming out? I have 3.89 cheers, Simon.McClenahan@mel.dit.csiro.au \CSIRO Supercomputing Support Group CSIRO Division of Information Technology\ tel: +61 3 282 2623 723 Swanston St, Carlton 3053 AUSTRALIA \ fax: +61 3 282 2600 All I ask is a chance to prove that money can't make me happy. From owner-pine-info@cac.washington.edu Wed Feb 16 18:36:56 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22505; Wed, 16 Feb 94 18:36:56 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14530; Wed, 16 Feb 94 18:15:00 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from aau.dk by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA14524; Wed, 16 Feb 94 18:14:42 -0800 Received: from slam.aar-vki.dk by aau.dk with SMTP id AA28962 (5.67a8/IDA-1.4.4 for ); Thu, 17 Feb 1994 03:13:33 +0100 Received: from vkipc22.aar-vki.dk by slam.aar-vki.dk id aa26398; 17 Feb 94 3:13 MEZ Date: Thu, 17 Feb 1994 03:11:28 PST From: Eigil Krogh Sorensen Subject: Re: Mime decoder To: Jason Cross Cc: pine-info@cac.washington.edu X-Sender: eks@slam.aar-vki.dk In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Feb 1994, Jason Cross wrote: > Is there a mime decoder available for those users who receive > messages with mime attachments, yet do not have a mime mailer? > > > ciao, > Jason Cross > EDS > Troy, Mi. > > Yes there is. It's called metamail. Metamail is used by elm if it receives mails with MIME stuff (if you configured elm to support MIME of course. Metamail does not follow elm, so search for "metamail" not "elm". Eigil Krogh Sorensen --------------------------------------------------------------------- Address: Water Quality Institute Science Park Aarhus 10, Gustav Wieds Vej DK-8000 Aarhus C DENMARK. Phone: +45 86 20 20 00 or +45 86 20 20 11 local 2114 Fax: +45 86 19 75 11 E-mail: eks@aar-vki.dk ---------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Wed Feb 16 22:04:45 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24464; Wed, 16 Feb 94 22:04:45 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25662; Wed, 16 Feb 94 21:45:15 -0800 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/UW-NDC Revision: 2.30 ) id AA25656; Wed, 16 Feb 94 21:45:14 -0800 Received: by shiva2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09877; Wed, 16 Feb 94 21:45:04 -0800 Date: Wed, 16 Feb 1994 21:45:04 -0800 (PST) From: David L Miller Subject: Re: How to make pine more elm-like? To: Simon McClenahan Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Simon, The "elm-style-save" option is now obsolete, having been replaced by a couple feature-list options. At least the first of your suggestions will be available in the next release of Pine. We do not have any current plans for an X interface, although we have toyed with the idea of some primitive mouse support, about like PC-Pine has. We are hoping to have the next release ready about late spring. Thanks for the suggestions! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 17 Feb 1994, Simon McClenahan wrote: > Hi, > I was a happy user of elm until I became a happier user with > pine. I have elm-style-save=yes in my .pinerc , but there are other > things that I miss from elm. > > 1) the ability to sort-tag-save messages from one mailbox to another > > 2) a feature that I found most desirable and is probably possible with > pine but I haven't figure it out, is the automatic saving of composed or > reply messages in the mailbox corresponding with the To: address, i.e. > this is the line in .elm/elmrc (I think) > # save messages, incoming and outbound, by login name of sender/recipient? > savename = ON > > > Any thoughts on an X interface to pine as well? :) > > > When is the next version coming out? I have 3.89 > > > cheers, > > Simon.McClenahan@mel.dit.csiro.au \CSIRO Supercomputing Support Group > CSIRO Division of Information Technology\ tel: +61 3 282 2623 > 723 Swanston St, Carlton 3053 AUSTRALIA \ fax: +61 3 282 2600 > All I ask is a chance to prove that money can't make me happy. > From owner-pine-info@cac.washington.edu Wed Feb 16 23:06:35 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25027; Wed, 16 Feb 94 23:06:35 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16305; Wed, 16 Feb 94 22:44:26 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from castor.cc.utu.fi by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16299; Wed, 16 Feb 94 22:44:23 -0800 Received: by utu.fi id <165631-3>; Thu, 17 Feb 1994 08:44:10 +0200 Date: Thu, 17 Feb 1994 08:44:07 +0200 From: Kari Sutela Subject: Re: Mime decoder To: Jason Cross Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 16 Feb 1994, Jason Cross wrote: > Is there a mime decoder available for those users who receive > messages with mime attachments, yet do not have a mime mailer? Yep, there is something called metamail. /KS From owner-pine-info@cac.washington.edu Thu Feb 17 03:19:22 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28333; Thu, 17 Feb 94 03:19:22 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17806; Thu, 17 Feb 94 02:47:22 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from mhc.mtholyoke.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17800; Thu, 17 Feb 94 02:47:20 -0800 Received: by mhc.mtholyoke.edu (5.65/Ultrix4.3a_931226.03) id AA07188; Thu, 17 Feb 1994 05:47:16 -0500 Date: Thu, 17 Feb 1994 05:47:15 -0500 (EST) From: "Michael A. Crowley" Subject: Re: Default Folder Name Selection (PC-Pine) Cc: pine-info@cac.washington.edu, ouchark@HUSC15.HARVARD.EDU In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII As a workaround, make a link in your mail directory between the saved messages file that pine uses and the name you want to use. -mike On Wed, 16 Feb 1994, David L Miller wrote: > Date: Wed, 16 Feb 1994 13:16:21 -0800 (PST) > From: David L Miller > To: "Bill Ouchark, Networks Group, (617) 495-1271" > Cc: pine-info@cac.washington.edu, ouchark@HUSC15.HARVARD.EDU > Subject: Re: Default Folder Name Selection (PC-Pine) > > Bill, > > Sorry about the slow reply! This is on our to-do list for an upcoming > version of Pine. > > Thanks for the suggestion! > > --DLM > > On Wed, 26 Jan 1994, Bill Ouchark, Networks Group, (617) 495-1271 wrote: > > > Is there a way in PC-Pine 3.89 to set the name of the folder > > used by default for Saves? It defaults to "savemail", but as > > I have a remote folder collection used as the default I would > > prefer to use "saved-messages". I did notice the > > "saved-msg-name-rule=" option in NEWSRC, but it doesn't appear > > to have the option of choosing a specific name. > > > > -Bill Ouchark- > From owner-pine-info@cac.washington.edu Thu Feb 17 06:44:29 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00793; Thu, 17 Feb 94 06:44:29 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29295; Thu, 17 Feb 94 06:26:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from utsw.swmed.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29288; Thu, 17 Feb 94 06:26:54 -0800 Received: from iliad.swmed.edu by UTSW.SWMED.EDU (PMDF V4.2-14 #3937) id <01H8ZHRX1QM89EETV3@UTSW.SWMED.EDU>; Thu, 17 Feb 1994 08:26:48 CDT Received: by iliad.swmed.edu (920330.SGI/911001.SGI) for @utsw.swmed.edu:pine-info@cac.washington.edu id AA29506; Thu, 17 Feb 94 08:34:10 -0600 Date: Thu, 17 Feb 1994 08:34:09 -0600 (CST) From: "Daniel P. Joy" Subject: Pine, IMAP and VMS - summary To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 7BIT Regarding my question yesterday about Pine and IMAP on VMS. I received some information from Innosoft about their PMDF product - maybe other VMS users will find it useful. The next version of Innosoft's PMDF (4.3?) will have Pine and an IMAP client for VMS. I believe it will be released in about one month. --------------------------------------------------------------------- Daniel Joy Systems Manager Internet: joy@howie.swmed.edu Howard Hughes Medical Institute BITNET: joy@utsw UT Southwestern Medical School Phone: (214) 648-5034 From owner-pine-info@cac.washington.edu Thu Feb 17 09:34:50 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04464; Thu, 17 Feb 94 09:34:50 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA20871; Thu, 17 Feb 94 09:06:54 -0800 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/UW-NDC Revision: 2.30 ) id AA20865; Thu, 17 Feb 94 09:06:52 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00295; Thu, 17 Feb 94 09:06:04 -0800 Date: Thu, 17 Feb 1994 09:06:04 -0800 (PST) From: David L Miller Subject: Re: help ? To: SANJEEV SINGH Cc: pine-info@cac.washington.edu In-Reply-To: <9402110919.AA26029@ern.doe.ernet.in> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sanjeev, Pine does not yet support MIME external-body constructs, but we do plan to implement it in the future. Until that time, you will need to manually execute ftp outside of Pine. Sorry. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 11 Feb 1994, SANJEEV SINGH wrote: > Hello! pine group > > > How can I execute *ftp* command from message body (or some > where else ? ) of pine to fetch data from remote M/C in > case message body is large enough. > > can someone help me ? > > thanx in advance. > > -sanjeev From owner-pine-info@cac.washington.edu Thu Feb 17 09:53:37 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04922; Thu, 17 Feb 94 09:53:37 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01396; Thu, 17 Feb 94 09:26:10 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from post.demon.co.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01389; Thu, 17 Feb 94 09:26:06 -0800 Received: from compcg.demon.co.uk by post.demon.co.uk id aa26972; 17 Feb 94 17:03 GMT Received: from compass.unity by compcg.demon.co.uk (4.1/SMI-4.1) id AA27530; Thu, 17 Feb 94 16:17:57 GMT Received: by compass.unity (5.61/1.35) id AA26441; Thu, 17 Feb 94 16:17:54 GMT Date: Thu, 17 Feb 1994 16:14:15 +0000 (WET) From: Martin Beenham Reply-To: Martin Beenham Subject: Re: Reading News Question To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Tue, 15 Feb 1994, ILAN GRAIFER wrote: > I don't think pine should become a full news-reader. There are many > readers that are both powerful and easy to use and which are easily > obtainable on the net. > I would prefer to see pine as a mail agent only, which does what > it is supposed to do and doesn't try to be an all in one package. There is a high degree of common functionality and purpose between news and mail. I for one strongly prefer them to be combined. As a busy administrator of many systems two into one goes down a treat in reducing the number of packages to maintain. Also, I don't wish to hop about between packages when replying to news articles via mail, forwarding etc. I use and prefer a common news and mail utility on my PC at home. I think you are underestimating the PINE team in implying that they wouldn't make as good a job of it as existing news offerings on the net. I'm sure they'd do even better! In any case, if you don't want to use PINE's in-built news facilities you don't have to. There seems little reason not to continue the logical path on which PINE has embarked. > I would like to suggest adding an option of making an uuencoded attachment > in addition to the MIME attachments. Many people don't have MIME, and it > will be nice if it was possible to send a uuencoded file to those people > from within pine. An automatic decoding would be nice as well :) That gets my vote. Even though it's easy to do by shelling out it's a common enough operation to warrent a built-in facility IMHO. Regards, -- Martin G. Beenham "IT - what's that?" (martin@compass)|Tel +44 635 550660 Compass Computer Group, Newbury, Berks, UK RG14 5PX |Fax +44 635 521268 Internet: martin@compcg.demon.co.uk (@work) martin@aman.demon.co.uk (@home) From owner-pine-info@cac.washington.edu Thu Feb 17 10:51:26 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06684; Thu, 17 Feb 94 10:51:26 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02362; Thu, 17 Feb 94 10:30:14 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from thrain.vancouver.wsu.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02354; Thu, 17 Feb 94 10:30:11 -0800 Received: by vancouver.wsu.edu (Smail3.1.28.1 #8) id m0pXDU8-000DQhC; Thu, 17 Feb 94 10:30 PST Date: Thu, 17 Feb 1994 10:30:00 -0700 (PDT) From: "Philip D. Young" Subject: addressbooks To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I would like to see multiple personal and shared addressbooks included in the next release of pine. Phil Young From owner-pine-info@cac.washington.edu Thu Feb 17 11:46:43 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08382; Thu, 17 Feb 94 11:46:43 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22837; Thu, 17 Feb 94 11:21:51 -0800 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/UW-NDC Revision: 2.30 ) id AA22831; Thu, 17 Feb 94 11:21:49 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07258; Thu, 17 Feb 94 11:21:44 -0800 Date: Thu, 17 Feb 1994 11:21:44 -0800 (PST) From: David L Miller Subject: Re: addressbooks To: "Philip D. Young" Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Philip, Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Thu, 17 Feb 1994, Philip D. Young wrote: > I would like to see multiple personal and shared addressbooks included in > the next release of pine. > > > Phil Young > From owner-pine-info@cac.washington.edu Thu Feb 17 12:56:34 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA10304; Thu, 17 Feb 94 12:56:34 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04266; Thu, 17 Feb 94 12:25:34 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from usc.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04256; Thu, 17 Feb 94 12:25:30 -0800 Received: from Law.USC.EDU by usc.edu (4.1/SMI-3.0DEV3-USC+3.1) id AA07819; Thu, 17 Feb 94 12:25:28 PST Received: from hal.Law.USC.EDU by Law.USC.EDU (4.1/SMI-4.1) id AA04108; Thu, 17 Feb 94 12:25:27 PST Received: by hal.Law.USC.EDU (4.1/SMI-4.1) id AA17963; Thu, 17 Feb 94 12:25:26 PST Date: Thu, 17 Feb 1994 12:25:26 -0800 (PST) From: Elmar Kurgpold Reply-To: Elmar Kurgpold Subject: mail thinks user is someone else To: Pine Info Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII I am not positive this is a Pine problem, and now I can't even duplicate it. Just created a new user "mtom", and I've triple-checked it by now. We have another user "stom" on a different system (but same NIS domain). For a while, mtom was sending out messages that had two From headers, which by itself doesn't seem out of the ordinary, but maybe someone who's more up on the RFC than I can correct me. The problem is the headers were different-- the first said "mtom" and the second said "stom". The comment (GCOS) field was even filled in accordingly on the second "From" (which was actually "From:" with the colon). Both users said they could not find the message in the sent-mail folder, although here I am telling you what I found in this folder. If you have an idea what might be causing this, I'd like to hear it. If someone can definitely rule out that this might be a Pine problem, I'll be glad to hear that too. :-) ------------------------------------------------------------------------- | Elmar Kurgpold | EMAIL: ekurgpol@Law.USC.EDU | | Network Administrator | VOICE: (213)740-2571 | | University of Southern California | FAX: (213)740-5502 | | The Law Center | | ------------------------------------------------------------------------- From owner-pine-info@cac.washington.edu Thu Feb 17 14:26:16 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12804; Thu, 17 Feb 94 14:26:16 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25382; Thu, 17 Feb 94 14:03:06 -0800 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/UW-NDC Revision: 2.30 ) id AA25374; Thu, 17 Feb 94 14:03:02 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09786; Thu, 17 Feb 94 14:02:36 -0800 Date: Thu, 17 Feb 1994 14:02:35 -0800 (PST) From: David L Miller Subject: Re: Multiple Personal and Shared Addressbooks To: John Trimble Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, Thanks for the suggestion! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, John Trimble wrote: > I would like to see multiple personal and shared addressbooks in the next > version of pine. > > **************************************************************************** > John Trimble VOICE: (206) 737-2039 > Washington State University FAX: (206) 690-4611 > 1812 E. McLoughlin Blvd. > Vancouver, WA 98663-3597 INTERNET: trimble@vancouver.wsu.edu > **************************************************************************** From owner-pine-info@cac.washington.edu Thu Feb 17 14:27:43 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12851; Thu, 17 Feb 94 14:27:43 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05931; Thu, 17 Feb 94 14:08:17 -0800 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/UW-NDC Revision: 2.30 ) id AA05925; Thu, 17 Feb 94 14:08:16 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09864; Thu, 17 Feb 94 14:08:11 -0800 Date: Thu, 17 Feb 1994 14:08:11 -0800 (PST) From: David L Miller Subject: Re: new release of pine To: Raymond Pendergast Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Raymond, Thanks for the suggestion! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Raymond Pendergast wrote: > I'd like to see multiple personal and shared address books in the > new release of pine. thanks. > > From owner-pine-info@cac.washington.edu Thu Feb 17 14:27:56 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12858; Thu, 17 Feb 94 14:27:56 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05822; Thu, 17 Feb 94 14:03:02 -0800 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/UW-NDC Revision: 2.30 ) id AA05816; Thu, 17 Feb 94 14:02:58 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09780; Thu, 17 Feb 94 14:02:11 -0800 Date: Thu, 17 Feb 1994 14:02:11 -0800 (PST) From: David L Miller Subject: Re: Multiple Delete/Jump to top To: Virtual Dave Lankes Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dave, The next version of Pine will include all of these. Thanks for the suggestions! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 15 Feb 1994, Virtual Dave Lankes wrote: > I remember some mention of a multiple delete in coming versions of Pine. > This is a VERY useful feature I'd like to see implemented. The ability to > tag messages 1-30 for deletion. Thi might work as a command line option > or like Pico's multiple line selection. > > Another feature that is standard in other mail programs and would make a > lot of sense to me...the ability to jump to the top or bottom of a message > (or file in Pico). > > ........................................................... > : "Virtual" Dave Lankes rdlankes@ericir.syr.edu : > : AskERIC Researcher "This is not your father's Internet" : > : School of Information Studies Syracuse University : > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > From owner-pine-info@cac.washington.edu Thu Feb 17 14:31:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA13056; Thu, 17 Feb 94 14:31:00 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25554; Thu, 17 Feb 94 14:13:25 -0800 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/UW-NDC Revision: 2.30 ) id AA25548; Thu, 17 Feb 94 14:13:23 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09924; Thu, 17 Feb 94 14:13:17 -0800 Date: Thu, 17 Feb 1994 14:13:16 -0800 (PST) From: David L Miller Subject: Re: PC Pico enhancement To: John Stumbles Cc: Pine User Group In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII John, Unfortunately the meanings of those keys are not clearly defined on non-PC keyboards. Many keyboards just send a NULL for both of them... --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 31 Jan 1994, John Stumbles wrote: > I keep finding myself using Control with the left- and right-arrow keys to > try to get around: this is pretty standard key-binding in PC editors - > could it be implemented in PICO? > > John Stumbles j.d.stumbles@reading.ac.uk > Reading University 0734 318435 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > From owner-pine-info@cac.washington.edu Thu Feb 17 15:39:31 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15159; Thu, 17 Feb 94 15:39:31 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06573; Thu, 17 Feb 94 14:51:02 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from yarrina.connect.com.au by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06563; Thu, 17 Feb 94 14:50:55 -0800 Received: from lsupoz.apana.org.au by yarrina.connect.com.au with SMTP id AA24418 (5.67b8/IDA-1.5 for ); Fri, 18 Feb 1994 09:50:46 +1100 Received: by budge (Linux Smail3.1.28.1 #14) id m0pXHB1-00012wC; Fri, 18 Feb 94 09:26 EST Date: Fri, 18 Feb 1994 09:24:28 +0100 From: Subject: Re: Compression in PINE ? To: pine-info In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 14 Feb 1994, David L Miller wrote: > > This has been suggested before. Our basic opinion is that disk space is > cheaper than the extra CPUs we would have to buy to support compression > for a given amount of raw data. The rest of the PC world seems to think otherwise..... From owner-pine-info@cac.washington.edu Thu Feb 17 15:57:28 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15637; Thu, 17 Feb 94 15:57:28 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06983; Thu, 17 Feb 94 15:21:06 -0800 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/UW-NDC Revision: 2.30 ) id AA06977; Thu, 17 Feb 94 15:21:05 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA11063; Thu, 17 Feb 94 15:20:53 -0800 Date: Thu, 17 Feb 1994 15:20:52 -0800 (PST) From: David L Miller Subject: Re: Pine / PTX futures. To: Dave King Cc: Pine Information In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Dave, The future of Dynix/ptx here is somewhat uncertain. Presuming our Sequent stays around that long, we will certainly port Pine to version 4. Otherwise we will support it the best we can with user contributions. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Tue, 1 Feb 1994, Dave King wrote: > We use Pine 3.89 on DYNIX/ptx 2.0.4 with no problems. > > Sequent recently told me that ptx version 4 will be released sometime in > Q1/Q2 of this year. I'm aware that ptx is a mjor Pine platform, and that > Pine runs on ptx at UW, but ... > > Could someone please advise if Pine will be ported to ptx version 4 when > it is released? > > Thanks, > > Dave > > ------------------------------------------------------------------- > Dave King, Admin. Computing Services Manager, University of Bristol > Dave.King@uk.ac.Bristol (JANET) Dave.King@Bristol.ac.uk (INTERNET) > From owner-pine-info@cac.washington.edu Thu Feb 17 16:55:23 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17207; Thu, 17 Feb 94 16:55:23 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA07746; Thu, 17 Feb 94 16:13:03 -0800 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/UW-NDC Revision: 2.30 ) id AA07739; Thu, 17 Feb 94 16:13:01 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12037; Thu, 17 Feb 94 16:09:50 -0800 Date: Thu, 17 Feb 1994 16:09:50 -0800 (PST) From: David L Miller Subject: Re: PINE built for XENIX? To: Alex Brown Cc: pine-info@cac.washington.edu, a.brown@ieee.org In-Reply-To: <9401031505.AA24872@codex.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Alex, Sorry about the very slow reply, we have been swamped. Unfortunately we do not have alot of experience/expertise with the older SYSV environments. About the closest thing we would have is an as yet untested ISC port. In the long run you might be better off just converting the whole system to Linux or NetBSD, both of which have working Pine implementations. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Mon, 3 Jan 1994, Alex Brown wrote: > Hello -- > > I'm trying to provide a small school with a simple mail+news installation; > the system available is 80386 Xenix 2.3.2. I have an incomplete PICO port > working, but there seem to be some more fundamental problems with PINE. > As I'm doing this as a volunteer, I don't have much time to put into solving > them. I'd appreciate any contact information regarding ports of PINE to > Xenix, SCO UNIX, 386/ix, or any other 386 System V environment. > > I'd appreciate reply by mail -- I'm not a subscriber to this list. > Please reply to the address below, not the origination address of this > note. Thanks! > > Alex Brown > a.brown@ieee.org > > > > Date: Mon, 3 Jan 1994 01:36:05 -0500 (EST) > > From: Laurence Lundblade > > Subject: Re: PINE built for XENIX? > > To: Alex Brown > > Cc: mikes@cac.washington.edu, a.brown@ieee.org > > In-Reply-To: <9310292035.AA24568@codex.com> > > Message-Id: > > References: <9310292035.AA24568@codex.com> > > Mime-Version: 1.0 > > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Status: R > > > Hello Alex, > > I'm not so directly involved with Pine anymore. I think some folks > > have made attempts, but no one has really got it running. You might try > > posting to pine-info@cac.washington.edu and see if you get any help there. > > > Laurence Lundblade > > lgl@csgrad.cs.vt.edu 703-552-2537 > > Virginia Tech -- Blacksburg, Virginia > > > > On Fri, 29 Oct 1993, Alex Brown wrote: > > > > Date: Fri, 29 Oct 93 16:28:32 -0400 > > > From: Alex Brown > > > To: lgl@cac.washington.edu, mikes@cac.washington.edu > > > Cc: a.brown@ieee.org > > > Subject: PINE built for XENIX? > > > > > > Has there been any word of a XENIX port of PINE/PICO? > > > I'd appreciate any contact information if so. > > > > > > Thanks -- > > > > > > Alexander S. Brown a.brown@ieee.org > > > IEEE Society for Social Implications of Technology > > > PO Box 341, Hopkinton MA 01748 (508) 435-4765 > > > > > > From owner-pine-info@cac.washington.edu Thu Feb 17 18:15:24 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA18899; Thu, 17 Feb 94 18:15:24 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28595; Thu, 17 Feb 94 17:54:56 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from uafhp.uark.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA28587; Thu, 17 Feb 94 17:54:54 -0800 Received: from comp.uark.edu by uafhp.uark.edu with SMTP (1.37.109.4/15.6) id AA11064; Thu, 17 Feb 94 19:55:52 -0600 Received: by (5.0/SMI-SVR4) id AA08773; Thu, 17 Feb 94 19:55:11 CST Date: Thu, 17 Feb 1994 19:55:11 -0600 (CST) From: Richard Lee Subject: Export messages To: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 940 A friendly suggestion for the wonderful pine development team. When exporting a message to a file pine (nicely) checks to see if the file exists. If it does, the user is given the option of appending the new message to the end of the exiting file. If you say "n"o, the export will be canceled. (I assume ^C will have the identical effect.) There is no way, so far as I know, of *choosing* to overwrite the old message with the new one. (Of course one could shell out, rm the old file, and then return to the export, but that's several steps.) So consider adding: "File exists, (o) overwrite, (a) append, or (c) cancel?" If you don't like this ("hey, the other messages give yes/no options instead of a list"), no big deal. -- Dr. Richard Lee rlee@comp.uark.edu Department of Philosophy Old Main 318 rlee@uafsysb.BITNET University of Arkansas phone: 501-575-5826 Fayetteville, AR 72701 From owner-pine-info@cac.washington.edu Thu Feb 17 18:38:54 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA19129; Thu, 17 Feb 94 18:38:54 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09468; Thu, 17 Feb 94 18:22:44 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from rainier.lib.washington.edu by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA09462; Thu, 17 Feb 94 18:22:43 -0800 Received: by rainier.lib.washington.edu (5.65/UW-NDC Revision: 2.24 ) id AA02215; Thu, 17 Feb 94 18:22:37 -0800 Date: Thu, 17 Feb 1994 18:22:36 -0800 (PST) From: Adam Garrett Subject: Re: Export messages To: Richard Lee Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I like this idea too. I like to save files to 'temp', for example, all the time and would rather overwrite it, then append it. -Adam Adam R. Garrett University of Washington Libraries INTERNET: garrett@lib.washington.edu 352 Suzzallo Library, FM-25 PHONE: (206) 543-8843 Seattle, WA 98195 FAX: (206) 685-8049 On Thu, 17 Feb 1994, Richard Lee wrote: > A friendly suggestion for the wonderful pine development team. > When exporting a message to a file pine (nicely) checks to see if > the file exists. If it does, the user is given the option of appending > the new message to the end of the exiting file. If you say "n"o, the > export will be canceled. (I assume ^C will have the identical effect.) > There is no way, so far as I know, of *choosing* to overwrite the old > message with the new one. (Of course one could shell out, rm the old > file, and then return to the export, but that's several steps.) So > consider adding: "File exists, (o) overwrite, (a) append, or (c) cancel?" > If you don't like this ("hey, the other messages give yes/no > options instead of a list"), no big deal. > > -- > > Dr. Richard Lee rlee@comp.uark.edu > Department of Philosophy Old Main 318 rlee@uafsysb.BITNET > University of Arkansas phone: 501-575-5826 > Fayetteville, AR 72701 From owner-pine-info@cac.washington.edu Thu Feb 17 22:03:00 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA21500; Thu, 17 Feb 94 22:03:00 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00298; Thu, 17 Feb 94 21:41:51 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from wave.aoml.erl.gov by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA00292; Thu, 17 Feb 94 21:41:50 -0800 Received: from localhost (chen@localhost) by aoml.erl.gov (8.6.5/8.6.4) id AAA09677; Fri, 18 Feb 1994 00:41:17 -0500 Date: Fri, 18 Feb 1994 00:41:16 -0500 (EST) From: Ying-Yuang Chen Subject: Re: Mime decoder To: John Ladwig Cc: Jason Cross , pine-info@cac.washington.edu In-Reply-To: <9402162046.AA13025@saturn.soils.umn.edu> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII How could I make pine and metamail work together ? Ying-Yuang Chen Computer Services, UNIX System Admin. US Department of Commerce NOAA / AOML 4301 Rickenbacker Causeway, Miami, FL 33199 From owner-pine-info@cac.washington.edu Fri Feb 18 03:06:48 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA24922; Fri, 18 Feb 94 03:06:48 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12545; Fri, 18 Feb 94 02:26:59 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from gate.ggr.co.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA12539; Fri, 18 Feb 94 02:26:56 -0800 Received: from mailhub.ggr.co.uk by gate.ggr.co.uk; Fri, 18 Feb 1994 10:25:14 GMT Received: from uk0x04 by mailhub.ggr.co.uk; Fri, 18 Feb 1994 10:22:58 GMT Received: from localhost by uk0x04 (8.6.4/imd160294) id KAA10853; Fri, 18 Feb 1994 10:24:21 GMT Date: Fri, 18 Feb 1994 10:24:20 +0000 (GMT) From: Ian Dunkin Subject: Re: Export messages To: Richard Lee Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 17 Feb 1994, Richard Lee wrote: > When exporting a message to a file pine (nicely) checks to see if > the file exists. If it does, the user is given the option of appending > the new message to the end of the exiting file. If you say "n"o, the > export will be canceled. (I assume ^C will have the identical effect.) > There is no way, so far as I know, of *choosing* to overwrite the old > message with the new one. (Of course one could shell out, rm the old > file, and then return to the export, but that's several steps.) So > consider adding: "File exists, (o) overwrite, (a) append, or (c) cancel?" Yes! That would be very popular here too. I. -- Ian Dunkin -- From owner-pine-info@cac.washington.edu Fri Feb 18 08:37:31 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29146; Fri, 18 Feb 94 08:37:31 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04227; Fri, 18 Feb 94 08:00:38 -0800 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/UW-NDC Revision: 2.30 ) id AA04221; Fri, 18 Feb 94 08:00:37 -0800 Received: from red.ariel.cs.yorku.ca by shivafs.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA08211; Fri, 18 Feb 94 08:00:32 -0800 Received: from green (green-srv) by ariel.cs.yorku.ca (4.1/SMI-4.1) id AA25791; Fri, 18 Feb 94 10:59:15 EST Received: by green (4.1/SMI-4.1.1) id AA05885; Fri, 18 Feb 94 10:59:13 EST Date: Fri, 18 Feb 1994 10:58:41 -0500 (EST) From: ILAN GRAIFER Reply-To: ILAN GRAIFER Subject: Re: Reading News Question To: Martin Beenham Cc: pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII On Thu, 17 Feb 1994, Martin Beenham wrote: > There is a high degree of common functionality and purpose between news > and mail. I for one strongly prefer them to be combined. As a busy > administrator of many systems two into one goes down a treat in reducing > the number of packages to maintain. Also, I don't wish to hop about > between packages when replying to news articles via mail, forwarding etc. Although having a combined mail client and a newsreader might reduce the initial installation time of the packages, it will defiantly increase the complexity of the whole package, making it harder to use. If you take a look, at any of the newsreaders that are available for UNIX, you will see that there are many different options, and incorporating them into pine will create a package that will be extremely hard to use for novice users. I think the best part about pine is it's ease of use, and simplicity, thus adding so many features will increase the number of options and reduce the usefulness of the whole package. > > I use and prefer a common news and mail utility on my PC at home. I think > you are underestimating the PINE team in implying that they wouldn't make > as good a job of it as existing news offerings on the net. I'm sure > they'd do even better! In any case, if you don't want to use PINE's > in-built news facilities you don't have to. There seems little reason not > to continue the logical path on which PINE has embarked. I had no intention to imply that the PINE team can't create a newsreader that will be as good or even better than other newsreaders that are available, but I just don't feel it is necessary to reinvent the wheel all over again. On a UNIX platform there are many good newsreaders, including readers for the X window system, such as rn, trn, xrn and several others. If the system in question is DOS based, then I am not sure if there exist any good newsreaders. In this case a combined news/mail client can be a good idea, but I feel that the news should be implemented only in PC-PINE, and preferably as a second package that will interact closely with pine. Ilan -- _==| Ilan Graifer _==| )__) | )_) )___) )) cs922080@ariel.cs.yorku.ca )___) )____))_) yku00401@cawc.yorku.ca _ )____)_____))__)\ an41635@anon.penet.fi \---__|____/|___|___-\\--- ^^^^^^^^^\ oo oo oo oo /~~^^^^^^^ ~^^^^ ~~~~^^~~~~^^~~^^~~~~~ ~~^^ ~^^~ ~^~ ~^ ~^ ~^~~ ~~~^^~ From owner-pine-info@cac.washington.edu Fri Feb 18 09:03:23 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA29808; Fri, 18 Feb 94 09:03:23 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15589; Fri, 18 Feb 94 08:37:16 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from cosmail2.ctd.ornl.gov by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA15583; Fri, 18 Feb 94 08:37:06 -0800 Received: from [128.219.128.57] by cosmail2.ctd.ornl.gov (8.6.5/1.34) id LAA01756; Fri, 18 Feb 1994 11:37:01 -0500 Message-Id: <199402181637.LAA01756@cosmail2.ctd.ornl.gov> X-Sender: jnm@cosmail2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 18 Feb 1994 11:37:01 -0500 To: pine-info@cac.washington.edu From: jnm@cosmail2.ctd.ornl.gov (Jamey Maze) Subject: how to influence Pine about MIME type/subtypes??? (please!) I'm wanting to use Pine to send binary files around, specifically WordPerfect 5.1, and Microsoft Word. There are IANA defined MIME type/subtype's defined for these document types (application/wordperfect5.1, application/msword). When I upload a WordPerfect 5.1 file from my PC to my workstation and attach it to a message with Pine, Pine sends it as test/plain. I need some way to tell Pine that this file is to be sent as application/wordperfect5.1 with base64 encoding. I'd think you'd do that with some type of mapping from the file extension (e.g., *.w51 maps to application/wordperfect5.1 with base64 encoding). Does Pine support such mappings or is there an alternate way to accomplish the same objective? I would really appreciate your help with this question. Thanks! -- Jamey Maze 615/574-6355 Martin Marietta Energy Systems, Inc. FAX:576-4992 Oak Ridge National Laboratory "Personally, I'm always ready to learn, although I do not always like being taught." -- Winston Churchill From owner-pine-info@cac.washington.edu Fri Feb 18 09:53:59 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA01275; Fri, 18 Feb 94 09:53:59 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA16532; Fri, 18 Feb 94 09:36:51 -0800 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/UW-NDC Revision: 2.30 ) id AA16526; Fri, 18 Feb 94 09:36:49 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22245; Fri, 18 Feb 94 09:36:46 -0800 Date: Fri, 18 Feb 1994 09:36:45 -0800 (PST) From: David L Miller Subject: Re: Mime decoder To: Ying-Yuang Chen Cc: John Ladwig , Jason Cross , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII The next version of Pine will incorporate much of metamail, though perhaps not all. Specifically, the same mailcap database will be usable by pine and metamail. There will also be a Pipe command that will allow calling metamail directly. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 18 Feb 1994, Ying-Yuang Chen wrote: > > How could I make pine and metamail work together ? > > Ying-Yuang Chen > Computer Services, UNIX System Admin. > US Department of Commerce NOAA / AOML > 4301 Rickenbacker Causeway, Miami, FL 33199 > From owner-pine-info@cac.washington.edu Fri Feb 18 10:22:01 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02070; Fri, 18 Feb 94 10:22:01 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05903; Fri, 18 Feb 94 09:56:06 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from carson-oms2.u.washington.edu by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA05897; Fri, 18 Feb 94 09:56:04 -0800 Received: from shiva1.cac.washington.edu by carson-oms2.u.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA25521; Fri, 18 Feb 94 09:55:59 -0800 Date: Fri, 18 Feb 1994 09:55:58 -0800 (PST) From: Terry Gray Subject: Re: how to influence Pine about MIME type/subtypes??? (please!) To: Jamey Maze Cc: pine-info@cac.washington.edu In-Reply-To: <199402181637.LAA01756@cosmail2.ctd.ornl.gov> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jamey, We have been struggling with the best way to handle typing of potentially ambiguous data. In some cases, the file extension is the only thing available to distinguish the data --but should it be trusted to be correct? I'm actually surprised that the WP doc ended up as text/plain, rather than application/octet-stream, but either way we agree that having the official type recognized is highly desirable. The existing mechanisms should be sufficient to get the document to the recipient without corruption (note that Pine uses B64-encoding even text attachments, to assure their integrity), but automated processing by the recipient does require proper typing. -teg On Fri, 18 Feb 1994, Jamey Maze wrote: > I'm wanting to use Pine to send binary files around, specifically > WordPerfect 5.1, and Microsoft Word. There are IANA defined MIME > type/subtype's defined for these document types > (application/wordperfect5.1, application/msword). When I upload a > WordPerfect 5.1 file from my PC to my workstation and attach it to a > message with Pine, Pine sends it as test/plain. I need some way to tell > Pine that this file is to be sent as application/wordperfect5.1 with base64 > encoding. I'd think you'd do that with some type of mapping from the file > extension (e.g., *.w51 maps to application/wordperfect5.1 with base64 > encoding). Does Pine support such mappings or is there an alternate way to > accomplish the same objective? > > I would really appreciate your help with this question. > > Thanks! > > > -- > Jamey Maze 615/574-6355 > Martin Marietta Energy Systems, Inc. FAX:576-4992 > Oak Ridge National Laboratory > > "Personally, I'm always ready to learn, although I do not always like being > taught." -- Winston Churchill > > > From owner-pine-info@cac.washington.edu Fri Feb 18 10:27:26 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02324; Fri, 18 Feb 94 10:27:26 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06060; Fri, 18 Feb 94 10:06:04 -0800 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/UW-NDC Revision: 2.30 ) id AA06054; Fri, 18 Feb 94 10:06:03 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA22896; Fri, 18 Feb 94 10:05:49 -0800 Date: Fri, 18 Feb 1994 10:05:49 -0800 (PST) From: David L Miller Subject: Re: Reading News Question To: ILAN GRAIFER Cc: Martin Beenham , pine-info@cac.washington.edu In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Fri, 18 Feb 1994, ILAN GRAIFER wrote: > On Thu, 17 Feb 1994, Martin Beenham wrote: > > > There is a high degree of common functionality and purpose between news > > and mail. I for one strongly prefer them to be combined. As a busy > > administrator of many systems two into one goes down a treat in reducing > > the number of packages to maintain. Also, I don't wish to hop about > > between packages when replying to news articles via mail, forwarding etc. > > Although having a combined mail client and a newsreader might reduce the > initial installation time of the packages, it will defiantly increase the > complexity of the whole package, making it harder to use. > > If you take a look, at any of the newsreaders that are available for UNIX, > you will see that there are many different options, and incorporating them > into pine will create a package that will be extremely hard to use for > novice users. > I think the best part about pine is it's ease of use, and simplicity, thus > adding so many features will increase the number of options and reduce the > usefulness of the whole package. > I think you will be pleasantly surprised by the Pine news support. For the novice user, the transition from a mail folder to a newsgroup will be barely noticable. One of the biggest reasons for putting news support into pine is to give the novice user something that is not as daunting as the conventional Unix newsreader. Pine will probably never be as sophisticated as the big news packages, but they do not meet the usability needs of our primary target audience! |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA From owner-pine-info@cac.washington.edu Fri Feb 18 10:27:32 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA02337; Fri, 18 Feb 94 10:27:32 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06090; Fri, 18 Feb 94 10:08:27 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from gmlink.gmeds.com by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06084; Fri, 18 Feb 94 10:08:24 -0800 Received: from earth.ae.eds.com (earth.troy.eng.eds.com) by gmlink.gmeds.com with SMTP id AA16320 (InterLock SMTP Gateway 1.1 for ); Fri, 18 Feb 1994 13:08:16 -0500 Received: from majorca (majorca.troy.eng.eds.com) by earth.ae.eds.com (4.1/AE-1.0) id AA19837; Fri, 18 Feb 94 13:08:16 EST Date: Fri, 18 Feb 1994 13:09:42 -0500 (EST) From: Jason Cross Subject: pc-pine To: pine-info@cac.washington.edu Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Is there much difference (in terms of look and functionality) between the pc and unix versions? Is the pc version just as easy to compile and install as unix? Any feedback (subjective or objective) is welcome. Thanks a bunch. ciao, Jason Cross EDS Troy, Mi. From owner-pine-info@cac.washington.edu Fri Feb 18 10:58:54 1994 Received: from mx2.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03273; Fri, 18 Feb 94 10:58:54 -0800 Received: by mx2.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA06501; Fri, 18 Feb 94 10:37:07 -0800 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/UW-NDC Revision: 2.30 ) id AA06493; Fri, 18 Feb 94 10:37:05 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23445; Fri, 18 Feb 94 10:37:02 -0800 Date: Fri, 18 Feb 1994 10:37:02 -0800 (PST) From: David L Miller Subject: Re: Pine is greedy To: Matt Simmons Cc: Pine Mailing List In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Matt, I'm afraid it is a general Unixism when you reconfigure the terminal driver. Pine does not do anything explicitly to suck up keystrokes. Thanks for the report! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Wed, 2 Feb 1994, Matt Simmons wrote: > When you exit pine, it seems to suck up all of the keystrokes from the > time you hit expunge-yes until the prompt returns... Is there any way for > pine to not suck up these keystrokes, so I can start typing the next > command while it is exitting? I've noticed this problem with other > (SunOS 4.1.something) programs... Is it a general UNIXism? > > Devoted _n______________________________________________ _________________ > Teri / \|[]|"" \ |[]| |[]| |[]| |[]| / || \ |[]| |[]| > Polo ,(_____| |()_()\___| |___| |___| |___| |___/ || \___| |___| | > Fan <_______|__|_(_)_____|__|___|__|___|__|___|__|______||______|__|___|__| > =========\ Walt Disney World Monorail System || > LCA _____\________________________________________________||_________________ > __/ This highway's in perfect shape. Quick! Thank god I'm not a > _/ Break it so we can 'fix' it! -- IDOT Motto F. I. P. =) > > From owner-pine-info@cac.washington.edu Fri Feb 18 10:59:56 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA03312; Fri, 18 Feb 94 10:59:56 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17358; Fri, 18 Feb 94 10:41:54 -0800 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/UW-NDC Revision: 2.30 ) id AA17352; Fri, 18 Feb 94 10:41:53 -0800 Received: by shiva1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA23550; Fri, 18 Feb 94 10:41:41 -0800 Date: Fri, 18 Feb 1994 10:41:41 -0800 (PST) From: David L Miller Subject: Re: Pine locking (fwd) To: Ian Dunkin Cc: The Pine list In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Ian, Sorry about the slow reply to this. Unfortunately this apparently simple operation gets quite complicated behind the scenes. If you have users who do this kind of thing routinely, you might consider converting to one of the alternate INBOX formats (e.g. Tenex) that allows shared concurrent access. Thanks for the request! --DLM |\ | |\/| David L. Miller dlm@cac.washington.edu (206) 685-6240 |/ |_ | | Software Engineer, Pine Development Team (206) 685-4045 (FAX) University of Washington, Networks & Distributed Computing 4545 15th Ave NE, Seattle WA 98105, USA On Fri, 28 Jan 1994, Ian Dunkin wrote: > > Had the following query from a user here. I'm sure I've seen discussion > of this on the list, but it doesn't seem to have been implemented. Would > it be a good thing to add? In summary: > > User runs Pine, leaves the session going > > User goes away and logs in from somwhere else; Pine correctly takes > the lock from the first session > > User comes back to the first session. Would like a way to grab > _back_ the lock. > > Thanks, > > I. > > ---------- Forwarded message ---------- > > Date: Fri, 28 Jan 1994 15:42:02 +0000 (GMT) > From: [...] one-of-our-users > Subject: Pine locking > > When I dial-in to my workstaion & look at mail with Pine it is very good > at grabbing the file locking, but when I get back to the console I have > to quit Pine, then run it again to leave the read-only mode. Is there a > way of getting the file lock back in Pine? > > R. From owner-pine-info@cac.washington.edu Fri Feb 18 11:49:10 1994 Received: from mx1.cac.washington.edu by shivams.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA04885; Fri, 18 Feb 94 11:49:10 -0800 Received: by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17716; Fri, 18 Feb 94 11:10:25 -0800 Errors-To: owner-pine-info@cac.washington.edu Sender: owner-pine-info@cac.washington.edu Return-Path: Received: from oxmail.ox.ac.uk by mx1.cac.washington.edu (5.65+UW94/UW-NDC Revision: 2.30 ) id AA17710; Fri, 18 Feb 94 11:10:21 -0800 Received: from teaching.physics.ox.ac.uk by oxmail.ox.ac.uk with SMTP (PP) id <27045-0@oxmail.ox.ac.uk>; Fri, 18 Feb 1994 19:10:00 +0000 Received: from teaching6 by teaching.physics.ox.ac.uk (NX5.67d/NX3.0M) id AA20178; Fri, 18 Feb 94 19:09:54 GMT Received: by teaching6.physics.ox.ac.uk (NX5.67d/NX3.0X) id AA15644; Fri, 18 Feb 94 19:09:50 GMT Date: Fri, 18 Feb 1994 19:09:49 +0000 (GMT) From: The PenMaster Subject: Next Pine version- When? To: pine-info@cac.washington.edu Message-Id: