Contents

• Introduction

• New in Scalix 11.0

• Packaging

• Supported Environments

• Fixed in This Update

• Known Issues and Workarounds

Introduction

Back to top

New in Scalix 11.0

Back to top

This release is intended for preview purposes ONLY. It should not be used on production servers or data.

Packaging

Back to top

Supported Environments

Back to top

Fixed in This Update

Back to top

Known Issues and Workarounds

Back to top

Issue

Workaround

If you've installed your Scalix system on host(s) running SUSE Linux Enterprise 9, your Outlook users will not be able to take advantage of Single Sign On, due to a flawed Kerberos interaction between SUSE and Microsoft.

Solution: There is no workaround or solution at this time.

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 TimeZone, Date and Time between the domain Controller, mail server, and the client user's workstation. The timestamp difference between mail server and Domain controller should not be greater than the "Maximum tolerance for computer clock synchronization setting" of the domain controller.

The synchronization command, omldapsync, will not create a new Scalix mailbox for an Active Directory user who has accented characters in a "friendly" name.

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

• 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 server and process iCal type meetings.
• All-day events across time zones appear in local time and are not marked specifically as All day events.
• 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 previous had exceptions.
• Updating text for a series of recurring meetings may fail to display the update where the recurring meeting previous had exceptions.
• Sending a meeting request from Evolution to Outlook with Scalix will lose the attendee status of "Optional". As a result, all attendees on the meeeting request will appear as "Required".

[iCal Workarounds] --

• To get full Calendaring inter-operability between Scalix and Exchange 5.5, you need to use the TNEF route and Outlook as the client.
• The meeting should be removed from the Calendar when accepting the cancellation request, to enable the time to be displayed as "Free".
• This is a Microsoft issue with Outlook 10.

• None

• None

• None

• None

• None

If you modify an email user's name using SAC or CLI (the ommodu command) while the user is actively connected to the server, the user may not be able to sign on again using SWA or Outlook/Connect.

To avoid this problem, first use SAC or CLI to verify that the user is logged off. 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.

German umlauts (and other non 7bit characters) can cause problems with misfiring rules created with the Web Rules Wizard.

If umlauts (and other non 7bit characters) are causing problems with misfiring rules created in the Scalix Web Rules Wizard, update the Wizard configuration with 'omwebconf -ra -l lang' (where lang is ENGLISH, AMERICAN or GERMAN). The problematic rules must then be re-edited.

If the Apache/Tomcat connector has not been installed (see Scalix Installer cannot automatically configure...) the server cannot contact the Search and Index Service (SIS) using the default port (80).

Change the SIS port from 80 (the default) to 8080 on the server and all individual users.

1. Edit ~scalix/sys/general.cfg and add the following lines:

   USRL_SIS_URL=sxidx://fqdn:8080/%u
   USRL_BB_SIS_URL=sxidx://fqdn:8080/BB@fqdn

   where fqdn is the fully qualified hostname of the machine.

To change every existing user's entry:

1. Run the command omshowu -n <username> and look for the line:
   SIS URL : sxidx://fqdn/guid

2. Run the command ommodu -n <username> -index sxidx://fqdn:8080/guid
   where fqdn is the fully qualified hostname of the machine and guid is a unique identifier.

The above can also be automated using a simple shell script.

Back to top

Issue

Workaround

During installation of Scalix web applications, 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 this:

To resolve this issue Apache web server needs to be restarted manually. You can use the following CLI commands depending on the host OS:
"service httpd restart" on RedHat or Fedora Core, or "/etc/init.d/apache2 restart" on SUSE.

If you installed SLES 9 on the Scalix Server host, the python-gtk-2.0.0-215.1 package is automatically installed. 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.

When uninstalling Scalix, after uninstalling the Scalix Postgres integration component, the installer does not stop the PostgreSQL database.

Manually stop the database after the uninstallation procedure is complete.

Back to top

Issue

Workaround

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

Transfer OLE data as an attached file.

In Outlook 2002, enabling "Instant Messaging in Microsoft Outlook" (Tools > Options > Other) might reduce response time when viewing messages in the Preview pane.

Disable this option.

The contents of any of the standard ("default") folders disappear from the Outlook folder list when the user is working offline.

In offline mode, despite logging into the server and synchronizing folders between Outlook and the server, the contents of the standard Outlook folder contents are missing. (The standard folders--Inbox, Sent Mail, etc.-- appear in the folder list.)

At this point, a solution is to log out of the mail server before re-enabling offline working.

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

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.

If you exceed 255 characters in an email subject line, an error message appears and the line is truncated.

Keep subject lines to lengths of fewer than 255 characters.

Deleted folders in the Scalix Recovered Items folder prevent successful cache initialization.

Delete the folder from the Scalix Recovered Items folder.

When the "To" field is added to the Inbox display, the recipient's address may at times appear garbled. This does not impact delivery and messages can be forwarded.

None

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.

Back to top

Issue

Workaround

Recurring appointments with exceptions

Evolution 2.4 does not handle exceptions to recurring appointments well. Exceptions created in Outlook do not show up in Evolution. Furthermore Evolution won't let you create a real exception to a recurring appointment. It will however allow you to "detach" an instance, which results in an additional appointment that is not related to the series.

Making instance of series movable crashes Evolution

Detaching a single instance from a series (making it movable) may crash or hang Evolution.

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.

Modifications to an appointment in Evolution -- for example adding an attachment -- may delete both the description and the attachment.

None

Outlook and SWA may create duplicate appointments in the calendar, even if the meeting has already been accepted using Evolution as the client.

None

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

Cannot send meeting requests with attachments when working in Evolution.

None

Updating a recurring meeting in the Outlook calendar is not represented when viewed with Evolution.

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

Issue

Workaround

Delegation is not available in this preview release.

None

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.

German language is not translating properly

1. Go to /opt/scalix-tomcat/webapps/webmail/WEB-INF/data/strings_de.xml
2. On line 1520, remove the two dashes after the commented bug number so that <!-- bug 12300 -- need translation --> changes to <!-- bug 12300 need translation -->
   
   

Back to top

Issue

Workaround

Restarting Tomcat on machines where the Management Agent (aka Remote Execution Service or RES) is deployed requires an interval of few seconds.

If you have to restart Tomcat, stop Tomcat first, let it shut down properly by waiting for a few seconds, and then restart it.

Users created in the Scalix Management Console with passwords that contain characters with umlauts cannot log in to Scalix Web Access.

Change user passwords to text entries without diacritical marks.

Users do not receive messages after you remove mailbox limits for a user who has exceeded their specified limit(s).

Restart the Client Interface, Service Router, and Local Delivery services.

In environments that have the Management Agent (RES) operating in Kerberos mode and have other large applications deployed on the server, you must have Tomcat running on the RES server before you start Tomcat on the server that runs the Scalix Management Console.

Ensure that the Management Agent is deployed first in Tomcat (before other large applications) and that all Tomcat instances are started before you start the Scalix Management Console service.

If you modify an email user's name using SAC or CLI (the ommodu command) while the user is actively connected to the server, the user may not be able to sign on again using SWA or Outlook/Connect.

To avoid this problem, first use SAC or CLI to verify that the user is logged off. 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.

Back to top