GroupWise 6 Support Pack 1
November 1, 2001

IMPORTANT: If you are downloading the GroupWise 6 Support Pack 1 for use in France, make sure you download the 56-bit encrypted version (GW6SP1FR.EXE). French regulations require the use of the 56-bit encrypted version, not the 128-bit encrypted version (GW6SP1.EXE).

Table of Contents

1. Installation of GroupWise 6 Support Pack 1

If you are installing from a GroupWise 6 Support Pack 1 CD, follow the instructions provided in the GroupWise 6 Installation guide. The Installation guide, named GroupWiseInstallationGuide.PDF, is located in the DOCS/<lang> directory on the CD, where <Lang> represents a language.

If you are installing from GroupWise 6 Support Pack 1 files downloaded from the Novell Web site, follow the installation instructions provided in the support pack's Technical Information Document.

2. Additional Documentation

The GroupWise 6 product documentation includes detailed instructions for installing, administering, and troubleshooting all components of a GroupWise system. The GroupWise documentation is located at the Novell Documentation site.

3. General Issues

3.1 Support Pack 1 Includes Padlock Patch
This SP1 release includes the Padlock patch, a security update made available for GroupWise 6. If you have the Padlock patch, do not apply it to SP1.

For more information about the Padlock patch, see the Novell GroupWise page at:

http://www.novell.com/products/groupwise

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

File names can consist of up to 8 characters, with extensions of up to 3 characters. Do not use long file names. This requirement applies to any non-GroupWise-specific files (such as SSL certificates and key files) that are used by GroupWise components.

3.3 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.4 Current System Address Book for Caching Mode Users
When users prime their Caching mailboxes, they receive a copy of the system Address Book. To make sure that Caching mode users always have a current copy to download, make sure the POA is configured to generate the system Address Book regularly, as described in the Agents Readme.

If you want to generate the system Address Book for download more often than once a day, you can delete the existing WPROF50.DB file from the \WPCSOUT\OFS subdirectory of each post office. A new downloadable system Address Book will be generated automatically for users on each post office.

3.5 GroupWise Target Service Agent (GWTSA) Issues
If you are using a backup process other than the GroupWise Target Service Agent (GWTSA) and you enable GroupWise Smart Purge, you must run the GroupWise Time Stamp Utility (GWTMSTMP) after each successful backup for Smart Purge to function properly.

Supported Third-Party Backup Software
At the time of release, the GWTSA supports Veritas Backup Exec for NetWare.

GWTSA Temporary Directory
By default, the GWTSA places temporary files in the \SYSTEM\TEMP directory during the backup process. Use the /tempdir switch to specify an alternate location. For example:

load gwtsa /tempdir-\temp\gwtsa

Limitation of SBackup Console
If you are using the SBackup Console (SBCON.NLM) in conjunction with the GWTSA, you may encounter the following limitation: If you navigate down through the directory structure and then back up to the root directory, you are unable to navigate down a different directory. You can exit the SBackup Console and restart it to choose a different directory below the root directory.

3.6 Restoring Mailbox Items
If you create a backup copy of a post office, you must define the backup copy as a GroupWise restore area before the post office’s users will be able to use the GroupWise client’s Restore feature to restore mailbox items from the backup. If you don’t define the backup as a restore area, GroupWise users can still access the restore area (if you let them know the location), but they will receive an error when they try to restore items.

To define a post office backup as a restore area:

1. In ConsoleOne, click the Tools menu > click GroupWise System Operations > click Restore Area Management to display the Restore Area Directory Management dialog box.
   
   
2. Click Create to display the Edit Backup/Restore Area dialog box.
   
   
3. On the Identification tab, fill in the following fields:
   
   Name: Enter a name for he restore area.
   
   UNC Path: Select the path to the backup copy of the post office.
   
   
4. Click the Membership tab.
   
   
5. To assign a post office to use the restore area, click Add > select the post office.

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

3.8 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.9 NetWare 5.1 SP1 Compatibility
If you are using the AutoUpdate feature for installing the GroupWise 6 client, you may encounter an error if you are installing the client from a NetWare 5.1 server where Support Pack 1 has been installed. The SETUPIP.EXE program used during the AutoUpdate process may not run correctly.

