Scalix 11.4 - Release Notes $Rev: 264 $

Release Date: 22 May 2008


Contents




Introduction

Back to top

Thank you for downloading Scalix 11.4.

Scalix 11.4 is the latest release of Scalix 11, providing new functionality, updated platform support as well as several important enhancements and fixes to previous versions. We recommend you upgrade all systems running Scalix 11 to this latest release.

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 http://www.scalix.com/documentation. 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:

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 https://bugzilla.scalix.com/.

Scalix Corporation 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 http://www.scalix.com/forums/. 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 sending email to support@scalix.com.



Acknowledgments

Back to top

Starting with version 11.3 Scalix Connect for Outlook now includes software developed by the OpenSSL project for use in the OpenSSL toolkit. (http://www.openssl.org). It also includes includes cryptographic software written by Eric Young (eay@cryptsoft.com) and software written by Tim Hudson (tjh@cryptsoft.com). 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 (http://www.mozilla.org), written by Simon Montagu (smontagu@smontagu.org), Shy Shalom (shooshX@gmail.com), Shoshannah Forbes <xslf@xslf.com> and others. Scalix would like to thank these individuals and the Mozilla community for their valuable contributions.



Important End of Life Notices

Back to top

Scalix 11.4 is the last release of Scalix to provide support for SuSE Linux Enterprise Server 9 (SLES 9). We recommend that you upgrade to SuSE Linux Enterprise Server 10 (SLES 10).

Scalix is planning to freeze development of Scalix Connect for Outlook for Outlook versions 9 (Outlook 2000) and 10 (Outlook XP/2002) in one of the next releases of Scalix. We recommend that you consider upgrading to Outlook 2003 or Outlook 2007. 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.

Scalix is committed to both providing programmatic access to the system as well as to promote the use of open standards. With Scalix 11.3, we released support for CalDAV (RFC 4791) and will continue to enhance Scalix WebDAV capabilities in future releases. As there is significant overlap between the technologies, we are considering to halt further development and then later remove support for Scalix REST-based Messaging Services APIs, which use proprietary interfaces and data formats. If you are using Scalix Messaging Services for your application development, we recommend investigating into updating your code to use CalDAV/WebDAV interfaces instead. No date has been set for this change yet.


Upgrade Notices

Back to top

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

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

If you are upgrading Scalix Connect for Outlook to version 11.4 from any previous version of Scalix Connect for Outlook 11, there are several things to be aware of:

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

          Change
                        JAVA_HOME=/usr/java/jre1.5.0_06
          or
                        JAVA_HOME=/usr/java/jre1.5.0_11
          to
                        JAVA_HOME=/usr/java/jre1.5.0_13

If you are upgrading your server to Scalix 11.3 or later from any previous installation of Scalix 11, there are a number of new packages supporting Scalix Server:

If you are using Scalix Community Edition and you are upgrading your server to Scalix 11.3 or later from any previous version of Scalix, please note that the number of free Premium User licenses has changed from 25 to 10.

If you are upgrading your Server to Scalix 11.4 from any previous installation of Scalix 11 and if you have changed the SMTP Relay configuration in smtpd.cfg your changes will be saved in Osmtpd.cfg since Scalix 11.4 delivers a new version of smtpd.cfg. You need to manually integrate the changes you made into the new smtpd.cfg after finishing the upgrade.

On Windows Vista auto upgrading to Scalix Connect for Outlook 11.4 from version 11.3 will not work. You need to manually install the new connector.

Please also check the Scalix 11 Upgrade FAQ on the Scalix Wiki.


New in Scalix 11

Back to top

New Features in Scalix 11.4

Scalix 11.4 provides the following new features:

General

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook (for Scalix "Premium" users only)

* Running Outlook 2003 and Outlook 2007 on Vista 64bit is subject to a number of issues and known limitations. Please see Bug 17250 for details.

New Features in Scalix 11.3

Scalix 11.3 provides the following new features:

General

Licensing

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook (for Scalix "Premium" users only)

New Features in Scalix 11.2

Scalix 11.2 provides the following new features:

General

Server

Scalix Connect for Outlook (for Scalix "Premium" users only)

New Features in Scalix 11.1

Scalix 11.1 provides the following new features:

Scalix Server

Scalix Web Access

Scalix Connect for Outlook (for Scalix "Premium" users only)

Scalix Connect for Evolution

New Features in Scalix 11.0

Scalix 11 includes many new product features and improvements across all product components:

Scalix Mail Server

Scalix Web Access

Scalix Connect for Outlook (for Scalix "Premium" users only)

Mobility

Management and Administration (Scalix Management Console)

Services Architecture

Internationalization and Localization

Scalix Search and Indexing Service

Note: This product includes a 'phone home' feature, which, for Community Edition installations, summarizes basic server and installation information such as platform type and number of users, and periodically sends it back to Scalix via email. This information helps Scalix to track product usage statistically and better plan our upcoming releases. The information is also sent by email to your administrator account so that you can confirm that the content is simple, transparent and non-sensitive. Except where disallowed by local statute, it is a violation of the licensing conditions to disable or circumvent this feature. Installing a Small Business or Enterprise Edition license key deactivates this feature.

Note: Group scheduling features and public folders in Scalix Connect for Evolution are available only to Scalix Premium users, not Standard users.



Bugs fixed in Scalix 11.x

Back to top

Fixed in 11.4

The following issues have been addressed in Scalix 11.4:

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook

Scalix Installation

Fixed in 11.3 U1

The following issues have been addressed in Scalix 11.3 U1:

Scalix Web Access


Fixed in Scalix 11.3

The following issues have been addressed in Scalix 11.3:

Scalix Admin Tools

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook


Fixed in Scalix 11.2

The following issues have been addressed in Scalix 11.2:

Scalix Admin Tools

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook

* 'scalix-text-extractors' are only available for Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)


