Dennis Gorelik

1) Today (2020-05-04) my email client (The Bat 9.1.18 Professional) - lost ability to receive or send emails from our corporate @postjobfree.com email addresses [that G-suit handles for us].

The Bat started to return "Server reports error. The response is: 5.7.0":
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!2020-05-04, 06:18:43: SEND - Server reports error. The response is: 5.7.0 https://support.google.com/mail/?p=WantAuthError h188sm3660946qke.82 - gsmtp
2020-05-04, 06:18:43: SEND - connection finished - 0 message(s) sent
2020-05-04, 06:18:43: SEND - Some messages were not sent - check the log for details
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(Times are in EST)

2) The reason for this error is that Google [temporarily] stopped supporting "Less Secure Apps" in G-Suite (which we use to manage postjobfree.com emails).

3) This instruction: https://hotter.io/docs/email-accounts/secure-app-gmail/ is now obsolete.
"Less secure app access panel" no longer exists on https://myaccount.google.com/security page.

4) Actually, less secure access to Gmail works again, but, most likely, only temporary.
=======
https://gsuiteupdates.googleblog.com/2020/03/less-secure-app-turn-off-suspended.html
Last December, we announced that we’d be turning off less secure app (LSA) access to G Suite accounts, and that you should migrate to OAuth authentication instead. The first phase of the LSA turn-down was scheduled for June 15, 2020. As many organizations deal with the impact of COVID-19 and are now focused on supporting a remote workforce, we want to minimize potential disruptions for customers unable to complete migrations in this timeframe.
As a result, we are suspending the LSA turn-off until further notice. All previously announced timeframes no longer apply.
...
Despite these timing adjustments, Google does not recommend the use of any application that does not support OAuth.
=======

5) This is the fix for this The Bat - Gmail issue:
~~~~~~~~~~~~~
https://www.ritlabs.com/en/news/6777/
To configure OAuth for existing Gmail or Mail.Ru accounts in The Bat!, users should access the "Account -> Properties -> Transport -> Receive mail -> Authentication" menu, enable "OAUTH (using Web Browser)" and save changes. The Bat! will remove the password from the account and apply the modern authentication mechanism to send and receive messages.
~~~~~~~~~~~~~

Click "Authentication":


Switch from "Regular" to "OAUTH (using Web Browser)":


6) The Bat works again.

7) The next step - is to switch our PostJobFreeService C# code that works with Gmail over [secure] Smtp/Pop3 to OAuth.

Several years ago I created Gmail account for my daughter.
A year later she signed up for infamous Google+.
Google+ asked my daughter for her birthday and permanently deleted her account based on age.

I thought it would be possible to recreate her Gmail account again, but unfortunately Google does not allow login or create new account.
When I try to recover that account, Google says: This account was deleted and is no longer recoverable.



Multiple forums discussed this, but the bottom line is:
---
If you get the error the account is deleted and no longer recoverable; then you have to create new account with different username.
Gmail never recycle the old username.
---
Why would Google setup such a strict policy? Why not allow reusing old usernames after a year of account being deleted?