You are currently not able to Alias a subdomain through plesk. Instead you must create the subdomain as a primary if you wish to alias it. In many situations it would make sense from an organizational standpoint to keep the subdomain under a main domain while still adding aliases to it. I do not believe this is a technical restriction of the webservers so it would be helpful if plesk allowed you to add aliases to subdomains.

if you would manage multiple Plesk servers that function very appropriate

Add a DNS TTL per entry option instead of just SOA TTL.

This will make it more inline with products like cPanel etc and is very useful when using dynamic dns to have low TTL but other entries like mx can have a high TTL

At the moment by default any webmail interface is under domain webmail.<domain>

Some people would like to use custom one. For me personally it's important to have this as server-wide setting (I have basic workaround for this - custom domainWebmail.php), but it isn't perfect (many links to webmail service missing, e.t.c.).

And that's why we have plesk - user friendly interface.

Add HHVM support

The version of GD provided with Plesk PHP packages does not have support for webp enabled by default. Almost all browsers now support this format.
https://developers.google.com/speed/webp/

t would be a good idea to have an SQL section where users can run optimization scripts like MYSQLTUNER etc and enter suggestioned changes in a GUI that directly change the mysql.conf directly and correctly.

An ability to monitor performance and tweak would be ideal, making the task of SQL performance monitoring and tweaking far easier.

Also optimize commands and other tasks could be run for this panel.

as well as optimize and the ability to add it to cron for weekly or monthly.

I suggest you add a feature in Settings with which we can enable SPAM / VIRUS protection for newly created mailboxes by default.

Discussion here:

http://forum.parallels.com/showthread.php?287233-Anti-virus-and-anti-spam-enabled-by-default-on-mailbox-creation&p=715980#post715980

It would be nice to have an external SMTP (smarthost) ability for a per-domain basis (most mail services have this)

We use this for external scanning, data leak prevention and more.

Can this be be done?

Most of RBLS are checking the SMTP Banner and currently only the first domain name is being used. To reduce scamming or to prevent being blacklisted you should apply myhostname with the according domain name.

We have many support requests from our customers (non technical) to search logs and find if a message was sucessfull delivered and consume much from our support.

If the customer could search logs from a specific sender ou destination, filtering by date, will be great for us.

If I use FTP, I can make as many users as I want. For various reasons, using FTP is not optimal at my workplace. I'd like to be able to let each ftp user I create log in with chrooted sftp.

I'm able to modify /etc/passwd and /var/www/vhosts/example.org/etc/passwd to make it work, but doing that manually kind of defeats the point of using a tool like Plesk...

Specifically, I give the ftp user the same home directory, and shell as the initial sftp user has in each passwd file.

I'll like to create a hosting that only use Nginx as webserver. Also I'll like to do this with Node.js, but I think it will not be approved.

It would be nice to provide mail SSL/TLS support with SNI for more domains from single IP

Some of security configuration requires GeoIP detection. It also useful for tracing and should be easy as adding '--with-http-geoip-module' option to configure command for the package.

Many mail servers have this feature. Please include in plesk possibility to add disclaimer to mail footer on specified domain.

Many Clients ask me how to add Disclaimer to mail footer automatically not from webmail.

As we have to use apache, i don't like to go for an aditional nginx proxy just to simulate HTTP/2 ;-)

I think apache is capable to handel HTTP/2 :-D

What about DDOS Protection in Plesk?

Please add Mailman support to Let's Encrypt.

Ideally, one could issue either a certificate directly for lists.domain.com or a wildcard certificate for *.domain.com.

Furthermore, a secure connection should be enforceable.

Thanks!

Doing this by hand is very time consuming. An option for rename database would be great feature.