Re: shared folders.

Chris Newman <Chris.Newman@innosoft.com> Sun, 31 August 1997 00:06 UTC

Received: from cnri by ietf.org id aa13086; 30 Aug 97 20:06 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 UAA20114 for <ietf-archive@CNRI.Reston.VA.US>; Sat, 30 Aug 1997 20:10:08 -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 RAA04704; Sat, 30 Aug 1997 17:06:40 -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 RAA15920 for <imap@lists.u.washington.edu>; Sat, 30 Aug 1997 17:03:54 -0700
Received: from THOR.INNOSOFT.COM (SYSTEM@THOR.INNOSOFT.COM [192.160.253.66]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id RAA13007 for <imap@u.washington.edu>; Sat, 30 Aug 1997 17:03:52 -0700
Received: from eleanor.innosoft.com ("port 43206"@ELEANOR.INNOSOFT.COM) by INNOSOFT.COM (PMDF V5.1-10 #8694) with SMTP id <01IN23QQEHZ294FI3Q@INNOSOFT.COM> for imap@u.washington.edu; Sat, 30 Aug 1997 17:03:13 PDT
Message-Id: <Pine.SOL.3.95.970830165553.6300B-100000@eleanor.innosoft.com>
Date: Sat, 30 Aug 1997 17:05:10 -0700
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: Chris Newman <Chris.Newman@innosoft.com>
To: Pravin Singhal <pravin@pacbell.net>
Cc: imap@u.washington.edu
Subject: Re: shared folders.
In-Reply-To: <34080097.F3D1ABD@pacbell.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset="US-ASCII"
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

On Sat, 30 Aug 1997, Pravin Singhal wrote:
> Can someone enlighten me how to create a shared folder in IMAP4 
> and what are the issues involved for the client to support it. 

There are three scenarios:

(1) On some server implementations, it may be impossible to create shared
folders through IMAP4 -- they have to be created manually on the server or
simply aren't available.

(2) On some server implementations, the client has to somehow magically
"know" where to create such folders -- usually by asking the user.  The
NAMEMODEL proposal will correct this problem.

(3) On some servers, one simply creates the folder and uses the ACL
extension to share it.  On these servers, simply displaying the LIST "" %
hierarchy will allow navigation to the shared folder.

The key things for client authors to do for shared folder support:

(a) For now, you have to allow the user to configure multiple search paths
for a given server.  Otherwise shared folders may be inaccessible.

(b) As soon as NAMEMODEL is published, I recommend supporting it -- it
will improve consistancy and should leave (a) as a power-user feature.

(c) Allow folders to be created with a type-in path -- not restricted to
some subtree.

(d) Support subscriptions so users don't have to see folders they're not
interested in.

(e) Support connections to multiple IMAP servers.

(f) Don't try to bypass the \Deleted & EXPUNGE model.

(g) Support the ACL extension.

		- Chris