• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

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