In 1.12, we improved the security of the app's networking by adding a check for "server names specified in the server's certificate".
Yes some servers may fail the new check, esp. with custom domains.
One workaround is to long press on the account -> account setup -> Manual and change "security" from "SSL (strict)" to "SSL (any)" then tap Next again and make same change for the outgoing server.
But:
To get things back working and get the new improved security at the same time - your mail server names need to match whatever's specified in the certificate presented by the server, and then you can use "SSL (strict)" again (with the new check).
If you can't work out the right server names - please follow Nadia's advice above, and email us you current server names, we'll try to find "the right ones" for you.
---
An example:
user@brownies.com <- custom domain
Actual mail service is MailService Inc.,
http://www.mailservice.comYour current servers:
imap.brownies.com and smtp.brownies.com
The SSL certificates on these servers indicate the following "acceptable" server names:
*.mailservice.com
This does not match imap. / smtp. brownies.com -> error if using "SSL (strict)"
But let's say your mail provider's help page (for email settings) says you can use:
mail.mailservice.com (or imap.mailservice.com and smtp.mailservice.com)
instead of your current
imap. <your domain> .com and smtp. <your domain> .com
Bingo. These server names ( imap. / smtp. mailservice.com ) will pass the check against the "*.mailservice.com" pattern in the certificate -> no error even if using "SSL (strict)".