Thunderbird: Free Your Inbox2d ago

"Houston, we have a solution."

#Thunderbird #ArtemisII

Show threadPortlandia2d ago

@thunderbird

More like replacing one problem with another. My #thunderbird was taking 10 seconds to handshake and read my outlook mail. I switched to #betterbird and that problem disappeared.

If you look at all the outstanding bug requests on #tbird, you'll see why #Mozilla products are no longer the browser/email client of choice.

Show threadHans van Zijst1d ago
@Portlandia
you'll see why #Mozilla products are no longer the browser/email client of choice

Speak for yourself 😉

A show handshake can be caused by sooo many different things, and without having even a hint of what's causing it, you can't simply blame it on TB.

Start by watching what's happening on the network: big change that TB is waiting for packets from the server.
Social.woefdram.nl

Show threadPortlandia1d ago

@hans

I may not have noted in my original post, but I have tried both TB and BB many times over several weeks including TB updates and in all instances TB did not work and BB did.

So I think it's a fair assumption that the problem is with TB. They must have made a change in their fork that BB did not.

And as I said, if I keep trying TB updates it will probably be fixed at some point and I can continue using TB then.

Show threadHans van Zijst
@Portlandia
So I think it's a fair assumption that the problem is with TB.

Not sure if I agree with that. "Assumption is the brother of all fuckups", to use a quote from "Lock, stock and 2 smoking barrels".

Again, check what's happening on the network. I have enough experience with Microsoft and their dealing with competing software to suspect that they could have implemented something in Exchange to make things to bad when the client turns out to be Thunderbird. Would be a step they have taken countless times in the past 3 decades...

Check for example how they have introduced a slightly different and thereby incompatible "LOGIN" mechanism in SASL and forced out every mail client that only used the agreed-upon version.

Again, assumption is dangerous, you first need to know in which part of the entire chain the problem is.
Apr 5 at 4:04pmWeb