Re: Communciator 4.02 Imap EXPUNGE problem

Cyrus Daboo <daboo@cyrusoft.com> Wed, 27 August 1997 16:10 UTC

Received: from cnri by ietf.org id aa08764; 27 Aug 97 12:10 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 MAA10564 for <ietf-archive@CNRI.Reston.VA.US>; Wed, 27 Aug 1997 12:13:16 -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 JAA13774; Wed, 27 Aug 1997 09:03:34 -0700
Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id JAA12274 for <imap@lists.u.washington.edu>; Wed, 27 Aug 1997 09:03:02 -0700
Received: from mx2.cac.washington.edu (mx2.cac.washington.edu [140.142.33.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA02083 for <imap@u.washington.edu>; Wed, 27 Aug 1997 09:03:00 -0700
Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by mx2.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id JAA04390 for <imap@cac.washington.edu>; Wed, 27 Aug 1997 09:02:58 -0700
Received: from sardis.cyrusoft.com (sardis.cyrusoft.com [206.31.218.203]) by darius.cyrusoft.com (8.8.5/8.8.5) with SMTP id MAA11994; Wed, 27 Aug 1997 12:02:26 -0400 (EDT)
Message-Id: <604569.3081672334@sardis.cyrusoft.com>
Date: Wed, 27 Aug 1997 12:05:34 -0400
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: Cyrus Daboo <daboo@cyrusoft.com>
To: imap <imap@cac.washington.edu>
Cc: "Barry Leiba, Multimedia Messaging" <leiba@watson.ibm.com>
Subject: Re: Communciator 4.02 Imap EXPUNGE problem
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Authenticated: daboo by imap.cyrusoft.com
X-Licensed-To: Cyrus Daboo
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

--On Wed, Aug 27, 1997 11:26 AM -0400 "Barry Leiba, Multimedia Messaging"
<leiba@watson.ibm.com> wrote: 

> Go back to a point that Mark was making in a couple of his responses: 
IMAP 
> *does not guarantee* shared access to mailboxes.  Yes, the protocol
allows 
> it (POP explicitly forbids it), and yes, many/most servers support it. 
But 
> some servers in some configurations may not, generally because of 
> limitations in the back-end mail store.
> 

OK - but how does a client know whether it can take advantage of multiple
connections to a single mailbox? Fine, if the server CAPABILITY states it
supports ACL, then you can reasonably assume this to be the case, but
there is no CAPABILITY or response to indicate that this really is allowed
or disallowed (as pointed out before). All the client can do in the
current environment is attempt to make a multiple connection (if it so
desires) and it is then upto the server to refuse this if it can't support
it. The client must then handle such a refusal in a friendly way.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cyrus Daboo                                   mailto:daboo@cyrusoft.com
Cyrusoft International, Inc.                    http://www.cyrusoft.com
Voice: +1 412 605 0499                             Fax: +1 412 605 0705
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Proud Purveyors of Mulberry: Internet Mail from the Ground Up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~