Fixed in Scalix 11.1.0

The following issues have been addressed in Scalix 11.1.0:

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook

Scalix Installation


Fixed in Scalix 11.0.4

The following issues have been addressed in Scalix 11.0.4:

Scalix Server

Scalix Messaging Services

Scalix Search and Indexing Services

Scalix Web Access

Scalix Connect for Outlook

Scalix Installation

* Indexing of binary attachment types (Word, PowerPoint, Excel, PDF) is only available for Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)
** The Recovery Folder feature is only available for premium users in Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)


Fixed in Scalix 11.0.3

The following issues have been addressed in Scalix 11.0.3:

Scalix Admin Tools

Scalix Server

Scalix Messaging Services

Scalix Web Access

Scalix Connect for Outlook

Scalix Installation

Scalix Migration Tool

* The Scalix Migration Tool (SMT) is a separate product for migrating user data from Exchange 5.5, 2000, 2003 and 2007 to Scalix. Please contact Scalix Sales at info@scalix.com for further information.
** The Recovery Folder feature is only available for premium users in Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)
*** Indexing of binary attachment types (Word, PowerPoint, Excel, PDF) is only available for Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)


Fixed in Scalix 11.0.2.1

The following issues have been addressed in Scalix 11.0.2.1:

Scalix Server


Fixed in Scalix 11.0.2

The following issues have been addressed in Scalix 11.0.2:

Scalix Admin Tools

Scalix Server

Scalix Web Access

Scalix Mobile Web Client

Scalix Connect for Outlook

Scalix Installation


Fixed in Scalix 11.0.1

The following additional issues have been addressed in Scalix 11.0.1:

Scalix Web Access

Scalix Connect for Outlook

Scalix Installation

Scalix Search and Indexing Services

Scalix Server


Fixed in Scalix 11

The following issues have been addressed in this release:

Scalix Admin Tools

Scalix Web Access

Scalix Connect for Outlook

Scalix Server

Scalix Installation

Scalix Active Directory Extensions



Supported Environments

Back to top

Supported Linux Platforms

Scalix 11.4 is supported on the following platforms:

System Requirements

Please check the Scalix Installation guide for current minimum system requirements.

Alert

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 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.



Packaging

Back to top

The Scalix 11.4 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:

Component

Package

Build

Scalix Installer

Linux .bin

11.4.0.2476

Scalix Server

Linux .bin

11.4.0.11669

Scalix Character Set Detectors

Linux .bin

1.0.20071031

Scalix Libical

Linux .bin

0.27.20071008

Scalix iconv Extras

Linux .bin

1.2

Scalix Management Services (SAC, RES)

Linux .bin

11.4.0.4501

Scalix Messaging Services ("Platform")

Linux .bin

11.4.0.1922

Scalix Web Access (SWA)

Linux .bin

11.4.0.11344

Scalix Mobile Web Client (Mobile)

