1–10 of 51 posts
Use this as your SMTP server in a test environment to guarantee that your users don't receive test emails.
Looking for feedback, especially on the security side.
Show HN: A fake SMTP server for software integration testing
fakemail.stream
anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation!
well done!
The “OG” I would consider Mailcatcher [2] from my Rails days
I prefer self-hosting MailHog: https://github.com/mailhog/MailHog
I prefer self-hosting MailHog: https://github.com/mailhog/MailHog
> 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.
hugged to death? anyway - i got a great 429 back with a suggested try-after -time. it made me smile in appreciation! well done!
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