Release Notes r14

Isode R14.
2 Release Notes
Isode R14.2 Release Notes

Isode
Copyright 2008 Isode Limited, London, U.K.
1. Introduction
Release R14.2 is a new upgrade release of the full Isode product set consisting of: M-Vault (including M-Vault X.500 and M-Vault Connector) M-Switch (including M-Switch X.400, M-Switch SMTP, M-Switch Anti-Spam, and M-Switch MIXER and associated tools and utilities) M-Store X.400 M-Box (including M-Box POP/IMAP Gateway) M-Link XMPP server. M-Link will be the subject of a special announcement. Descriptions of these products are given on http://www.isode.com/products/. These release notes contain important information in Section 4, Upgrading. You must read these before starting to upgrade. Otherwise, you may lose data or have an unusable system.
2. New Features
This section outlines the new features available in R14.2.
2.1. M-Vault Family

Preliminary support for security labels and clearances is added, including Rule-Based Access Controls (RBAC) in MVault. Sodium has preliminary support for displaying security labels and clearances Password policy support is enhanced to support account locking, password aging, and the exclusion of special accounts from the policy. Passwords can be automatically migrated to use new hash algorithms. Sodium Sync now supports: Running updates without a GUI. Changing RDNs. Reparenting orphaned entries, flattening the tree. Better support for LDIF, including syncing from LDIF. Sodium has new editors for GeneralizedTime and CrossCertificatePair attributes. The Directory client API now supports password policy during binds, and SASL binds.
2.2. M-Switch Family

Support for STANAG 4406 Annex E and ACP 142 operation over STANAG 5066 is added. Sub-addressing (e.g. joe+folder@example.com) support is added. Core elements of configuration management are now accessible in MConsoles Switch View. Currently this support is read-only.
Isode R14.2 Release Notes The Event Viewer (part of MConsole) has usability and scaling improvements. The X.400 APIs are extended to support: X.411 Message Envelope features Some P772 (STANAG 4406) Military Messaging features Enhanced P7 list API to support size limit and ranges.
2.3. M-Box Family

Global SIEVE scripts are supported. Message cleanout, so that old messages may be automatically deleted on the server.
2.4. M-Link Family

M-Link is a new high-performance XMPP server.
2.5. Availability and Limitations

Mixing 32- and 64-bit versions of Isode products on a single system will not work. For example the 64-bit version of M-Vault must not be installed with the 32-bit versions of M-Switch and M-Box. Xuxa is only provided on Linux and 32-bit Windows. M-Box and M-Link are not supported on HP-UX. Sender Policy Framework (SPF) is not supported on Windows or HP-UX. ClamAV is the only 64-bit anti-virus plugin. The Sophos and Norman plugins are not available. Note that currently the Windows packages install all features selecting discrete features to install is not possible. If Custom installs are done, the same directory locations must be chosen for all packages.
3. Platform and Version Support

3.1. Supported Versions
Isode generally supports releases for 12 months from the date of release of the next major or minor release. The following releases are supported by Isode: R12.0 (until May 2008) R14.0 (until Oct 2008) R14.1 (until March 2009) Support is generally no longer provided by Isode for the following releases: R10.2 (since July 2005) R10.5 (since January 2006) R10.6 (since April 2006) R11.0 (since May 2006) R11.1 (since November 2006) R11.2 (since December 2006) R11.3 (since April 2007) R11.4 (since June 2007)
Isode R14.2 Release Notes R11.5 (since October 2007)
3.2. Supported Platforms

R14.2 is supported on the following platforms: Red Hat Enterprise Linux 4.0 (32- and 64-bit) and 5.0 (32- and 64-bit) and CentOS equivalents SuSE Linux Enterprise Server 10 Solaris 10 (64-bit) HP-UX 11iv1 on PA-RISC (32-bit) Windows Server 2003 Enterprise Edition with SP2 (32- and 64-bit) However please note the exceptions listed in Section 2.5, Availability and Limitations. Isode strongly recommends that production services operate only on supported platforms, and that evaluations of Isode products are only undertaken on supported platforms. Use of the Isode servers on Windows XP and Vista is appropriate for simple evaluations and demonstrations. However, Isode does not support running the servers on these OSes in a production environment. The Isode client applications are fully supported on Windows XP and Vista. The Solaris packages are only supported on UltraSPARC processors (sun4u architecture) or later. Linux and Windows packages require a Pentium II or better, or AMD Athlon. In all cases the operating system must be updated with all available updates and patches from the operating system supplier. This can be important for the security of your system. Isode reserves the right not to support a system which is not up to date. On Solaris it is necessary to have the latest patched version of Suns C++ run time libraries. The latest patch number is 119963-08. More recent versions of these patches should be used if available.
3.3. Supported Platforms (Future Releases)

A future release will add support for: Windows Server 2008 We are also considering adding support for: Solaris 10 on Intel HP-UX on Itanium Update releases on existing platforms will not be affected. If these changes might cause you problems, please let us know as soon as possible.
3.4. Cryptographically Secure Source of Random Data

M-Vault, M-Switch, M-Box and M-Link require a source of random data for certain cryptographic operations which on Unix is conventionally obtained from /dev/urandom. However, not all versions of HP-UX have this device by default, and while this will not prevent M-Vault, M-Switch, M-Box and M-Link from working, Isode recommends that where possible, you install an appropriate operating-system patch for HP-UX. For HP-UX 11i and higher, you should obtain the HP-UX Strong Random Number Generator, which provides /dev/ urandom, by visiting http://software.hp.com/ and installing the KRNG11i package.
Neither Solaris, Linux nor Microsoft Windows require any additional operating-system patches relating to cryptographic random data to support M-Vault, M-Switch, M-Box, or M-Link.
3.5. Licensing
You will need licenses appropriate to R14 for each of your licensed products. Please contact <license@isode.com> for further details. You should obtain this file prior to installing the new version.
3.6. Documentation
Documentation of previous releases is available from the Isode web site at http://www.isode.com/support/docs.html. R14.2 documentation will be available shortly after the release in the same location.
3.7. External Dependencies

