Now that May 30th has come and gone, and we are all still able to access Gmail using app-specific passwords, don't you think it's overdue for you to retract your prior comments about the necessity to use OAuth2 to access Gmail?

There was ample evidence that OAuth2 was not going to be required, and yet your comments on this subject appear to have ignored all evidence to the contrary. Your continued silence, after May 30th, deserve to be clarified asap. Thanks.

Maybe you should reconsider your claim a little bit when taking into account what Edward posted here - just for the convenience of everyone I'm quoting it below:

For companies or organizations that have outsourced mail to and form their domains to Google, 2-factor authentication is an option they can enable or disable at the domain level. Especially with large organizations, individual users may not have enough clout to persuade their domain administrator to enable this option just so they can use pmail or other email clients.

And he's got himself as a sample case as you can tell by a subsequent post of him in the same thread.

I think Pavarotti is optimistic. My gmail "glitched" one morning, then became OK later. Today, it stopped. NOT a non-issue. Here is my info in it, which I will also post under my prior entry. Trying to help folks get their email.

David et al, feel free to use any of it in a post of updates.

I am a long-time Pegasus Mail user and I really like the program. Thanks, David Harris! And helpers!

Learning that gmail was making authorization changes is a big deal to me, so I looked at PMail for info.

David Harris said he was making changes to cover OAUTH2. Then he said Google was demanding large fees, and he couldn't pay them. (rightly so!) Then he updated with, maybe those fees won't be required, but he can't decipher Google's requirements.

Google said changes were as of May 30, but my email gmail access stopped working on June 7 (today).

Info on the Pegasus Community site by Brain F pointed me to a solution - Pegasus does NOT have to be updated to still work with gmail! Procedures below get around this problem.

It isn't easy, as it has many steps. Google help has good info, but also too much info! 2-Step verification: https://support.google.com/accounts/answer/185839

I believe that a phone or other is required for initial 2-step verification, but after that Pegasus on a computer should work like normal. NOT needed to phone verify every time.

Here are the steps, in summary. Per my notes.

Login to gmail, with email and password.
On the left side, select Security. Scroll on the right and verify that you have a valid recovery phone number for texts. (Calls MIGHT work.)
Find the Signing in to Google section.
Under that, choose 2-step Verification.
Again enter your password.
See your phone number and select Continue.
Select text or call and choose SEND.
Get a text with confirmation number, then enter that number on the Google page asking for it.
Google may show devices that it expects to connect with.
Now you need an App Password for your email program, Pegasus.
At Google, Security on the left side.
In the section on the right, Signing in to Google, click on the App Password line.
Again put in your password.
Then, select the App for which you want the password, either Email from the list or choose custom and put in Pegasus or whatever. Then click on Generate.
A 16-digit will be posted. COPY it!
Then go to your Pegasus email. Tools-Internet Options
Receiving and Sending tabs and REPLACE your former password with the new 16-digit one just received.
Done. Send and receive as before this change.

Good luck!

David has made explicit statements to the effect that OAuth2 would be required after May 30. He has yet to acknowledge the various discusions here that first suggested, and then confirmed that this is definitely not the case.

David does not have anything to explain. His goal should be to insure Pegasus Mail works for everyone. Goggle's requirement of OAuth2 will break Pegasus Mail for some users as Michael referenced. The fact that the app password workaround works for some of us is irrelevant to David's goal.

I would like to thank RichU for giving us instructions on how to use Pegasus GMail, overcoming the OAUTH2 barrier. My email was barred earlier today, i visited this site, and applied the solution, which worked perfectly. many thanks, John Meehan

Brian, David has implied (if not explicitly stated) that OAuth would be required by all users. There was not any ambiguity in his updates. I don't believe that app-specific passwords are a "workaround", and I don't believe that Google actually stated that OAuth2 would be required (although it's true that they didn't try hard to remove any ambiguity).

As to the local administrator "case" where 2FA might not be available, has this been confirmed, or is it possible that this is also incorrect? 2FA is something that Google obviously wants to push, so I'd be surprised if they allowed some sites to block it.

David obviously has limited resources to invest in Pegasus, and again he's stated that OAuth2 took him several hundred hours that he didn't want to spend. We live in a world where David doesn't seem to know about app-specific passwords. I'm not asking David to apologize, I requested that he clarify the OAuth2 situation. His latest post has good news, but doesn't address this question. Your statement that he has nothing to explain is very supportive, but I'm not sure that even you believe it.

I am also a long-time Pegasus Mail user and my Gmail access stopped 2 days ago. So, I would like to thank RichU for giving us instructions on how to configure my GMail account for use with Pegasus. I am now able to use Pegasus again. BTW, I initially could not find the Gmail security section. So if you experience the same, just log on to: https://myaccount.google.com/ and follow RichU's instructions.