MailCatcher VS Mosh

hey HN, I recently published an article going deep into email previewing (in Ruby on Rails, but I think it's relevant beyond Rails).

MailCatcher (https://github.com/sj26/mailcatcher) and MailHog (https://github.com/mailhog/MailHog) are super handy and easy to run locally. Both spin up an SMTP server which you can direct mail to, and give you a nice web interface to browse mail and preview it.

Happy to answer any question! thanks, harrison

A couple others

* Mail Catcher https://mailcatcher.me/

Useful. Seems very similar to MailCatcher, but not depending on Ruby is always a plus.

I just upgraded to Alpine Linux 3.16.1 This is an important upgrade as it fixes 2 major issues: - busybox CVE-2022-30065 - openssl CVE-2022-2097 Related information: Mailcatcher as a docker image using Alpine Linux 3.16.1: https://hub.docker.com/r/stpaquet/alpinemailcatcher Github repo: https://github.com/spaquet/docker-alpine-mailcatcher Mailcatcher: https://mailcatcher.me

Mailcatcher: https://mailcatcher.me

Mailhog sounds a lot like mailcatcher

I would install https://mailcatcher.me and see if that local smtp works.

Useful links: Mailcatcher homepage: mailcatcher.me Dockerfile and Docker Compose: https://github.com/spaquet/docker-alpine-mailcatcher Dockerhub: https://hub.docker.com/r/stpaquet/alpinemailcatcher

I can run MailCatcher or MailHog or Postfix or Sendmail or any number of other solutions, but there's not any other linux sysadmins here so something with an easy gui setup would be convenient so others can poke around if needed.

If you haven’t already, and I know this doesn’t hold up for GUI emacs or vim, but consider running them through https://mosh.org/

FWIW, I wouldn't try to parse escape sequences "directly" from the input bytestream -- it's easy to end up with annoying bugs. Longer-term it's probably better to separate the logic e.g.:

- First step (for a UTF-8-input terminal emulator) means "lexing" the input bytestream as UTF-8 into a stream of USVs, which involves some subtleties (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- Second step is to run the DEC parser/FSM logic on the sequence of USVs, which is independent of the escape sequences (https://vt100.net/emu/dec_ansi_parser ; https://github.com/mobile-shell/mosh/blob/master/src/termina...).

- And then the third step is for the terminal to execute the "dispatch"/"execute"/etc. actions coming from the FSM, which is where the escape sequences and control chars get implemented (https://github.com/mobile-shell/mosh/blob/master/src/termina...).

Without this separation, it's easier to end up with bugs where, e.g., a UTF-8 sequence or an ANSI escape sequence is treated differently when it's split between multiple read() calls vs. all in one call.

Btw, you can use mosh to hide the latency of SSH. https://mosh.org/

I've been using Kitty's SSH features for as long as I can remember but I recently setup Mosh and I really like how it doesn't drop connections and supports roaming.

I am surprised many people write about ssh into a server. Mosh[1] feels more responsive and it also supports longer sessions.

[1] - https://mosh.org/

Also they support Mosh which I install on my servers. It's way better than plain ssh when you're on mobile networks and wifi, especially with connections that are unreliable or bandwidth-constrained.

I’ve recently been experimenting with MoSH (Mobile Shell). Basically think SSH but with UDP - so more resilient to shoddy network conditions, roaming access points, etc.

If it is not for production (e.g. running as a daemon or a server) and you only care about the development, another ad-hoc way is using screen/tmus-like software incl. byobu, and combine it with mosh.