JAMES-3962 JMAP Email/set: move EmailHeader[] from bodyValues to htmlBody/textBody

[vttranlina]

Currently, the client sends a JSON request with headers: EmailHeader[] under the bodyValues property, structured as follows:

"bodyValues": {
                 "a49d": {
                 "value": "$htmlBody",
                  "isTruncated": false,
                  "isEncodingProblem": false,
                  "header:Specific:asText": "MATCHME"
                  }
               }

However, according to RFC 8621, EmailBodyValue does not reference headers property.

Instead, headers are mentioned in the EmailBodyPart.

The example in the RFC is also similar.

To align with the RFC specification, we need to update the mapping.
This change will also support cases where the email part uses blobId instead of partId, while still allowing the client to set headers.

[chibenwa]

Good catch

[Arsnael]

Shouldn't this change be documented somewhere?

[vttranlina]

Shouldn't this change be documented somewhere?

The James document is already similar to rfc8621
https://github.com/apache/james-project/blob/master/server/protocols/jmap-rfc-8621/doc/specs/spec/mail/message.mdown?plain=1#L1249

[Arsnael]

Yes but I meant more for clients using already jmap, if we move a field in the response?

[vttranlina]

Yes but I meant more for clients using already jmap, if we move a field in the response?

sorry, but I'm confused what should I do?

[chibenwa]

+1 for avoiding breaking change...

[Arsnael]

sorry, but I'm confused what should I do?

Add an entry in upgrade-instructions.md?

[chibenwa]

Not sure, we only better conform to the RFC...

[vttranlina]

rebase & squash