To resolve the problem, you must modify the MAGNUS.CONF file located in the SYS:\NOVONYX\SUITESPOT\HTTP-<web_server_name>\CONFIG directory by adding the following line:

MaximumFilesReturnedInIndex 500

Then run the client installation again.

3.10 TurboFat Compatibility
If you see E811 errors on the POA or the GroupWise client, a possible cause is that TurboFat is causing corruption to 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 programs disable TurboFat at startup.

3.11 Help Files
To better support accessibility requirements within GroupWise Help, the Help for the following GroupWise components has been changed from Microsoft Windows Help to Microsoft HTML Help:

• GroupWise client
• GroupWise Agents (MTA and POA) for Windows NT/2000
• GroupWise Internet Agent for Windows NT/2000
• GroupWise Monitor for Windows NT/2000
• GroupWise Check utility
• GroupWise Certificate Signing Request utility

In order for Microsoft HTML Help to display on a Windows workstation, the workstation must have Internet Explorer 4.x or higher installed.

3.12 International Issues

3.12.1 Double-Byte Characters in Directory Names and File Names
Do not use double-byte characters in directory names and file names.

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

3.12.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 may display as an upside-down question mark when viewed in the Java 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 above to correctly display the Euro character.

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

3.12.5 Windows Messaging System
When installing the GroupWise client to a non-English or non-Japanese Windows NT/2000 operating system, users will receive a prompt asking them to replace a Windows Messaging System DLL with the English version of the DLL. Users must click YES and replace this Windows Messaging System DLL. Otherwise, GroupWise will not function properly.

If you install the GroupWise client to a Japanese Windows XP operating system, Windows XP must be using the English version of Windows Messaging System. To install the English version of Windows Messaging System, run WMS.EXE from the CLIENT\WIN32\WMS\NT\US directory on the GroupWise CD

4. Agent Issues

4.1 Windows 2000 Service Pack 2 Required
If the GroupWise agents are installed on Windows 2000 and the GroupWise domain directory and post office directories accessed by the agents are on a NetWare server (or any non-Windows server), you need to apply the Windows 2000 Service Pack 2 to the operating system.

You can download Windows 2000 Service Pack 2 from:

http://windowsupdate.microsoft.com

Note: If, as required with the initial release of GroupWise 6, you already installed Microsoft HotFix Q266066, you do not need to apply Windows 2000 Service Pack 2.

4.2 Using SSL
GroupWise 6 SP1 supports the use of SSL connections between agents (MTA-to-MTA, MTA-to-POA). If you use SSL between agents, you cannot run the agents in protected mode or on a multiprocessor machine.

4.3 Username and Password Required when Running Agents in Protected Mode in a Server Cluster
GroupWise 6 SP1 supports Novell Cluster Services. If you run the GroupWise Agents in protected mode in a NetWare server clustering system, you need to use the /user-<username> and /password-<password> startup switches to supply a valid network user ID and password.

This requirement applies to versions of NetWare 5.1 prior to NetWare 5.1 Support Pack 4 and versions of NetWare 6 prior to NetWare 6 Support Pack 1. If you are using a more recent version of NetWare 5.1 or NetWare 6, you do not need to use the /user and /password startup switch unless the agent requires access to a GroupWise document storage area located on a remote server.

4.4 Updating to GroupWise 6 Agents
If you are updating an existing GroupWise 5.x system, and you are running the MTA and a POA on the same machine, you should not choose to launch the agents at the end of the installation process. Start the MTA first, so that it can update the domain to a GroupWise 6 level. When this process is finished, then start the POA to update the post office.

4.5 Generating the System Address Book for Caching Mode Users
When users prime their Caching mailboxes, they receive a copy of the system Address Book. To make sure that Caching mode users always have a current copy to download, make sure the POA is configured to generate the system Address Book regularly. On the POA Agent Settings page in ConsoleOne, make sure that Generate Address Book for Remote is selected. You can choose the time when you want the generation to take place.

4.6 Unread Message Count Feature Requires SP1 Version of the Post Office Agent (POA)
The GroupWise 6 SP1 client includes a new feature, Unread Message Count. Next to each folder, GroupWise displays the number of unread messages included in the folder.

For the Unread Message Count feature to work when the GroupWise client is running in Online mode, the GroupWise Post Office Agent must be the GroupWise 6 SP1 version.

