Outlook 2016 For Mac Certificate Error

Outlook 2016 For Mac Certificate Error 5,6/10 7041 votes
Outlook 2016 for mac certificate error free

Aug 22, 2018 - Creating and renewing S/MIME certificates; Sending digitally signed messages. The S/MIME certificates become invalid and the messages display this error. In Outlook 2016 for Mac, a signed email message reports, 'The.

You should configure Autodiscover for your domain because Outlook and other clients insist on it, and ultimately it will improve the user experience when configuring new accounts. This certificate error is probably coming from your web server, which isn't set up properly for SSL communication and does not have a CA signed and trusted certificate. This article describes how to setup autodiscover in your DNS In the 'Details' section of the article, the third bullet is most likely the requirement you need to satisfy. Either get a signed certificate for your website or disable SSL on your web server if it's not necessary. The issue is that the autodiscover client (Outlook) tries to connect to your web server so that it can realize that it's actually not a valid autodiscovery server. Without a valid certificate, it can't get past the SSL connection phase to determine that it's not a viable server.

So in other words, it needs to be able to succeed so that it can fail. Eventually it will use SRV DNS lookup to determine the correct address of your Kerio Connect server. Unfortunately autodiscovery is setup to perform the SRV method last, after all other autodiscover methods have failed. Hi Brian, Sorry for the late response. We have a signed certificate in place. I have double checked the public and private DNS settings for autodiscover. Open Both records look fine to me.

Yet, if people use autodiscover to configure an Exchange account with Outlook 2016 on a Mac they receive the wrong certificate (screen shot attached). I do not recognize this certificate, this particular domain is not being use by our organization, we also never purchased it. This certificate (the wrong one) is not installed on Kerio Connect. In fact we have only one certificate (UCC) installed. As I have said before everything works fine if one enters the actual host name for the server and if autodiscover has been disabled in Outlook.

• Attachment: (Size: 73.94KB, Downloaded 187 times). Pavel, I am not sure if I understand your response. Of course the cert is coming Kerio and I do not recognize it. That is what concerns me. Outlook always does autodiscover. Even if you manually enter the server address Outlook defaults to autodiscover. One has to deliberately disable autodiscover.

This is what I did for the users who get the error message. Maybe I should add that I am not using the Kerio setup tool to configure Outlook. It has been a hit and miss in the past also it does not allow for adding multiple accounts in Outlook (some users just need access to multiple accounts and prefer working with one application only). I checked the autodiscover settings on my network from Windows and Mac and the results seem fine to me.