Thunderbird: Free Your Inbox2d ago

"Houston, we have a solution."

#Thunderbird #ArtemisII

Show threadPortlandia

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

Apr 3 at 7:16pmWeb
Show threadAleca2d ago
@portlandia999 @thunderbird oh, I'm sorry you're experiencing issues.
Would you mind reporting the bug in bugzilla, or sending me a message directly?
Betterbird is a soft fork of Thunderbird, so the protocol code is exactly the same.
It might be that your problem was solved when setting up a new profile in Betterbird for different reasons, but I would love to investigate and solve your problem, so you can come back and not use a less secure version of Thunderbird :D
Show threadPortlandia2d ago

@alecaddd @thunderbird

Thanks for your reply :>)

After an update, TB started doing 6 or more handshakes to read 2 Outlook inboxes.

I updated again and it didn't fix it, so I tried BB which worked. BB uses the same TB profile so that is not the issue.

I would normally try TB updates until the issue is fixed, but with Mozilla putting AI into its products, I prefer to use alternative forks which don't (including Waterfox). If that changes I will consider switching back.

Thx

Show threadAleca2d ago

@portlandia999 @thunderbird I'm sure you know this already, but just in case, Thunderbird development is independent from the general Mozilla push for AI.
We're not adding any AI features in Thunderbird and we're not planning to do that.
Maybe add-ons in the future, but just for those users that want to experiment with it.

Anyway, I would love to help you fix your issues since we want to improve support for Outlook inboxes.

Let me know if you feel comfortable reporting a bug.
Cheers

Show threadPortlandia2d ago

@alecaddd @thunderbird

Ok, good to know.

I now have separate profiles for TB and BB because updating TB locks out BB. So based on what you've said, I will continue to update TB and the problem will hopefully be fixed at some point, so I will consider switching back since I've used TB a long time.

A lazy approach, but sorry, not much for doing bug reporting.

Thx

Show threadAleca2d ago

@portlandia999 @thunderbird I'll let our protocol developers know about your issue and we will try to investigate.

Please, let me know if anything changes.
Thanks for engaging with us!

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 Zijst11h ago
@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.