Re: [Jmap] DSN and MDN in JMAP

Regarding "delivered" there is a 4th state which you haven't captured here which is "definitely not yet" while the message is still in an outbound queue.  That's not quite the same as unknown.  Obviously a future-send email would also have that state.
On Wed, 19 Jul 2017, at 03:14, Neil Jenkins wrote:
> *delivered*: `String`
>  * This MUST be one of the following values:
> `unknown`: The delivery status is unknown. This is the initial value.
> `yes`: A DSN has been received for this recipient with Action (as per RFC3464 section 2.3.3) equal to "delivered".
> `no`: A DSN has been received for this recipient with Action equal to "failed".
>  * *seen*: `String`
> This MUST be one of the following values:
> `unknown`: The seen status is unknown. This is the initial value.
> `yes`: An MDN has been received for this recipient with Disposition-Type (as per RFC 3798 section 3.2.6.2[1]) equal to "displayed".
>  * *dsnBlobIds*: `String[]`
> A list of blob ids for DSNs received for this recipient, in order of receipt, oldest first.
>  * *mdnBlobIds*: `String[]`
> A list of blob ids for MDNs received for this recipient, in order of receipt, oldest first.> The other nice thing about this is that JMAP servers may be able to update the delivered/seen properties based on other mechanisms (for example when there are local recipients); the client doesn't have to care how the server knows if the message has been delivered/seen.> 
> Neil.
> _________________________________________________
> Jmap mailing list
> Jmap@ietf.org
> https://www.ietf.org/mailman/listinfo/jmap

--
  Bron Gondwana, CEO, FastMail Pty Ltd
  brong@fastmailteam.com


Links:

  1. https://tools.ietf.org/html/rfc3798#section-3.2.6.2