ios 10 with self-signed certificate in MS Exchange

After 3 days of speaking to Apple, 1^st level, then 2^nd level, then 3^rd level, then being referred to Apple UK 4^th tier support, who then referred me to Apple international enterprise partner support. They have finally acknowledged there is an issue. They will not take no responsibility for causing the problem because they say it is a “cross level system” ie Apple talking to Microsoft, even though it only affects ios 10. They have said they are working on a fix but it won’t be rolled out until most likely the next couple of versions of ios 10. They apparently will keep me in the loop on their progress.

For the time being the only workaround I found is to use the Microsoft Outlook client for iphones, until Apple notifies otherwise.

Hello,

tested after installing iOS 10.1 and looks like Apple has fixed issue.

Still doesn't work for me. It is fine if you had the certificate trusted from ios 9.3, even if you have deleted the email account and re-add it. But still get just get details and cancel when adding an new account to ios 10.1.

this works not for me - does anyone have an how-to to fix this problem?
iOS 10.1 Update does not help with this

thanks

Hello,

i have the same issue, self signed certicate and ios 10.1 does not fit (on my iphone) - on my ipad it works because the account was created in an 9.x version and I think there was an "accept" or "install" button for the certificate - now there is no one and i can´t use my exchange account.

Please Apple help and make a solution to accpet self signed certificates

Thanks

Eric

I have the same problem trying to accept a self signed certificate for Mac OS server 10.12

HI, I have the same problem when try to add mail on a ios10.1.1 tjat nerver been usel before.

Hi, we have unfortunately the same problem. A iphone 6 with version 10.1.1 and installed self-signed certificate we do not get to run!
If we like the attempt on an Iphone 5 with 10.1.1 and installed self-signed certificate works!
Has anyone of you can solve the problem?

You have to delete and re-add your Exchange account, except when re-adding it, specify a correct server name but provide false info for the other fields. So for example, enter the server name as normal but then put the letter "a" in the other fields. When you click next it will ask if you want to continue instead of just details or cancel, and then it'll say it cannot verify Exchange details, at which point click OK and enter the correct info in all fields, then click next and save, and voila Exchange should be working again.

I had that headache myself when we changed the self-signed certificate on our Exchange server. Very annoying bug (or feature) that Apple introduced in iOS 10. In iOS 9 and below, any changes in certificates prompts you to continue as normal without having to do the above.

Why Apple???

Thank you! This workaround did the trick.

ios 10.1.1 connecting to Exchange 2010 using self published cert.

Thank you! This saved my day 😉

I had the same problem, the listed solution did not work for me. However, entering the mail server's direct IP address worked like a charm! If you need to find your mail server's IP address, you can simply "ping mail.yourdomain.com" from most command prompts or shells.

Hello,
I have the same problem with a messenger server ie MDaemon, apple works with a solution where the decision is irevocable
Thank you

None of the provided Solutions worked for me, but I got it working either way using a slightly different Approach.

This has been tested twice with both an iPhone 5s and an iPad Air (don't know the Revision) running iOS 10.2

First off, delete all Exchange-related Certificates off of your iDevice.

Then export your Domains root-CA's certificate(s), which is used to establish the Domain trust.

Send yourself an E-Mail containing the certificate(s) and make sure to Import it/them from within the mail app. (this is crucial)

Afterwards you can re-add your Exchange-Account and it will give you the Option to trust the Connection, because now the CA is known and trusted by your device.

I hope this helps. I was also struggling with this issue since October and stumbled upon this solution by complete accident at work.

Regards,