C
Cranky
Guest
Time for a new feature-requests thread as my last one has become messy and confusing. Lots of great feedback, I think I've pulled all the important ones here - some from my last thread, some from elsewhere on the forums, and some from Plesk for Windows:
- AWStats as an option alongside webalizer
- DSpam integration
- Reseller creating sub-resellers user hierarchy
- Statistics for subdomains
- Branded webmail (per-client and per-domain basis)
- Language packs inclusive in cost
- Multiple FTP logins (with restrictive access for some FTP logins to certain directories)
- Ability to hide un-necessary directories from FTP users (bin, conf, pd, etc.)
- Hard-disk quota in "limits" section
- Separate DNS templates for each Client
- Circular/notifications system to communicate with clients, domain users and email users - with reseller support
- Per-client trouble ticket controls (e.g. admin can switch it off for his clients, but his clients can use it for his/her domain users)
- Zope support
- Remote access MySQL option per-db
- Moving clients to a predefined template rather than manually adjusting limits to change package
- Suspended domain holding page when domain switched "off"
- Per client holding page (instead of Plesk placeholder)
- Vhost.conf and vhost_ssl.conf updates via interface
- Urchin integration (like Coldfusion integration currently is)
- SPF DNS entries (http://spf.pobox.com) - at the moment we can enter these, but a wizard to generate them would be useful
- Have rollover transfer, where you have a monthly transfer and allow to set max rollover. Like they have 60GB/mo, and they only use 20GB, and the max rollover is 15GB, so they'll have 60GB next month plus the 15GB rolled over for 75GB next month.
- Automated server backup system
- Improved spamassassin support (e.g. score <1 = normal, 1-3 = tagged, 3+ = deleted) and also option to forward spam to a second mailbox
- Subdomain/webuser password-protected directories
- Subdomain/webuser frontpage support
- GnuPG support for email
- phpsuexec support
- Client overselling support (useful occasionally)
- Hard data transfer limits (overuse transfer and your site switches to holding page)
- Outlook automatic email account installer generator
- Additional webmail options (choose between IMP and SquirrelMail)
- Database user sharing ... 1 user for more than 1 database (maybe, I believe technically this can cause problems with PHP)
- Multiple users with same name in control panel (At the moment you can't add 2 clients with the same name (eg: John Smith))
- Shoutcast streaming integration (live streaming)
- Darwin streaming integration (streaming from playlist)
- mod_bandwidth integration for limiting bandwidth to some domains/clients
- Domain registration plugins - ENOM, DirectI, OpenSRS, etc.
- Master Control Panel On/Off switch to control whether clients can log in or not (like forum software has) which would be useful prior to and after upgrades.
- Jabber support might be a pretty cool option to be able to offer your clients. Their own IM server, with transports to AIM, ICQ, MSN, etc (http://www.jabber.org)
- Ability to have the central webmail covered by a domain's own SSL certificate instead of the default PLESK certificate.
- Option to hide Greyed-out buttons.
- /webstat and /ftpstat only viewable within Plesk (admin option).
- Option to add the DB username as a required prefix.
- FrontPage and FTP logins use same login details (click a checkbox to copy the details from FTP to the frontpage fields, or just automatically do it greying out the frontpage fields when the checkboxes clicked). (Plesk 7 for Windows uses same login for both)
- Option to have httpdocs and httpsdocs merged per-domain, e.g. checkbox makes http and https both serve files from the same directory
- "Live Support" addon option in the CP. Like an IRC chat window in the CP where sessioned clients could interact with logged in admin or support staff.
- I would be nice if the Plesk interface supports the abillity to choose with ACL rights a created database user should have... (at least in MySQL as its very simple to implement a point and click interface that supports it).
- Ability to register ACL for other allowed hosts than localhost to login as database user
- Easy setup for backup MX
- Improve spamassassin for users: trusted_networks, ok_languages, ok_locales and allow decimals in required hits.
- Client/domain templates, ability to decide which skin the client/domain has.
- Cerberus helpdesk integration (or even a simple 'contact us' form as option instead of the Helpdesk
- Redirect : Ability to choose between Redirect, Redirect Copy, Forward First ## characters (can be used for generating SMS alerts on mobiles).
- Advanced Filters / Forwarding rules : To create rules for handling & forwarding emails. Current rules apply only for webmail interface - Would be nice to have comprehensive rules at the mailbox level. (Example: If TO/CC Contain/Do Not Contain <Value Here> then Forward/Forward Copy/Move/Delete message to email/folder ).
- WebDAV support via the Control Panel just like that of protected directories.
- Webalizer should have more "clever" settings, for first, we need to remove referer from itself.
- SpamAssassin settings need an option to forward spam to a seperate email box and not just the one that it is currently filtering, this was you can forward it to your spamcop.net account ect..
- When training your Bayes filter they need to add a "Select all as spam" for people who have a dedicated spam dropbox instead of having to click on thousands of emails to designate they are spam.
- The ability to choose between different virus scanner backends such as clamAV, f-prot, etc., and have the email virus scanning icon appear if you have any of them enabled not just for dr.web.
- Have the default skins managed in the Skins button, as opposed to the Preferences button.
- Make the skin dropdown boxes list the skins alphabetically.
- Ability to move clients and domains between "client templates" and "domain templates" would be useful.
- A feature that allows users to import there address book to the white list in spam filter configuration would be nice.
- Possibilty to switch off the user rights to change the skin.
- Mono open source asp.net interpretor for *nix systems support.
- Spamassassin 3 support
- Ability to add an IP block rather than individual IP's to server IP Pool
- TMDA Support would be really, really nice.
- Nagios integration (www.nagios.org), as a module
- APF integration, as a module
- Reseller-level creation utilities (so resellers can link a system such as modernbill to Plesk for automated account creation, etc.)
- A basic and advanced interface selection (basic including the odd thing such as FTP password changes, mailbox setup - basically a very simple interface for users who don't have a clue, and standard Plesk interface for those who do - controllable by admin/client/domain level)
- Advanced feature selection (such as not showing any of the hosting stuff if we want to setup an email only domain-level account)
- Web user control panel access
- ProFTPd SSL patch
- Easy-to-configure control panel access so that we can serve Plesk from port 443 on a specific IP rather than messing with httpsd.conf, etc. to bind Plesk to an IP for behind-firewall access when 8443 is blocked
- Password-protected directories for subdomains
- Domain vhost and email aliasing (web/ftp, mail, or web/ftp/mail type)
- Advanced reseller branding (ability to add welcome message and news to main page of control panel etc.)
- Automated client backups (similar to domain-level, but client-wide)
- GUI for psa-bu with full-server backup automation
- Password Revealer, show to admin/client/domain/mail any password under their control, like FTP, mail, DB, PLESK etc.
- Ability to move domains between clients
- SSH sessions manager
- Database Space Limits
- Remote MySQL support
- Urchin Stats Support
- Hotlink protection
- Shared SSL Setup
- DNS SOA/IFXR customization
- Configuring script library access (in client/domain templates, and afterwards)
- phpMyAdmin root access
- FrontPage extensions on subdomains
Any further ideas?
Let's try keep it on topic please ...
- AWStats as an option alongside webalizer
- DSpam integration
- Reseller creating sub-resellers user hierarchy
- Statistics for subdomains
- Branded webmail (per-client and per-domain basis)
- Language packs inclusive in cost
- Multiple FTP logins (with restrictive access for some FTP logins to certain directories)
- Ability to hide un-necessary directories from FTP users (bin, conf, pd, etc.)
- Hard-disk quota in "limits" section
- Separate DNS templates for each Client
- Circular/notifications system to communicate with clients, domain users and email users - with reseller support
- Per-client trouble ticket controls (e.g. admin can switch it off for his clients, but his clients can use it for his/her domain users)
- Zope support
- Remote access MySQL option per-db
- Moving clients to a predefined template rather than manually adjusting limits to change package
- Suspended domain holding page when domain switched "off"
- Per client holding page (instead of Plesk placeholder)
- Vhost.conf and vhost_ssl.conf updates via interface
- Urchin integration (like Coldfusion integration currently is)
- SPF DNS entries (http://spf.pobox.com) - at the moment we can enter these, but a wizard to generate them would be useful
- Have rollover transfer, where you have a monthly transfer and allow to set max rollover. Like they have 60GB/mo, and they only use 20GB, and the max rollover is 15GB, so they'll have 60GB next month plus the 15GB rolled over for 75GB next month.
- Automated server backup system
- Improved spamassassin support (e.g. score <1 = normal, 1-3 = tagged, 3+ = deleted) and also option to forward spam to a second mailbox
- Subdomain/webuser password-protected directories
- Subdomain/webuser frontpage support
- GnuPG support for email
- phpsuexec support
- Client overselling support (useful occasionally)
- Hard data transfer limits (overuse transfer and your site switches to holding page)
- Outlook automatic email account installer generator
- Additional webmail options (choose between IMP and SquirrelMail)
- Database user sharing ... 1 user for more than 1 database (maybe, I believe technically this can cause problems with PHP)
- Multiple users with same name in control panel (At the moment you can't add 2 clients with the same name (eg: John Smith))
- Shoutcast streaming integration (live streaming)
- Darwin streaming integration (streaming from playlist)
- mod_bandwidth integration for limiting bandwidth to some domains/clients
- Domain registration plugins - ENOM, DirectI, OpenSRS, etc.
- Master Control Panel On/Off switch to control whether clients can log in or not (like forum software has) which would be useful prior to and after upgrades.
- Jabber support might be a pretty cool option to be able to offer your clients. Their own IM server, with transports to AIM, ICQ, MSN, etc (http://www.jabber.org)
- Ability to have the central webmail covered by a domain's own SSL certificate instead of the default PLESK certificate.
- Option to hide Greyed-out buttons.
- /webstat and /ftpstat only viewable within Plesk (admin option).
- Option to add the DB username as a required prefix.
- FrontPage and FTP logins use same login details (click a checkbox to copy the details from FTP to the frontpage fields, or just automatically do it greying out the frontpage fields when the checkboxes clicked). (Plesk 7 for Windows uses same login for both)
- Option to have httpdocs and httpsdocs merged per-domain, e.g. checkbox makes http and https both serve files from the same directory
- "Live Support" addon option in the CP. Like an IRC chat window in the CP where sessioned clients could interact with logged in admin or support staff.
- I would be nice if the Plesk interface supports the abillity to choose with ACL rights a created database user should have... (at least in MySQL as its very simple to implement a point and click interface that supports it).
- Ability to register ACL for other allowed hosts than localhost to login as database user
- Easy setup for backup MX
- Improve spamassassin for users: trusted_networks, ok_languages, ok_locales and allow decimals in required hits.
- Client/domain templates, ability to decide which skin the client/domain has.
- Cerberus helpdesk integration (or even a simple 'contact us' form as option instead of the Helpdesk
- Redirect : Ability to choose between Redirect, Redirect Copy, Forward First ## characters (can be used for generating SMS alerts on mobiles).
- Advanced Filters / Forwarding rules : To create rules for handling & forwarding emails. Current rules apply only for webmail interface - Would be nice to have comprehensive rules at the mailbox level. (Example: If TO/CC Contain/Do Not Contain <Value Here> then Forward/Forward Copy/Move/Delete message to email/folder ).
- WebDAV support via the Control Panel just like that of protected directories.
- Webalizer should have more "clever" settings, for first, we need to remove referer from itself.
- SpamAssassin settings need an option to forward spam to a seperate email box and not just the one that it is currently filtering, this was you can forward it to your spamcop.net account ect..
- When training your Bayes filter they need to add a "Select all as spam" for people who have a dedicated spam dropbox instead of having to click on thousands of emails to designate they are spam.
- The ability to choose between different virus scanner backends such as clamAV, f-prot, etc., and have the email virus scanning icon appear if you have any of them enabled not just for dr.web.
- Have the default skins managed in the Skins button, as opposed to the Preferences button.
- Make the skin dropdown boxes list the skins alphabetically.
- Ability to move clients and domains between "client templates" and "domain templates" would be useful.
- A feature that allows users to import there address book to the white list in spam filter configuration would be nice.
- Possibilty to switch off the user rights to change the skin.
- Mono open source asp.net interpretor for *nix systems support.
- Spamassassin 3 support
- Ability to add an IP block rather than individual IP's to server IP Pool
- TMDA Support would be really, really nice.
- Nagios integration (www.nagios.org), as a module
- APF integration, as a module
- Reseller-level creation utilities (so resellers can link a system such as modernbill to Plesk for automated account creation, etc.)
- A basic and advanced interface selection (basic including the odd thing such as FTP password changes, mailbox setup - basically a very simple interface for users who don't have a clue, and standard Plesk interface for those who do - controllable by admin/client/domain level)
- Advanced feature selection (such as not showing any of the hosting stuff if we want to setup an email only domain-level account)
- Web user control panel access
- ProFTPd SSL patch
- Easy-to-configure control panel access so that we can serve Plesk from port 443 on a specific IP rather than messing with httpsd.conf, etc. to bind Plesk to an IP for behind-firewall access when 8443 is blocked
- Password-protected directories for subdomains
- Domain vhost and email aliasing (web/ftp, mail, or web/ftp/mail type)
- Advanced reseller branding (ability to add welcome message and news to main page of control panel etc.)
- Automated client backups (similar to domain-level, but client-wide)
- GUI for psa-bu with full-server backup automation
- Password Revealer, show to admin/client/domain/mail any password under their control, like FTP, mail, DB, PLESK etc.
- Ability to move domains between clients
- SSH sessions manager
- Database Space Limits
- Remote MySQL support
- Urchin Stats Support
- Hotlink protection
- Shared SSL Setup
- DNS SOA/IFXR customization
- Configuring script library access (in client/domain templates, and afterwards)
- phpMyAdmin root access
- FrontPage extensions on subdomains
Any further ideas?
Let's try keep it on topic please ...