May Sale! All accounts are 40% off this week.
I'm getting this error when I hit submit on my contact form
Failed to authenticate on SMTP server with username "[email protected]" using 2 possible authenticators.
Authenticator LOGIN returned Expected response code 235 but got code "535", with message "535 Incorrect authentication data ".
Authenticator PLAIN returned Expected response code 235 but got code "535", with message "535 Incorrect authentication data ".
As far as I know all my details is corrected and my cpanel php is 7.3.
On my live site the contact form works correctly, but on my localhost I'm getting the above mentioned error. I used mailtrap to test out my contact form and that worked as well.
I can't understand why I'm getting this error when those details is working fine on my live site.
this is my .env
MAIL_DRIVER=smtp
MAIL_HOST=mail.domain.com
MAIL_PORT=587
[email protected]
MAIL_PASSWORD=password
MAIL_ENCRYPTION=null
In general you need an SMTP server to send emails through SMTP. Your local environment doesn't have this default. You can use alternative tools like mailhog to catch the SMTP calls and watch the email in there.
So locally using SMTP is always an issue :P
If your mail server password contains a # then you should quote the environment string since everything after # will be taken as comment (starting in Laravel 5.8)
@snapey Take a lots of love brother.....It's worked successfully Alhamdulillah
I loooooooooooooove you, 4hours i was trying to fix, get headache of that. thanks dear
@Snapey But my own password doesn't even contain # so what is the issue when all the smtp credentials are correct and it still throws in this error
@Snapey thank you very much
@Snapey Thanks, faced the same error now, I had a # in my mail server password, I had to quote it and solve the error
@SNAPEY - Thank you so much. That worked I did have a # in my password
@snapey You saved my day) thanks
Another one that you saved the day. Thank you so much, @snapey !
Could you please show me where to find the # mentioned in this thread? thank you so much! I am an amateur!
@phuthao you might not have one. It is saying that if your secrets in .env contain # then you must quote the string eg;
MAIL_PASSWORD = r39304#d^fd
The # marks the start of a comment, so the password ends up being 'r39304'
The solution;
MAIL_PASSWORD = "r39304#d^fd"
@Snapey Thanks Bro
@snapey I'm so glad I came across this solution. My password actually started with #. Thank you soooo much.
I am facing issue with mail and trying to solve issue for past three days
MAIL_DRIVER=smtp MAIL_HOST=smtp.gmail.com MAIL_PORT=587 MAIL_USERNAME=bhupendratiwari675@gmail.com MAIL_PASSWORD="appPassword" # Generated from google app Password MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=bhupendratiwari675@gmail.com
Please help
{ "exception": "[object] (Symfony\Component\Mailer\Exception\TransportException(code: 535): Failed to authenticate on SMTP server with username "[email protected]" using the following authenticators: "LOGIN", "PLAIN", "XOAUTH2". Authenticator "LOGIN" returned "Expected response code "235" but got code "454", with message "454-4.7.0 Too many login attempts, please try again later. For more information,
454-4.7.0 go to
454 4.7.0 ". Authenticator "PLAIN" returned "Expected response code "235" but got empty code.". Authenticator "XOAUTH2" returned "Expected response code "235" but got empty code.". at /var/www/html/pedms/vendor/symfony/mailer/Transport/Smtp/EsmtpTransport.php:212) I am getting this error and i am using gmail smtp for sending mails
@292marxist have you enabled less secure apps in your google settings?
@Snapey Is that needed to be done for this issue because this issue is only occurring sometimes in my system not all the time
@292marxist why dont you start your own question and put the correct information in it?
@snapey Hey... any idea what's wrong here?
'smtp' => [
'transport' => 'smtp',
'driver' => 'smtp',
'host' => 'smtp.gmail.com',
'port' => 465,
'encryption' => 'ssl',
'username' => <username>,
'password' => <pass>,
'timeout' => null,
'auth_mode' => null,
'verify_peer' => false,
'verify_peer_name' => false,
'allow_self_signed' => true,
'options' => [
'ssl' => [
'verify_peer' => false,
'verify_peer_name' => false,
'allow_self_signed' => true,
'security_level' => 0,
'peer_name' => 'smtp.gmail.com'
]
],
MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=465
MAIL_USERNAME=
MAIL_PASSWORD=
MAIL_ENCRYPTION=ssl
running these on cPanel terminal:
$ php artisan tinker
Psy Shell v0.12.7 (PHP 8.2.25 — cli) by Justin Hileman
Mail::raw('Test email', function($message) { $message->to('[email protected]')->subject('Test'); });
Symfony\Component\Mailer\Exception\TransportException Failed to authenticate on SMTP server with username "[email protected]" using the following authenticators: "LOGIN", "PLAIN". Authenticator "LOGIN" returned "Expected response code "235" but got code "535", with message "535 Incorrect authentication data".". Authenticator "PLAIN" returned "Expected response code "235" but got code "535", with message "535 Incorrect authentication data".".
Note: I've got the 16-digit app password for the email address and use it without any spaces in the config>mail file
P.S. excuse the messy format...
MAIL_MAILER=smtp
MAIL_HOST=smtp.gmail.com
MAIL_PORT=587
[email protected]
MAIL_PASSWORD="your gmail pass here"
MAIL_ENCRYPTION=plain #"Be careful here, make sure to put plain"
MAIL_FROM_ADDRESS="[email protected]"
MAIL_FROM_NAME="${APP_NAME}"
Failed to authenticate on SMTP server with username [email protected] using the following authenticators: LOGIN , PLAIN . Authenticator LOGIN returned Expected response code 235 but got code 535 , with message 535 5.7.8 Error: authentication failed: (reason unavailable) . . Authenticator PLAIN returned Expected response code 235 but got code 535 , with message 535 5.7.8 Error: authentication failed: (reason unavailable) . .
none of these works for me. I think laravel should improve on this. There seems to be no consistency with this error and a clear explanation on what the cause is.
@Gemley If you're having SMTP connection issues, it probably has nothing to do with Laravel. You should make a separate thread and explain your issues there (with full error messages).
This thread is 5 years old and marked as solved.
Please or to participate in this conversation.