• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

403 4.7.0 TLS handshake failed

ErwanG

Regular Pleskian
Hello,

Some emails are not delivery to Qmail server (Plesk 12). Error message:

Deferred: 403 4.7.0 TLS handshake failed.


What's the problem? I have found nothing about that...

Thank you.

Erwan
 
Make sure that you have file /var/qmail/control/tlsserverciphers with following content:

ALL:!ADH:!LOW:!SSLv2:!SSLv3:!EXP:+HIGH:+MEDIUM
 
There is no problem with most of the users but for some:
- error message with: 403 4.7.0 TLS handshake failed
- no error message but the noting in the recepient account...

In the log there isn't no trace.

I don't understand. It seems to be a problem since Poodle & Beast update for this server.
 
Another thing (related?) : with Horde, we can not send message.

Error: Could not open secure TLS connection to the server
 
Igor,

From another server to the server:

#openssl s_client -starttls smtp -connect pop3.xxx.com:25

I have:
....
New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-GCM-SHA384
...
Is Cipher correct?
 
On my test 12.0 Plesk server with default installation I see:

New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
 
Igor,

If i change mail server (Qmail) to Postfix, is the ssl config is reset or no?
Or how i can reset ssl config?
 
We have had the problem with 3 servers. We have tested the migration on one of them yesterday night.
It seems that the problem disapear.
 
Back
Top