Sun Java System Connector for Microsoft Outlook 7 2005Q1 Release Notes

Sun Java™ System Connector
for Microsoft Outlook Release Notes

Version 7 2005Q1

Part Number 819-0031-10

Last updated: February 1, 2005

These release notes contain important information available at the time of release of Version 7 2005Q1 of Sun Java System Connector for Microsoft Outlook (also referred to as Connector for Microsoft Outlook). New features and enhancements, known limitations and problems, technical notes, and other information are addressed here. Read this document before you begin using Sun Java System Connector for Microsoft Outlook 7 2005Q1.

The most up-to-date version of these release notes can be found at /docs/cd/E19955-01/819-0031. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and manuals.

Please see the section What’s New in This Release for information on features that are new to this release.

These release notes contain the following sections:

Third-party URLs are referenced in this document and provide additional, related information.


Sun is not responsible for the availability of third-party Web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Release Notes Revision History

Table 1  Revision History 


Description of Changes

September 2004

Initial release of these release notes (Version 7 2005Q1).

November 2004

Beta release of these release notes.

December 2004

Final review draft of these release notes.

February 2005

Final release of these release notes (Version 7 2005Q1).

About Sun Java System Connector
for Microsoft Outlook, Version 7 2005Q1

Sun Java System Connector for Microsoft Outlook enables Outlook to be used as a desktop client with Sun Java Enterprise System.

Connector for Microsoft Outlook is an Outlook plug-in that must be installed on the end-user’s desktop. Connector for Microsoft Outlook queries the Sun Java System Messaging Server for folder hierarchies and email messages. It converts the information into Messaging API (MAPI) properties that Outlook can display. Similarly, it uses WCAP to query the Sun Java System Calendar Server for events and tasks which are then converted into MAPI properties. With this model, Sun Java System Connector for Microsoft Outlook builds an end-user Outlook view from two separate information sources: mail from Messaging Server and calendar information from Calendar Server.

When users create and modify items through Outlook, Connector for Microsoft Outlook passes the new message along to the appropriate server depending on its message type. It sends new outgoing e-mail to an SMTP mail server for delivery, and sends modified e-mail messages back to the user’s IMAP folder for storage. New calendar events and tasks are converted into a standard format to be stored in the Calendar Server database.

Sun Java System Connector for Microsoft Outlook 7 2005Q1 includes support for address book service. This service makes use of WABP and allows a user to have their personal address book accessible from both Outlook and Sun Java System Communications Express.


Please note, the package that is Sun Java System Connector for Microsoft Outlook does not include any migration tools. You need those tools if you have users that are currently on Microsoft Exchange and would like to use Outlook with Sun Java Enterprise System. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Enterprise System.

This section includes:

What’s New in This Release

New features in Sun Java System Connector for Microsoft Outlook 7 2005Q1 include:

Key Features in Sun Java System Connector
for Microsoft Outlook

The following key features and functionality are available with this release:

System Requirements

The following describes the system requirements and recommendations for Sun Java System Connector for Microsoft Outlook.

Bugs Fixed in This Release

The table below describes the bugs fixed in Sun Java System Connector for Microsoft Outlook 7 2005Q1:

Table 2  Fixed Bugs in Sun Java System Connector for Microsoft Outlook 7 2005Q1 

Bug Number



Advanced Find shows incorrect “in Folder” information.


Searching across multiple folders is not possible.


Message with Content-Type: Message/External-body; sometime results in error messages.


Switching from one folder to another takes a long time.


Unread messages count next to the folder name in the folder list is not retained after closing and restarting Outlook.


Changing the SMTP configuration does not ask to restart the Outlook.


Advanced Find does not search subfolders.


Task delegation via e-mail does not work.


Search via Advanced find does not work for all cases.


Starting Outlook after installation, the mail folder appears as “Mail Folders” instead of “Mail Folders - user.”


Virtual memory consumption is tremendous when moving or deleting a large amount of messages.


