IWorx-Paul
03-07-2008, 03:12 AM
This is a minor bug fix release.
The bugs fixed are summarized below.
Servers with auto-update enabled will have this update automatically applied at some time over the next 24 hours. You can do the update manually also. Login to the server as root and run the command:
yum update
* Horde/IMP webmail security hole - This bug was brought to our attention by Alex from Sliqua Enterprise Hosting - thanks Alex!
* ClamAV failed to start and enable on new InterWorx installs.
* "Unknown Error" from Mass Transfer Import due to /usr/bin/expect version change
* Invalid API key fails to generate correct error message in some cases
* Manually adding or editing a MX record that exists under other domain names fails
* Importing an account with secondary domains would "get stuck" in some cases
* Adding a 4th dns-template NS record would add the record incorrectly
* When configuring server as cluster manager, NodeWorx would sometimes report the incorrect IP as the "primary" IP on an interface
* Restarting webserver via NodeWorx interface failed in some cases with the latest apache version
* Maximum non-zero account quota limit was incorrect
* DNS "mutual" synchronization between two servers didn't always sync both ways when IP addresses and not hostnames were used for setting up the sync's
* Misc language string fixes
The bugs fixed are summarized below.
Servers with auto-update enabled will have this update automatically applied at some time over the next 24 hours. You can do the update manually also. Login to the server as root and run the command:
yum update
* Horde/IMP webmail security hole - This bug was brought to our attention by Alex from Sliqua Enterprise Hosting - thanks Alex!
* ClamAV failed to start and enable on new InterWorx installs.
* "Unknown Error" from Mass Transfer Import due to /usr/bin/expect version change
* Invalid API key fails to generate correct error message in some cases
* Manually adding or editing a MX record that exists under other domain names fails
* Importing an account with secondary domains would "get stuck" in some cases
* Adding a 4th dns-template NS record would add the record incorrectly
* When configuring server as cluster manager, NodeWorx would sometimes report the incorrect IP as the "primary" IP on an interface
* Restarting webserver via NodeWorx interface failed in some cases with the latest apache version
* Maximum non-zero account quota limit was incorrect
* DNS "mutual" synchronization between two servers didn't always sync both ways when IP addresses and not hostnames were used for setting up the sync's
* Misc language string fixes