When the upgrade from v91 to v102 came for my Windows 10 desktop, I said, "Go ahead!" After restarting the client, Tbird would go to check new messages and would just ke… (читать ещё)
When the upgrade from v91 to v102 came for my Windows 10 desktop, I said, "Go ahead!" After restarting the client, Tbird would go to check new messages and would just keep spinning in its progress area without downloading new messages - which I knew were there. Eventually I had to downgrade back to v91, which thankfully worked well.
I have a Ubuntu 20.04LTS desktop that my partner uses. It was going along fine with v91 but v102 came last night and I didn't notice in the list of packages to be upgraded until it was too late. Now they have the same problem! I haven't downgraded yet since the process will be a little more involved in Ubuntu and I would like to solve the underlying problem so I can keep upgrading to newer versions without worry in the future.
There is a wrinkle to my problems in that both setups are a little unconventional. My mail host eschews passwords in favor of SSH keys. What I've had to setup - and it's been working for about 15 years or more - is an SSH tunnel via an xinetd service. On my Windows box I use Cygwin and for Ubuntu I just use regular old bash and the services directly. When I encounter this new problem upon loading Tbird, I can telnet to my custom port on localhost and see that the connection is being made to the remote IMAP server. I can even list things with a little manual interaction. I really have no idea why it is not working.
I have a wireshark recording from when my Windows installation stopped working, but I would be hesitant to share too many personal details on a public forum.
My mail host/server is using Ubuntu's uw-imapd version 8:2007e~dfsg-3.2ubuntu1 (from Ubuntu
22.04.1).