We’re happy to announce the release of InterWorx-CP version 1.9.2
This update will be applied automatically within 24 hours if your server has auto-updates enabled (the default). If you choose to perform the update manually we recommend logging into your server as root, and running the command:
If you have any problems with this update please open a Support Ticket
While this is a minor version update, there are quite a few changes worth mentioning.
SpamAssassin Integration Improvements
Both Horde and Squirrelmail webmail systems now have configuration options for some select SpamAssassin preferences, that each e-mail user can set.
SpamAssassin’s auto-whitelist and Bayes database is now automatically set up for each e-mail address.
E-mail users can train their Bayes database by putting Spam and Ham (non-spam) in two special IMAP folders, “Learn Spam” and “Learn Ham”.
Once per day these messages will be used to train the Bayes database, and then deleted.
Each time messages are used to train the Bayes database, the e-mail user will receive an e-mail detailing the results of the training session.
If an e-mail account has an IMAP folder named “Spam”, SpamAssassin tagged spam will be delivered to that IMAP folder rather than the Inbox.
There are two new e-mail settings in NodeWorx that the server manager can use to control the Bayes learning. There is an option to turn the daily Bayes training cron on/off (on by default), and you can limit the number of e-mail messages trained per-folder, each day (since the Bayes training can be resource intensive if there are a lot of messages and a lot of e-mail boxes to train) - default 250.
Backup System Improvements
SiteWorx users can now schedule a backup to happen in one of 3 intervals: Daily, Weekly, or Monthly.
If the server manager doesn’t want the SiteWorx users to be able to schedule backups of their site, this can be disabled editing the /home/interworx/iworx.ini file and changing the line
SiteWorx users can now specify alternate locations for the backup from the default.
The alternate location can be a different location in their account storage space (limited to the siteworx user’s home directory), or it could be a remote location, transferring the backup either via scp or ftp. The user is prompted for a username, password, hostname, and path on the host to transfer the file to.
Server managers with root access to the server can use the command line backup script to accomplish a number of tasks. Here is a listing of the new parameters to this script.
–file-path=/new/path/to/backup/ allows you to specify an alternate path to store backup files
–domains has replaced --domain, and you can use it the following ways:
–domains=singledomain.com (backup 1 account)
–domains=domain1.com,domain2.com,domain3.com (backup multiple accounts)
–domains=all (backup all siteworx accounts)
–scp, scp the backup file to location in either the siteworx transfer.ini file, or in the global transfer.ini file (specified using --transfer-ini=)
–ftp, ftp the backup file to location in either the siteworx transfer.ini file, or in the global transfer.ini file (specified using --transfer-ini=)
this option, used when backing up multiple/all domains, sets a global transfer.ini file to be used. When backing up multiple domains, the individual siteworx transfer.ini files are ignored, and will only transfer the backups if this option is set.
Format of the transfer.ini file:
Other Miscellaneous features or bug fixes
FTP Bandwidth now counts towards each SiteWorx account’s total bandwidth.
Fixed bug with IP address changing (affected multiple domains on the same shared IP instead of just one domain)
Fixed public_html symlink so that it works in FTP clients now.
Fixed bug in Fileman when un-tarring files with very long path or file names.