-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gmail API not working anymore #1431
Comments
yep can confirm this |
gg |
Yes can confirm also from my side. |
I wonder if there's a way to run a headless browser, and go to Gmail's password recovery page https://accounts.google.com/signin/v2/usernamerecovery. Use the headless browser to input the email to verify, and hopefully with the messages that Gmail returns, we can know its existence. Similarly to how we currently do for hotmail. |
tried that method |
Did quick research and there "kind of" is alternative but it requires your cookie and additional token. Look for |
Nah, not good at all...
…On Fri, Mar 1, 2024, 3:50 PM er ***@***.***> wrote:
Yes can confirm also from my side. In my experience SMTP is very
unreliable, are there any other methods that can be used for Gmail ?
Did quick research and there "kind of" is alternative but it requires your
cookie and additional token. Look for
https://people-pa.clients6.google.com url in Github. This is an endpoint
where google checks if account is with them. Previously it was
https://mail.google.com/mail/gxlu
—
Reply to this email directly, view it on GitHub
<#1431 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABDLT27ESUXK7Z2KC6A7I4DYWB2PTAVCNFSM6AAAAABB4RZ2KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZTGEZTSMJZGY>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Email to check
[email protected]
From where did you run check-if-email-exists?
anywhere, even local machine
Version of check-if-email-exists (if running it yourself)
8e79884
What happened?
We added the ability to verify Gmail addresses using an API (instead of a SMTP connection): #1193.
However, since a couple of days ago, this seems to have stopped working. Maybe Gmail changed something on their side. Emails that used to be
safe
now returninvalid
. You can try with[email protected]
for example.Relevant log output
No response
The text was updated successfully, but these errors were encountered: