GroupWise 6.5 Support Pack 1

Overview

The information in this Readme file pertains to GroupWise^® 6.5 Support Pack 1.

This Support Pack contains updates for all components contained in the GroupWise 6.5 product. You must have GroupWise 6.5 installed before you install Support Pack 1.

For information on the latest Support Pack issues, see TID 10084510 at the Novell Support Web site .

This Support Pack does not contain updates for GroupWise Messenger. GroupWise Messenger 1.0 Support Pack 1 is a separate download.

1.0 Support Pack Installation

1.1 GroupWise Version Information

GroupWise 6.5 Support Pack 1 can be applied to the following GroupWise version in your software distribution directory:

• GroupWise 6.5 (original version)

When you update the software distribution directory, all GroupWise components should be updated to keep them at the same version level.

1.2 Prerequisites

Before installing GroupWise 6.5 Support Pack 1:

• Ensure that the network login account used to apply the Support Pack has Read, Write, Create, and Erase rights to the GroupWise software distribution directory.
• Ensure that users do not access the software distribution directory during the update process.
• Verify that the GroupWise software distribution directory and files are not flagged Read-Only.

1.3 Downloading the Support Pack

GroupWise 6.5 Support Pack 1 is available in regular format for installing from a local or network driven and in ISO format for burning CDs. You can choose between multilingual and English-only downloads.

1.3.1 Downloading the Regular Version

The regular-format download is available as one self-extracting (.exe) file that includes both administrative and client files.

1. In the list of Support Packs, click GroupWise 6.5 Admin/Client SP1.

