• 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 Change certificate for lists vhost for mailman3

blindzero

New Pleskian
Server operating system version
Debian12
Plesk version and microupdate number
18.0.58 #2
Hi there,

up front: I am aware that mailman3 is not officially supported yet and seems also not fully developed at all a.t.m.
Hence I am tinkering around to get this running based on the setup / installation Plesk is doing (based on this post).

One basic issue I have is the following:
Nginx and Apache get a lists.* vhost in the plesk.conf.d\server.conf using the server's default certificate.
As you can imagine, a lists.* will not work with one certificate, changing the certificate to the right one seems not to survive very long due to Plesk's internal procedures.
Any other idea here?
I though about creating a site called lists.domain.tld but Plesk is prohibiting this as the domain is already in use by mailing lists.

Best & Thanks,
Matthias
 
Back
Top