Test Mail won’t get through, and I have tried everything…

  • Resolved andreascarlsson

    (@andreascarlsson)


    5 years, 1 month ago

    I have installed zillion of email accounts, and I *think* that I know what I’m doing, but now something really weird has happened.

    I am creating a contact form for a client that uses an email provider (openit.se) I haven’t used before. They gave me the credentials to the account.

    I have tried the account with my Mail application and it works as it should. However, when I set it up in the WP Mail SMTP plugin, it just say that it can’t authenticate.

    I have tried with and without SSL/TLS/Passwords etc etc, and just to be sure that something wasn’t effed up with the WP installation I deleted the SMTP plugin and reinstalled it. I have also tried an account on a server that I know works, and that was no problems.

    Do any of you guys know if RoundCube (that openit.se use) have some kind of setting that forbids contact forms or connection via PHP? ??
    Because I don’t know of any other possible answer to this culprit.
    I could of course talk to the provider, but they haven’t been very supportive so far.

    Error log (clients domain have been censored):

    Versions:
    WordPress: 5.2.4
    WordPress MS: No
    PHP: 7.3.10
    WP Mail SMTP: 1.6.2
    Params:
    Mailer: smtp
    Constants: No
    ErrorInfo: SMTP Error: Could not authenticate.
    Host: ******.se
    Port: 587
    SMTPSecure: tls
    SMTPAutoTLS: bool(true)
    SMTPAuth: bool(true)
    Server:
    OpenSSL: OpenSSL 1.0.2k 26 Jan 2017
    SMTP Debug:
    2019-10-22 14:01:47 Connection: opening to ******.se:587, timeout=300, options=array (
    )
    2019-10-22 14:01:47 Connection: opened
    2019-10-22 14:01:47 SERVER -> CLIENT: 220 mail.axier.org ESMTP Postfix (Ubuntu)
    2019-10-22 14:01:47 CLIENT -> SERVER: EHLO *****.se 2019-10-22 14:01:47 SERVER -> CLIENT: 250-mail.axier.org
    250-PIPELINING
    250-SIZE 10240000
    250-VRFY
    250-ETRN
    250-STARTTLS
    250-AUTH PLAIN LOGIN CRAM-MD5 DIGEST-MD5
    250-AUTH=PLAIN LOGIN CRAM-MD5 DIGEST-MD5
    250-ENHANCEDSTATUSCODES
    250-8BITMIME
    250 DSN
    2019-10-22 14:01:47 CLIENT -> SERVER: STARTTLS
    2019-10-22 14:01:47 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS 2019-10-22 14:01:47 CLIENT -> SERVER: EHLO *****.se 2019-10-22 14:01:47 SERVER -> CLIENT: 250-mail.axier.org
    250-PIPELINING
    250-SIZE 10240000
    250-VRFY
    250-ETRN
    250-AUTH PLAIN LOGIN CRAM-MD5 DIGEST-MD5
    250-AUTH=PLAIN LOGIN CRAM-MD5 DIGEST-MD5
    250-ENHANCEDSTATUSCODES
    250-8BITMIME
    250 DSN
    2019-10-22 14:01:47 CLIENT -> SERVER: AUTH CRAM-MD5
    2019-10-22 14:01:47 SERVER -> CLIENT: 334 PDMxMzE2NTI2MDcuMTE0NzE5MTFAbWFpbC5heGllci5vcmc+
    2019-10-22 14:01:47 CLIENT -> SERVER: a29udGFrdEBsanVzZXhwZXJ0ZW4uc2UgNWVmOTYxN2U4ZDQ0ZGZjZTk1OTgyYjZhYWU2OTM1ZjE= 2019-10-22 14:01:47 SERVER -> CLIENT: 535 5.7.8 Error: authentication failed: authentication failure
    2019-10-22 14:01:47 SMTP ERROR: Username command failed: 535 5.7.8
    Error: authentication failed: authentication failure
    2019-10-22 14:01:47 SMTP Error: Could not authenticate.
    2019-10-22 14:01:47 CLIENT -> SERVER: QUIT
    2019-10-22 14:01:47 SERVER -> CLIENT: 221 2.0.0 Bye
    2019-10-22 14:01:47 Connection: closed
    2019-10-22 14:01:47 SMTP Error: Could not authenticate.

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

  • Hi @andreascarlsson,

    This could be due to an incorrect SMTP authentication setting in the email server configuration. Also, make sure that the username in your SMTP configuration to be your full email address, which includes the domain. If you feel everything is correct, the next best step is to contact your webhost. Unfortunately, I’m not aware of RoundCube and it’s configuration.

    Thanks!

    Thread Starter andreascarlsson

    (@andreascarlsson)

    Thanks Mr Aryal,

    I have contacted them. Unfortunately they are quite irrogant about our situation.

    So, basically I think their server is set to not allow PHP connections. That’s what I have told them, and they “should check it”.

    Hi @andreascarlsson,

    In case it’s helpful, you might consider switching to one of our mailer options to potentially get around this issue with your webhost.

    While the Other SMTP mailer shown in your error log works within your hosting provider’s server (and so is super prone to any issues in that server), the other mailer options use APIs to work with outside services for this same end goal of improving your site’s email delivery.

    Since it already looks like your site’s server is prone to issues, I’d specifically recommend Sendinblue, Mailgun, or SendGrid (since Google’s API is also prone to server-based issues). While I can’t be certain about your specific situation, we’ve seen lots of other cases where simply switching to one of these API-based mailers allows things to get up and running smoothly.

    In case it helps, we’ve shared an overview of all mailer options (including links to step by step tutorials) here.

    Hopefully this might help you get an alternate solution!

    Thread Starter andreascarlsson

    (@andreascarlsson)

    We finally figured it out; The mailserver don’t accept CRAM MD-5 encryption, which is the default encryption method in WP Mail SMTP. We could change it to PLAIN in the code, and now it works.

    Maybe the plugin should have this as an option?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Test Mail won’t get through, and I have tried everything…’ is closed to new replies.