Can't find settings on new account setup
I have 6 active, working accounts on my Thunderbird. I am trying to set up a new account. I entered all the required information for a manual setup. Everything is the same for my other accounts, except username and password. After clicking "retest" I get a yellow error message saying "can't find account settings." I've tried all combinations of security and password, etc, but nothing works.
The email is valid, and the password is correct. Using Filezilla, I can go into the account and see new emails coming through. I use the manual setup because I want the incoming setting to be pop3, not imap.
Thunderbird offers nothing in terms of trouble shooting, so I do not have any idea of where this problem lies. Can someone please give me a clue what the problem might be?
Все ответы (2)
Other users have discussed problems with security.tis. I do not know anything about this. how would I determine if this is the problem? Where do I find this? Is it within TB, or is it a parameter on the server? One user suggested that these values solved his problem.
security.tls.version.min = 1 security.tls.version.enable-deprecated = true
how/where do I find this to make a change?
TB has been working just fine for me for many years (maybe that's the problem, it is just too old to keep working). My version number is 115.9.0 (64-bit) which is very different from other version I see on this forum. It says that it is the latest version.
Seriously, the very first thing you choose in the new account wizard is the choice of IMAP Vs POP if Thunderbird finds both settings, for example looking in the database here https://autoconfig.thunderbird.net/v1.1/. Or using its probes.
Diagnostics have to be enabled, failure that requires them should not be normal in the first place. https://wiki.mozilla.org/MailNews:Logging
Otherwise if it does not find anything it drops you into the manual settings with the yellow banner that it can not find the settings for your email account.
So perhaps we can back up a little here, because I simple don't think you should need to be "fixing" encryption protocols on a production server. Anything using a version of TLS like one is in the realms of Luddites. TLS version one was replaced with a newer version in 2008. Just like not fiddling with unsupported SSL which in reality was obsolete in the last century. https://en.wikipedia.org/wiki/Transport_Layer_Security
These sorts of low level security issues can be observed to be the issue in the error console (ctrl+shift+J). No one should just change them in the config editor and see what happens.
I would suggest you try offering details of the domain these accounts function under. Especially so if it is self hosted for through a hosting service as they have all sorts of special requirements depending on the service. Perhaps the results of attempts without antivirus products interfering.