2. Click the filename (gw65sp1m.exe for multilingual or gw65sp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

3. Extract the .exe file into a directory at the root of your local drive or to a network server drive that can handle long pathnames.

   The compressed file contains directory paths that could exceed DOS limits.

4. Continue with Section 1.4: Installing the Support Pack.

1.3.2 Downloading the ISO Version

The ISO-format download is available as two self-extracting (.exe) files, one for the GroupWise Administrator CD and one for the GroupWise Client CD.

1. In the list of Support Packs, click GroupWise 6.5 Admin SP1 ISO for the GroupWise Administrator CD.

2. Click the filename (gw65asp1m.exe for multilingual or gw65asp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

3. In the list of Support Packs, click GroupWise 6.5 Client SP1 ISO for the GroupWise Client CD.

4. Click the filename (gw65csp1m.exe for multilingual or gw65csp1e.exe for English only), then follow the instructions to download the file into a temporary directory.

5. Extract the administrator and client .exe files into two separate directories at the root of your local drive or to a network server drive that can handle long pathnames.

   The compressed files contain directory paths that could exceed DOS limits.

6. Burn a separate CD for each directory.

7. Continue with Section 1.4: Installing the Support Pack.

1.4 Installing the Support Pack

Use Windows to run the GroupWise setup.exe program extracted in the preceding section.

1. Click Start > Run > Browse.

2. Select the setup.exe file on the local or network drive.

   or

   Select the setup.exe file at the root of the GroupWise Administrator CD.

3. Click OK to run the GroupWise Installation program.

4. Follow the on-screen instructions provided in the GroupWise Installation program to update the software distribution directory and the administration, agent, and client software that is in production.

5. After applying the Support Pack on NetWare^® servers where GroupWise agents are running, restart the servers to ensure that all updated NLM^TM programs are loaded.

   This will resolve any errors you might see during the update process.

2.0 Installation Issues

2.1 Recommendation for Overwriting Newer Files

When the gwpo.dc and ngwguard.dc files from the original GroupWise 6.5^® release are installed, they receive the date and time when they are installed rather than retaining their original date and time. As a result, they might have a newer date and time than the gwpo.dc and ngwguard.dc files in Support Pack 1. If they do, you receive the following message:

"The files you are installing are older than the files on your system. Do you want to replace these files?"

Typically you should respond No to such a prompt, but in this case you should respond Yes so that the Support Pack version of the .dc files are installed. If necessary, you can manually copy these files from GroupWise 6.5 Support Pack 1 to the corresponding location in the software distribution directory:

\po\gwpo.dc
\domain\gwpo.dc
\po\ngwguard.dc
\client\win32\ngwguard.dc

You might also see this message if you are installing GroupWise 6.5 Support Pack 1 as an update to GroupWise 6 where Support Pack 3 or later has been installed. Again, respond yes to overwrite new newer files.

As an alternative, you can create a new software distribution directory for the GroupWise 6.5 Support Pack 1 files.

2.2 WebAccess and Monitor on the Same Web Server

The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. If you plan to run these applications on the same Web server, you must update all three before any of them will work properly.

2.3 Wireless Device Support for WebAccess and Monitor

The GroupWise WebAccess and Monitor software included in GroupWise 6.5 Support Pack 1 supports the following wireless devices:

• WAP-enabled wireless devices that use HDML 3 or WML 1.1 compatible microbrowsers
• Palm OS* devices

We are continually evaluating and adding support. As we add support for additional devices, we will post the updates at the Novell^® GroupWise Wireless Web site. We encourage you to check this site frequently for updates and news.

2.4 Windows 2000 Service Pack 2 or Later Required for Agents

If the GroupWise Post Office Agent, Message Transfer Agent, Internet Agent, and WebAccess Agent are installed on Windows 2000 and the GroupWise domain and/or post office directories accessed by the agents are on NetWare^® servers, you need to apply Windows 2000 Service Pack 2 or later on the Windows servers. You can download Windows 2000 Service Packs from Microsoft*.

NOTE:  If, as required with the initial release of GroupWise 6, you already installed Microsoft HotFix Q266066 on all Windows 2000 servers where GroupWise agents run, you do not need to apply Windows 2000 Service Pack 2 or later.

2.5 Additional Installation Issues

Installation issues for individual GroupWise components are located under the heading for each component.

3.0 Component Issues

3.1 Administration Issues

3.1.1 Directory Names and Filenames

All directory names in paths to GroupWise domains and post offices can consist of up to 8 characters.

Filenames can also consist of up to 8 characters, with extensions of up to 3 characters. Do not use long filenames for any files used by any GroupWise components. This requirement applies even to files that are not specific to GroupWise (such as SSL certificates and key files).

3.1.2 Server Names

When filling in a UNC Path field in ConsoleOne^®, you must specify the server name. You cannot use an IP address or DNS host name.

3.1.3 ConsoleOne on Windows NT

If you will run ConsoleOne on Windows NT* 4, you must install NT 4 Service Pack 6 before you install ConsoleOne.

3.1.4 GWTSA and Duplicate Source Directories

GWTSA handles situations where the same directory names are used on different volumes to back up by numbering the instances. For example:

Original GWTSA:
GroupWise System/[Dom]Provo2:
GroupWise System/[Dom]Provo2:

Support Pack GWTSA:
GroupWise System/1[DOM]Provo2:
GroupWise System/2[DOM]Provo2:

Each instance is numbered and DOM is in all uppercase letters. After updating GWTSA with Support Pack 1, you must re-create your backup jobs because the path has changed.

3.1.5 Quotas on NSS Volumes

If you use NSS volumes with quotas turned on, then you must turn on quotas on all GroupWise directories. Otherwise, you will receive No Disk Space errors.

3.1.6 TurboFat Compatibility

If you see E811 errors on the POA or the GroupWise client, a possible cause is that TurboFat is corrupting GroupWise database pointers. The solution is to turn off TurboFat.

• To turn off TurboFat on NetWare 5.x servers, use turbodis.nlm.
• To turn off TurboFat on NetWare 6.x servers, use tdis600.nlm.

These NLM^TM programs disable TurboFat at startup.

3.2 Agent Issues

3.2.1 POA Slows Down

If you are running the POA on NetWare 6.0 Support Pack 2 on a multiprocessor such as a Dell* 6650 PowerEdge* or an IBM* Netfinity, the POA might gradually slow down after a few hours or a day, depending on its load. GroupWise client users will also experience extremely slow response time from the POA. Update from NetWare 6.0 Support Pack 2 to Support Pack 3.

3.2.2 Potential CAP Port Conflict

By default, the POA uses 1026 for its CAP (Calendar Access Protocol) port. On some Windows 2000 servers, port 1026 is already used the Windows Task Scheduler or other Windows service. If this occurs, configure the POA to use a different CAP port in ConsoleOne.

3.3 Client Issues

3.3.1 NetWare 5.1 SP1 Compatibility for Client Installation

If you are using the AutoUpdate feature for installing the GroupWise 6.5 client, you might encounter an error if you are installing the client from a NetWare 5.1 server where a Support Pack has been installed. The setupip.exe program used during the AutoUpdate process might not run correctly.

To resolve the problem, you must modify the magnus.conf file located in the following directory:

sys:\novonyx\suitespot\http-web_server_name\config

by adding the following line:

MaximumFilesReturnedInIndex 500

Then run the client installation again.

3.4 Internet Agent Issues

3.4.1 Address Resolution Change Since GroupWise 6

In GroupWise 6 and its Support Packs, there was a problem with the address format used for sending to distribution lists and resources if you set Internet Addressing to one of the following formats (which are not appropriate for distribution lists and resources):

• first_name.last_name@Internet_domain
• last_name.first_name@Internet_domain

Messages to distribution lists and resources were initially undeliverable and were sent to the Internet Agent. The Internet Agent then successfully resolved the addresses and sent the messages back into the GroupWise system. Users did not notice the problem, but some administrators noticed unnecessary traffic through the Internet Agent.

In GroupWise 6.5, the address format problem for sending to distribution lists and resources was corrected. However, users who originally used GroupWise 6 have the erroneous address format for distribution lists and resources in their Frequent Contacts address books. If unnecessary traffic through the Internet Agent is a continuing problem, have users delete distribution lists and resources from their Frequent Contacts address books so that the correct address format is used for name completion in the future.

3.5 Monitor Issues

3.5.1 Restoring Monitor Settings after Reinstallation

Monitor settings are stored in the monitor.xml file in the Monitor installation directory. If you reinstall the Monitor software, the monitor.xml file is backed up as monitor.001. To restore previous Monitor settings, remove the newly installed monitor.xml file and rename monitor.001 to monitor.xml.

3.6 WebAccess Issues

3.6.1 Unicode Support

Unicode* support using UTF-8 encoding has been implemented in WebAccess to provide better support for international character sets. Unicode support enables users to intermix characters within the same message and have all character sets display correctly.

For Support Pack 1, Unicode support is not fully implemented for double-byte character set languages (CBCS languages). In order to correctly compose in a DBCS languages, users need to set their browser accept language to the desired DBCS language. And in Support Pack 1, intermixing two different DBCS languages is not supported. These limitations will be removed in the next version of WebAccess.

If you will update to Support Pack 1 in stages, update the WebAccess Agent first throughout your system, then update the WebAccess Application. If the update to Unicode support causes undesirable side effects for your particular languages or combination of languages, you can turn it off using the /utf8off startup switch with the WebAccess Agent. Then comment out the Charset.default setting in the webacc.cfg and webpub.cfg files. This procedure will not be necessary after Unicode support is fully supported for DBCS languages.

3.6.2 Using the Latest Novell Client

If you receive an error during installation indicating that the nvweb.dll file cannot be found, update the workstation to the latest Novell Client^TM. The Novell Client is available for download from the Novell Software Downloads site.

3.6.3 Display Problems with Netscape 4.x

If you experience display problems using Netscape* 4.x with WebAccess, update to a later version of Netscape.

3.6.4 Installing to Non-Supported Web Servers

The GroupWise WebAccess Installation program installs the WebAccess and WebPublisher Applications to the Web servers listed below. These are the Web servers for which Novell Technical Services^SM will provide support.

• NetWare Enterprise Web Server for NetWare 5 (and later)
• Apache Web Server 1.0.3 (or later) for NetWare 6 (and later)
• Netscape Enterprise Server* 3.6 (or later) for Windows NT
• Microsoft Internet Information Server 4.0 (or later) for Windows NT, or Microsoft Internet Information Server 5 (or later) for Windows 2000
• Apache Web Server 1.3.3 (or later) for UNIX* Solaris*

If necessary, you can run the WebAccess and WebPublisher Applications on a non-supported Web server as long as the Web server supports a Java* servlet engine that is JSDK 2.0 and JDK* 1.1.6 compatible. However, the Installation program will not install the applications to other Web servers, which means you must manually install and configure them. When you run the Installation program, deselect the options to install the WebAccess Application and WebPublisher Application, install the WebAccess Agent, then complete the following steps to install the applications:

1. Unzip webaccess.zip to the root of the network server volume where the Web server resides.

   The webaccess.zip file and the ZIP files referred to in the next three steps are in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

2. Unzip webaccessdocs.zip to the Web server's document root directory.

3. Unzip webaccessservlets.zip to the servlet root directory.

4. Unzip webaccessjars.zip to a library or jar file directory on the network server (for example, you might want to create a \novell\lib directory), then add the jar files (ldapfilt.jar, ldapjdk.jar, njgwap.jar, njweb.jar, spellservlet.jar, xalan.jar, and xerces.jar) to the class path.

5. Modify your Java engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.

   The WebAccess servlet.properties file is located in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

6. Modify the Templates.path setting in the webacc.cfg and webpub.cfg files, located in the \novell\webaccess and \novell\webpublisher directories, to replace java/servlets with the path to the servlet root directory.

7. If you created the \novell directory structure in the location specified in step 4 (the root of the volume where the Web server resides), the paths for the following settings in the webacc.cfg and webpub.cfg should already be correct. If not, you need to modify the paths to make them correct from the perspective of the Web server.

   File.Upload.path

   Log.path

   Security.Timeout.path

   Provider.GWAP.Config.file

   Provider.LDAP.Config.file (webacc.cfg only)

8. Copy the index.html file to the Web server's document root directory.

   You can replace your Web server's current default home page with this file, or you can rename the file and link to it from your current default home page.

9. Copy the commgr.cfg file, located in the WebAccess gateway home directory (domain\wpgate\webac65a), to the \novell\webaccess directory and the \novell\webpublisher directory.

3.6.5 Configuring WebAccess to Use a Java Servlet Engine Other Than the Novell Servlet Gateway or Tomcat Servlet Engine

If you use a Java servlet engine other than the Novell Servlet Gateway or the Tomcat servlet engine, the servlet engine needs to be JSDK 2.0 and JDK 1.1.6 compatible.

After you've installed WebAccess, complete the following tasks to configure WebAccess to work with the Java servlet engine:

1. Modify the Java servlet engine's servlet properties file to include the settings shown in the sample WebAccess servlets.properties file.

   The sample servlets.properties file is located in the \internet\webacces\other directory of GroupWise 6.5 Support Pack 1.

2. In the webacc.cfg and webpub.cfg files, modify the Templates.path setting to replace java/servlets with the path to the servlet root directory.

   The files are located in the novell\webaccess and novell\webpublisher directories on the root of the server.

3. Add the WebAccess jar files (ldapfilt.jar, ldapjdk.jar, njgwap.jar, njweb.jar, spellservlet.jar, xalan.jar, and xerces.jar) to the class path.

   On a NetWare server, the jar files are located in the java\lib directory. On a Windows server, the files are located in the novell\java\lib directory.

3.6.6 Login Page Reappears after Successful Login

If the WebAccess login page appears in one or more of the frames (for example, the Folder list or the Item list) after a WebAccess user has successfully logged in, the user is probably accessing WebAccess through one or more proxy servers.

To prevent this problem:

1. In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then click Properties.

2. On the Security page (located on the Application tab), deselect the Use Client IP in Securing Sessions option.

   For information about this option, click Help on the Environment page.

3. Click OK to save the change.

3.6.7 Security Issue with WebAccess and Internet Explorer 5.0

When using Internet Explorer 5.0 to view messages through WebAccess, URLs to messages become part of the History cache and can be read by other users who have access to the same workstation. For solutions to this problem, see TID 10056452 in the Novell Knowledgebase.

3.6.8 Recommendation for Tomcat Memory Allocation (Heap Size)

If you are using the Tomcat servlet engine with GroupWise WebAccess, the maximum memory allocation (heap size) for Tomcat should be at least 128 MB. The maximum memory allocation is set by using the -Xmx parameter when starting Tomcat (for example, -Xmx128m).

4.0 International Issues

4.1 Double-Byte Characters in Directory Names and Filenames

Do not use double-byte characters in directory names and filenames.

4.2 Double-Byte Characters in Passwords

Do not use double-byte character in users' passwords.

The Change GroupWise Password dialog box in ConsoleOne currently allows entry of double-byte characters. However, the GroupWise client login does not allow entry of double-byte characters in passwords, so a user who was assigned a password with double-byte characters in ConsoleOne would not be able to type the double-byte characters when attempting to log in to GroupWise.

4.3 Euro Character in Subject Field

If a WebAccess client user receives a message, task, or appointment with a Euro character in the Subject field, it might display as an upside-down question mark when viewed in the Java version of the Calendar. The issue resides with the user's browser.

Netscape users need to upgrade to Netscape Communicator* 6.

Internet Explorer users need to be using at least version 3309 of the JVM*. The latest JVM can be downloaded from the Microsoft Web site and installed on the user's workstation. This JVM enables Internet Explorer 4.x and later to correctly display the Euro character.

4.4 Print Calendar Language

The GroupWise client Print Calendar feature always prints calendars in the language specified in Regional Options or Regional Settings in the Control Panel, even if the client is installed in a different language. For example, if French (Switzerland) or French (Swiss) is specified in the Control Panel and the client is installed in German, calendars will print in French.

4.5 RichWin and GroupWise 6.5

If you use RichWin in combination with GroupWise 6.5, be sure to run RichWin first, then run GroupWise.

5.0 Defect Fixes

5.1 Address Book Fixes

• Performance when opening the Address Book from a new mail message has been improved.
• Name completion continues to work correctly after an external user has been added to your Frequent Contacts address book.
• The Address Selector works correctly with very large Address Books (for example, more than 100,000 users).
• With your system set up as described in TID 10008444, the Address Selector provides the e-mail address in the correct format.
• You can search the GroupWise Address Book on the GroupWise E-Mail Address field and the list scrolls correctly as you type.
• You cannot filter the GroupWise Address Book on the GroupWise E-Mail Address field. You can, however, filter personal address books on the GroupWise E-Mail Address field.
• When you have two users with the same name but with different user IDs and in different post offices, the Quick Info pop-up on the sender's name in a received message displays the correct user.
• You can edit and save a group without receiving an error.
• Members of an organization can be viewed in a shared address book.
• After closing all address books, you can open them again.
• Admin-defined fields that receive special processing as MAPI attributes are returned as both admin defined fields and MAPI attributes:

  eDirectory Attribute	Explanation	MAPI Attribute
  L	Location	PR_OFFICE_LOCATION
  PHYSICAL DELIVERY OFFICE NAME	City	PR_LOCALITY
  POSTAL CODE	Zip Code	PR_POSTAL_CODE
  S	State	PR_STATE_OR_PROVINCE
  SA	Street Address	PR_STREET_ADDRESS

  As a result, both the Novell eDirectory^TM attributes and the MAPI attributes are available as admin-defined fields and as columns in the GroupWise Address Book, personal address books, the Address Selector dialog box, and the Contacts folder.

• Accented characters display correctly in the GroupWise LDAP address book.

5.2 Administration Fixes

• You can select multiple users and select the same default client options for all of them in a single operation.
• You can add User objects where the first three characters of the object name are "all."
• When you delete a user, the deleted user is automatically removed from all other users' proxy lists.
• The Restore Deleted Account utility now restores the deleted user's membership in distribution lists.
• You can move disabled user accounts without getting a D109 error.
• In the User Move Status utility, the Clear Status button is available with any selection.
• The user interface prevents you from specifying too many users to perform Mailbox/Library Maintenance on.
• Distribution lists can be synchronized without losing information.
• A domain path can be up to 256 characters in length.
• If you select Restrict System Operations to Primary Domain under System Preferences, an administrator connected to a secondary domain cannot make changes to any other domain besides the local secondary domain.
• When you are merging an external domain into your system, ConsoleOne provides the database path in the correct format.
• Missing attributes in older databases do not prevent post office creation.
• You can rebuild a 5.x domain database from a 6.5 domain.
• You can rebuild a 4.x post office database from a 6.5 domain.
• Changing link configuration information in a multi-tree system does not require logging to remote trees.
• If you manually delete a software distribution directory outside of ConsoleOne, you must go to each post office that was using the deleted software distribution directory and select a different directory.
• The Graft Wizard prevents you from matching a GroupWise user with an eDirectory Alias object.
• Applicable fields in ConsoleOne display a warning that includes actions to take if the GroupWise DirXML^® driver is installed.
• The GroupWise snap-ins register correctly with ConsoleOne so that they are listed when you click Help > About Snapins.
• The Country field in the GWSCRGEN utility is restricted to two characters to help prevent specifying invalid codes (such as USA).
• GWTSA processes past the first resource defined by a /home switch that isn't found on the server.
• GWTSA correctly handles situations where the same directory names are used on different volumes to back up.
• GWTSA correctly backs up new files on its second pass through the offiles and gwdms directories.
• GWTMSTMP displays an appropriate error message if its language resource file fails to load.

5.3 Admin API Fixes

• Trusted applications install correctly to a system that has been updated from 6.0 to 6.5.

5.4 Agent Fixes

• The POA Web console includes WebAccess users along with Windows client users on the C/S Users page.
• The agents auto-load calnlm32.nlm when loading in protected memory to prevent public symbol errors.
• The POA consistently rolls over to secondary LDAP servers.
• The POA consistently handles messages that exceed the established size limits, with an undeliverable message CC'd to the domain administrator and no attachment.
• The POA consistently enforces intruder lockout for Remote client users, whether or not Live Remote is enabled.
• The POA does not lock users out if they log in successfully multiple times in a very short time interval (for example, one minute).
• The move user process succeeds even if the POA fails over to a different node in a cluster while the move is in progress.
• The IP address provided by the /ip startup switch is used with all port numbers, not just the client/server port (for example, MTP port, HTTP port, IMAP port, and so on).
• The POA /home startup switch is no longer case sensitive with regard to \\server_name\volume_name in a cluster.
• Fixed a POA abend.
• The MTA respects the send size limit set for each post office.
• The MTA respects the delay message size setting on a domain link.
• Live Remote connections are established successfully for mobile users who move back and forth from inside and outside the firewall.
• The MTA retries locked files in its queues so that the activities of third-party programs such as InocuLAN* do not prevent the MTA from processing all the files in its queues.
• Fixed some MTA abends.

5.5 Client Fixes

• Performance when reading plain text messages has been improved.
• You can resend an item to a user who has moved to a different post office since the item was originally sent.
• After moving a message into a folder, you receive proper notification when the next message arrives.
• When you right-click a URL in a received message, the drop-down menu includes Copy.
• Quote marks in URLs are handled correctly so that the link works.
• If an e-mail address in a received message is surrounded by single quote marks ('), the quote marks are stripped off when you click the e-mail address link to send a message.
• URLs entered in HTML view display correctly when read in Plain Text view.
• You can copy and paste a .wmf file into a message in HTML view.
• If your default read view is set to Plain Text, you can select Force so that HTML-formatted messages are never automatically displayed, even for HTML-only messages.
• If an HTML-formatted message contains a link to an executable, the executable is not allowed to run in the background. However, you can click the link and run the executable.
• When you reply to or forward an HTML-formatted message that uses a background color, the background color is retained in the reply or forwarded message.
• Occasional HTML-formatted messages that were blank when forwarded now display correctly when forwarded.
• Appointments cannot be retracted if a user has turned off the creation of sent items. The user is now warned that the appointment cannot be retracted because no sent item exists.
• When you drag and drop an appointment to reschedule it, the old appointment is removed from recipient's calendars.
• On the Accept drop-down menu of an appointment, the Accept item has been clarified to read Accept with Options.
• After deleting a single instance of an auto-date appointment, you receive proper notification of subsequent instances.
• Appointment details are read 12 hours in advance. The client now prevents you from setting an alarm more than 11 hours 59 minutes in advance.
• You can change alarm properties on recurring posted appointments.
• Notify behaves consistently under low-memory conditions.
• After a user has been moved to a different post office, appointment properties display correctly from the Calendar.
• The multi-user calendar displays posted reminder notes created in the Month view.
• When you reply to a posted item, the subject line is retained.
• When a shared folder is displayed as a calendar, new appointments display properly.
• When you create a task before 12:00 p.m. (noon), the time stamp in the header displays the correct time.
• When multiple items are delegated, the prompt to keep or discard the items comes up as it should.
• The Contacts folder filter no longer affects the items displayed in the Calendar.
• The Contacts folder retains the selected sort settings.
• You can turn a Checklist folder into a shared folder and the checklist items display properly.
• You can create a checklist item in a shared folder.
• You can filter the Trash folder when it contains a very large number of items and there are no incorrect matches.
• In a folder with over 600 items sorted in ascending order, the Select First Unread Item When Folder Is Opened option correctly identifies the first unread item.
• In a shared folder viewed as a Discussion Thread, if you select a thread status of Ignore, that status is retained after you refresh the folder.
• Documents in shared folders have correct version information when edited by various users who share the folder.
• Deletion of multiple items in a subfolder can be canceled.
• If you sort an item list on the From column, the sort ignores initial double quote (") or angle bracket (<) characters.
• When you create a rule to attach files, the files to attach are not duplicated when you later edit the rule.
• A rule that is supposed to delete a link to a message does not delete the original message.
• When you send an item to a resource and the resource has a rule to delegate the message to another user, the message arrives to the recipient with the message text unchanged.
• With Read Only access, proxy users cannot change the search criteria on a Query folder in another user's mailbox.
• As a proxy, you cannot open private appointments in the Month view.
• If you attempt to proxy to another user and do not have rights, that user is not added to the drop-down proxy list.
• When you add a new user as a proxy and then add that user to the multi-user calendar, the user appears when the multi-user calendar is printed.
• If the administrator has limited attachment size and a user sends an attachment that exceeds the limit, the resulting error dialog displays the size limit correctly.
• If you receive a message from an external source that has a comprtf.001 file attached, and if you forward this message with new text in the message body, the new text is visible for the recipient.
• You can play .wav file attachments without getting an extraneous error message.
• You can attach .jpg files that include information about camera settings and other recent .jpg format changes.
• Attached executable (.exe) files are saved successfully if you select No the first time and Yes the second time when you receive the virus warning prompt.
• You can attach a message to a new message that you save in the Work in Progress folder, then open, edit, and send the saved message and its attachment successfully.
• You can change a message that was forwarded as an attachment into an appointment.
• When you are resending a message, if you edit the message, attach a file, view the attached file, then view the edited message, your editing changes appear in the viewer version of your message.
• If the administrator has disabled LDAP password changing in GroupWise and a user's password is about to expire, the resulting prompt no longer implies that the user can change the password in GroupWise.
• When you use ActivCard* as your default S/MIME provider, you can successfully trust any certificate from a signed message.
• You can select ActivCard with driver version 2.2 as your cryptographic security provider.
• If S/MIME has been disabled for a user, post office, or domain and a user receives a digitally signed message with an attachment, the attachment can be viewed.
• When trying to encrypt a message to a user who does not have a certificate or who has multiple certification, the search for a valid certificate continues past invalid (expired) certificates.
• When you reply to a digitally signed message, the reply is not digitally signed by default unless you have selected Sign Digitally under Tools > Options > Security > Send Options.
• Hit the Road can now download certain messages that previously stopped the download process even though those messages could be successfully opened, replied to, forwarded, archived, and unarchived.
• Hit the Road can download personal address books that contain more than 4961 entries.
• You can turn the status window on and off when using Hit the Road.
• Because IMAP clients cannot detect when your password has been changed when LDAP authentication is in use, you receive a warning when you start using grace logins.
• In an IMAP client, if you search on the IMAP keyword SEEN, no unread items are displayed.
• When downloaded to an iPaq*, messages no longer contain visible MIME boundaries.
• After searching in your Backup mailbox, you can open the items in the list of search results without receiving an error.
• The mailbox display refreshes correctly after turning on and off a filter that includes only items with a status other than Opened.
• When you create a mail view that includes text, the text in the mail view does not overwrite message text when you forward the message.
• Custom views created with the View Designer display correctly.
• When you select the font size for the MS Sans Serif font for message text on the Appearance tab of the Windows Display Properties dialog box, it is retained in the message box of the Mail To view.
• The keystroke sequence Shift+Del to purge a message followed by Ctrl+Up to open the previous message works when executed very rapidly before the view has refreshed from the deletion.
• You can press Enter in the message window when another dialog box (for example, Tools > Options > Environment) is open.
• Pressing the arrow keys or Tab on the Properties tab of an item no longer causes the client to hang.
• Changing toolbars no longer causes the message window to resize, so that the bottom message does not appear to drop out of the window.
• When you are editing the toolbar of an outgoing message, the Calendar window, or the Find Results window, the Switch to Task and Switch to Reminder Note buttons in the Edit category display correctly when you mouse over them.
• The Modify Find button on the Find Results folder toolbar opens the Find Results folder properties with the Find tab selected.
• Some problems with customizing toolbars have been fixed.
• Mnemonics on the Address Book toolbar that are not applicable have been removed.
• When you mouse over the From or Newsgroup field in a newsgroup message, the mouseover text displays correctly.
• When you mouse over an appointment in your calendar, the Quick Info box doesn't blink when the To list is long and the GroupWise window is positioned at the top of the screen.
• The Forwarded and Replied To icons display correctly in the Mailbox folder when only Received Items is selected.
• When the POA fails over in a cluster and the client loses its connection while sending messages, the client displays a message that the connection to the post office has been lost. When you click OK on the error, the client reconnects.
• Extraneous 0-byte files are no longer created in the client directory.
• When creating an Application object for ZENworks^® for Desktops, the default path to the source files displays the directories in the proper order.
• The Installation program can install the GroupWise client on Windows NT 4 with Internet Explorer 4 even if no MAPI files are present on the workstation.
• If the Installation program detects an incompatible version of mapi32.dll, it prompts the user to reinstall MAPI.
• When installing the client using SETUPIP, if a network timeout occurs, the user has a Retry option so that the installation can be continued.
• When installing the client using ZENworks for Desktops, if the Installation program detects an incompatible version of MAPI, it prompts the user to install Windows Messaging System so that compatible version of MAP will be available.
• If you start Word from the Program menu and edit multiple documents in a GroupWise library, the documents are all saved successfully.
• The GroupWise client can open and forward Netscape Communicator TNEF mails.
• On Windows 98/ME, you can use File > New > Mail without getting an error.
• On Windows 98 SE, signatures are handled correctly.
• An extended character followed by a hyphen (-) displays and prints correctly.
• The Busy Search dialog box is formatted correctly in all languages.
• In localized versions, a search on a library that returns a large number of hits does not contain extraneous empty lines.
• If you have multiple languages installed, you can change the name of Calendar folders and the changes are retained when you change languages.
• Cyrillic characters are displayed correctly in the subject line.
• Hebrew messages downloaded for POP accounts display correctly.
• Rules work in the Hebrew client because field names now match correctly.
• Extended characters in the subject line of a Hebrew message display correctly.
• Appointment times print in the correct location on a Hebrew calendar.
• Print Preview works for a Hebrew calendar.
• In the Swedish client, the title of the Access Rights box on the Proxy List tab of client Security Options is correctly translated.
• In the German client, the translation for Download Headers Only under Properties > Advanced on an IMAP account has been corrected and the word Page is now translated when printing messages.

5.6 Client API Fixes

• HTML messages generated by the client API display properly in GroupWise.
• TPH DLLs can register either under HKEY_CURRENT_USER (for the user that is currently logged in) or under HKEY_LOCAL_MACHINE (for all users who might log in).
• All windows have unique Windows class names.

5.7 Engine Fixes

• Caching and Remote mailboxes are protected from item expiration after users are moved.
• Delayed delivery messages are handled properly after a message database is restored from backup.
• The process for downloading the Address Book to the Remote client takes into account active application threads to prevent damage to the new copy of the Address Book database.
• The version tag on the ngwguard.dc file is properly updated.
• Multiple remote operations of the same type are permitted to facilitate the DirXML driver.

5.8 GWCheck Fixes

• In GroupWise Check, Mailbox/Library Maintenance in ConsoleOne, and the client Cleanup options, the maximum number of days that an item can remain in the system is consistent and has been increased to 9999.
• On the Misc tab, you can use the delsubscriberecords support option to resolve problems with users' Notify alarms.
• On the Misc tab, you can use the proxyfix support option to clear out duplicate records in a user's proxy list and to remove a deleted user from all other users' proxy lists.
• GroupWise Check scans for orphaned library directory records and deletes them if the library has been deleted.
• GroupWise Check repairs or removes cross-linked messages that sometimes occur when an individual message database is restored into a post office.
• Resources are no longer removed from notification lists by a content check.
• The GroupWise Check log provides the correct number of items that matches the expire criteria.
• If you try to run GroupWise Check at the same time when Mailbox/Library Maintenance is running from ConsoleOne, a message informs you that a duplicate task is already running.
• You can perform an expire/reduce operation on an archive on Windows NT.

5.9 Internet Agent Fixes

• Members of distribution lists receive one copy of Internet messages, not multiple copies.
• Attachments of content type Text are treated the same as attachments of content type Text/plain.
• The /forceoutboundauth startup switch works correctly with the gwauth.cfg file to route messages through an external SMTP relay host.
• Internet user names that contain a middle initial display correctly in the To field.
• In multipart/mixed messages, two spaces in sequence do not disrupt the boundary definition established by quote marks, allowing attachments to be successfully displayed.
• The Internet Agent correctly builds multipart-related messages from attachments so that images appear where they should.
• The Internet Agent does not change the hostname in Internet e-mail addresses incorrectly when the address includes additional routing information in the personal address book.
• When you move an Internet message into the Checklist folder and then mark it completed, the Internet Agent no longer tries to send a status message back to the sender.
• If the Internet Agent is running on a different server where the domain database is located, and if the domain server is restarted, the Internet Agent is able to reconnect successfully.
• The Installation program can install the Internet Agent as a Windows service without error if the SNMP service is already running.
• The Installation program copies the msvcp60.dll file to the Windows system directory if there is not already a more recent one there.
• Fixed some Internet Agent abends.
• The default date format is dd month yyyy, where month is the month name rather than a number so that dates are unambiguous in all countries.

5.10 Monitor Fixes

• Monitor alerts can be relayed off of a SendMail system.

5.11 WebAccess Fixes

• Startup switches can be specified for the WebAccess Agent when it is running as a service by putting them in the new startup file named WebAccess_object.wa.
• Novell branding and logo are retained even if you customize the WebAccess interface.
• WebAccess users can be tracked along with Windows client users from the POA Web console.
• The WebAccess Agent Web console HTTP port uses the same IP address as the WebAccess agent so that it can fail over successfully in a cluster.
• The WebAccess Agent Web console displays the name of the domain where the agent is defined.
• Messages sent to a distribution list by selecting the distribution list from the Address Book are routed correctly.
• You can send to a local user who is in multiple personal address books without that user being considered ambiguous, providing you have copied the user from one personal address book to another, rather than copying multiple times from the system Address Book.
• Proxy works successfully when a GroupWise user in an LDAP-enabled post office proxies to a user in a non-LDAP-enabled post office.
• A problem with the Unopened Items folder was fixed.
• WebAccess generates WML strictly according to WAP specifications.
• If your connection to the Web server times out while you are composing a message, the message is not lost. It displays on the login page so you can copy it into a new message when you reconnect.
• After updating from 6.0 to 6.5, no users have problems with their user databases that prevent them from sending messages.
• Images in messages are displayed correctly when running WebAccess with Microsoft Internet Information Server.
• The WebAccess Agent installs correctly as a Windows service.
• WebAccess installs correctly from a Windows 98 workstation.
• Fixed some WebAccess Agent abends.

6.0 Documentation

6.1 GroupWise 6.5 Readme Files

For Readme information about specific GroupWise 6.5 components, see the following additional Readme files that shipped with the original release of GroupWise 6.5:

Administration: \admin\readmeus.txt
Agents: \agents\readmeus.txt
Client: \client\win32\readmeus.txt
WebAccess: \internet\webaccess\readmeus.txt
Internet Agent:\internet\gwia\readmeus.txt
Monitor: \admin\monitor\readmeus.txt

6.2 GroupWise 6.5 Installation Guide

For detailed installation and update instructions, see the GroupWise 6.5 Installation Guide (GroupWiseInstallationGuide.pdf) in the \docs\us directory of the Support Pack. It has been updated to correspond with GroupWise 6.5 Support Pack 1.

6.3 GroupWise 6.5 Administration Guide

For additional GroupWise 6.5 documentation, see the GroupWise 6.5 Administration guide at the Novell Documentation Web site. It has been updated to correspond with GroupWise 6.5 Support Pack 1.

6.4 GroupWise 6.5 Help

To support accessibility requirements within GroupWise Help, the Help for all GroupWise components uses Microsoft HTML Help. In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4.x or later installed.

7.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (^®, ^TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.

8.0 Legal Notices

Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.

Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

You may not export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.

U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 5,963,938; 6,081,804; 6,138,170; 6,167,393; D393,457; 6,216,123 and Patents Pending.

Copyright ^© 2003 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

GroupWise, NetWare, and Novell are registered trademarks of Novell, Inc. in the United States and other countries.

NLM is a trademark of Novell, Inc.

All third-party trademarks are the property of their respective owners.