3.7.1. Tcl, Tk, Tix
For release R14.2 you must use the new Isode Tcl/Tk and Tix packages. All platforms require the Isode supplied versions of Tcl/Tk and Tix. For release R14.2 these versions are: Tcl 8.4.15, Tk 8.4.15 and Tix 8.1.3. These are available from the same location as the main packages. Also note that 64-bit versions of Tcl, Tk and Tix must be used with 64-bit versions of Isode products.
3.7.2. Java
Some components of release R14.2 are written in Java. You should install any Java dependencies before installing the following components of the Isode packages. If you do not require these components then you do not need to install Java. On HP-UX you must download HPs JRE/JDK implementation. On all other platforms Isode recommend you download either JDK 5 (1.5) or JDK 6 (1.6) from the Sun website (see http://java.sun.com/javase/downloads/). Note that 64-bit installations require a 64-bit JRE. The default JRE on Red Hat Linux (gcj) does not work. IBMs JRE also does not work. DConsole, Sodium, MConsole: These applications require that a suitable Java Runtime Environment (JRE) has been installed, and that (on Solaris, Linux and HP-UX) it is earlier in the PATH than any other directory containing a java executable. Xuxa: This application requires that a suitable Java Runtime Environment (JRE) has been installed. Audit Database and IMA Web Applications: The Web Applications are written in Java/JSP and you must install a JDK (not a JRE) so that Tomcat can deploy the webapp. No other components of R14.2 require Java.
3.7.3. Audit Database Dependencies

To run the new features based on the Audit Database (i.e. Message Tracking and Quarantine Management), you must ensure that these external dependencies are satisfied: Tomcat: The Web Applications run as Tomcat servlets. You must download and install Tomcat 5.5 from http:// jakarta.apache.org/tomcat/. Java Development Environment (JDK): See Section 3.7.2, Java. PostgreSQL: The Audit database requires PostgreSQL 8. Red Hat EL 4: download PostgreSQL 8 from http://www.postgresql.org/.
Isode R14.2 Release Notes Red Hat EL 5: install the current version from Red Hat. SuSE: install the current version from SuSE. Solaris 10: use the version supplied by Sun. Windows: download PostgreSQL 8 from http://www.postgresql.org/ and install everything except for the Development and PostGIS components. You will also need the Tcl Postgres library. Download the static version of libpgtcl1.5.dll from http:// pgfoundry.org/projects/pgtcl/. No other components of R14.2 require Tomcat or PostgreSQL.
4. Upgrading
Follow the instructions appropriate for the platform you are using, and the release you are upgrading from.
4.1. From R11 to R14.2v0

4.1.1. Linux
1. If non-TCP OSI transports are being used, follow this additional step: 2. Section 4.5.1, OSI Transport Providers
If M-Switch is installed, follow this additional step: Section 4.5.2, Empty the Message Queue
3.
If M-Vault is installed, follow this additional step: Section 4.5.3, Find Old GDAMs
4. 5.
Section 4.5.5, Stop Linux programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
6. 7. 8.
Section 4.5.13, Upgrade Linux Tcl, Tk and Tix packages Section 4.5.17, Upgrade Linux Packages If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.27, Restart M-Vault on Linux
9.
If M-Box is installed, follow these additional steps: a. b. Section 4.5.31, msg_track.db Change Section 4.5.32, ms_sync.xml Change
10. If M-Switch is installed, follow these additional steps: a. b. Section 4.5.34, Upgrade M-Switch Configuration Section 4.5.35, Rebuild M-Switch Tables
11. If M-Store is installed, follow these additional steps: a. Section 4.5.36, Upgrade M-Store Configuration
Isode R14.2 Release Notes b. Section 4.5.37, Upgrading M-Store X.400 Mailboxes
12. Section 4.5.39, Restart Linux Servers 13. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
14. If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.1.2. Solaris
3.
4. 5.
Section 4.5.6, Stop Solaris programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
6. 7. 8.
Section 4.5.14, Upgrade Solaris Tcl, Tk and Tix packages Section 4.5.18, Upgrade Solaris Packages If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.28, Restart M-Vault on Solaris
9.
11. If M-Store is installed, follow these additional steps: a. b. Section 4.5.36, Upgrade M-Store Configuration Section 4.5.37, Upgrading M-Store X.400 Mailboxes
12. Section 4.5.40, Restart Solaris Servers 13. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
14. If any webapps (Message Tracking or IMA) are installed, follow this step:
Isode R14.2 Release Notes Section 4.5.44, Redeploying Web Applications
4.1.3. HP-UX
1. If M-Switch is installed, follow this additional step: 2. Section 4.5.2, Empty the Message Queue
3. 4.
Section 4.5.8, Stop HP-UX programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
5. 6. 7.
Section 4.5.15, Upgrade HP-UX Tcl, Tk and Tix packages Section 4.5.19, Upgrade HP-UX Packages If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.29, Restart M-Vault on HP-UX
8.
If M-Switch is installed, follow these additional steps: a. b. Section 4.5.34, Upgrade M-Switch Configuration Section 4.5.35, Rebuild M-Switch Tables
9.
If M-Store is installed, follow these additional steps: a. b. Section 4.5.36, Upgrade M-Store Configuration Section 4.5.37, Upgrading M-Store X.400 Mailboxes
10. Section 4.5.41, Restart HP-UX Servers 11. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
4.1.4. Windows
3. 4.
Section 4.5.9, Stop Windows programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
5.
If M-Box is installed, follow this additional step:
Isode R14.2 Release Notes 6. 7. 8. 9. Section 4.5.12, Uninstall M-Box Service
Section 4.5.16, Upgrade Windows Tcl, Tk and Tix packages Section 4.5.20, Upgrade Windows Packages Section 4.5.22, Recreate Windows Services If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.30, Restart M-Vault on Windows
10. If M-Box is installed, follow these additional steps: a. b. c. Section 4.5.31, msg_track.db Change Section 4.5.32, ms_sync.xml Change Section 4.5.33, Restart M-Box Windows Service
13. Section 4.5.42, Restart Windows Services 14. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
4.2. From R12.0 to R14.2v0

4.2.1. Linux
3.
4. 5.
Section 4.5.5, Stop Linux programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
6.
Section 4.5.13, Upgrade Linux Tcl, Tk and Tix packages
Isode R14.2 Release Notes 7. 8. Section 4.5.17, Upgrade Linux Packages If M-Vault is installed, follow these additional steps: a. b. c. d. 9. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.27, Restart M-Vault on Linux
12. Section 4.5.39, Restart Linux Servers 13. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
4.2.2. Solaris
3.
4. 5.
Section 4.5.7, Stop Solaris services If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
6. 7. 8.
Section 4.5.14, Upgrade Solaris Tcl, Tk and Tix packages Section 4.5.18, Upgrade Solaris Packages If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.28, Restart M-Vault on Solaris
Isode R14.2 Release Notes 9. If M-Box is installed, follow these additional steps: a. b. Section 4.5.31, msg_track.db Change Section 4.5.32, ms_sync.xml Change
10
12. Section 4.5.40, Restart Solaris Servers 13. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
4.2.3. HP-UX
3. 4.
Section 4.5.8, Stop HP-UX programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
5. 6. 7.
Section 4.5.15, Upgrade HP-UX Tcl, Tk and Tix packages Section 4.5.19, Upgrade HP-UX Packages If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.29, Restart M-Vault on HP-UX
8.
If M-Switch is installed, follow these additional steps: a. b. Section 4.5.34, Upgrade M-Switch Configuration Section 4.5.35, Rebuild M-Switch Tables
9.
If M-Store is installed, follow these additional steps: a. b. Section 4.5.36, Upgrade M-Store Configuration Section 4.5.37, Upgrading M-Store X.400 Mailboxes
10. Section 4.5.41, Restart HP-UX Servers 11. If Message Tracking is installed, follow this step:
Isode R14.2 Release Notes Section 4.5.43, Upgrading MTrack Database Schema
11
4.2.4. Windows
3. 4.
Section 4.5.9, Stop Windows programs If M-Vault is installed, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
5.
If M-Box is installed, follow this additional step: Section 4.5.12, Uninstall M-Box Service
6. 7. 8. 9.
Section 4.5.16, Upgrade Windows Tcl, Tk and Tix packages Section 4.5.20, Upgrade Windows Packages Section 4.5.22, Recreate Windows Services If M-Vault is installed, follow these additional steps: a. b. c. d. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes Section 4.5.30, Restart M-Vault on Windows
13. Section 4.5.42, Restart Windows Services 14. If Message Tracking is installed, follow this step: Section 4.5.43, Upgrading MTrack Database Schema
12
4.3. From R14.0 to R14.2v0

4.3.1. Linux
1. If M-Vault is being used with the old qbDiskGdams, follow this additional step: 2. 3. Section 4.5.3, Find Old GDAMs
Section 4.5.5, Stop Linux programs If M-Vault is being used with the old qbDiskGdams, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
4. 5. 6.
Section 4.5.13, Upgrade Linux Tcl, Tk and Tix packages Section 4.5.17, Upgrade Linux Packages If M-Vault is being used with the old qbDiskGdams, follow these steps: a. b. c. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes
7.
If M-Vault is installed, follow this additional step: Section 4.5.27, Restart M-Vault on Linux
8.
9.
Section 4.5.39, Restart Linux Servers
4.3.2. Solaris
Section 4.5.7, Stop Solaris services If M-Vault is being used with the old qbDiskGdams, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
4. 5. 6.
Section 4.5.14, Upgrade Solaris Tcl, Tk and Tix packages Section 4.5.18, Upgrade Solaris Packages If M-Vault is being used with the old qbDiskGdams, follow these steps: a. b. c. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes
7.
If M-Vault is installed, follow this additional step: Section 4.5.28, Restart M-Vault on Solaris
8.
If M-Box is installed, follow these additional steps:
Isode R14.2 Release Notes a. b. 9. Section 4.5.31, msg_track.db Change Section 4.5.32, ms_sync.xml Change
13
Section 4.5.40, Restart Solaris Servers
4.3.3. HP-UX
Section 4.5.8, Stop HP-UX programs If M-Vault is being used with the old qbDiskGdams, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
4. 5. 6.
Section 4.5.15, Upgrade HP-UX Tcl, Tk and Tix packages Section 4.5.19, Upgrade HP-UX Packages If M-Vault is being used with the old qbDiskGdams, follow these steps: a. b. c. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes
7.
If M-Vault is installed, follow this additional step: Section 4.5.29, Restart M-Vault on HP-UX
8. 9.
Section 4.5.41, Restart HP-UX Servers If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.3.4. Windows
1. If M-Vault is being used, follow this additional step: 2. 3. Section 4.5.4, Find All GDAMs
Section 4.5.9, Stop Windows programs If M-Vault is being used with the new High-Performance GDAMs, follow this additional step: Section 4.5.10, Prepare High-Performance GDAMs on Windows
4.
If M-Vault is being used with the old qbDiskGdams, follow this additional step: Section 4.5.11, Prepare GDAMs for Upgrade
5.
If M-Box is installed, follow this additional step: Section 4.5.12, Uninstall M-Box Service
6. 7. 8. 9.
Section 4.5.16, Upgrade Windows Tcl, Tk and Tix packages Section 4.5.20, Upgrade Windows Packages Section 4.5.22, Recreate Windows Services If M-Vault is being used with the old qbDiskGdams, follow these steps:
Isode R14.2 Release Notes a. b. c. Section 4.5.23, Schema Check Section 4.5.24, Upgrading DSA GDAMs Section 4.5.25, Rebuild All Indexes
14
10. If M-Vault is installed, follow this additional step: Section 4.5.30, Restart M-Vault on Windows
12. Section 4.5.42, Restart Windows Services 13. If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.4. From R14.1 to R14.2v0

4.4.1. Linux
1. 2. 3. Section 4.5.5, Stop Linux programs Section 4.5.17, Upgrade Linux Packages If M-Vault is installed, follow these additional steps: a. b. 4. Section 4.5.26, Rebuild Integer Indexes Section 4.5.27, Restart M-Vault on Linux
If M-Store is installed, follow this additional step: Section 4.5.38, Update M-Store Message Index Entries
5. 6.
Section 4.5.39, Restart Linux Servers If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.4.2. Solaris
1. 2. 3. Section 4.5.7, Stop Solaris services Section 4.5.18, Upgrade Solaris Packages If M-Vault is installed, follow these additional steps: a. b. 4. Section 4.5.26, Rebuild Integer Indexes Section 4.5.28, Restart M-Vault on Solaris
5. 6.
Section 4.5.40, Restart Solaris Servers If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
15
4.4.3. HP-UX
1. 2. 3. Section 4.5.8, Stop HP-UX programs Section 4.5.19, Upgrade HP-UX Packages If M-Vault is installed, follow these additional steps: a. b. 4. Section 4.5.26, Rebuild Integer Indexes Section 4.5.29, Restart M-Vault on HP-UX
5. 6.
Section 4.5.41, Restart HP-UX Servers If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.4.4. Windows
1. 2. 3. Section 4.5.9, Stop Windows programs Section 4.5.21, Upgrade R14.1 Windows Packages If M-Vault is installed, follow these additional steps: a. b. 4. Section 4.5.26, Rebuild Integer Indexes Section 4.5.30, Restart M-Vault on Windows
5.
If M-Box is installed, follow these additional steps: Section 4.5.33, Restart M-Box Windows Service
6. 7.
Section 4.5.42, Restart Windows Services If any webapps (Message Tracking or IMA) are installed, follow this step: Section 4.5.44, Redeploying Web Applications
4.5. Upgrade Steps

This section contains all the individual steps required on each platform, and is not meant to be read or followed directly. See the version and platform-specific steps in Section 4, Upgrading.
4.5.1. OSI Transport Providers

The configuration of OSI transport providers other than over TCP has been significantly changed in R14.0. These are often used for X.400 P1 connections. As documentation of this is not yet available, please contact Isode Support for information about this, sending a copy of your /etc/isode/isotailor file. (If you have no isotailor file, then you are not using a non-TCP OSI transport provider).
4.5.2. Empty the Message Queue

1. Disable the inbound channels, which will cause the MTAs message queue to empty. Stopping the smtpsrvr and/ or iaed processes (for Internet or X.400 MTAs respectively) does this.
Isode R14.2 Release Notes 2.
16
In addition any XMT or Isode Gateway client should have their outbound sides (i.e. transferring messages into the MTA) disabled.
4.5.3. Find Old GDAMs

R14.0 implements a new high performance GDAM database. In addition an updated version of the Sleepycat library is being used. Upgrading from previous releases requires that the following steps are performed carefully in order to avoid the risk of data loss. This upgrade process is irreversible; the only way to revert to a previous release of M-Vault is to restore the database from backup. Therefore it is critical that you take a backup. To prepare for the upgrade, you must follow the steps below before installing the new packages. 1. 2. Connect EDM to each DSA. Select each old GDAM and choose Database properties.... Write down (e.g. on paper, or in a text file) the value of each GDAMs directory path. Note: High-performance GDAMs do not need upgrading; their properties are accessed using a different option: High performance database properties....
4.5.4. Find All GDAMs

The database environments used in R14.0 GDAMs on Windows is incompatible with R14.1, and needs to be cleaned up prior to upgrading. To prepare for the upgrade, you must follow the steps below before installing the new packages. 1. 2. Connect EDM to each DSA. Select each GDAM and choose Database properties.... Write down (e.g. on paper, or in a text file) the value of each GDAMs directory path. Note: do this for High-performance GDAMs as well as the previous GDAM implementation.
4.5.5. Stop Linux programs

All the Isode products need to be stopped. To stop any servers: 1. If M-Store X.400 is installed, run:
# /etc/rc.d/init.d/pumice stop
2.
If M-Box is installed, run:

# /etc/rc.d/init.d/mbox stop
3.
If M-Switch is installed, run:

# /etc/rc.d/init.d/pp stop
4.
If M-Vault is installed, run:

# /etc/rc.d/init.d/eddy stop
4.5.6. Stop Solaris programs

All the Isode products need to be stopped. To stop any servers:
Isode R14.2 Release Notes 1. If M-Store X.400 is installed, run:

# /etc/init.d/pumice stop
17
2.

# /etc/init.d/mbox stop
3.

# /etc/init.d/pp stop
4.

# /etc/init.d/eddy stop
4.5.7. Stop Solaris services

# svcadm disable -t pumice
2.

# svcadm disable -t mbox
3.

# svcadm disable -t pp
4.

# svcadm disable -t eddy
4.5.8. Stop HP-UX programs

# /sbin/pumice stop
2.

# /sbin/pp stop
3.

# /sbin/eddy stop
18
4.5.9. Stop Windows programs

All the Isode products need to be stopped. To stop any servers: 1. 2. 3. Run Isode Service Manager. Select Service Stop all. Wait for the services to stop. Exit the Isode Service Manager.
4.5.10. Prepare High-Performance GDAMs on Windows

The database environments used in R14.0 GDAMs on Windows is incompatible with R14.1, and needs to be cleaned up prior to upgrading. To prepare for the upgrade, you must follow the steps below before installing the new packages. On each High-Performance GDAM recorded in Section 4.5.4, Find All GDAMs: Perform database recovery and remove the environment. Run the command:
C:\Program Files\Isode\bin\> db_recover -c -h gdam-dir
4.5.11. Prepare GDAMs for Upgrade

R14.0 implements a new high performance GDAM database. In addition an updated version of the Sleepycat library is being used. Upgrading from previous releases requires that the following steps are performed carefully in order to avoid the risk of data loss. This upgrade process is irreversible; the only way to revert to a previous release of M-Vault is to restore the database from backup. Therefore it is critical that you take a backup. To prepare for the upgrade, you must follow the steps below before installing the new packages. 1. 2. Perform a full backup of the DSA (not an incremental backup which just copies newer transaction logs). On each old qbDiskGdam GDAM recorded in Section 4.5.3, Find Old GDAMs: a. Perform database recovery and use db_recover to preserve the database environment. Run the command:
# db_recover -h gdam-dir -e
b.
Make sure there are no uncheckpointed transactions. Run the command:

# db_checkpoint -h gdam-dir -1
(the final argument is numeric one) c. Find out what transaction logs are no longer required. Run the command:
# db_archive -h gdam-dir
d.
Remove transaction logs that are no longer required. For example on Unix run the command:
# cd gdam-dir/txnlog; rm -f `db_archive -h gdam-dir`
e.
Run recovery and remove the database environment. Run the command:
19
# db_recover -h gdam-dir
4.5.12. Uninstall M-Box Service

Before upgrading M-Box from a previous version, you need to run Start Programs Isode R14.0 Uninstall MBox services or C:\Program Files\Isode\bin\mbox uninstall. This will remove information about M-Box services, but will not affect other configuration (like (ETCDIR)\ms.conf) or existing email.
4.5.13. Upgrade Linux Tcl, Tk and Tix packages

# rpm -U ISDtcl-*rpm ISDtkx-*rpm ...
4.5.14. Upgrade Solaris Tcl, Tk and Tix packages

1. Remove each old package:
# yes | pkgrm ISDtcl # yes | pkgrm ISDtkx # ...
2.
Install each new package:

# pkgadd -d ./ISDtcl-*pkg all # pkgadd -d ./ISDtkx-*pkg all # ...
4.5.15. Upgrade HP-UX Tcl, Tk and Tix packages

# swremove ISDtcl # swremove ISDtkx # ...
2.

# swinstall -s `pwd`/ISDtcl-*depot '*' # swinstall -s `pwd`/ISDtkx-*depot '*' # ...
Alternatively, sam(1M) can be used.
4.5.16. Upgrade Windows Tcl, Tk and Tix packages

1. 2. Remove the previous Isode TclTkTix package using Control Panel Add/Remove Programs. Install the new MSI file by either double-clicking on it, or using the msiexec.exe tool.
4.5.17. Upgrade Linux Packages

# rpm -U ISDbase-*rpm ISDtps-*rpm ...
20
4.5.18. Upgrade Solaris Packages

# yes | pkgrm ISDbase # yes | pkgrm ISDtps # ...
2.

# pkgadd -d ./ISDbase-*pkg all # pkgadd -d ./ISDtps-*pkg all # ...
4.5.19. Upgrade HP-UX Packages

# swremove ISDbase # swremove ISDtps # ...
2.

# swinstall -s `pwd`/ISDbase-*depot '*' # swinstall -s `pwd`/ISDtps-*depot '*' # ...
Alternatively, sam(1M) can be used.
4.5.20. Upgrade Windows Packages

1. 2. Remove the previous Isode packages using Control Panel Add/Remove Programs. We recommend running regedit.exe and manually removing any references to previous Isode installations in the values of the Windows Registry key: HKLM\Software\Microsoft\Windows\CurrentVersion\SharedDLLs Values of the key will be the full path of files under (by default) C:\Program Files\Isode\. 3. Install the new MSI files by either double-clicking on them, or using the msiexec.exe tool.
4.5.21. Upgrade R14.1 Windows Packages

Install the new MSI files by either double-clicking on them, or using the msiexec.exe tool.
4.5.22. Recreate Windows Services

1. 2. Run Isode Service Manager. Select Service Create Default Isode Services. You should see that old services are removed and new services are added. 3. Edit the startup order (you may have to remove duplicate entries.)
21
4.5.23. Schema Check

The directory schema has been changed and extended since R12.0. In particular, new object classes have been added that are required by the new database implementation. If you have made local changes to the default OID tables then you should ensure that the new object class bAGdam copied across before upgrading. If youre using the EncryptedPassword syntax then you should check that any newly installed OID tables are appropriately updated, otherwise simply authenticated binds are likely to fail.
4.5.24. Upgrading DSA GDAMs

After preparing the DSA as described in Section 4.5.11, Prepare GDAMs for Upgrade and installing the new packages you should run the dsaupgrade script. This upgrades the DSA in-place to the new high-performance database format.
dsaupgrade -D dsa-directory -u dsa-manager-dn [-v] [-l log-directory] [-b backup-directory]
Where:
-D dsa-directory
The location of the DSAs directory on disk; i.e. the directory containing the dse.db file.
-u dsa-manager-dn
The DSA Managers DN.

-v
Run in verbose mode (recommended.)

-l log-directory
Log details of the upgrade to this directory instead of the default directory.
-b backup-directory
Copy a backup to this directory instead of the default directory. The script can perform backups for you if required, though this is not necessary if, as recommended in Section 4.5.11, Prepare GDAMs for Upgrade, a full backup of the DSA has already been made. A log of the upgrade procedure is written to dsaupgrade.log in the regular Isode logging directory (or elsewhere if the -l flag was passed to dsaupgrade).
4.5.25. Rebuild All Indexes

Note that the upgraded DSA will have a default set of indexes. In order to build any required indexes you should start the DSA, connect with EDM and configure indexes as necessary.
4.5.26. Rebuild Integer Indexes

The format of indexes used for attributes of syntax Integer and Enumeration, has changed. The old indexes should be removed and new ones created. For example, to recreate an equality index for myattr in the GDAM /var/isode/dsa-db/gdam1, run:
# cd /var/isode/dsa-db/gdam1 # /opt/isode/sbin/dsbdmkindex -x myattr:e # /opt/isode/sbin/dsbdmkindex myattr:e
4.5.27. Restart M-Vault on Linux

Run:
22
# /etc/rc.d/init.d/eddy start
4.5.28. Restart M-Vault on Solaris

Run:
# svcadm enable eddy
4.5.29. Restart M-Vault on HP-UX

Run:
# /sbin/eddy start
4.5.30. Restart M-Vault on Windows

1. 2. 3. Run Isode Service Manager. Select the Isode M-Vault service. Select Service Start.
4.5.31. msg_track.db Change

The format of C:\Isode\ms\msg_track.db (Windows) and /var/isode/ms/msg_track.db (Unix) has changed. Before starting R14.2 M-Box for the first time the file should be deleted manually.
4.5.32. ms_sync.xml Change

The ms_sync.xml has changed slightly: the previous imap_id attribute is now called frontend_id and the pop3_id attribute is now called backend_id.
4.5.33. Restart M-Box Windows Service

1. 2. Choose Start Programs Isode R14.2 Services Install M-Box services. Choose Start Programs Isode R14.2 Services Start M-Box services.
4.5.34. Upgrade M-Switch Configuration

In R14.0 there was a significant change in the configuration of content conversion. This particularly affects MIXER gateways. If your configuration has been altered from the standard configurations, please make a copy of your mtatailor file (in /etc/isode/switch/mtatailor or C:\Isode\etc\switch\mtatailor). As documentation of the configuration mechanism is not yet available, you are advised to contact Isode Support prior to your upgrade, sending your current mtatailor file. This should not be necessary for a simple X.400 or Internet M-Switch system, as the configuration will be upgraded appropriately. You must do the following after installing the packages: Run EMMA. a. b. Follow the upgrade instructions. For each non-external MTA: i. Right-click and create a stub MTA tailor file.
Isode R14.2 Release Notes ii.
23
Move the created stub file to C:\Isode\etc\switch or /etc/isode/switch on the system running the MTA.
iii. Rename the file created (mtatailor.mtaname) to mtatailor.
4.5.35. Rebuild M-Switch Tables

If you have configured M-Switch tables with type=dbm, you must remove the ppdbm directory which is normally C: \Isode\etc\switch\ppdbm on Windows and /etc/isode/switch/ppdbm on Unix). Then, recreate the dbm files by running dbmbuild. On Unix you must do this as the user which owns the file (EXECDIR)/sendmail, which is usually pp.
4.5.36. Upgrade M-Store Configuration

