[GH-ISSUE #577] [suggestion] Extract the HTML checker code to a public repository #371

New issue

Closed

opened 2026-03-15 14:07:40 +03:00 by kerem · 2 comments

kerem commented

2026-03-15 14:07:40 +03:00

Owner

Originally created by @deathiop on GitHub (Oct 22, 2025).
Original GitHub issue: https://github.com/axllent/mailpit/issues/577

Hi there,

I'm working, in Golang, with emails.
The features you expose as an HTML checker is something I have a use for, and I'm basically about to redo what you already wrote in your code.

So, I'm opening this ticket in order to ask you whether you would considerate exporting this HTML checker in a public repository, as a library anyone can use.
I think this might benefit to many other people working with emails.

Thanks for reading!

Originally created by @deathiop on GitHub (Oct 22, 2025). Original GitHub issue: https://github.com/axllent/mailpit/issues/577 Hi there, I'm working, in Golang, with emails. The features you expose as [an HTML checker](https://mailpit.axllent.org/docs/usage/html-check/) is something I have a use for, and I'm basically about to redo what you already wrote [in your code](https://github.com/axllent/mailpit/tree/develop/internal/htmlcheck). So, I'm opening this ticket in order to ask you whether you would considerate exporting this HTML checker in a public repository, as a library anyone can use. I think this might benefit to many other people working with emails. Thanks for reading!

kerem closed this issue

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

kerem commented

2026-03-15 14:07:51 +03:00

Author

Owner

@axllent commented on GitHub (Oct 22, 2025):

Hi! I totally understand what you're asking here, but when I wrote Mailpit I very intentionally did not expose the internal functionality. The reason was that I did not want to be restricted by what I could and couldn't do within those "Mailpit modules" (backwards compatibility, versioning etc, plus the overheads of support, feature requests etc).

Mailpit keeps me busy enough as it is and I don't need the additional pressure of maintaining this one a separate module 😃

The source is of course free and available, so please feel free to copy/paste and build your own library.

@axllent commented on GitHub (Oct 22, 2025): Hi! I totally understand what you're asking here, but when I wrote Mailpit I very intentionally did not expose the internal functionality. The reason was that I did not want to be restricted by what I could and couldn't do within those "Mailpit modules" (backwards compatibility, versioning etc, plus the overheads of support, feature requests etc). Mailpit keeps me busy enough as it is and I don't need the additional pressure of maintaining this one a separate module 😃 The source is of course free and available, so please feel free to copy/paste and build your own library.

kerem commented

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

Author

Owner

@deathiop commented on GitHub (Oct 24, 2025):

Hey,

Thanks for your kind answer.
I do understand you don't want to give yourself more job :)

I'll take what I need then, thank you!

@deathiop commented on GitHub (Oct 24, 2025): Hey, Thanks for your kind answer. I do understand you don't want to give yourself more job :) I'll take what I need then, thank you!

kerem referenced this issue

2026-03-15 14:24:32 +03:00

[PR #371] [CLOSED] Chore: Bump modernc.org/sqlite from 1.32.0 to 1.33.1 #534