-
Notifications
You must be signed in to change notification settings - Fork 24
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
send-email component of github action is failing #64
Comments
When you fix this, we won't need to manually send the email anymore, so remove step 6 from here: https://github.com/w3c-ccg/w3c-ccg.github.io/blob/master/publish_minutes.md |
Is 2FA turned on with the new ownership of the gmail account? If so, that's the issue (it has to be turned off)... but, I'm pretty sure you've probably already looked into that. https://github.com/marketplace/actions/send-email#gmail Looks like we're using this to send email in the Github Action: |
I tried it with 2FA, and it also didn't work, so I disabled it and it also didn't work. I made sure the password env var was up to date, and still no luck |
Looking at this again. The error continues to be an authentication error. I don't have access to the repo's secrets or the gmail account but a reference is here to walk through in case a step was missed before: https://github.com/marketplace/actions/send-email |
I updated the account info by adding a username and updating the password and secrets but still got this error: 535-5.7.8 Username and Password not accepted. But afterwards I noticed the troubleshooting at this bottom of this: https://github.com/marketplace/actions/send-email So I enabled "Less secure app" and turned on IMAP in the email settings. Hopefully it works for the next person who publishes minutes. |
Look at Action logs in the week of 6/22-25 for failure messages. Essentially we can no longer send through the w3c-ccg gmail account, and it broke when we switched over ownership of the account. We need someone to investigate and fix
The text was updated successfully, but these errors were encountered: