fetchmail-users — User questions and discussion

[Fetchmail-users] ANNOUNCE: The 6.5.0.beta8 snapshot of fetchmail is available

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

The 6.5.0.beta8 release of fetchmail is now available at the usual 
locations,
including <https://downloads.sourceforge.net/project/fetchmail/branch_6.5/>.

The source archive is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.beta8.tar.xz/download>

The detached GnuPG signature is available at:
<https://downloads.sourceforge.net/project/fetchmail/branch_6.5/fetchmail-6.5.0.beta8.tar.xz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.5.0.beta8.tar.xz)= 2d984fcd03a26629efdb9126c33db5d03c63b59c35b3924f86f0ec8700fbfcd9


Here are the release notes since beta7, but also review the NEWS file
for all changes since 6.4.28..6.4.34 which are also part of this release
but not shown here for brevity.
See <https://gitlab.com/fetchmail/fetchmail/-/blob/6.5.0.beta8/NEWS>

--------------------------------------------------------------------------------
* --auth ssh may be removed from future fetchmail versions. Use --auth implicit.
* Future fetchmail releases (even minor ones) may change undocumented parts of
  the .netrc parser in incompatible ways to enhance compatibility with typical
  ftp(1) .netrc parsers.
* Apparently OPIE is dying. I only have this support on FreeBSD, and
  FreeBSD 14 (slated for release in 2023) is about to remove it.
--------------------------------------------------------------------------------
* FreeBSD's OPIE implementation cannot be found when using a C++ compiler.
  This should not affect the normal build, which uses a C compiler.
* .netrc now may not have more than 0700 permission if it contains 
* passwords, else fetchmail will warn and ignore the file.
* The .netrc parser no longer permits "machine" after "default".
* Add manpage info on the .netrc syntax, as ftp(1) is not standardized and
  may not be installed. Fixes Launchpad Bug #1976361 reported by Bill Yikes.
* fetchmail's --auth option ssh was renamed to implicit, to make clear that it
  does *NOT* imply any particular type or features of the --plugin.  --auth ssh
  will be understood for a while for compatibility but fetchmail will report it
  as implicit.
* fetchmail can be built with meson <https://mesonbuild.com/>.
================================================================================

[Fetchmail-users] ANNOUNCE: fetchmail 6.4.34 is available (critical softbounce fix and translation updates)

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

The 6.4.34 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

It fixes a situation where a permanent SMTP refusal could cause loss of 
messages (by deletion from the upstream server) even though softbounce 
was set.  Bug report and patch courtesy of Horváth Zsolt.
Translation update for Serbian courtesy of Miroslav Nikolić.

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.xz/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.lz/download>

The detached GnuPG signature is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.xz.asc/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.34.tar.lz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.4.34.tar.xz)= c3bdded1b5ce236960bd1ceeee3f3257220ed99c3eec84a5d76bb5618e3258d4
SHA2-256(fetchmail-6.4.34.tar.lz)= 920b9b488471d1c76a2e7060344eec347b409ef954a86a200549cf6c2adf40fe


Here are the release notes:
--------------------------------------------------------------------------------
fetchmail-6.4.34 (released 2022-10-15, 31701 LoC):

# CRITICAL BUG FIXES:
* When an SMTP receiver refuses delivery, a message would be deleted from
  the mail store in spite of a softbounce option that is enabled.
  Bug report, analysis and patch by Horváth Zsolt. Gitlab, fixes #50.

# BUILD NOTE:
* If you are reusing config.cache from prior builds, this may cause
  issues with finding Python or some libraries.  In case of trouble,
  remove config.cache and retry.

# TRANSLATIONS: language translations were updated by this fine person:
* sr:    Мирослав Николић (Miroslav Nikolić) [Serbian]

--------------------------------------------------------------------------------

Re: [Fetchmail-users] Proper method to submit code update/patch?

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

Am 15.10.22 um 03:50 schrieb William R Somsky:
> I've developed a patch to fetchmail:next to successfully perform OAuth2
> authentication in daemon mode. What is the proper method to submit this for
> consideration to the baseline code?

