Sending mail gives ‘critical error’

  • Resolved barcombeboy

    (@barcombeboy)


    4 years, 2 months ago

    Hi.

    Although the Gmail-SMTP plugin connects correctly and is authenticated by our designated Google account sending the mail seems to cause a critical error. Here’s the (anonomized) log. Any help appreciated.
    Wordpress 5.5
    Gmail SMTP 1.2.0

    2020-09-01 10:33:01 Connection: opening to smtp.gmail.com:587, timeout=300, options=array ( ‘ssl’ => array ( ‘verify_peer’ => false, ‘verify_peer_name’ => false, ‘allow_self_signed’ => true, ),)
    2020-09-01 10:33:01 Connection: opened
    2020-09-01 10:33:01 SMTP INBOUND: “220 smtp.gmail.com ESMTP z14s*****203wre.** – gsmtp”
    2020-09-01 10:33:01 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP z14s*****203wre.** – gsmtp
    2020-09-01 10:33:01 CLIENT -> SERVER: EHLO <the domain name>
    2020-09-01 10:33:01 SMTP INBOUND: “250-smtp.gmail.com at your service, [*.**.**.**.**]”
    2020-09-01 10:33:01 SMTP INBOUND: “250-SIZE 35882577”
    2020-09-01 10:33:01 SMTP INBOUND: “250-8BITMIME”
    2020-09-01 10:33:01 SMTP INBOUND: “250-STARTTLS”
    2020-09-01 10:33:01 SMTP INBOUND: “250-ENHANCEDSTATUSCODES”
    2020-09-01 10:33:01 SMTP INBOUND: “250-PIPELINING”
    2020-09-01 10:33:01 SMTP INBOUND: “250-CHUNKING”
    2020-09-01 10:33:01 SMTP INBOUND: “250 SMTPUTF8”
    2020-09-01 10:33:01 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [*.**.**.**.**]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
    2020-09-01 10:33:01 CLIENT -> SERVER: STARTTLS
    2020-09-01 10:33:01 SMTP INBOUND: “220 2.0.0 Ready to start TLS”
    2020-09-01 10:33:01 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS
    2020-09-01 10:33:01 CLIENT -> SERVER: EHLO <domain name>
    2020-09-01 10:33:01 SMTP INBOUND: “250-smtp.gmail.com at your service, [*.**.**.**.**]”
    2020-09-01 10:33:01 SMTP INBOUND: “250-SIZE 35882577”
    2020-09-01 10:33:01 SMTP INBOUND: “250-8BITMIME”
    2020-09-01 10:33:01 SMTP INBOUND: “250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH”
    2020-09-01 10:33:01 SMTP INBOUND: “250-ENHANCEDSTATUSCODES”
    2020-09-01 10:33:01 SMTP INBOUND: “250-PIPELINING”
    2020-09-01 10:33:01 SMTP INBOUND: “250-CHUNKING”
    2020-09-01 10:33:01 SMTP INBOUND: “250 SMTPUTF8”
    2020-09-01 10:33:01 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [*.**.**.**.**]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
    2020-09-01 10:33:01 Auth method requested: XOAUTH2
    2020-09-01 10:33:01 Auth methods available on the server: LOGIN,PLAIN,XOAUTH2,PLAIN-CLIENTTOKEN,OAUTHBEARER,XOAUTH
    2020-09-01 10:33:01 CLIENT -> SERVER: QUIT
    2020-09-01 10:33:01 SMTP INBOUND: “221 2.0.0 closing connection z14s*****203wre.** – gsmtp”
    2020-09-01 10:33:01 SERVER -> CLIENT: 221 2.0.0 closing connection z14s*****203wre.** – gsmtp
    2020-09-01 10:33:01 Connection: closed
    There has been a critical error on your website. Please check your site admin email inbox for instructions.

    • This topic was modified 4 years, 2 months ago by barcombeboy.
  • The topic ‘Sending mail gives ‘critical error’’ is closed to new replies.