1198581 - after upgrading to Thunderbird 38.2.0 I couldn't receive email on two of my 5 pop accounts

Status: RESOLVED INCOMPLETE

(Thunderbird :: Untriaged, defect)

Description

[akgrizz]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150812163655

Steps to reproduce:

I upgraded from 37.1 like Thunderbird asked me too


Actual results:

I have 5 email accounts on 3 different servers. the accounts for alaskais.com (TWO)
on  ultra.fastservercore.com  995  465 (pop3) would not receive email but I could send I have one more account on the same server grizzlyinternetservices.net and it worked along with my other accounts on different servers all are POP3 accounts SSL/TLS I called my support at my hosting company and they looked at there server logs and said there was nothing wrong with there end but they had been contacted by other Thunderbird customers and they were double checking everything. So I deleted the two accounts that wouldn't receive email and set them up again manually still wouldn't receive so I downloaded version 37.1 and installed and everything has worked fine since. I didn't do any changes after I installed 37.1 my OS is Windows 7 Pro 64bit
I didn't get any errors the only thing I noticed was it would say in the stats bar that it was connecting to ultra.fastservercore.com would last for about 30 sec. then nothing would say no email although there was 30 emails in my webmail that I hadn't read.


Expected results:

I should have been able to receive my email on my two accounts and I did do a install of 38.2 again and it didn't work before I installed 37.1

Comment 1

[Wayne Mery (:wsmwk)]

Anything in Tools | Error console?

Comment 2

[akgrizz]

nothing in tools or error console. updated to 40.beta this morning on my laptop and and every thing seems fine (windows 10 64 bit OS)

Comment 3

[Wayne Mery (:wsmwk)]

Odd. Thanks for the update

Comment 4

[akgrizz]

I updated my main computer to 40.Beta the computer I was having trouble windows 7 pro 64bit it would not receive email on the same two accounts in the error log it said the server cert were to weak sh1 or something like that. so I did what I saw in forum 
Preferences -> Advanced -> General -> Configuration Editor ...

Promise you will be careful! ...

Look for ssl3 at the search bar....

security.ssl3.dhe_rsa_aes_128_sha must be switched from true to false security.ssl3.dhe_rsa_aes_256_sha must be switched from true to false

did that and now works fine funny the other two email accounts on the same server worked all the time.

Comment 5

[akgrizz]

laptop that worked before with Thunderbird version 40 beta this morning doesn't work won't receive email again here is error report I will send this on to the server folks also. I will make changes in the Configuration Editor like I did in the last comment I made the changes above and it received all( emails fine (one more thing that's not working in this beta the X in top right hand corner doesn't change color on mouse over and will not shut down Thunderbird)

Timestamp: 8/26/2015 7:20:45 PM
Error: An error occurred during a connection to ultra.fastservercore.com:995.

SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.

(Error code: ssl_error_weak_server_ephemeral_dh_key)

Timestamp: 8/26/2015 7:20:49 PM
Error: An error occurred during a connection to ultra.fastservercore.com:995.

SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.

(Error code: ssl_error_weak_server_ephemeral_dh_key)

Timestamp: 8/26/2015 7:20:52 PM
Error: An error occurred during a connection to ultra.fastservercore.com:995.

SSL received a weak ephemeral Diffie-Hellman key in Server Key Exchange handshake message.

(Error code: ssl_error_weak_server_ephemeral_dh_key)

Comment 6

[akgrizz]

server folks are working on it server cert was not complete here's a link
https://www.sslshopper.com/ssl-checker.html#hostname=ultra.fastservercore.com
I had to go back to 37.01 beta and set both to true 40 beta was to buggy

Comment 7

[akgrizz]

server folks thought they had it fixed but they don't I'm running 38.2 with the work around

Comment 8

[akgrizz]

Outlook 2010 doesn't have this problem works fine.

Comment 9

[Wayne Mery (:wsmwk)]

akgrizz, do you still see this issue in a current version?

Comment 10

[Phoenix]

Resolved per whiteboard