Re: IMAP REPLACE extension

Adrien -

I believe message sequence numbers are only valid in the context of a 
Selected mailbox, so REPLACE is not valid in Authenticated state.  I had 
considered doing away with support for sequence numbers and relying on 
IMAP-URL-style specification of the original message in order to avoid 
the need for Selected state, but landed where I did based on:
1) STORE + UID EXPUNGE require Selected state and those are component 
parts of REPLACE
2) being already in Selected state for APPEND is actually a lot more 
common than one would expect

- Stuart

On 5/5/15 5:54 PM, Adrien de Croy wrote:
>
> REPLACE wraps APPEND which has a mailbox name as an argument.  Therefore
> REPLACE must also have this argument and that's also why it's an
> authenticated-state command and not a selected-state command.
>
> Adrien
>
>
> ------ Original Message ------
> From: "Pete Maclean" <[email protected]>
> To: "Stu Brandt" <[email protected]>; "'[email protected]'"
> <[email protected]>
> Sent: 6/05/2015 6:35:58 a.m.
> Subject: Re: [imapext] IMAP REPLACE extension
>
>> Stu,
>>
>> This is a good start indeed but I find a few things to mention.
>>
>> Is UID REPLACE valid in the authenticated state?  My assumption would
>> be that it is but it might be good for the text to make that explicit.
>>
>> Can REPLACE be used to replace a message in a mailbox other than the
>> one the client has selected?  Surely it should not be.  Which perhaps
>> suggests that REPLACE should not have a mailbox-name argument.
>>
>> The penultimate paragraph in section 3.4 strikes me as awkward and
>> unclear.
>>
>> There is a typo ("replacment") in the first paragraph of the Abstract.
>>
>> Pete Maclean
>>
>> _______________________________________________
>> imapext mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/imapext
>

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext