[GH-ISSUE #479] Feature Request: Customizable link in the WebUI #310

Closed
opened 2026-03-15 13:49:18 +03:00 by kerem · 4 comments
Owner

Originally created by @D-i-t-gh on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/axllent/mailpit/issues/479

Thanks for your work on this nice tool!

It would be helpful to have an option in Mailpit's WebUI that allows integrating a clickable link to external resources, such as an internal documentation page.

This link could be positioned in the header/title area, similar to your website:

Image

The link could be conditionally displayed based on configuration parameters, for example:

MP_UI_CUSTOM_LINK_NAME="Help"
MP_UI_CUSTOM_LINK_URL="<URL>"

The link would only appear if both parameters are configured with valid values.

Originally created by @D-i-t-gh on GitHub (Apr 5, 2025). Original GitHub issue: https://github.com/axllent/mailpit/issues/479 Thanks for your work on this nice tool! It would be helpful to have an option in Mailpit's WebUI that allows integrating a clickable link to external resources, such as an internal documentation page. This link could be positioned in the header/title area, similar to your website: ![Image](https://github.com/user-attachments/assets/86135e9f-6c50-45f2-9c4b-d7f06139f379) The link could be conditionally displayed based on configuration parameters, for example: ``` MP_UI_CUSTOM_LINK_NAME="Help" MP_UI_CUSTOM_LINK_URL="<URL>" ``` The link would only appear if both parameters are configured with valid values.
kerem closed this issue 2026-03-15 13:49:23 +03:00
Author
Owner

@axllent commented on GitHub (Apr 6, 2025):

Hi @D-i-t-gh. I'm glad to hear you like Mailpit! I'm going to need to give this request some more thought as thee are a few issues I can see:

  1. There isn't actually room where you have suggested. Whilst a link with a short title such as "Help" fits on a wide desktop (as per your suggestion), it definitely does not fit if the title was much longer, nor when scaling down the browser size to tablet or phone widths. There simply isn't enough room there.
  2. I always need to seriously consider things when it involves adding a new CLI flag (which goes hand-in-hand with environment variables) as there are already a lot of them (mailpit --help is already a lot to get through). In addition to that, your suggestion actually requires not just one, but two flags, both of which are required just to add a single feature.

To help me understand your requirement, can you please explain exactly what it is you are wanting to use this feature for?

<!-- gh-comment-id:2781329314 --> @axllent commented on GitHub (Apr 6, 2025): Hi @D-i-t-gh. I'm glad to hear you like Mailpit! I'm going to need to give this request some more thought as thee are a few issues I can see: 1. There isn't actually room where you have suggested. Whilst a link with a short title such as "Help" fits on a wide desktop (as per your suggestion), it definitely does not fit if the title was much longer, nor when scaling down the browser size to tablet or phone widths. There simply isn't enough room there. 2. I always need to seriously consider things when it involves adding a new CLI flag (which goes hand-in-hand with environment variables) as there are already a lot of them (`mailpit --help` is already a lot to get through). In addition to that, your suggestion actually requires not just one, but two flags, both of which are required just to add a single feature. To help me understand your requirement, can you please explain exactly what it is you are wanting to use this feature for?
Author
Owner

@D-i-t-gh commented on GitHub (Apr 6, 2025):

Hi, thank you very much for your answer! Regarding your question: consider large companies with dedicated service teams that provide self-hosted tools (such as Mailpit) to multiple development teams. In such a scenario, it would be practical for the development teams to have streamlined access to the service team for reporting issues or asking questions. I think having a link to the service team's documentation page in Mailpit would be a convenient and user-friendly solution.

However, I know that this is a feature request for a special use case, and I don't expect it will be implemented, as probably not many people are requesting this.

<!-- gh-comment-id:2781567048 --> @D-i-t-gh commented on GitHub (Apr 6, 2025): Hi, thank you very much for your answer! Regarding your question: consider large companies with dedicated service teams that provide self-hosted tools (such as Mailpit) to multiple development teams. In such a scenario, it would be practical for the development teams to have streamlined access to the service team for reporting issues or asking questions. I think having a link to the service team's documentation page in Mailpit would be a convenient and user-friendly solution. However, I know that this is a feature request for a special use case, and I don't expect it will be implemented, as probably not many people are requesting this.
Author
Owner

@axllent commented on GitHub (Apr 9, 2025):

Sorry about the delay getting back to you @D-i-t-gh. Whilst I do understand the convenience of your request, I feel it is simply not practical to implement in a meaningful manner without stashing the link away (so not to clutter the interface), thus hiding it away from plain sight (which defeats the purpose of what you are wanting).

I also think it's also fair to say that Mailpit would only be a very small part of your application ecosystem, so I would expect there would be a dedicated intranet with documentation about all the various other tools used which your users should be aware of. It's unlikely all your applications allow you to add custom links, so even if Mailpit was to have such a feature, it would only be addressing a small fraction of the apps.

As much as I want to implement every feature request, I unfortunately do have to turn down some requests, specifically when they are "special use cases" which don't offer any benefit to the application itself, and little to the wider community using Mailpit. I hope you can understand my reasoning to declining your request?

<!-- gh-comment-id:2788313205 --> @axllent commented on GitHub (Apr 9, 2025): Sorry about the delay getting back to you @D-i-t-gh. Whilst I do understand the convenience of your request, I feel it is simply not practical to implement in a meaningful manner without stashing the link away (so not to clutter the interface), thus hiding it away from plain sight (which defeats the purpose of what you are wanting). I also think it's also fair to say that Mailpit would only be a very small part of your application ecosystem, so I would expect there would be a dedicated intranet with documentation about all the various other tools used which your users should be aware of. It's unlikely all your applications allow you to add custom links, so even if Mailpit was to have such a feature, it would only be addressing a small fraction of the apps. As much as I want to implement every feature request, I unfortunately do have to turn down some requests, specifically when they are "special use cases" which don't offer any benefit to the application itself, and little to the wider community using Mailpit. I hope you can understand my reasoning to declining your request?
Author
Owner

@D-i-t-gh commented on GitHub (Apr 9, 2025):

Thanks for your answer, no problem :)

<!-- gh-comment-id:2788669259 --> @D-i-t-gh commented on GitHub (Apr 9, 2025): Thanks for your answer, no problem :)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mailpit#310
No description provided.