Linux .bin

11.4.0.872

Scalix Search and Indexing Services (SIS)

Linux .bin

11.4.0.1030

Scalix Text Extractors for Indexing and Search *

Linux .bin

1.0

Scalix DB (Postgres)

Linux .bin

11.4.0.1922

Scalix Tomcat Connector

Linux .bin

11.4.0.891

Scalix Tomcat

Linux .bin

5.5.25-415

Scalix Connect for Evolution

Linux .bin

11.4.0.82

Scalix Connect for Outlook

Windows .zip

11.4.0.7614

Scalix Migration Tool (SMT) ***

Windows .zip

11.4.0.590

Scalix Active Directory Extensions (ADE) ****

Windows .zip

11.4.0.746


* 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

Back to top

Installing the Scalix Mail Server requires Linux system administration skills and root access to the server. Coordination with your site networking team is also required to ensure that workstations are able to connect to the server (through TCP/IP sockets) and that the server itself is visible to the network, including any necessary DNS/MX configuration. If the network uses Firewalls and/or VPNs, then additional modifications to the network might be necessary to enable the required network connections to the appropriate ports on the server, as described in the Scalix Installation Guide.

Back to top

Scalix Installer

Issue

Workaround

If you installed SLES 9 on the Scalix server host, the python-gtk-2.0.0-215.1 package automatically installs. This version of the package forces the Scalix Installer to display the following error message:

Error: Please upgrade python-gtk package to version 2.0.0-215.3 or newer, currently installed version 2.0.0-215.1 contains a bug that affects Scalix Installer.

Exit the Scalix installer and use YaST to upgrade the python-gtk package by the means provided by SLES 9.

After installation, the automatic launch of the Scalix Management Console can sometimes be accompanied by a series of error messages saying, "Shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory." Ignore these messages. The browser launches anyway. (Bug 4754)

None.

Reconfiguring the Messaging Services or the PostgreSQL Database Integration with the Installation Wizard upgrade process can, in some cases, cause users to be locked out when they later try to sign in to the Scalix Mobile Web Client. (Bug 13947)

If the PostgreSQL database password changes, it must also be changed in the file, platform.properties, which is located at <instance>/platform/platform.properties. This requires a restart of Tomcat. If the database is on a separate server from the platform, this change must be done manually.

Installer quits without warning if "dig" is not available (Bug 15771)

make sure that dig is installed. On most distributions, this is part of the "bind-utils" package.

When replacing an existing Scalix SBE or EE license during upgrade installation, sometimes the Scalix Server is not restarted properly and the license manager will die unexpectedly (Bug 15770)

Check the status of the license monitor using the "omstat -a" command. If not running or aborted, restart the server using "omshut" and "omrc".

ommakeom quits if hostname contains uppercase characters. (Bug 15014)

Do not use uppercase characters when configuring the hostname.

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

Create an admin user named sxadmin.

When performing a custom install the Forward button may not respond after selecting some components to be installed (Bug 16083)

When selecting "Scalix Server" make sure to also select "Scalix Libical" and "Scalix Character Set Detection".

 


Back to top

Scalix Mail Server

Issue

Workaround

After upgrading Scalix Mail Server from Scalix 10 to Scalix 11, users with a large number of messages in their email client folders might notice reduced client/server performance when they access the message store. This is caused by upgrades to the message store container file structure that occur when they are next accessed by a user (through the client UAL process or the local delivery service).

To control when the upgrading of the message store happens so that it doesn't slow down mailbox access, shut down the Scalix Mail Server after upgrade and with only the daemons running (omrc -n), run the commands omtidyu and omscan without the fixmode (-f) option. For example, enter: omtidyallu -M and omscan -Aa.


Note: The first time it runs after an upgrade, omscan can take twice as long as is typical because it is upgrading message store containers. Scalix recommends that you perform this task in off hours (nights or weekends) to minimize impact on the Scalix Mail Server.

If you've installed your Scalix system on host(s) running SUSE Linux Enterprise 9 (SLES9), your Outlook users will not be able to take advantage of single sign on because of a flawed Kerberos interaction between SUSE and Microsoft inherent in the Heimdal Kerberos implementation provided with SLES9.

Upgrade to SUSE Linux Enterprise Server 10 (SLES10) which uses a MIT Kerberos implementation.

