Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά κατάχρησης».

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 έχουν αυτό το πρόβλημα
  • 7 προβολές
  • Τελευταία απάντηση από JoeatWC

more options

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.

Ανάγνωση απάντησης σε πλαίσιο 👍 1

Όλες οι απαντήσεις (2)

more options

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

more options

Επιλεγμένη λύση

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