latest thunderbird update not functional with my configuration

Bug #1992291 reported by Steven Hirsch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mozilla Thunderbird
Expired
Unknown
thunderbird (Ubuntu)
New
Undecided
Unassigned

Bug Description

After many troublefree years, I'm sorry to report that the latest Thunderbird update for Bionic really hosed me. My existing local IMAP configuration was not migrated and when I try to set it up manually it cannot deal with the fact that incoming mail originates in my IMAP, while outgoing passes directly to gmail SMTP. No way to specify two different accounts apparently and after about an hour I ripped it out and tried to revert. Unfortunately its predecessor version is not available and I had to go back to version 60.0 to regain functionality.

Very disappointing and I hope this will be addressed. The prior version is available on in source form and I'm not looking forward to building such a complex app.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, could you give details on which version you installed exactly which didn't work as expected?

Revision history for this message
Steven Hirsch (snhirsch) wrote :

Ah - sorry. The newer package is 1:102.2.2+build1-0ubuntu0.18.04.1. As I noted above, it did not migrate my primary e-mail setup at all and I was unable to manually configure it. There was an option for exactly one password, yet my local IMAP and Gmail's SMTP use different auth methods and passwords! The bigger and more immediate question is why in $deity's name is the previous version no longer available as a recovery option? I was able to downgrade back to the base version 60.0, but lost compatibility with add-ons. Pulling the immediate predecessor package is less than the most optimal way to manage the repository. I looked for a solid hour yesterday and still could not find a DEB for 1:91.11.0+build2-0ubuntu0.18.04.1 (most recent working level).

Revision history for this message
Steven Hirsch (snhirsch) wrote :

Can you PLEASE, PLEASE make the previous build available for download? This is really a major issue here, even if I'm the only person on earth seeing it.

Revision history for this message
Steven Hirsch (snhirsch) wrote :

Finally, success in locating the previous version (why is this so difficult?).

For anyone else who's been hit by this breakage, here's where to find a working version of Thunderbird:

https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/24124419

After reverting back to this level everything "just works" again. I'll have to figure out how to lock out updates.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Sorry to read that the update didn't go well for you Steven.
Could you please file an upstream bug at https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird and share the link here?

Revision history for this message
In , Steven Hirsch (snhirsch) wrote :

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.

Revision history for this message
Steven Hirsch (snhirsch) wrote :
Changed in thunderbird:
status: Unknown → New
Revision history for this message
In , Mkmelin+mozilla (mkmelin+mozilla) wrote :

What is IMAP local?

Revision history for this message
In , Steven Hirsch (snhirsch) wrote :

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

Revision history for this message
In , Mkmelin+mozilla (mkmelin+mozilla) wrote :

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

Revision history for this message
In , Ebertran (ebertran) wrote :

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.

Revision history for this message
In , Mkmelin+mozilla (mkmelin+mozilla) wrote :

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

Revision history for this message
In , Steven Hirsch (snhirsch) wrote :

(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.

Revision history for this message
In , Vseerror (vseerror) wrote :

Please comment if you have additional information.

Note - Updates generally don't involve migration.

Revision history for this message
In , Steven Hirsch (snhirsch) wrote :

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.

Changed in thunderbird:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.