• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Recent content by ErwanG

  1. E

    403 4.7.0 TLS handshake failed

    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.
  2. E

    403 4.7.0 TLS handshake failed

    Igor, If i change mail server (Qmail) to Postfix, is the ssl config is reset or no? Or how i can reset ssl config?
  3. E

    403 4.7.0 TLS handshake failed

    How i can change it?
  4. E

    403 4.7.0 TLS handshake failed

    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?
  5. E

    403 4.7.0 TLS handshake failed

    Yes. I've not this problem. I've found that : http://serverfault.com/questions/667692/reason-403-4-7-0-tls-handshake-failed But i don't know how i can fix.
  6. E

    403 4.7.0 TLS handshake failed

    12.0
  7. E

    403 4.7.0 TLS handshake failed

    Another thing (related?) : with Horde, we can not send message. Error: Could not open secure TLS connection to the server
  8. E

    403 4.7.0 TLS handshake failed

    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.
  9. E

    403 4.7.0 TLS handshake failed

    Igor, I have exactly the same content...
  10. E

    403 4.7.0 TLS handshake failed

    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
  11. E

    Message "Message successfully relayed to a system that does not support receipts"

    Thank you. No another message and there is only the problem with my customer. Sender is @samsung.com.... ....
  12. E

    Message "Message successfully relayed to a system that does not support receipts"

    Hello, A customer (mail server under plesk 12) doesn't receive email from sender. Sender receive message error : "Message successfully relayed to a system that does not support receipts" Do you know what's the problem? Thanks
  13. E

    Openssl problem

    So there isn't solution for sslv3_alert_handshake_failure;??
  14. E

    Openssl problem

    But it's normal after this http://kb.odin.com/en/125741 no?
  15. E

    Openssl problem

    Igor: not yet for theses servers... And for "sslv3_alert_handshake_failure"?
See more
Back
Top