1496343 - gmail with personal domain / IMAP, error "Failed to connect via oauth: [message n.] every time I open a message

Status: RESOLVED INVALID

(Thunderbird :: Security, defect)

Description

[Gianluca]

Attachment: Screenshot from 2018-10-04 10-26-47.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce:

Since yesterday update of Thunderbird (Ubuntu Linux, Version 60.2.1) every time I open a message I get the error message "Failed to connect via oauth: [message n.]"
I use maildir, the error is on my main mailbox, IMAP, gmail with personal domain
Thunderbird still works properly downloading and moving messages
Screenshot attached


Actual results:

I still can read the complete message if it was downloaded for offline use


Expected results:

no error message

Comment 1

[Gianluca]

Attachment: Screenshot of the error message

Comment 2

[Drewzilla]

Attachment: Thunderbird v60.2.1 - Gmail oauth error message.png

Comment 3

[Drewzilla]

I am seeing the same behavior in Thunderbird v60.2.1. I keep getting the "Failed to connect via oauth: 2147500036" error every time I click a message in any folder. Thunderbird also regularly prompts me to re-login with my Gmail credentials and reauthorize via OAuth. I have 2FA enabled. Thunderbird does, however, download the messages successfully.

See also: https://bugzilla.mozilla.org/show_bug.cgi?id=1497283

Comment 4

[Jorg K (CEST = GMT+2)]

BTW:
Value	0x80004004 (2147500036)
Name	NS_ERROR_ABORT

Comment 5

[gene smith]

A "try" build of 60.2.2 with one minor and unrelated patch seems to work OK for me with gmail on linux with 2FA and maildir. I suspect the abort is being initiated by gmail but no way to know without looking with wireshark or equivalent. Or there may be some low level network logging in mozilla that can be enabled (don't see anything). Or maybe just a standard IMAP:5 log would might show something? 

Are you connecting directly to gmail server or might there be proxies or maybe a VPN involved?

Comment 6

[Gianluca]

Good morning, no proxy in my case, direct connection

Comment 7

[Gianluca]

Good afternoon, it seems that disabling "Gmail buttons" add-on make the error disappear