5. Internet Agent Issues

5.1 Windows 2000 Service Pack 2 Required
If the Internet Agent is installed on Windows 2000 as a Windows service and the GroupWise domain directory accessed by the Internet Agent is on a NetWare server (or any non-Windows server), you need to apply the Windows 2000 Service Pack 2 to the operating system.

You can download Windows 2000 Service Pack 2 from:

http://windowsupdate.microsoft.com

Note: If, as required with the initial release of GroupWise 6, you already installed Microsoft HotFix Q266066, you do not need to apply Windows 2000 Service Pack 2.

5.2 IMAP Access Requires SP1 Version of the Post Office Agent (POA)
The GroupWise 6 SP1 version of the Post Office Agent (POA) must be running against any post offices that the Internet Agent will access via IMAP.

5.3 Using the STATUS.XML File to Change Status Messages
The Internet Agent returns status messages for all outbound messages. For example, if a GroupWise user sends a message that the Internet Agent cannot deliver, the Internet Agent returns an undeliverable message to the GroupWise user.

By default, the Internet Agent will use internal status messages. However, you can override the internal status messages with status messages you define. To do so:

1. Open the STATUS.XM_ file, located in the <domain>\WPGATE\<gwia> directory.
   
   
2. Make the modifications you want.
   
   
3. Save the file, renaming it from STATUS.XM_ to STATUS.XML.
   
   
4. Restart the Internet Agent.

The Internet Agent will now use the status messages defined in the STATUS.XML file rather than its internal status messages.

6. WebAccess Issues

6.1 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. The Novell Client is available for download from the Novell Software Download site:

http://download.novell.com

6.2 Installing NetWare 5 Support Pack 3a or NetWare 5.1
If you install NetWare 5 Support Pack 3a or NetWare 5.1 after you install the WebAccess and WebPublisher Applications to a NetWare 5 server, you will need to reinstall the WebAccess and WebPublisher Applications.  The Support Pack and NetWare 5.1 replace the JAVA.CFG file and other files that are modified by the GroupWise WebAccess Installation program.

If you install the WebSphere Application Server that is part of NetWare 5.1, the WebAccess and WebPublisher Applications will no longer function. Reinstalling them will not resolve the problem. You will need to restore them from backup.

6.3 Windows 2000 Service Pack 2 Required
If the WebAccess Agent is installed on Windows 2000 as a Windows service and the GroupWise domain directory accessed by the WebAccess Agent is on a NetWare server (or any non-Windows server), you need to apply the Windows 2000 Service Pack 2 to the operating system.

You can download Windows 2000 Service Pack 2 from:

http://windowsupdate.microsoft.com

Note: If, as required with the initial release of GroupWise 6, you already installed Microsoft HotFix Q266066, you do not need to apply Windows 2000 Service Pack 2.

6.4 Running WebAccess and Monitor on the Same Web Server
The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. This library changed significantly from GroupWise 6 to GroupWise 6 SP1. If you will run these applications on the same Web server, you must update all three before any of them will work properly.

6.5 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 will provide support.

• NetWare Enterprise Web Server for NetWare 5 (and higher)
• Netscape Enterprise Server 3.6 (or higher) for Windows NT
• Microsoft Internet Information Server 4.0 (or higher) for Windows NT, or Microsoft Internet Information Server 5 (or higher) for Windows 2000
• Apache Web Server 1.3.3 (or higher) 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 > 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.  WEBACCESS.ZIP and the ZIP files referred to in the next three steps are in the INTERNET\WEBACCES\OTHER directory on the GroupWise 6 SP1 CD.
   
   
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 may 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 on the GroupWise 6 SP1 CD.
   
   
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\<WEBAC60A>) to the NOVELL\WEBACCESS directory and the NOVELL\WEBPUBLISHER directory.

6.6 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 SERVLETS.PROPERTIES file is located in the INTERNET\WEBACCES\OTHER directory on the GroupWise 6 Support Pack 1 CD.
   
   
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 NT server, the files are located in the NOVELL\JAVA\LIB directory.
   

6.7 Running Busy Search on a UNIX Post Office
GroupWise WebAccess will not return valid Busy Search results for users whose mailboxes are on UNIX post offices.

