THIS PROJECT IS DEAD!

[PaoloC68]

Just put a tombstone on it and don't lure people in! It is a pity, I just spent hours in finding out that the swagger schema is just making you waste time as it does not match the reality of the project.
There are 939 forks, more than 200 pull requests are unattended ... The maintainer should find somebody else as minimum.... Again, a big pity!
Sorry but people should be warned!

[jki21]

I just use it to test email integration and it works fine for me. What are the non-dead alternatives?

[Lenitr]

I've recently switched to maildev

It supports some more features (forwarding email, responsive testing, better support for persistent storage

Mailhog was working totally fine and I appreciate the project, but when you run into bugs/annoyances it's looking like they won't be fixed anymore unfortunately.

[Neilq5]

I just use it to test email integration and it works fine for me. What are the non-dead alternatives?

Laravel now recommends Mailpit in their latest version

[PaoloC68]

I just use it to test email integration and it works fine for me. What are the non-dead alternatives?

Laravel now recommends Mailpit in their latest version

Exactly, it is instructive to read in the Mailpit read_me the motivation that brought him to create mailpit in the first place!

[ian-kent]

Hey @PaoloC68 👋

Sorry that the swagger spec was out of date, and I appreciate it's frustrating that there's so many PRs that haven't been reviewed or merged.

I personally don't have time to maintain the project anymore, and as I no longer use it, there's little incentive to dedicate time to it like I used to - I have other projects to focus on. But I hear you and I will try to find some time to give it a bit of a spring clean (but I don't know how soon that'll be).

Having said that, I wouldn't describe the project as dead, just frail and in need of some TLC - as far as I know, MailHog still works and serves the purpose it was created for even if there are a few rough edges.

The maintainer should find somebody else as minimum....

Unfortunately this is easier said than done.

It's interesting to hear about Mailpit though - not to dismiss MailHog entirely, but since Mailpit is an actively maintained project which does basically the same thing, and created from scratch far more recently (I can't argue with the authors justification for doing this, and MailHog is 8 years old now), I'd see that as a good alternative if MailHog isn't meeting your needs.

[espen]

I use this project and it works great for my needs. Yes there are some open PRs (27 not more than 200) but it is an open source project, @PaoloC68 you didn't pay anything for this. The author doesn't owe you anything, not finding a new maintainer, not fixing the bug you encountered or anything else. You got code for free that you didn't have to write yourself (since you like to talk about wasted time). In addition there are alternatives if you feel that it doesn't suit your needs. Please refrain from attacking people who use their time to release code to the community for free, there are better ways of addressing any issues with OSS projects. No one is stopping you from clicking the fork button and maintaining a new fork of this project.

Thanks for all your efforts @ian-kent

[n1ngu]

@ian-kent Thanks for this excellent tool, it has been very useful to me for a long time. That said,

I personally don't have time to maintain the project anymore, [...] I wouldn't describe the project as dead, just frail and in need of some TLC

Unmaintained means dead to me. Dead in the sense that nobody should build expectations about compiling or running this software in any platform in any future, nor being able to contribute an improvement to the upstream sources.

as far as I know, MailHog still works and serves the purpose it was created for even if there are a few rough edges

While this is true, and MailHog is probably only used as a debugging local tool (no critical infrastructure at all), in the mid-term one won't be able to build it and run it without an unexpected amount of effort. There is a difference between sine-die declaring a feature freeze because you can't review PRs and never again building the docker image!

Unfortunately [finding new maintainers] is easier said than done.

Also very true and I appreciate you don't just trust whoever shows first at your door, as that can be path for harming users. Trust is not transitive. Also I don't think you have the duty of doing so.

But for the community to organize itself around a fork or a scratch-rewrite like MailPit, it would be very helpful if you acknowledged MailHog stupor by opting by some, if not all, of the following:

• archiving this repository
• pinning this issue and/or
  • Is there any updated fork of this project? #375
  • Looking for a fork #399
  • Curated list of similar software to MailHog #392
• stating the project state in the Readme, explaining the feature-freeze policy or including links to those issues

With that done, if you ever want to reboot the project you might find some fork is already updated and healthy and maybe whoever are its maintainers can join you and @gedge and @tyndyll back in https://github.com/mailhog

Thanks for everything!