iOS 4 Mail and self-signed certificates

The only thing I see in this forum, is the lack of support from apple.

Apple released a big update and disastrous.

They have more problems than improvements.

MobileMail has many problems, not only with the certificates, in some users (like me) can not send mail if the port is 25 and using 3G.

Lot of users have problems with data transfer is cut off or they run slow.

There are comparative and videos everywhere.

Apple does not say anything!

too swindled us with a phone that has manufacturing defects, poor quality antenna and sensor problems that to this day have not been solved well.

Should be more careful, I think that users are not that dumb. We will not always be buying everything that apple makes.

Apple is forgetting who gave them to eat and begins to perform worse than microsoft to their consumers.

I just tried substituting the ip address for the name of the server for an imap certificate.

Used (from the terminal):
nslookup imap.myserver.com

to find the actual ip address

Typed it in where the name was and then accepted the non-trusted certificate inside the "Detail" dialog box (as someone described above). It didn't work UNTIL I rebooted the iphone. I had tried changing the port number, but that was to no avail. Also emailing the pef form of the certificates didn't wok (you can get them by using Firefox 4 to go the server site and exporting the non-trusted certificates).

This is a huge issue as you can't even access your phone without dismissing the dialog box, which is presented multiple times, every time you wake the phone (lots of fun when you need to make a call while driving)

I'll post if for some reason it stops working,

This is only happening on my work email account for the college I work at and not my other email accounts. Our IT group said I was the first to report the problem. I can't be the only one on campus that has upgraded to 4.2.1 so what is up with this?

Hey everyone.

Here's the scoop....

This update requires that you keep "Use SSL" connected, no matter what.

Most of us are either resellers or on a reseller account, so the SSL is set up with the company that owns the server.

You can easily access the smtp information (for using an SSL) from your server through CPanel, or by contacting your host.

Once I changed the SMTP, everything worked perfectly.

My solution:
Original SMTP - mail.mydomainname.com
New SMTP - cs26.servercompany.net

Hope this helps everyone out.

Here's what I did to fix my repeated errors:

Load up Keychain Access on your Mac, choose "Certificates" from the Category panel.
Find the certificate for your mail server in the list, and double click it.
In the information window that should open, Option/Alt-drag the certificate image from the top-left corner into a new message in Mail. You'll know it's done it right if you have a .PEM attachment, not a .CER one.
Send that email to yourself.

Now, on the iOS device, open the email and tap on the certificate. It should take you into Settings and allow you to install the certificate.

On my iPhone, this worked fine, but not on my iPad! You can check if it's trusted by going into Settings, General, Profiles.

Edit: Ah ha, make sure it's the one from the system keychain, not the login one!

Message was edited by: Drarok

Dear mflocks:

First, you "sound" like you are an Apple employee. Whether you actually are or not is irrelevant.

However, the tone in your comment (e.g., "xxx has been elevated to Apple Engineering . . .") is dismissive and has tones of...unfortunately arrogance.

I'm a end-user who uses PKI issued soft certificates AND who wants to migrate from my Blackberry to an iPhone. Frankly, I acknowledge and credit Apple with developing an innovative product.

However, on the other side, telling users that "ABC has been elevated to Apple engineering..." and "DEF has been elevated to Apple Engineering" is just quite frankly arrogant.

Maybe you ...or others in Apple should have considered and included in the "systems engineering concept, design, engineering, implementation and 'test and evaluation' as well as 'validation' components" of the iPhone development?

If you still retain your ..quite frankly 'cocky attitude' maybe the fact that there are xxx of Blackberry users...who represent a potential market could or should persude you and Apple to have a more "consilitary, amicable attitude"? What would that attitude, tone or gesture hurt ...other than a smile on your face?

References:

1. "Blackberry has a 55 percent market share in North America"
http://us.blackberry.com/developers/whyblackberry.jsp

2. Blackberry still boss in smartphone users
http://www.bizjournals.com/washington/stories/2010/03/08/daily60.html

Add me to the list of people who emailed myself the .pem file and installed it. I exported it from Thunderbird (Windows).

So far so good. It survived a background email shutdown and a reboot.

Annoying. Very annoying. Fortunately there are places like this to find support from fellow victims.

Drarok, you're a genius! This totally fixed the problem for me. It was driving me nuts 🙂

I've written up your procedure in a bit more detail, including how to ensure you export a .pem file instead of a .cer file:

http://mac.elated.com/2011/02/26/how-to-fix-ios-mail-cannot-verify-server-identi ty-error-with-self-signed-certificates/

Thanks man!

Late to the party...I just used the technique here: http://www.blackfinsoftware.com/wordpress/2008/08/iphone-and-imapsslself-signed- cert/ to fix this problem. The method is to set up the accounts properly on the Mac, delete the accounts from the phone, then sync.

Perry

This worked for me.

I use siteground for my hosting. in cPanelx > Email Accounts > Configure Email Client > Manual Settings

there are different settings for:

Mail Server Username: +.org
Incoming Mail Server: ..org
Incoming Mail Server: (SSL) x.y.com
Outgoing Mail Server: ..org (server requires authentication) port 2525
Outgoing Mail Server: (SSL) x.y.com (server requires authentication) port 465

I did not have the SSL settings in place.

I'm not saying that my mistake is what is troubling others; I'm only saying that this was what was troubling me. Thanks to the previous respondant.

when verifying the account it should prompt you regarding the 'not trusted' certificate.

i have seen this on ios 4.1 and 4.2 today.

you can choose to accept the certificate.

I am having the exact same problem. Have you found a fix? I really don't want to buy an SSL cert.

I broke down and bought a cert today. It's a shame, but that MobileMail pop-up window was driving me crazy.

Message was edited by: kevinmoore73

Someone please help... Or apple fix this asap... With nearly 15 domains, I'm not about to buy private certificates. Why can't I accept it once, or trust the site like I always have before.