• 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.

client's "outbound" email SSL certificate different?

michaellunsford

Regular Pleskian
To secure email transfers, I've installed a chained SSL certificate on my server (which required me to tweak the ssl.conf file for apache). I also had to generate a pop3d.pem file in the /usr/share/courier-imap directory. Inbound e-mail works wonderfully, but when I try sending e-mail, it's using a different certificate.

Mail was unable to verify the identity of this server, which has a certificate issued to "plesk".

What is pointing to the plesk certificate, and how do I get it pointing to the right one?
 
As I'm having the exact same problem, I'd like to bump this thread asking for help. Anyone?
 
Back
Top