[iCal Information] --

  • Exchange 5.5 does not support iCal, therefore SWA-generated meeting requests and meeting requests sent from Outlook/Exchange using the "Forward as iCalendar" do not work correctly.
  • A canceled meeting scheduled via iCal shows as "Tentative" rather than "Free".
  • Outlook 2002 (Outlook 10) with an IMAP profile does not recognize iCal messages. The only way Outlook XP will render iCal is if the content type is text/calendar and is the only body type. Most iCal messages are formatted as multipart/alternative. The same messages viewed with OL11/IMAP are correctly processed. Therefore you cannot use Outlook 10 in IMAP mode to connect to a Scalix Mail Server and process iCal type meetings.
  • All-day events across time zones appear in local time and are not marked specifically as all-day.
  • Advanced recurrence patterns are not supported, e.g. every 2 weeks, Tuesday and Sunday (where the week starts on a Monday) or yearly recurrence of the first weekend day of December.
  • Responding to an iCal meeting request and proposing a new time is not supported. Scalix does not currently support the COUNTER method of iCal.
  • Updating text for a series of recurring meetings may fail to display the update where the recurring meeting previously had exceptions.
  • Sending a meeting request from Evolution to Outlook with Scalix loses the "Optional" attendee status. As a result, all attendees appear as "Required".

[iCal Workarounds] --

  • To get full calendaring interoperability between Scalix and Exchange 5.5, use the TNEF route and Outlook as the client.
  • To make a time slot display as "free," manually remove the meeting from the calendar when accepting a cancellation request.
  • This is a Microsoft issue with Outlook 10.

 

 

 

  • None

 

  • None

 

  • None
  • None

If you modify an email user's name while the user is actively connected to the server, the user may not be able to sign on again using SWA or Outlook/Connect. This applies to modifications made both in the Scalix Management Console or the ommodu command on the CLI.

Use SAC or the CLI to verify that the user is logged off before making any modifications. You can then use SAC to modify the user record, or use CLI and issue the following command:

ommodu --requireSignoff -o "<name> "

Where <name> is the user's Scalix name.

If a user's account is moved from one server to another when SmartCache is enabled, local caches do not update with the user's new internal server address.

When a user is moved to a different server, the profile and cache must be recreated.

If using SmartCache in SmartCache mode, when a user's mailbox is moved from one server to another within a multi-Server Scalix Enterprise Edition environment, you must create a new profile on the user's desktop and re-initialize the user's cache.

Create a new profile on the user's desktop and re-initialize the user's cache.

If you use DDVs to store ISO bulletin board subjects, any DDVs that contain 8-bit ISO characters should be moved to the DDVn-TX variants before upgrading to 11.0. Otherwise, upgrade and/or directory synchronisation may fail for these entries.

DDVs that contain 8-bit ISO characters should be moved to the DDVn-TX variants before upgrading to 11.0. On the system where the directory entry is locally owned, use omsearch to extract (e.g. omsearch -e S=bb1 -m DDV1) and ommodent to 'move' it. For example: ommodent -e S=bb1 -n DDV1=/DDV1-TX=<ddv1_value>.

With the 11.0 release, the interchange character set used for storing ORN's has been changed from T61 to UTF8. This means that when communicating with legacy Scalix machines (Scalix 10.0 and earlier) via the Sendmail Interface (SMINTFC), character set conversion needs to take place.

To achieve interoperability with legacy machines, the SMINTFC routes need to be flagged with a new "Version Number" field, which can be set with a new "-v" option to omaddrt/ommodrt and which can be viewed with the pre-existing "-f" option to omshowrt. When creating a NEW route to a Scalix 1.0.x machine, the version number should be set to "0" or "1". If creating a Sendmail interface route to another 11.0 machine, the route version should be set to "2". In multi-server environment, if a machine is upgraded to 11.0, initially all interface routes will remain as version 0. But as soon as it receives a message on one of those routes which it detects to be an 11.0 message, then the Sendmail Interface Service automatically upgrades that route to version 2. This way, as other machines in the network are upgraded, Sendmail interface communication continues to work.

In some cases, you may be able to log in to SAC using administrative privileges from a server not registered with SAC. (Bug 14088)

On each server, use a different management domain password (set during installation and applied to the sxqueryadmin user) so that they do not match.

After Scalix 11 upgrade, all directory entries (both new and existing) set up to allow mailing to a Public Folder require manual entry of a common name (CN) value, or the sendmail interface reports the user as unknown. (Bug 14017)

Run the following command on a one-time, per folder basis: ommodent -e S=+BB/IA-FORMAL=public.folder@domain.com -n "CN=Public Folder Name", where the IA-FORMAL value is the Internet address of the public folder and the CN value is the name of the Public Folder.

Cannot send eMail from external to distribution lists with default access permissions set to None when using SMTPFILTER=TRUE option (Bug 14712)

If you have set a PDL so that it cannot be sent from the outside world using, for example

   omaddaci -l PDL-Name -f Default -c read

then the ldapmapper will not recognize the affected PDLs as valid scalix addresses because it normally binds to the Scalix LDAP server anonymously and therefore cannot see "protected" PDLs itself. sendmail relies on the ldapmapper to route messages back into Scalix.  To allow the ldapmapper to correctly identify these addresses, it must use authenticated admin LDAP access. You can do this by adding a ~/sys/ldapmapper.cfg file for each Scalix instance on the server.  This can contain, for example,

   DN=cn=sxqueryadmin
   PASSWDFILE=../../caa/scalix.res/config/psdata


in which case it re-uses the standard admin account created for Scalix Management Services during installation. You can user other admin accounts if desired. See the ldapmapper(8) man page for more information.

As of Scalix Version 11.4 SMTPFILTER is deprecated in favor of the newly introduced MILTER interface on the SMTP Relay. Integrating your filter through the new interface may provide another workaround.

When converting a normal user to a resource with 'ommodu --resource y', calendar folder is not automatically created and permissions set (Bug 10641)

Logging as the 'resource' user with either Outlook or SWA will create the calendar folder. Then, permissions for the calendar folder will need to be setup so that users who should be able to automatically book the resource have write access to the folder.


Note that permissions will be setup correctly by default for users newly created with omaddu or through the Scalix Management Console. This issue only occurs in the rare case when a normal user is converted into a resource.

On Red Hat Enterprise Linux 5 (RHEL 5), setting up stunnel to provide TLS support for SMTP does not work (Red Hat Bug 284801)

You can still use SMTP over SSL (without TLS) using stunnel on RHEL5. Otherwise, please contact Red Hat through Red Hat Support to provide further priorization on fixing the bug.

The following characters are not supported for Proxy Folders (Bug 17021, 17118): $ % * / # [ ]

None.

Proxy Folders do not support redirects or webcal:// URLs (Bug 17064)

Use the full http:// address when specifying an URL for Proxy Folders .

sxpfadd will fail to create a Proxy Folder when the username contains chinese or japanese characters (Bug 17220)

Use the auth-id instead if the username.

Under certain conditions the local delivery service may leak memory (Bug 12568).

Restart the local delivery service on a regular basis, e.g. nightly via cron. Users will most likely take no notice of the restart, since the only impact is that delivery during this time will take a little bit longer. This issue will be fixed in a later version of Scalix.

 


Back to top

Scalix Messaging Services

Issue

Workaround

Cannot access calendar folders shared by other users when using CalDAV access with Apple iCal.app

This functionality has been disabled for this release (See Bug 16251) because of some issues (Bug 16156). It will be fixed in a future release of Scalix

Colons in user password breaks http authentication in CalDAV (Bug 16428)

Do not use a colon as part of the password.

Free/Busy information will not be updated when adding meetings via CalDAV (Bug 16976)

None. This will be fixed in a future release of Scalix.

Creating a meeting via CalDAV will not create a message in Sent Items (Bug 17007)

None. This will be fixed in a future release of Scalix.

Exception "Sending error M00010 resource not found" logged when adding another users calendar in SWA.

None. SWA automatically recovers and completes the operation.

CalDAV does not support attachments for calendar entries (Bug 16557)

None. This will be fixed in a future release of Scalix.



Back to top

Scalix Search and Index Service

Issue

Workaround

In some cases, keywords within complex messages or binary attachments (*) are not found when performing full text searches with Outlook or Scalix Web Access

A number of indexing issues have been fixed in Scalix 11.0.x releases. Some of these require a users mailbox to be re-indexed. Please follow the instructions provided in this How-To to reindex mailboxes.

Search for prefix does not work (Bug 15234)

None. This will be fixed in a future release of Scalix.

* Indexing of binary attachment types (Word, PowerPoint, Excel, PDF) is only available for Scalix Small Business Edition (SBE) and Scalix Enterprise Edition (EE)


