Re: [Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[Kevin J. McCarthy]

On Wed, Mar 27, 2019 at 04:54:04PM +0100, felixs wrote:

Having studied oauth2 more in depth I do not consider it to be secure
enough (as such) mainly because of its overwhelming complexity, and I will NOT 
use it for mail purposes.


Thanks for the update felixs.  I've just returned from overseas so my
schedule is a bit full, but as soon as I can I will fix up and push the
patch into stable.

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature

[Fwd: Re: Impossible to connect to mail server via pops3 using mutt 1.11]

[felixs]

On Sat, Mar 23, 2019 at 08:29:44PM +0800, Kevin J. McCarthy wrote:
> On Sat, Mar 23, 2019 at 10:27:38AM +0100, felixs wrote:
> > 'getoauthbearersupport'  and 'no refresh command defined', not showing
> > any willingness to download my e-mais.
> 
> Hi felixs,
> 
> The OAUTH support was added in version 1.11.0.  Perhaps the POP
> implementation hasn't gotten enough testing.

Thanks, Kevin, for your kind answer. Actually, I downloaded the
oauth2.py script and I will check if I can adapt it for using it with
pop as well (importing the pop libs), so I will do some testing,
at least with my gmail account. I'm not a real programmer, but I am in the 
'training
circuit'...)

(...)
I now will try to set up the oauth2 authentication.
(...)


Having studied oauth2 more in depth I do not consider it to be secure
enough (as such) mainly because of its overwhelming complexity, and I will NOT 
use it for mail purposes.
For more secure authentication to the mail server, one might consider using 
OpenID Connect, but on
the other hand I am meditating about whether I need such a system at all.

felixs