Mail not send

Viewing 4 replies - 1 through 4 (of 4 total)
  • Sanjeev Aryal

    (@sanzeeb3)

    5 years, 5 months ago

    Hi @kaizur-ahmed,

    Thanks for the details. Please share the full error log after sending test email, here’s the screenshot to get full error log. If might need to use App password instead of your regular Gmail account password, this is especially required if your account has a two-factor authentication enabled. If you haven’t already, try with TLS encryption with port 587.

    Thanks!

    • This reply was modified 5 years, 5 months ago by Sanjeev Aryal.
    Thread Starter Kaizur Ahmed

    (@kaizur-ahmed)

    5 years, 5 months ago

    Hi Sanjeev Aryal,

    Thanks for your reply. I have no two-factor authentication enabled. That’s why I tried with TLS encryption with port 587. But the same case happened.

    Error Log:
    Versions:
    WordPress: 5.5.3
    WordPress MS: No
    PHP: 7.4.13
    WP Mail SMTP: 2.5.1

    Params:
    Mailer: smtp
    Constants: No
    ErrorInfo: SMTP Error: Could not authenticate.
    Host: smtp.gmail.com
    Port: 587
    SMTPSecure: tls
    SMTPAutoTLS: bool(true)
    SMTPAuth: bool(true)

    Server:
    OpenSSL: OpenSSL 1.1.1d 10 Sep 2019
    Apache.mod_security: No

    Debug:
    Mailer: Other SMTP
    SMTP Error: Could not authenticate.

    SMTP Debug:
    2021-01-04 10:43:36 Connection: opening to smtp.gmail.com:587, timeout=300, options=array()

    2021-01-04 10:43:36 Connection: opened

    2021-01-04 10:43:37 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP 193sm54756530pfz.36 – gsmtp

    2021-01-04 10:43:37 CLIENT -> SERVER: EHLO clothbank.com.bd

    2021-01-04 10:43:37 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [198.54.114.17]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8

    2021-01-04 10:43:37 CLIENT -> SERVER: STARTTLS

    2021-01-04 10:43:37 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS

    2021-01-04 10:43:37 CLIENT -> SERVER: EHLO clothbank.com.bd

    2021-01-04 10:43:37 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [198.54.114.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8

    2021-01-04 10:43:37 CLIENT -> SERVER: AUTH LOGIN

    2021-01-04 10:43:37 SERVER -> CLIENT: 334 VXNlcm5hbWU6

    2021-01-04 10:43:37 CLIENT -> SERVER: [credentials hidden]

    2021-01-04 10:43:37 SERVER -> CLIENT: 334 UGFzc3dvcmQ6

    2021-01-04 10:43:37 CLIENT -> SERVER: [credentials hidden]

    2021-01-04 10:43:37 SERVER -> CLIENT: 535-5.7.8 Username and Password not accepted. Learn more at535 5.7.8 https://support.google.com/mail/?p=BadCredentials 193sm54756530pfz.36 – gsmtp

    2021-01-04 10:43:37 SMTP ERROR: Password command failed: 535-5.7.8 Username and Password not accepted. Learn more at535 5.7.8 https://support.google.com/mail/?p=BadCredentials 193sm54756530pfz.36 – gsmtp

    SMTP Error: Could not authenticate.

    2021-01-04 10:43:37 CLIENT -> SERVER: QUIT

    2021-01-04 10:43:37 SERVER -> CLIENT: 221 2.0.0 closing connection 193sm54756530pfz.36 – gsmtp

    2021-01-04 10:43:37 Connection: closed

    SMTP Error: Could not authenticate.

    Sanjeev Aryal

    (@sanzeeb3)

    5 years, 5 months ago

    Hi @kaizur-ahmed,

    Thanks for the details. These two steps should help you identify the problem. Likely is you’ll need to allow less secure apps.

    I hope this helps!

    Sanjeev Aryal

    (@sanzeeb3)

    5 years, 4 months ago

    Hi @kaizur-ahmed – We haven’t heard from you in about a week, so I’m going to go ahead and mark this ticket resolved. If you still have questions, though, please feel welcome to continue the conversation.

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

The topic ‘Mail not send’ is closed to new replies.