Hello William,

the most convenient way for me would be if you had to Gitlab account and
would submit a pull request through it, here:
https://gitlab.com/fetchmail/fetchmail/-/merge_requests - or if you are
unsure about Git, you can instead file an "issue" there and attach it.

The other thing is if the patch is small enough (< 30 kB) you can submit
it through the fetchmail-devel@ mailing list which is subscriber-only
posting and requires that you can tell your mailer to mark the patch a.
as attachment and b. as text/plain or similar, so it does not get
stripped away.

Looking forward to your submission!

Regards,
Matthias

[Fetchmail-users] Proper method to submit code update/patch?

[William R S. <wrs...@gm...>]

I've developed a patch to fetchmail:next to successfully perform OAuth2
authentication in daemon mode. What is the proper method to submit this for
consideration to the baseline code?

WRSomsky <wrs...@gm...>

[Fetchmail-users] Microsoft deprecated

[Jerry G. <jer...@gm...>]

Hi - I just joined the list.

I have centos 7 running fetchmail  fetchmail-6.3.24-7.el7.x86_64
Been working for years till microsoft deprecated basic auth.

How can I update fetchmail to support this?

I just saw another post about it...

Jerry

[Fetchmail-users] Working with Office 365; fetchmail_oauth2.py

[<rb...@al...>]

	A mail server I use uses Office 365, recently switched to its
OAuth2.  I've gotten OAuth2 to work with gmail, which is different.
	I downloaded github.com/lubonbvba/fetchmail_oauth2 but see no
instructions to make it work - does it?
	Another person mentions using fetchmail 7 - what does
fetchmail say about that?

russell bell

[Fetchmail-users] ANNOUNCE: fetchmail 6.4.33 is available (translation and contrib/ updates)

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

The 6.4.33 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

Turns out the snapd version of HTMLDOC 1.9.16 is broken, so I have added 
a wrapper script that uses the flatpak version of HTMLDOC, for the 
benefit of rebuilding on distros that do not ship HTMLDOC natively.

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.xz/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.lz/download>

The detached GnuPG signature is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.xz.asc/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.33.tar.lz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.4.33.tar.xz)= 82954ebd26c77906463ce20adca45cbcf8068957441e17941bd3052a5c15432e
SHA2-256(fetchmail-6.4.33.tar.lz)= 80fe73c709e8390deabe7e7db979fca4c161d35056331397a4b783c4aacb5911

Here are the release notes:
--------------------------------------------------------------------------------
fetchmail-6.4.33 (released 2022-08-27, 31696 LoC):

# TRANSLATIONS: language translations were updated by this fine person:
* fr:    Frédéric Marchal [French]

# CONTRIBUTED SCRIPT CHANGES:
* contrib/fetchsetup improvements by Matěj Cepl
* contrib/runfetchmail improvements by Matěj Cepl

--------------------------------------------------------------------------------

[Fetchmail-users] ANNOUNCE: fetchmail 6.4.32 is available (translation updates)

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

The 6.4.32 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

It updates translations and makes maintainer-build fixes.

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.xz/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.lz/download>

The detached GnuPG signature is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.xz.asc/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.32.tar.lz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.4.32.tar.xz)= 3ee7444665606ad06fb5f7b15f91e3173b845bc98b646b1a4514a46aa48b7228
SHA2-256(fetchmail-6.4.32.tar.lz)= fea53fc9088207c65bcc3692d66ad91958fbff2e65aef74ca34094f4361e8169


Here are the release notes:
--------------------------------------------------------------------------------
fetchmail-6.4.32 (released 2022-07-30, 31696 LoC):

# FIXES:
* Use configure to find rst2html, some systems install it only with .py suffix,
  others only without, and some install both.
* Update README.maintainer

