oh and I forgot, the only reason I still even have Plesk users, Mailman support! I would really like to get rid of Plesk.
Speaking of Mail, if we decide to set up a dedicated Mail server so all mail isn’t handled on the IW server (could be another IW server handling mail) have the ability to:
Remove the Mail Options from the SiteWorx Control Panel, and have a link over to where the email server is located.
[quote=R-n-R;16036]Speaking of Mail, if we decide to set up a dedicated Mail server so all mail isn’t handled on the IW server (could be another IW server handling mail) have the ability to:
Remove the Mail Options from the SiteWorx Control Panel, and have a link over to where the email server is located.[/quote]
Actually already have a Feature Request open for this, among other things. 
It’s a pain in the butt having to run ~vpopmail/bin/vdeldomain every time a user moves their mail off-site and in turn have to keep track of that. I’m very excited about a new feature being available to handle this.
[quote=sliqua;16039]Actually already have a Feature Request open for this, among other things.
[/quote]
Hey cool, this would be the “cats meow”
Any more teasers?
[quote=R-n-R;16036]Speaking of Mail, if we decide to set up a dedicated Mail server so all mail isn’t handled on the IW server (could be another IW server handling mail) have the ability to:
Remove the Mail Options from the SiteWorx Control Panel, and have a link over to where the email server is located.[/quote]
Done 
Actually, we’ve gone a step or two further with that. In the next release, in addition to being able to control your MX records from SiteWorx, you can also set up an external SMTP server, so the webmail will continue to work!
It’s been posted in other threads, but we added RoundCube to the webmail programs.
Nearly every action that you can do in the browser is now possible through the XMLRPC API.
AND! There’s now a MUCH more robust CLI system - both interactive and programmatic. You can key in what you want to do, and it’ll prompt you to log in, and then step you through things. There are a few things that are a little clumsy in CLI, but I find many actions to be significantly faster on the command line. You need to jump through a hoop, but you can even stay logged in while your shell session is active, or, if you have an API key, you can just add that to your environment and be authenticated that way.
So when do we get it?? need plesk migration really bad!
any more news ?
Has anyone else found FTP slow on their boxes? I always find it sluggish, not sure if it’s my firewall but I found ProFTPd faster on a Cpanel box, but that could just be me.
Might be worth Iworx having the ability to switch to another FTP server if the admin wishes, a bit like Cpanel does currently.
[QUOTE=gareth25;16118]Has anyone else found FTP slow on their boxes? I always find it sluggish, not sure if it’s my firewall but I found ProFTPd faster on a Cpanel box, but that could just be me.
Might be worth Iworx having the ability to switch to another FTP server if the admin wishes, a bit like Cpanel does currently.[/QUOTE]
Funny you mention this, I was using SmartFTP and uploading to a cPanel box and then moments later I uploaded to a IW box and it was a lot slower. Both the IW and cPanel or on the same pNet in the same data center.
Interesting… maybe it’s worth IWorx looking into that in the new release.
NEW FEATURE that WOULD be unique
I am having a few requests to have not only just “Secondary domains”, but for SEO reasons, Secondary Domains that actually reside on a different Server with a different IP address, and maybe even in a totally different Data Center.
Some of the really good SEO geeks have said that having different IP address associated with your different Secondary(aka Addon for cPanel)will give a slight edge with Google as for as ranking/linking is concerned.
So what would be really nice is to be able to set up a Package in NodeWork that would be able to allocated Secondary Domains on another IW server that is totally controlled by the primary SiteWorx account.
Currently I am doing this manually as I have had several clients of mine ask for this capability. Not sure of all the magic would be involved in getting this done on the programming side, but it sure would put IW way out on the cutting edge.
Can clients finally manage their own DNS zones?
Phobos - MX records, yes, otherwise, no.
R-n-R - That certainly would be unique! It’s not something we’ve considered, though. It seems like it would be difficult to implement, and extremely difficult to implement well. I think you’re on the right track, as you can simply create subdomains as whole SiteWorx accounts. Your clients would then just manage it as though it was an entirely separate domain.
Tim
[QUOTE=IWorx-Tim-Pgh;16129]
R-n-R - That certainly would be unique!.. It seems like it would be difficult to implement, and extremely difficult to implement well.
Tim[/QUOTE]
Ahh, yes, that is what separates the great ones from the rest of the pack, being able to do the things that are hard. I am sure you have heard the saying, “anything worthwhile isn’t easy to do.”
Thanks for the reply Tim
Thanks for the feature request, and the tip R-n-R
Paul
What about native ruby on rails support? or at least the ability to change the path of the document root?
I would like to add this to the WISH list.
The emails the system sends out, allow the server admin (same for the reseller), via NodeWorx, to control the emails the server sends out regarding bandwidth, disk space and any other automated emails that are sent relating to any service on the server. Maybe this could be set up using tiny_mce? Or to be honest a simple text field to manage the emails would suffice.
Thanks for the consideration.
proftpd discussion moved to http://www.interworx.com/forums/showthread.php?t=2931
Feature request:
- Space Report (detailed info about quota/ status of mail users, web space, etc…)
(mail users is the most important, because checking 100 user for the guy that as all que quota :-))