MBOX-Line: From dave at cridland.net  Wed Jun 23 09:40:05 2010
To: imap-protocol@u.washington.edu
From: Dave Cridland <dave@cridland.net>
Date: Fri Jun  8 12:34:45 2018
Subject: [Imap-protocol] Handle failures during STORE command execution
In-Reply-To: <alpine.OSX.2.00.1006230919010.266@hsinghsing.panda.com>
References: <AANLkTimu9HE_yXxlM9Zy6yNhvmgoOW3Xlj3aDQmCBDDL@mail.gmail.com>
	<30462.1277309118.168996@puncture>
	<AANLkTimuPuKtomDd6kyvXLkofyQyShbDxRDUZLaeWwQ6@mail.gmail.com>
	<alpine.OSX.2.00.1006230919010.266@hsinghsing.panda.com>
Message-ID: <30462.1277311205.980277@puncture>

On Wed Jun 23 17:21:07 2010, Mark Crispin wrote:
> On Wed, 23 Jun 2010, Norman Maurer wrote:
>> Ok now we I have different answers :( I understand the Problem with
>> SILENT, but not See why its the Case otherwise....
> 
> The SILENT option in STORE is used when you don't care about  
> knowing what
> happened.
> 
> 
That's not quite what you wrote in 3501:

        A suffix of ".SILENT" in
      the data item name prevents the untagged FETCH, and the server
      SHOULD assume that the client has determined the updated value
      itself or does not care about the updated value.

> However, in most cases the question is moot since yours would  
> probably be
> the first server that has a "some but not others" STORE result.  It  
> would
> be better to keep it moot by abolishing that possibility.

Right - I would understand "OK" to mean "I have changed all flags"  
and "NO" to mean "I have changed no flags".

Albeit my client ignores the OK/NO unless .SILENT is being used.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

