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

Request for Features

P

prexusnet

Guest
We've recently moved our servers from Ensim to Plesk 8.1. Overall, we're pleased with the move but there are a few things we miss that we would like to see added into Plesk:

QMail:
- Would like the option to choose between Dr. Web and ClamAV (ClamAV works great and doesn't cost anything). I'm presently planning to attempt to configure that myself (or pay someone to do it) but I don't like the idea that it may screw up future Plesk upgrades (or that I could screw it up on the setup).

- Would like better logging facilities - I want to know when a message is rejected and why (including when rejected by DNS RBL). Of course, it also would be cool to be able to have statistics of mails killed as "potential spam".

Apache:
- Would like to be able to easily specify more advanced settings for sites without affecting others. For example, one site may need/want to have PHP Globals on, but I certainly don't want that for the rest. Doing it with an individual .conf in Plesk doesn't work and using .htaccess seems to be a little "quirky".

- Would like the ability to specify whether subdomains are their own entity in the subdomains folder or just an alias for a folder in the home domain's folder (e.g., /var/www/vhosts/myhost.com/subdomains/mysub/httpdocs versus /var/www/vhosts/myhost.com/httpdocs/mysub)


Thanks!
 
QMail:
- Would like the option to choose between Dr. Web and ClamAV (ClamAV works great and doesn't cost anything). I'm presently planning to attempt to configure that myself (or pay someone to do it) but I don't like the idea that it may screw up future Plesk upgrades (or that I could screw it up on the setup).

Using Atomic Rocket Turtle's packages you can integrate ClamAV into the qmail chain using qmail-scanner. Make sure you uninstall Dr. Web first.

Apache:
- Would like to be able to easily specify more advanced settings for sites without affecting others. For example, one site may need/want to have PHP Globals on, but I certainly don't want that for the rest. Doing it with an individual .conf in Plesk doesn't work and using .htaccess seems to be a little "quirky".

You do this by creating a vhost.conf file (vhost_ssl.conf for https) in a domain's conf directory. You can specify any domain-specific settings in that file. You'll need to use websrvmng after creating the file to make sure it is included in httpd.include. See the manual for more info on this procedure.
 
Re: Re: Request for Features

Originally posted by breun
Using Atomic Rocket Turtle's packages you can integrate ClamAV into the qmail chain using qmail-scanner. Make sure you uninstall Dr. Web first.



You do this by creating a vhost.conf file (vhost_ssl.conf for https) in a domain's conf directory. You can specify any domain-specific settings in that file. You'll need to use websrvmng after creating the file to make sure it is included in httpd.include. See the manual for more info on this procedure.

Thanks - we're planning to go with ART's instructions for doing that but may decide to pay someone who's done it a time or two if I don't feel up to it by this evening. Just too much to do and too little time to do it all.

Some directives don't work in the vhost.conf file - for example, PHP "register_globals on" has to be set in .htaccess because setting it in a vhost.conf file seems to have the effect of applying it server-wide (depending on which host it reads last).

One thing Ensim did a good job of was putting each domain in its own "jail". Each domain had its own php.ini, which it dutifully obeyed - perfect for customizing settings like max upload, max post, register globals, and all of that in a friendly format. The domain owner could even make those adjustments to their own /etc/php.ini if they felt so inclined. Of course, I have no idea what kind of additional overhead (if any) that meant to the server. I'm sure for every plus, there's a minus.
 
My company does dedicated server management and we have a lot of experience with ART's setup using qmail-scanner, ClamAV and the latest SpamAssassin. Let me know if you might be interested in our services.

It's perfectly possible to enable register_globals for a single domain through a vhost.conf file. Just add the following to vhost.conf:

Code:
php_admin_flag register_globals On
 
Originally posted by breun
My company does dedicated server management and we have a lot of experience with ART's setup using qmail-scanner, ClamAV and the latest SpamAssassin. Let me know if you might be interested in our services.

It's perfectly possible to enable register_globals for a single domain through a vhost.conf file. Just add the following to vhost.conf:

Code:
php_admin_flag register_globals On

Hmmm... tried that flag and it seemed to have the effect of turning it on server-wide even though it's enclosed in the <Virtual Host>. Will take another look at that.

May also send you a private message in a bit regarding the qmail-scanner.

Thanks!
 
Hmmm... tried that flag and it seemed to have the effect of turning it on server-wide even though it's enclosed in the <Virtual Host>. Will take another look at that.

I even tried that on one my own servers today before I said it just works. I set 'php_admin_flag register_globals On' for domain1.com and phpinfo() on domain1 said the register_globals was enabled locally for domain1, but not globally (master value). On domain2 (unmodified) phpinfo() said register_globals was disabled (local and master value).
 
Back
Top