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
Initial release of these release notes (Version 7 2005Q1).
Beta release of these release notes.
Final review draft of these release notes.
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:
- Support for Outlook 2003
- One store provider for mail, calendar, tasks, and contacts
- Default Outlook folders, Sent Items, and Drafts are stored on the server and are accessible from other mail clients
- Contact folder of Outlook is mapped to Address Book service and is part of Sun Java System Communications Express
- Support for Find and Advanced Find
- Support for Organize and Rules Wizard features in Outlook
- Outlook desktop notifications and reminders
- Enhanced interoperability between Sun Java System Communications Express and Outlook
- Seamless upgrade from previous version
- Conversion of IMAP/POP profiles to Sun Java System Connector for Microsoft Outlook 7 2005Q1 profile.
Key Features in Sun Java System Connector
for Microsoft Outlook
The following key features and functionality are available with this release:
- Access to Sun Java System Messaging Server, and Sun Java System Calendar Server.
- Access to e-mail folders on the Messaging Server via IMAP4.
- Access to calendar data (events, appointments) and tasks stored in the Calendar Server via WCAP.
- Access to corporate directory via LDAP.
- Access to contacts stored in the Address Book server.
- Typical Outlook mail features:
- Share mail folders with one or more users.
- Subscribe to other users’ mail folders.
- Typical calendar features:
- E-mail based group scheduling.
- Share calendar with other users and set specific permissions for shared calendars.
- Subscribe to other users’ calendars.
- Delegate calendar access to others.
- Typical task-related functionality (new task, modify task).
- Client-side rules attached to folders and data types
- Desktop-only access to notes and journal.
- Read-only offline access to mail and calendar.
- Interoperability with web client (Communications Express).
The following describes the system requirements and recommendations for Sun Java System Connector for Microsoft Outlook.
- Operating systems:
- Microsoft Outlook versions:
- Sun Java System Calendar Server 6 2005Q1
Calendar Server customers who have deployed previous versions of Sun Java System Calendar Server need to engage with Sun Professional Services to enable their data to be converted and migrated to the new format. A Sun Professional Services offering is available. This migration is required for the use of Outlook, and is necessary because of the underlying changes in the storage and management of recurring events. No migration service is required for new customers of Calendar Server 6 2004Q2 or later.
- Sun Java System Messaging Server 6 2005Q1
Both Calendar Server and Messaging Server are installed via Sun Java Enterprise System. You can download Sun Java Enterprise System from: http://wwws.sun.com/software/download/java_system.html.
- Web Publishing Wizard (required for Outlook 2000 only)
If you are using Windows 2000, check for the Wpwiz.exe program file to determine if you have the Web Publishing Wizard installed on your computer. For example, if your programs are installed on your C drive, check the following location:
C:\Program Files\Web Publish\Wpwiz.exe
Or, search for the Wpwiz.exe file using the Find or Search command from the Start button.
If you don’t have the Web Publishing Wizard on your Windows 2000 computer, you can download this from:
To install, the administrator can copy the entire Microsoft Office/Outlook CD and put in a network drive. Enter the location in the Desktop Deployment program. The end user installation picks up and installs the LDAP service from the specified location. For more information, see “Desktop Deployment Toolkit Components” in the Sun Java System Connector for Microsoft Outlook Deployment Planning Guide.
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
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 http://sunsolve.sun.com/pub-cgi/show.pl?target=patchpage for the latest information about any required patches.
The installation and deployment is a three-step process:
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:
- Sun Java System Connector for Microsoft Outlook Installation Guide (/docs/cd/E19955-01/819-0029)—Describes how to install the administrator package.
- Sun Java System Connector for Microsoft Outlook Administration Guide (/docs/cd/E19955-01/819-0027)—Describes how to create an installation package for the end user using the Deployment configuration Program.
- Sun Java System Connector for Microsoft Outlook Deployment Planning Guide (/docs/cd/E19955-01/819-0028)—Describes the deployment of the Connector for Microsoft Outlook.
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.
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 http://www.sun.com/software/product_categories/email_calendar_collaboratoin.html.
It is recommended that customers also install the latest set of patches, which are available at Sun Solve (http://sunsolve.sun.com).
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 sesta.com server. This example configures Messaging Server. If you are using another email server, refer to that product’s documentation for the equivalent process.
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 sesta.com 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:
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 email@example.com -c johnsmith create johnsmith
# ./csattribute -a firstname.lastname@example.org add johnsmith
# ./csattribute -a email@example.com 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 sesta.com domain, use the ldapmodify tool as follows:
aci: (target="ldap:///uid=*,o=sesta.com")(targetattr=*)(version 3.0;
acl "allowAll-calmaster";allow (all)(userdn="ldap:///uid=calmaster,o=sesta.com");)
aci: (target="ldap:///uid=*,o=sesta.com")(targetattr=*)(version 3.0;
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 uwc_folders.map file contains the system folder mapping definitions for Communications Express. The outlook_folders.map 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, outlook_folders.map or uwc_folders.map, 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 sjoc_folders.map 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 sjoc_folders.map 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 sjoc_folders.map 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:
- Every distinct identity in the Directory Server (for example, users, resources, conference rooms) must have an email address. For more information, see Required LDAP mail Attribute.
- Arbitrary attachments in calendar events are not stored back in the server.
- Rich text in the appointment and meeting description field is lost once the same calendar event is modified in the Communications Express client.
- Message recall functionality is not available.
- Description of events is not available when checking availability.
- Sub-folders created under the default calendar folder are locally stored. The primary default calendar folder and other calendar folders are stored on the server.
- Free/Busy lookup does not display TENTATIVE or OUT-OF-OFFICE color coding.
- The properties for Sun Java System Connector for Microsoft Outlook cannot be modified using the Tools->Services option from the Outlook menu. To modify the properties:
- Free/busy lookup using SSL is not supported. See Outlook Free-Busy Lookup and SSL for more information.
- Installing Sun Java System Connector for Microsoft Outlook on Exchange servers is not supported.
- The installer will not run if Outlook is in Internet Mode. In Outlook 2000, the Internet Mail Only mode can contain both a POP and IMAP profile. Those profiles are not upgraded or converted in to the Connector for Microsoft Outlook 7 2005Q1 version.
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:
- For converting or creating a user profile in silent installation mode, it is mandatory to have a default profile. (4938665)
- User unable to open Outlook for the first time without administrative rights. (5053786)
- If previously converted user profiles exist, the Deployment Configuration Program will not create a new profile when the “Convert/Upgrade or create” option is selected in the User Profiles tab. The administrator must create a profile using the “Create new user profiles without conversion/upgrade” option. (5107345)
- Contacts forwarded as attachments are not saved in the Contacts folder (Outlook 2000). (6212865)
- Using the web tool bar crashes Outlook. (6214643)
- Limited offline support:
- Downloading messages from online to offline is not supported.
- Contacts are supported as read only. Calendar, Tasks, and mail are supported as read/write.
- During an offline session, if any folder that resides on the IMAP server is modified using Outlook, and then another client is used to modify the same folder, the changes may become lost when the user returns to online mode in Outlook.
- Recurring tasks are not supported.
Installation and Upgrade
- When upgrading from the Connector for Microsoft Outlook 6 2004Q2 version to the Connector for Microsoft Outlook 7 2005Q1 version, if the server names and port numbers have changed, the upgrade only takes into consideration the old server names and port numbers.
- During the upgrade to the Connector for Microsoft Outlook 7 2005Q1 version, the DLLs from the previous version are not removed. Users can see the interface for both versions. (5104844)
Communications Express Interoperability
The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Sun Java System Communications Express:
The name in the From: header changes if an attendee replies to an event invitation and attaches the winmail.dat calendar invitation. For example, Joe (using Outlook) sends an invitation to an event to Bob. Bob replies to Joe, using an email client that automatically sends the original winmail.dat calendar attachment back to Joe. When Joe opens the reply, the From: header is changed to Joe.
- Events created in Outlook that span multiple days are not displayed correctly in Communications Express. For example, if you create an event in Outlook with a start time of Tuesday at 8:00am and an end time of Friday at 8:00am, it displays correctly in Outlook. In Communications Express, however, the month view displays the event as a one-day event on Tuesday with a duration of 0 hours. The duration is incorrectly displayed in all views. The day and week view correctly displays the event in Communications Express. (4958773)
- Email ID is a must for Outlook. (4969029)
If a task is created (either in Outlook or Communications Express) while Outlook is synched with the server, then the task is deleted and the user attempts to switch to the Tasks folder in Outlook, an “Unable to display all cells due to low memory” error is generated. As a workaround, switch to another folder and then back again to the Tasks folder.
- Unable to authenticate Address Book Server from Outlook if Address Book is deployed on Application Server (6189264).
- RTF formatting in Outlook is not preserved if the description text is edited using Communications Express.
- Differences exist in privacy classes between Outlook and Communications Express. Outlook has two privacy classes (Private and Public), while Communications Express has three classes (private, Date and Time only, and Public). In Outlook, a private event is created as a “Date and Time only” event in Communications Express. A public event in Outlook maps to the public event in Communications Express. Similarly, a Communications Express “Date and Time Only” event maps as a private event in Outlook, and a public event maps as a public event in Outlook. A Communications Express private event also maps to Outlook as a private event. To create a private event in Outlook so it appears as a private event in Communications Express, select “Free” from the “Show time as:” field. The Communications Express private event cannot be seen in a shared Calendar folder by another user.
- There are differences in the way free/busy is implemented in Outlook and Communications Express. The default private event is free in Communications Express. If the event is to be included for free/busy lookup, then it should manually be set to busy. In Outlook the default events are busy for both private and public events.
- If you export an event from Communications Express to a file in Outlook format, you cannot import the event from the same file into Outlook.
- Incompatibilities exist in how recurring tasks are implemented in Outlook and Communications Express. Recurring tasks in Outlook do not conform to RFC 2445 while Communications Express is specifically designed to work with RFC 2445-compliant information. This causes problems when recurring task information is passed between Outlook and Calendar Server.
Information stored locally by Outlook does not always match information which is stored on the Calendar Server. Sun Java System Connector for Microsoft Outlook, for example, does not transfer any information dealing with the recurrence of a task to the Calendar Server. Any tasks created in Outlook (recurring or non-recurring) appears in Communications Express as single tasks. A task that is created in Communications Express only uses the recurring information from the Calendar Server when that task is written for the first time in the Outlook client and not during any modification of any existing task on Outlook.
For these reasons, recurring tasks viewed in Outlook and tasks viewed in Communications Express appear different in many cases. We recommend that users who work with recurring tasks choose either Outlook or Communications Express and not attempt to work with recurring tasks in both clients interchangeably.
- If a message is sent from Outlook in Rich Text format, the message contains a plain text body with no formatting and a WINMAIL.DAT attachment. The WINMAIL.DAT attachment contains the Rich Text message along with any other attachments that may have been added. Because the format is Microsoft proprietary, only Outlook can read the WINMAIL.DAT attachment. Communications Express (and any other client) sees only the unformatted text message and a WINMAIL.DAT attachment. It is recommended that HTML format be used instead of Rich Text format to send messages.
- If contacts groups in Outlook contain external SMTP mail recipients or other contacts groups, they are not seen by Communications Express. Communications Express cannot send mail to these recipients.
- Outlook saves calendar events and tasks (any calendar folder not under the Calendar folder tree), contacts (any contacts folder not under the Contacts folder tree), notes, and journals in the Messaging Server. Because the data is saved as Microsoft TNEF format, Communications Express cannot decode and correctly display them.
Microsoft Exchange Interoperability
The following issues relate to the interoperability between Sun Java System and Microsoft Exchange:
Email filters (rules) which are created using LDAP GAL entries do not work in Outlook 2000. If the same procedure with an Exchange profile (adding an LDAP GAL and using one of the LDAP entries directly in a mail filter/rule) shows the same results in the Exchange profile. That is, in Outlook 2000, the filter will not work. In Outlook XP (and Outlook 2003), the filter does work.
As a workaround, add to your personal address book any contacts that you want to use in an email filter/rule. Then, use the local contact in the rule instead of the LDAP entry.
If a distribution list from a personal address book (in the contacts folder) is added to an email rule/filter, a dialog from the rules wizard appears asking if the distribution list should be expanded. The rules/filter requires that the rule contain the expanded list of email addresses. If an LDAP group (from an LDAP GAL) is added to a rule/filter, the rules wizard does not ask to expand the group and simply uses the email address of the group itself. Rules which are created using LDAP groups do not work. This same behavior can be observed in profiles which connect to Exchange (and which have LDAP directories configured as services).
As a workaround, add the individual group members to your personal address book and use them in the email filter.
The following issues relate the calendar portion of Sun Java System Connector for Microsoft Outlook only:
- If delegate accepts or declines an invitation from the organizer’s Shared Inbox, the calendar event is added to delegate’s calendar, but not to the organizer’s calendar.
- Microsoft TNEF messages are sent when sending calendar attachments. iTIP and iMIP calendar attachments are not supported.
- All Day events may become a non-All Day events (one event scheduled from 12:00am until 12:00pm) if the desktop time zone is different from the Calendar Server calendar time zone.
- When creating an invitation from Outlook, if an error occurs when saving it to Calendar Server, the invitation is still sent by Outlook.
- If a recurring event is created by Outlook with no end date, it will be saved internally in the Calendar Server with a finite number of occurrences. Also, free/busy information is only kept up to the number of occurrences kept in the Calendar Server. For example, if you create a daily recurring event at 10:00 am in Outlook and the Calendar Server only keeps up to 60 repeating events, on day 61 the event still appear on Outlook but the 10:00 am time appears as “free” when calculating availability.
- Changing permissions of a calendar requires restarting Outlook for the new permission setting to take effect for the Calendar folder in the Shared Calendar.
- Tasks displayed in Shared Calendars are the login user’s tasks, not the subscribed user’s tasks. The calendar view always shows the login user’s tasks.
- If you create a recurring invitation in Outlook, but delete a single instance of that event, the recipients (attendees) will not see the deleted invitation if Calendar Server has not processed the initial recurring invitation before the deletion.
The following issues relate the mail portion of Sun Java System Connector for Microsoft Outlook only:
The “Large Table” support flag must be manually set. To do this:
- Open the Folders Properties dialog by right-clicking on “Folders - your user name” and select Properties for “Folders - your user name.”
- In the Folder Properties dialog, click on Advanced...
- Select the Advanced tab in the Sun Java System Connector for Microsoft Outlook dialog.
- Click the Personal Folders button and check the box next to “Allow upgrade to large tables” in the Personal Folders dialog.
- Click OK to all open dialogs and restart Outlook.
The following issues affect the localized versions of Sun Java System Connector for Microsoft Outlook:
- Localized online help on Windows machines may contain one or more issues in the following areas (5035363, 5031913, 5028387, 5028413, 5034886, 5028420):
- Installer for the Deployment Configuration Program is not localized. Some of the installation panels for the Connector for Microsoft Outlook are also in English (5028359).
- Unrecognized characters appear while entering a Korean full name in the Korean Connector for Microsoft Outlook installation panel (5028453).
- Log file may contain unrecognized characters (5033783).
- Sender name is not displaying properly for messages (6213093).
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:
- Sun Software Support services online at
So that we can best assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://www.oracle.com/technetwork/indexes/documentation/index.html 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:
- Documentation for Sun Java System Connector for Microsoft Outlook
- Sun Java System Documentation
- Sun Java System Professional Services
- Sun Java System Software Products and Service
- Sun Java System Software Support Services
- Sun Java System Support and Knowledge Base
- Sun Support and Training Services
- Sun Java System Consulting and Professional Services
- Sun Developer Support Services
- Sun Java System Software Training
- Sun Software Data Sheets
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 http://www.sun.com/patents 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 http://www.sun.com/patents et un ou les brevets suppl�mentaires ou les applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
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.