Re: [Jmap] DSN and MDN in JMAP

[Neil Jenkins <[e-mail]>]

After discussing this with Chris, we agreed that most of this is probably not useful, and we would be better off simplifying the key information into two properties, and providing access to the raw DSN/MDN as blobs should a client wish to do more.
So I propose we add the following to the DeliveryStatus object for each recipient:
 * *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.

Links:

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