olgoat

Not sure if that was a typo or not but the instructions were to restart thunderbird AFTER the disable and re-enable of the ssl filtering. That is what I did and I am still ok this morning. One thing that doesn't make sense to me is that I have been running NOD32 for over a decade and IMAP on Gmail for almost that long and I have NEVER had this issue before.

I didn't realize you were all on a different product. I am using NOD32 FWIW and the fix above is still holding on my WIN10 laptop. My POP3 filtering is still toast and have not heard anything from eset yet on that ticket.

That seems to have resolved the imap issue for now. I will test it for a bit. I assume this would have no affect on the POP3 issue. I have a ticket in for the pop3 filter problem

Add 22402 to the list of updates.

I have problems with both POP3 and IMAP since last nights download of detection engine updates 22403 through 22405. The only solution I have found is to disable POP3 scanner setup and IMAP Scanner setup. Thunderbird 78.5.0 Windows 10.

This morning I was not able to retrieve email from a POP3 server or from GMAIL using IMAP using latest Thunderbird 78.5.0 on windows 10. I initially thought it was Thunderbird but was told to try disabling the POP3 Scanner setup, which got around the problem. The IMAP problem was very intermittent until I disabled the IMAP Scanner setup in NOD32. Then it worked without issue. Checked the root cert in ESET and it says OK. Last night the detection engine updates 22403-22405 were downloaded. I believe after that, I was not able to filter POP3 or IMAP anymore. I opened a ticket for POP3. I did not open one for IMAP yet.