• OAUTH2 itercept at Yahoo

    From Adam H. Kerman@ahk@chinet.com to comp.mail.pine on Wed Sep 30 18:41:48 2026
    From Newsgroup: comp.mail.pine

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to comp.mail.pine on Wed Sep 30 22:34:12 2026
    From Newsgroup: comp.mail.pine

    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to comp.mail.pine on Mon Oct 5 06:41:15 2026
    From Newsgroup: comp.mail.pine

    Adam H. Kerman <ahk@chinet.com> wrote:
    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.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Eduardo Chappa@chappa@washington.edu to comp.mail.pine on Wed Oct 7 21:15:05 2026
    From Newsgroup: comp.mail.pine

    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).
    --
    Eduardo
    https://alpineapp.email (web)
    http://repo.or.cz/alpine.git (Git)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Adam H. Kerman@ahk@chinet.com to comp.mail.pine on Thu Oct 8 04:20:27 2026
    From Newsgroup: comp.mail.pine

    Eduardo Chappa <chappa@washington.edu> wrote:
    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.

    I found it in folder collections and a role. I seem to have had XOAUTH2
    as well but I don't know the difference.

    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.

    2.26 Debian build

    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.

    Just commented it out.

    Have you tried replacing /auth=oauth2 by /auth=plain (or if you do not
    have that string, to add it).

    Good idea.

    I added /auth=plain to the incoming messages collection, the folder
    collection, and the SMTP portion of the role. alpine asked for the app
    password again, so I provided it for IMAP. I used the role to send a
    test message and was asked for the app password for SMTP.

    No more OAUTH2 intercept screen.

    I had thought I was using an app password but I must have used OAUTH2
    for both IMAP and SMTP.

    Yahoo wasn't causing problems till I posted about it here.

    Thank you.
    --- Synchronet 3.22a-Linux NewsLink 1.2