Scalix 11.0.4 - Release Notes

Release Date: 2007-05-03

Contents

Introduction

Back to top

Thank you for downloading Scalix 11.0.4.

This is the latest release of Scalix 11, providing several important updates and fixes to previous versions. We recommend you upgrade all systems running previous versions of Scalix 11 to this latest release. If you are not yet running a version of Scalix 11, this new release is a full package, so new installations and upgrades to Scalix 10 or prior can use this version directly without first installing or upgrading to any previous version of Scalix 11.

This document includes late-breaking information about product capabilities, known issues and workarounds. After reading this, you may begin planning your Scalix installation or update.

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 bugtracking system at http://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/community. 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.


Important End of Life Notice

Back

Scalix 11.0 is the last release of the Scalix product to support RedHat Enterprise Server 3 (RHEL3). We recommend that, as part of this installation process, you upgrade all Scalix servers running on RHEL3 to RedHat Enterprise Server 4 (RHEL4). Starting with the next release, 11.1, we will provide packages for Scalix 11 on RHEL3 only to Small Business Edition and Enterprise Edition customers with active subscriptions on request and they will be removed from the standard enterprise and community downloads.

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 Scalix 10.x or earlier, there are several changes of which you should be aware:

    If you are upgrading to Scalix 11.0.4 from any previous version of Scalix 11, there are several things to be aware of:

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

New in Scalix 11

Back to top

New Features

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

Back to top

Fixed in Scalix 11.0.4

The following issues have been addressed in Scalix 11.0.4:

* 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:

* The Scalix Migration Tool (SMT) is a separate product for migrating user data from Exchange 5.5, 2000 and 2003 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:

Fixed in Scalix 11.0.2

The following issues have been addressed in Scalix 11.0.2:

Fixed in Scalix 11.0.1

The following additional issues have been addressed in Scalix 11.0.1:

Fixed in Scalix 11.0.0

The following issues have been addressed in this release:


Supported Environments

Back to top

Supported Linux Platforms

Scalix 11.0 runs on the following platforms:

* The Scalix Small Business and Enterprise Edition commercial and evaluation downloads do not contain RedHat Enterprise Linux 5 (RHEL5) packages. If you want to evaluate or test Scalix on RHEL5, please go to http://www.scalix.com/downloads and download the RHEL5 Community Edition package.

Note: An unsupported Community Edition package for Debian-based Linux distributions is also available for download at http://www.scalixcom/downloads.


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 IO-bound, using variable, small-blocksize random read/write synchronous file IO.

Also note that we do 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 most notable for 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 recommend putting the Scalix message store on a Hardware RAID Array, using RAID 1+0 for optimal performance and RAID 5 otherwise. 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.0.4 Release consists of a single gzipped tar package. This contains some or all of the following components with specific build numbers:

Component

Build

Scalix Installer

11.0.4.25

Scalix Server

11.0.4.25

Scalix Management Services (SAC, RES)

11.0.4.25

Scalix Messaging Services (Platform)

11.0.4.25

Scalix Web Access (SWA)

11.0.4.25

Scalix Mobile Web Client (Mobile)

11.0.4.25

Scalix Search and Indexing Services (SIS)

11.0.4.25

Scalix Text Extractors for Indexing and Search *

1.0

Scalix DB (Postgres)

11.0.4.25

Scalix Tomcat Connector

11.0.4.25

Scalix Tomcat

5.5.16.263

Scalix Connect for Outlook (MAPI) **

11.0.4.27

Scalix Connect for Evolution

11.0.4.25

Scalix Migration Tool (SMT) ***

11.0.4.25

Scalix Active Directory Extensions (ADE) ****

11.0.4.25

* 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

During installation of Scalix Web applications, the Apache Web server may not register all workers after the installer restarts it.

In this case, some Web applications will not come up. The error reported in the Apache error log looks like:

[Tue Dec 13 14:32:15 2005] [error] [client 10.17.64.125] File does not exist: /var/www/html/webmail

To resolve this issue, restart the Apache Web server manually with following CLI commands:

  • On RedHat or Fedora Core: "service httpd restart"
  • On SUSE: "/etc/init.d/apache2 restart"

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.

On a 64-bit machine with JRE 1.5_05 already installed, installation may abort. (Bug 13998)

Remove JRE 1.5_05 before installing or upgrading and allow the installation wizard to install its own, updated version of JRE 1.5_06.

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.

Windows-based installer for Scalix Connect for Outlook crashes at the end of installation when starting setup.exe from inside a Windows compressed folder even though installation completed successfully. (Bug 14281)

Extract setup.exe from the compressed folder and execute it directly from a normal folder.

When installing via the command line, installation may abort if you first choose to use an existing but outdated JRE, but later are forced to upgrade to JRE 1.6.0_06.

None.

When installing via the GUI on RedHat Enterprise Linux 3 (RHEL3) x86_64, installation will not properly recognize a preinstalled Java Runtime Environment and will also not allow you to install a new one.  (Bug 14796)

There are two possible workarounds:


1. You can de-install the preinstalled Java Runtime Environment (JRE) before you start the installation.

2. You can use the command line installation (CLI Mode)

Note: As RHEL3 is deprecated as a platform, the issue will not be fixed and the suggested workarounds will stay in place until support for RHEL3 is discontinued.

 

Back to top

Scalix Mail Server

