This release history for Message Classification includes the list of all releases along with new features and bugs that were fixed in each release.  

If you are a Message Classification customer that has purchased maintenance and support please email info@titus.com to request the most recent build.

Version 1.0

Ø      First version

Ø      Preconfigured classifications with one level of classification

Version 2.0

Ø      Customization available through the administration tool wizard.

Ø      Customization of the following:

·         classification tags

·         default tag

·         location of the tag in the body

·         the ability to include extra text at the bottom of the message

·         Ability to Force users to select a classification.

Ø      Registry values are now used to store customizations.

Version 2.1

Ø      Added the ability to place the classification in the subject field of a message.

Version 2.2

Ø      Second level of classification added.

Ø      Integration with Microsoft Windows Rights Management Services.

Version 2.3.0.22

Ø      Support provided for Microsoft Word as an email editor.

Ø      Support provided for the ‘Send To’ command from Windows Explorer, Internet Explorer etc.

Ø      Added an option to prevent or warn users about downgrading messages on replies or forwards.

Ø      Support provided for classification of Calendar appointments.

Ø      Classifications appear in printed hardcopies of emails.

Ø      Classification levels can now be displayed in the user’s Inbox by adding the classification columns in the Inbox, thus allowing the user to easily view the classification of the emails as well as sort messages by classification.

Ø      New Admin Tool GUI introduced.

Version 2.31.0.08

Ø      Support for subject tag abbreviation of classifications.

Ø      Support for text label formatting, allows the administrator to select the font, size and color.

Version 2.40.0.17

Ø      Support for Microsoft Windows Rights Management Services templates. Create an association between the second level of classification and RMS templates.

Ø      Support for RMS failure events.

Ø      Support to allow administrators to disable the Message Classification toolbar.

Ø      Support to allow for the enabling of the second classification level at or above a predefined first classification level.

Version 2.41.0.1 – Issues Resolved

Ø      Users are now able to edit a single occurrence of a recurring calendar appointment without getting a pop up dialog error.

Version 2.41.0.3 – Issues Resolved

Ø      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.41.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.6.0.18 – 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.

Ø      Pictures imbedded in emails no longer disappear when force classification is cancelled.

Ø      Comma's can now be included in classification tags.

Ø      Meeting requests that are forwarded by an attendee will now maintain their classification level.

Ø     Message Classification custom properties are no longer printed when a hard copy of the email is required. The categories are still printed below the subject line.

Version 2.6.0.21 – Issues Resolved

Ø      Fix for install problem when Message Classification V2.6 is installed on a Windows 2000 machine.

Ø      Fix for V2.6.0.18 which causes Outlook 2003 to crash on some machines when large messages are classified.

Version 2.6.0.27 – Issues Resolved

Ø      Fix for problem which causes Outlook to crash when using the Attachment Classification feature and sending multiple attachments.

Ø      Fix for problem when Message Classification is used in conjunction with the Symantec (KVS) Enterprise Vault. Outlook crashes when trying to classify a message which had been archived in the vault.

Ø      Fix for problem which occurs when trying to turn off calendar and task classification in a Citrix Terminal Server environment.

Version 2.6.0.29 – Issues Resolved

Ø      While using KVS as a mail archiving solution, a problem was fixed when a user replied to a message in a shared mailbox after an archived message had been opened in the users own mailbox.

Ø      Fixed a problem where the Help button was not fully visible in the classification dialog.

Ø      Saving / Sending meeting requests and task items no longer causes server errors when running with cached mode disabled in Outlook.

Ø      Fixed parsing of x-protective-header for Australian protective marking standard for interoperability with other classification clients.  The CAVEAT was not getting properly parsed in the previous build, now it is being read properly.

Version 2.61.7 – New Release

Ø      A new feature was added to disable the forced classification on the save of a message. When enabled, classifications will only be forced when the user sends the message, thus eliminating the prompt to classify the message on a save or auto save.

Ø      Attachment classification check can no longer be bypassed.

Ø      Cancelling out of force classification then saving your email to your drafts folder will no longer cause message contents to be lost.

Version 2.61.10 – Issues Resolved

Ø      The ORIGIN field has been added back into the Australian x-protective-marking header.

Ø      The drop down list in the classification tool bar has been increased from 8 to 15 lines. This will allow those using more classification levels to display each classification without the use of the scroll bar.

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.

Version 2.71.4 – New Release

Ø      Support for Outlook 2007 and Ribbon toolbar added.

Ø      Improvements were made in handling of attachments and imbedded objects in emails that are sent in Rich Text format.

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

Ø      For Outlook 2000 and 2002,  the "Send to" command (invoked from other Microsoft applications or from Windows Explorer) will no longer trigger Message Classification  if Outlook has not been launched. These emails will be sent without a classification tag. If Outlook is running, the emails will be classified.

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

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.