6.8 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) > click Properties.
   
   
2. On the Environment page (located on the Application tab), deselect the Use Client IP in Securing Sessions option. For information about this option, click the Help button on the Environment page.
   
   
3. Click OK to save the change.

7. Monitor Issues

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

7.2 Running Monitor and WebAccess on the Same Web Server
The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. This library changed significantly from GroupWise 6 to GroupWise 6 SP1. If you will run these applications on the same Web server, you must update all three before any of them will work properly.

8. Client Issues

8.1 Librarian and Mass Document Operations
Librarian and mass document operations are available only in the Online mode of the GroupWise 6 SP1 client.

8.2 Caching Mode Address Book and Rules
All address books and rules will be downloaded on the initial priming of the Caching mailbox. You can configure how often you want to re-download the system Address Book, your personal address books, and rules by clicking Accounts > Account Options > Options > Advanced and specifying the number of days in the Refresh Address Books and Rules Every field.

Address books and rules will also be re-downloaded in Caching mode when you click Tools > Retrieve Entire Mailbox.

8.3 Unread Message Count Feature
The GroupWise 6 SP1 client includes a new feature, Unread Message Count. Next to each folder, GroupWise displays the number of unread messages included in the folder.

For the Unread Message Count feature to work when the GroupWise client is running in Online mode, the GroupWise Post Office Agent must be the GroupWise 6 SP1 version.

8.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 and the client is installed in German, calendars will print in French.

9. Changes Since the Last Release (GroupWise 6)

The following sections provide information about changes that have been made in Support Pack 1 to resolve issues in the GroupWise 6 release. These changes do not include information about features that have been added in Support Pack 1. For information about new features, see "What's New in GroupWise 6" in the GroupWise 6 documentation.

9.1 Administration
The following changes were made to resolve GroupWise administration issues:

• You can create a post office which previously existed in your GroupWise system. (279470)
• If, while in ConsoleOne, you attempt to create a new domain while connected to a secondary domain, your domain connection will be switched from the secondary to the primary. If the primary domain connection cannot be made, you will receive the following error: "Database Error: The following GroupWise domain database file cannot be accessed properly: <UNC path to primary domain>." (244647)
• When creating a new dial-up schedule profile for the Internet Agent (Internet Agent object > SMTP/MIME tab > Scheduling page), the schedule information will be saved correctly to the new profile. In the past, if the new profile was not added to the end of the profile list (because of the alphabetic listing), the schedule information could be incorrectly assigned to another profile. (266777)
• GroupWise object descriptions display correctly. (266715)
• Modification of GroupWise objects no longer causes DB17 error (279931)
• The Setting Source information for the Internet Agent's Access Testing (Internet Agent object > Access Control tab > Settings page > Test button > View Access button) now displays the correct information. (261411)
• GroupWise users who are members of an NDS organizational role or NDS group can now be successfully removed as members of the role or group (266772)
• The SSL settings for the MTA and POA have been moved to their own page (ConsoleOne > MTA or POA object > GroupWise tab > SSL page). A certificate file is required to enable SSL. (263209)
• The Apply button on the WebAccess object property pages in ConsoleOne now works correctly. (263401)
• Moving or renaming an object in a single-domain system will now correctly generate synchronization updates to be sent to any connected external GroupWise systems. (263934)
• Switching connections from one domain to another while GroupWise object property pages are open no longer causes a NullPointerException error. (266272)
• Creating a new Link Schedule profile for an MTA will generate an MTA restart request. (264584)
• You can now disable Daylight Saving Time (DST) when modifying a time zone definition (265857)
• Scheduled events that have been migrated from GroupWise 5.x to GroupWise 6 can now be edited. (267229)
• Releasing a GroupWise domain in ConsoleOne no longer causes errors. (267598)
• A user or resource, when added to a distribution list through the Distribution List page on the User or Resource object, now appears on the Membership page of the Distribution List object. (267793)
• When creating a new post office with a library, the document type lookup table is now populated with the appropriate entries. (268362)
• When updating from GroupWise 5.x, the correct document storage area paths are retained (Library object > GroupWise tab > Storage Areas page). (268871)
• The Validate Domain option can now be used to fix the problem of two or more domains being marked as primary in a GroupWise system. The Validate Domain solution will only work is you have previously created Admin-defined fields; Admin-defined fields, when created, are assigned to the primary domain, so the validation process can check to see which primary domain the Admin-defined fields are assigned to and then change the other primary domains to secondary domains. (277461)
• The Internet Address options for External objects (External object > GroupWise tab > Internet Address page) will not be available unless Internet Addressing for the GroupWise system has been enabled. (281244)
• If a duplicate entry occurs when rebuilding a database, the duplicate entry's index and record ID will be written to a log file named REBUILD.LOG in the primary domain's directory. (277309)
• After merging a GroupWise 5.x domain into a GroupWise 6 system, you can now successfully move a user from a post office in the 5.x domain to a post office in a GroupWise 6 domain. All user information and mailbox items will be moved. (275687)
• You can now edit the default class of service for GroupWise WebAccess (WebAccess Agent object > Access Control tab > Settings page) and GroupWise Internet Agent (Internet Agent object > Access Control tab > Settings page). (277894)
• When grafting users, non-NDS users who do not match with NDS users now appear as unmatched users. (282916)
• You can now disable the flastname addressing format (279788)
• When you move a user from one post office to another, any GroupWise client options you've set for the user at the User level will be retained. (264123)
• Various issues regarding ConsoleOne performance were resolved (259116)
• You can now change a non-NDS user's GroupWise password in ConsoleOne, either through the user's GroupWise Account page (GroupWise External Entity object > GroupWise tab > Account page) or the user's GroupWise client options. (269946)
• You can now assign an NDS Group to a post office in a domain that you are not connected to. Previously, you could only see the post offices in the currently-connected domain. (273858)

