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

Question Plesk supports certificate verification through a supported setting rather than editing a generated file manually.

B

bosse1

New Pleskian
Server operating system version
Debian 13
Plesk version and microupdate number
18.0.80
Plesk Obsidian 18.0.80 on Debian 13 with the MSMTP relay-only component generates /etc/msmtprc
through /usr/local/psa/admin/sbin/msmtpmng, which hardcodes tls_certcheck off.

Is there a supported persistent method to enable MSMTP server certificate verification, such as a panel.ini setting, configuration override/drop-in file, template, or supported CLI parameter, that survives regeneration and Plesk upgrades?
 
You must log in or register to reply here.

Similar threads

J.Wick
Issue External Email Stopped Working after Upgrading to Plesk Obsidian 18.0.70 Update #2
Replies
1
Views
6K
J.Wick
J.Wick
Back
Top