Ah the famous test@test.test email addresses we used to use in our test scripts to avoid sending email to anyone by accident. If we need to test the contents of the email then we use Mailhog these days. Can’t recommend it enough.
Serious question: SMTP clients from 20 years ago are basically compatible with today's. Is it necessary to continuously maintain a piece software if the requirements stay the same?
One example where I had issues with Mailhog was that the docker images was very bloated 138.8MB[0], there was a PR that should have brought it back to 7MB or something but it was never merged.
And not sure about this, but at least for docker, the included certificates can become outdated if not frequently rebuilt, and since Mailhog is software used when testing, being able to spin up a ready-to-use sandboxed instance is very useful.
Ah the famous test@test.test email addresses we used to use in our test scripts to avoid sending email to anyone by accident. If we need to test the contents of the email then we use Mailhog these days. Can’t recommend it enough.
https://github.com/mailhog/Mailhog
Yep, mailhpg works, but is not anymore maintained.
We have been successfully using https://github.com/axllent/mailpit
Serious question: SMTP clients from 20 years ago are basically compatible with today's. Is it necessary to continuously maintain a piece software if the requirements stay the same?
One example where I had issues with Mailhog was that the docker images was very bloated 138.8MB[0], there was a PR that should have brought it back to 7MB or something but it was never merged.
And not sure about this, but at least for docker, the included certificates can become outdated if not frequently rebuilt, and since Mailhog is software used when testing, being able to spin up a ready-to-use sandboxed instance is very useful.
[0] https://hub.docker.com/r/mailhog/mailhog/tags