AquaMail Forum
English - Android => General Discussion => Topic started by: nhlevin on June 18, 2017, 04:29:12 pm
-
OK, here we go again. There was much written about this in the forum back in 2013 and a few tidbits since though I just spent the past few days trying to troubleshoot an authentication issue with my mac.com IMAP account, which occurred shortly after latest update. I can get my email through the iCloud web portal and from my MAcBook Pro with Mac Mail, though can no longer authenticate from Aqua Mail.
Settings are well published:
User id is full email.
993 and imap.mail.me.com incoming
587 and smtp.mail.me.com outgoing
Been trying all security types.
Any insights?
Otherwise, still love this app! Truly well done.
-
See this thread for possible help with this.
https://www.aqua-mail.com/forum/index.php?topic=5825.0;topicseen
-
https://blog.freron.com/2017/application-specific-passwords/
1:
A while ago Apple announced that they are going to require that all applications accessing iCloud data (including emails in iCloud email accounts) must do so using a so-called application specific password. This happens a week from now, that is, on June 15.
2:
Apple uses an authentication method only available to applications created by Apple. All third party applications are going to require an application specific password if they need to access an iCloud account.
-
I just added an announcement and a help article to the web site:
http://www.aqua-mail.com/?p=3422
-
Well THAT was certainly easy.
Is it me or is that just unnecessarily nutty of Apple?
Many thanks, Katsya. Your app remains one of my favorites. Great work!
Neal
-
A few mail providers these days are calling the "good old" password based method of logging in "less secure" and don't allow it (Gmail, Yahoo).
A few others support a "more secure" method but it's not mandatory.
This "more secure" is called OAUTH2 and is open for mail apps to implement.
Apple's latest move however is a bit different:
- They don't allow password based anymore
- And yet there "more secure" is *not* OAUTH2, so probably can't be supported by third party apps.
"Think different" (AKA "one vendor ecosystem") and all that...