11–20 of 51 posts
I prefer self-hosting MailHog: https://github.com/mailhog/MailHog
From the Mailpit README: > Mailpit was originally inspired by MailHog which is no longer maintained and hasn't seen active development or security updates for a few years now.
Security updates sure, but what really needs to update on an STMP (+ TLS?) solution?
hugged to death? anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation! well done!
That's the wrong status code The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time ("rate limiting"). Unless the server believes you as an individual user were sending too many it should not have been a 429 If the server was unable to handle the volume of requests more generally it should have been a 503 which also supports Retry-After
Either something is wrong with my rate-limiting code or there are many people behind a single IP address.
Anyway the limits are increased now.
Comes with a small API so your integration tests can actually check the contents of emails that were expected to be sent out. Did a Show HN a while ago with more details - https://news.ycombinator.com/item?id=40590670
Earlier quoted context omitted.
That's the wrong status code The HTTP 429 Too Many Requests response status code indicates the user has sent too many requests in a given amount of time ("rate limiting"). Unless the server believes you as an individual user were sending too many it should not have been a 429 If the server was unable to handle the volume of requests more generally it should have been a 503 which also supports Retry-After
The 429 response is sent when rate-limiting (based on IP address). Either something is wrong with my rate-limiting code or there are many people behind a single IP address. Anyway the limits are increased now.
Earlier quoted context omitted.
From the Mailpit README: > Mailpit was originally inspired by MailHog which is no longer maintained and hasn't seen active development or security updates for a few years now.
Curious as to why it would need updates. Security updates sure, but what really needs to update on an STMP (+ TLS?) solution?
Although in mailhog's case it looks like STARTTLS was never implemented. Hence the forks.
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/