Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Cannot conenct to SMTP server or autoconfig server without new profile.

  • Žane wotmołwy
  • 0 ma tutón problem
  • 15 napohladow
dalše nastajenja

On replpacing our SMTP server, we've found a strange problem.

Connecting to the SMTP server through TLS, the connection fails, if we add another account, it can't get the configuration data from autoconfig.domain.

Using wireshark it appears that it doesn't even attampt to resolve or connect to the autoconfig server (or connect throughj a proxy).

I can change the SMTP configuration to send insecurely (server can be accessed internally).

If I use a portable copy of thunderbird or start a new User Profile, both autoconfig and connecting to the server works, but all existing users profiles are broken in exactly the same way.

Does anyone know if there's a way to fix the profiles withough removing them and starting from scratch?

TIA for any help in resolving this.

On replpacing our SMTP server, we've found a strange problem. Connecting to the SMTP server through TLS, the connection fails, if we add another account, it can't get the configuration data from autoconfig.domain. Using wireshark it appears that it doesn't even attampt to resolve or connect to the autoconfig server (or connect throughj a proxy). I can change the SMTP configuration to send insecurely (server can be accessed internally). If I use a portable copy of thunderbird or start a new User Profile, both autoconfig and connecting to the server works, but all existing users profiles are broken in exactly the same way. Does anyone know if there's a way to fix the profiles withough removing them and starting from scratch? TIA for any help in resolving this.