In this space there is also Mailpit[0], written in GO, runs from a single binary (also has Docker images).
MailCrab
11–20 of 36 posts
Re: MailCrab
#12Typo
* _its_ own bullet
Re: MailCrab
#13That’s nice since MailHog seems dead. I’ve had PRs open for their SMTP server package for years. One for a bug, the other to support Unicode recipient addresses.
Once I got one of their attention on Twitter and they said they would have it looked at the next week, but nothing seemed to happen.
Re: MailCrab
#14One of the things I like about Django is the builtin support for a console backend for emails In dev it means you can have sent emails get logged to the terminal which makes debugging easier. But it only really works well with text emails, this seems like a more robust solution
The terminal solution is handy but sometimes it fails because you could end up with a sign in link or some type of link with a very long token that wraps to multiple lines making it impossible to click. Rails also prints emails to the terminal and has a backend solution that doesn't really send emails out but I still prefer using MailCatcher to display them in a UI (it has both amd64 and arm64 Docker support[0], real…
It also just works for all frameworks if you hack the receiver and BCC: emails you want to test to yourself to make sure they're actually being sent and look alright.
Re: MailCrab
#15Embarrassed to ask, so what’s the use case for this?
Re: MailCrab
#16In 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
A tiny cross-platform binary, a tiny docker image image? That’s every bullet point but the written in rust one!
Re: MailCrab
#17Looking forward to trying this out. I do a lot of email testing locally for paced.email and vend.email. MailHog is 90% of the way there, but seems like it's fallen by the wayside...
Re: MailCrab
#18Embarrassed to ask, so what’s the use case for this?
One use-case I can think of is integration and validation tests. Send emails, then use the API to programmatically retrieve and check content.
Re: MailCrab
#19For shared non-production environments, I’ve always been a big fan of Mailtrap.io in this space. Same idea of faking delivery but puts it in a location where non-devs can access and review it. https://mailtrap.io/
You could also look at https://imitate.email
Similar idea to mailtrap but has a web widget so that you can embed it in the projects you’re building, improving the UX for devs and testers.
(Disclaimer: It’s mine!)
Re: MailCrab
#20Embarrassed to ask, so what’s the use case for this?
It's really useful during development to test email send functionality in your app.