Re: [Fetchmail-users] fetchmail + oauth2 + outlook

[Matthias A. <mat...@gm...>]

Am 12.01.25 um 17:56 schrieb Gerard E. Seibert:
> poll outlook.office365.com with protocol imap timeout 30 and options bad-header accept
>      auth oauthbearer <User Email Address>
>      passwordfile "/home/john/.fetchmail-token" is <John_Smith> here
>      options flush forcecr dropdelivered smtpname 'john_smith@mydomain,com' ssl sslproto 'auto' sslcertfile /usr/local/share/certs/ca-root-nss.crt sslcertck sslcertpath /usr/local/etc/
>
> This is fetchmails response.
>
> fetchmail:/usr/local/etc/fetchmailrc:46: syntax error, unexpected STRING, expecting AUTHTYPE at oauthbearer
> fetchmail:/usr/local/etc/fetchmailrc:46: syntax error, unexpected STRING, expecting AUTHTYPE at oauthbearer
> Stopping fetchmail.
> Waiting for PIDS: 52729.
> Starting fetchmail.
> fetchmail:/usr/local/etc/fetchmailrc:46: syntax error, unexpected STRING, expecting AUTHTYPE at oauthbearer
> /usr/local/etc/rc.d/fetchmail: WARNING: failed to start fetchmail
>
> I found nothing in the Fetchmail FAQ or manual for configuring oauth2 with outlook.
>
> Fetchmail's version:
>
> This is fetchmail release 6.5.1+RPA+SDPS+TLS+NLS.

Gerard,

fetchmail releases (such as 6.5.x in FreeBSD or other operating systems)
do not support OAuth2. In fact, fetchmail does not formally support
OAuth2 at all. There is some contributed code in the Git repository on
the "next" branch, which requires some more development tools and user
proficiency installed to use. It is not a turnkey solution.

I would be helpful to lobby providers away from the massive burden of
OAuth2 towards existing solutions, such as GSSAPI-based Kerberos.

Regards
Matthias