This release history for Message
Classification Enterprise Edition includes the list of all
releases along with new features and bugs that were fixed in
each release.
If you are a Message Classification Enterprise Edition
customer who has purchased maintenance and support, please email
info@titus.com to request
the most recent build.
Version 2.5.0.24
Ø
Addition of third level of classification, which
allows for unlimited classification labels.
Ø
Support provided for dynamic labelling based on a
users membership in Active Directory groups.
Ø
Safe Recipient Lists, which checks to ensure that
the intended recipients have the appropriate permissions to
receive the email before it is sent.
Version 2.51.0.3 – Bugs fixed
Ø
Fixed problem relating to error message when
workstation or laptop is disconnected from Active Directory
Ø
RMS Template selection now functions for French
Outlook.
Ø
Messages that were delivered with SMTP headers
will now display the classification in the Inbox field chooser
so that the users are able to sort by classification levels.
Ø
Subject tag abbreviation works again for
classifications that are more than one word.
Ø
The send to email recipient from within Adobe
Acrobat will now maintain the body text of the message once it
is sent.
Version 2.51.0.10 – Additional features & Bugs fixed
Ø
Messages saved in the Drafts folder now retain the
classification level.
Ø
Subject tag can now be inserted both before and
after the subject of the email.
Ø
Lowercase characters with French accents will now
retain their classification levels on a reply or forward.
Ø
Saving a meeting request will no longer add
multiple classifications in the message body.
Ø The
Property name now supports the use of special characters, within
the limitations of Microsoft Office. The backslash, double
quotes and period are not supported.
Ø Outlook
no longer crashes when the assignee of a task uses Outlook today
to complete the task.
Ø
Warnings were occurring on the Exchange server
when the clients were running Outlook XP. The EventID of 8241
was being caused by Outlook not saving the meeting request
properly on a send. The issue has been fixed in this release and
these errors will no longer occur on the server.
Version 2.61.5 – Additional features
Ø
Australian Email Protective Marking standard
supported.
Ø
Classification events can now be added to the
Windows Event log.
Ø
Documents that have been classified using Titus
Labs Document Classification will automatically show their
classification when attached to an email message.
Ø
Classification Help feature added.
Ø
More flexible formatting of the classifications
that are added to the message body now possible.
Ø
Classification tags over 50 characters now
supported.
Ø
Support for three new custom properties allowing
the user to add extra metadata to each email sent. This includes
date field support.
Ø
Administrator can now configure automatic
encryption of message based on classification selected. Outlook
compatible encryption software required.
Ø
Commas can now be included in classification tags.
Version 2.61.13 – Issues Resolved
Ø
The Tool Tip for the Select button will now be displayed. In
earlier releases, the tool tip for the Select button was not
being displayed to the users when they hovered their mouse over
the button.
Ø
Extra classification meta data is no longer printed in the hard
copies of emails. Previously, if users made changes to the
classifications via the classification tool bar, when a hard
copy of the email was printed out, Outlook was inserting
redundant information regarding the classification of that
email. This redundant information has been removed from the
email printouts.
Ø
The use of the third custom property will no
longer insert an invalid date into the body of an email. If the
third custom property is enabled and a VBA formula was used to
control the output of that custom property in the body tag, it
was possible for the formula to return a string value in the
form of a date. This string value would then be placed into the
body of the message, confusing the recipients as to it's nature.
Ø
Fixed Outlook problem if the product was configured such
that the user's classification selections had gaps when compared
to the available tags. For example, if all the available level 1
tags were UNCLASSIFIED;CONFIDENTIAL;SECRET, and a user didn't
have the CONFIDENTIAL label in their selection, Outlook would
fail when they tried to send a message. Note that there is still
a restriction that the first classification selection in the
level 1 classifications needs to be common throughout the
organization.
Version 2.71.4 – New Release
Ø
Support for Outlook 2007 and Ribbon toolbar added.
Ø
A warning message can be configured to appear when an email is
sent at or above a certain classification level, or to more than
a predetermined number of users at a certain classification
level.
Ø
Emails sent to recipients outside of trusted domains can now be
blocked for specific classification levels.
Ø
Improvements were made in handling of attachments and imbedded
objects in emails that are sent in Rich Text format.
Ø
When custom properties are enabled and they contain a default
selection, it is now possible to configure Message
Classification to allow the email to be sent without prompting
the user for input.
Ø
The automatic population of categories in an email
can now be disabled.
Ø
Double byte characters are now supported in the
body and subject of the email. The email must be composed in
Rich Text format and the email editor must be Word.
Ø
An interaction issue with signed email was fixed. Issue involved
reading signed emails that were sent over POP/SMTP.
Ø
Outlook 2000 will no longer place the first two characters of
the email before the classification prefix in the body of the
email.
Version 2.71.12 – Issues Resolved
Ø
When using Word as your email editor and Rich Text as your email
format, the body tagging will no longer be inserted into the
middle of the body text of the message.
Ø
If only one level of classification is defined,
the body tag separator will no longer be included in the body
tag of the message.
Ø
Opaque-signed messages will no longer be TNEF encoded when they
are sent.
Ø
Parsing of the subject line classification has been restored in
order to maintain compliance to the Australian Governments email
protective marking standard.
Ø
The Trusted Domains feature now supports sending to addresses
in your personal contact list.
Ø
When using Word as your email editor with safe recipient lists
and event logging enabled, encountering a safe recipient warning
and selecting to remove the recipients who aren't cleared for
the message will no longer result in Outlook crashing.
Version 2.71.14 – New Release
Ø
Options for application of Microsoft Rights Management by
Message Classification has changed. The new implementation will
no longer remove RMS templates that have manually been applied
by the user. Users will now be able to manually apply an RMS
template to an email. The only situation in which user applied
RMS permissions will be changed occurs when Message
Classification is configured to apply a different template based
on the dropdown selections made by the user. When the user
attempts to send an email in this situation, they will be
warned that the Message Classification policy dictates that a
different RMS template will be applied to the message.
Ø
Custom Property 3 is now displaying the correct date when a
selection is made. The previous build was not mapping the
correct date to the defined configuration, instead today's date
was being inserted.
Ø
Support for VISTA and Exchange 2007 have now been added.
Ø
When a user opens and accepts a meeting request from a user who did not
set any classifications in the original meeting request,
Outlook will no longer crash. This bug most frequently
occurred when users accepted meeting requests from recipients
who are outside of their domain. When the user selects
the Outlook default of "Send message now",
when accepting the meeting request, Outlook
will no longer crash.
|
