Re: [Jmap] DSN and MDN in JMAP

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

On 18 Jul 2017, at 19:14, Neil Jenkins wrote:
> 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.

I think that should be explicit in the spec, perhaps say:

JMAP servers MAY set the delivered/seen strings based on information 
other than standard DSN and MDN messages.


We could move dsnBlobIds & mdnblobIds to the MessageSubmission object. 
For the power users (or support staff) who want the details in those 
messages, JMAP-level per-recipient correlation isn't that important and 
it may be easier for a UI to put a "show technical details" feature on a 
messageSubmission object.

A couple other details I think are helpful to articulate:

JMAP servers MAY (SHOULD?) hide standard DSN and MDN messages that 
correlate to a MessageSubmission object from the normal mailbox view and 
expose them only in the dsnBlobIds and mdnblobIds fields.

When a JMAP server performs a message submission, it MAY use the same ID 
string for the RFC 3461 ENVID parameter and the JMAP MessageSubmission 
object ID. JMAP servers that do this MAY replace a client-provided value 
for ENVID with a server-provided value.

		- Chris