From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seamonkey automatic email download after switch to Oauth2
Date: Fri, 03 Jun 2022 12:57:42 +0100 [thread overview]
Message-ID: <11997582.O9o76ZdvQC@wstn> (raw)
In-Reply-To: <8074927.T7Z3S40VBb@dell_xps>
On Friday, 3 June 2022 09:53:22 BST Michael wrote:
> On Friday, 3 June 2022 02:45:11 BST Dale wrote:
> > Howdy,
> >
> > Early this morning Seamonkey could no longer fetch emails. It wouldn't
> > accept the username and password. I did some searching and it seems
> > that Google is disabling plain text username and password. Honestly,
> > sounds like a good idea really. During my searches, most recommended
> > OAuth2 so I switched to it.
>
> Err ... perhaps not? The use of a browser to delegate sign on is not
> necessarily a good idea, because it introduces layers of complication and
> with it potential vulnerabilities. Random explainer here:
>
> https://medium.com/securing/what-is-going-on-with-oauth-2-0-and-why-you-shou
> ld-not-use-it-for-authentication-5f47597b2611
>
> I recall some IMAP4 devs complaining about it, but Google pushed on
> regardless. From the end of May if you want to login to Gmail you have no
> option but to use OAuth2. I expect this will break some users login if they
> have not disabled what Google calls "Less secure application access" and
> shared with Google their mobile phone number and what other *private*
> information Google wants to know, before it allows you to access your email
> messages.
Would a practical alternative be to have all gmail messages forwarded to
another account? I haven't looked into this, but I have a gmail account, which
perhaps I could set up to forward (relay?) all incoming mail to my Zen
account.
--
Regards,
Peter.
next prev parent reply other threads:[~2022-06-03 11:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 1:45 [gentoo-user] Seamonkey automatic email download after switch to Oauth2 Dale
2022-06-03 8:53 ` Michael
2022-06-03 9:31 ` Dale
2022-06-03 10:39 ` spareproject776
2022-06-03 10:07 ` spareproject776
2022-06-03 9:54 ` Michael
2022-06-03 11:15 ` spareproject776
2022-06-03 10:50 ` Michael
2022-06-03 11:57 ` Peter Humphrey [this message]
2022-06-03 14:57 ` Matt Connell (Gmail)
2022-07-23 18:58 ` Dale
2022-07-23 19:21 ` Wol
2022-07-23 20:50 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11997582.O9o76ZdvQC@wstn \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox