Is anyone else having this problem? I'm trying to set up my work IMAP email with the native Email app on my new S5. When it tries to verify the incoming server settings, the app crashes and I get the "Unfortunately, Email has stopped." error.
If the port or the server name are wrong, it tells me they are wrong. But when it's all right, this happens. I tried factory resetting the phone and starting over, but the problem persisted.
I brought the phone back to the retailer and showed them. The Samsung store guy in Best Buy tried an update and the problem continued. So, they switched out the phone. Sure enough, the same thing happened on the second S5.
I have no problem getting the account to work with Aqua Mail. And, using the exact same settings, I can get my old S3's native Email app to work just fine.
I don't want to post the server info, but I will say that my work's imap incoming server name is not the standard imap.companyname.com format. Instead, it's beehive.companyname.com. It uses SSL security and port 993. The crash happens whether I choose the "SSL" or the "SSL (accept all certificates)" options.
Since it's happening on both S5's I'm thinking this is an app bug problem. Anyone else run into this?
If the port or the server name are wrong, it tells me they are wrong. But when it's all right, this happens. I tried factory resetting the phone and starting over, but the problem persisted.
I brought the phone back to the retailer and showed them. The Samsung store guy in Best Buy tried an update and the problem continued. So, they switched out the phone. Sure enough, the same thing happened on the second S5.
I have no problem getting the account to work with Aqua Mail. And, using the exact same settings, I can get my old S3's native Email app to work just fine.
I don't want to post the server info, but I will say that my work's imap incoming server name is not the standard imap.companyname.com format. Instead, it's beehive.companyname.com. It uses SSL security and port 993. The crash happens whether I choose the "SSL" or the "SSL (accept all certificates)" options.
Since it's happening on both S5's I'm thinking this is an app bug problem. Anyone else run into this?