Sup VS Mail

Sup is also “a console-based email client for people with a lot of email”: https://sup-heliotrope.github.io/

A long time ago I used https://sup-heliotrope.github.io/ , which is sort of mutt with a gmail approach to email. Being a curses-based email client, it of course lets you shell out to vim for writing your email.

I enjoyed reading the Philosophy [1] behind Sup, for the glimpse into how Gmail's immediate search feature changed how people use email clients, and how it inspired Sup.

[1]: https://github.com/sup-heliotrope/sup/wiki/Philosophy

"2.8.0.1. Fixes file permissions in 2.8.0 release. No code changes."

https://github.com/mikel/mail/tags

I would look to existing libraries to see how they solve the problem. Stack Overflow is OK, but I find that the "one liner" solutions you find there often oversimplify. There is a popular, and currently maintained, Rubygem library called Mail that includes a class for quoted printable, which in turn provides a class method for decoding quoted printable strings.

This is easiest if you have a MacBook since Ruby is installed by default. You can make a small script using this Ruby gem (plugin) - https://github.com/mikel/mail

There are basically three levels of address checking:

1) You need to validate an email field for login or a website - checking for an @ mark with some text before and at least one . after the @ will do for this.

2) You need to do some sort of address validation, library regexps like this will do for 99.9...% of these.

3) You are building an email handling system which needs to actually support the RFCs, in which case regexp will not handle what you need, and you need to use a proper parser, like https://github.com/mikel/mail/tree/master/lib/mail/parsers

Ref: I am the original author of the Ruby mail gem.

Email addresses have a lot of gotchas that can make rolling your own logic hard. I haven't used Ruby in a while but there are gems like Mail that can help validating email addresses easier.