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

Yahoo also wants OAuth or "enable legacy insecure apps" #1889

Closed
BjarniRunar opened this issue Jul 24, 2017 · 1 comment
Closed

Yahoo also wants OAuth or "enable legacy insecure apps" #1889

BjarniRunar opened this issue Jul 24, 2017 · 1 comment
Labels
Back End Mailpile-v1-is-Obsolete Tagging issues we won't fix because Mailpile v1 development has stopped
Milestone

Comments

@BjarniRunar
Copy link
Member

Same problems as GMail.

We should ultimately add OAuth support for Yahoo.

In the near term, adding Yahoo to the static ispdb list, with hints that trigger the warning would be better than what we do now (nothing: the user just gets told their password is wrong).

@BjarniRunar BjarniRunar added this to the 1.0 Release milestone Jul 24, 2017
@BjarniRunar
Copy link
Member Author

It seems some sort of secret hoops must be jumped through for Yahoo to allow one to create OAuth accounts that can access mail: https://stackoverflow.com/questions/36058534/how-can-yahoo-mail-be-accessed-by-imap-using-oauth-or-oauth2-authentication

I doubt this will get fixed for 1.0rc1, but we can at least warn the user.

@BjarniRunar BjarniRunar modified the milestones: 1.0 Release, 1.1 Release Oct 23, 2018
@BjarniRunar BjarniRunar added the Mailpile-v1-is-Obsolete Tagging issues we won't fix because Mailpile v1 development has stopped label Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Back End Mailpile-v1-is-Obsolete Tagging issues we won't fix because Mailpile v1 development has stopped
Projects
None yet
Development

No branches or pull requests

1 participant