[Feature]: Make labels prefix user definable #139

Open
opened 2026-11-21 21:16:53 +00:00 by faisal · 0 comments

Since there is no official standard for user defined labels/keywords in JMAP it could be a pain if you use different mail clients which handle labels differently. A label defined in ihasmail would not be shown if the other client is coded to use a different label syntax.

For example, Bulwark labels have a "$label:" prefix. While ihasmail names their labels simply "$label" or "label". The JMAP syntax below shows the same label, added twice; once by each client, as they have different approaches to label syntax.

"keywords": {
            "$label:updates": true, //Bulwark
            "updates": true, //ihasmail
            "$seen": true
          },

Adding a setting "User defined prefix" to the labels settings would allow a user to make labeling consistent across the clients they use. Could be left empty to keep current method, or could be defined if wanted.

Since there is no official standard for user defined labels/keywords in JMAP it could be a pain if you use different mail clients which handle labels differently. A label defined in ihasmail would not be shown if the other client is coded to use a different label syntax. For example, Bulwark labels have a "$label:" prefix. While ihasmail names their labels simply "$label" or "label". The JMAP syntax below shows the same label, added twice; once by each client, as they have different approaches to label syntax. ``` "keywords": { "$label:updates": true, //Bulwark "updates": true, //ihasmail "$seen": true }, ``` Adding a setting "User defined prefix" to the labels settings would allow a user to make labeling consistent across the clients they use. Could be left empty to keep current method, or could be defined if wanted.
jcoffey-dev added the enhancement
priority
p3
labels 2026-11-22 01:25:08 +00:00
jcoffey-dev self-assigned this 2026-11-22 01:25:08 +00:00
jcoffey-dev added this to the 27.7 milestone 2026-11-22 01:25:08 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-webmail#139