MBOX-Line: From janssen at parc.com  Tue Mar 13 19:47:56 2007
To: imap-protocol@u.washington.edu
From: Bill Janssen <janssen@parc.com>
Date: Fri Jun  8 12:34:38 2018
Subject: [Imap-protocol] SEARCH restricted to one mailbox? Extensions? 
In-Reply-To: <45F750AD.3020507@aol.com> 
References: <07Mar12.152936pst."57996"@synergy1.parc.xerox.com>
	<1173743673.9167.65.camel@hurina> <45F6A2E4.3060502@aol.com>
	<07Mar13.082943pst."57996"@synergy1.parc.xerox.com>
	<45F750AD.3020507@aol.com>
Message-ID: <07Mar13.184804pst."57996"@synergy1.parc.xerox.com>

> The client would know to use this method the same way it would know to 
> do any other extension, it would be written to take advantage of the 
> advertised capability.

Oh, OK.  I was trying to think of ways to do it that wouldn't require
an extension.

> Is there a way to identify a mailbox as read-only?  What happens when a 
> client tries to copy or append a new message to your "search all 
> folders" mailbox?  I suppose you'd have to respond NO, but there should 
> be a way for the client to know before trying such an operation.

From RFC 3501:

      If the client is not permitted to modify the mailbox but is
      permitted read access, the mailbox is selected as read-only, and
      the server MUST prefix the text of the tagged OK response to
      SELECT with the "[READ-ONLY]" response code.

But my search folders are really Presto folders (see section 4.2 of
http://www2.parc.com/csl/projects/placeless/papers/tochi-presto.pdf,
page 9), though the system isn't based on the Presto codebase.  So
I could support COPY and/or APPEND.

Bill

