From: grarpamp <gra...@gm...> - 2017-02-22 08:34:44
|
> https://sourceforge.net/p/fetchmail/mailman/message/34628292/ >> https://frontier.com/helpcenter/categories/internet/email/email-security-upgrade > https://johnlane.ie/gmail-fetchmail-is-a-less-secure-app.html OAuth2 https://tools.ietf.org/html/rfc6749 OAuth2 Bearer https://tools.ietf.org/html/rfc6750 SASL-IR http://tools.ietf.org/html/rfc4959 https://developers.google.com/gmail/xoauth2_protocol If there's no suitable library [search / github?] it should be possible to pass the preliminary bits out to a user program that returns the needed token bits. Probably with env vars carrying the name of a just then created mkstemp(3) file for the return purpose. Vars for user / pass / authtype / server... whatever fetchmail has for that particular session / connection. Some users could write program scripts for contrib. It's uglier than a library, and leaves a lot to the user, but seems doable even in /bin/sh, wget, openssl base64, etc... common system tools. |