# TRANSLATIONS: language translations were updated by these fine people:
(in alphabetical order of language codes so as not to prefer people):
* cs:    Petr Pisar [Czech]
* es:    Cristian Othón Martínez Vera [Spanish]
* ja:    Takeshi Hamasaki [Japanese]
* pl:    Jakub Bogusz [Polish]
* ro:    Remus-Gabriel Chelu [Romanian]
* sq:    Besnik Bleta [Albanian]
* sv:    Göran Uddeborg [Swedish]

--------------------------------------------------------------------------------

[Fetchmail-users] 'Modern Authentication'

[<rb...@al...>]

	Replied someone at Caltech:

	'I utilize fetchmail on Linux to retrieve mail from o365, and
there is currently no production release of fetchmail that supports
oauth2.
	'That said IMSS licenses Red Hat Enterprise Linux and
fortunately for me the system on which I need to utilize fetchmail is
RHEL 8.  The is a current request in Bugzilla asking that oauth2 be
supported in RHEL 8, and there is a development source rpm that can be
rebuilt on Red Hat systems, and very likely CentOS 8.
	'If you use either of those, there is an open request for
customers to test the recently added oauth2 function ; I am personally
planning on doing this soon as I have a vested interest in continuing
to utilize fetchmail once Microsoft has made the change to o365.'


russell bell

Re: [Fetchmail-users] 'Modern Authentication'

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

Am 27.07.22 um 04:10 schrieb rbell--- via Fetchmail-users:
> 	Caltech says, 'Modern Authentication is the replacement for
> Basic Authentication.  Modern Authentication is a more secure method
> to access information and it is based upon OAuth 2.0 for
> authentication and authorization.  Modern authentication also supports
> Multi Factor Authentication.' and, 'POP and IMAP will no longer be
> supported'.
> 	Can I make fetchmail authenticate 'modernly'?

If Caltech are taking away/down POP3 and IMAP service, then fetchmail
will most likely become useless, no matter the form of authentication,
but it seems they got themselves confused.

If they keep POP3 and IMAP service but require OAuth2 then the question
will be if they just hand out the necessary IDs or if they want the
software reviewed and thereabouts, which I am not going to submit
fetchmail for because OAuth2 in practice means "you mail service
provider's specific local variant of OAuth2". The "next" branch in
fetchmail's Git repository has some support, and you may need to adapt
the Microsoft dialect of OAuth2 to your Caltech account, but this is all
depending on Caltech's local policies, and I cannot personally support it.

--
Matthias Andree

[Fetchmail-users] 'Modern Authentication'

[<rb...@al...>]

	Caltech says, 'Modern Authentication is the replacement for
Basic Authentication.  Modern Authentication is a more secure method
to access information and it is based upon OAuth 2.0 for
authentication and authorization.  Modern authentication also supports
Multi Factor Authentication.' and, 'POP and IMAP will no longer be
supported'.
	Can I make fetchmail authenticate 'modernly'?

russell bell

Re: [Fetchmail-users] ANNOUNCE: fetchmail 6.4.31 is available (manpage version and date tags wrong)

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

Note that fetchmail 6.4.31's tarball contains the wrong date and version 
in the manual page, it will identify as 6.4.30 from February this year,
not as up to date 6.4.31.  If you find that confusing, apply the 
following one-line patch (also attached in Git e-mail patch format):

--- a/fetchmail.man
+++ b/fetchmail.man
@@ -10,7 +10,7 @@
 .\" Load www macros to process .URL requests, this requires groff:
 .mso www.tmac
 .\"
-.TH fetchmail 1 2022-02-18 "fetchmail 6.4.30" "fetchmail reference manual"
+.TH fetchmail 1 2022-07-16 "fetchmail 6.4.31" "fetchmail reference manual"
 
 .SH NAME
 fetchmail \- fetch mail from a POP, IMAP, ETRN, or ODMR-capable server

-- 
Matthias Andree

[Fetchmail-users] ANNOUNCE: fetchmail 6.4.31 is available (netrc, configure, manpage updates)

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

