test

Sun Java System Communications Services 2005Q4 Release Notes

Chapter 6 Sun Java System Connector for Microsoft Outlook 7 2005Q4 Release Notes

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.

Note –

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 6–1 Sun Java System Connector for Microsoft Outlook Revision History

Date 

Description of Changes 

July 2005 

Beta release of these release notes (Version 7 2005Q4) 

October 2005 

Final release of these release notes (Version 7 2005Q4) 

About Sun Java System Connector for Microsoft Outlook, 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.

Note –

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.

Key Features in Sun Java System Connector for Microsoft Outlook

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

What’s New in This Release

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

Requirements

This section describes the requirements and recommendations for Sun Java System Connector for Microsoft Outlook.

Note –

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:

The following versions of Microsoft Outlook are supported:

Other requirements for Connector for Microsoft Outlook are:

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

Note –

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.

ProcedureInstalling Connector for Microsoft Outlook

  1. Install the administrator package.

  2. Create an installation package for the end user.

  3. Deploy the installation package.

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

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

Converting Data

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

LDAP Attributes

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

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

Compatibility Issues

This sections describes any compatibility issues that exist in the Connector for Microsoft Outlook.

Sun Java System Calendar Server Considerations

This section describes Sun Java System Calendar Server considerations for the Connector for Microsoft Outlook.

Calendar Server Installation

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.

Note –

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

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

  1. Add the mail attribute to the LDAP server using the csattribute utility:

    # ./csattribute -a mail=Room100@sesta.com add Room100

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

ProcedureSetting up the bitbucket Channel for the Resource Email (Messaging Server)

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.

  1. Ensure the bitbucket channel is defined in the imta.cnf file.

  2. To direct messages to the bitbucket channel, create the email address for the resource using the csresource utility:

    # ./csattribute -a mail=Room100@bitbucket.sesta.com add Room100

    Note –

    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.

ProcedureSetting up the bitbucket Channel for the Resource Email (Sendmail)

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.

  1. In the /etc/aliases file on the appropriate host, add an entry such as:


    # Resource/Conference room aliases
Room100: /dev/null

  2. Add the email address for the resource to the LDAP directory using the csresource utility:

    # ./csattribute -a mail=Room100@sesta.com add Room100

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 john.smith@sesta.com 
\ -c johnsmith create johnsmith
# ./csattribute -a mailalternateaddress=johns@sesta.com add johnsmith
# ./csattribute -a mailalternateaddress=jsmith@sesta.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:

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.

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 8, Configuring SSL, in Sun Java System Calendar Server 6 2005Q4 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 18, Administering the Delete Log Database, in Sun Java System Calendar Server 6 2005Q4 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:

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

Note –

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.

LDAP Configuration in Clients

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:

Setting up International Searches

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 = 1.3.6.1.4.1.42.2.27.9.4.34.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 (1.3.6.1.4.1.42.2.27.9.4.34.1). The filter looks at the CN for strings starting with “Gae”

cn:1.3.6.1.4.1.42.2.27.9.4.34.1.6:=Gae*

Updating the Indexes

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: 1.3.6.1.4.1.42.2.27.9.4.34.1.6
Note –

Do not add any space, tab, or other non-visible characters at the beginning or at the end of the value.

Note –

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

Setting up the Search Filter in Communications Express

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

Allowing Anonymous Access to the corporate Directory

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");)

Allowing Directory Browsing

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.113730.3.4.2 
supportedControl=2.16.840.1.113730.3.4.3 
supportedControl=2.16.840.1.113730.3.4.4 
supportedControl=2.16.840.1.113730.3.4.5 
supportedControl=1.2.840.113556.1.4.473  ------> Server Side Sort Control 
supportedControl=2.16.840.1.113730.3.4.9 ------> VLV Control 
supportedControl=2.16.840.1.113730.3.4.16 
supportedControl=2.16.840.1.113730.3.4.15 
supportedControl=2.16.840.1.113730.3.4.17 
supportedControl=2.16.840.1.113730.3.4.19 
supportedControl=1.3.6.1.4.1.42.2.27.9.5.2 
supportedControl=1.3.6.1.4.1.42.2.27.9.5.6 
supportedControl=2.16.840.1.113730.3.4.14 
supportedControl=1.3.6.1.4.1.1466.29539.12 
supportedControl=2.16.840.1.113730.3.4.12 
supportedControl=2.16.840.1.113730.3.4.18 
supportedControl=2.16.840.1.113730.3.4.13

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.113730.3.4.9,cn=features,cn=config" \
"objectclass=*" aci oid=2.16.840.1.113730.3.4.9,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.113730.3.4.9,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"

