• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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