The 6.4.31 release of fetchmail is now available at the usual locations,
including <https://sourceforge.net/projects/fetchmail/files/branch_6.4/>.

It should make the build a bit more robust and the manpage more 
portable, and adds some error checking to the .netrc file parser.

Further .netrc parser updates and documentation of expected input 
formats are postponed to fetchmail 6.5 because they might break existing 
setups, so should not change in a patchlevel release.

Note that OpenSSL and wolfSSL both had security updates, OpenSSL for 
c_rehash, and wolfSSL had fixes for side channel attacks. Upgrade those 
before you upgrade fetchmail. Versions are at least OpenSSL 1.1.1q or 
3.0.5, or wolfSSL 5.4.0. The documentation has been updated accordingly,
but fetchmail does not enforce these, leaving it up to distributors.

The source archive is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.xz/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.lz/download>

The detached GnuPG signature is available at:
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.xz.asc/download>
<https://sourceforge.net/projects/fetchmail/files/branch_6.4/fetchmail-6.4.31.tar.lz.asc/download>

The SHA256 hashes for the tarballs are:
SHA2-256(fetchmail-6.4.31.tar.xz)= 904bf9247054df8e91b47b1a9fe15a31dda8478c25b5291da0424653744a28f7
SHA2-256(fetchmail-6.4.31.tar.lz)= db7bf0af57f5a5b41ef5cb4c8d62e3f20b3513fc5b964fd2ea84cf1b7814a53c


Here are the release notes:
--------------------------------------------------------------------------------
fetchmail-6.4.31 (released 2022-07-16, 31694 LoC):

# BUG FIXES:
* Try to fix ./configure --with-ssl=... for systems that have multiple OpenSSL
  versions installed.  Issues reported by Dennis Putnam.
* The netrc parser now reports its errors to syslog or logfile when appropriate,
  previously it would always log to stderr.
* Add error checking to .netrc parser.

# CHANGES:
* manpage: use .UR/.UE macros instead of .URL for URIs.
* manpage: fix contractions. Found with FreeBSD's igor tool.
* manpage: HTML now built with pandoc -> python-docutils
  (manServer.pl was dropped)

--------------------------------------------------------------------------------

Happy fetches,
Matthias

Re: [Fetchmail-users] pls help on: 523 Message length (10485822 bytes) exceeds administrative limit (10485760)

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

Am 20.06.22 um 11:11 schrieb mario chiari:
> Hi
>
> I am unable to download a message with several large attachments.
>
> Log says:
>
> 523 Message length (10485822 bytes) exceeds administrative
> limit(10485760).
> sendmail: Unable to submit message.
> fetchmail: reading message <mymail>@pop3.<myDomain>:13 of 18 (12384194
> octets) (log message incomplete)
> fetchmail: MDA returned nonzero status 67
> fetchmail:  not flushed
>
> I have already asked help on this a couple of years ago, but I do not
> remember if/how  we fixed it (I doubt we did).
>
> It seems to be a issue with sendmail (or maybe, with the courier
> limited version of sendmail), but I do not how to check/reset sendmail
> configuration.

Mario,

you will need to find the documentation or assistance for your local MTA
that fetchmail delivers into. That is outside fetchmail's scope, but 10
MB seems to be a popular limit.


So if you are using Courier MTA in a full install, you need to find the
Courier documentation that sets a 10 MByte size limit for SMTP port, and
raise that limit.

Myself not being a Courier-MTA user, I cannot help much, Googling seems
to yield
https://manpages.debian.org/stretch/courier-mta/courier.8.en.html and it
documents sizelimit but you need to see which exact version you are
using and where and how you need to set the configuration and what it
takes (such as reloading or restarting the server after the change).
Further questions please to the Courier lists.

HTH.

Regards
Matthias

[Fetchmail-users] pls help on: 523 Message length (10485822 bytes) exceeds administrative limit (10485760)

[mario c. <ml...@ma...>]

Hi

I am unable to download a message with several large attachments.

Log says:

