Re: korgalore v0.2 released with JMAP, IMAP, Maildir support

[Sudeep Holla <sudeep.holla@arm.com>]

Hi Linus,

Thanks for reporting this, I have been postponing it for a while.

On Mon, Jan 12, 2026 at 08:52:45PM +0100, Linus Walleij wrote:
> On Sun, Jan 11, 2026 at 9:16 PM Konstantin Ryabitsev
> <konstantin@linuxfoundation.org> wrote:
> 
> > > I would almost set this up to run as a cron job if it wasn't for the fact that
> > > the Googly API wants to reauthenticate every now and then. Other than
> > > that it is smooth as butter to work like this!
> >
> > I've not actually had to redo my gmail authentication again, but I do hear
> > that it's less smooth for others.
> 
> I've had to do it twice, second time today.
> 
> About that!
> 

For me, it's most 1 week and I can see that it matches the expiry in the
token.

> What happens when the token expires is this:
> 
> $ kgl pull
> (long splat like the one below)
> 

Yes I too get the same if the token has expired.

[...]

> 
> This isn't very pretty, the reason is that korgalore seems to have no idea
> about overwriting an existing authentication token.
> 
> Some try-catch thingie is needed here, right? If it's hard for you to reproduce
> I can try to do some Python hacking the next time it happens.
> 
> You have to manually do this:
> 
> rm .config/korgalore/gmail-personal-token.json

Indeed, I do this too.

> linus@Fecusia:~$ kgl auth personal
> critical: Log in to Gmail account for personal
> Please visit this URL to authorize this application:
> https://accounts.google.com/o/oauth2/auth?Authenticated target:
> personal (type: gmail)
> (...)
> Authentication complete.
> 
> Maybe this could be made more smooth, as in prompting:
> "Do you want to delete your old expired access token and get a new one?"
> 

That would be nice.

> Yours,
> Linus Walleij

-- 
Regards,
Sudeep