1. 2. Run EMMA. For each M-Store in the configuration choose Configure DSA for Message Store use.
4.5.37. Upgrading M-Store X.400 Mailboxes

The format in which messages are stored has changed for R14.0, and pre-R14 mailboxes cannot be read by the new version of M-Store X.400. As documentation of the upgrade mechanism is not yet available, you are advised to contact Isode Support prior to your upgrade.
4.5.38. Update M-Store Message Index Entries

The message index entries held in M-Vault changed between R14.1 and R14.2. To upgrade them run:
# /opt/isode/sbin/ms_upgrade_R14p1
4.5.39. Restart Linux Servers

1. If M-Store X.400 is installed, run:
# /etc/rc.d/init.d/pumice start
2.

# /etc/rc.d/init.d/mbox start
3.

# /etc/rc.d/init.d/pp start
4.5.40. Restart Solaris Servers

# svcadm enable pumice
2.

# svcadm enable mbox
Isode R14.2 Release Notes 3. If M-Switch is installed, run:

# svcadm enable pp
24
4.5.41. Restart HP-UX Servers

# /sbin/pumice start
2.

# /sbin/pp start
4.5.42. Restart Windows Services

1. 2. Run Isode Service Manager. Select Service Start all.
4.5.43. Upgrading MTrack Database Schema

