Closed Bug 1684506 Opened 4 years ago Closed 4 years ago

portableapps thunderbird yahoo settings restart has CLIENTBUG select

Categories

(Thunderbird :: Untriaged, defect)

defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: mhuttemail-forum, Unassigned)

Details

(Whiteboard: [support])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

Using portableapps thunderbird portable allowed update and it stopped connecting correctly to yahoo.
It started to show the CLIENTBUG select message.
This was probably 3 months ago. So probably 78.3? Still an issue in 78.6.0

I have tried quite a few changes. Including deleting and regen account in thunderbird. Which sets it up as Oauth2.
I was successfully using an app password before this.
Both the Oauth & app password work initially then on next start it fails.

=========================== Settings are:
Incoming Mail (IMAP) Server
Server - imap.mail.yahoo.com
Port - 993
Requires SSL - Yes
Outgoing Mail (SMTP) Server
Server - smtp.mail.yahoo.com
Port - 465 or 587
Requires SSL - Yes
Requires authentication - Yes

Options > Privacy & Security >
Select checkbox 'Accept cookies from sites'

Account Settings > Edit SMTP server
Set outgoing server (SMTP) 'Authentication Method' to 'Oauth2'

Account Settings > Server Settings
Set incoming server 'Authentication Method' to 'Oauth2'

NOTE: Oauth2 is Normal Password for "App Password".
==== Also tried the below:
Options > Advanced > Config Editor >
toggle general.useragent.compatMode.firefox true

Actual results:

Deleteing passwords and restart works for only the first time.
On next start it comes up with the CLIENTBUG select message.

Expected results:

Able to see all the mail folders and get new mail.

For support, please see https://support.mozilla.org/products/thunderbird (or perhaps there's some special one for portable version too). Do try if it's a problem with the normal version.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
Whiteboard: [support]
You need to log in before you can comment on or make changes to this bug.