• 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 MailServer + Let's encrypt

Hello,

my hostname: mars.example.com.
I have multiple domains "exampl1.com", "example2.com" etc. with mailboxes.
If I set a ssl certificate via Configuration => SSL/TLS-Certificates I can only secure the hostname / one mailserver address (mail.example.com) of the server.
To allow all domains ssl secured connection to the mail server they have to use "mail.example.com", right? Not "mail.example1.com", "mail.example2.com" etc.

This way every email will be send through "mail.example.com" which should be no problem, isn't it?
 
Back
Top