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

changing mailman url

P

punt

Guest
Ok, so I've been using plesk for a while and never had any problems with lists being at lists.domain.com. However, I now have a client with a subdomain being hosted by me, on a different machine from the parent. He doesn't control DNS and can't get 'list.sub.domain.com' created.

I figured out how to change the list's url (i think) but when I try to modify his httpd config to add the mailman aliases, they simply don't work. Am I missing something? I added, to his httpd.include:

Code:
ScriptAlias /mailman/ /var/mailman/cgi-bin/
Alias /icons/ /var/www/icons/
Alias /pipermail/ /var/mailman/archives/public/

I tried adding the <Directory /var/mailman/archives/> directive from the base httpd.include and reloading but that didn't work either, and it technically shouldn't matter since I'm not even playing with the archives part yet.

I keep getting a 403 Forbidden error, and when I try to directly access one the mailman scripts (like /mailman/admin) I get a 500 internal server error. The error_log just says premature end of script headers.

Any ideas? I'm guessing this is an httpd config issue, but I'm just missing something.
 
Solved my own problem - this was a suexec issue.

In order to make this work, I had to remove suexec from this client's configuration. Not so happy about that solution.. but what can you do?
 
Back
Top