[Outlook Target Principal Name issue]

Thank you for looking into this. I have contacted the e-mail provider.

[Outlook Target Principal Name issue]

On 7/31/2019 at 1:11 AM, itman said:

Whereas there is a way to export the self-signed cert. from their webmail site here: https://webmail.jpberlin.de/roundcube/ and import it into Eset's list of SSL/TLS known certificates, I don't know if it would work in regards to Eset's client e-mail scanning. Someone from Eset will to comment on this.

I am assuming the webmail certificate is the same one their client e-mail servers are using.

 

Thank you! The jpberlin.de SSL wildcard certificate is issued by Thawte/digicert. I have imported it into eset's known certificate list. The issue persists.

For the www.jpberlin.de Web page, Firefox 68.0.1 also warns that "connection verified by a certificate issuer that is not recognized by Mozilla". The ESET certicate was imported into the Firefox certificate list, though. For now, it's just a warning...

[Outlook Target Principal Name issue]

At least on my machine, it looks as if the certificate is indeed issued by "ESET SSL Filter CA". The underlying "ESET SSL Filter CA" certificate is issued by the same entity it is issued to.

It might be that Outlook 2019 has issues with the wildcard certificate. The links address SAN certificates but this is not the case here.

 

[Outlook Target Principal Name issue]

I use ESET Internet Security 12.2.23.0 on Windows 10 build 18362.239.
When I try to sync my IMAP folder in Outlook 2019 MSO 16.0.11727.2022 32-Bit
with its server at mail.jpberlin.de I receive the warning
"The target principal name is incorrect".
Seems that the self-signed certificate for *.jpberlin.de issued by "ESET SSL Filter CA" could be the issue.

What could I do in this case?