release notes r14

Isode R14.2 Release Notes 1

Isode R14.2 Release NotesIsode

Copyright © 2008 Isode Limited, London, U.K.

1. IntroductionRelease 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 associat-ed 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 up-grade. Otherwise, you may lose data or have an unusable system.

2. New FeaturesThis 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 M-Vault.

• 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 ac-counts 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. “[email protected]”) support is added.

• Core elements of configuration management are now accessible in MConsole’s “Switch View”. Currently this sup-port is read-only.

http://www.isode.com/products/


• 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 ofM-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. IfCustom 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)


• 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 Isodeproducts 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 arefully 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 sup-plier. This can be important for the security of your system. Isode reserves the right not to support a system which is notup to date.

On Solaris it is necessary to have the latest patched version of Sun’s C++ run time libraries. The latest patch number is119963-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 usknow 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 onUnix 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 wherepossible, 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.

http://software.hp.com/


Neither Solaris, Linux nor Microsoft Windows require any additional operating-system patches relating to cryptograph-ic 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 <[email protected]>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, Tk8.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 thefollowing components of the Isode packages. If you do not require these components then you do not need to install Ja-va.

On HP-UX you must download HP’s JRE/JDK implementation. On all other platforms Isode recommend you downloadeither JDK 5 (1.5) or JDK 6 (1.6) from the Sun website (see http://java.sun.com/javase/downloads/). Note that 64-bit in-stallations require a 64-bit JRE.

The default JRE on Red Hat Linux (gcj) does not work. IBM’s JRE also does not work.

• DConsole, Sodium, MConsole: These applications require that a suitable Java Runtime Environment (JRE) has beeninstalled, and that (on Solaris, Linux and HP-UX) it is earlier in the PATH than any other directory containing a javaexecutable.

• 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 aJDK (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 mustensure 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/.

http://www.isode.com/support/docs.html

http://java.sun.com/javase/downloads/

http://jakarta.apache.org/tomcat/

http://jakarta.apache.org/tomcat/

http://www.postgresql.org/


• 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 “Devel-opment” 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. UpgradingFollow 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:

• Section 4.5.1, “OSI Transport Providers”

2. 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. Section 4.5.5, “Stop Linux programs”


• Section 4.5.11, “Prepare GDAMs for Upgrade”

6. Section 4.5.13, “Upgrade Linux Tcl, Tk and Tix packages”

7. Section 4.5.17, “Upgrade Linux Packages”

8. If M-Vault is installed, follow these additional steps:

a. Section 4.5.23, “Schema Check”

b. Section 4.5.24, “Upgrading DSA GDAMs”

c. Section 4.5.25, “Rebuild All Indexes”

d. Section 4.5.27, “Restart M-Vault on Linux”

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

a. Section 4.5.31, “msg_track.db Change”

b. Section 4.5.32, “ms_sync.xml Change”

10. If M-Switch is installed, follow these additional steps:

a. Section 4.5.34, “Upgrade M-Switch Configuration”

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

http://www.postgresql.org/

http://pgfoundry.org/projects/pgtcl/

http://pgfoundry.org/projects/pgtcl/


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







4. Section 4.5.6, “Stop Solaris programs”



6. Section 4.5.14, “Upgrade Solaris Tcl, Tk and Tix packages”

7. Section 4.5.18, “Upgrade Solaris Packages”





d. Section 4.5.28, “Restart M-Vault on Solaris”










12. Section 4.5.40, “Restart Solaris Servers”






4.1.3. HP-UX





3. Section 4.5.8, “Stop HP-UX programs”



5. Section 4.5.15, “Upgrade HP-UX Tcl, Tk and Tix packages”

6. Section 4.5.19, “Upgrade HP-UX Packages”





d. Section 4.5.29, “Restart M-Vault on HP-UX”







10. Section 4.5.41, “Restart HP-UX Servers”





4.1.4. Windows





3. Section 4.5.9, “Stop Windows programs”



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


• Section 4.5.12, “Uninstall M-Box Service”

6. Section 4.5.16, “Upgrade Windows Tcl, Tk and Tix packages”

7. Section 4.5.20, “Upgrade Windows Packages”

8. Section 4.5.22, “Recreate Windows Services”





d. Section 4.5.30, “Restart M-Vault on Windows”




c. Section 4.5.33, “Restart M-Box Windows Service”







13. Section 4.5.42, “Restart Windows Services”





4.2. From R12.0 to R14.2v0

4.2.1. Linux

















d. Section 4.5.27, “Restart M-Vault on Linux”















4.2.2. Solaris







4. Section 4.5.7, “Stop Solaris services”









d. Section 4.5.28, “Restart M-Vault on Solaris”
















4.2.3. HP-UX














d. Section 4.5.29, “Restart M-Vault on HP-UX”













4.2.4. Windows

















d. Section 4.5.30, “Restart M-Vault on Windows”

















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:







6. If M-Vault is being used with the old qbDiskGdams, follow these steps:





• Section 4.5.27, “Restart M-Vault on Linux”







4.3.2. Solaris













• Section 4.5.28, “Restart M-Vault on Solaris”








4.3.3. HP-UX













• Section 4.5.29, “Restart M-Vault on HP-UX”




4.3.4. Windows

1. If M-Vault is being used, follow this additional step:

• Section 4.5.4, “Find All GDAMs”


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














• Section 4.5.30, “Restart M-Vault on Windows”








4.4. From R14.1 to R14.2v0

4.4.1. Linux




a. Section 4.5.26, “Rebuild Integer Indexes”

b. Section 4.5.27, “Restart M-Vault on Linux”

4. If M-Store is installed, follow this additional step:

• Section 4.5.38, “Update M-Store Message Index Entries”




4.4.2. Solaris





b. Section 4.5.28, “Restart M-Vault on Solaris”







4.4.3. HP-UX





b. Section 4.5.29, “Restart M-Vault on HP-UX”






4.4.4. Windows


2. Section 4.5.21, “Upgrade R14.1 Windows Packages”



b. Section 4.5.30, “Restart M-Vault on Windows”




• Section 4.5.33, “Restart M-Box Windows Service”




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 areoften 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 ofyour /etc/isode/isotailor file. (If you have no isotailor file, then you are not using a non-TCP OSI transportprovider).

4.5.2. Empty the Message Queue

1. Disable the inbound channels, which will cause the MTA’s message queue to empty. Stopping the smtpsrvr and/or iaed processes (for Internet or X.400 MTAs respectively) does this.


2. In addition any XMT or Isode Gateway client should have their outbound sides (i.e. transferring messages into theMTA) 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 isbeing used. Upgrading from previous releases requires that the following steps are performed carefully in order to avoidthe 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 databasefrom 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. Connect EDM to each DSA.

2. Select each old GDAM and choose Database properties.... Write down (e.g. on paper, or in a text file) the value ofeach GDAM’s 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 upprior to upgrading.


1. Connect EDM to each DSA.

2. Select each GDAM and choose Database properties.... Write down (e.g. on paper, or in a text file) the value ofeach GDAM’s 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




# /etc/init.d/pumice stop


# /etc/init.d/mbox stop


# /etc/init.d/pp stop


# /etc/init.d/eddy stop

4.5.7. Stop Solaris services



# svcadm disable -t pumice


# svcadm disable -t mbox


# svcadm disable -t pp


# svcadm disable -t eddy

4.5.8. Stop HP-UX programs



# /sbin/pumice stop


# /sbin/pp stop


# /sbin/eddy stop


4.5.9. Stop Windows programs


1. Run Isode Service Manager.

2. Select Service → Stop all. Wait for the services to stop.

3. 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 upprior to upgrading.


• 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 isbeing used. Upgrading from previous releases requires that the following steps are performed carefully in order to avoidthe 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 databasefrom backup. Therefore it is critical that you take a backup.


1. Perform a full backup of the DSA (not an incremental backup which just copies newer transaction logs).

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


# 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 M-Box 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# ...


# 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. Remove the previous Isode “TclTkTix” package using Control Panel → Add/Remove Programs.

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


4.5.18. Upgrade Solaris Packages


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


# pkgadd -d ./ISDbase-*pkg all# pkgadd -d ./ISDtps-*pkg all# ...

4.5.19. Upgrade HP-UX Packages


# swremove ISDbase# swremove ISDtps# ...


# swinstall -s `pwd`/ISDbase-*depot '*'# swinstall -s `pwd`/ISDtps-*depot '*'# ...

Alternatively, sam(1M) can be used.

4.5.20. Upgrade Windows Packages

1. Remove the previous Isode packages using Control Panel → Add/Remove Programs.

2. We recommend running regedit.exe and manually removing any references to previous Isode installations in thevalues 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


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


4.5.23. Schema Check

The directory schema has been changed and extended since R12.0. In particular, new object classes have been addedthat are required by the new database implementation. If you have made local changes to the default OID tables thenyou should ensure that the new object class bAGdam copied across before upgrading.

If you’re using the EncryptedPassword syntax then you should check that any newly installed OID tables are appro-priately 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 pack-ages you should run the dsaupgrade script. This upgrades the DSA in-place to the new high-performance database for-mat.

dsaupgrade -D dsa-directory -u dsa-manager-dn [-v] [-l log-directory] [-b backup-directory]

Where:

-D dsa-directory

The location of the DSA’s directory on disk; i.e. the directory containing the dse.db file.

-u dsa-manager-dn

The DSA Manager’s 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 ifthe -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 startthe 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 beremoved 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:


# /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


2. Select the Isode M-Vault service.

3. 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_idattribute is now called backend_id.

4.5.33. Restart M-Box Windows Service

1. Choose Start → Programs → Isode R14.2 → Services → Install M-Box services.

2. 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 MIXERgateways. If your configuration has been altered from the standard configurations, please make a copy of your mtatailorfile (in /etc/isode/switch/mtatailor or C:\Isode\etc\switch\mtatailor). As documentation of the con-figuration mechanism is not yet available, you are advised to contact Isode Support prior to your upgrade, sending yourcurrent mtatailor file. This should not be necessary for a simple X.400 or Internet M-Switch system, as the configura-tion will be upgraded appropriately.

You must do the following after installing the packages:

• Run EMMA.

a. Follow the upgrade instructions.

b. For each non-external MTA:

i. Right-click and create a stub MTA tailor file.


ii. Move the created stub file to C:\Isode\etc\switch or /etc/isode/switch on the system runningthe 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 (EX-ECDIR)/sendmail, which is usually “pp”.

4.5.36. Upgrade M-Store Configuration

1. Run EMMA.

2. 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 ver-sion of M-Store X.400.

As documentation of the upgrade mechanism is not yet available, you are advised to contact Isode Support prior to yourupgrade.

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


# /etc/rc.d/init.d/pumice start


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


# /etc/rc.d/init.d/pp start

4.5.40. Restart Solaris Servers


# svcadm enable pumice


# svcadm enable mbox



# svcadm enable pp

4.5.41. Restart HP-UX Servers


# /sbin/pumice start


# /sbin/pp start

4.5.42. Restart Windows Services


2. 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_databasescripts 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 thenisode/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. Stop Tomcat.

2. Stop all applications using the audit database.

3. Remove the old webapps (both the .war files and the deployed directories with the same name with the war ex-tension.)

4. Copy the new webapps from /opt/isode/lib/java/webapps into the Tomcat webapps directory.

5. Copy the classes from /opt/isode/lib/java/classes/*.jar into the Tomcat common/lib directory.

6. On Windows, you must ensure that the Isode bin directory (typically C:\Program Files\Isode\bin) is in-cluded in the PATH setting for the Tomcat process. The Isode web applications rely on this in order to be able towork properly.

7. Finally, restart Tomcat.

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


High-Performance GDAM

41475 Glue entries created between DSA and initial naming context

41540 Index test (man 043) UNRESOLVED on Linux - DSA test suit

41551 DB errors not logged with sufficient detail.

41553 Name lock error reported after total update processing in consumer

41559 Look through limits are not honoured.

41569 certain search filters can cause DSA crash on Windows

41570 DSA crashes when attempting to read entries that contain "audio" attributes

41572 Searches fail if filter contains substrings shorter than index supported length.

41588 bagdam doesn't properly honour "group of names" ACIs

41594 Filters containing ORs do not return all results

41595 Access controls from inner areas ignored in searches

41596 Dbulk uses excessive memory when loading to a BAG database

41615 ModifyDN not handled correctly in consumer

41616 BAG doesn't support support subtype matching as was allowed in old database

41628 dsbdmkindex doesn't create multiple indexes for an attribute

41665 Empty attributes can remain in cache after remove values in incremental update

41673 modifydn operations that should return "already exists" return "naming violation"

41688 DSA leaks file handles with file-based attributes

41693 DSA core dump if index operation in progress when DSA is shut down

Bulk loading tools

41529 dsaupgrade ignores the -l flag

41674 DSA upgrade leaves bogus entries in shadow changelog database.

Chaining

41618 Failed DSP Associations never get retried

edmsh

41506 dmi modify does not call editors correctly on Windows

LDAP interface

41548 LDAP connections are logged with an incorrect IP address

41589 LDAP client sending broken server-side sort request may cause DSA to segfault

41609 Bad PasswdModify operation values aren't rejected properly

Management

41625 SNMP logs hostnames not IP addresses.

Security

41550 Configuring CRL checking for M-Vault fails and disables any subsequent strong authentication

41603 TLS cipher suite choice is not restricted by DSA server settings

41622 EntryACI ignored in browsing DIT

41640 Setting pwdConfiguredSchemeGenerators to "cleartext" crashes DSA


Shadowing

41554 Shadow ModifyDN operations sent by R14 DSAs fail in pre-R14 consumers.

41571 R14.1 incremental applier is not forgiving of replayed modify operations.

5.1.2. Sodium ADUA

General

41274 RDN editor thinks that RDNs match when they differ in case/whitespace

41461 Sodium crashes during LDIF load over DAP when input data is invalid

41472 Sync mapping <add> action when conditional can fail due to syntax conversion

41489 A missing bind profile doesn't cause Sync to stop immediately

41490 Sodium Sync's mapping rules for AD don't handle proxyaddress

41538 CA entries using certificationAuthority are not displayed sensibly

41641 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 EMMA doesn't show synonyms and aliases when using OU naming policies

41455 Can't create users with White Pages

41480 Wrong DSA attributes used for P-MUL settings

41508 Can't create a new Message Store remotely

41515 Tcl error raiseds when trying to add an existing Routing Tree node

41519 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


5.2.2. Message Switch

822-local-channel

41040 822-local delivery on MIXER MTA has problems

General

4044 Unnecessary attributes and syntaxes defined

Other

41477 shutdown script on hpux ignores SWITCH_PROGS_TO_KILL

Checker formatter

41539 Cannot interface to ClamAV on Windows

41653 FD leakage and FD accessed after close in uudecoding

Housekeeper channel

41487 M-Switch generates an invalid DSN

41578 Housekeeper channel can generate bad DR if given Probe which has content-return set

Lists channel

41453 List channel generates wrong Non Delivery Report Diagnostic

41523 Processing multiple DRs though single list channel instance can cause error

mhsmime-formatter

41504 The IPN to DSN mapping generated by MIXER doesn't comply to RFC 2156

qmgr

41456 qmgr does not log to mlogd

41552 Handles leaked when Qmgr starts channel process

41560 Rerouting not displayed when rerouted MTA not available

41561 Groups not reassigned when rerouting changes on MTA config reload

41563 Message stats decremented incorrectly on submission failure

41574 Break in SOM connection while returning data can lock MTA or message

41670 Setting maximum connections to MTA does not disable auto tuning

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 slmtp core dump

41531 DATA failure results in subsequent messages on same connection failing

41536 Failure to open connection to second address for host can cause crash


SMTP server

41660 Server can block on DNS forward lookup check

Submission library

41575 Confusing DRR+DRD when message sizelimit exceeded

41584 Timout interval for Probes not configurable

41605 Sets incorrect content-type for reports

41657 alternate-receipient-allowed always defaults to TRUE

41658 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 Unnecessary logging by the x400p1 channel

41413 Switch shutdown does not close inbound associations

41454 P1 Responder does not match single space and zero length password

41505 Initiator leaks file handles when recovery enabled

41517 Permanent association does not detect remote MTA failure

41532 Dynamic multicast announce fails if multicasts loopback

5.2.3. MConsole

General

41535 Text for Switch failedAssoc and rejectedAssoc counts is wrong

41671 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 Memory leak from SOM Queue Manager interface

41690 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


Common

41471 Xuxa doesn't start when not installed on non-default paths on Windows

41599 Cannot get originator-requested-alternate-recipient from MT envelope

41606 Content decode failure can lead to duplicate memory free

41639 The X400api Makefile.sdk is out of date.

41701 Fetching strings from redirection history object may result in a crash

X.400 P7 and P3

41558 Does not work with Marben MS

5.2.7. Open Group APIs

GENERIC

41677 xomExtra header file still not right for example programs

XMT

41468 example XMT apps include internal isode header

41649 Transfer in and out of large message is very slow

41651 Minor memory leaks

41663 Trace not generated correctly on transfer-in via XMT

Syntaxes

41458 Cannot decode ADATP3 bodypart with line-orientated data

41585 Cannot encode ForwardedContentBodypart containing GeneralContent

41637 Bad Sensitivity value encoded in IPM Heading

5.3. M-Store X.400

5.3.1. Message Store

Other

41604 Memory error in ms_upgrade program

41614 Memory error in ms_upgrade

attrib-library

41646 Cannot generate id-hat-this-ipm attribute

41647 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


P7 server

41500 Store does not generate NRNs on message deletion

41545 Need mechanism for configuring AgentX contact mechanism

41546 pumice build depends on license.h

41556 RegisterMS operation cannot save AutoAction Registration in Directory

41567 Delayed autoforwarding autoaction is not implemented

41613 Failure to store submitted message mishandled

41619 P7server imposes hard limit of 400 P7 connections

41678 Message Store blocks on LDAP lookups during Bind operation

5.3.2. M-Store console

General

41541 MS backup and restore scripts do not work when -a flag specified

41608 xmsconsole crashes when large number of mailboxes are configured

41652 Tcl error written to stderr when using XMSconsole

41654 Connections folder does not close properly

5.4. M-Box

5.4.1. IMAP/POP/LMTP Message Store

IMAP server

41469 COMPRESS with unknown algorithm may crash imapd.

41486 imapd parent is restarting crashed imapd during shutdown

41533 IMAP interoperability problem with Apple Mail.app 3.0

41626 QRESYNC stalls when change list is long

41631 Cache loading code is not sufficiently resilient to cache record corruption

41672 Some valid search criteria are rejected by IMAP SEARCH command

41681 Group parsing fails in some cases

41685 Junk after STATUS command causes two tagged responses

mclient/libimap4cli

41491 IMAP migration can mark all messages as read (\Seen)

LMTP server

41370 Delivering multiple messages crashes lmtp on Windows

41467 Memory leaked when an event is freed

41479 LMTP crash on disconnect

41498 LMTP error logging is not sufficient

41590 LMTP might not recognize end of DATA command in some cases

41666 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


41507 Migration leaves users in migration state, not active.

41512 msadm migrate/ms_syncd should canonicalize the supplied username

41549 Segfault in ms_syncd when protocol logging is enabled

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 Special characters in passwords unrecognized

41630 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 Double call to close causes imapd and pop3d to crash on windows

41635 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 simultaneous uid allocations can result in the same uid being allocated

41564 LMTP server should be able to deliver mail to partially created mailboxes

41587 Failed to rename mmapped files on SMB file-store

41659 Quota usage information is lost under load

41682 RECENT report incorrect when all messages are recent

41692 imapd can run out of memory when FETCHing big messages and use_mmap is set to false

msadm command line management tool

41416 msadm list is not showing disabled accounts with no passwords

41488 msadm can't handle parameters (such as passwords) with spaces in batch mode

41511 msadm migrate doesn't support setting of arbitrary extra attributes

41513 "msadm du" should canonicalize username

41518 msadm del doesn't fully delete LDAP users

41527 msadm doesn't handle missing closing quote properly

41534 msadm add can partially fail when some extra attributes are specified

41565 msadm in batch mode should return line numbers

41576 A hardcoded limit on the number arguments accepted

41592 msadm batch mode line lenght limit is too low


Issues related to M-Box packaging

41451 M-Box startup order is incorrect on redhat.

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 Double-free in PConnResponse

rtsap

1150 Incorrect encoding of recovered SCI in RTORQ and RTOAC PDUs

servicemanager

41634 ISM can't find services starting with "Isode."

Session layer

41522 Can generate duplicate session connection identifiers

41621 Unexpected normal transport disconnect not reported as error

41623 Bad session TSDU negotiation on 64bit big-endian platforms

X.500 syntaxes

41509 EncryptedPassword syntax does not hash plaintext passwords

41620 Integer syntax does not have CANONOUT format

tsap

41503 Cannot do more than 0xFFFF transport connect / disconnect pairs

41516 Race condition on connection close can cause crash

41566 TNetWait waits for twice the period asked for

5.5.2. Packaging

Packages

41502 Update release results in 2 installs

41627 Copyright/License incorrect

41650 Use of Eclipse libraries is uncredited

41704 Don't package Xuxa on Windows 64


5.5.3. SASL library

Plugins

41591 Use of NTLMv2 will cause crash

release notes r14

Documents