They actually suggested the same thing you did, that it was somehow my service provider that made the configuration change that caused this problem. There is little wonder then, that their support articles are of no use to solve this problem. So far, Apple support has been of no use. That's what motivated me to try to ask here.
I did remove and recreate the account with the problem, which did not solved nothing. It really is shockingly unhelpful to repeat what a quick search in the support pages returns. In fact, I had already seen that article, and tried everything in it before posting here.
Then, when I recreated those email accounts, I was able to accept the certificate as before the 10.2.1 update. It was in the outgoing mail server list for the Google mail account where I was able to delete the failing outgoing mail server entries. As long as that entry exists in the outgoing email server list, iOS will not present the option to trust its certificate after the 10.2.1 update.įor us, I deleted all email accounts on our iPads that were hosted by Dreamhost, leaving my Google mail account. It does nothing to delete the account that has the failing outgoing mail server, as suggested by the Apple support page, if you have more than one email account defined. It isn't possible to delete the entry for the failing outgoing mail server if it is in use by any email account What has to be done is to go to the outgoing mail server settings for another email account (after deleting the mail account that was using the failing outgoing mail server), and deleting the failing outgoing mail server entry from the list of outgoing mail servers. Since I have several email accounts, that outgoing mail server entry remains in iOS, available for those other email accounts to use. Simply deleting the email account that is using the offending outgoing mail server doesn't do the job. I did get that suggestion from Dreamhost, and that was going to be my last resort.:
0 kommentar(er)
