I've just tried to send some more emails with ssl filtering enabled and it again doesn't work. The emails are sent (I receive them on my android devices), but not saved in TB in the sent folder and I can't receive them using TB.
To add to what @Marcoshas previously posted, I have encountered past incidences in Thunderbird where multiple Eset certificates existed in Thunderbird's Authorities certificate store. What I advise if this situation exists is the following.
First open Eset GUI and navigate to SSL/TLS settings. Under the Root Certificate section, select View certificate. Note particulars about the Eset certificate such as Valid From Date, etc.. Next, return to Thunderbird's Authorities certificate store and delete all Eset certificates other than the current Eset certificate noted previously.
Thank you itman. I'm not a very experienced user and I'm using a German version of the program, so I hope I've understood your instructions correctly. In Eset I see only one root certificate, valid starting 30 November 2020. In Thunderbird's Authorities certificate store I can also see only one certificate, which is valid until 6 June 2028, but with a start date of 9 June 2018. This would be the only one I can see to delete, and I'm not sure what would happen then, so I'm afraid to try it.
2. It is possible that Thunderbird is now deferring to the Windows root CA certificate store even though the corresponding use of enterprise root certificates option is not enabled as is the case currently in FireFox.
Many thanks for your precise instructions! I have followed them on both of my desktop computers and now everything works fine. The current eset certficate is also now visible in the Thunderbird Authorites certificate store. :)
First on select Eset installations, a new Eset root certificate was created as a result of this new network protection module update. Why this happened only on some devices, Eset needs to investigate. What I did observe on the day of the network module update was that an Eset module update was attempted on my device upon first system startup that day. This was odd to me since I have never observed an Eset module update running at boot time. At this time I checked my Eset Event log, but no recent module update was recorded there. Err ....... what? What I theorize is the network module was updated but the rest of the updating crapped out. Hence, no Thunderbird Eset root certificate update for lucky me!
Eset stores on each device a private key that is used by Eset root certificate. When Thunderbird tried to use the non-current Eset root certificate in its Authorities store, the private key needed was no longer available but it instead tried to use the private key associated with the Eset certificate that was recently updated and currently resident in the Window root CA certificate store.
If Eset can't access Thunderbird because its currently in use, it suspends the update processing. It then generates an Eset alert instructing the user to terminate Thunderbird processing so the certificate update can proceed. Once Thunderbird is shutdown, then Eset resumes the certificate update processing. Once update processing completes, Eset generates another alert indicating it's OK to re-open Thunderbird.
I was able to solve it by deleting the password of the problematic imap email account stored in the Thunderbird Password Manager. My guess is that some files used by the password manager are corrupted.
Before you try to disable SSL etc. in Eset Security try to reset the password of the email account first, it is stored in the Password Manager of Thunderbird under Options > Privacy and Security > Saved Passwords.
They did solve the problem, but it took several hours (that I'll never get back) of troubleshooting before I could point to NOD32 as the cause of the problem. I'm really disappointed that ESET made this change and pushed it out without testing.
A couple of weeks ago, NOD32 claimed an email message had the "HTML/Fraud.EK trojan." The message was plain text--no HTML content whatsoever! I reported it as a false positive, but ESET hasn't bothered to acknowledge this.
We didn't make any change that would have caused this issue. Please read my explanation with preliminary findings at -problems-with-thunderbird-and-imaps/?tab=comments#comment-125459. Investigation is ongoing.
Morning all, Apologies first off, I am not techy and so I'm not understanding all the posts ref NOD32 etc, but currently the only way I can receive my work related GMails is by switching off Protocol Filtering and SSL. As you can see from the screenshot, it is still switched off now. As soon as I enable it again, I stop receiving my emails.
Hi Marcos - Thank you for replying. Yes, I've tried this a couple of times, including shutting down completely and then enabling the setting just after the re-start and before Thundirbird is open. I send a test email and while it is enabled, it doesn't come through and as soon as I have disabled Protocol Filtering, its comes through.
Since 2-3 weeks I'm getting these annoying notifications telling me that my license ends in X days. The orange warn sign, the notification pop-up in the task bar, the ERROR notification window on EVERY single PC start?! Really ESET?
It has been suggested before that there should be a "do not remind me again" button or something like that. But then ESET cannot be blamed if the users uses that option and then forgets to renew (because he did not see the warning anymore) and wonders why the product hasn't been updated for over a month. But I fully understand that some users do find it annoying.
if eset implements that option and you click "don't remind" after the expiration you could get infected and then you and everyone else will blame eset for not protecting your pc's.
so, renew the license or remove it and install another free product.
You think thats bad. I like Eset software. its unobtrusive, powerful and doesnt install tons of i never asked for and cant get rid of (rhymes with Sh*t agender) so i renewed my licence (Nod32 Antivirus) yet i'm still getting tthis fecking annoying notice. So i'm you're screwed if you do and screwed if you dont....
If you have renewed your license and entered the new username and password into the eset product you should not see the license warning. Open the main eset window, press ctrl+u and enter the new license username and password. You need admin rights, otherwise the new info would not apply. You can also check if the details changed in advanced settings window. On main screen press F5, navigate to update. Restarting the pc could help too.
Uninstalling ESET just because of such a small notification? Just renewing is the best solution for your problem. And as you can do this (usually*) also some time before the license "times out" (without loosing the remaining days of course), you may be able to renew it some days before it expires so you won't see this notification at all (or at least only one time).
When it's time for me to renew I only see the "x amount of days left" notification at boot ONE time, nothing after that. Not sure why you see it that often. And I can agree that the notification is displayed too often in your case, it would be interesting to find out why the interval differs so much though.
This exact issue is making me consider choosing something other than ESET. It is ridiculous to get a F-ing pop up in the middle of your screen periodically and warnings every startup. I know I didnt renew it yet, and I might just not renew it at all then.
This issue has just started on my machine. Every start up, I get a message saying I have 5 days left to renew. Every time it's 5 days. I have a valid subscription for 18 months because I just renewed it, and the problem appeared when I renewed.
We already ordered reneval of the licenses but we do not receive the new ones until we pay them and the payment date is stated on the day of expiry, so we will now rather pay before that, just to get rid of these notifications.
However they have seem to include now a new option to disable this notifications under Advances Options / User Interface / [ ]Show license messages and notifications. So for the next time I will just push policy to disable this messages.
7fc3f7cf58