Error message is displayed when Mail Folders is opened.


Default auto-archive fails.


HTML background is lost when messages are moved from mail folders to personal folders.


Formatting of in-line included messages are poorly formatted.


Message delay delivery does not work; messages are delivered immediately.


Outlook crashes if a mail message opens with a modeless dialog and folder switch.


Sound not played when new mail arrives.


Nothing displayed in View Message Source.


When logging into different IMAP servers, it is only possible to log into one if the userID is different for the other.


Changing the timezone and then creating events displays an error.


Non-fatal IMAP errors appear frequently.


Outlook today shows “AAAAAAAAAAAA 9999" instead of Inbox and number of messages.


Mail Sent Items folder does not display correct column fields.


Moving between folders rule results in APPEND instead of COPYUID in Rule Wizard.


Running rules on SUN One Folders creates a copy of the messages in Deleted Items.


IMAP ACLs on shared folders are not reflected in the folder menu.


Rules Wizard does not save a new rule when creating using the Tools->Organize menu.


Running autoarchive often generates errors.


Outlook crashes during retrieving events from shared calendar that no longer exists.


Outlook connector should support Mail and Calendar proxy auth.


Group-By functionality does not work.


Mail Sort-by-icon sometimes displays a black square for some messages.


Unable to subscribe to shared calendars with AUTH LDAP.


Drag and drop for a draft message becomes non-editable.


Cannot empty deleted items using the Outlook shortcuts.


No error message when SMTP configured with wrong port.


Offline mode required.


Cannot display CREATED IMAP folders.


Other Sun Java System services disappear if Connector for Microsoft Outlook is configured first.


All day event created in Outlook doesn’t get synched properly in Calendar Server.

5021880 and 5021881

Online to Offline switch does not properly occur.


Error should ask user to check IMAP port also in case user is unable to connect to the Messaging Server.


Dialog errors displayed when switching to offline mode.


Receiving “download operation complete” dialog after cancelling “download all message parts” operation.


Offline mode hangs Outlook.


“Mail Folder” and address error.


Flag under “Mail Folder” cannot be set for messages.


Free/busy availability does not display in Korean locale.


Unable to send or receive messages if the Calendar Server is down.


Strange behavior of public events in Korean locale.


Ambiguous translation in Debug Log dialog in Korean locale.


cannot set e-mail log to “important” in Korean locale.


Reference to the Syntegra product: “IMAPSP Folder name” under the IMAP Tab.


“Do not deliver before” feature does not work.


Permissions in properties dialog for calendar are not saved.


Shortcuts are created more than necessary when a new profile is created.


Task Due date modified from Communications Express is not correctly set.


Administrator package does not have a valid version/build number.


Cannot access calendar view.


Outlook crashes in istore32.dll if a rule on SMTP transport is enabled.


After user changes password, when sending a message, SMTP doesn’t prompt for new password.


Message delivery options for future message delivery to not properly function.


Request change for default location of sent messages.


Messaging Server folders should be only one tree.


Login.wapb should take user name and password as POST.


Contact information with non-ASCII data is not saved correctly in Dress Book Server.


Outlook crashes on a particular message.


Shared calendars are not getting synched in Outlook 2003.


Unable to receive new mail in Outlook 2003 without logging out and logging back into Outlook.


Unread Mail does not get updated.


State of mail in preview pane does not change.


Subscribed calendar cannot be viewed in multi-calendar view.


Need silent install of Outlook Connector on the desktop.


Outlook Today does not display message counts for mail folders.


Property page on a mail folder displays an error message.


User is able to drag and drop subfolders into Deleted Items folder


Read receipts are not sent when requested.


Outlook 2000 sometimes creates PSTs named S1OC.pst for a 7.0 profile.


Cannot save changes in Contacts after session expires.


Sent messages are saved as unread.


Empty outlook calendar calls calstore_fetch_deletedcomponents.wcap when syncing.


