Isode R14.4: XUXA (Test & Demo X.400 User Agent) Features

This is the final message describing new features in Isode R14.4, scheduled to ship this week. You can see all of the messages on this blog relating to R14.4 by clicking on this link.

Isode provides XUXA as a test and demonstration X.400 client. This gives access via X.400 P3 or P7 to the capabilities of Isode's servers and APIs.  R14.4 contains a number of improvements including:

1. Demonstration of the new X.400 features, in particular message sequence integrity (needed for AMHS Security).

2. Ability to send and receive X.411 security labels.  A specific goal of this is to help test out M-Switch MIXER security label handling.
3. Probe improvements, to set message length and content type.
4. New logging tab to give easy access to log and error information.
5. Improved handling of messages with multiple body parts. Body parts can now be saved directly from the Body parts list.

We've also made a general improvement in support of Directory Names. X.400 OR Names comprise an OR Address and a Directory Name.   Older X.400 deployments primarily work on the basis of OR Address, and XUXA has used OR Addresses only. Use of OR Addresses is pragmatic, but has the disadvantage of containing the rather awkward ADMD and PRMD components.  Directory lookup is supported, but addresses are primarily handled as OR Addresses.   R14.4 adds a mode so that Directory Names can be used (or both, which looks rather ugly). This will help test out Directory Name based deployments.  Use of Directory Names allows a more natural naming structure and hiding the OR Addresses (as IP addresses are hidden by Internet email addresses), and also means that information on users, including capabilities can always be looked up.

In addition P772/STANAG 4406 Military Header "Message Type" is now correctly set and Displayed (previously this was GUI only), so there is now a working P772 header in addition to STANAG 4406 Priority (MTS). We may add UI support for other P772 capabilities (now fully supported in the underlying C and Java client APIs) in a future release and would welcome feedback on this.