[Protocol filtering stops access to emails]

14 hours ago, Marcos said:

SSL inspection requires a root certificate to be imported into the trusted root CA certificate store in order for the browser or email client to trust the communication. If the correct root certificate is not present for whatever reason, the browser or email client will report an error. That's not unique for ESET, it's typical for any AV or software that performs SSL inspection.  You can keep SSL filtering disabled if you don't mind the risk of SSL communication not being scanned for threats.

You miss my point. I fixed my issue by turning filtering off. And then immediately turning it on again. That's a bug.

[Protocol filtering stops access to emails]

Today my Win 10/Thunderbird 78.5.0 stopped working, specifically unable to log on to my ISP or Google because the User Name wasn't being transmitted on logon. Works fine restarting in Safe Mode but that's a diagnostic rather than a work around. Eventually after 1/2 day pottering around forums I switched off SSL filtering and then switched it back on. All is now well.

My question is why should I have to? ESET is a fine AV but most of your customers aren't either interested or competent to mess around with SSL filtering. It's a bug. Say so and fix it.

[Thunderbird email fetching issue]

I have a similar but different problem. Specifically ESET is blocking my ISP logon, hence my email Client (Thunderbird) never gets to download. I've bypassed ESET by starting in Safe mode but that's too much of a hassle. How to I lighten whatever is stopping the transmission of my User I/d?