In my process of changing some X tools for console tools I am testing mutt with gmail accounts.

I have a working gmail (account_1) with app password, TLS and authentication user for pop, and login for smtp.

I have a working gmail (account_2) with oauth and "oauthbearer:xoauth2" for authentication both smtp and pop.

I don't use imap.

I use only mutt to send and fetch mails, no 3rt aplications like fetchmail, getmail or procmail. msmtp, sSMTP or opensmtpd.

Some problems I encountered hope someone can help:

1- To get mails I use push <fetch-mail> when enter on the mailbox folder. Or I use "G" . Playing with idle timeout but not found a config to automate fetch mails from mutt (seems is not possible). Sure I need external program but I want to have the minimum applications and configs possible. Some tips to automate the fetch in mutt?

2- With oauth account_2 I created the gmail application in testing mode, the token renew is to short. To deal with the oauth token renovation it is needed to set up application in production. https://stackoverflow.com/questions/...token-duration What implications have it? It is fine for normal users? it is free? Seems it is not for users or I need go deeper?

3- If oauth are not viable I can deal with app passwords because I don't have to much sensitive information in my mails, and maybe I can set up some gpg to crypt sensitive data but... Did you think app_password authentication system (TLS and login) are fine?

Self response for 3, looking/thinking when writing, TLS seems ok, the only oauth advantage are fine tune on the application permissions. Rigth?
TLS is a well tested technology and 16 lowercase chars are "strong". So why google call this: access for insecure applications? This guys scared me but seems this is the way.

Thanks in advance.