• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Mailman/Apache Configurations not correct

Timo_Mämecke

New Pleskian
I have two problems regarding Mailman Mailing Lists.

1)
The Mailman Interface is usually located under lists.domain.tld/mailman (I changed the config from /cgi-bin/mailman/ to just /mailman/), but it seems the apache confs for this subdomain are not applied – I only see the servers default page when visiting this URL. domain.tld/mailman works, though. It would be great if lists.domain.tld/mailman would actually work and domain.tld/mailman wouldn't work.
How do I change/repair the configurations properly? I've installed the newest MU and already to reinstall mailman.

2)
I get an Internal Server Error when visiting the domain.tld/mailman Interface. Reason is mod_suexec, which I need to disable for domain.tld/mailman, but where and how? All the vhost configurations are created automatically.
I could imagine this is related to my first problem and the mod_suexec thing is properly configured in the lists-subdomain config.

Thanks in advance!
Timo
 
Hi! Thanks for the links, they are pretty useful.

After a lot of searching I am sure this is a bug in Plesk. There is no lists.domain.tld:80 server running in nginx, so there is no way to forward it to apache (port 7080). I'm going to open a ticket.
 
Yes, you can create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
If it is found that your problem was caused by product bug w/o available solution or workaround from Parallels, then your purchase will be re-funded.
 
Back
Top