[2546] in Release_7.7_team
Re: IMAP text client
daemon@ATHENA.MIT.EDU (Karl Ramm)
Wed Jan 17 15:33:10 2001
To: "t. belton" <tbelton@MIT.EDU>
Cc: Greg Hudson <ghudson@MIT.EDU>, John Hawkinson <jhawk@MIT.EDU>,
<release-team@MIT.EDU>
From: Karl Ramm <kcr@1ts.org>
Date: 17 Jan 2001 15:32:46 -0500
In-Reply-To: "t. belton"'s message of "Wed, 17 Jan 2001 10:27:27 -0500 (EST)"
Message-Id: <uusvgrdor69.fsf@ORTHANC.1TS.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
"t. belton" <tbelton@MIT.EDU> writes:
> On 14 Jan 2001, Karl Ramm wrote:
>
> > Actually, given our lack of familiarity with the software and the kinds of
> > earth shattering bugs pine tends to have, attachandrun scripts seem like a
> > good idea.
>
> What kind of "earth-shattering bugs"? I've used pine heavily for the
> better part of six years and I have never run into a single problem, not
> even when using the quasi-unsupported POP methods (pine likes to keep the
> mail file locked the whole time you're running, which won't do for POP
> boxes).
Cert advisory CA-1998-10 <http://www.cert.org/advisories/CA-1998-10.html>
is the one that springs to mind, which applies to both mutt and pine...
although I thought I remembered a pine specific one.
> I'd also disagree with the classification of pine as only suitable for
> beginning-to-advanced users - name me a feature you want in a mail program
> that pine doesn't have - but I'll agree that you have to wander DEEP into
> the config menus to turn on all the really good stuff.
Then you probably don't get enough mail... :->
kcr
