Re: Setting Up OAUTH2 Support for Fetchmail and Postfix
Matthias Andree <[email protected]>
| Newsgroups | gmane.mail.fetchmail.user |
|---|---|
| Message-ID | <[email protected]> |
Am 09.10.20 um 23:16 schrieb Ranjan Maitra: > On Wed, 7 Oct 2020 20:33:13 +0200 Matthias Andree <[email protected]> wrote: > >> Am 07.10.20 um 19:00 schrieb Ranjan Maitra: >>> On Wed, 7 Oct 2020 18:39:41 +0200 Matthias Andree <[email protected]> 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? > Yes it is, and I don't think I will be doing many releases from development branches before it's release candidate time. We have Git and we have autoreconf.