Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.comp.software.seamonkey    |    Not a bad little Mozilla fork    |    9,725 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 9,288 of 9,725    |
|    NFN Smith to David H Durgee    |
|    Re: Problematic popup for imap.mail.yaho    |
|    10 Oct 25 14:40:51    |
      From: worldoff9908@gmail.com              David H Durgee wrote:       >       > I have Thunderbird on my system as well, but I don't use it as I prefer       > SeaMonkey. If I were to set up Thunderbird to access Yahoo mail via       > IMAP and SMTP with oauth2, assuming it will work, would there be a way       > to pull the oauth2 entry from it and add it to the SeaMonkey password       > file to get it working here?              I use both Thunderbird and Seamonkey, and prefer Seamonkey, as well.              I don't believe that OAuth2 tokens are portable, even if you move a       profile from one computer to another.              I don't know the internal mechanics of how tokens are composed, but       they're essentially a fingerprint of your mail client, and where each       token is entirely unique, and not reusable.              I don't believe there's a way of export and import of a token, but even       if there was, the server in question would reject a submitted token as       inauthentic.              Remember that the purpose of OAuth2 is for multi-factor authentication,       where your password is "something you know", and the token is "something       you have". I'm guessing, but the creation of a token is likely to be       something that is done with server participation, which would mean that       the server recognizes the configured mail client.              Although it seems intimidating, if you have a token in one client and       want to use another client, then you have to use the second client to       create its own token. However, that should be simple enough to do in       the second client if you make sure there are no saved tokens, and then       let the process work the way intended. That means that after the server       has been contacted (and authenticated your password), you get a pop-up       initiated by the server that requests a re-entry of your password. When       the password is correct, then the token will be created, and       subsequently, should be invisible to you.              Smith              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca