Re: Communciator 4.02 Imap EXPUNGE problem

Mike Macgirvin <MAX@netscape.com> Tue, 26 August 1997 20:11 UTC

Received: from cnri by ietf.org id aa14386; 26 Aug 97 16:11 EDT
Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid QAA07777 for <ietf-archive@CNRI.Reston.VA.US>; Tue, 26 Aug 1997 16:14:44 -0400 (EDT)
Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA18013; Tue, 26 Aug 1997 13:04:29 -0700
Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA25462 for <imap@lists.u.washington.edu>; Tue, 26 Aug 1997 13:03:51 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id NAA12622 for <imap@u.washington.edu>; Tue, 26 Aug 1997 13:03:49 -0700
Received: from jimi-hendrix.mcom.com (h-205-217-228-33.netscape.com [205.217.228.33]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id NAA26847 for <imap@cac.washington.edu>; Tue, 26 Aug 1997 13:03:46 -0700
Received: from Netscape.COM (metal.mcom.com [205.217.228.164]) by jimi-hendrix.mcom.com (Netscape Messaging Server 3.0) with ESMTP id AAA27523; Tue, 26 Aug 1997 13:03:12 -0700
Message-Id: <34033611.EBCE071C@Netscape.COM>
Date: Tue, 26 Aug 1997 13:01:21 -0700
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: Mike Macgirvin <MAX@netscape.com>
To: "Barry Leiba, Multimedia Messaging" <leiba@watson.ibm.com>
Cc: imap <imap@cac.washington.edu>
Subject: Re: Communciator 4.02 Imap EXPUNGE problem
References: <SIMEON.9708261337.F@uranus.diz.watson.ibm.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="------------F5F6600F3A812A261B6F549E"
X-Sender: "Mike Macgirvin" <max@netscape.com>
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

> > I guess the problem I have with this is that it states the obvious!
> 
> Yes, and I think it doesn't; I think it's not obvious until we have a 
> discussion like this.  Remember that you've been doing this for a long time 
> and you have more than one implementation behind you.  Someone getting into 
> this for the first time will reasonably assume that she can do these sorts 
> of things, unless we say otherwise and point out why not.
> 
> > It certainly does not belong in the specification, which is large and 
> 
> Oh, absolutely.  I'm suggesting an "Implementer's Guide".  Perhaps I'll try 
> putting together a draft of one, and let people beat on it and add their 
> favourite stumbles.  I think such a document will be useful -- because if 
> this stuff were really all as obvious as you say, not so many people would 
> be stumbling over it.

There are a great number of issues which have come up which have nothing to
do with legal protocol, but all affect inter-operability. A lot of these
issues seem perfectly obvious to somebody who's been on this list for
several years and has munged through c-client and the details of dealing
with multiple platforms and message stores until their head hurts. I can
understand the frustration of those building products armed only with the
RFC, and can think of at probably thirty topics which should be *required*
reading for anybody attempting an IMAP product.