SeaMonkey vs. OAuth2

[TPR75]

Some says OAuth2 is future:
https://en.wikipedia.org/wiki/OAuth#OAuth_2.0

Some says it should make life easier for lazy people:
http://homakov.blogspot.com/2013/02/hac ... hrome.html

Well, I hope that future is not "Idiocracy":
https://c.tenor.com/IHv5Hqp5sqoAAAAC/id ... olytes.gif

Unfortunately, Google requires it to use their e-mail service, Gmail. So I was forced to switch to OAuth2 too.

It works... somehow. But I'm not sure it should works like this - is it a feature or is it a bug?

I have POP3 type account and until OAuth2 I was typing password every time I started SeaMonkey (once per session) and when I wanted to send e-mail (once per session too). And it worked like for any other POP3 account.
After OAuth2 password was remembered not per session but for good. And it was remembered for both incoming and outgoing messages. Not remembering password was part of my security and now it's gone.

But wait, there is more! SeaMonkey is set to check for new messages every 20 minutes. But this function doesn't work anymore. And I must check for Gmail account specifically because general function "Get All New Messages" doesn't work either. So, is this a bug or is it a feature? Fortunately, Gmail account is fourth degree/class e-mail service for me and checking once a day is not a problem (so far). But I'm curious...

[therube]

(I only know as much that OAuth2 does work in SeaMonkey. Other issues, no clue?)

[Peter Creasey]

I have no issues with 4 email account being accessed by SeaMonkey using OAuth2 (at least, none that I know about).