Table of Contents

Release Date: March 2014


Thank you for downloading Scalix 12.1.

Scalix 12.1 is the latest upgrade of Scalix 12, providing important fixes and exciting new features to previous versions. We recommend you upgrade all systems running Scalix to this latest version.

This document includes late-breaking information about product capabilities, known issues and workarounds. Please read this document thoroughly before beginning your installation or upgrade.

For full documentation on how to install, configure and administer Scalix, see the customer documentation at In addition, after Installing the Scalix Mail Server and other applications, you can access the following online help systems, which are embedded in the product:

  • Scalix Web Access Online Help
  • Scalix Management Console Online Help
  • Scalix Connect for Microsoft Outlook Online Help

You also can learn more about any of the known issues listed here - or report others - by going to the Scalix bug tracking system at

Scalix, Inc. is committed to your success with our software. For additional information above and beyond what is provided here and in the official product documentation, visit the Scalix Forums at

Customers who have purchased support from Scalix also may also contact Scalix Technical Support to request help, ask questions about how to use a particular feature, provide feedback, or report bugs by visiting



Starting with version 11.3 Scalix Connect for Outlook now includes software developed by the OpenSSL project for use in the OpenSSL toolkit. ( It also includes cryptographic software written by Eric Young (This email address is being protected from spambots. You need JavaScript enabled to view it.) and software written by Tim Hudson (This email address is being protected from spambots. You need JavaScript enabled to view it.). Scalix would like to thank these individuals and the OpenSSL community for their valuable contributions.

Starting with version 11.3 Scalix Server now includes software based on the Universal Character Set Detector from the Mozilla project (, written by Simon Montagu (This email address is being protected from spambots. You need JavaScript enabled to view it.), Shy Shalom (This email address is being protected from spambots. You need JavaScript enabled to view it.), Shoshannah Forbes and others. Scalix would like to thank these individuals and the Mozilla community for their valuable contributions.

Installation issues

  • The following procedure/adjustments are mandatory if you installed CentOS6 (64bit) or ORACLE Linux 6 (x86/x64)
    • If port 80 is not set to allow connections (open) in ip tables, Tomcat will not work at all - scalix-tomcat service will run, but in the tomcat log there will be a big backtrace
      • Open port 80 in iptables
      • restart the iptables service
      • restart the scalix-tomcat service
      • restart the httpd service
    • After this it should be working correctly
    • Secondly initialization of all web applications in tomcat can take over 20 sec - tomcat will work only after initialization of its webapps. If you make changes to tomcat such as above, please also restart apache (service httpd restart).
  • Due to license limitations the Oracle JRE is not packaged together with Scalix anymore. You need to have installed and verify that the JRE is installed properly and no libraries are in conflict.
  • On OpenSUSE 13 for x64, the package 'libglib-2_0-0-32bit' must be installed manually before installing 'scalix-server' to avoid the error '/opt/scalix/bin/omcheckgc: error while loading shared libraries: libglib-2'.
  • On Debian 7 for x64, if the OS is upgraded to 7.4 after installing 'scalix-server' sucessfully, the OS may report inconsistent package dependencies that require removal of 'scalix-server' package to fix.
  • On Debian and Ubuntu, only the default Scalix Community Edition license is active, other Scalix licenses are not recognized and supported by this release (will be changed with scalix 12.2).


Important end of Life Notices

When running Scalix in a mixed-version multi-server setup, where your front end servers are running SWA 12.1 and the back end servers have to be upgrade to at minimum version 12.1 as well.

·         Scalix 12 is the last release of Scalix to provide support for SuSE Linux Enterprise Server 10 (SLES 10). We recommend that you upgrade to SuSE Linux Enterprise Server 11 (SLES 11) to prepare for the release and upgrade to Scalix 13.

·         Scalix 12 is the last release of Scalix to provide support for Red Hat Enterprise Linux Server 5 (RHEL5). We recommend that you upgrade to Red Hat Enterprise Linux Server 6 (RHEL6) to prepare for the release and upgrade to Scalix 13.

·         Scalix is halting development of Scalix Connect for Outlook versions 12 (Outlook 2007) and earlier Outlook versions in Scalix 12. We recommend that you upgrade to Outlook 2010 or Outlook 2013. Note that we will continue to provide support on the basis of a frozen connector version, however, no new functionality in Scalix Connect will be made available for these platforms.


Upgrade Notices

Please read the following notes very carefully, as some specific actions might be required as you upgrade from earlier versions of Scalix.

Upgrading from any previous version

If you are upgrading from a previous version of Scalix, there are several changes of which you should be aware of:

  • Before beginning any upgrades, check your license key. If you are upgrading to or from a Small Business Edition (SBE), Enterprise Edition (EE) or Hosting Edition (HE) installation, you need to have a valid and current license key with a "Last Valid Issue Date" (LVID) on or after 1 October 2013 (2013-10-01) to use Scalix 12. If you continue installation after the respective warning and the license is not valid, your installation will downgrade to Community Edition. To check the LVID of your license, use the Scalix Management Console or the sxlicense command. To extend your upgrade subscription or get a new license key, please contact Scalix Sales.
  • It is NOT supported to run Outlook with an older Scalix Connector version against a newer server, It is not supported to run Outlook with a newer Scalix Connector version against an older server, e.g. you cannot run Scalix Connect for Outlook 12 against a Scalix 11.x server. You must always upgrade all your servers first before upgrading Scalix Connect for Outlook.

Upgrading from a previous version of Scalix 11.4 or earlier

Please note the following:

  • If you are using omldapsync to manage Scalix users and groups through an external directory:

·         Scalix version 12.x is currently forced to come WITHOUT Java, Oracle Java Runtime Environment due to Oracle licensing restrictions. The Scalix Tomcat installation will NOT automatically use the local installation of your current Java version, and will need to have its JAVA_HOME variable set. Any existing sync agreements for omldapsync, stored in /var/opt/scalix/<instance>/s/ldapsync/ <sync_agreement_name>/sync.cfg, will need to be updated manually to reflect the new version.

·         tomcat _uses_ default java unless you set custom JAVA_HOME in config.

·         If you are upgrading your Server to Scalix 12.1.0 or later from any previous installation of Scalix 11 and if you have changed the SMTP Relay configuration in smtpd.cfg you need to manually integrate the changes you made into the new smtpd.cfg after finishing the upgrade.

  • If you are upgrading from 11.4.x or earlier to 12.1.0 or later, it is recommended that you empty your IMAP caches by running the following command on your backend server. Please note that this command may only be run when nobody is signed on to the system (when the rci and IMAP services are off):
    • cd $(omrealpath "~/"); find user* -name imap-cache -exec rm -rf {} \;

Upgrading from Scalix 11.3 or earlier is not supported.



Features & Supported OS

Scalix 12.1 provides the following features:

General (Server+Installer) features/support:

General (Server+Installer) REMOVED features/support (End-of-life):

  • Support of RHEL4
  • Support of CentOS4
  • Support of SLES9
  • Support of Outlook 2003 and older Outlook releases (MAPI may still work but is not tested by scalix anymore)
  • Removed WAP and PAW web profiles
  • Installer SSL configuration

Scalix Web Access

  • Support for Firefox 27
  • Support for Internet Explorer 9, 10 and 11
  • Support for Chrome
  • Support for Safari
  • Overlay Calendars
  • Smarthost SMTP-Authentication support

Scalix Connect for Outlook

  • Outlook 2007/2010/2013 (32bit) Support on Windows 7/8 (32bit and 64bit)
  • Outlook 2007/2010/2013 Support on Windows Terminal server 2008 R1/R2 (32bit and 64bit)
  • Outlook 2007/2010/2013 Support on Windows Terminal server 2012 R1/R2 (32bit and 64bit)
  • SmartCache is completely rewritten and back as part of this new release
  • Outlook 2013 64bit support (beta!) on all supported Windows OS.
  • Speedup of Scalix Connect




Scalix 12.1

Scalix Connect for Outlook

  • Memory error on closing Outlook.
  • Folder Properties (SXACLExtension)
    In offline mode, acl property page is displayed, so a message comes up, that Outlook is in offline mode.
  • Outlook Options (SXDelegatesExtension)
    In offline mode, Delegates property page is displayed, so a message comes up, that Outlook is in offline mode.
  • Outlook 2010/2013 Add-In loading issues
  • Outlook 2007 freezes on accepting meeting requests
  • Installer sometimes do not register Extended Menu Extensions correctly
  • Ribbon Bars do not work on Windows 8
  • A wide range of performance and stability related bugs got resolved as part of the overall MAPI code overhaul (to much to list)

Scalix Server

  • Bug 50015 – Internet Gateway (unix.out) crashes when sending Meeting Requests (RHEL6 only)
  • Bug 50013Debian dependencies bugs
  • Bug 50017 – Installer missing dependencies bug

Scalix SAC

  • German Umlauts bug of Scalix 12.1


Scalix 12.1

Scalix Server

  • Bug 16241 - omslapd sends log information to syslog instead of scalix log
  • Bug 21415 - Notification handling can cause performance issues when there are large Public Folders
  • Bug 21308 - Errors after renaming Proxy Folders using SWA/IMAP client
  • Bug 21410 - Option to prevent BES client from reactivating appoinment reminder
  • Bug 21198 - Notification message was not displayed in Inbox.
  • Bug 21280 - OutTray container with negative component count prevents Outlook mailing
  • Bug 19503 - Incorrect MIME generated for PDF attachment
  • Bug 12753 - Error when opening an appointment in SWA, previously modified in OL
  • Bug 19890 - Server does not record UserFolder changes in the sync log for SmartCache
  • Bug 21281 - Reduce load on servers with lots of active users and lots of group ACLs on Public Folders
  • Bug 21294 - Truncated MIME produced (and ERRORs) when a msg has a missing 'delivery envelope'
  • Bug 20326 - Attachment filename provided in name=attribute should not be discarded
  • Bug 20493 - Server should sanitize messages with invalid Content-Transfer-Encoding
  • Bug 20515 - mime content-disposition sometimes has filename= twice
  • Bug 18759 - LDAP search is broken when | (OR) operator is used with omMailnode filter
  • Bug 21267 - Ability to delete messages from a Queue by Subject
  • Bug 21525 - ldapmapper fails to start on SLES 11 platform
  • Bug 17890 - sxmboxlist fails for some public folders
  • Bug 21167 - Some sxmbox* commands can not find users by user name.
  • Bug 21023 - sxmboxexp - segmentation violation exporting Public Folders
  • Bug 20782 - sxmbox* exits with Error Code 10 and prints message-catalog related error message
  • Bug 241 - Deferred delivery messages from sendmail - where to put them?


For a list of Fixes/Changes of Scalix 11 and previous versions, please check the related release notes listed at


Supported Environments

Scalix 12.1 is supported on the following platforms:

Scalix Server+Installer:
Scalix Connect for Outlook:
  • The following combinations of Windows and Outlook are supported
Component Outlook version (32bit) Outlook version (64bit) BETA
XP 32bit SP3 2003 SP3, 2007 SP2, 2010 -
XP 64bit SP2 2003 SP3, 2007 SP2, 2010 -
Vista 32bit SP2 2003 SP3, 2007 SP2, 2010 -
Vista 64bit SP2 2003 SP3, 2007 SP2, 2010 -
Win7 32bit 2007 SP2, 2010, 2013 -
Win7 64bit 2007 SP2, 2010, 2013 2013
Win8 32bit 2007 SP2, 2010, 2013 -
Win8 64bit 2007 SP2, 2010, 2013 2013
Win 2008 R1/R2 Terminal Server 32bit 2010, 2013 -
Win 2008 R1/R2 Terminal Server 64bit 2010, 2013 2013
Win 2012 R1/R2 Terminal Server 64bit 2010, 2013 2013

·         NOTES:

o   Other combinations of Service Packs may work also but are not part of our QA process.

o   Scalix Web Access and Scalix Management Console: IE9, 10 and 11 on Windows; Firefox 27.0 on Windows, Mac OS/X or Linux. Other browsers based on the IE and Gecko engines may work. Chrome 31.0 on Windows, Mac OS/X or Linux.

System Requirements:

Please the Scalix Installation guide for current minimum system requirements.


Note that the choice of storage environments will have a major influence on performance of your Scalix system. Scalix as an application is largely I/O-bound, using variable, small-blocksize random read/write synchronous file I/O.

Also note that Scalix does not support putting a Scalix Message Store on a NFS- or SMB-based storage device such as a NAS Filer. Performance issues and/or Message Store corruption can occur. This is true for all Linux distributions using Linux 2.6.x kernels as the NFS client software in these kernels have known issues with file locking operations, which Scalix heavily relies on.

We suggest putting the Scalix message store on a Hardware RAID Array, using RAID 1+0 for best performance. The use of RAID 5 or RAID 6 will result in substantially worse performance due to the nature of Scalix Disk I/O patterns (small, synchronous random writes) and is not recommended. In larger installations, we do recommend using iSCSI- or FibreChannel-based SAN storage. We also recommend the use of battery-backed write cache on the RAID controller where available



The Scalix 12.1 Release consists of a self-extracting shell archives for Linux and a separate ZIP file download for the Windows components.

The Components in the package and their respective version numbers are as follows:




Scalix Installer

Linux .bin


Scalix Server

Linux .bin

Scalix Character Set Detectors

Linux .bin


Scalix Libical

Linux .bin


Scalix iconv Extras

Linux .bin


Scalix Management Services (SAC, RES)

Linux .bin

Scalix Messaging Services ("Platform")

Linux .bin

Scalix Web Access (SWA)

Linux .bin

Scalix Mobile Web Client (Mobile)

Linux .bin

Scalix Search and Indexing Services (SIS)

Linux .bin

Scalix Text Extractors for Indexing and Search *

Linux .bin


Scalix DB (Postgres)

Linux .bin

Scalix Tomcat Connector

Linux .bin

Scalix Tomcat

Linux .bin


Scalix Connect for Evolution**

Linux .bin

Scalix Connect for Outlook

Windows .zip


Scalix Migration Tool (SMT) ***

Windows .zip

Scalix Active Directory Extensions (ADE) ****

Windows .zip


* Text extractors allow the indexing of binary Microsoft Office (Word, Excel and PowerPoint) and PDF documents. They are only available as part of Scalix Small Business Edition (SBE) or Enterprise Edition (EE)
** For Scalix Community Edition downloads, Scalix Connect for Outlook (MAPI) is a separate ZIP-file download.
*** The Scalix Migration Tool is a separately-sold product to migrate eMail, Calendar, Contacts and other objects from Exchange 5.5, 2000, 2003 to Scalix. Please contact
Scalix Sales for details.
**** The Scalix Active Directory Extensions are only available as part of Scalix Small Business Edition (SBE) or Enterprise Edition (EE)



Known Issues and Workarounds

Scalix Admin Tools




JRE for omldapsync


Unable to change password for sxadmin.

Workaround: Have administrative users change their passwords in their clients before accessing the management console, remove the pre-set flag on the command line (ommodu with a -E option) or avoid the use of pre-expired passwords entirely


when creating a mailnode using the Mailnode screen in SAC, public folder structure in hosting mode is not created and users cannot login.

Do not create the Hosted Mailnode using the Mailnode Screen in SAC; use the provided SAC Hosted Mailnode plugin instead. In Scalix 11.5, the functionality will be fully embedded into SAC and the plugins will go away


Default values for LDAP size limit inadequate

The size limit for LDAP queries in SAC may be insufficient for even simple installations. The default will be raised in a future release. The limit can be manually adjusted in if the said error appears

Scalix Server





Umlauts in passwords do not work correctly

It is recommended not to use non-ASCII characters in passwords. For best security and compatibility, use a combination of ASCII characters, numbers and special characters. non-ASCII characters in passwords are subject to client processing and are not likely to work across different clients


ommodu --resource Y does not create calendar folder and set calendar permissions

It is not recommended to change a normal user to a resource. Delete the user mailbox and create a new one, which will have the calendar folder setup. Otherwise, you'll have to log-in to a calendar-enabled client with the user and setup folder permissions on the Calendar manually


LDAP server should disable anonymous binds by default to allow for better security

The desired effect can be achieved by setting LDAP_MUST_AUTHENTICATE=TRUE in general.cfg


sxhostcfg script silently assumes sxadmin as admin username and fails if that's not the case

For Scalix 11.4, the default admin username ("sxadmin") must be accepted during installation for Hosting mode to work correctly. In Scalix 11.5, this restriction no longer applies as Hosting edition setup works differently altogether


sxaa: An applied filter including non-ascii characters is not effective.

This will be fixed in a future release of Scalix


omtidy omtidyallu options -d -w0 cause problems

The combination of options will be disabled in a future release of Scalix and should be considered unsupported and deprecated


RSS ProxyFolder should keep history of entries independent of server feed content

The behaviour will change in a future release of Scalix


FREEBUSY not working properly in iCal

Currently, Free/Busy data is published by F/B-enabled clients like Outlook and SWA. The functionality will move to the server in Scalix 11.5, allowing non-F/B-publishing clients to work correctly


Some special characters not allowed in Proxy Folder names

Do not use any of these characters in proxy folder names: "[", "]", "$", "%", "*", "#" or "/"


Can't recognize CJK user names in Proxy Folder setup

Find out the ASCII version of the Scalix username (as per omshowu) and use this to create the proxy folder as a workaround


omscan server cycle will not run if time was in the future during last cycle

Reset the Server Cycle timer using omscan -Z


sxdu -r should automatically correct wrong recovery folder size.

The wrong size information can be corrected by running omscan in "-S" fix mode and then deleting another item, so that it gets added to the recovery folder. Future versions of Scalix will automatically correct the wrong information


Allow for unlimited number of elements in a folder, including Inbox.

Scalix 12 will eventually allow for an unlimited number of items in each folder. For Scalix 11, the limitations are 128K (=131072) items per folder (including subfolder entries, but NOT including subfolder items) and 32K (=32767) when Outlook is supposed to access the folder using Scalix Connect


ommodpdl fails when CN has more than 40 characters

Use PDL names shorter than 40 characters


Duplicate sub-Folders Created in BB device after moving messages in SWA.

This is a known issue with Scalix Connect for Blackberry Enterprise Server. It will be fixed in a future release

Scalix Messaging Services





Cannot authenticate against Messaging Services, CalDAV or ActiveSync when password contains ":"

Use passwords not containing a colon character when using one of these services


CalDAV should allow viewing of attachments

This functionality will be added in a future release of Scalix


CalDAV scheduling POST to Outbox should result in message in Sent Items

This will be improved in a future release of Scalix, as the CalDAV-Scheduling standard evolves towards a full RFC

Scalix Web Access





Folder name having greater then (<) and (>) lesser then sign are not displayed in folder tree

Do not use "<" and ">" characters when naming folders for use in SWA


Invoking SWA within a frameset yields erroneous error message

Using SWA inside a frameset is currently not supported. A future version of SWA will be made more portal-friendly


Attaching file having semicolon in filename removes all the earlier attachments.

Using semicolons in attachment names is not supported for SWA. The behavior will be improved for a future release


SWA appears to allow changes to read-only Proxy Folder

Future versions of SWA will display proxy folders differently and not allow changes using UI limitations


SWA test button should trigger browser prompt to install appropriate media plugin on IE7

Correct Media plugins must be installed manually before the SWA session for SWA to play sounds correctly on receiving email


Folder names with ! don't work in SWA, do in Outlook, cause issues in sxmboxexp/imp

Do not use folder names containing exclamation marks ("!") to be able to use a folder in SWA


Can't open attachment with apostrophe in the file name

In Internet Explorer and when running on Vista, files with apostrophes in the name cannot be opened when received as an attachment. This will be fixed in a future release. As a workaround, please re-send the file with the attachment renamed. In general, it is not recommended to use filenames with special characters for attachments


Search Result Pane returns blank window, when pop-up blocker is turned on.

The search window will be integrated into the main window in a future release of Scalix. Popup handling will be improved. For the time being, popup blocking must be fully disabled for SWA to work correctly


Keep getting "Your request to the server has timed out. Keep trying?" popup message.

Scalix 11.5 will vastly improve on SWA used bandwidth and how timeouts are managed. The number of occurrences of this (valid) timeout will be reduced


SWA fails to send mail to the PDLs having special characters in their names.

Certain special characters like double quotes ("), ampersand (&), angle quotes (<>) or semicolon (;) should not be used in the display name of a personal distribution list in the SWA contact folder; otherwise, it will not be possible to send email to these distribution lists

Scalix Connect for Outlook





Extended Japan Support ISO-2022-jp does not work yet

Will be fixed in Scalix 12.2


Outlook 2010/2013 sometimes freezes on accepting meeting requests IF there are two users with the same CN on a server.

Will be fixed in Scalix 12.2


OLE embeded objects are not viewable on the message in the Sent Items folder

The use of embedded OLE objects is not supported with current versions of Scalix Connect


MAPI limits number of items displayed in a folder to the first 32767

Currently, only the first 32767 items in any folder can be accessed through Outlook/MAPI. This limit will be lifted in a future release of Scalix


Subject displays empty in sent items folder when mail sent with more than 178 i18n chars.

This issue will be resolved in future versions of Scalix


Scalix (Outlook) Help doesnt show up on Vista and Windows 7.

Online help for Scalix Connect for Outlook is currently unavailable on Windows Vista. This will be fixed in a later release


System address book cached copy should be updated on change

User must wait for the AB_DOWNLOAD_INTERVAL to expire and/or restart Outlook for Address Book Changes to be propagated to SmartCache


Support for "To-Do Bar" search for Tasks on Outlook 2007

This feature of Outlook 2007 or higher will be supported in Scalix 11.5


When searching in Outlook the "search in subfolders" option is ignored for subfolders with special characters in their names.

The behavior will be improved in a future release of Scalix. It is not recommended to use non-ascii characters in folder names for maximum client compatibility



"Recall message" functionality should be supported with Scalix Connect.

This may be implemented in a future release of Scalix. It should be noted, however, that the funtionality is only weakly implemented in Outlook, as in many cases only a "Disregard previous message" message can be provided


Repairing connector installation gives outlook information store error.

Do not use the "Repair" option at this time. If there are any issues with the installation of Scalix Connect for Outlook, uninstall and re-install the connector


Regression: Setup.exe uses CPU more than 95% while setup is triggered from shared folder.

This is a known issue with the Scalix Connect for Outlook installer. Copy the setup.exe file to a local drive before launching the installer


Progress indicator sometimes not visible or updated on OL12

This issue happens rarely with Scalix Connect for Outlook 11.4.5


iTunes does not support sync with iphone using iTunes OutlookSyncClient

Support for wired synchronization using Outlook and iTunes will be supported in Scalix 11.5. Scalix ActiveSync, providing for Push Email and wireless calendar and contact synchronization, could be used as a better alternative


Outlook Connect does not install if filename is renamed in Vista

Leave the filename of the installation image as Setup.exe


Outlook 2003 used right after intallation can report error: "Unable to open default email folder..."

Start Outlook once and activate it before using it with Scalix Connect


WDS: Support indexing of non-cache profiles and ensure it scales appropriately

As of Scalix 11.4.5, Windows Desktop Search will correctly index SmartCache profiles. Future versions will enable non-cached profiles to be indexed as well


Support for Blackberry Desktop Manager

Blackberry Desktop Manager v4.1 and v4.2 can be enabled to work with Scalix using a patch to those products provided in the "extras" folder of the Scalix Connect distribution. Future versions of Scalix connect will support BBDM without such a patch


Scalix Connect to support Google Desktop Search

A future version of Scalix Connect will support Google Desktop Search. Use Windows Desktop Search with Scalix Connect 11.4.5 or higher as a workaround

Scalix Installation





Unable to login into Mobile Web Client after reconfiguring only DB/only messaging services

When reconfiguring either of these components, choose all components to be reconfigured


Installation fails if hostname contains uppercase characters.

Use a hostname for your scalix server consisting of all-lowercase characters


Installer should be smart enough to handle running scalix server with license upgrade during installation

If you need a different Scalix license key after a planned upgrade, install that license key before running the installer to upgrade the software


Custom Install path to rpms in graphical installer does not support spaces in directory name

Do not unpack the Scalix package into a directory that has spaces in any component. This issue is fixed in Scalix 11.5/p>


On SLES10 64-Bit, has undefined symbol: proxy_module

This is caused by the Novell/SuSE setup putting the module lines in the configu file in wrong order. Manually check /etc/init.d/apache2 and make sure that the APACHE_MODULES entry contains all of "proxy", "proxy_ajp" and "proxy_http", in this order, correct it if necessary and restart Apache