• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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