Version 7 2005Q4
These release notes contain important information available at the time of release of Version 7 2005Q4 of Sun Java TM 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 2005Q4.
The most up-to-date version of these release notes can be found at http://docs.sun.com/coll/1312.1. 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.
Description of Changes
Beta release of these release notes (Version 7 2005Q4)
Final release of these release notes (Version 7 2005Q4)
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 email to an SMTP mail server for delivery, and sends modified email 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 2005Q4 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.
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 email 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:
Compose, reply, and forward messages
Use Microsoft Word to write and edit messages
Apply spell check and encryption to message body
Apply address completion to message headers
Add signatures to messages
Share mail folders with one or more users.
Subscribe to other users’ mail folders.
Typical calendar features:
Create new appointments and events (all-day, recurring, public, private)
Suggest alternate time for events
Track responses to event requests
Email 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
Notes and Journal stored in IMAP folders.
Full offline support for mail, calendar, and address book.
Interoperability with web client (Communications Express).
Global Address List manages server-side message filters.
New features in Sun Java System Connector for Microsoft Outlook 7 2005Q4 include:
Global Address List with browsing capabilities
Removal of dependency on Microsoft LDAP
Out-of-office setting, and ability to notify user that setting is activated at login
Progress displayed when synchronizing large folders
Setting mail filters
Ability to search for users for mail folders sharing
Name and email address automatically set and updated from LDAP
Option to preview body of all messages
This section describes the requirements and recommendations for Sun Java System Connector for Microsoft Outlook.
The Sun Java System Communications Express patch 118540–20 must be applied to Connector for Microsoft Outlook. You can download this patch from Sunsolve.
The following operating systems are supported:
Microsoft Windows 2000 (Service Pack 3 or higher)
Microsoft Windows XP (Service Pack 1 or higher)
Microsoft Windows 2003 Terminal Server
The following versions of Microsoft Outlook are supported:
Outlook 2000 SP3 (Workgroup mode)
Outlook 2002 SP2
Other requirements for Connector for Microsoft Outlook are:
Sun Java System Calendar Server 6 2005Q4
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 2005Q4
Both Calendar Server and Messaging Server are installed via Sun Java Enterprise System. You can download Sun Java Enterprise System from: http://www.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 http://www.microsoft.com.
Although this web site states that this download for Web Publishing Wizard is for Windows 95 and Windows NT 4.0, this is the correct version to download for Windows 2000.
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 the SunSolve website for the latest information about any required patches.
The installation and deployment is a three-step process.
Install the administrator package.
Create an installation package for the end user.
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:
Sun Java System Connector for Microsoft Outlook 7 2005Q4 Installation Guide describes how to install the administrator package.
Sun Java System Connector for Microsoft Outlook 7 2005Q4 Administration Guide describes how to create an installation package for the end user using the Deployment configuration Program.
Sun Java System Connector for Microsoft Outlook 7 2005Q4 Deployment Planning Guide 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 the Sun Java System Calendar Server 6 2005Q4 Administration Guide and the Sun Java System Messaging Server 6 2005Q4 Administration Guide.
This sections describes any compatibility issues that exist in the Connector for Microsoft Outlook.
This section describes Sun Java System Calendar Server considerations for the Connector for Microsoft Outlook.
The latest version of Calendar Server is available at theCollaboration and Communication download site.
It is recommended that customers also install the latest set of patches, which are available at SunSolve.
For detailed installation instructions, refer to theSun Java Enterprise System 2005Q4 Installation Guide for UNIX. For configuration instructions, refer to theSun Java System Calendar Server 6 2005Q4 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.
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:
csresource utility for new resource calendars
csuser utility for new users
For related information about csattribute, csresource , and csuser, refer to theSun Java System Calendar Server 6 2005Q4 Administration Guide. For related information about ldapmodify utility, refer to the Sun Java System Directory Server Resource Kit Tools Reference.
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.
Add the mail attribute to the LDAP server using the csattribute utility:
# ./csattribute -a mail=Room100@sesta.com add Room100
To check that the attribute has been set, use the csattribute list command with the -v (verbose) option:
# ./csattribute -v list Room100 ... cn=Room 100,ou=conferenceRooms,dc=sesta,dc=com has mail: Room100@sesta.com
The following examples sets up the bitbucket channel for Messaging Server for the email generated for resource calendars. This example uses 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.
Ensure the bitbucket channel is defined in the imta.cnf file.
To direct messages to the bitbucket channel, create the email address for the resource using the csresource utility:
# ./csattribute -a mail=Room100@bitbucket.sesta.com 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.
The following example sets up the bitbucket channel for Sendmail for the email generated for resource calendars. This example uses 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.
In the /etc/aliases file on the appropriate host, add an entry such as:
# Resource/Conference room aliases Room100: /dev/null
Add the email address for the resource to the LDAP directory using the csresource utility:
# ./csattribute -a mail=Room100@sesta.com add Room100
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:
User ID (uid) and calid: johnsmith
Email address: email@example.com
Email Alias’s: firstname.lastname@example.org and email@example.com
Use these Calendar Server utility commands:
# ./csuser -g John -s Smith -y password -l en -m firstname.lastname@example.org \ -c johnsmith create johnsmith # ./csattribute -a email@example.com add johnsmith # ./csattribute -a firstname.lastname@example.org add johnsmith
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:
Anonymous binding: service.wcap.userprefs.ldapproxyauth = "no"
Authenticated proxy binding: service.wcap.userprefs.ldapproxyauth = "yes"
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:
dn: o=usergroup changetype: modify add: aci aci: (targetattr="icscalendar || cn || givenName || sn || uid || mail")(targetfilter=(objectClass=icscalendaruser))(version 3.0; acl "Allow calendar administrators to proxy - product=ics,class=admin,num=2,version=1"; allow (proxy) groupdn = "ldap:///cn=Calendar Administrators,ou=Groups,o=usergroup";)
For the domain basedn node, the following example shows the correct ACI:
dn: o=sesta.com,o=usergroup changetype: modify add: aci aci:(targetattr="icscalendar || cn || givenName || sn || uid || mail") (targetfilter=(objectClass=icscalendaruser))(version 3.0; acl "Allow calendar users to read and search other users - product=ics,class=admin,num=3,version=1"; allow (search,read) userdn = "ldap:///uid=*, ou=People, o=sesta.com, o=usergroup";)
If there is no domain, add this ACI to the root suffix itself by removing the o=sesta.com part on the dn: line.
The Calendar Server configuration program, csconfigurator.sh, adds these ACIs. If you are upgrading from Java Enterprise System Release 1, you must rerun the configuration program to get these updated ACIs.
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:
SSL Mode — To access Calendar Server using SSL, use the SSL port. The default port number is “443” and is set in the ics.conf file by this parameter:
service.http.ssl.port = "443"
Non-SSL Mode — To use the Outlook Free/Busy Lookup option, access Calendar Server using the regular HTTP port. The default port number is “80” and is set in the ics.conf file by this parameter:
service.http.port = "80"
For information about SSL, refer to Chapter 8, Configuring SSL, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
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 18, Administering the Delete Log Database, in Sun Java System Calendar Server 6 2005Q4 Administration Guide.
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:
Deleted Items=Deleted Items
Sent Items=Sent Items
In Communications Express the folder naming is:
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.
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:
[fr] INBOX=’Boîte de réception’ Deleted Items=’Éléments supprimés’ Drafts=’Brouillons’ 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’] = ’Boîte de réception’ i18n[’trash folder’] = ’Éléments supprimés’i18n[’draft folder’] = ’Brouillons’ i18n[’sent folder’] = ’Éléments envoyés’ ... fldr[’INBOX’] = ’Boîte 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.
Before users log into Communications Express, the users' preferred language needs to be set. To do this, set the preferredLanguage or preferredLocale attribute using the ldapmodify command.
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.
All the client products that are released with Sun Java System Communications Services allow users to search the corporate directory and their own address books. While this does work, some LDAP tuning might improve the user experience.
This section discusses:
Whether using Communications Express or Connector for Microsoft Outlook, performing search in your personal contacts or the public address book for a particular string is a locale-specific operation. For example, a French user searching for “Gaelle” expects to get back entries containing the string “Gaelle” but also any entry containing the string “Gaëlle.”
The various rules driving the way entries are presented to a user based on locale are called collation rules or collation order. The collation order provides language and cultural-specific information about how the characters of a given language are to be sorted. It identifies things like the sequence of the letters in the alphabet, how to compare letters with accents to letters without accents, and if there are any characters that can be ignored when comparing strings. The collation order also takes into account culture-specific information about a language, such as the direction in which the language is read (left to right, right to left, or up and down).
The Sun Java System Directory Server supports a large variety of locales and collation rules (See “Identifying Supported Locales” in the Sun Java System Directory Server 5 2005Q1 Administration Reference). Depending on your user base, you first need to choose the locale that makes the most sense in your environment. In the following, we will use the English (US) locale (OID = 220.127.116.11.18.104.22.168.22.214.171.124.1) as an example.
To specify which locale to use when performing a search, use the matching rule filter syntax, described in “Searching an Internationalized Directory” in the Sun Java System Directory Server 5 2005Q1 Administration Reference. This syntax lets you to specify the locale as well as the type of search (equality, substring, and so on).
For example, the following filter will perform a substring comparison (.6) on the CN attribute, using the English (US) collation rules (126.96.36.199.188.8.131.52.184.108.40.206.1). The filter looks at the CN for strings starting with “Gae”
When performing an LDAP search, most performance problems are due to the fact that indexes are not present or are not properly configured. By default, the Directory Server is configured so that lookups issued by Communications Express or by Connector for Microsoft Outlook are indexed and should return in a reasonable amount of time. Nevertheless, the Directory Server is not set up for international searches. So one need to alter the existing indexes so that they take into account the collation rules that have been chosen. This is described in the “Managing Indexes” section in the Sun Java System Directory Server 5 2005Q1 Administration Guide.
For example, the CN attribute is indexed by default in the userRoot suffix:
# ldapsearch -D "cn=Directory manager" -b "cn=cn,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config" "objectclass=*" cn=cn,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config objectClass=top objectClass=nsIndex cn=cn nsSystemIndex=false nsIndexType=pres nsIndexType=eq nsIndexType=sub
To enable it for international searches using the English (US) collation rules, add one nsMatchingRule attribute with the English (US) OID. The clients perform substring searches so it is necessary to add the substring suffix (“.6”) to the OID :
#ldapmodify -D "cn=Directory manager" dn: cn=cn,cn=index,cn=userRoot,cn=ldbm database, cn=plugins,cn=config changetype: modify add: nsMatchingRule nsMatchingRule: 220.127.116.11.18.104.22.168.22.214.171.124.1.6
Do not add any space, tab, or other non-visible characters at the beginning or at the end of the value.
The nsMatchingRule is a multivalued attribute. Different types of searches for the same OID, or different OIDs can be added.
One must then run the db2index.pl script located under serverroot/slapd-instance:
# perl db2index.pl -D "cn=Directory Manager" -w \ secret -n userRoot -t cn
This operation is run online and may take some time to finish. Alternatively the suffix can be reinitialized. See “Reinitializing a Suffix” in the Sun Java System Directory Server 5 2005Q1 Administration Guide.
The console can also be used to add the nsMatchingRule (see the “Managing Indexes” section in the Sun Java System Directory Server 5 2005Q1 Administration Guide).
In the following sections, the list of indexes that need to be modified is provided. Ensure that no non-indexed searches are performed. This can be done by looking at the Directory Server access log file (and looking for a notes=U in the search results entries).
The search filter used by Communications Express needs to be changed to accommodate the matching rule syntax. This is achieved by enabling the collation rule parameters specified in the db_config.properties file (which resides under deployed-path/WEB-INF/ldappstore (for personal store) and deployed-path/WEB-INF/corp-dir (for corporate directory).
The parameters are:
# Collation Rule # Uncomment below to apply collation rule # collation_rule=en-US # Search Fields for which collation rule should be applied. # The fields provided here should be disambiguator formatted fields # e.g. entry/displayname, person/givenname etc. # Uncomment below to supply the comma-separated fields # search_fields=entry/displayname
Uncomment the collation_rule and search_fields parameters to enable the collation rule. In order to specify a separate set of field or fields in the search, change the value of search_fields to the desired values. The collation_rule can contain either the language tag or the OID corresponding to that language (in the example 126.96.36.199.188.8.131.52.184.108.40.206.1) without the suffix specifying the type of search. The Web Container Instance needs to be started after making the change.
The following attributes should be indexed on the LDAP Server for international search against Communications Express:
cn (under the ou=people/ou=groups suffix)
displayname (under the o=piServerDb suffix)
The Connector for Microsoft Outlook can be configured to bind using a DN and password or to bind as anonymous. To enable anonymous access to the corporate directory, add an ACL at the root level of the ou=people/ou=group sub-trees.
For example, if the root level is dc=red,dc=sesta,dc=com, do the following:
#ldapmodify -D "cn=Directory manager" dn: dc=red,dc=sesta,dc=com changetype: modify add: aci aci: (targetattr != "userPassword") (version 3.0;acl "Anonymous access"; allow (read,compare,search) (userdn = "ldap:///anyone");)
New in this 7 2005Q4 release, Connector for Microsoft Outlook now allows the end user to browse directories. When bringing up the address book page, the first 10 entries in the directory are shown. The user may then scroll up and down, or type a few characters and see the results automatically refreshed. This is a change from previous versions of Connector for Microsoft Outlook where the user was only able to search for one particular user.
To enable this feature while keeping good performance, the connector relies on two LDAP control extensions called Virtual List View (VLV) and Server Side Sorting of Search Results (RFC 2891). The following ldapsearch example returns the list of supported controls:
# ldapsearch -s base "objectclass=*" supportedControl supportedControl=2.16.840.1.1137220.127.116.11 supportedControl=2.16.840.1.113718.104.22.168 supportedControl=2.16.840.1.113722.214.171.124 supportedControl=2.16.840.1.1137126.96.36.199 supportedControl=1.2.840.1135188.8.131.523 ------> Server Side Sort Control supportedControl=2.16.840.1.1137184.108.40.206 ------> VLV Control supportedControl=2.16.840.1.1137220.127.116.11 supportedControl=2.16.840.1.113718.104.22.168 supportedControl=2.16.840.1.113722.214.171.124 supportedControl=2.16.840.1.1137126.96.36.199 supportedControl=188.8.131.52.184.108.40.206.220.127.116.11 supportedControl=18.104.22.168.22.214.171.124.126.96.36.199 supportedControl=2.16.840.1.1137188.8.131.52 supportedControl=184.108.40.206.4.1.1466.29539.12 supportedControl=2.16.840.1.1137220.127.116.11 supportedControl=2.16.840.1.113718.104.22.168 supportedControl=2.16.840.1.113722.214.171.124
The Sun Java System Directory Server does support both controls. Nevertheless, the VLV control is by default only available to authenticated users:
ldapsearch -D "cn=Directory Manager" -b \ "oid=2.16.840.1.1137126.96.36.199,cn=features,cn=config" \ "objectclass=*" aci oid=2.16.840.1.1137188.8.131.52,cn=features,cn=config \ aci=(targetattr != "aci")(version 3.0; acl "VLV Request Control"; \ allow( read, search, compare, proxy ) userdn = "ldap:///all";)
To allow anonymous access to the VLV control, add the corresponding ACI:
#ldapmodify -D "cn=Directory Manager" \ dn: oid=2.16.840.1.1137184.108.40.206,cn=features,cn=config \ changetype: modify add: aci aci: (targetattr !="aci")\ (version 3.0; acl "VLV Request Control"; allow (compare,read,search) \ userdn = "ldap:///anyone"; )
To improve the performance of searches requiring VLV plus Sort, create a Browsing Index in the Directory Server (as described in “Managing Browsing Indexing” in the Sun Java System Directory Server 5 2005Q1 Administration Guide). Each Browsing Index is specific to one base DN, search filter, scope, and sorting attribute. The VLV settings can be tuned on the client side using the deployment configuration tool.
In that particular case, a Browsing Index needs to be created for a base dn equal to dc=red,dc=iplanet,dc=com, a filter equal to (&(mail=*)(cn=*)), using a sort on the cn attribute. The Browsing Index information is added into the configuration containing the base dn (in this case userRoot):
#ldapmodify -D "cn=Directory Manager" dn: cn=Browsing red.sesta.com,cn=userRoot, cn=ldbm database,cn=plugins,cn=config changetype: add objectClass: top objectClass: vlvSearch cn: Browsing red.sesta.com vlvbase: dc=red,dc=sesta,dc=com vlvscope: 2 vlvfilter: (&(mail=*)(cn=*)) aci: (targetattr="*") (version 3.0; acl "VLV for Anonymous"; allow (read,search,compare) userdn="ldap:///anyone";) dn: cn=Sort by cn, cn=Browsing red.sesta.com,cn=userRoot, cn=ldbm database,cn=plugins,cn=config changetype: add objectClass: top objectClass: vlvIndex cn: Sort by cn vlvSort: cn
Next run the vlvindex command located under serverroot/slapd-instance:
# ./vlvindex -n userRoot -T "Sort by cn"
There are no documentation updates at this time.
The following lists the bugs fixed in Sun Java System Connector for Microsoft Outlook 7 2005Q4:
Connector for Microsoft Outlook should support Mail and Calendar proxy auth.
View Message Source does not display anything.
Need a cancel button to abort downloading of email.
View Message Source does not display anything.
LDAP client should be renamed as “Microsoft LDAP provider: Sun Java System LDAP Directory.”
Online help search does not work.
OpenEntry failed with hr = 0x80040107.
Alarm not stored in the server for attendee.
Multi-byte does not auto-select under the Sun Java System LDAP directory.
“Create/convert vs. install only” checkbox not correctly initialized and saved in deployment configuration wizard.
Offline mode can change to online mode with blank password.
Installation failed; log indicates required configuration parameter LDAP Host is missing.
Send bcc to sender option not working for new profile.
Calendar event reminder box not checked after Exchange migration.
Login to Outlook profile with lots of messages in Inbox takes a long time
Message never sent when sending a large message on a slow connection.
Alarms are not synching from Communications Expressto Outlook and vice versa.
Messages saved in Drafts in Outlook lose header information when viewed from other clients.
Messages sometimes remain in Outbox in Outlook 2000 but are still delivered.
Changing From: address and choosing Contact address as the From: does not correctly display “On behalf Of.”
Need to be able to share Address Book with another user.
User would like to be able to share a mail folder using a group name (group of users).
IMAP provider does not add reference headers.
Expunge does not work for mail folder other than Inbox.
Request for a progress bar during startup.
Message-flag: header not taken into account.
Sending a message from Excel with check password not enabled causes problems.
Messages in shared mail folder do not display.
Cannot open encrypted messages generated by Mozilla.
Email content in read receipt notification mail on Outlook 2002.
“Read receipt” doesn't work for individual messages.
Using Powerpoint to send for Review hangs Outlook when sending to a recipient.
Duplicated Inbox (English Inbox and Localized “Inbox”) folders in non-English Outlook.
Multiple byte character name IMAP folder is missing in English environment.
Cannot create profile in Windows (English) when first logging into Windows XP (Japanese) plus Outlook (Japanese).
Outlook might crash when loosing IMAP+SSL connection.
Calendar events sometimes lose body content if the content is large.
Users with a password containing characters other than letters cannot login to address book server using Connector for Microsoft Outlook.
README title was not translated correctly.
Contacts lose Notes content if the content is large.
Sender name does not display properly for messages composed with ISO2022JP in Windows XP (Japanese) with Outlook 2003 (Japanese).
Japanese translation is not suitable in User Profiles tab.
Can't view group members when composing messages in Outlook.
Attachment appears as Winmail.dat when attaching a file in a meeting request using Connector for Microsoft Outlook.
Message not translated in Deployment Configuration Program under German locale.
Copying a message from local store to IMAP folder causes received date to be changed to current date.
LDAP filter for Microsoft LDAP connector should be able to be set at install time (on Outlook 2000).
Add “Do not show this dialog again” for Debugging logging.
Outlook crashes when creating a calendar appointment with no content.
Password clearly appears in Connector for Microsoft Outlook log file under some conditions.
Contacts without email address appearing in the Outlook Address Book user interface.
EXPUNGE never get called if deleting a contact from an IMAP Contact folder.
Save changes for a IMAP Contact entry in PST when permissions are not granted.
Message does not appear when deleted from Inbox then selecting Deleted Items folder.
If SMTP AUTH is not enabled on the server, and Outlook requires it, mail is indefinitely submitted.
Build 214 installer displays version as 213.
Outlook 2000 hangs while downloading messages the first time. No progress bar is displayed.
Image picture.JPG appears as picture.JPG.jpg (case sensitive extension).
message with content-type application does not show attachment (clip) icon in message list.
When forwarding a message with winmail.dat , the forwarded message contains two winmail.dat attachments.
Option to empty and resynchronize IMAP folders required.
Mail stays in the Outbox of Outlook instead of going to the Sent folder.
When sharing or subscribing to folders in Outlook, the exact user name needs to be provided.
Need to be able to force synchronization on a per-folder basis.
Problems with advanced “find” dialog.
Users should not have to click “find” when searching for addresses.
Messages composed in Rich Text allow all recipients to see BCC recipients when viewed from Outlook.
BCC recipients are not saved in Sent Items or Draft folder.
Incorrect RRULE generated for yearly events.
Unable to install on Windows XP machine.
Receiving error “It is not allowed to turn on the transparency flag for a resource.”
Need help handling Error code 81.
Background HTML is sent as attachment when forwarding messages.
Installer doesn't check AUTH SMTP check box for newly created Outlook profiles.
Installation request to have the international searches automated.
Inserted pictures when forwarded are forwarded as attachments.
All-day event is 1 hour late when Windows daylight savings is enabled.
After installation on end-user machine, Outlook hangs at its startup during first attempt (Outlook XP and Outlook 2003).
Cannot see ACLs for default contact folder after deleting .pst file.
Image in a multipart/related appears as an attachment if content-location is used.
Shared Contacts name is not displaying for the Shared contacts folder for French or Japanese.
No follow-up is received for by recipient.
The Personal address book of a user is not refreshed when a Contact is deleted from the subscribed user.
When member details of a distribution list is modified and saved, the member is deleted from the distribution list.
Error occurs when a member is added to distribution list and to contact list from subscribed user.
Modifying a contact in a distribution list deletes the contact from the distribution list.
Contact names in distribution list are scrambled after context synchronization.
Multipart/mixed containing a multipart/report crashes Outlook.
Some messages are sent with a body where the text is replaced by multiple CRLF (Outlook XP French).
Moving mail folder from parent to child causes the folders to disappear.
Powerpoint 2003 crashes after sending mail as an attachment.
Message count is not shown in status bar once background synchronization is performed.
Message count is not shown in status bar once background synchronization is performed.
Error code 79 fromCalendar Server is not handled by Connector for Microsoft Outlook.
Message with outer message/rfc822 not correctly displayed.
User cannot view the shared tasks of another user.
Connector for Microsoft Outlook and Communications Express cannot read messages sent from Powerpoint 2000 with “send to mail recipient” menu.
Outlook XP hangs on startup with preview pane.
Creating a group and adding a member at the same time does not cause an error to occur.
Outlook crashes when the Mail Filter page is invoked.
Invitations created or modified from Outlook should not trigger Calendar Servernotifications.
Outlook crashes when an offline user attempts to access the mail filter page.
When the owner deletes a shared folder, the subscriber still sees the shared folder and an error occurs.
User with read only permission appears to be allowed to delete messages in folder.
Address book synchronization fails after just one contact.
Error must occur when creating mail folders with invalid character.
Option to look up user in directory needed when sharing Contacts.
Option to look up user in LDAP needed when subscribing to a Contact.
Cannot delete messages when performing right-click on trash in Outlook.
Messages with multipart/alternative containing several HTML parts displays the wrong HTML part.
Auto-preview pane does not work for unread messages.
Outlook delivers multiple copies of the same message.
Validation for user typing id of mail and contacts Permission page.
Allow user entering groupid in Permission page to set mail folder ACL for group.
Allow user select from GAL to set mail folder group ACL.
Display “myright” for Permission subscribed mail folder.
OPEN_IF_EXISTS flag in MAPI call Folder create not correctly handled.
When member is added to shared contact and distribution list from subscribed user, member added to address book.
Access Control Entries added are not effective when used in conjunction with Communications Express.
Cannot view messages in Unread Mail folder.
Mail folder errors due to folder name case insensitive matching rule.
Mail filter loops if there is an error in retrieving ACLs on a folder.
MAPI clients such as activesync or msn desktop crash Outlook when synchronization occurs.
Version number out of sync in the installer.
When composing a new message, the View->Message Source menu item should be disabled.
Installer should set Global Address List in the list of searchable address books.
Menu option “change this folder to contain” is too small.
Change this folder type pull-down items are not correctly translated in French.
Unnecessary warning “LDAP - 'User preference search base', must contain a value” when creating package.
Invitee receives meeting mail which mostly shows the conflict with another nonexistent meeting.
Allow Vacation Message heading to be customizable.
Progress bar displays after selecting IMAP folder soon after login, but no progress is shown.
GAL does not take into account timeout parameter.
Should not allow “user select group” for Permission page of Calendar and Contacts.
After synchronization of address book, group (from GAL) which was added to address book is deleted.
Error message displays when a user is searched in the Global Address List on Outlook 2003.
GAL becomes unusable.
Bringing up first page of the GAL causes too many LDAP searches.
Viewing the details of a GAL entry results in duplicate LDAP search.
GAL does not gracefully handle lost connection.
User interface issues.
When distribution list is modified by adding group from GAL, the group is deleted after synchronization.
Option “Maximum number of search results returned” in LDAP tab does not work.
Unable to open the deployment configuration program on non-English operating system.
If package creation is cancelled, Deployment Configuration Program continues to create.
Shared contacts modification from subscriber not reflected in provider's address book.
Error: “CABContainer::GetProps MAPI_E_NO_SUPPORT” seen in Outlook XP.
admin.exe does not use or launch localized user interface.
Accessing mail filters takes a long time.
Crash in background sync.
Installer does not upgrade old version.
Random crash in GAL code.
Saving GAL entry to local contacts folder does not synchronize correctly in Outlook 2000.
Outlook crashes, if empty string is given to GAL Advanced Search (Find).
resolvename fails when called from Outlook and only one match is found.
Installer doesn't follow installation rights for restricted user login.
GAL should not work in offline mode.
When typing non-ASCII characters in GAL browser window, index moves to the entry after the match.
Two vcard attachments are shown i n Outlook when receiving a message from Communications Express with vcard.
Response time slow and errors exist when entering single character into To field.
Silent mode created profile does not work.
Options under “User .pst->IMAP/POP profile setting” are confusing.
Outlook hangs while opening a folder while Google desktop is fetching info in the background.
Outlook.exe randomly crashes.
Profile conversion on Outlook XP results in corrupt profile.
Sort by message size does not work under certain circumstances.
Cannot set message as unread when starting in offline mode.
Drag and drop from PST of a contact results in wrong email address.
No help file associated with Deployment Configuration Program.
Outlook crashes when adding an LDAP group from GAL.
Bug report should correctly spell system information.
Contacts.html is missing for all languages.
Label for VLV sort attribute is corrupted for Japanese.
Dialog for Login Address Book Server is unusual in Japanese.
Smaller font on Global Address List tab (Japanese).
Email displayed twice when third party software plugs into Outlook.
Japanese characters cannot be displayed on Global Access List tab.
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:
Right click the Outlook icon and select Properties.
The Properties dialog appears.
Select Folders - < your user name> from the list of services.
Free/busy lookup using SSL is not supported. See Outlook Free-Busy Lookup and SSL
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 2005Q4 version.
Recurring tasks are not supported.
During an offline session, if any item in a Calendar, Task, mail, or Contact folder is modified using Outlook, and then another client on the server is used to modify the same item, the changes made offline are lost when the user returns to online mode in Outlook. The changes made by the other client on the server remain.
When creating a new event in offline mode, the invitation is saved to the user's Outbox. If, while still in offline mode, the user opens the invitation, the invitation disappears from the Outbox once it is closed.
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)
Unable to install if Outlook is upgraded. (6253840 and 6254598)
If a user with a current Connector for Microsoft Outlook profile upgrades Outlook XP, the existing profile fails to open. Attempting to install a fresh profile also fails.
Workaround: When the Outlook version is upgraded or changed, please uninstall and reinstall Connector for Microsoft Outlook.
Upgrade defaults to previous servers and ports.
When upgrading from the Connector for Microsoft Outlook 6 2004Q2 version to the Connector for Microsoft Outlook 7 2005Q4 version, if the server names and port numbers have changed, the upgrade only takes into consideration the old server names and port numbers.
The following issues relate to the interoperability between Sun Java System Connector for Microsoft Outlook and Sun Java System Communications Express:
Address change in From: header. (4949659)
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.
Email ID is a must for Outlook. (4969029)
If a person with a calendar ID but no email ID is invited to an event in Communications Express, this person is not displayed as an attendee in Outlook. An email ID is required for Outlook.
Unsubscribing to a calendar does not remove the calendar from the folder list. (5032872)
If you subscribe to or unsubscribe from a calendar in Communications Express, the information is updated in Outlook only after Outlook has been restarted. Additionally, if the LDAP configured for lookup is a replica, the subscription list is not updated until the replica is updated.
Error generated when Outlook synchronizes with server. (6175103)
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.
Configuration parameter needs to be set in order for address book server contacts to be properly synchronized. (6229276)
The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .
Folders with the same name but different case cannot both be displayed. Only one folder is displayed. (6268483)
If a user creates a folder in Outlook (for example, TEST) and then later in Communications Express creates a folder with the same name but different case (for example, Test) only the first folder created ( TEST) is displayed in Connector for Microsoft Outlook.
If the user then deletes the existing folder TEST in Communications Express and keeps (or creates) the folder of the same name but different case ( Test), when the user first logs onto Outlook, the folder TEST is deleted but the folder Test is not shown until the user exits and logs back into Outlook.
The following are additional issues related to Communications Express interoperability that do not have bug ids:
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.
The following issues relate to the interoperability between Sun Java System and Microsoft Exchange:
Free Busy Proxy for Exchange does not return complete Free/Busy information. (6174201)
Tab is inserted within a long subject. (6194768)
If a message from an Exchange server is sent to a server using Connector for Microsoft Outlook and Sun Java System Messaging Server with an exceedingly long subject, the message is sent with a tab inserted within the subject line.
Rules are not working correctly. (6200399)
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.
Rules from people or distribution lists do not work. (6203018)
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.
Cannot recover deleted items. (6255190)
After selecting “Empty Deleted Items Folder,” Connector for Microsoft Outlook does not allow for recovery of deleted items.
Receipt of a message with embedded OLE objects and HTML in RTF from Exchange (versions 5.5, 2000, and 2003) to Connector for Microsoft Outlook does not work.
The following issues relate the calendar portion of Sun Java System Connector for Microsoft Outlook only:
Creating a new calendar profile brings up the old calendar reminders. (5104189)
When you logging in for the first time to a newly created calendar profile in Outlook that is set to your default Calendar Server, Outlook alarms pop up for old events as well as for future events.
Names of subscribed calendars not visible in Calendar view. (6190293)
When you first subscribe to a calendar, the calendar name is labeled as “Calendar”, not the name of the subscribed calendar. To see the name of the subscribed calendar, log off Outlook and then log back into Outlook. The subscribed calendar’s name should be displayed.
Opening a shared calendar link does not hook into subscription (Outlook 2003). (6292026)
In Outlook 2003, clicking the calendar icon at the bottom of the left pane, displays the calendar view. Within that calendar view, clicking “Open a Shared Calendar” displays a dialog that allows the user to enter the user name of a shared calendar. When the user name of a known shared calendar is entered, the error “Unable to display the folder. Your profile is not configured to support this operation for this user.” is displayed. This occurs also with contacts and tasks.
As a workaround, to view a shared calendar, select the shared calendar folder in the folders list.
The following are additional issues related to the calendar portion of Connector for Microsoft Outlook that do not have bug ids:
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:
Saving attached files inside a forwarded message. (4946488)
When an attachment is received as part of a forwarded message, the attachment cannot be saved after double-clicking on the attachment. To save the attachment, right-click on the attachment, then chose “Save As.”
If a user’s mailbox contains over 16,000 messages in the inbox, Outlook does not download all messages. (5099436)
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 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.
Cannot move a message resulting from a search to another folder. (6227085)
In Outlook XP, if a user searches for a message and then attempts to move a message resulting from that search to another folder, an error occurs.
Outlook 2003 Junk Mail Filter does not work. (6312677)
The “Junk Email” feature available in Outlook 2003 (select Tools->Option) does not function with Connector for Microsoft Outlook. Senders that are set to be filtered using this tool are not filtered. As a workaround, use the Tools->Mail Filter option.
The following issues relate to the Address Book portion of the Sun Java System Connector for Microsoft Outlook.
Deleting a contact from Communications Express does not delete it from Outlook. (6225049)
The Communications Express configuration parameter delete_perm in the db_config.properties file needs to be set to false in order for Outlook to capture contact entries which have been deleted from Communications Express. The entry should be:
The default is true. The entry can be found at /var/opt/SUNWuwc/WEB-INF/config/ldapstore/db_config.properties .
Shared contact not removed from Address Book after unsubscribing. (6267180)
After unsubscribing to a shared contact, it is not removed from the “Show Names from the” list of the Address Book. Two workarounds exist:
If the subscribed contact has been added to the “Show Names from the” list of the Address Book,” the user should uncheck the “Show this folder as an email Address Book” option from the “Outlook Address Book” property page before unsubscribing from the contact.
Remove the contact directly from the address book properties.
In Outlook XP:
Select Tools>Email account.
Then choose “View or change existing directories or address books.” and select “Microsoft Outlook Address Book” to change.
Select the item to remove from your address book.
In Outlook 2000:
Select Tools>Services..., from the Outlook menu.
The Services window is displayed.
Select the “Services” tab.
Select “Outlook Address Book” from the list of services set up in your profile and click “Properties.”
The Microsoft Outlook Address Book properties window is displayed.
Select the item to remove from your address book and click Close.
Note that user must logout and logon again to take the effect.
Login to Address Book Server fails if the proxy configured in the default web browser is down (6315910).
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):
Index list is not sorted in localized languages.
Online help context search using non-English words is difficult.
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).
“Contacts” is garbled (6212970).
In the “Select members” window, the item “Contacts” in the “Show names for the” combo box is garbled (Japanese and Chinese versions of Outlook 2003 on Windows XP).
Japanese characters garbled when printing from configuration program (6309420).
If Japanese characters are included at printing from the Deployment Configuration Program, they are garbled.
Description of some buttons missing in Setup Wizard (6309494).
In the Traditional Chinese version, some words as button labels are missing in the description part of the Setup Wizard panels (“Next,” “Install,” “Back,” and “Cancel”).
Setup Wizard dialog corrupted (6309523).
The Setup Wizard dialog in the Outlook 2000 on Windows 2000 Japanese and Chinese versions is corrupted for “Sun Communication Server.”
Cannot find profile if profile name is in Japanese (6310160).
If a profile is in Japanese, the conversion fails (Outlook 2003 on Windows 2003).
Outlook does not start when profile is manually created (6310190).
After creating a profile manually, Outlook cannot start with this profile. The error message “Sun Java System Connector for Microsoft Outlook error” is displayed.
Cannot convert IMAP profile name in Japanese (6313321).
If an IMAP profile already exists, and this profile has never been used by Outlook, the conversion fails.
Connector for Microsoft Outlook does not use any redistributable files.