-
Notifications
You must be signed in to change notification settings - Fork 29
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 setup stopped working after the update #185
Comments
What version did you update from? |
The previous one 4.0.4. I also tried sending email with Gmail using CLI test command. Same situation. |
I get this same error trying to utilize gmail. Not sure if I've ever had it working as it's been a while but the setup seems simple enough, and save's fine, but get this. edit: version 4.1.1 |
Did you see this note in the README:
Are you using an App password? |
FYI, I just tested this with an app password and it worked fine. I had to set my 'from address' to the same google account I was using to login with, and also Google gave me an app password like this: |
Yes, I have been using an app password via 2 factor authentication settings. Hey! The spaces were the key. I would have never expected to have to modify the password they gave me. I do see your note now in the docs (not sure if I initially missed it of if you added it). When I first tried removing the spaces I pasted into another field and cleared them out, but also managed to get an extra space at the end which obviously failed. Long story short, double triple check the app password is just the characters from google and no extra spaces! Thanks for your time on this. |
I had a setup for the gmail smtp, like so:
It was working fine for my both sites (I have a multisite setup) until the most recent update to 4.1.0. version. Now, it is logging this error:
I have tested the same credentials with phpMailer in a separate script, and it works no problem. This plugin (for me, at least) only works with Outlook currently, but not with Gmail.
The text was updated successfully, but these errors were encountered: