SSL, webmail disable/enable, POP/IMAP seperate disable

Hi,

I have hundreds of new features I’d like to see in interworx… I’ll start with just a few and as they get added I’ll get to the rest :slight_smile:

One of the more important features I would like to see added is the ability to disable or enable SSL within interworx and webmail. At the moment I am forced to use SSL and interworx’ generated SSL certificate. I don’t mind this for siteworx and nodeworx, but I would like it disabled for horde. Also, It’d be nice if we could specify/generate etc. our own SSL certificates from within interworx. It looks a little unprofessional to our customers when these certificates all come up with interworx.info written all over them :slight_smile:

I’d also like to see the ability to disable/enable POP/IMAP seperately on my box. e.g. I don’t like running IMAP and only use POP mail. At the moment I’ve had to remove imap from my /service directory and svs -d both imap and imap-ssl. The problem now is that even though pop3 and pop3-ssl are still working 100%, nodeworx shows ALL the mail services as being disabled.

Another feature I’d like is: When I make an alteration to one of the packages, the change is also made to all the users currently on that package. i.e. if I decide this month to allow all Basic account users an additional GB of bandwidth and make the change within the “packages” section, all the users on the basic account plan should automatically be allocated an additional 1gb of bandwidth. I hate having to do this manually every time.

There is a bug in siteworx: If you try and add a subdomain, but have exceeded your allotment, you get an error that says, “Can’t add subdoamin” (note spelling mistake!). This should probably be something like: “Can’t add subdomain, you have already exceeded your allotment of x subdomains.”

I’d like interworx to also take into account MAIL bandwidth. At the moment even if a basic account user only has a 2gb bandwidth allotment, they can still receive 1000gb of mail and I would never know. (well, i prolly would, but i would have no way of proving that it’s their bandwidth and then charge them for it :P) The bandwidth calculator should show all bandwidth used by the user, right down to mail, ftp, http and mysql (if that’s possible).

That’s all for now, should keep you busy for a while! :slight_smile: Keep up the good work…


Richard

Re: SSL, webmail disable/enable, POP/IMAP seperate disable

Hi Richard,

Thanks for the feedback. I’ll address your various points below.

Originally posted by dpr
One of the more important features I would like to see added is the ability to disable or enable SSL within interworx and webmail.
InterWorx-CP automatically runs on port 2443 over SSL, but it also listens on port 2080, over plain old HTTP. This means you should be able to just go directly to http://<ipaddress>:2080/nodeworx and have it work. You can make this the default for node/siteworx and webmail by editing the /etc/httpd/conf.d/iworx.conf file, and changing all occurances of “2443” to “2080”. That is probably a reasonable work around for now.

Also, It’d be nice if we could specify/generate etc. our own SSL certificates from within interworx. It looks a little unprofessional to our customers when these certificates all come up with interworx.info written all over them :slight_smile:
Agreed. We’re working on this.

I’d also like to see the ability to disable/enable POP/IMAP seperately on my box. e.g. I don’t like running IMAP and only use POP mail. At the moment I’ve had to remove imap from my /service directory and svs -d both imap and imap-ssl. The problem now is that even though pop3 and pop3-ssl are still working 100%, nodeworx shows ALL the mail services as being disabled.
Understood. At the very least the services display should go into more detail about each mail service, and ideally there’d be more granular control all around for each of these services. Look for this in a future release.

Another feature I’d like is: When I make an alteration to one of the packages, the change is also made to all the users currently on that package. i.e. if I decide this month to allow all Basic account users an additional GB of bandwidth and make the change within the “packages” section, all the users on the basic account plan should automatically be allocated an additional 1gb of bandwidth. I hate having to do this manually every time.
There are good arguments for and against this. The most you could hope for here would be an option on the edit-package screen to perhaps “apply change to all existing accounts”. The problem with this at the moment is that the features for each account is stored independent of any package template that was selected when the package was created. It’s done this way so that you can choose a package for a new account and edit the features of that package on a per-account basis easily. We will give this some more thought though, thanks for bringing it up.


There is a bug in siteworx: If you try and add a subdomain, but have exceeded your allotment, you get an error that says, “Can’t add subdoamin” (note spelling mistake!). This should probably be something like: “Can’t add subdomain, you have already exceeded your allotment of x subdomains.”

I’d personally call this a “vague misspelled error message” rather than a bug :), but you’re definately right. Expect this to be fixed in the next release.


I’d like interworx to also take into account MAIL bandwidth. At the moment even if a basic account user only has a 2gb bandwidth allotment, they can still receive 1000gb of mail and I would never know. (well, i prolly would, but i would have no way of proving that it’s their bandwidth and then charge them for it :P) The bandwidth calculator should show all bandwidth used by the user, right down to mail, ftp, http and mysql (if that’s possible).

Agreed again, we’re aware of this and it is in the plans.

Thank you again Richard, we appreciate the feedback!

Paul

Hi. I would really like to disable the SSL on my server. It has a certificate for interworx.info, so anytime anyone accesses a CP, it says the certificate might be a phishing attempt and warns my users away.

Thanks,
Mark

You can tell users to use your non-secure login page:

http://yourip:2080/siteworx

Or, once you’ve purchased your own SSL cert for the domain of your choice, you can overwrite the contents of

/home/interworx/etc/iworx.crt and
/home/interworx/etc/iworx.key

and then restart InterWorx.

Ok, that worked. Thank you. I just wish there was a way to turn it off so http://www.domain.com/siteworx didn’t redirect to the https:// one… :slight_smile:

Look in /etc/httpd/conf.d/iworx.conf… :slight_smile:

woohoo! It worked! Thanks a ton, Socheat. The issue is IE7. It makes it look like I am stealing everyone’s passwords with the big, giant red X and the pop saying to close the window… <_<

Although I use Firefox. :slight_smile: