mailpit

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.

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

I have used tools like these for nearly a decade and find them invaluable. My current favourite is Mailpit [1]. The “OG” I would consider Mailcatcher [2] from my Rails days [1] https://github.com/axllent/mailpit [2] https://mailcatcher.me/

Yep, mailhpg works, but is not anymore maintained. We have been successfully using https://github.com/axllent/mailpit

I have not tested it, still using smtp-sink from postfix tools but there is Mailpit [1] which may fit your needs assuming that you BCC each account from the sending address to accomplish the "Sent" aspect of your requirements. meaning people would see what you sent and then the responses. [1] - https://github.com/axllent/mailpit

I agree with pwg that postfix is fairly straight forward but to answer your question there are debugging programs that capture email such as mailpit [1] but I don't know if you would consider that to be easier. I have not tried it out yet as I have always used smtp-sink for debugging part of postfix tools. Mailpit has a nifty web UI and claims to process 70 to 100 emails per second. The reason I suggested Postfix is due to the nature of it being on many internet facing servers and being battle-hardened over the decades and having started off very secure. Anything else should probably be confined behind bubblewrap and AppArmor or SELinux. Regardless of what tool you end up using consider adding firewall rules to explicitly block outbound SMTP in the event someone finds a way to relay through whatever tool you end up using as a bumper-gu

My work machine is prohibited from connecting to port 25 outside of the accepted work systems. When on VPN, I can't even connect to port 25 within the local networks. docker run -d --name=mailpit --restart unless-stopped -p 8025:8025 -p 1025:1025 axllent/mailpit I can connect to port 1025 just fine. --- This test data isn't something that should be leaving the local network either. Can you run mailtrap.io on your local machine or in your data center? --- Oops, I accidentally set it to send all the emails. How much does it cost to handle 500 email in the next few minutes? Mailpit is free. --- That 500 test email that were sent to mailpit, they're correct and should be sent out to the testers. https://github.com/axllent/mailpit/wiki/SMTP-relay What is the cost to forward 500 emails this week? And again next week? --- Mailpit (and i

In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images). [0]: https://github.com/axllent/mailpit