Issue Plesk PCI Compliance Resolver - PHPmailer Openssl not working - WHMCS/Wordpress

[Xavier12]

Hey guys,

Recently used Plesk pci compliance resolver to be sure to make our server compliant to the latest PCI compliance standard.. which means TLSv1 is disabled server wide... in doing this, it seems that Php 5.5 and 5.6 no longer works with phpmailer or smtp emails at all. Emails are no longer going through WHMCS or Wordpress contact forms. A valid certificate is installed and emails work fine within email apps, but php just wont work with email smtp at all... I believe it has to do with openssl and pointing openssl to the specific certificate files in php.ini... the SSL we are using for mail is Letsencrypt. Here is the error in WHMCS. Everything is correct, including the mail server, username and login.

CLIENT -> SERVER: EHLO www.MYDOMAIN.com
CLIENT -> SERVER: STARTTLS
SMTP Error: Could not connect to SMTP host.
CLIENT -> SERVER: QUIT
SMTP ERROR: QUIT command failed:
SMTP Error: Could not connect to SMTP host.

Email Sending Failed - SMTP Error: Could not connect to SMTP host.

Please advise, thanks!

Centos/Cloudlinux 6.8
Plesk Onyx
Postfix & Dovecot

 

[Xavier12]

For such a crucial issue in regards to Plesk being PCI Compliant, I know that I CANNOT be the only one having this problem. Instead of the PCI compliance resolver fixing the issue, it created one major one.

Please advise, thanks guys.

 

[UFHH01]

Hi Xavier12,

it seems that Php 5.5 and 5.6 no longer works with phpmailer or smtp emails at all.

Pls. provide MORE informations, why you stated that "it seems" to be the root cause. Being a registered member here in the Plesk - forum, you should be aware that FACTS are needed for investigations and not guessings.

Consider to POST the corresponding scripts, which you use, if you need help to correct possible misconfigurations.

Consider to POST corresponding log - entries from your mail - logs.

Consider to RAISE the log - level, in order to get a more verbose output in your webserver - logs for the corresponding (sub)domain and POST the corresponding log - entries.

Here is the error in WHMCS

That doesn't help at all, because we cannot investigate extensions from a THIRD-PARTY. A possible reproduction will also fail, because the WHMCS - extensions is not free of charge. Consider to contact THEIR support if you experience issues with THEIR product, please - you PAID for THEIR product, so you have legal claim to support.