Back to top

Scalix Admin Tools

Issue

Workaround

Users created in the Management Console whose passwords contain umlauts cannot log in to Scalix Web Access. (Bug 4108)

Change user passwords to text entries without diacritical marks.

Users who exceed their mailbox size limits do not receive messages even after you remove the limits. (Bug 4971)

After removing the mailbox size limit, restart the Client Interface, Service Router, and Local Delivery services.

A user whose name is modified while he/she is actively connected to the server may not be able to sign on again using SWA or Outlook.

Verify that the user is logged off before changing his name. Or use the command line to forcibly sign them off with the following command:

ommodu --requireSignoff -o "<user_name>"

If an administrative user has a pre-expired password (requiring that they change their password upon next login), the user cannot log on to the management console until the password is reset. (Bug 13881)

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.

Milter and proxy folder services doesn't display in SAC (Bug 17026)

None. This will be fixed in a future release of Scalix.



Back to top

Scalix AntiSpam and Scalix ZeroHour AntiVirus

Issue

Workaround

Reporting back False Positives using sxmilter in tool mode will only send back the message if the level is found to be 4. Messages categorized 3 or lower will not be sent back.

Do not use sxmilter to report report back False  Positives/Negatives but send them via email.



Back to top

Scalix Connect for Outlook

Issue

Workaround

OLE objects embedded in the body of an email message may not be usable by the message recipient. (Bug 723)

Transfer OLE data as an attached file.

In Outlook 2002, enabling the instant messaging feature impacts response time when viewing messages in the Preview pane.

Disable this option.

If users create additional folders using existing standard folder names ("Inbox", etc), they will not be able to open or use them in SWA or other IMAP clients that do not utilize MAPI.

Solution: Don't create folders named "Inbox" (or "Draft" or "Junk E-mail", etc.) if you want to use SWA to check your mailbox.

Once SmartCache is enabled, you cannot revert to non-SmartCache mode.

If you wish to discontinue caching, create a new profile without the SmartCache feature enabled.

The use of non-ASCII characters in display or common names to log in to SWA and Outlook is not supported.

None

In rare circumstances, a delegate can see a new folder created by his or her "principal" but cannot open it. This happens if the principal creates a new folder shortly after the delegate adds the principal's mailbox to his own profile.

Restart Outlook and the new folders become accessible to the delegate.

If you are trying to cradle-sync a Blackberry device with the Microsoft Outlook client, you must use Blackberry Desktop Manager 4.1.x or 4.2.x and also replace the Intellisync file ilxolk.fil with a customized Scalix version. The customized version is located in the .tar.gz file under software/scalix_connect_outlook/extras

To install the patch file for Scalix/Intellisync, please see the "extras" subdirectory of the Scalix Connect for Outlook software package for the updated file and installation instructions for Blackberry Desktop Manager 4.1.x and 4.2.x.

If a non-email folder is set to display first when launching Outlook, the Scalix Rules Wizard fails to load and the connection to the server is lost. (Bug 8284)

Only specify the Inbox folder as the initial display mode.

When using a profile with SmartCache enabled, cache initialization takes a very long time and performance is poor when running a Virus Scanner with Online Filesystem protection on the workstation.

Configure the Virus Scanner to exclude files and subdirectories in the following directory tree from online access scanning:


C:\Documents and Settings\<Windows Username>\Local Settings\Application Data\Scalix\Scalix\MAPI\Profiles

International character set and Unicode support is functional in Outlook 11 and Outlook 12, but not Outlook 9 and 10. (Bug 13324)

If Unicode support is needed, use Outlook 11 or Outlook 12.

In Sent Items folder only, the subject line displays as empty on emails with more than 178 internationalized characters. (Bug 14634)

None.

Active Sync Issues:

  • When using Active Sync against Outlook profiles setup with Scalix SmartCache, modifications to items can be lost if an item is created on the Outlook side in offline mode and synced to the device before the change is committed from the local cache to the Scalix Server (Bug 15682)
  • When syncing recurring appointments, recurrence patters can be lost in some cases when exceptions to the recurring meeting are created (Bug 15679)
  • Cannot reply to eMail synced to the device using Active Sync (Bug 15680)

None. The issues will be fixed in a future release of Scalix.

Outlook 2007 Instant Search does not work and can crash Scalix Connect for Outlook (Bug 15389)

