TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 5fdcbcf9
REPLY: 2:221/1.58@fidonet eb8a5ccc
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
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 90/1 103/705 105/81 120/340 123/131 124/5016 154/10
SEEN-BY: 203/0 221/0 226/30 227/114 702 229/101 275 424 426 452 550
SEEN-BY: 229/664 1016 240/5832 249/110 206 317 400 280/464 5003 288/100
SEEN-BY: 292/854 8125 310/31 317/3 322/757 342/200 396/45 423/120
SEEN-BY: 712/848 770/1 2452/250
PATH: 280/464 229/101 426