On Sun, 20 Mar 2022, Roderick wrote:
> This authorization process is not simple, and with my nettop, when I am
> not at home, difficult, if not impossible.
>
> The question is why google rejects alpine as not fulfilling who knows
> what. And even if the problem is solved, it seems google changes the
> rules continuosly, one cannot rely on google.
I do not want to speak badly about google when they already speak badly
about themselves.
I do not know what you want to accomplish. The problem you found using
Alpine you will have it with any other app that uses the same client-id
and client-secret that you are using with Alpine. You do not need to get a
client-id and client-secret anymore, all you need to do is to authorize
Alpine every week using the same client-id and client-secret. I have done
this process so many times that I can do it in a short amount of time, and
so I see it as a small incovenience, but since you went through a painful
process to get this working, the memory of the pain is still fresh on you
and no matter what you do (using mbsync or Alpine) you will have to go
through this process every week. I am sorry this is the case, but this
issue will not disappear because you will use other programs than Alpine,
so if there is a better app than Alpine for you, use that because it is
better. This issue that you want to solve will not go away.