Disable Outlook 2007 Instant Search. This will be supported in a future release of Scalix.

Certain Outlook plugins are known to be incompatible with Scalix Connect, including

  • Microsoft Windows Desktop Search (including Instant Search in Vista/Outlook 2007) (Bug 11700, Bug 15389, Bug 16184)
  • AVG Antivirus (Bug 15360)

Disable the conflicting plugin or deinstall the software. Scalix is working on additional plugin support for future releases of Scalix Connect.

Outlook 2007 To-Do folder is always shown as empty (Bug 15549)

The issue will be fixed in the next release of Scalix.

Running Scalix Connect for Outlook with Outlook 2003 or Outlook 2007 on Vista has some known issues (Bug 14770)

The issues will be fixed in the next release of Scalix.

When using a SmartCache-enabled profile, updates to the System directory are sometimes not reflected on the client and entries in the address book appear to be missing or outdated (Bug 14829)

Add the following line to general.cfg:

AB_DOWNLOAD_INTERVAL=n

Where <n> is the number of days after which a resync of the address book should be forced as part of normal sync operation.

Scalix Connect for Outlook is not compatible with Blackberry Desktop Manager 4.3 (BBDM) (Bug 16151)

Support for BBDM 4.3 will be included in a future release of Scalix.

Outlook hangs when using Kaspersky Anti Virus/Active Virus Shield together with outgoing rules (Bug 13690).

Disable all outgoing rules. Incoming rules can still be used.

Some Scalix properties are missing when accessing a profile from control panel (Bug 16136)

Access Scalix Properties via Outlook's Tools menu.

On creating a new profile Outlook 2000 may display Use SSL option even when the server does not support it (Bug 16334)

None

Outlook 2007 fails to open mailbox with "Can not open your default email folders.The information store could not be opened." after using the installers Repair option (Bug 16693)

Uninstall and Install Scalix Connect for Outlook.

Outlook 2007 hangs on Windows XP after network connection was lost (Bug 17093)

Try the following steps:

  1. User Work Online/Work Offline to let it retry
  2. Disconnect/Reconnect Network
  3. Restart Outlook and related processes

Outlook 2007 will not repaint window when loading inbox on startup (Bug 17203)

None, the issue will be fixed in a future release of Scalix.

Outlook 2007 will stop updating the progress bar when clicking into the main window on startup (Bug 17204)

None, the issue will be fixed in a future release of Scalix.

Autoupgrade triggers User Access Control Dialog on Vista when updating Connect (Bug 17213)

On Windows Vista an administrative user is needed to automatically upgrade Connect or UAC needs to be disabled.



Back to top

Scalix Web Access

Issue

Workaround

When using Internet Explorer with high-resolution displays, users with dpi settings other than 96 dpi may experience that certain modal dialogs within Scalix Web Access do not display all of the information that the dialog contains.

Set dpi setting to Normal size (96 dpi) through Windows Control Panel > Display Properties.

Popup-blocking software installed on your machine might prevent SWA from starting up.

You need to either disable pop-up blocking or add the Scalix Web Access URL to the list of allowed sites.

The use of non-ASCII characters in display or common names to log in to SWA and Outlook is not supported.

None

When upgrading SWA, customizations to the login page are not retained.

Prior to upgrade, save a copy of index.html and web.xml, which are where login customizations are made, and use these as a guide to make the same changes once the update has completed successfully.

Umlauts created from an English keyboard (alt+0228 or alt+0252) on Internet Explorer 7 do not display properly in the contacts list if the URL used to access SWA is not on the list of trusted sites. They do display properly in email or calendar items.

Use a German language keyboard.

SWA does not accept resource bookings made with global character sets.

None

If upgrading directly from 10.0.1 or later to Scalix 11, the event services may not start, which can cause the Scalix Mobile Web client to fail and SWA performance to deteriorate. (Bug 14133)

After completing upgrade to 11.0, the xinetd process needs to be signaled to reload its configuration. Run the following command: "/etc/init.d/xinetd reload". Then restart the Scalix mail server (omshut/omrc).

In Firefox, resizing the message list pane shrinks the entire pane to only one pixel, obscuring the message list. (Bug 10397)

At the top of the preview pane, pull the border repeatedly until it reaches the desired size. This may take a few repetitions as the border bounces back.