523 Message length (10485822 bytes) exceeds administrative
limit(10485760).
sendmail: Unable to submit message.
fetchmail: reading message <mymail>@pop3.<myDomain>:13 of 18 (12384194
octets) (log message incomplete)
fetchmail: MDA returned nonzero status 67
fetchmail:  not flushed

I have already asked help on this a couple of years ago, but I do not
remember if/how  we fixed it (I doubt we did).

It seems to be a issue with sendmail (or maybe, with the courier
limited version of sendmail), but I do not how to check/reset sendmail
configuration. 

Your advise is welcome
Thanks Cheers
mario 

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[Marco G. <ga...@li...>]

Mandi! joe a
  In chel di` si favelave...

> A bit more digging shows anything below V7 may be fruitless to pursue. 

No, you can still patch fetchmail 6.4 and make it work with oauth2, but the
culprit came by the fact that the 'test' oauth2 app you cane esaly create
last one week.

You have to 'publish' the oauth2 app, and this seems really complicated for
BigG...


Real answer: use app password, as stated here.

-- 
  Does anybody here remember Vera Lynn?
							(Pink Floyd)

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[Dennis P. <da...@be...>]

On 6/14/2022 9:23 AM, rbell--- via Fetchmail-users wrote:
> 	'Go to "Manage account". Select "Security" and enable 2 factor
> authentication. One that is done go back to security to "App
> passwords." Follow that process and get a key.'
> 	When I do that I don't get a key.  I have to give a phone
> number to send a key to then get a key for each interaction or buy a
> physical key or have a phone (I have no phone service) to run an app
> on.  What am I doing wrong?
>
> russell bell
>
>
>
Correct. The phone number gets you a key for the 2 factor 
authentication. If you have no phone service then you need to borrow or 
go somewhere you do have phone service. You only need to do this once. 
After that is done, THEN you can set up the "app password.' It is a 
multi-step process.

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

On 6/12/2022 2:36 PM, Dennis Putnam wrote:
> I've just gone through the same thing. It turns out that OAuth2 is not 
> necessary. Log on to your google mail user and set up 2 factor 
> authentication. Go to "Manage account'. Select "Security" and enable 2 
> factor authentication. One that is done go back to security to "App 
> passwords." Follow that process and get a key. Use that key as the 
> password in your fetchmailrc and you will be good to go.
> 

Thanks, you've saved me a lot of investigative work! (apologies to Nick 
Danger)

joe a.

(I sent this yesterday, but appears not to have posted.  Please excuse 
any double post)

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

On 6/14/2022 9:23 AM, rbell--- via Fetchmail-users wrote:
> 
> 	'Go to "Manage account". Select "Security" and enable 2 factor
> authentication. One that is done go back to security to "App
> passwords." Follow that process and get a key.'
> 	When I do that I don't get a key.  I have to give a phone
> number to send a key to then get a key for each interaction or buy a
> physical key or have a phone (I have no phone service) to run an app
> on.  What am I doing wrong?
> 
> russell bell

I think you may still be at the verification stage to enable 2 factor 
authentication.  It appears you have to use one of the methods Google 
deems acceptable to assure them "you are you".

Once you get past that stage, you can then "go back to security" to 
request a key.  You can write it down or copy and paste what is provided 
as the key.

I confess I did not find the process "a piece of cake".

joe a.

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[<rb...@al...>]

	'Go to "Manage account". Select "Security" and enable 2 factor
authentication. One that is done go back to security to "App
passwords." Follow that process and get a key.'
	When I do that I don't get a key.  I have to give a phone
number to send a key to then get a key for each interaction or buy a
physical key or have a phone (I have no phone service) to run an app
on.  What am I doing wrong?

russell bell

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

On 6/12/2022 2:36 PM, Dennis Putnam wrote:
> I've just gone through the same thing. It turns out that OAuth2 is not 
> necessary. Log on to your google mail user and set up 2 factor 
> authentication. Go to "Manage account'. Select "Security" and enable 2 
> factor authentication. One that is done go back to security to "App 
> passwords." Follow that process and get a key. Use that key as the 
> password in your fetchmailrc and you will be good to go.
> 

Thanks, you've saved me a lot of investigative work! (apologies to Nick 
Danger)

joe a.

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

On 6/12/2022 6:54 PM, Matthias Andree wrote:
>. . . 
> But I did like the part of OAuth2 replacing 42 as the Google's answer to
> whatever will require me to have a towel handy. Which does not imply
> that the "OAuth2" answer were correct.
> 

Good to know I can still amuse now and then.  It is my only fault.  Or 
was that "among my only faults"?

Keep that towel handy!

joe a.

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

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

Am 12.06.22 um 19:41 schrieb joe a:
> A bit more digging shows anything below V7 may be fruitless to pursue.
> All I find on V7 on github confounds me as it seems to say the alpha
> code was withdrawn and I'd quickly be over my head.
>
> Searching the list archives turns up nothing,  Which for me is par for
> the course.

I have pulled the alpha tarballs since they'd constantly be outdated and
I don't care to release tarballs of that moving code -- people are
better off with updating the Git clone if they want to run the 7-alpha.

But I did like the part of OAuth2 replacing 42 as the Google's answer to
whatever will require me to have a towel handy. Which does not imply
that the "OAuth2" answer were correct.

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[Dennis P. <da...@be...>]

I've just gone through the same thing. It turns out that OAuth2 is not 
necessary. Log on to your google mail user and set up 2 factor 
authentication. Go to "Manage account'. Select "Security" and enable 2 
factor authentication. One that is done go back to security to "App 
passwords." Follow that process and get a key. Use that key as the 
password in your fetchmailrc and you will be good to go.

On 6/12/2022 1:41 PM, joe a wrote:
> A bit more digging shows anything below V7 may be fruitless to pursue. 
> All I find on V7 on github confounds me as it seems to say the alpha 
> code was withdrawn and I'd quickly be over my head.
>
> Searching the list archives turns up nothing,  Which for me is par for 
> the course.
>
> joe a.
>
> On 6/12/2022 11:58 AM, joe a wrote:
>> I've avoided this, until now, as things seemed to be "in flux" and 
>> the issue generating some ill will.
>>
>> Downloaded 6.4.30 in anticipation, but after some fruitless 
>> searching, I need to ask for the location for any current docs on 
>> configuring fetchmail with gmail.  OAuth2 is apparently google's 
>> answer to everything, overthrowing 42 as the reigning champion.
>>
>> Thanks for any assistance and understanding.
>>
>> joe a.
>>
>>
>> _______________________________________________
>> Fetchmail-users mailing list
>> Fet...@li...
>> https://lists.sourceforge.net/lists/listinfo/fetchmail-users
>
>
> _______________________________________________
> Fetchmail-users mailing list
> Fet...@li...
> https://lists.sourceforge.net/lists/listinfo/fetchmail-users

Re: [Fetchmail-users] Oauth, gmail, docs/guide?

[joe a <joe...@j4...>]

A bit more digging shows anything below V7 may be fruitless to pursue. 
All I find on V7 on github confounds me as it seems to say the alpha 
code was withdrawn and I'd quickly be over my head.

Searching the list archives turns up nothing,  Which for me is par for 
the course.

joe a.

On 6/12/2022 11:58 AM, joe a wrote:
> I've avoided this, until now, as things seemed to be "in flux" and the 
> issue generating some ill will.
> 
> Downloaded 6.4.30 in anticipation, but after some fruitless searching, I 
> need to ask for the location for any current docs on configuring 
> fetchmail with gmail.  OAuth2 is apparently google's answer to 
> everything, overthrowing 42 as the reigning champion.
> 
> Thanks for any assistance and understanding.
> 
> joe a.
> 
> 
> _______________________________________________
> Fetchmail-users mailing list
> Fet...@li...
> https://lists.sourceforge.net/lists/listinfo/fetchmail-users