On Sun, 7 Mar 2021 20:51:14 +0000 Bev Nicolson lumos@gmx.co.uk allegedly wrote:
On 07/03/2021 20:30, mick wrote:
On Sun, 7 Mar 2021 17:54:58 +0000 Bev Nicolson lumos@gmx.co.uk allegedly wrote:
But, as I have two other emails connected to Thunderbird (this one I'm using now and another gmx address) and they are fine, how do I track the problem down? It must be something specific to the isp related addresses. (Folders compacted, cache reduced, emails moved, etc, btw.)
One more quick thought before I suggest trying anything else. If you do not have a fixed IP address from idnet, please try re-booting your router to get a new one.
Done that. Still slow.
(Though having moved some emails from another gmx account, once it's connected, it's bit quicker. Go figure. Though you'll probably guess what's up!)
Bev
I've taken a look at the idnet site and it seems that they give out fixed IPV4 addresses and a /48 for IPV6 - so rebooting your router won't have changed the address.
One question I don't think we have addressed is whether the problem only occurs on this one specific email address at idnet (you say you use Tbird for others such as gmx). To eliminate that possibility, is it possible for you to set up a completely new address with your ISP and test connectivity to that? If that works fine, there may be some corruption to the existng account which is causing the problem. You mentioned earlier that you saw a STATUS error on a non-existent mailbox. Whilst I don't /think/ that is actually material to this problem it may be indicative of an account corruption.
If after that test you still get the same symptoms of slow connection using any of Tbird, claws, evolution and a CLI connect with openssl FROM your network, but no problem from outside your network (you say the phone connection was fine), my last (and only remaining suggestion (beyond using wireshark) is that you test the idnet server using a remote service on the 'net. There are several about, and I use them fairly often when I want to check my own server configurations (for example to check TLS certificates). If an external test shows no problem then the problem must lie somewhere in your network or it's route to the idnet server and you can then go in to bat with idnet support for help.
So - try https://pingability.com/mailtest.jsp BUT NOTE that you must give them your email address and password. For obvious reasons I suggest strongly that you only do that only for your new test address, not the address you are actually concerned about.
Try also https://www.wormly.com/test-smtp-server they have both SMTP and POP3 tests (but no IMAP that I can see)
and you can test the TLS certificates at https://ssl-tools.net/mailservers. This will enable you to check both valid responses from the server and the possibility that a TLS problem could be the cause of the fault. (Some email clients will barf at a dodgy TLS cert).
Also see https://www.immuniweb.com/ssl/ who give a comprehensive suite of TLS tests.
After that, I'm out of ideas. But my money is on either a corruption in your idnet account, or some weird comms problem between you and the idnet IMAP server.
Mick
--------------------------------------------------------------------- Mick Morgan gpg fingerprint: FC23 3338 F664 5E66 876B 72C0 0A1F E60B 5BAD D312 https://baldric.net/about-trivia ---------------------------------------------------------------------