9.2 Agents
The following changes were made to resolve MTA and POA issues:

• Resolved several issues that were causing the MTA to ABEND. (270552, 278562)
• The MTA now creates a log entry when a message is moved from a gateway into the MTA's GWINPROG queues. (279999)
• The Web console (HTTP view) for the MTA and POA now works properly with Netscape 6.1. (280085)
• Resolved several issues that were causing the POA to ABEND. (281094, 271572)
• Resolved an issue that was causing messages to be duplicated upon delivery. (265042)
• Resolved an issue that was causing the Move User process to fail if there was a C059 error on a deferred database (NGWDFR.DB). (260723)
• Resolved an issue that was causing the POA to create library directories for a post office after the post office's database had been rebuilt, even if the post office didn't have a library associated with it. (264952)
• After updating from GroupWise 5.x to GroupWise 6, scheduled maintenance tasks will now run properly (271105)
• The POA indexing process will now correctly generate wordlist files for documents marked for regeneration by GWCheck. (272086)
• Resolved an issue that was causing an item's message body not to appear when the item was sent using wildcard addressing (269273)

9.3 GWCheck and GWBackup
The following changes were made to resolve GWCheck and GWBackup issues:

• Resolved an issue that was causing GWCheck to crash when processing setup records. (283948)
• The GWCheck Storedrop option now works correctly. It will remove all user.db, msg.db, dmd*.db and dms*dB database types from the store catalog. (274486)
• Resolved an issue that was causing BackupExec for NT to fail when backing up a large number of files in a post office's OFUSER directory. (271027)
• The GWTSA is now able to back up all user databases in the post office's OFUSER directory. (280083)

9.4 Internet Agent
The following changes were made to resolve Internet Agent issues:

• Resolved several issues that were causing the Internet Agent to ABEND. (284051, 284053, 256292, 271307)
• In previous versions, inbound Internet messages sent to the Internet Agent's mailer-daemon could cause a loop between the mailer-daemon and the sender. This issue has been resolved; all messages sent to the mailer-daemon are moved to the Internet Agent's problem directory. (257277)
  

9.5 WebAccess
The following changes were made to resolve WebAccess issues:

• Resolved several issues that were causing the WebAccess Agent to ABEND when viewing certain types of documents. (255204, 255013, 258920, 253828, 255559)
• Resolved an issue that was causing the WebAccess Agent to ABEND. (261855)
• When viewing the next 25 items in a search, the correct list is now generated and displayed. (273588)
• An issue with the OBJ.CONF file that was causing users to experience login problems has been resolved. (271281)
• If a user does not have rights to a document that is in a shared folder, the user will still be able to see the document; he or she will no longer receive a "document not available" error. This is consistent with the GroupWise client for Windows functionality. (269080)
• Resolved an issue with the HTML viewers (by updating to version 7.1 of the viewers) that was causing problems some documents to display slowly and tie up the Web server. (272486)