In some cases, the Drafts folder may have multiple copies of the same message. ()

Delete the extras after sending.

A JavaScript error appears when a delegate opens a private appointment from his principal's mailbox.

None

Clicking the ‘next’ arrow button of the message window prompts a JavaScript error.

None

Setting an empty Out of Office Message will lead to an error message when trying to reopen the Out of Office Agent (Bug 12984)

Log in to the Scalix Rules Wizard and delete the Auto-Action rule. You can now re-enable the Out of Office Agent with a valid message.

Invoking SWA within a frameset yields erroneous error message (Bug 16549)

None, SWA is not supported to be run inside of a frameset.

SWA appears to allow changes to read-only Proxy Folder like deleting items from or filing items into them (Bug 17035)

None, the issue will be fixed in a later version of Scalix.

The From address of RSS/Atom Feeds is displayed as rss@invalid.com (Bug 17075)

None, the issue will be fixed in a later version of Scalix.



Back to top

Scalix Connect for Evolution

Issue

Workaround

Recurring appointments "Every Xth Y of month M every year" cannot be created or edited in Evolution

You can create recurring appointments with the pattern "Every Xth Y of month M every year" in Outlook and SWA but not in Evolution. If created in SWA or Outlook, though, it displays correctly in Evolution although you cannot edit them.

Nested PDLs (address-lists)

You cannot create nested PDLs in Evolution. When created in Outlook, nested PDLs only show with their top-level members in Evolution.

Freebusy data of organizer not displayed

The "Scheduling" section of the meeting editor does not show the free/busy data for the organizer.

Offline mode

Only mail features are currently supported in offline mode. While certain calendar and contacts operations do work, they are not officially supported.

Message filters

Message-filters do not file new messages automatically although the "apply filters to new messages in the Inbox" option in the account profile is checked. "Apply Filters" from the Message menu however works.

SMTP configuration

You cannot configure the SMTP and IMAP servers separately. They are always the same and the SMTP port is always 25. If you need a different configuration, manually change your account profile settings through gconf-editor:

  • Run gconf-editor
  • Expand /apps/evolution
  • Select mail
  • Double-click on accounts in the right-hand pane
  • Select the relevant account and click "Edit"
  • In the text box, find the XML element <url> inside the <transport> element and add ":###" after the hostname, where ### is the port of your SMTP server.

Modifying an existing Scalix account in Evolution to a new account does not update the calendar and contact data for the new user.

Delete the existing Scalix account by choosing Edit ->Preferences in Evolution and then create a replacement ("New") Scalix account.

When accepting a meeting request in Evolution, adding a comment results in an empty message attachment in the response when viewed by an Exchange user in the Outlook client.

None

Evolution users cannot accept updated instances of recurring meetings sent from Outlook.

None

Additional invitees to a recurring meeting may not display when the appointment is viewed in Evolution.

None

Resource booking is not supported in Evolution.

None

Evolution does not display priority or sensitivity levels set in SWA or Outlook.

None

Evolution does not show message formats as saved in the Outlook Drafts folder.

None

Messages sent to PDLs arrive in Evolution as "Undisclosed-Recipient."

None

 


Back to top

Blackberry Cradle Synchronisation with Blackberry Desktop Manager (BBDM) 4.1/4.2

Intellisync is included as part of the Blackberry Desktop Manager (BBDM) software bundle distributed by Blackberry. You can download Blackberry Desktop Manager from the Blackberry web site. The BBDM software needs to be patched with a patch provided by Scalix to enable synchronisation with Scalix. Please see the "extras" subdirectory of the Scalix Connect for Outlook software package for details. The patch is provided for versions 4.1.x and 4.2.x of the BBDM software. The current version of Scalix Connect for Outlook is not compatible with versions 4.3.x of the BBDM software. This will be supported in a future release of Scalix.


Back to top

Scalix Migration Tool

Issue

Workaround

Microsoft Exchange out-of-office settings do not transfer during migration. So if a user's out-of-office assistant is activated during migration, it stops responding.

After migration, reset out-of-office notifications in Scalix.

When migrating a user with the Scalix Migration Tool, the Outlook rules are not preserved because Microsoft rules are not compatible with Scalix.

None

 


Back to top


Scalix Administration Resource Kit

The Scalix Administration Resource Kit is located at http://www.scalix.com/wiki/index.php?title=Admin_Resource_Kit.

Back to top of page...