Messages are disappearing and appearing again in mail folders.


Messages are stuck in Outbox (Outlook 2000).


Hardcoded pop up messages for double booking not allowed.


Outlook XP crashes during exit.


Cannot remove all values from contacts, categories, and phone fields in Contact Entry.


Undeleted messages are lost after sync with server.


Some messages are displayed as raw HTML.


Upgrade from 6.0 to 7.0 fails to associate the 6.0 psts with the 7.0 profile.


Upgrading from 6.0 (with a password protected pst) to 7.0 fails.


Option “Associate all existing desktop data...” should be checked by default for convert/upgrade.


LDAP/Contacts display order not followed by installer.


Password dialog pops up three times after creating new profile without checking “Saving Password.”


Distribution List in Contacts does not display individual group members after sync.


Messages saved in drafts folder cannot be edited.


Installer displays incorrect error messages.


Error while opening a Contacts group in Address Book Server.


Message crashes Outlook 2003.


Event delegation does not function properly.


Empty attachment received when forwarding inline message.


LDAP users disappear from Outlook distribution list.


Old version number and old product name still appears in places.


Profile setup-wizard window sizing issue.


Some strings in French are truncated in the user interface.


Invitation shows incorrect organizer and attendee in Shared Calendar.


Messages are sent without X-Mailer header.


Content-transfer-encoding and other headers should be sent without capital letters.


Cannot purge unread message in Deleted Items folder.


installation fails if password is incorrectly entered during installation.


Problems occur when renaming a shared mail folder with read and write permission.


A blank value for the default address book server is not allowed in the Deployment Configuration Program.


Different list of folders display for Outlook than display for Communications Express.


Attachments sometimes display as only 1KB in size.


Calendar and Contacts not synched when staring Outlook in offline then switching to online mode.


Online help is not found in Outlook XP.


Problems subscribing to shared mail folder (folder length problem).


Cannot start Outlook in offline mode.


Voting buttons cannot be used while composing messages.


SSL port not automatically set when creating a new profile.


Hardcoded Sun mail server name in error window.


Cannot decode the MSIMAP voting button TNEF and display the correct form.


Event description is not synched with server when edited.


Messages are not marked as read on the server when viewing messages in separate window.


Voting buttons do not work correctly in messages.


Unable to assign “read only” permission to folder when sharing for first time.


Cannot move a subfolder back to top-level folder.


Cannot correctly store LDAP members into Address Book.


No response to requests for read receipts.


Outlook 2000 crashes.


Shared folders do not appear with French version of Outlook XP.


Cannot drag and drop a top-level folder to a shared folder.


Messages with unusual formatted recipient causes Outlook to crash.


Subscribe tab is missing in shared calendar if calendar authentication fails.


Message with attachments cannot be opened when moved to a new folder.


Outlook crashes at startup.


Offline mode does not work.


Email address lost for contact added from LDAP GAL.


Unable to remove all group members.


Subscribed folders do not get unsubscribed when a subscribed folder is renamed.


Unable to continue installation if back button is selected during installation.

Installation and Configuration Notes

Connector for Microsoft Outlook is an Outlook plug-in that requires installation on the end users’ desktop. A deployment and configuration program is provided to aid the organization in deploying Connector for Microsoft Outlook.


Before you install Sun Java System Connector for Microsoft Outlook, please check for the latest information about any required patches.

The installation and deployment is a three-step process:

  1. Install the administrator package.
  2. Create an installation package for the end user.
  3. Deploy the installation package.

The Connector for Microsoft Outlook packages ships an installer for the administrator package. The system administrator should prepare a special installation package called the Setup Wizard for the end user. The Setup Wizard installs and configures the Connector for Microsoft Outlook software on your desktop. This installation package is designed to simplify and automate the installation process.

For installation, configuration, and deployment instructions please see the following:

Converting Data

