Skip to content
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

Add FAQ entry for Gmail suspicious sign-on blocks #201

Open
iandunn opened this issue Aug 14, 2014 · 6 comments · May be fixed by #216
Open

Add FAQ entry for Gmail suspicious sign-on blocks #201

iandunn opened this issue Aug 14, 2014 · 6 comments · May be fixed by #216

Comments

@iandunn
Copy link
Contributor

iandunn commented Aug 14, 2014

Sometimes Gmail blocks connections from SupportFlow because it think they're suspicious.

https://support.google.com/accounts/answer/6063333?hl=en

We should have a FAQ entry to alert users to this possibility, to help them troubleshoot.

@iandunn
Copy link
Contributor Author

iandunn commented Aug 14, 2014

Users should be instructed to sign in to their account and mark the activity as legitimate, and to also try the unlock CAPTCHA at www.google.com/accounts/DisplayUnlockCaptcha

@VarunAgw VarunAgw linked a pull request Aug 16, 2014 that will close this issue
@VarunAgw
Copy link
Contributor

Users should be instructed to sign in to their account and mark the activity as legitimate, and to also try the unlock CAPTCHA at www.google.com/accounts/DisplayUnlockCaptcha

https://support.google.com/accounts/answer/2461835?hl=en

I think it is not case with SupportFlow. I think if google think IP is suspicious it then expect user to visit the link with same IP (device) and enter the captcha. But in case of supportflow, there is no device. Also SupportFlow IP will be different from user IP. So unlock might not work

@iandunn
Copy link
Contributor Author

iandunn commented Aug 19, 2014

I'm not 100% sure, but I think it will, I've had to do it before. Their documentation doesn't make it clear, though.

@iandunn
Copy link
Contributor Author

iandunn commented Dec 29, 2014

For future reference, this article may also be helpful: https://support.google.com/mail/answer/14257?p=client_login&rd=1

@iandunn
Copy link
Contributor Author

iandunn commented Nov 20, 2015

We should also say that sometimes they put temporary blocks in place that you can't remove with any of their support tools, and you just have to wait until the next day.

@iandunn
Copy link
Contributor Author

iandunn commented Nov 20, 2015

Rather than making this a FAQ, it should be an admin notice when we detect a failure adding a Gmail account. That way people don't have to go hunting for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants