Also I try with the secureConnection=true or false and with port 465 or 587. On all cases the error was:
Failed to send email. Reason: Invalid login - 535-5.7.8 Username and Password not accepted. Learn more at 535 5.7.8 https://support.google.com/mail/?p=BadCredentials e6sm1879051qkg.89 - gsmtp.
I use the above settings for gitlab on my own server and all works ok…
any help appreciated…
Same error for me (Failed to send email. Reason: Invalid login - 535 Authentication failed: Bad username / password.)
I’m using GHOST 2.37.0 On Azure App Service (Windows)
Config added to config.production.json
“mail”: {
“transport”: “SMTP”,
“from”: “‘my email’ av8or@email.com”,
“options”: {
“service”: “Gmail”,
“auth”: {
“user”: “av8or@gmail.com”,
“pass”: “P@ssowrd”
}
}
},
Set the gmail to “allow less secure”
No, the password is ok. Also I tried to use the configuration with another software with smtp and It works ok, so the problem is with ghost or ghost in docker…
I had some fun with this a while ago. I managed to get it working in the end with a custom domain in GSuite, not a Gmail account. But it should be very similar.
The config in your config.*.json file should look something like this.
In your Gmail or GSuite account, log into the account, go to My Account, Security, App Passwords. Create an app password (bypasses 2 Step Verification if it is setup) then try sending an email from Ghost.
Please note: When you send an email for the first time it may be blocked. Check for a blocked email in your Google account to “approve” Ghost sending the email. You should then be free to send any emails once you have approved it.
Hello. So, I’m new to Ghost. Just recently got it set up using the DO OCA. It was working fine except email. I found this and edited my config.*.json file. I wasn’t thinking and I tried to restart Ghost from root. Obviously, it told me I could not do that, but it still executed. Now I’m getting a 502 error. Any help on fixing it?
This is how I got it working on my self-hosted Ghost using a custom domain with SMTP going to Google. And bonus points, it uses a one-time password instead of dumping my credentials on a file somewhere for the hackerz to find.
I tried with the TLS settings and secure: true but ended up getting OpenSSL version errors.