Isode's Harrier release is a Fully Supported Isode release of Harrier (see the Supported Releases page for more details).

Read on for the major changes that Harrier 3.0 introduced. Please note Harrier 3.0, has now been superceeded by Harrier 3.1

Separate Product

Prior to release 3.0, Harrier has been shipping as part of the messaging server release set (currently at R18.0).

Harrier 3.0 can be used with any version of the Isode messaging servers, noting the R18.0 is recommended, as this is needed to enable full Role support. Harrier 3.0 can also be used with Microsoft Exchange. *Please note that Microsoft Exchange functionality was removed in a later release. This statement is being kept for prosperitys sake. *

Role Support

Military Messaging uses Role-based mailboxes. Harrier makes use of directory-based role configuration, where each role can specify which users are allowed to occupy the role. Harrier will authenticate a user. If the user can only occupy one role, this role will be immediately assumed. Otherwise, the user will be given a choice of roles. This approach allows a role to be supported by multiple users, with independent audit of which user is performing actions undertaken by the role.

Harrier clearly displays both the role and the authenticated user.

Profiler Support

Support for message profiling, as provided by M-Switch Profiler to distribute messages based on content. Harrier will recognize messages that have been profiled and make this clear to the Harrier user. Harrier will provide information on the profiled message, in particular the full list of action and info recipients, which can be expanded or hidden as desired.

Action/Info Support

The distinction between action messages (for which the recipient is responsible) and info messages is a vital element of military messaging. Harrier 3.0 improves the UI to clearly distinguish between action and info messages in the scan listing and message display. This includes support for profiling (which has action and info recipients) and for military distribution lists where action and info membership of the list is distinguished. Harrier shows action/info status clearly, and where a message has been distributed by military distribution list or profiler.

Draft & Release and Organizational configuration in LDAP

Draft & Release configuration, as well as Organizational entries can now be stored in LDAP. Draft & Release configuration was also extended to support senders that can optionally use Draft & Release procedure.

SMTP submission on port 465

Harrier now support SMTP submission directly on TLS port (port 465) as specified in RFC 8314. This is in addition to SMTP submision on STARTTLS port (port 587), which was already supported.

Elliptic Curve key generation for S/MIME

Automatic CSR (Certificate Signing Request) generation now supports Elliptic Curve.