Skip to main content

Issue sending mails through 3rd party

gxHL
Hi I would like to use 3rd party SMTP settings to send emails from my app. But for some reason I cannot use TLS in my app to send the emails. I tried couple services which include Amazon SES, Sendinblue and Sendgrid. These are my settings. SMTP Host : tls://smtp.sendgrid.net SMTP User : myusername SMTP Pass : mypass SMTP Port : 587 tried also with 25, 2525 and SSL 465 with (ssl://smtp.sendgrid.net) I have searched through the forums and couldn't find answers. I read a lot of references about the firewall. I have to mention that the installation is default by my hosting company to my VPS so I didn't installed any and I don't know if I have any installed. I am always receiving an error like this PHP Warning: stream_socket_enable_crypto(): Peer certificate CN=`vmi67875.example.host' did not match expected CN=`smtp.sendgrid.net' PHP Notice: Error: Password not accepted from server! [LIST]
  • CENTOS 7.2 x86_64 kvm " vmi67875 [LIST]
  • WHM 56.0 (build 24 Any help appreciated.

    • Comments

    4 comments

    Date Votes
    • gxHL
      Fixed it was a configuration "SMTP Restrictions"
      0
    • cPanelMichael
      Hello, I'm happy to see you were able to address the issue. Thank you for updating us with the outcome.
      0
    • wickodesign
      So did you simply disable the SMTP restrictions? Does this not make the server more vulnerable for sending spam?
      0
    • reberiii
      Hello! I've recently run into this issue where the server provider performed a physical update to my machine causing an outage. After service was restored, I had several websites that were encountering the error above. Here's my version of the error: SMTP Error: Could not connect to SMTP host. Connection failed. stream_socket_enable_crypto(): Peer certificate CN=`my.server.com' did not match expected CN=`smtp.office365.us' I looked into the SMTP Restrictions setting, however, my SMTP Restrictions was already set to disabled. Simply Enabling the SMTP Restriction and then immediately disabling it once again fixed my issue. Simply toggling the setting on and back off again was the trick. Hope this helps someone at some point.
      0

    Please sign in to leave a comment.

    Didn't find what you were looking for?

    New post