I am trying to use Google's SMTP server to send emails from my Laravel 7.x application.
The config settings I am using are copied from my other working Laravel apps (with credentials changed).
My Gsuite account has 2-step verification enabled and I am using application password in my .ENV file.
Somehow though, I am getting the following error every time:
Failed to authenticate on SMTP server with username "hello#xxxxx.com" using 3 possible
authenticators. Authenticator LOGIN returned Expected response code 235 but got code "535", with
message "535-5.7.8 Username and Password not accepted. Learn more at 535 5.7.8
https://support.google.com/mail/?p=BadCredentials gb19sm28030pjb.38 - gsmtp ". Authenticator PLAIN
returned Expected response code 235 but got code "535", with message "535-5.7.8 Username and
Password not accepted. Learn more at 535 5.7.8 https://support.google.com/mail/?p=BadCredentials
gb19sm28030pjb.38 - gsmtp ". Authenticator XOAUTH2 returned Expected response code 250 but got code
"535", with message "535-5.7.8 Username and Password not accepted. Learn more at 535 5.7.8
https://support.google.com/mail/?p=BadCredentials gb19sm28030pjb.38 - gsmtp ".
My .env entries look like this:
MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
MAIL_USERNAME=hello#xxxx.com
MAIL_PASSWORD=hqubwafijjkkvexnah
MAIL_ENCRYPTION=tls
Issue is with Goog;le's smtp because when I point to mailtrap instead, everything works fine.
I managed to solve this by changing Less Secure Apps to On and also, turning 2-Step verification off. But I do not think this is the approach I would like to go with, in the long term.
For now, this stands solved.
Related
response=421 4.7.0 Try again later, closing connection. (EHLO) vj23-20020a170907131700b0078db51bb303sm9553ejb.86 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) vj23-20020a170907131700b0078db51bb303sm9553ejb.86 - gsmtp Error: Server terminates connection. response=421 4.7.0 Try again later, closing connection. (EHLO) vj23-20020a170907131700b0078db51bb303sm9553ejb.86 - gsmtp: 421 4.7.0 Try again later, closing connection. (EHLO) vj23-20020a170907131700b0078db51bb303sm9553ejb.86 - gsmtp
I found a solution I hope it will help you I replaced nodemailer Smtp by emailjs and this will solve the problem.
https://www.npmjs.com/package/emailjs
I believe Nodemailer uses the computer's hostname in place of the name property when creating a transport. This can cause issues with some email relays such as Gmail. To fix this you can explicitly set the name property in the SMTP transport options to an arbitrary string.
I'm trying to use the Docusign API for an application that I'm running locally and I see the following error:
"message":"Uncaught Error when executing a Single
Cause: com.docusign.esign.client.ApiException: Error while
requesting server, received a non successful HTTP code 400 with response Body:
'{"errorCode":"HTTPS_REQUIRED_FOR_CONNECT_LISTENER",
"message":"HTTPS required for Connect listener communication."}'
Description: com.docusign.esign.client.ApiException: Error while
requesting server, received a non successful HTTP code 400 with response Body:
'{"errorCode":"HTTPS_REQUIRED_FOR_CONNECT_LISTENER",
"message":"HTTPS required for Connect listener communication."}
I am behind a company proxy but I have been able to use the API in the past and create envelopes without an issue so I'm not sure how to address this. Any help would be greatly appreciated.
This change is discussed in the Jan release notes.
Connect can only be used with https listeners (customers' servers).
And note that the server must use a certificate that chains to a root cert in the Microsoft standard root cert list. (Self-signed certs won't work.) You can use a free cert from LetsEncrypt or a $15 cert from a reputable CA.
I'm sorry that this update caught you by surprise.
Getting error now, it was working fine before:
Fatal error: Uncaught DocuSign\eSign\Client\ApiException: Error while requesting server, received a non successful HTTP code [400] with response Body: O:8:"stdClass":2:{s:9:"errorCode";s:35:"HTTPS_REQUIRED_FOR_CONNECT_LISTENER";s:7:"message";s:50:"HTTPS required for Connect listener communication.";}
I am trying to create a script that will run commands over my 1000 Cisco devices.
The device model is: Cisco Sx220 Series Switch Software, Version 1.1.4.1
The issue is that there is some kind of strange behavior for some of those Cisco devices.
When I am trying to login with regular SSH (PUTTY) with the correct credentials we are first getting 'Authentication Failure' and after 1 seconds I am getting the User Password Prompt again, typing the same credentials again is giving me a successful login.
The problem is that when I am trying to connect using my script (uses ParallelSSHClient), the connection drops after getting the authentication failure message and not able to enter the credentials again since it is getting the exception and terminal the program.
I am looking for a way to enter those credentials manual by connecting to the machine, getting the Authentication Failure message and ignoring it, recognizing that the current prompt has the User or Password appears on screen and then send it manually.
I look for this kind of procedure anywhere but without any luck.
Does ParallelSSHClient has this feature?
If Paramiko has it, I am willing to move to Paramiko.
Thanks :)
try:
client = ParallelSSHClient(hosts=ip_list, user=user, password=password)
except Exception as err:
print("There was an issue with connecting to the machine")
command_output = client.run_command(command)
Here is the accrual error that I am getting:
pssh.exceptions.AuthenticationException: ('Authentication error while connecting to %s:%s - %s', '172.31.255.10', 22, AuthenticationException('Password authentication failed',))
How can I use from a VM (linux) where a Java application is running a SMTP Server/relay?
For connecting to SMTP I want to use an O365 account, so configuration looks like:
host: smtp.office365.com
port: 587
TLS: true
uid: UID-O365
pwd: PWD-O365
As response I get:
An error has occurred with sending the test email:
MailException: com.sun.mail.smtp.SMTPSendFailedException:
501 5.1.7 Invalid address [AM4P190MB0211.EURP190.PROD.OUTLOOK.COM]
;
nested exception is:
com.sun.mail.smtp.SMTPSenderFailedException: 501 5.1.7 Invalid address
[AM4P190MB0211.EURP190.PROD.OUTLOOK.COM]
remark: The application that wants to connect runs on java, what is probably unimportant
The server is telling you that the address "AM4P190MB0211.EURP190.PROD.OUTLOOK.COM" that you're using in your message as a sender or recipient address is not a valid email address. It at least needs a "#" in there somewhere. You can get more detail in the JavaMail debug output.
The solution is simple: sender email address (what was not listed above) and UID must be the same
I am a newby who purchased a reskin app and I'm having problems when trying to get the ads to pop up while in Xcode 7 testing on my iphone. I followed the steps to enter the token and secret ID codes after registering the app in playhaven but I keep getting the below error when running the test on Xcode in the debug area.
Stackoverflow is my last resort as the guy who sold me the app can't help...
Playhaven-1.24.0 Request received HTTP response: 403
Playhaven-1.24.0 Request finished
Playhaven-1.24.0 Server response
errorbj - null
error - 403 Forbidden
response - invalid signature
I have tried the new SDK but get more errors/bugs
Please help me
Thanks so much
Andy
Seems like playhavens end doesnt communicate with my account and token codes etc, same with Startapp!