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

Issue mailman3: host and web-host not aligned with custom domain name

Jan

Basic Pleskian
Server operating system version
Debian 12.6
Plesk version and microupdate number
18.0.63 Update #4, last updated on Sept 4, 2024 06:27 AM
Is:

In the mailman3-configuration example.com / localhost is encoded at various places:
  1. /etc/mailman3/mailman.cfg: site_owner:
  2. /etc/mailman3/mailman-web.py: EMAILNAME
  3. postorious / django3 Web-Host List (https://<domain>/mailman3/admin/sites/site/): example.com
Should:

1. and 2. should be valid email-addresses to contact the site-owner. These are default addressed for moderation-requests
3. Is more tricky. This can either be the name of the vhost oder the host. That depends on how django is integrated into plesk. IMHO, the best-case scenario would be to have a dedicated web-host per enabled domain including a valid let's-encrypt certificate ... But this is seemingly not the case. However, example.com does not fit, here
 
Back
Top