Documentation Updates

There are no documentation updates at this time.

Problems Fixed in This Release

The following lists the bugs fixed in Sun Java System Connector for Microsoft Outlook 7 2005Q4:

2107172

Connector for Microsoft Outlook should support Mail and Calendar proxy auth.

2116848

View Message Source does not display anything.

4875157

Need a cancel button to abort downloading of email.

4967870

View Message Source does not display anything.

5022085

LDAP client should be renamed as “Microsoft LDAP provider: Sun Java System LDAP Directory.”

5028420

Online help search does not work.

5028541

OpenEntry failed with hr = 0x80040107.

5035442

Alarm not stored in the server for attendee.

5038124

Multi-byte does not auto-select under the Sun Java System LDAP directory.

5038216

“Create/convert vs. install only” checkbox not correctly initialized and saved in deployment configuration wizard.

5038757

Offline mode can change to online mode with blank password.

5047818

Installation failed; log indicates required configuration parameter LDAP Host is missing.

5091363

Send bcc to sender option not working for new profile.

5099266

Calendar event reminder box not checked after Exchange migration.

5108660

Login to Outlook profile with lots of messages in Inbox takes a long time

5109537

Message never sent when sending a large message on a slow connection.

6173626

Alarms are not synching from Communications Expressto Outlook and vice versa.

6180425

Messages saved in Drafts in Outlook lose header information when viewed from other clients.

6183786

Messages sometimes remain in Outbox in Outlook 2000 but are still delivered.

6193123

Changing From: address and choosing Contact address as the From: does not correctly display “On behalf Of.”

6194778

Need to be able to share Address Book with another user.

6194896

User would like to be able to share a mail folder using a group name (group of users).

6195481

IMAP provider does not add reference headers.

6197649

Expunge does not work for mail folder other than Inbox.

6199186

Request for a progress bar during startup.

6199964

Message-flag: header not taken into account.

6203173

Sending a message from Excel with check password not enabled causes problems.

6204359

Messages in shared mail folder do not display.

6204495

Cannot open encrypted messages generated by Mozilla.

6206259

Email content in read receipt notification mail on Outlook 2002.

6206392

“Read receipt” doesn't work for individual messages.

6207446

Using Powerpoint to send for Review hangs Outlook when sending to a recipient.

6209895

Duplicated Inbox (English Inbox and Localized “Inbox”) folders in non-English Outlook.

6210992

Multiple byte character name IMAP folder is missing in English environment.

6211112

Cannot create profile in Windows (English) when first logging into Windows XP (Japanese) plus Outlook (Japanese).

6211879

Outlook might crash when loosing IMAP+SSL connection.

6212853

Calendar events sometimes lose body content if the content is large.

6212895

Users with a password containing characters other than letters cannot login to address book server using Connector for Microsoft Outlook.

6212963

README title was not translated correctly.

6212973

Contacts lose Notes content if the content is large.

6213093

Sender name does not display properly for messages composed with ISO2022JP in Windows XP (Japanese) with Outlook 2003 (Japanese).

6215104

Japanese translation is not suitable in User Profiles tab.

6215157

Can't view group members when composing messages in Outlook.

6216569

Attachment appears as Winmail.dat when attaching a file in a meeting request using Connector for Microsoft Outlook.

6216657

Message not translated in Deployment Configuration Program under German locale.

6217379

Copying a message from local store to IMAP folder causes received date to be changed to current date.

6218593

LDAP filter for Microsoft LDAP connector should be able to be set at install time (on Outlook 2000).

6219391

Add “Do not show this dialog again” for Debugging logging.

6219555

Outlook crashes when creating a calendar appointment with no content.

6221249

Password clearly appears in Connector for Microsoft Outlook log file under some conditions.

6221384

Contacts without email address appearing in the Outlook Address Book user interface.

6221491

EXPUNGE never get called if deleting a contact from an IMAP Contact folder.

6221500

Save changes for a IMAP Contact entry in PST when permissions are not granted.

6222698

Message does not appear when deleted from Inbox then selecting Deleted Items folder.

6224103

If SMTP AUTH is not enabled on the server, and Outlook requires it, mail is indefinitely submitted.

6224510

Build 214 installer displays version as 213.

6224517

Outlook 2000 hangs while downloading messages the first time. No progress bar is displayed.

6224755

Image picture.JPG appears as picture.JPG.jpg (case sensitive extension).

6225078

message with content-type application does not show attachment (clip) icon in message list.

6225092

