Re: [Jmap] Draft messages - mutability

[Brandon Long <[e-mail]>]

In terms of message mutability, we've had another case for plain messages
that we find complicated, which is if the server chooses to modify the
message.

As an example case, suppose the server has decided that a message a client
has already synced is now a phishing message, and as such, wants to rewrite
all of the links in the message or make them not-linkable.  The only way to
do this with immutable messages is to remove the old message and create a
new one.[1]

If the client has already synced the message and read it, then on the next
sync, it will fail to apply the read action since the message no longer
exists, and the user will be presented with the message again as new, which
for a phishing message seems like a bad idea.

Perhaps we don't need to make them mutable, but a replace semantic which
was available in both directions would allow the client to sync state to
the new copy of the message.

[1] Of course, if you own the MUA and server, you can just say the message
is $Phishing and the MUA can modify how it displays the message, but
enterprise customers like to use their favorite clients and their security
ops folks like to protect them

On Tue, Apr 25, 2017 at 7:56 PM, Neil Jenkins <[e-mail]> wrote:

> On Wed, 26 Apr 2017, at 12:40 PM, Ted Lemon wrote:
>
> I suppose that if the old draft were present in a viewer,
>
>
> Yes, this is the case I was referring to: where the draft is currently
> open for editing.
>
> Neil.
>
> _______________________________________________
> Jmap mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/jmap
>
>