Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More
Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.
Archivado

Thunderbird failed to find the settings for your email account.

GerardoPcp04 replied
Rodrigo

Hi everyone,

I'm trying to set up a Titan-hosted email address on Thunderbird, but I keep running into an error.

After entering the email and password, Thunderbird tries to auto-detect settings and inserts an invalid incoming server hostname starting with a dot (e.g., .exampledomain.com). When I try to manually correct it (replacing with imap.titan.email, port 993, SSL/TLS), I get the following error:

   Error Creating Account: Incoming server already exists.

Here's what I've already tried:

   Deleting all previously failed or partial accounts in Thunderbird's UI

Downgrading to previous versions of Thunderbird

   Manually editing the prefs.js file to remove any reference to the invalid hostname
   Restarting Thunderbird after each change


Despite that, Thunderbird still reverts or blocks the setup with that error.

Titan’s official configuration is:

   IMAP: imap.titan.email, port 993, SSL/TLS
   SMTP: smtp.titan.email, port 465, SSL/TLS

Is there a clean way to fully reset Thunderbird's internal server registry or prevent the autoconfig from interfering?

Appreciate any guidance!

Thanks.

Hi everyone, I'm trying to set up a Titan-hosted email address on Thunderbird, but I keep running into an error. After entering the email and password, Thunderbird tries to auto-detect settings and inserts an invalid incoming server hostname starting with a dot (e.g., .exampledomain.com). When I try to manually correct it (replacing with imap.titan.email, port 993, SSL/TLS), I get the following error: Error Creating Account: Incoming server already exists. Here's what I've already tried: Deleting all previously failed or partial accounts in Thunderbird's UI Downgrading to previous versions of Thunderbird Manually editing the prefs.js file to remove any reference to the invalid hostname Restarting Thunderbird after each change Despite that, Thunderbird still reverts or blocks the setup with that error. Titan’s official configuration is: IMAP: imap.titan.email, port 993, SSL/TLS SMTP: smtp.titan.email, port 465, SSL/TLS Is there a clean way to fully reset Thunderbird's internal server registry or prevent the autoconfig from interfering? Appreciate any guidance! Thanks.

Todas las respuestas (1)

Hola, Esta indicando como que hay una configuración previa, el archivo prefs.js es la configuración del usuario y esta dentro de la carpeta de perfil del Thunderbird, si no tiene otras cuentas o datos puede crear in perfil nuevo. Saludos