Accessing the Rules Wizard

[MGonz]

Hi,

The problem I'm having is that I have Scalix Web Access to be accessed through the https port with tomcat. The thing though is that whenever someone tries to access the Rules Wizard, it trys to connect to the regular http port, which is closed off. What should I do to fix this?

[ScalixSupport]

This has been covered many times on the forums.

Edit this setting:

swa.settings.rulesWizardURL=

in /etc/opt/scalix/webmail/swa.properties

Regards,
Don

[MGonz]

What do I set to?

I set it to https://mail.domain.com:8443/Scalix/rw and it won't send me there. I added the 's' to http and also added the port but still sends it to a "Could not load" page.

[bwesson]

This has been covered many times on the forums.

Edit this setting:

swa.settings.rulesWizardURL=

in /etc/opt/scalix/webmail/swa.properties

Regards,
Don

Forgive me, but when I make a purchase of a software product and there is a bug, the software company usually declares the problem a bug and fixes it. We purchased the small business edition and I feel that this purchase should entitle us to a bug fix and not a posted work around. So to declare this issue just needs to be edited in some configuration files do not work for me. I'm a busy network administrator and I expect bugs to be fixed and updated in the next release of the product. This post was made in October of 2006 before the release of version 11. It seems to me that the bug should have been fixed in version 11 -- the version I started with and am running now.

The Rules Wizard does not work for those of us that have closed for security reasons Internet access to port 80 and run only on port 443.

Are you guys in support running a business or are you running a chummy club for Linux enthusiast where you are willing to take anyone's money and expect Linux experts are the only people running your software?

[kanderson]

This is a configuration change to a non-standard port. Making that change takes about 30 seconds, including time to restart the service.

As this is a deviation from the standard install, it seems natural to me that it would require some amount of change. This isn't a bug. For 99% of the installs out there, including 100% of the default installs, this works as expected.

Having said that, I think having the installer ask "Do you want this set up to communication via HTTPS or HTTP" is a valid enhancement request. As such, I've raised the following enhanceent request...

http://bugzilla.scalix.com/show_bug.cgi?id=14863

Kev.

[florian]

Dear bwesson,

first of all, thanks for your comments.

With regards to your concerns, I think it is fair to say that indeed we take our customer's issues very serious - I think most of them would confirm this. Also, we certainly run this as a business, with all the consequences.

As you're well aware, it's impossible to create a large-scale software product with no bugs or faults or just things that could be improved; the latter we track as enhancements. I could add some thoughts about complexity theorems and why that is the case, but most would simply acknowledge this as a fact.

Given that we work with finite resources, we have to make careful choices, based on severities, priorities and impact, so that under these adverse operating conditions we provide the best possible value to our customers and clients. For this very reason, we've crafted a sophisticated scheme of checks and balances, where we look at severity, impact, effort and various other factors to determine relative priorities and scheduled targets for working on certain issues.

This effectively means that we will not be able to address every single issue that we know about in "the next release". It's as simple as that. Actually, it's part of my job - and a big part of it - to continously adjust priorities so that we address things in proper order of importance.

Now, for the specific problem reported in this thread, this simply didn't make the cut. It does not qualify to be prioritized very high. It's a simple "default configuration" issue where what the installer sets up is certainly less than ideal for some environments; however, the administrator can change this easily - it probably takes less time to do it than to talk about it. The issue itself was first reported and tracked quite a while ago. Please see http://bugzilla.scalix.com/show_bug.cgi?id=2924 for details. Other things got in front of it and were processed first - and I think rightfully so.

Having said all this, I'm happy to report that Bug 2924 was actually picked up last month and a fix for this will be included in our next monthly release of Scalix 11, scheduled for early April. This was actually done independently of this particular discussion thread. Therefore, once you upgrade to this coming release, and re-run your SWA configuration, the problem will disappear. The new bug that kanderson raised (see his post above) is therefore actually a duplicate and I will close it as such.

If you have any further questions or concerns about this issue, please feel free to contact me directly. You can also purchase and open up a support case with Scalix Tech Support, should you require a faster resolution and want to escalate it. If you need help to implement the workaround, our Professional Services team is also available to help you with this.

Kind regards,
Florian von Kurnatowski
Director Product Management
Scalix Corporation.