SMTP Error: Could not authenticate.

  • Resolved chrdol72

    (@chrdol72)


    3 years, 4 months ago

    Hello,

    Users are currently receiving bounced back emails when attempting to reset passwords. I am unable to send a test email and receive the following error log: 

    Versions:
WordPress: 6.1.1
WordPress MS: No
PHP: 7.4.33
WP Mail SMTP: 3.7.0

Params:
Mailer: smtp
Constants: Yes
ErrorInfo: SMTP Error: Could not authenticate.
Host: c30456.sgvps.net
Port: 587
SMTPSecure: tls
SMTPAutoTLS: bool(true)
SMTPAuth: bool(true)

Server:
OpenSSL: OpenSSL 1.1.1q 5 Jul 2022

Debug:
Email Source: WP Core

Mailer: Other SMTP

SMTP Error: Could not authenticate.
Email Source: Ultimate Member

Mailer: Other SMTP

SMTP Error: Could not authenticate.
Email Source: Sucuri Security - Auditing, Malware Scanner and Hardening

Mailer: Other SMTP

SMTP Error: Could not authenticate.
Email Source: WP Mail SMTP

Mailer: Other SMTP

SMTP Error: Could not authenticate.

SMTP Debug:
2023-01-18 11:41:03 Connection: opening to c30456.sgvps.net:587, timeout=300, options=array()

2023-01-18 11:41:03 Connection: opened

2023-01-18 11:41:03 SERVER -> CLIENT: 220-c30456.sgvps.net ESMTP #2 Wed, 18 Jan 2023 11:41:03 +0000 220-We do not authorize the use of this system to transport unsolicited, 220 and/or bulk e-mail.

2023-01-18 11:41:03 CLIENT -> SERVER: EHLO frslearn.com

2023-01-18 11:41:03 SERVER -> CLIENT: 250-c30456.sgvps.net Hello frslearn.com [127.0.0.1]250-SIZE 52428800250-8BITMIME250-DSN250-VRFY250-AUTH LOGIN PLAIN250-STARTTLS250 HELP

2023-01-18 11:41:03 CLIENT -> SERVER: STARTTLS

2023-01-18 11:41:03 SERVER -> CLIENT: 220 TLS go ahead

2023-01-18 11:41:03 CLIENT -> SERVER: EHLO frslearn.com

2023-01-18 11:41:03 SERVER -> CLIENT: 250-c30456.sgvps.net Hello frslearn.com [127.0.0.1]250-SIZE 52428800250-8BITMIME250-DSN250-VRFY250-AUTH LOGIN PLAIN250 HELP

2023-01-18 11:41:03 CLIENT -> SERVER: AUTH LOGIN

2023-01-18 11:41:03 SERVER -> CLIENT: 334 VXNlcm5hbWU6

2023-01-18 11:41:03 CLIENT -> SERVER: [credentials hidden]



2023-01-18 11:41:03 SERVER -> CLIENT: 334 UGFzc3dvcmQ6



2023-01-18 11:41:03 CLIENT -> SERVER: [credentials hidden]



2023-01-18 11:41:05 SERVER -> CLIENT: 535 Incorrect authentication data

2023-01-18 11:41:05 SMTP ERROR: Password command failed: 535 Incorrect authentication data

SMTP Error: Could not authenticate.

2023-01-18 11:41:05 CLIENT -> SERVER: QUIT

2023-01-18 11:41:05 SERVER -> CLIENT: 221 c30456.sgvps.net closing connection

2023-01-18 11:41:05 Connection: closed

SMTP Error: Could not authenticate.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Dake

    (@dakeg)

    3 years, 4 months ago

    Hi @chrdol72

    Thanks for reaching out and we’re sorry to hear that you’re experiencing issues with the Other SMTP mailer.

    I looked through the log that you shared and I noticed these reasons:

    • “Could not authenticate.”
    • “We do not authorize the use of this system to transport unsolicited, 220, and/or bulk e-mail.”
    • Password command failed: 535 Incorrect authentication data

    These SMTP errors indicate that your web server isn’t able to connect to the SMTP server.

    Please, recheck your SMTP credentials with your SMTP provider.

    Also, there could be a firewall between your web server and the SMTP server. When you get a chance, could you please contact your web hosting support and ask them to look into the issue? You can provide them with the SMTP settings you’re using and this SMTP log. They should be able to figure out the issue.

    Alternatively, we recommend setting up other available mailers instead of using “Other SMTP”. The “Other SMTP” mailer does not use a dedicated API, which can lead to potential errors based on your website hosting settings.

    Transactional Mailers

    Transactional email service providers such as our #1 recommended mailer, SendLayer (https://a.supportally.com/G1oPX3), are perfect for sending emails from your WordPress site. If it’s contact form notifications or e-commerce emails, they will deliver them quickly and reliably. 

    Sendinblue, SMTP.com, SendGrid, and Mailgun are also transactional email service providers if you’d like to consider your options.

    Transactional mailers also allow you to send emails with custom ‘From Email’ specific to your domain (examples: [email protected], [email protected]).

    If you’d like to check out more details on the mailers mentioned above or any others you may be interested in, you can see our complete guide here: https://wpmailsmtp.com/docs/a-complete-guide-to-wp-mail-smtp-mailers/.

    I hope this helps 🙂

    Thread Starter chrdol72

    (@chrdol72)

    3 years, 4 months ago

    Thank you, what is the difference between the transactional mailer and the SMTP ones?

    Plugin Support Dake

    (@dakeg)

    3 years, 4 months ago

    Hi @chrdol72

    They are all using SMTP, but transactional mailers are specifically designed for what we call transactional emails. For example:

    • Password reset emails
    • Account creation emails
    • Welcome emails
    • Shipping confirmations
    • Payment invoices
    • Purchase receipts
    • Order confirmation emails
    • Payment failure notifications

    So if those are the type of emails you intend to send and not bulk emails like newsletters and marketing emails etc, then we generally recommend looking into a transactional mailer.

    I hope this helps 🙂

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘SMTP Error: Could not authenticate.’ is closed to new replies.