Closed Bug 1795922 Opened 2 years ago Closed 2 years ago

102 update fails to show my imap account - shows with 91

Categories

(Thunderbird :: General, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: snhirsch, Unassigned)

Details

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

Steps to reproduce:

Upgraded from 91.11 to 102.2.2 using Ubuntu 18.04 main repository.

Actual results:

My primary e-mail account was not migrated. It uses a local IMAP with very basic authentication for incoming mail and Gmail SMTP w/ Oauth2 for outgoing. Different account names and passwords for the two. The name 'IMAP Local' did not even appear as a choice and when I tried to setup manually I was unsuccessful. There appeared to be no option for specifying local IMAP and remote SMTP using distinct accounts and passwords.

Expected results:

It should have simply showed "IMAP Local" as an account and allowed me to receive and send e-mail. After a lot of hair-pulling I found the previous version buried in one of Ubuntu's repositories. Manually downgrading brought everything back to proper function immediately.

What is IMAP local?

Summary: Latest update failed to properly migrate configuration → 102 update fails to show my imap account - shows with 91

It is my main mail account as described above. Local IMAP server on my home network for incoming and Gmail SMTP for outgoing.

Try Help | Troubleshoot mode.
Also note if there are any errors in the Error Console (Ctrl+Shift+J)

When I try to retrieve messages to Thunderbird, I receive a message:

"Login to server 'outlook.office365.com' failed with username...."

This has been going on for 5 days (October 19), which is when I received the last messages on THUNDERBIRD. Before it worked perfectly. I have not made any changes to the server or password.
It seems as if there is suddenly an incompatibility with the OUTLOOK server.

Enric: unlikely to be the same issue. Microsoft is rolling out forced use of OAuth2. Change to that in Account Settings | Server Settings | Authentication Method

(In reply to Magnus Melin [:mkmelin] from comment #3)

Try Help | Troubleshoot mode.
Also note if there are any errors in the Error Console (Ctrl+Shift+J)

I'll screw up my courage and give it another try.

Please comment if you have additional information.

Note - Updates generally don't involve migration.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Component: Migration → General
Resolution: --- → INCOMPLETE

Sorry to have dropped the ball on this. Since no one else has seen the issue I'll just keep the current (working) revision locked against updates and move on. Something is definitely broken, but if I'm the only user affected it's not worth valuable time.

You need to log in before you can comment on or make changes to this bug.