9.6 Object API
The following changes where made to resolve issues with the Object API:

• The oMessage.Routed = True setting now functions correctly. Messages are routed rather than sent to each recipient at the exact same time. (256647)
• In caching mode, the Query object now functions correctly. (270166)
• Resolved an issue that was causing a folder Query cloning problem with Query.Expression. 272898)

9.7 Client
The following changes were made to resolve issues with the GroupWise client for Windows:

• In caching mode, you can now resend an item with a hidden attachment (an attachment not visible in the item's default view) without receiving an 8209 error. In the past, this error would only occur if the resent item had originally been sent while in online mode, downloaded to the caching mailbox, and then resent while in caching mode. (261993
• When proxying another user's mailbox, you can now properly view attachments while in the Send view. (241292)
• Improvements have been made to decrease memory usage when downloading or synchronizing NNTP accounts. (267752)
• In caching mode, you will no longer receive D124 errors when proxying to another user's mailbox. In the past, the connection was maintained to the proxied mailbox even after the proxy user changed back to his or her own mailbox. The connection to the proxied mailbox is now terminated. (278350)
• In remote mode, if you are using a dial-up networking connection, you will be automatically disconnected if you have enabled the "Hang Up When Send/Retrieve Is Done" options (GroupWise client > Accounts menu > Account Options > General Options). (114530)
• The issues with garbage characters appearing at the end of a reply has been resolved. (281221)
• After proxying to another user's or resource's mailbox and viewing the Month Calendar, the user's own Month Calendar will still display his or her own Calendar items. In the past, the user's Month Calendar would display the proxied user's or resource's Month Calendar. (260712)
• In caching and online mode, the default library setting (Tools > Options > Documents > Library Configuration) is the same. (269681)
• After moving a user from one post office to another, Busy Search will work correctly. (269662)
• You can now synchronize with a Windows CE device through MAPI. (269942)
• Appointments without a message body will now appear in an IPAQ Calendar. (272712)
• When using the GroupWise client with the Entrust 5.01 Entelligence client, you can now log out of GroupWise and GroupWise will be released from memory. In the past, GroupWise would not be released from memory and you could not log out of Entrust. (270042)
• After synchronizing reminder notes from a Palm device to the GroupWise client, you can print the reminder notes from your Calendar. (270428)
• You can now define Address Book custom filters that use the "contains" parameter. (270459)
• You can now use Internet Explorer 6.0 with GroupWise.
• The Signature settings (Tools > Options > Environment > Signature) will no longer be reset after running the Analyze/Fix Database maintenance option on a user's post office database. (271570)
• Edited attachments in a routed item now retain the modifications. (282627)
• Saving a draft of an item you are resending will no longer replace the draft of the original item. (269159)
• A user who has received Read rights to another user's appointments can no longer delete those appointments. This was only possible through the Month Calendar view. (273248)
• Resolved a memory issue that sometimes caused the GroupWise client to crash when a null password was entered during login (rather than the actual password). (273685)
• Resolved an issue with documents losing their "Official Version" tags. (273847)
• When associating a file type with an application in GroupWise (for example, right-click an attachment > click Open With > select an application > select Always Use This Program to Open These Files), the association is remembered in subsequent GroupWise sessions. (275206)
• The GroupWise client now works with RSA Keon Desktop CA. (275979)
• The GroupWise client is compatible with Windows XP and Windows Office XP. (282895)
• After a resource is moved or renamed, the Address Book now correctly reflects the renamed resource. (281236)
• When a user sends an item from a proxy mailbox, the proxy mailbox signature is added to the item rather than the user's own signature. (283871)
• An issue with QuickCorrect causing editing problems was resolved (253174)

10. Legal Information

10.1 Disclaimer, Export Notice, Patents, and Copyright
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.

This product may require export authorization from the U.S. Department of Commerce prior to exporting from the US or Canada.

US 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 and Patents Pending.

Copyright (C) 2001 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.

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

ConsoleOne, NLM, Novell Client, and Novell Cluster Services are trademarks of Novell, Inc.

Novell Technical Services is a service mark of Novell, Inc.

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