Closed Bug 1433934 Opened 8 years ago Closed 8 years ago

IMAP does not work since 2018/01/28

Categories

(Thunderbird :: Untriaged, defect)

52 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: thomas.buhl, Unassigned)

Details

(Whiteboard: [Support])

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20180103231032 Steps to reproduce: Since 2018/01/28 my IMAP accounts don't connect any more to the servers (different accounts, different servers, two different computers). Other web based eMail software gets the connections. Thunderbirds logs in when I do it with POP3. When I erase the password for the IMAP account, Thunderbird does not ask for it but reports a time out error. I use Thunderbird 52.6.0 on a PC with Windows 10 (64 bit). Actual results: Time out error Expected results: Well, it should send and receive the eMails with IMAP protocol as perfectly as ever ;-)
This looks like a support case. Please ask at https://support.mozilla.org/en-US/products/thunderbird. We don't know what happened on your machine on 28th Jan. Likely you updated to the new version 52.6. and now some "security" software on your machine is blocking the access of the program. I tried IMAP on 52.6 and it works for me. BTW, we have large tests suites and a testing team testing every single release automatically and manually so it's basically impossible that a version gets shipped, where a mayor component doesn't work. OK, we make small mistakes here and there, bit killing IMAP and shipping that is highly unlikely.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
Whiteboard: [Support]
Thanks for your fast response. Of course you are right. As no one else reports the problem it seems to be on my side. On one machine I use gDATA on the other one Avast, so it seems unlikely to me, that's a question of security software. Notwithstanding, I agree your conclusion that it's nothing for the bug report. Thank that your took your time to try it for me.
You need to log in before you can comment on or make changes to this bug.