Re: [Fetchmail-users] Setting Up OAUTH2 Support for Fetchmail and Postfix

[Peter P. <ro...@ri...>]

On Fri, Oct 09, 2020 at 04:16:54PM -0500, Ranjan Maitra wrote:
> On Wed, 7 Oct 2020 20:33:13 +0200 Matthias Andree <mat...@gm...> wrote:
> 
> > Am 07.10.20 um 19:00 schrieb Ranjan Maitra:
> > > On Wed, 7 Oct 2020 18:39:41 +0200 Matthias Andree <mat...@gm...> wrote:
> > >
> > >> Am 07.10.20 um 06:51 schrieb Ranjan Maitra:
> > >>> According to the site, that may be dated, but fetchmail has oauth2 support from fetchmail7. Will it be available soon?
> > >> Ranjan,
> > >>
> > >> that depends on how leniency of your definition of "soon".
> > >>
> > >> First we will have a 6.5 release branch, and that has not yet happened,
> > >> so I expect that 7.x will be a matter of 2021, but if you are running it
> > >> from the up-to-date "next" branch in Git (available on Gitlab and
> > >> Sourceforge), feel free to file bug reports.
> > >>
> > >> Regards,
> > >> Matthias
> > > Thanks,
> > >
> > > I have used fetchmail 7 without much of a problem (or something that I have noticed, anyway). Is it possible to backport the patch for oauth2 in the  6.x.x releases? I prefer using the rpms released by the distributions.
> >
> > I am not doing that, and the purpose of the existing 6.x.y branches is
> > compatiblity as we update y and if possibly also when updating x. There
> > may be minor features in 6.5.y.
> >
> > 7.x.y is for major changes.
> >
> 
> So, I was looking at https://sourceforge.net/projects/fetchmail/files/branch_7-alpha/ and here, there has not been an update here since about 2 years ago. Is the git version more up-to-date?

The "next" branch in the Git repository has commits from this year:

https://sourceforge.net/p/fetchmail/git/ci/next/tree/

G'luck,
Peter

-- 
Peter Pentchev  ro...@ri... ro...@de... pp...@st...
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13