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

Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

Setting up mail.com account in TB

  • 2 réponses
  • 3 ont ce problème
  • 90 vues
  • Dernière réponse par 628dcox
  • Archivé

628dcox
628dcox

When I set up an account pointing to mail.com, TB finds the server setup without a problem. It fails to authenticate the log-in at the mail.com server. I've tried every setting using those provided by mail.com and searching the internet, IMAP and POP3. Nothing works. The initial authorization fails with every permutation of settings.

HELP please.

When I set up an account pointing to mail.com, TB finds the server setup without a problem. It fails to authenticate the log-in at the mail.com server. I've tried every setting using those provided by mail.com and searching the internet, IMAP and POP3. Nothing works. The initial authorization fails with every permutation of settings. HELP please.

Toutes les réponses (2)

sfhowes
sfhowes
  • Top 25 Contributor

Do you have a Premium subscription? It's required for IMAP, POP and SMTP access.

https://support.mail.com/premium/imap/thunderbird.html

628dcox
628dcox Auteur de la question

Thanks, but that solution doesn't work. I've also tried the one for POP3. Both return an authorization error. I'm just going to install the Mail.com app. I was trying to avoid that and use Thunderbird but it doesn't seem to be within my capabilities.

I was a software developer before retiring and am thoroughly familiar with setting up email accounts, I just can't get it to work in Thunderbird. It could be Mail.com's problem. But I can't run a debugger on either of these to see the exact line of code causing this outcome.