Security Message

[BenFenner]

the client has a certificate problem

How do you figure that?

[Moonchild]

The bad news is the problem still exists, exactly as with Norton.

Avast using the same kind of TLS interception (no surprise there) means you will have the same kind of problem. This is NOT a client problem. You can work around it by installing intermediate certificates in Epyrus but it will not solve the fundamental issue of breaking your TLS trust chain. It's inherent to the kind of "must inspect your encrypted data" setup they use.

Also, both Avast and Norton fall under the same corporate umbrella. See viewtopic.php?f=65&t=31970

[Bilbo47]

antipathy toward Norton ... Norton alone wasn't the culprit.

Agree. Just bc one of those system-mangling packages sucks doesn't mean the others don't.

[moonbat]

Off-topic:
There is no need for any separate anti-virus on Windows when there's MSE, provided you don't do dumb things like opening unknown attachments, downloading software from anywhere other than its official website or inserting USB drives of unknown origin while having autoplay enabled. The days of drive-by malware that can hijack your system with zero user intervention are long gone (they were an IE6 phenomenon), and social engineering is the primary way people get hacked these days. There's no antivirus substitute for common sense though, and it clearly isn't very common going by how often people continue to fall for phishing scams. Antivirus software with their constant subscriptions are just a tax for being dumb online.

[JoeyG]

Ummm, my wife also uses Norton, but she uses Thunderbird. She doesn't have the problem.

My guess is that no one who doesn't use Epyrus has the problem.

Maybe my logic is overly simplistic, but since - as indicated by the input here in the forum - the issue seems to be restricted to Epyrus, l've drawn my conclusion.

[Moonchild]

Ummm, my wife also uses Norton, but she uses Thunderbird. She doesn't have the problem.

You're forgetting that antivirus packages when installing likely have certificate installation routines for the most commonly used mail clients. Your wife likely has her email connections hijacked by the antivirus without even knowing.

[JoeyG]

Although l still have 443 days on my Norton subscription and a year on a one-year Avast sub l recently bought on ebay, l gave up and bought 18 mo.
of Bitdefender. It's a waste of money, but the aggravation finally got to me.

[Bilbo47]

Closer to the original post in the thread: The other time I get cert dialogs that look like this is when the IMAP server legit updates its cert every x-months, *and* EP was connecting to it using a DNS name that's not listed in the cert. In other words, the cert contains the server's real name, but DNS entries may contain a different name.

So when connecting to the server by its real name, the cert validates without this dialog.
But when connecting to the server by its name listed in DNS, the cert is considered not-valid, so the dialog appears.
Not sure what happens when connect to the server by its IP address.

It this the right way of understanding it, or is there anything I'm missing?