The underlying database used by MTrack has changed, and must be upgraded using the appropriate upgrade_database scripts in the right order. For example, to upgrade from R11.2 to R14.0 you must run isode/share/upgrade_database_111_113.sh and then isode/share/upgrade_database_113_120.sh and then cisode/share/upgrade_database_120_140.sh.
4.5.44. Redeploying Web Applications

To redeploy the web applications (MTrack and IMAdmin) you should: 1. 2. 3. 4. 5. 6. Stop Tomcat. Stop all applications using the audit database. Remove the old webapps (both the .war files and the deployed directories with the same name with the war extension.) Copy the new webapps from /opt/isode/lib/java/webapps into the Tomcat webapps directory. Copy the classes from /opt/isode/lib/java/classes/*.jar into the Tomcat common/lib directory. On Windows, you must ensure that the Isode bin directory (typically C:\Program Files\Isode\bin) is included in the PATH setting for the Tomcat process. The Isode web applications rely on this in order to be able to work properly. Finally, restart Tomcat.
7.
5. Bugs Resolved In R14.2v0 Since R14.1v0

5.1. M-Vault
5.1.1. LDAP/X.500 Directory Services
General 41698 DSP Result encode errors are not being sent correctly to a DSP initiator
Isode R14.2 Release Notes High-Performance GDAM 41475 41540 41551 41553 41559 41569 41570 41572 41588 41594 41595 41596 41615 41616 41628 41665 41673 41688 41693 Glue entries created between DSA and initial naming context Index test (man 043) UNRESOLVED on Linux - DSA test suit DB errors not logged with sufficient detail. Name lock error reported after total update processing in consumer Look through limits are not honoured. certain search filters can cause DSA crash on Windows DSA crashes when attempting to read entries that contain "audio" attributes Searches fail if filter contains substrings shorter than index supported length. bagdam doesn't properly honour "group of names" ACIs Filters containing ORs do not return all results Access controls from inner areas ignored in searches Dbulk uses excessive memory when loading to a BAG database ModifyDN not handled correctly in consumer BAG doesn't support support subtype matching as was allowed in old database dsbdmkindex doesn't create multiple indexes for an attribute Empty attributes can remain in cache after remove values in incremental update modifydn operations that should return "already exists" return "naming violation" DSA leaks file handles with file-based attributes DSA core dump if index operation in progress when DSA is shut down
25
Bulk loading tools 41529 41674 dsaupgrade ignores the -l flag DSA upgrade leaves bogus entries in shadow changelog database.
Chaining 41618 edmsh 41506 dmi modify does not call editors correctly on Windows Failed DSP Associations never get retried
LDAP interface 41548 41589 41609 LDAP connections are logged with an incorrect IP address LDAP client sending broken server-side sort request may cause DSA to segfault Bad PasswdModify operation values aren't rejected properly
Management 41625 Security 41550 41603 41622 41640 Configuring CRL checking for M-Vault fails and disables any subsequent strong authentication TLS cipher suite choice is not restricted by DSA server settings EntryACI ignored in browsing DIT Setting pwdConfiguredSchemeGenerators to "cleartext" crashes DSA SNMP logs hostnames not IP addresses.
Isode R14.2 Release Notes Shadowing 41554 41571 Shadow ModifyDN operations sent by R14 DSAs fail in pre-R14 consumers. R14.1 incremental applier is not forgiving of replayed modify operations.
26
5.1.2. Sodium ADUA

General 41274 41461 41472 41489 41490 41538 41641 RDN editor thinks that RDNs match when they differ in case/whitespace Sodium crashes during LDIF load over DAP when input data is invalid Sync mapping <add> action when conditional can fail due to syntax conversion A missing bind profile doesn't cause Sync to stop immediately Sodium Sync's mapping rules for AD don't handle proxyaddress CA entries using certificationAuthority are not displayed sensibly Sodium crashes when trying to a display CRL that has empty "lastupdate" or "nextupdate" fields
5.1.3. DAP/LDAP DUA library

Documentation 41601 Need more examples in the API docs
5.1.4. Directory Services Library

common 41520 dsap_init() not thread-safe
5.1.5. Directory Client Applications

LDAP tools 41525 ldapsearch segfaults when using "-E" to specify search extensions
5.2. M-Switch
5.2.1. Message Switch Configuration
General 41449 41455 41480 41508 41515 41519 EMMA doesn't show synonyms and aliases when using OU naming policies Can't create users with White Pages Wrong DSA attributes used for P-MUL settings Can't create a new Message Store remotely Tcl error raiseds when trying to add an existing Routing Tree node Missing DSA access attributes for new MTAs when using archiving
EMMA library 41662 split logging get log files names wrong
tclicamlib 41602 Tcl error raised when trying up upgrade old Message Stores
27
5.2.2. Message Switch

822-local-channel 41040 General 4044 Other 41477 shutdown script on hpux ignores SWITCH_PROGS_TO_KILL Unnecessary attributes and syntaxes defined 822-local delivery on MIXER MTA has problems
Checker formatter 41539 41653 Cannot interface to ClamAV on Windows FD leakage and FD accessed after close in uudecoding
Housekeeper channel 41487 41578 M-Switch generates an invalid DSN Housekeeper channel can generate bad DR if given Probe which has content-return set
Lists channel 41453 41523 List channel generates wrong Non Delivery Report Diagnostic Processing multiple DRs though single list channel instance can cause error
mhsmime-formatter 41504 qmgr 41456 41552 41560 41561 41563 41574 41670 qmgr does not log to mlogd Handles leaked when Qmgr starts channel process Rerouting not displayed when rerouted MTA not available Groups not reassigned when rerouting changes on MTA config reload Message stats decremented incorrectly on submission failure Break in SOM connection while returning data can lock MTA or message Setting maximum connections to MTA does not disable auto tuning The IPN to DSN mapping generated by MIXER doesn't comply to RFC 2156
qmgr interface library 41495 Rerouting conflict between queue manager and channel
Quickconfig 41462 Quick Config on Windows cannot cope with some non standard paths
SMTP/LMTP (slmtp) outgoing channel 41230 41531 41536 slmtp core dump DATA failure results in subsequent messages on same connection failing Failure to open connection to second address for host can cause crash
Isode R14.2 Release Notes SMTP server 41660 Server can block on DNS forward lookup check
28
Submission library 41575 41584 41605 41657 41658 Confusing DRR+DRD when message sizelimit exceeded Timout interval for Probes not configurable Sets incorrect content-type for reports alternate-receipient-allowed always defaults to TRUE Loops not detected for Probes or DRs
tailor-library 41501 Library exits if no tailor file
X.400 library 41392 Wrong logging or network address checking E-MTA_X400-CallingAddressError
X.400(88) channel 41320 41413 41454 41505 41517 41532 Unnecessary logging by the x400p1 channel Switch shutdown does not close inbound associations P1 Responder does not match single space and zero length password Initiator leaks file handles when recovery enabled Permanent association does not detect remote MTA failure Dynamic multicast announce fails if multicasts loopback
5.2.3. MConsole
General 41535 41671 Text for Switch failedAssoc and rejectedAssoc counts is wrong MConsole cannot display messages sorted in priority order
5.2.4. Audit Database

General 41645 Malformed quoting in SQL statements
5.2.5. Switch Operational Management Client

C library for SOM 41667 41690 Memory leak from SOM Queue Manager interface Memory leaks when SOMSessionCreate/Delete called more then 20 times
5.2.6. X.400 P1/P3/P7 APIs

Java bindings 41695 isode-x400.jar is being mis-built on Linux
Isode R14.2 Release Notes Common 41471 41599 41606 41639 41701 Xuxa doesn't start when not installed on non-default paths on Windows Cannot get originator-requested-alternate-recipient from MT envelope Content decode failure can lead to duplicate memory free The X400api Makefile.sdk is out of date. Fetching strings from redirection history object may result in a crash
29
X.400 P7 and P3 41558 Does not work with Marben MS
5.2.7. Open Group APIs

GENERIC 41677 XMT 41468 41649 41651 41663 example XMT apps include internal isode header Transfer in and out of large message is very slow Minor memory leaks Trace not generated correctly on transfer-in via XMT xomExtra header file still not right for example programs
Syntaxes 41458 41585 41637 Cannot decode ADATP3 bodypart with line-orientated data Cannot encode ForwardedContentBodypart containing GeneralContent Bad Sensitivity value encoded in IPM Heading
5.3. M-Store X.400

5.3.1. Message Store
Other 41604 41614 Memory error in ms_upgrade program Memory error in ms_upgrade
attrib-library 41646 41647 Cannot generate id-hat-this-ipm attribute Store crashes when trying to retrieve content attributes from P22 message
DB library 41648 Transaction file recovery does not work properly
Message delivery library 41573 Store leaks file handles when out of disk space
Directory interface library 41481 Cannot bind as user added while Store is running
Isode R14.2 Release Notes P7 server 41500 41545 41546 41556 41567 41613 41619 41678 Store does not generate NRNs on message deletion Need mechanism for configuring AgentX contact mechanism pumice build depends on license.h RegisterMS operation cannot save AutoAction Registration in Directory Delayed autoforwarding autoaction is not implemented Failure to store submitted message mishandled P7server imposes hard limit of 400 P7 connections Message Store blocks on LDAP lookups during Bind operation
30
5.3.2. M-Store console

General 41541 41608 41652 41654 MS backup and restore scripts do not work when -a flag specified xmsconsole crashes when large number of mailboxes are configured Tcl error written to stderr when using XMSconsole Connections folder does not close properly
5.4. M-Box
5.4.1. IMAP/POP/LMTP Message Store
IMAP server 41469 41486 41533 41626 41631 41672 41681 41685 COMPRESS with unknown algorithm may crash imapd. imapd parent is restarting crashed imapd during shutdown IMAP interoperability problem with Apple Mail.app 3.0 QRESYNC stalls when change list is long Cache loading code is not sufficiently resilient to cache record corruption Some valid search criteria are rejected by IMAP SEARCH command Group parsing fails in some cases Junk after STATUS command causes two tagged responses
mclient/libimap4cli 41491 IMAP migration can mark all messages as read (\Seen)
LMTP server 41370 41467 41479 41498 41590 41666 Delivering multiple messages crashes lmtp on Windows Memory leaked when an event is freed LMTP crash on disconnect LMTP error logging is not sufficient LMTP might not recognize end of DATA command in some cases Sieve fileinto to a non-US-ASCII mailbox doesn't work
ms_syncd service and related libraries 41466 ms_syncd crashes on Windows when used with POP3 backend
Isode R14.2 Release Notes 41507 41512 41549 Migration leaves users in migration state, not active. msadm migrate/ms_syncd should canonicalize the supplied username Segfault in ms_syncd when protocol logging is enabled
31
SIEVE server 41544 putscript of active script returns OK but doesn't replace active script
libsasl and its plugins 41526 msadm del can't delete users in certain LDAPDB configurations
Common libraries 41497 41630 Special characters in passwords unrecognized Error in unpack_uint64() function can result in corrupted cache values for INTERNALDATE and Sent date
Mbox documentation (manual, man pages) 41679 fetch *:1 doesn't return anything
libms_utils library (configuration [LDAP,XML], SASL, TLS) 41612 41635 Double call to close causes imapd and pop3d to crash on windows Two threads can select the same temporary cache file name
mbox.exe service management utility (Windows) 41656 mbox.exe disable/enable is not working
Mdir mail volume driver 41478 41564 41587 41659 41682 41692 simultaneous uid allocations can result in the same uid being allocated LMTP server should be able to deliver mail to partially created mailboxes Failed to rename mmapped files on SMB file-store Quota usage information is lost under load RECENT report incorrect when all messages are recent imapd can run out of memory when FETCHing big messages and use_mmap is set to false
msadm command line management tool 41416 41488 41511 41513 41518 41527 41534 41565 41576 41592 msadm list is not showing disabled accounts with no passwords msadm can't handle parameters (such as passwords) with spaces in batch mode msadm migrate doesn't support setting of arbitrary extra attributes "msadm du" should canonicalize username msadm del doesn't fully delete LDAP users msadm doesn't handle missing closing quote properly msadm add can partially fail when some extra attributes are specified msadm in batch mode should return line numbers A hardcoded limit on the number arguments accepted msadm batch mode line lenght limit is too low
Isode R14.2 Release Notes Issues related to M-Box packaging 41451 M-Box startup order is incorrect on redhat.
32
startup/shutdown scripts 41482 Annoying "failed to connect to (/var/run/mseventd)" error messages when stopping M-Box on Linux
5.4.2. Internet Messaging Administrator

Common 41521 Login doesn't work after first incorrect login try
5.5. General
5.5.1. Basic transport, tools, services etc
psap 41683 rtsap 1150 Incorrect encoding of recovered SCI in RTORQ and RTOAC PDUs Double-free in PConnResponse
servicemanager 41634 ISM can't find services starting with "Isode."
Session layer 41522 41621 41623 Can generate duplicate session connection identifiers Unexpected normal transport disconnect not reported as error Bad session TSDU negotiation on 64bit big-endian platforms
X.500 syntaxes 41509 41620 tsap 41503 41516 41566 Cannot do more than 0xFFFF transport connect / disconnect pairs Race condition on connection close can cause crash TNetWait waits for twice the period asked for EncryptedPassword syntax does not hash plaintext passwords Integer syntax does not have CANONOUT format
5.5.2. Packaging
Packages 41502 41627 41650 41704 Update release results in 2 installs Copyright/License incorrect Use of Eclipse libraries is uncredited Don't package Xuxa on Windows 64
33
5.5.3. SASL library

Plugins 41591 Use of NTLMv2 will cause crash

Release Notes r14

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Release Notes r14

Hochgeladen von

Copyright:

Verfügbare Formate

Isode R14.

Isode R14.2 Release Notes

2.1. M-Vault Family

2.2. M-Switch Family

2.3. M-Box Family

2.4. M-Link Family

2.5. Availability and Limitations

3. Platform and Version Support

Isode R14.2 Release Notes R11.5 (since October 2007)

3.2. Supported Platforms

3.3. Supported Platforms (Future Releases)

3.4. Cryptographically Secure Source of Random Data

Isode R14.2 Release Notes

3.7. External Dependencies

3.7.3. Audit Database Dependencies

4.1. From R11 to R14.2v0

Isode R14.2 Release Notes Section 4.5.44, Redeploying Web Applications

If M-Box is installed, follow this additional step:

Isode R14.2 Release Notes 6. 7. 8. 9. Section 4.5.12, Uninstall M-Box Service

4.2. From R12.0 to R14.2v0

Section 4.5.13, Upgrade Linux Tcl, Tk and Tix packages

Isode R14.2 Release Notes

4.3. From R14.0 to R14.2v0

Section 4.5.39, Restart Linux Servers

If M-Box is installed, follow these additional steps:

Section 4.5.40, Restart Solaris Servers

4.4. From R14.1 to R14.2v0

Isode R14.2 Release Notes

4.5. Upgrade Steps

4.5.1. OSI Transport Providers

4.5.2. Empty the Message Queue

Isode R14.2 Release Notes 2.

4.5.3. Find Old GDAMs

4.5.4. Find All GDAMs

4.5.5. Stop Linux programs

If M-Box is installed, run:

If M-Switch is installed, run:

If M-Vault is installed, run:

4.5.6. Stop Solaris programs

Isode R14.2 Release Notes 1. If M-Store X.400 is installed, run:

If M-Box is installed, run:

If M-Switch is installed, run:

If M-Vault is installed, run:

4.5.7. Stop Solaris services

If M-Box is installed, run:

If M-Switch is installed, run:

If M-Vault is installed, run:

4.5.8. Stop HP-UX programs

If M-Switch is installed, run:

If M-Vault is installed, run:

Isode R14.2 Release Notes

4.5.9. Stop Windows programs

4.5.10. Prepare High-Performance GDAMs on Windows

4.5.11. Prepare GDAMs for Upgrade

Make sure there are no uncheckpointed transactions. Run the command:

Isode R14.2 Release Notes

4.5.12. Uninstall M-Box Service

4.5.13. Upgrade Linux Tcl, Tk and Tix packages

4.5.14. Upgrade Solaris Tcl, Tk and Tix packages

Install each new package:

4.5.15. Upgrade HP-UX Tcl, Tk and Tix packages

Install each new package:

Alternatively, sam(1M) can be used.