We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, Tmail support json request with headers: EmailHeader[] under the bodyValues property, structured as follows:
headers: EmailHeader[]
bodyValues
"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
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
Deprecated
The text was updated successfully, but these errors were encountered:
Do not work on this too soon: we need backend team to make progress on this first...
Sorry, something went wrong.
No branches or pull requests
Currently, Tmail support json request with
headers: EmailHeader[]
under thebodyValues
property, structured as follows:However, this format does not comply with RFC8621
The correct format should move the specific header from
bodyValues
tohtmlBody
/textBody
: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
The text was updated successfully, but these errors were encountered: