Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JMAP Email/set - Update Body Request Format for Specific Header #3526

Open
vttranlina opened this issue Feb 28, 2025 · 1 comment
Open

JMAP Email/set - Update Body Request Format for Specific Header #3526

vttranlina opened this issue Feb 28, 2025 · 1 comment

Comments

@vttranlina
Copy link
Member

Currently, Tmail support json request with headers: EmailHeader[] under the bodyValues property, structured as follows:

        "htmlBody": [
            {
              "partId": "a49d",
              "type": "text/html"
            }
          ],
          "bodyValues": {
            "a49d": {
              "value": "$htmlBody",
              "isTruncated": false,
              "isEncodingProblem": false,
              "header:Specific:asText": "MATCHME"
            }
          }

However, this format does not comply with RFC8621
The correct format should move the specific header from bodyValues to htmlBody/textBody:

        "htmlBody": [
            {
              "partId": "a49d",
              "type": "text/html",
               "header:Specific:asText": "MATCHME"
            }
          ],
          "bodyValues": {
            "a49d": {
              "value": "$htmlBody",
              "isTruncated": false,
              "isEncodingProblem": false
            }
          }

The James pr apache/james-project#2659 support for both formats. However, the old format is now marked as Deprecated.
We should move to new format

@chibenwa
Copy link
Member

Do not work on this too soon: we need backend team to make progress on this first...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants