Is your email notification working?
-
http://serverfault.com/questions/635139/how-to-fix-send-mail-authorization-failed-534-5-7-14
There is an answer there… Not sure if it will work for you.
-
@hda:
Dunno. Maybe in header info from the SSL ?
I won't test… Try smtps again after test with 25 and/or 587 ?But, smtps 465 seems a depriciated method. Go for 587 if you must avoid 25.
Changed to port 587 and now I'm getting:
Feb 25 16:59:32 php-fpm[5995]: /system_advanced_notifications.php: Could not send the message to myusername@gmail.com -- Error: could not connect to the host "smtp.gmail.com": ?? -
Change back and try the solution in the link I sent previously.
-
The better supported receiver method is just port 25 with or without STARTTLS
-
Sending on port 25 may probably be a ISP nightmare depending on who you ISP is.
-
Oh, then the best method for the future is submission, 587 :D
-
perhaps, but mine is set up same as his with no problems. Quite odd.
-
Usually when I install new piece of hardware that supports email notifications I create for that specific customer new gmail account for notifications use only. Many times I need to do this to get it working properly
https://support.google.com/accounts/answer/6010255?hl=en
It's more reliable to use port 587 then 465. Many devices still do not support SSL.
-
kejianshi you are the man!
Its working now!
As suggested in that post, went to www.google.com/settings/security
and "Access for less secure apps" was turned off, turned it on and voila started working right away.
I searched google but never came across this setting.Thanks again!
-
I did something right? Must be my lucky day…
-
I did something right? Must be my lucky day…
You did a right thing by posting that link ;)
-
Usually when I install new piece of hardware that supports email notifications I create for that specific customer new gmail account for notifications use only. Many times I need to do this to get it working properly
https://support.google.com/accounts/answer/6010255?hl=en
It's more reliable to use port 587 then 465. Many devices still do not support SSL.
Thanks!
-
The solution does not work if u have enabled "two-factor-authentification" (so we did) in your Google-Apps-account. The "apps-password" we have generated do not work, showing "Error: 535-5.7.8 Username and Password not accepted.".
We tried several different generated apps-passwords, no luck.
Any hints?
-
Don't use two factor authentication?
-
The solution does not work if u have enabled "two-factor-authentification" (so we did) in your Google-Apps-account. The "apps-password" we have generated do not work, showing "Error: 535-5.7.8 Username and Password not accepted.".
We tried several different generated apps-passwords, no luck.
Any hints?
Have you tried setting up relay instances? There are limitations if you're on a dynamic IP, but they work well.
-
The solution does not work if u have enabled "two-factor-authentification" (so we did) in your Google-Apps-account. The "apps-password" we have generated do not work, showing "Error: 535-5.7.8 Username and Password not accepted.".
We tried several different generated apps-passwords, no luck.
Any hints?
Hi
I also have two factor authentication enabled but unable to send email.
I disabled it and enabled access to less secure apps now while m able to relay emails but all are landing in my Gmail address not in mailbox which I specified in Notification E-Mail address. No email is being sent there. I tried multiple addresses.
