Three times this week, attemptiing to check my Yahoo inbox via IMAP,
I've gotten the OAUTH2 intercept screen and I've dutifully stored the
offered code in the passfile.
I assume this isn't a client issue.
Is this effectively the same as an app password? IMAP simply submits it
as part of my credentials, right?
OAUTH2 is a needlessly complicated way to solve a problem that an app >password did with a lot less fuss, and I've read plenty of criticism of
the actual security it provides.
Adam H. Kerman <ahk@chinet.com> wrote:
Adam H. Kerman <ahk@chinet.com> wrote:
Three times this week, attemptiing to check my Yahoo inbox via IMAP,
I've gotten the OAUTH2 intercept screen and I've dutifully stored the >>>offered code in the passfile.
I assume this isn't a client issue.
Is this effectively the same as an app password? IMAP simply submits it >>>as part of my credentials, right?
OAUTH2 is a needlessly complicated way to solve a problem that an app >>>password did with a lot less fuss, and I've read plenty of criticism of >>>the actual security it provides.
This time, I ignored it, which I should have done the other three times. >>Trying IMAP some time later, no OAUTH2 nag and IMAP was performed.
I looked at my Yahoo account. I had set an app password for use with
alpine in 2020. OAUTH2 is so annoying, I don't think I had been using
it.
I deleted the app password and generated a new one. I did not decrypr
the master password file, trying to force manual credential submission. >Nevertheless, alpine gives the OAUTH2 intercept. Using the app password
as the code doesn't work, of course.
How can I avoid that screen to enter the app password within alpine?
I forced alpine to save the app password. In .pinerc, the entry for the Yahoo inbox has the parameter /auth=oauth2, which I eliminated. Then I
was asked for the password and provided the app password.
Exiting and restarting alpine, I'm still presented with the OAUTH2 intercept, but at least I can exit to get to the index screen of the
inbox.
I discovered 3 OAUTH2 entries for Google, Outlet, and Yandex. Why are
those there? I don't use OAUTH2 with gmail, and I don't use the other
two services at all. Is there any reason at all not to just delete them?
I just don't want a code that would uniquely identify me hanging around
for no purpose.
On Mon, 5 Oct 2026, Adam H. Kerman wrote:
I forced alpine to save the app password. In .pinerc, the entry for the >>Yahoo inbox has the parameter /auth=oauth2, which I eliminated. Then I
was asked for the password and provided the app password.
I am not sure why you had that parameter there. If you do not want oauth2 >then do not add it. Make sure that nothing in your .pinerc says >"/auth=oauth2". That should help.
Exiting and restarting alpine, I'm still presented with the OAUTH2 >>intercept, but at least I can exit to get to the index screen of the >>inbox.
what version of Alpine are you using? My thinking is that the app password >should be tried first, so xoauth2 should not appear.
I discovered 3 OAUTH2 entries for Google, Outlet, and Yandex. Why are >>those there? I don't use OAUTH2 with gmail, and I don't use the other
two services at all. Is there any reason at all not to just delete them?
I just don't want a code that would uniquely identify me hanging around >>for no purpose.
That's internal data, which you can override. The point is that it is
there in case someone needs to authenticate to these services.
Have you tried replacing /auth=oauth2 by /auth=plain (or if you do not
have that string, to add it).
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:01:18 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,448 |