starred/mailpit

Fork 0

mirror of https://github.com/axllent/mailpit.git synced 2026-04-26 08:45:54 +03:00

[GH-ISSUE #169] Feature request: Delete or tag after release #113

New issue

Closed

opened 2026-03-15 12:38:16 +03:00 by kerem · 6 comments

kerem commented

2026-03-15 12:38:16 +03:00

Owner

Originally created by @mk-git on GitHub (Sep 26, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/169

I came across mailpit a few days ago while looking for a mailtrap with a release option. So I can check mails before they leave the building (or go to the customer). The release works flawlessly.

My feature request: would it be possible to add an option to automatically delete a mail after release or automatically tag it after release?

Version: Mailpit (v1.9.2) as container

Originally created by @mk-git on GitHub (Sep 26, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/169 I came across mailpit a few days ago while looking for a mailtrap with a release option. So I can check mails before they leave the building (or go to the customer). The release works flawlessly. My feature request: would it be possible to add an option to automatically delete a mail after release or automatically tag it after release? Version: Mailpit (v1.9.2) as container

kerem

2026-03-15 12:38:16 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-15 12:38:32 +03:00

Author

Owner

@axllent commented on GitHub (Sep 26, 2023):

Glad to hear it's working well for you @mk-git! I assume you are manually releasing individual messages here? If so, then I'm sure I could add a delete option (tickbox) to the UI when you release a message. Would that work for you?

@axllent commented on GitHub (Sep 26, 2023): Glad to hear it's working well for you @mk-git! I assume you are manually releasing individual messages here? If so, then I'm sure I could add a delete option (tickbox) to the UI when you release a message. Would that work for you?

kerem commented

2026-03-15 12:38:37 +03:00

Author

Owner

@mk-git commented on GitHub (Sep 26, 2023):

Hi. Yes I release the mails manually.
Yes, a way to delete directly would be great. But maybe for one or the other case it would be better to set a tag, e.g. "released". Then it remains flexible for everyone.

If you delete you don't need the tag. But vice versa, if you release but don't delete (or forget to click on it) nobody knows that it was already released once. then the tag would help to identify which ones were already released.

For me the "delete on release" function would already help, but I think together with a tag it is more flexible.

@mk-git commented on GitHub (Sep 26, 2023): Hi. Yes I release the mails manually. Yes, a way to delete directly would be great. But maybe for one or the other case it would be better to set a tag, e.g. "released". Then it remains flexible for everyone. If you delete you don't need the tag. But vice versa, if you release but don't delete (or forget to click on it) nobody knows that it was already released once. then the tag would help to identify which ones were already released. For me the "delete on release" function would already help, but I think together with a tag it is more flexible.

kerem commented

2026-03-15 12:38:42 +03:00

Author

Owner

@axllent commented on GitHub (Sep 27, 2023):

While I always like the idea of flexibility, I do not think that setting a pre-configured tag is exactly "flexible", plus it introduces additional code logic that needs to be maintained, and included in yet another environment variable / cli flag: this user wants it called "X", the next wants it called "Y", the next wants it to replace all tags with "B", the next want it to append to the existing tags with "W" etc. One of the downsides of maintaining a popular project is any change you make has a far greater impact & thus reaction :)

I will however add a tickbox to optionally delete the message after release as this doesn't modify the existing functionality much. If you would like to add a tag, then you can always just add that once the modal is closed.

@axllent commented on GitHub (Sep 27, 2023): While I always like the idea of flexibility, I do not think that setting a pre-configured tag is exactly "flexible", plus it introduces additional code logic that needs to be maintained, and included in yet another environment variable / cli flag: this user wants it called "X", the next wants it called "Y", the next wants it to replace all tags with "B", the next want it to append to the existing tags with "W" etc. One of the downsides of maintaining a popular project is any change you make has a far greater impact & thus reaction :) I will however add a tickbox to optionally delete the message after release as this doesn't modify the existing functionality much. If you would like to add a tag, then you can always just add that once the modal is closed.

kerem commented

2026-03-15 12:38:48 +03:00

Author

Owner

@axllent commented on GitHub (Sep 29, 2023):

I have just released v1.9.4 which includes the ability to delete a message after release (tickbox, default off). Please have a test and let me know if this works for you? Thanks!

@axllent commented on GitHub (Sep 29, 2023): I have just released v1.9.4 which includes the ability to delete a message after release (tickbox, default off). Please have a test and let me know if this works for you? Thanks!

kerem commented

2026-03-15 12:38:53 +03:00

Author

Owner

@mk-git commented on GitHub (Sep 30, 2023):

Works flawlessly. many thanks for the fast integration. ❤

@mk-git commented on GitHub (Sep 30, 2023): Works flawlessly. many thanks for the fast integration. ❤

kerem commented

2026-03-15 12:38:58 +03:00

Author

Owner

@axllent commented on GitHub (Sep 30, 2023):