Re: [Jmap] Best vs Good enough - adoption of JMAP

["Chris Newman" <[e-mail]>]

On 24 Apr 2017, at 22:56, Bron Gondwana wrote:
> On Tue, 25 Apr 2017, at 11:41, Chris Newman wrote:
>> True, if the WG finds rough consensus around the outbox model despite 
>> my
>> objections, then my implementation will have an always-empty outbox 
>> as
>> that's the only way to implement it without infrastructure 
>> disruption.
>> I'd prefer a JMAP design that allows me to provide delivery status UX
>> without infrastructure disruption.
>
> Ahh, I see you already replied with this.  Yeah, always-empty outbox 
> is my first plan too as a server implementer.  It's what I did for the 
> proxy, since it doesn't have reliable storage.
>
> The reason to hold email in the outbox temporarily is to implement 
> both undo-send and delayed send, both of which are popular features in 
> new mail clients.  We'll definitely do outbox-as-queue at FastMail 
> eventually.

Our infrastructure already supports FUTURERELEASE and an undo send 
capability to go with it. I'd love to expose those features to mail 
clients. So if JMAP had a submission command with envelope options and 
an undo send command that keyed off the \Sent folder; it'd be no problem 
for our implementation to provide both delayed send and undo send as 
client features. But if JMAP has the outbox model that forces mailstore 
semantics and queue semantics to be combined in one object, that's a 
huge amount of extra work on the server so I'd opt for the always-empty 
outbox approach (mostly for the improved security and scalability of a 
much simpler implementation).

So given we have at least two server implementers on the list who will 
do always-empty outbox for the first implementation, I think that begs 
the question of what's the more important feature for JMAP to offer:
A) outbox model
B) undo send and delayed send

If B is more important than A, I think we need to replace the outbox 
model with a simpler submit/undo-submit model so it's easier for servers 
to provide those features to clients.

		- Chris