Mdn draft 01#288
Conversation
| Original recipient address as specified by the sender of the message for which the MDN is being issued. | ||
| - **finalRecipient**: `String` (server-set) | ||
| Recipient for which the MDN is being issued. | ||
| - **originalMessageID**: `String|null` (server-set) |
There was a problem hiding this comment.
is it of any use? I mean, we already have a mandatory forEmailId field that allows to find the original Email.
There was a problem hiding this comment.
yes, when parsing an MDN there can be cases where you have the originalMessageID field but no matching email id
|
|
||
| This method allows you to parse blobs as [@!RFC5322] messages to get MDN objects. This can be used to parse and get detailed information about blobs referenced in the *mdnBlobIds* of the EmailSubmission object, or any email the client could expect to be an MDN. | ||
|
|
||
| The *forEmailId* property can be null or missing if the *originalMessageID* property is missing or not referencing an existing email. |
There was a problem hiding this comment.
Does it make sense to parse it at all?
There was a problem hiding this comment.
Sorry, I don't understand your question
There was a problem hiding this comment.
I mean, If the MDN doesn't match any message you have, why would you want to parse it?
There was a problem hiding this comment.
because you could have lost the sent mail matching it, but still want to be informed of received MDN. Fields in the MDN can still be relevant to the user.
| @@ -0,0 +1,278 @@ | |||
| # Introduction | |||
|
|
|||
| JMAP ([@!I-D.ietf-jmap-core] – JSON Meta Application Protocol) is a generic protocol for synchronising data, such as mail, calendars or contacts, between a client and a server. It is optimised for mobile and web environments, and aims to provide a consistent interface to different data types. | |||
There was a problem hiding this comment.
I doubled check, it's English, not American, see here: https://jmap.io/spec-mail.html#introduction
4 participants
This is the second version of the MDN draft, taking into accounts most comments made on linagora#18 and #253 and on IETF mailing list.