From: Carlos E. R. <car...@op...> - 2015-11-18 16:09:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2015-11-18 09:23, Matthias Andree wrote: > Am 17.11.2015 um 15:17 schrieb Carlos E. R.: > > First, Is configuring "access for less secure apps" on the Google > end an option, and would it help? Maybe. I'll try. This oauth thing is new to me: other accounts I have with gmail work fine with fetchmail, so I assume that "less secure setting" is enabled, but newer accounts get it automatically. > Fetchmail does not talk HTTP, and OAuth2 is breaking media. > Checking Google's SASL XOAUTH2 spec, it seems we'd need to write an > HTML client, a JSON parser, perhaps a cookie handler, a callback to > the user (which is incompatible with cron rigging and daemon mode > setups) per the "limited-input devices" MSC on > https://developers.google.com/identity/protocols/OAuth2. ... (long quote removed) I see. Thanks for the extensive explanation :-) > If Google want to force you to use a browser, that's fine - only > fetchmail won't be that browser. No, I don't want that either! Fetchmail is a wonderful app as it is. I just was not aware of what this oauth2 is. I guess it works with Thunderbird because it has access to a browser internally. I got a pop-up message the first time with some info. I should have taken a photo. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZMoq0ACgkQtTMYHG2NR9VjAwCeMlkU5KkLTdBmkBSKQ7zAsLyK H7YAn2Qh1kY2jl3BGNL5FIV0t/dVEEVd =pPMR -----END PGP SIGNATURE----- |