←back to thread

297 points mooreds | 2 comments | | HN request time: 0s | source
Show context
iruoy ◴[] No.42175560[source]
A tool like this is very useful, but this one isn't being maintained anymore. MailHog isn't either.

MailPit, MailCrab and smtp4dev are modern alternatives.

https://github.com/axllent/mailpit

https://github.com/tweedegolf/mailcrab

https://github.com/rnwood/smtp4dev

replies(17): >>42175787 #>>42175928 #>>42176115 #>>42176725 #>>42176926 #>>42177546 #>>42177804 #>>42178339 #>>42178590 #>>42178720 #>>42179230 #>>42180316 #>>42182891 #>>42183452 #>>42183958 #>>42184126 #>>42187070 #
Saris ◴[] No.42176115[source]
Does it need maintenance? It doesn't seem like much of a problem for working software that is local only.
replies(2): >>42176910 #>>42177607 #
hoistbypetard ◴[] No.42176910[source]
It really only likely matters if you're one of those who is tempted to let it run on `0.0.0.0` instead of loopback only.

Assuming you're not, there's certainly no urgency to migrate. But keep it in the back of your mind that it's unmaintained, and if things go weirdly wrong during an OS or ruby upgrade, remember that you will need to fix it or pick up something else that's kind of similar.

If you're not already using it, it might be a good idea to pick up something else.

I like [mailpit](https://github.com/axllent/mailpit) because it's a single static binary and because it has a nice api I can use during testing to see if a message made it out of the system I'm testing.

But none of that argues for switching away from a thing that's working for you.

replies(1): >>42177346 #
1. nicoburns ◴[] No.42177346[source]
This kind of product could also be useful in shared development environments (such as the sort that QA teams might have access to for example).
replies(1): >>42177634 #
2. andix ◴[] No.42177634[source]
I've seen a few shared Mailpit installations in companies. I think that's a quite popular pattern.