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

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

After updating Thunderbird to version 150.0.2, I can no longer connect to my lolipop.jp mail servers.

  • Keine Antworten
  • 0 haben dieses Problem
  • Offen
aigarashi.hibinosekkei
aigarashi.hibinosekkei

After updating Thunderbird to version 150.0.2, I can no longer connect to my lolipop.jp mail servers.

Symptoms:

  • Both IMAP and SMTP stopped working at the same time
  • Webmail works normally
  • Multiple mail accounts are affected
  • Thunderbird times out when connecting to the servers
  • The issue started immediately after updating to Thunderbird 150.0.2

Settings tested:

  • IMAP: imap.lolipop.jp / Port 993 / SSL-TLS / Normal password
  • SMTP: smtp.lolipop.jp / Port 465 SSL-TLS and Port 587 STARTTLS
  • Tried Thunderbird Safe Mode
  • Tried reinstalling Thunderbird
  • Tried disabling Norton security/firewall temporarily
  • Same issue persists

Could this be a known issue with Thunderbird 150.0.2? If so, is there any workaround or planned fix?

Thank you.

After updating Thunderbird to version 150.0.2, I can no longer connect to my lolipop.jp mail servers. Symptoms: * Both IMAP and SMTP stopped working at the same time * Webmail works normally * Multiple mail accounts are affected * Thunderbird times out when connecting to the servers * The issue started immediately after updating to Thunderbird 150.0.2 Settings tested: * IMAP: imap.lolipop.jp / Port 993 / SSL-TLS / Normal password * SMTP: smtp.lolipop.jp / Port 465 SSL-TLS and Port 587 STARTTLS * Tried Thunderbird Safe Mode * Tried reinstalling Thunderbird * Tried disabling Norton security/firewall temporarily * Same issue persists Could this be a known issue with Thunderbird 150.0.2? If so, is there any workaround or planned fix? Thank you.

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.