Issue

Workaround

After upgrading Scalix Mail Server from 10.0 to 11.0, 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 1: 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.

Kerberos-based single-sign-on (SSO) fails if the time stamps for domain controller, mail server and the workstation are not in sync.

The critical prerequisite to setting up successful SSO and Kerberos authentication is synchronization of time zone, date and time between the domain controller, mail server, and the client user's workstation. The timestamp difference between the mail server and the domain controller should not be greater than the "maximum tolerance for computer clock synchronization setting" of the domain controller.

On Scalix 10.0 servers only, the synchronization command, omldapsync, does not create a new Scalix mailbox for an Active Directory user whose "friendly name" includes accented characters. This has been fixed for Scalix 11, but if you have old 10.0 servers in your system, you may encounter this problem.

Use a mapping table entry that includes the custom map function:

!CUSTOM=TX_IA_TO_QP_IA

For example:
mail|INTERNET-ADDR|*,1,512|!CUSTOM=TX_IA_TO_QP_IA

The result is that:'"c?nt" <ia>' becomes '=?UTF8?Qc=C3=B6mm=C3=ABnt?= <ia>'

[iCal Information] --

The access URL for Webcal has changed. It is now http://my.scalix.server/api/name@domain.com/ical/Calendar.

  • 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 cancelled 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 synchronization 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>.

After migrating a user in to Scalix from Exchange via the Scalix Migration Tool (SMT), you may see some that some messages using internationalized character sets such as Japanese show garble in the subject and message fields if you are running against a Scalix 10 server. This is because Scalix 10 does not support Unicode for international character sets.

Upgrade all servers to Scalix 11

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.

If upgrading from a RC1 or earlier version of Scalix 11, clean out the IMAP cache. (Bug 14119)

Run the following command on the Scalix Mail Server: cd $(omrealpath \~/user) find -name imap-cache | xargs rm -rf . It is necessary to run this command when nobody is signed on to the system (when the rci and IMAP services are off).

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.

IMAP and SWA access do not work correctly after upgrade when Scalix 10 Outlook Offline Folder Sync was used before the upgrade (Bug 14710)

1. Find the User Folder of the affected user:
    # omshowu <username> -f
    server:/root # omshowu "John Smith" -f
    ...
    User Folder : ~/user/g000045/00000v8:1
    ...

2. Change to the User Folder:
    cd `omrealpath '~/user/g000045'`

3. Make sure the user is not logged on:
    omstat -u all -c

4. Delete the ofs and IMAP Caches:
    rm -rf 00000v8.ofs imap-cache

Note: After you execute these commands, all Outlook profiles for users using SmartCache or Offline Working need to be recreated.

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.

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.

 

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 Management Console (aka SAC)

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.

 

Back to top

Scalix Connect for Microsoft 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.

When using the German-language version of Outlook (with Scalix Connect), opening and using the Scalix Rules Wizard may result in a rule, but the process triggers an I-E script error, referring to "sclxresDE.dll". (Bug 10370)

The script error is triggered by clicking through the Wizard to the exceptions screen, whether any exception is chosen or not. The rule is, however, created successfully and works as configured by the user.

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.

On Outlook 2003 with Active Virus Shield installed and enabled, Outlook deadlocks when sending mail. (Bug 13690)

Disable the 'Scan on delivery' for Active Virus Shield.

  1. Start Outlook.
  2. From the Tools menu, select "Options". The Options dialog appears.
  3. Click the "Active Virus Shield" tab.
  4. In the "Settings" section, uncheck the "Scan on read," "Scan on Send" and "Scan on delivery" checkboxes.
  5. Click "Ok".

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

The Outlook Connector setup procedure does not properly extract the sxpro.exe when the /e switch is used. Because this .exe file creates Outlook profiles on Scalix, it is essential that it run properly and complete its function. (Bug 13965)

To launch the sxpro.exe function manually, install the MAPI SP and it extracts under the directory \Program Files\Scalix\Connect. Launch it from there.

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

If Unicode support is needed, use Outlook 11.

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

None.

Cant find Address Book Entries with Umlauts (Bug 8958)  

None

Back to top

Scalix Web Access

Issue

Workaround

There is a known issue which may affect adding messages with Unicode characters to the Platform database.  When this issue is encountered, it can lead to longer login times in SWA and in an extreme case, the inability to login (Bug 14282). 


The problem can be identified by an error message in the scalix-api.log file similar to:

WARN [RestServlet.sendError:28] Sending error
M00005 full folder sync failed
Message:java.sql.BatchUpdateException: Batch entry 1,198 insert into message values...

The issue will be addressed in the next release of Scalix where the installer will automatically reconfigure the database to use Unicode.

As a workaround you can manually recreate the platform database to accept Unicode data. The procedure is described in a Technical Bulletin that is published on the Scalix Wiki; Bug 14282 also links to the document.

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. (Bug 14194)

Delete the extras after sending.

Folders designated as shared may not appear in SWA. (Bug 13398)

Restart Tomcat and the IMAP process

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

Attachment filenames containing international characters are not processed correctly when using Firefox 1.5 (Bug 14912)

Use Firefox 2.0 or above.

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 Synchronization with Blackberry Desktop Manager

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.

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

 

Copyright 2007 Scalix Corporation. All rights reserved. (Ed: FvK 2007-05-08)