Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

login with Gmail failed with unclear message #2381

Closed
humazed opened this issue Mar 11, 2017 · 8 comments
Closed

login with Gmail failed with unclear message #2381

humazed opened this issue Mar 11, 2017 · 8 comments

Comments

@humazed
Copy link
Contributor

humazed commented Mar 11, 2017

Actual behavior

When login with Gmail account I got this error message
username or password incorrect (command: *sensitive*; response: #3# [No,[ALERT],Please login via web browser: http://support.google.com/mail/accounts/answer/78754(Failure)])
which is not a very useful message.
after searching on google I found the solution is to https://www.google.com/settings/security/lesssecureapps
and enable access for less secure apps.

Expected behavior

I should log into Gmail without much trouble, I know this might take a lot of time;
so I propose at least in the mean time to show the user more meaningful name with the link to this page. as it's not convenient for first time user to search the web for a solution.

Steps to reproduce

  1. Login with Gmail account with lesssecureapps turned off.

Environment

K-9 Mail version: 5.205

Android version:6.0, 7.0, 7.1

Account type (IMAP, POP3, WebDAV/Exchange): Gmail

@rijuldhir
Copy link

Got this same message when I tried to Login with Gmail.
I would like to work on it.

@humazed
Copy link
Contributor Author

humazed commented Mar 12, 2017

I'm already working on it. and will have PR in one day; of course you're welcome to make your own PR.

@humazed humazed changed the title login with Gmail failed login with Gmail failed with unclear message Mar 12, 2017
@gloomy-ghost
Copy link

I am using two step verification and therefore can't modify the lesssecureapps option. Maybe we should show apppasswords instead, and consider oauth2 in the future.

@philipwhiuk
Copy link
Contributor

philipwhiuk commented Mar 14, 2017

Error response improvement is (partially) covered in my Enhanced Status Code work.

OAuth work is mostly implemented in terms of backend work. It needs some UI work to finish off, especially in terms of supporting both Google and none Google providers.

You should already be able to use app specific​ passwords.

@philipwhiuk
Copy link
Contributor

Closing as I think existing issues cover all parts of this.

@humazed
Copy link
Contributor Author

humazed commented Mar 14, 2017

I was working on an enhanced dialog to show more clear error message and was getting ready to make PR should I proceed or do you think the existing solution is enough.

@philipwhiuk
Copy link
Contributor

Feel free to still create a PR. There's issues #1058, #1538 and #2000 still open which your PR would work towards fixing.

@roperi
Copy link

roperi commented Apr 24, 2017

I was getting the same error message and couldn't work out what was going on (I just came across this Github). At first I thought error message had to do with the 2 step verification process I had it turned it ON so I turned it OFF. But that didn't stop the error message from showing up again.

After reading the contents of the link referred by the error message I turned OFF the Allow the Less Secure Apps to be able to open my mails. So I agree with @humazed, the error message should refer to the Google's Less Secure Apps page or directly to https://myaccount.google.com/lesssecureapps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants