On Friday, 06.05.2022 at 22:38 +0800, lilydjwg wrote: > On Fri, May 06, 2022 at 03:32:38PM +0100, Dave Ewart wrote: > > [...] > > > > What are the implications of the access code expiring? I don't see any > > symptoms which might be associated with that and the Mutt client is > > running in 'screen' 24/7/365. > > When it expires you need to login via web and copy the code again. You > mean your access code doesn't expire? That's a good thing. Maybe it only > applies to recently created apps (e.g. mine).
I don't have to do that, no. I put this: set imap_oauth_refresh_command="~/src/google-oauth-for-mutt/oauth2.py --quiet --user=<email> --client_id=<STUFF.apps.googleusercontent.com --client-secret=SECRET --refresh_token=TOKEN" in my config in 2020 and I've never had to change it. Maybe I should just sit quietly and be glad that it all works and hope it continues that way :-) Dave. -- Dave Ewart da...@sungate.co.uk, http://twitter.com/DaveEwart All email from me is digitally signed, http://www.sungate.co.uk/ GPG key updated Jan 2013 see http://www.sungate.co.uk/gpg Fingerprint: CF3A 93EF 01E6 16C5 AE7A 1D27 45E1 E473 378B B197