When forwarding a message with winmail.dat , the forwarded message contains two winmail.dat attachments.

6225094

Option to empty and resynchronize IMAP folders required.

6226160

Mail stays in the Outbox of Outlook instead of going to the Sent folder.

6226599

When sharing or subscribing to folders in Outlook, the exact user name needs to be provided.

6226607

Need to be able to force synchronization on a per-folder basis.

6227247

Problems with advanced “find” dialog.

6227260

Users should not have to click “find” when searching for addresses.

6227673

Messages composed in Rich Text allow all recipients to see BCC recipients when viewed from Outlook.

6228303

BCC recipients are not saved in Sent Items or Draft folder.

6228571

Incorrect RRULE generated for yearly events.

6228797

Unable to install on Windows XP machine.

6230650

Receiving error “It is not allowed to turn on the transparency flag for a resource.”

6230655

Need help handling Error code 81.

6230806

Background HTML is sent as attachment when forwarding messages.

6231629

Installer doesn't check AUTH SMTP check box for newly created Outlook profiles.

6232561

Installation request to have the international searches automated.

6232649

Inserted pictures when forwarded are forwarded as attachments.

6233695

All-day event is 1 hour late when Windows daylight savings is enabled.

6236697

After installation on end-user machine, Outlook hangs at its startup during first attempt (Outlook XP and Outlook 2003).

6236969

Cannot see ACLs for default contact folder after deleting .pst file.

6237032

Image in a multipart/related appears as an attachment if content-location is used.

6238069

Shared Contacts name is not displaying for the Shared contacts folder for French or Japanese.

6238386

No follow-up is received for by recipient.

6240786

The Personal address book of a user is not refreshed when a Contact is deleted from the subscribed user.

6241494

When member details of a distribution list is modified and saved, the member is deleted from the distribution list.

6241511

Error occurs when a member is added to distribution list and to contact list from subscribed user.

6241650

Modifying a contact in a distribution list deletes the contact from the distribution list.

6241654

Contact names in distribution list are scrambled after context synchronization.

6242792

Multipart/mixed containing a multipart/report crashes Outlook.

6244760

Some messages are sent with a body where the text is replaced by multiple CRLF (Outlook XP French).

6245292

Moving mail folder from parent to child causes the folders to disappear.

6245704

Powerpoint 2003 crashes after sending mail as an attachment.

624582

Message count is not shown in status bar once background synchronization is performed.

6245822

Message count is not shown in status bar once background synchronization is performed.

6245909

Error code 79 fromCalendar Server is not handled by Connector for Microsoft Outlook.

6246018

Message with outer message/rfc822 not correctly displayed.

6248403

User cannot view the shared tasks of another user.

6248486

Connector for Microsoft Outlook and Communications Express cannot read messages sent from Powerpoint 2000 with “send to mail recipient” menu.

6248556

Outlook XP hangs on startup with preview pane.

6250273

Creating a group and adding a member at the same time does not cause an error to occur.

6251078

Outlook crashes when the Mail Filter page is invoked.

6251878

Invitations created or modified from Outlook should not trigger Calendar Servernotifications.

6252329

Outlook crashes when an offline user attempts to access the mail filter page.

6252818

When the owner deletes a shared folder, the subscriber still sees the shared folder and an error occurs.

6254229

User with read only permission appears to be allowed to delete messages in folder.

6254487

Address book synchronization fails after just one contact.

6254563

Error must occur when creating mail folders with invalid character.

6255167

Option to look up user in directory needed when sharing Contacts.

6255177

Option to look up user in LDAP needed when subscribing to a Contact.

6255241

Cannot delete messages when performing right-click on trash in Outlook.

6255802

Messages with multipart/alternative containing several HTML parts displays the wrong HTML part.

6256553

Auto-preview pane does not work for unread messages.

6258245

Outlook delivers multiple copies of the same message.

6263902

Validation for user typing id of mail and contacts Permission page.

6265019

Allow user entering groupid in Permission page to set mail folder ACL for group.

6265024

Allow user select from GAL to set mail folder group ACL.

6265029

Display “myright” for Permission subscribed mail folder.

6265053

OPEN_IF_EXISTS flag in MAPI call Folder create not correctly handled.

6266400

When member is added to shared contact and distribution list from subscribed user, member added to address book.

6268493

Access Control Entries added are not effective when used in conjunction with Communications Express.

6268850

Cannot view messages in Unread Mail folder.

6270259

Mail folder errors due to folder name case insensitive matching rule.

6272767

Mail filter loops if there is an error in retrieving ACLs on a folder.

