We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

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

Updated from TBird 31.5.0 to 31.6.0. Now get unable to connect. Have stopped/started TBird and even rebooted Win7. Any suggestions?

  • 2 பதிலளிப்புகள்
  • 6 இந்த பிரச்னைகள் உள்ளது
  • 2 views
  • Last reply by JoeatWC

On second PC, was operating with Tbird 31.5.0. Received notice that needed to upgrade. Ran automatic upgrade to 31.6.0. Immediately upon restart of TBird, I received the message Unable to Connect to live.mozellamessaging.com instead of normal Welcome message on lower half of window. If I try to do a "Get Messages", the message at the bottom shows "Connecting to pop.earthlink.net as is should but it just hangs there. I have restarted TBird and even rebooted the Win7 system to no avail. I looked at the TBird Account Settings and they appear OK. Any suggestions on where to start?

On second PC, was operating with Tbird 31.5.0. Received notice that needed to upgrade. Ran automatic upgrade to 31.6.0. Immediately upon restart of TBird, I received the message Unable to Connect to live.mozellamessaging.com instead of normal Welcome message on lower half of window. If I try to do a "Get Messages", the message at the bottom shows "Connecting to pop.earthlink.net as is should but it just hangs there. I have restarted TBird and even rebooted the Win7 system to no avail. I looked at the TBird Account Settings and they appear OK. Any suggestions on where to start?

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Thank you. I checked Norton AV and changed setting from Auto to Allow and that seemed to fix the problem.

Read this answer in context 👍 1

All Replies (2)

If you run a personal firewall make sure Thunderbird is allowed.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Thank you. I checked Norton AV and changed setting from Auto to Allow and that seemed to fix the problem.