• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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