Comments on: mutt integration with Gmail using OAuth https://luxing.im/mutt-integration-with-gmail-using-oauth/ Thoughs and things Sun, 04 Jun 2023 06:41:48 +0000 hourly 1 https://wordpress.org/?v=6.7.2 By: Luxing Huang https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-444 Sun, 04 Jun 2023 06:33:23 +0000 https://luxing.im/?p=813#comment-444 In reply to John Hinsdale.

It is 2023 and I am still using it fine.

]]> By: John Hinsdale https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-435 Wed, 04 May 2022 22:23:29 +0000 https://luxing.im/?p=813#comment-435 Hi Google is now saying the “out of band” Oauth will be deprecated in late 2022. Any ideas on how to keep Mutt working with Gmail?

]]> By: Kent https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-130 Fri, 27 Nov 2020 11:33:16 +0000 https://luxing.im/?p=813#comment-130 Thanks for a great guide.

Are there any security issues with storing the client_secret and/or refresh token in a .dotfiles repo on GitHub.

]]> By: Luxing Huang https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-129 Sat, 14 Nov 2020 06:06:48 +0000 https://luxing.im/?p=813#comment-129 In reply to archlicker.

Thanks for the Python3 update!

]]> By: archlicker https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-128 Mon, 09 Nov 2020 15:46:24 +0000 https://luxing.im/?p=813#comment-128 Hi. Great writeup. There is a mutt_oauth2.py script you can use now, which works with python3 (finally I can get rid of python2). I’m using it, and seems to work fine. https://gitlab.com/muttmua/mutt/-/blob/master/contrib/mutt_oauth2.py.README

]]> By: Luxing Huang https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-127 Fri, 21 Feb 2020 20:37:01 +0000 https://luxing.im/?p=813#comment-127 In reply to Nathaniel Evan.

Exactly

]]> By: Nathaniel Evan https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-124 Thu, 13 Feb 2020 01:53:32 +0000 https://luxing.im/?p=813#comment-124 In reply to Nathaniel Evan.

Sorry, I just noticed that you put the refresh token in the config file, not the access token itself. I take it, this is all that’s needed? If the access token expires, the same command will retrieve a new access token automatically?

]]> By: Nathaniel Evan https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-123 Thu, 13 Feb 2020 01:46:39 +0000 https://luxing.im/?p=813#comment-123 Hi, thanks for this neat guide you wrote. The access token I received is only valid for 3599 seconds; how do I get a permanent access token, so I could write it in the mutt config file without having to manually change the access token every time it expires?

]]> By: Luxing Huang https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-122 Sun, 02 Feb 2020 06:53:08 +0000 https://luxing.im/?p=813#comment-122 In reply to Rodrigo.

The asc files are generated by the following command:

gpg2 -e -r "recipient@email.address" --armor

The purpose of GPG is to not store plaintext info on my local disk

You will need to setup your GPG profile in order to use gpg.

]]> By: Rodrigo https://luxing.im/mutt-integration-with-gmail-using-oauth/#comment-121 Tue, 31 Dec 2019 03:37:50 +0000 https://luxing.im/?p=813#comment-121 Hi

Thanks for the article but what about those GPG “asc” files? Can you elaborate a little bit on that or provide some resource? thanks.

]]>