Hi August,

On 2020-12-18 08:25:00, you wrote to me:

 AA>>> "This is fixed in TB 68.2.1, but unless there is a
 AA>>> 60.9.1 released, you can apply the workaround:

 AA> [...]

 WvV>> If I remember correctly I checked the password that was
 WvV>> set in TB, and that was the correct one. And I haven't
 WvV>> changed my gmail password in ages...

 AA> The workaround relies on making an adjustment via the
 AA> about:config, so that the retention of the password is "seen"
 AA> (or something like that).  Not sure if an existing pw would
 AA> still work after the workaround - maybe it only gets saved and
 AA> seen properly when a NEW password is configured?

Ok, you got me curious enough! ;)

I made the change in my TB config, restarted it, and added my gmail account
again. And it works fine again! We'll see if the browser window for
authentication will appear again, but so far so good...

 AA> Myself, I still stick with smtp/pop. I found that an imap
 AA> configuration simply took too much time and too much data to
 AA> sync over a metered mobile connection.

It works fine here. I want to keep the mail on the gmail server anyway, so I
can access it from other devices and see the same mail. That's where imap works
best...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815