← Back to context

Comment by kmarc

2 years ago

Similarly, albeit with much less effort, I configured (neomutt) into the most beautiful and best, rapid UX mail client ever. I use it at work and for private purposes.

People are impressed when looking at it. A handful of them asked for the config. Don't think any one ever got used to it.

How did you configure neomutt? I mostly have the default configuration, with some other tweaks I've forgotten about (like changing mailboxes using a function key). What am I missing out?

What about SSO? Sadly, none of the terminal-based email clients I tried supported this, but since you said you use this at work, maybe it supports SSO login to your work email?

  • It's a bit of a trek to get there, but here's how to work around SSO...

    1. Go to the Microsoft/Google developer console with your work account and create an "internal app" for personal use 2. Generate a set of oauth2 creds under the app 3. Use a program like mbsync or offlineimap to sync your mail down to a maildir. Iirc mbsync was more reliable but required a shim script to convert oauth2 creds to an api token. 4. Point your email client to the mail-dir.

    I had this set up when I used gmail at work, but AIUI outlook should work roughly the same.

    There's a ton of blog posts out there of people setting this up, unfortunately too many variations to have "one true" guide, so sorta have to pull from several places.

  • How would SSO work for a terminal? What would it do?

    • In this case it's easier to bypass SSO with a set of oauth2 creds, but the aws and azure clis support SSO login by opening a browser to authenticate and generate a short-lived api token that gets passed back to the cli. So it's definitely possible for terminal apps to support SSO.