This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

I can't access any of my email server accounts since 45.0 update

  • 3 antwoorde
  • 1 het hierdie probleem
  • 8 views
  • Laaste antwoord deur Matt

more options

There could be 2 things happening here as I also have migrated my internet connection for copper-wire DSL to a FTTP (Australian NBN) connection, via Optusnet, just before Thunderbird was updated to version 45.0 on my main desktop PC.

Optusnet have assured me that they have removed any outbound port 25 block, and this can be validated as on my netbook PC which is still running Thunderbird 38.6.0 has no problem with sending and receiving any messages to and from any of the various email accounts that belong to my domain: outimage.net.

However on my main desktop with Thunderbird 45.0 I cannot download any email, but I can still send messages out. When I click the get messages button, the status message at the bottom just displays "(account name): Connected to mail.outimage.net..." and doesn't change. As with email accounts on other servers owned by Optusnet, Gmail and Yahoo, all their messages download fine without any problem.

There could be 2 things happening here as I also have migrated my internet connection for copper-wire DSL to a FTTP (Australian NBN) connection, via Optusnet, just before Thunderbird was updated to version 45.0 on my main desktop PC. Optusnet have assured me that they have removed any outbound port 25 block, and this can be validated as on my netbook PC which is still running Thunderbird 38.6.0 has no problem with sending and receiving any messages to and from any of the various email accounts that belong to my domain: outimage.net. However on my main desktop with Thunderbird 45.0 I cannot download any email, but I can still send messages out. When I click the get messages button, the status message at the bottom just displays "(account name): Connected to mail.outimage.net..." and doesn't change. As with email accounts on other servers owned by Optusnet, Gmail and Yahoo, all their messages download fine without any problem.

All Replies (3)

more options

We see this a lot following update. It is usually an anti virus (Norton mostly) waiting for instructions from home before supporting the new version. Manual intervention in the firewall and email scanner is sometime required.

more options

Matt said

We see this a lot following update. It is usually an anti virus (Norton mostly) waiting for instructions from home before supporting the new version. Manual intervention in the firewall and email scanner is sometime required.

Thank you Matt. I'm not a fan of anything Norton and every trace of Symantec bloatware is removed from all my desktops and note/netbooks. For just an update after my original post, I returned to the server settings for one of the affected accounts and changed the "Connection security" from "SSL/TLS" to "None". After that, I was able to download from the server. The problem now seems to no longer exist. However by now having connection security disabled, I'm now wondering what are the risks I'm now open to and what it actually was that the "SSL/TLS" setting was blocking in Thunderbird 45.0 but not blocking in earlier versions.

more options

Thunderbird 45 and I think 38.7 and 38.8 have tightened the available ciphers for TLS. Tls is the replacement for SSL and while everyone still uses the term, the protocol is obsolete.

Re enable the SSL/TLS and open the error console (ctrl+shift J), clear it. Now try and get mail is there and error appearing about SSL having not cypher overlap. That would confirm that we are on the right track.