The only thing I could find that worked was to exclude Thunderbird.exe from the Protocol Filtering. Then one account would receive again, and I could re-add my other Gmail account.
But this seems to leave me open to attack. I will look at turning off the IMAP/IMAPS scanning, as Marcos suggested and Tlapse said worked.
Still concerned about opening a security hole in my email client. Is that what I'm doing?
I'm on eset nod32 AV 5, T'Bird 24.3, and this all started right at the end of January.
I have submitted this problem through the eset support widget, including a full data dump.
Have at it, eset.
PS: "ESET doesn't support Thunderbird" per Marcos? What's that mean?
EDIT #1: I unchecked Thunderbird from the Protocol Filtering Exclusion list. I then turned on Protocol Filtering / SSL / Always scan SSL protocol (left two boxes on that panel checked by default). Then went back to Email client integration / IMAP, IMAPS / and left selected Use IMAPS protocol checking for selected ports. The 2 ports listed are 585 and 993. Note that 993 is the default outgoing IMAP server port for the auto-config by T'Bird of the GMail addresses.
When I first tested this, it took a while for a test email to land, so long that I was in the process of writing up the failure of this when T'Bird's notice of New Mail popped up. Subsequent tests find the email arrives almost instantly.
BUT: That first receipt of mail included several objections about unsigned certificates, although all of them had google.com addresses. Weirdly, one was for POP.google.com. Weird, since this is an IMAP-configured mailbox, and IMAPS-checking is what I'm enabling.
Thunderbird stopped working with gmail yesterday
in ESET NOD32 Antivirus
Posted · Edited by Kzoom
Had/have *exactly* the same problem, including the sudden stoppage of mail.
Posted about it over at Google, including my solution, at this link:
https://productforums.google.com/forum/#!msg/gmail/lw6OYhW3f5c/canumL0Mo_0J
The only thing I could find that worked was to exclude Thunderbird.exe from the Protocol Filtering. Then one account would receive again, and I could re-add my other Gmail account.
But this seems to leave me open to attack. I will look at turning off the IMAP/IMAPS scanning, as Marcos suggested and Tlapse said worked.
Still concerned about opening a security hole in my email client. Is that what I'm doing?
I'm on eset nod32 AV 5, T'Bird 24.3, and this all started right at the end of January.
I have submitted this problem through the eset support widget, including a full data dump.
Have at it, eset.
PS: "ESET doesn't support Thunderbird" per Marcos? What's that mean?
EDIT #1: I unchecked Thunderbird from the Protocol Filtering Exclusion list. I then turned on Protocol Filtering / SSL / Always scan SSL protocol (left two boxes on that panel checked by default). Then went back to Email client integration / IMAP, IMAPS / and left selected Use IMAPS protocol checking for selected ports. The 2 ports listed are 585 and 993. Note that 993 is the default outgoing IMAP server port for the auto-config by T'Bird of the GMail addresses.
When I first tested this, it took a while for a test email to land, so long that I was in the process of writing up the failure of this when T'Bird's notice of New Mail popped up. Subsequent tests find the email arrives almost instantly.
BUT: That first receipt of mail included several objections about unsigned certificates, although all of them had google.com addresses. Weirdly, one was for POP.google.com. Weird, since this is an IMAP-configured mailbox, and IMAPS-checking is what I'm enabling.
BTW, to eset, my posted case is #1135543.
Thanks all.