[GH-ISSUE #634] Manual tag colors + ignoring tags #398

New issue

Closed

opened 2026-03-15 14:14:45 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 14:14:45 +03:00

Owner

Originally created by @CosmicBara on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/axllent/mailpit/issues/634

Appreciate all the work and effort on this project!

I was wondering if these two tag-related features were at all on y'all's radar:

Manual tag colors? Like, as tags come in, auto-color them, but let us override the color when it matches something else a little too closely.

As an example, I tag my emails with the "environment" it came from (think: Dev, QA, Prod, etc.) but we have multiple sets of each environment (think: Dev1, Dev2, QA1, QA2). The problem is, the tags for env-dev and env-qa end up matching a little too closely, making it hard to differentiate them. Might be nicer to be manually adjust this as needed, and would allow for things like making env-dev and env-dev2 both different shades of green, and env-qa and env-qa2 different shades of blue, etc.

It seems that emails sent with a + in the username section (eg: someemail+somethingelse@domain.com) also creates a tag for them. Can we disable this? When I delete the tag manually in Mailpit, whenever a new email appears with that tag it gets re-added. Is there a way to always ignore that tag? Or perhaps to turn off the automated tagging from the + in the email? Ideally both approaches would be great!

Originally created by @CosmicBara on GitHub (Jan 28, 2026). Original GitHub issue: https://github.com/axllent/mailpit/issues/634 Appreciate all the work and effort on this project! I was wondering if these two tag-related features were at all on y'all's radar: 1. Manual tag colors? Like, as tags come in, auto-color them, but let us override the color when it matches something else a little too closely. - As an example, I tag my emails with the "environment" it came from (think: Dev, QA, Prod, etc.) but we have multiple sets of each environment (think: Dev1, Dev2, QA1, QA2). The problem is, the tags for `env-dev` and `env-qa` end up matching a little too closely, making it hard to differentiate them. Might be nicer to be manually adjust this as needed, and would allow for things like making env-dev and env-dev2 both different shades of green, and env-qa and env-qa2 different shades of blue, etc. - <img width="141" height="183" alt="Image" src="https://github.com/user-attachments/assets/6018e821-f42d-4c3c-b3ba-6a3de0088460" /> 2. It seems that emails sent with a + in the username section (eg: someemail+somethingelse@domain.com) also creates a tag for them. Can we disable this? When I delete the tag manually in Mailpit, whenever a new email appears with that tag it gets re-added. Is there a way to always ignore that tag? Or perhaps to turn off the automated tagging from the + in the email? Ideally both approaches would be great!

kerem closed this issue

2026-03-15 14:14:50 +03:00

kerem commented

2026-03-15 14:14:56 +03:00

Author

Owner

@axllent commented on GitHub (Jan 29, 2026):

Hi @CosmicBara. I appreciate the complement, and I'm happy to hear you're using Mailpit!

Whilst I completely understand your point about the colors, there are currently no current plans to add custom colors as I think that would add a significant chunk of complexity & functionality to the web UI for relatively little benefit, and if it existed (the option to configure this), then it would be an entirely browser-based option - so if you switched browsers then they would show in their original colors.

Lastly the auto-tagging of messages based on "plus addressing" (eg: test+tag@domain) can be specifically disabled - please see the documentation - specifically --tags-disable plus-addresses (or environment variable MP_TAGS_DISABLE="plus-addresses").

I hope this helps?

@axllent commented on GitHub (Jan 29, 2026): Hi @CosmicBara. I appreciate the complement, and I'm happy to hear you're using Mailpit! Whilst I completely understand your point about the colors, there are currently no current plans to add custom colors as I think that would add a significant chunk of complexity & functionality to the web UI for relatively little benefit, and if it existed (the option to configure this), then it would be an entirely browser-based option - so if you switched browsers then they would show in their original colors. Lastly the auto-tagging of messages based on "plus addressing" (eg: `test+tag@domain`) can be specifically disabled - please see [the documentation](https://mailpit.axllent.org/docs/usage/tagging/) - specifically `--tags-disable plus-addresses` (or environment variable `MP_TAGS_DISABLE="plus-addresses"`). I hope this helps?

kerem commented

2026-03-15 14:15:01 +03:00

Author

Owner

@CosmicBara commented on GitHub (Jan 29, 2026):

I didn't notice the plus-addresses option, thanks! That is exactly what I wanted.

I'm disappointed to hear about the colors issue. I wonder why it would be entirely browser-based? Why can't the colors be stored in the local db or in memory or wherever else any configuration data is stored? Or alternatively, could it just be additional arguments we can pass in to define the default tag color based on the tag name?

@CosmicBara commented on GitHub (Jan 29, 2026): I didn't notice the `plus-addresses` option, thanks! That is exactly what I wanted. I'm disappointed to hear about the colors issue. I wonder why it would be entirely browser-based? Why can't the colors be stored in the local db or in memory or wherever else any configuration data is stored? Or alternatively, could it just be additional arguments we can pass in to define the default tag color based on the tag name?

kerem commented

2026-03-15 14:15:06 +03:00

Author

Owner

@axllent commented on GitHub (Jan 30, 2026):

I didn't notice the plus-addresses option, thanks! That is exactly what I wanted.

Super!

I wonder why it would be entirely browser-based?

All the UI settings are browser based, such as toggling on/off the tag colors, theme, timezone, etc. The reason is that Mailpit is not designed to be multi-user, even though multiple users can of course use it.

Why can't the colors be stored in the local db or in memory or wherever else any configuration data is stored?

Mailpit does not retain any UI "user settings" beyond the web browser user storage ("cookies"). Implementing this feature would greatly increase the application's complexity and require considerable development effort. It would necessitate changes to the frontend for editing, loading, and managing dynamic updates, as well as the creation of extra API endpoints to facilitate these edits and loads, in addition to modifying the database to save these settings - and all of this would be just for customizing tag colors. So to put it simply, the effort needed for to implement and maintain this feature far outweighs the benefits.

I hope this makes sense?

@axllent commented on GitHub (Jan 30, 2026): > I didn't notice the `plus-addresses` option, thanks! That is exactly what I wanted. Super! > I wonder why it would be entirely browser-based? All the UI settings are browser based, such as toggling on/off the tag colors, theme, timezone, etc. The reason is that Mailpit is not designed to be multi-user, even though multiple users can of course use it. > Why can't the colors be stored in the local db or in memory or wherever else any configuration data is stored? Mailpit does not retain any UI "user settings" beyond the web browser user storage ("cookies"). Implementing this feature would greatly increase the application's complexity and require considerable development effort. It would necessitate changes to the frontend for editing, loading, and managing dynamic updates, as well as the creation of extra API endpoints to facilitate these edits and loads, in addition to modifying the database to save these settings - and all of this would be just for customizing tag colors. So to put it simply, the effort needed for to implement and maintain this feature far outweighs the benefits. I hope this makes sense?

kerem referenced this issue

2026-03-15 14:25:12 +03:00

[PR #398] [CLOSED] Chore(deps): Bump github.com/lithammer/shortuuid/v4 from 4.0.0 to 4.1.0 #543