6273022

MAPI clients such as activesync or msn desktop crash Outlook when synchronization occurs.

6273699

Version number out of sync in the installer.

6275910

When composing a new message, the View->Message Source menu item should be disabled.

6276394

Installer should set Global Address List in the list of searchable address books.

6276400

Menu option “change this folder to contain” is too small.

6276410

Change this folder type pull-down items are not correctly translated in French.

6276443

Unnecessary warning “LDAP - 'User preference search base', must contain a value” when creating package.

6277792

Invitee receives meeting mail which mostly shows the conflict with another nonexistent meeting.

6278081

Allow Vacation Message heading to be customizable.

6279093

Progress bar displays after selecting IMAP folder soon after login, but no progress is shown.

6279482

GAL does not take into account timeout parameter.

6279945

Should not allow “user select group” for Permission page of Calendar and Contacts.

6281352

After synchronization of address book, group (from GAL) which was added to address book is deleted.

6281399

Error message displays when a user is searched in the Global Address List on Outlook 2003.

6281406

GAL becomes unusable.

6281573

Bringing up first page of the GAL causes too many LDAP searches.

6281588

Viewing the details of a GAL entry results in duplicate LDAP search.

6283869

GAL does not gracefully handle lost connection.

6283887

User interface issues.

6284476

When distribution list is modified by adding group from GAL, the group is deleted after synchronization.

6285121

Option “Maximum number of search results returned” in LDAP tab does not work.

6286602

Unable to open the deployment configuration program on non-English operating system.

6286892

If package creation is cancelled, Deployment Configuration Program continues to create.

6287943

Shared contacts modification from subscriber not reflected in provider's address book.

6289293

Error: “CABContainer::GetProps MAPI_E_NO_SUPPORT” seen in Outlook XP.

6291418

admin.exe does not use or launch localized user interface.

6292161

Accessing mail filters takes a long time.

6292223

Crash in background sync.

6292270

Installer does not upgrade old version.

6292283

Random crash in GAL code.

6293214

Saving GAL entry to local contacts folder does not synchronize correctly in Outlook 2000.

6293388

Outlook crashes, if empty string is given to GAL Advanced Search (Find).

6293962

resolvename fails when called from Outlook and only one match is found.

6294291

Installer doesn't follow installation rights for restricted user login.

6294295

GAL should not work in offline mode.

6294360

When typing non-ASCII characters in GAL browser window, index moves to the entry after the match.

6294688

Two vcard attachments are shown i n Outlook when receiving a message from Communications Express with vcard.

6294698

Response time slow and errors exist when entering single character into To field.

6294835

Silent mode created profile does not work.

6295195

Options under “User .pst->IMAP/POP profile setting” are confusing.

6295258

Outlook hangs while opening a folder while Google desktop is fetching info in the background.

6295739

Outlook.exe randomly crashes.

6298656

Profile conversion on Outlook XP results in corrupt profile.

6301175

Sort by message size does not work under certain circumstances.

6301748

Cannot set message as unread when starting in offline mode.

6302626

Drag and drop from PST of a contact results in wrong email address.

6304343

No help file associated with Deployment Configuration Program.

6305421

Outlook crashes when adding an LDAP group from GAL.

6305480

Bug report should correctly spell system information.

6306813

Contacts.html is missing for all languages.

6306818

Label for VLV sort attribute is corrupted for Japanese.

6306841

Dialog for Login Address Book Server is unusual in Japanese.

6306846

Smaller font on Global Address List tab (Japanese).

6306918

Email displayed twice when third party software plugs into Outlook.

6309549

Japanese characters cannot be displayed on Global Access List tab.

Known Limitations and Issues

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

Limitations

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

Known Issues

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

The categories of issues discussed in this section are:

General

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)

Installation and Upgrade

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.

Communications Express Interoperability

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:

delete_perm=false

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:

Microsoft Exchange Interoperability

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.

Calendar

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:

Mail

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:

  1. Open the Folders Properties dialog by right-clicking on “Folders - your user name” and select Properties for “Folders - your user name.”

  2. In the Folder Properties dialog, click Advanced...

  3. Select the Advanced tab in the Sun Java System Connector for Microsoft Outlook dialog.

  4. Click the Personal Folders button and check the box next to “Allow upgrade to large tables” in the Personal Folders dialog.

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

Address Book Issues

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:

delete_perm=false

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:

Login to Address Book Server fails if the proxy configured in the default web browser is down (6315910).

Localization Issues

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

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.

Redistributable Files

Connector for Microsoft Outlook does not use any redistributable files.