Which feature or improvement would you like to request?
The current JMAP Identity signature fields (htmlSignature and textSignature) have a hard limit of 2048 characters, which is too restrictive for modern email signatures.
Many business email signatures include:
Company logos (as base64 inline images)
Rich HTML formatting
Contact information with social media icons
A typical signature with a small logo easily exceeds 2048 characters due to base64 encoding.
Requested change: Increase the limit to at least 100KB (102400 characters) for htmlSignature ?
Is your feature request related to a problem?
When trying to update an Identity with an HTML signature containing an inline image (base64 encoded logo), the JMAP server returns:
{"methodResponses":[["Identity/set",{"accountId":"h","notUpdated":{"XX":{"type":"invalidProperties","description":"Field could not be set.","properties":["htmlSignature"]}}},"XX"]],"sessionState":"XX"}
Code of Conduct
Which feature or improvement would you like to request?
The current JMAP Identity signature fields (htmlSignature and textSignature) have a hard limit of 2048 characters, which is too restrictive for modern email signatures.
Many business email signatures include:
Company logos (as base64 inline images)
Rich HTML formatting
Contact information with social media icons
A typical signature with a small logo easily exceeds 2048 characters due to base64 encoding.
Requested change: Increase the limit to at least 100KB (102400 characters) for htmlSignature ?
Is your feature request related to a problem?
When trying to update an Identity with an HTML signature containing an inline image (base64 encoded logo), the JMAP server returns:
{"methodResponses":[["Identity/set",{"accountId":"h","notUpdated":{"XX":{"type":"invalidProperties","description":"Field could not be set.","properties":["htmlSignature"]}}},"XX"]],"sessionState":"XX"}Code of Conduct