I was bitten by that too (port 119).
Thunderbird seemed to suggest that it was time
to change my password. But I don't remember
reading any rule about needing to change that
at a particular interval.
And I also wondered whether the underlying
problem was that my password had been hacked,
and someone had changed it already.
So I spent a lot of time trying to find out
whether my password was working or not. I could
log on to the website, but maybe the hacker had
changed it for the news reader, but not the
website.
When I was running Linux I would have used telnet
to check, but now I was using Windows 10 and I
don't have a telnet command. I do have ssh though,
and I wondered if ssh fell back to telnet. I did
a brief search but it wasn't conclusive, and a
test of ssh was inconclusive too.
Then I remembered that I had my own NNTP program
(pdpnntp) which I could run under PDOS/386, so I
tried that.
That was inconclusive because the command was so
long and it looked like it was timing out. It's
a very crude program - it's not designed to cope
with failure. It's more just proof of concept.
But I did get it to the point where it appeared
to be failing a password check. And then I put
the command into a batch file so that timeouts
weren't an issue, and by the time I had done
all that it had started working again.
Is it too much to ask that in 2024, with pretty
much everyone already moved to 64-bit, because
apparently 4 GiB of memory isn't enough in the
modern world, that Thunderbird or the underlying
infrastructure can report "system down - nothing
you can do but wait" instead of suggesting that
the user is doing something wrong (or not knowing
which party is at fault)?
Or - maybe it's the other way around. Maybe it's
the 64-bit and above 4 GiB memory and the year
2024 that we've already reached Idiocracy (see
the movie) and what we actually need is a return
to a simpler time - UUCP, 640k memory, 4.77 MHz,
and understandable and debuggable code.
I'm working on it ...
BFN. Paul.