3 ms·

After gmail recently greeted my mutt/IMAP request (which had worked perfectly for over a decade!) with "login failed", i've embarked upon the slow winding road

After gmail recently greeted my mutt/IMAP request (which had worked perfectly for over a decade!) with "login failed", i've embarked upon the slow winding road to getting mutt to use OAuth2, or is it OAUTHBEARER?, for gmail. Out of a dozen or so hints spanning the last couple of years (many which depend on having python2 still around), i'd humbly promote these links to best hints: [1] http://www.dcs.gla.ac.uk/~jacobd/posts/2022/03/configure-mutt-to-work-with-oauth-20/ http://www.dcs.gla.ac.uk/~jacobd/posts/2022/03/configure-mut... [2] https://www.reddit.com/r/backtickbot/comments/kyuq11/httpsnpredditcomrlinuxcommentskyhr5owhat_email/ https://www.reddit.com/r/backtickbot/comments/kyuq11/httpsnp... Please post any better sites you discover. It really is an overly server specific mess.

miguelitosd 4y ago
The other option, per a couple sites like: https://gist.github.com/bnagy/8914f712f689cc01c267 https://gist.github.com/bnagy/8914f712f689cc01c267 I set up application passwords, then configure a gmail rc file ~/.muttrc.gmail with the important bits: source "gpg -d ~/.pass/gmail-mutt.asc|" set from="ME@gmail.com" set spoolfile="imaps://imap.gmail.com/INBOX" set folder="imaps://imap.gmail.com/" set postponed="imaps://imap.gmail.com/[Gmail]/Drafts" and the GPG encrypted file has the following: set imap_user="ME" set imap_pass="APP_PASSWORD" set imap_idle="yes" set smtp_url="smtps://ME@gmail.com:APP_PASSWORD@smtp.gmail.com:465/' I wrapped a simple gmail command to run: mutt -F ~/.muttrc.gmail GPG pops up a password prompt, then mutt does it's thing and works just fine.