One of the optional steps that can be performed during setup and configuration of Connector for Microsoft Outlook is the conversion of data that resides on the desktop. This conversion process is invoked only if the administrator checks the “Convert existing profile” option during the creating of the end user installation package. Please note, this conversion process is not intended to, nor does it replace the need for server-based migration. Sun provides a migration service to help move data and users from an existing Exchange deployment to Sun Java Enterprise System.

LDAP Attributes

In order for Connector for Microsoft Outlook to function correctly, the following LDAP attributes in the Sun Java System Directory Server should be indexed for at least presence and equality to improve the overall performance:

For more information on these attributes, see Sun Java System Calendar Server Administration Guide and Sun Java System Messaging Server Administration Guide.

Sun Java System Calendar Server Considerations

Sun Java System Calendar Server considerations for the Sun Java System Connector for Microsoft Outlook 7 2005Q1 release include:

Calendar Server Installation

The latest version of Calendar Server is available at

It is recommended that customers also install the latest set of patches, which are available at Sun Solve (

For detailed installation instructions, refer to the Sun Java Enterprise System Installation Guide. For configuration instructions, refer to the Sun Java System Calendar Server Administration Guide.


If you are migrating from Calendar Server 5.x to the latest version of Calendar Server, you must run the cs5migrate_recurring utility to convert the database in order to comply with the Connector for Microsoft Outlook data model. Consult technical support for information about the cs5migrate_recurring utility.

Required LDAP mail Attribute

Calendar Server 6 2004Q2 (and later) requires users to have the LDAP mail attribute for both user and resource calendars.

For clients to use Microsoft Outlook to schedule resource calendars (for example, for meeting rooms or equipment such as a notebook computer or overhead projector), each resource must have an email address, even though email is not actually needed. The LDAP mail attribute specifies this email address.

You might specifically need to add the LDAP mail attribute as follows:

5.x Installation. Before you run the cs5migrate_recurring migration utility, add the mail attribute to users for both user and resource calendars. To add the mail attribute, use the Calendar Server csattribute utility or a utility such as the Directory Server ldapmodify utility.

New Installation (6 2004Q2 or later). Provision the LDAP mail attribute for existing users for both user and resource calendars using the Calendar Server csattribute utility or a utility such as the Directory Server ldapmodify utility.

If you create new calendars or users after installation, use the required -m email option to specify an email address when you run these Calendar Server utilities:

For related information about csattribute, csresource, and csuser, refer to the Sun Java System Calendar Server Administration Guide. For related information about ldapmodify utility, refer to the Sun Java System Directory Server Resource Kit Tools Reference.

Example: Adding the email LDAP Attribute to a Resource Calendar

The following example adds the LDAP mail attribute for a conference room named “Room100” on the server. This example configures Messaging Server. If you are using another email server, refer to that product’s documentation for the equivalent process.

  1. Add the mail attribute to the LDAP server using the csattribute utility:
  2. # ./csattribute -a add Room100

  3. To check that the attribute has been set, use the csattribute list command with the -v (verbose) option:
  4. # ./csattribute -v list Room100


    cn=Room 100,ou=conferenceRooms,dc=sesta,dc=com has mail:

Example: Setting up the bitbucket Channel for the Resource Email

The following examples set up the bitbucket channel for Messaging Server or the equivalent for Sendmail for the email generated for resource calendars. These examples use a resource named “Room100” on the server. If you don’t set up the bitbucket channel (or equivalent), you will need to periodically delete the email messages sent to the resource calendar.

For Messaging Server:

  1. Ensure the bitbucket channel is defined in the imta.cnf file.
  2. To direct messages to the bitbucket channel, create the email address for the resource using the csresource utility:
  3. # ./csattribute -a add Room100

For Sendmail:

  1. In the /etc/aliases file on the appropriate host, add an entry such as:
  2. # Resource/Conference room aliases

    Room100: /dev/null

  3. Add the email address for the resource to the LDAP directory using the csresource utility:
  4. # ./csattribute -a add Room100


    To enable these changes, you might also need to rebuild alias tables or configurations. Refer to the documentation for Messaging Server (or your email product) as well as your site's own documentation and procedures regarding changes to mail services.

Email Alias (mailalternateaddress Attribute)

If you need to setup an email aliases for a calendar user, use the LDAP mailalternateaddress attribute. The LDAP mail attribute provides the primary mail address, and the LDAP mailalternateaddress attribute is used for email aliases. Both attributes map the mail addresses to the user’s calendar ID (calid).

For example, to add the mailalternateaddress attribute for a user named John Smith with these values:

Use these Calendar Server utility commands:

# ./csuser -g John -s Smith -y password -l en -m -c johnsmith create johnsmith

# ./csattribute -a add johnsmith

# ./csattribute -a add johnsmith

Shared Calendar LDAP Lookup Configuration

If Directory Server requires authentication for the Shared Calendar LDAP lookup then the service.wcap.userprefs.ldapproxyauth parameter must be set in the ics.conf file as follows:

If service.wcap.userprefs.ldapproxyauth is “yes”, you must also set the appropriate LDAP ACI for the calmaster entry. For example, to set the calmaster ACI for proxy authentication for the domain, use the ldapmodify tool as follows:

changetype: modify
add: aci
aci: (target="ldap:///uid=*,")(targetattr=*)(version 3.0;
acl "allowAll-calmaster";allow (all)(userdn="ldap:///uid=calmaster,");)


aci: (target="ldap:///uid=*,")(targetattr=*)(version 3.0;
acl "allowproxy-calmaster";allow(proxy)(userdn="ldap:///uid=*,");)

Outlook Free-Busy Lookup and SSL

The Microsoft Outlook Free/Busy Lookup option is not supported for users who access Calendar Server in SSL mode. To use both SSL and non-SSL mode for the same Calendar Server instance, users must specify different port numbers, as follows:

For information about SSL, refer to Chapter 9, “Using SSL With Calendar Server” in the Sun Java System Calendar Server Administration Guide.

Calendar Server Delete Log Database

Calendar Server 6 2004Q2 or later includes the Delete Log database (ics50deletelog.db) to store deleted events and todos (tasks). For information, refer to Chapter 7, “Managing the Delete Log Database” in the Sun Java System Calendar Server Administration Guide.

System Folder Mapping Interoperability With Communications Express

While IMAP protocol defines only one system folder for incoming mail (INBOX), mail clients such as Outlook and Sun Java System Communications Express define their own system folders for drafts, sent mail, and deleted mail. The mail clients have no way of distinguishing those folders. These system folders are created by different preferred names and localized names according to locale and client software. This causes multiple physical IMAP folders that are created for a system folder if a single email account is accessed by more than one email client (or same email client, but accessed by a different locale machine).

In Outlook the folder naming is:

In Communications Express the folder naming is:

Defining the System Folders for Outlook

A new Sun Java System Connector for Microsoft Outlook mail system mapping file is available to provide better interoperability between Outlook and Communications Express. This solution allows the administrator to configure how system folders are mapped. The file contains the system folder mapping definitions for Communications Express. The file contains the system folder mapping definitions for Connector for Microsoft Outlook.

You can choose one of the mapping folders files to use as the default system folder mapping definition files in the Deployment Configuration Program (under the Mail tab). Select either Outlook style or Communications Express style to indicate which of these two standards the user program should use to name users’ IMAP folders. Your selection here determines which of two map files, or, will be used to map users’ IMAP folder names. An administrator may, before running this program, edit these files to suit local requirements, as long as the original filenames remain the same.

Defining the System Folders for Communications Express

Next, the system folders for Communications Express need to be defined. The i18n.js file defines the system folder names for Communications Express. This file is located in the /var/opt/SUNWmsgsr/config/html/lang directory, where lang is the specific localized language (for example fr for French). This file needs to be modified so that the mapping entries are similar to the entries in the file.

For example, by default folder mappings in the French i18n.js file are:

i18n[’INBOX’] = ’Inbox’

i18n[’trash folder’] = ’trash’

i18n[’draft folder’] = ’draft’

i18n[’sent folder’] = ’sent’


fldr[’INBOX’] = ’French Inbox’

fldr[’trash’] = ’French Trash’

fldr[’draft folder’] = ’French Draft Folder’

fldr[’sent folder’] = ’French Sent Folder’

The values for i18n[x] are used to create system folders in the IMAP store. For example, if i18n[’trash folder’]= ’trash’, then a folder with folder name trash will be created in the IMAP store. The values for fldr[y] are used for displaying the system folder names in the client interface.

In the file, the similar folder mappings are:


INBOX=’Boite de r�ception’

Deleted Items=’�l�ments supprim�s’


Sent Items =’�l�ments envoy�s’

So, the French i18n.js folder mappings should be modified to match the file:

i18n[’INBOX’] = ’Boite de r�ception’

i18n[’trash folder’] = ’�l�ments supprim�s’

i18n[’draft folder’] = ’Brouillons’

i18n[’sent folder’] = ’�l�ments envoy�s’


fldr[’INBOX’] = ’Boite de r�ception’

fldr[’trash’] = ’�l�ments supprim�s’

fldr[’Drafts’] = ’Brouillons’

fldr[’Sent’] = ’�l�ments envoy�s’

You will need to modify each language represented by a i18n.js file.


Because the i18n.js files are written in UTF8 code, you will need to use and editor that will preserve the UTF8 code.

This new folder mapping definition is only effective for new users.

New users should see only one set of system folders, except in the following case:

A user logs into Outlook with the locale set to French. Later, the same user logs into Communications Express with the preferred language set to English. This user sees system folders trash, draft, sent, �l�ments supprim�s, Brouillons, and �l�ments envoy�s in both Outlook and Communications Express.

Limitations and Issues

This section describes the limitations and known issues that exist in this release of Sun Java System Connector for Microsoft Outlook.


Some limitations exist in this release of Sun Java System Connector for Microsoft Outlook. The key limitations are:

Known Issues

This section describes the known issues at the time of this release of Sun Java System Connector for Microsoft Outlook. If known, bug IDs are included in parentheses.

The categories of issues discussed in this section are:


Installation and Upgrade

Communications Express Interoperability

The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Sun Java System Communications Express:

Microsoft Exchange Interoperability

The following issues relate to the interoperability between Sun Java System and Microsoft Exchange:


The following issues relate the calendar portion of Sun Java System Connector for Microsoft Outlook only:


The following issues relate the mail portion of Sun Java System Connector for Microsoft Outlook only:

Localization Issues

The following issues affect the localized versions of Sun Java System Connector for Microsoft Outlook:

How to Report Problems and Provide Feedback

If you have problems with Sun Java System Connector for Microsoft Outlook, contact Sun customer support using one of the following mechanisms:

So that we can best assist you in resolving problems, please have the following information available when you contact support:

Sun Welcomes Your Comments

Sun is interested in improving its documentation and welcomes your comments and suggestions.

To share your comments, go to and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this book is Sun Java System Connector for Microsoft Outlook 2005Q1 Release Notes, and the part number is 819-0031-10.

Additional Sun Resources

Useful Sun Java System information can be found at the following Internet locations:

Copyright � 2005 Sun Microsystems, Inc. All rights reserved.

Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and in other countries.


U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

Use is subject to license terms.

This distribution may include materials developed by third parties.

Portions may be derived from Berkeley BSD systems, licensed from U. of CA.

Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.

Copyright � 2005 Sun Microsystems, Inc. Tous droits r�serv�s.

Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plus des brevets am�ricains list�s � l'adresse et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.


L'utilisation est soumise aux termes du contrat de licence.

Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.

Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.

Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.

Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.