Release Notes

List of the major milestones and releases of Enkive. There is no set release schedule. Both major and minor releases occur when our development, and that of the community improve the software significantly. If you have features that you need, please contact us -- and we can tell you when that is likely to be included in an upcoming release. If you really need a feature, we would be happy to develop any feature necessary to make this product valuable for you.

March 17, 2015 -- Release 1.4.2

  • Bug 40 - Fixed issue in which emails without a Content-Transfer-Encoding field in the header would not be archived.

March 3, 2015 -- Release 1.4.1 final

  • Bug 29 - Fixed issue with IMAP retrieving incorrect emails
  • Bug 28 - Fixed indexing exceptions with later version of Apache Tika (1.6)
  • Bug 24 - Fixed mbox exports
  • Makes sure locale is correct
  • Paging fixes
  • Data storage location (i.e., docstore) is configurable
  • Fixed Enkive version check if enkive.org website is down
  • Email that is queued to be indexed at shutdown is now re-queued at startup

March 6, 2014 -- Release 1.4 final

  • Minor bug fixes

January 13, 2014 -- Release 1.4 RC2 Features

  • Sort order bug fix
    There was a bug in sort order for sorting by date, that resulted in dates near each other being in the wrong order. This is fixed, and dates sort correctly.
  • UI theming bug fix for paged results
    Paged search results beyond the first page were not properly themed.
  • Large search improvements
    MongoDB has an inherent limit on the size of un-indexed search results. When sorting a large search by a non-default key (e.g. date), this limit triggered, causing a Java backtrace to be displayed. The error is now a nice, user-understandable message. The results can now be paged up until the MongoDB limit is reached (rather than an immediate failure on sorting).
  • Improved init scripts
    Upstart for Ubuntu
    Proper sysv-init for Debian
  • New DocumentStore for attachments
    For datasets with lots of attachments or large attachments, the limitations of MongoDB's GridFS were causing unacceptable performance. Since the trend is more mail with larger attachments, this needed to be addressed. A new document store was created that stores documents in the filesystem, indexed by MongoDB rather than in MongoDB directly. This resulted in a 5X speedup in document processing (and hence import).

November 4, 2013 -- Release 1.4 RC1 Features

  • IMAP search
    The experimental IMAP support has been removed, and replaced with the ability to export searches via IMAP.
    Any search can be tagged as being an IMAP search, and will then show up as a folder when the user connects via IMAP.
    IMAP searches periodically update in the background, so they are never out-of-date
  • Search Update
    Searches can be updated clicking on the Update button on the search results page.
    This will update the search for new mail that has been archived since it was last run.
  • Update Version Check
    Enkive will periodically (by default every 2 weeks) check to see if there is a newer version.
    This can be configured or disabled.
  • Turnkey
    There is a Turnkey available with Enkive 1.4 pre-installed.
    It can be used for evaluation or as a basis for a full installation.
    It's based on Debian Squeeze.
  • Email Processing Performance
    Email processing has been optimized to achieve a 400% improvement in processing speed.
    This means that a higher volume of email can be archived on the same hardware, and that import performance is greatly improved.
  • Bugzilla bugs fixed:
    7, 15, 17, 19, 20

September 12, 2013 -- Release 1.3.1 Features

Here's what's changed in 1.3.1 since 1.3:

  • Fixed Bug 21 - Exchange Journalling results in two archives per email
  • Add the ability to poll for mail from a mail server
    - In addition to the Enkive Postfix filter, Enkive can now poll for
    mail from a mailbox (either IMAP or POP3) on a mail server. This can
    integrate with server-based journalling accounts.
  • Handle RFC 5987 encoded UTF-8 attachment filenames
    - Before, UTF-8 encoded filenames for attachments were ignored by the
    UI, causing those attachments to download as "attachment-#". Now,
    they are properly parsed, resulting in the correct attachment names
    showing in the UI.
  • Warnings fixes
  • Update to the newest Apache James and MongoDB versions

June 20th, 2013 -- Release 1.3 Features

  • Attachments downloaded through the web interface are in their original binary form (rather than in their encoded form). File names of attachments are maintained in many cases.
  • Significant improvement on authentication against LDAP and Active Directory. Other improvements on file-based authentication.
  • Improvements in IMAP access to user's archived email.
  • The ability to normalize email addresses according to various rules has been added to create additional flexibility.
  • Improved mechanism for database migrations to make future upgrades easier.
  • Additional scripts/tools in the scripts directory including enkive-migration-tool.sh and mongodb-index-tool.sh
  • Scripts/tools that had previously broken when supplied with relative paths can now use relative paths.
  • Fixed several bugs in Enkive query setup and execution which previously caused incorrect results to be returned
  • Fixed a bug in the statistics database. Unfortunately previous statistics history will be lost.
  • If certain expected data directories do not exist, Enkive will attempt to create them.
  • Component libraries have been upgraded.
  • Changes to fix hangs on shutdown.
  • Internal locking fixes.
  • Browser fix when downloading attachment file names with spaces.
  • Efficiency in many parts of the code has been improved. Various bugs have been eliminated.

October 4, 2012 -- Release 1.2 Features

  • IMAP Access A major new feature in the 1.2 release is the ability to browse the archive over IMAP. This means that you can use any imap capable client to connect to Enkive and browse through your archived messages by date. This feature is currently limited to browsing and has only been tested on a few clients, but please provide feedback as we'd like to make it more robust in release 1.4
  • StatisticsThis release includes a new page in the administration section of Enkive that displays statistics. From this page you can see things like the total size of your archive, how many messages are received per day, and many more statistics.
  • Interface updates This release of Enkive also has a few minor updates to the search interface. Search results are now sortable by using the arrows in the column labels.
  • Bug FixesEasier Installation. We've fixed a bug in the start up script that gave many users some trouble. The issue is described here: http://www.enkive.org/pipermail/users/2012-July/000019.html

June 7, 2012 -- Release 1.1 Features

  • Message Retention Policy The major new feature for Enkive 1.1 is the ability to set a retention policy for how long to keep messages in the archive. More about the message retention policy can be found on the message retention policy feature page
  • Mongo Administration Tool A simple administration tool for managing the Mongo Enkive database has been added. Currently this tool is just for ensuring all the proper mongodb indexes are in use, but this tool may be leveraged more in future releases of Enkive. Documentation for using this tool will be available at a later date.
  • Easier Installation The startup scripts we've shipped provide some helpful feedback when startup succeed, making installation and setup a little easier.
  • Search Interface Searching on email address fields are now case insensitive. Latest date searches now search until 11:59pm of that day, not 12:00am of that day For example, searching for messages from July 1st, 2011 to July 1st, 2011 will return all messages in the archive for July 1st, 2011. Previously this would return no messages.
  • Backend Changes The most notable change to the backend is the arrangement of spring configuration files. With the 1.0 release, all spring configuration was in a single file, enkive-server.xml. Spring has now been configured to use several files, making things a little easier for development and configuration of spring.

February 29, 2012 -- Release 1.0 features

  • Enkive 1.0 is the result of a significant re-architecting effort that reduced the memory footprint and increased the speed of archival and retrieval by orders of magnitude. This, in turn, offers increased flexibility in terms of hardware requirements. Furthermore, the new architecture positions Enkive so that future versions can run on clusters and in the cloud. Last but not least, it simplified the installation and configuration process.
    We achieved these results in part by transitioning from an Alfresco storage and
    indexing back-end, to a new custom storage and indexing system. Storage and indexing are now abstract processes in Enkive. For Enkive 1.0, the indexing engine is Indri (UMass) and the object storage engine is MongoDB. Both are open source.
  • Enkive 1.0 includes tools for seamless migration from the prior release of the software.
  • Self Service: In this release we turned on the ability of users to search their own emails in the archive
  • The features that were included in the previous releases are described on the bottom of this page

August 2011 Release 0.8 features

  • Attachment Download links while viewing a message
  • Enhanced message filtering support

February 27, 2011 -- Release 0.7 features

  • Vastly improved search and display
  • Preliminary multi-user (workspace) support
  • Search control

January 3, 2011 -- Release 0.6.1 features

  • JMX instrumentation to facilitate monitoring running Enkive
  • Ability to import messages in MBOX format

November 17, 2010 -- Release 0.6.0 features

  • Self-hosted (contact us for recommended hardware requirements)
  • Works in parallel with any SMTP email system, requiring no significant changes to the way the email system works
  • Configuration option to capture spam or exclude it
  • Automatic deduplication: retains only a single copy each of duplicate email messages and duplicate email attachments
  • Audit trail, viewable in web browser (System Administration tab)
  • eDiscovery: Search by message header information including sender, recipient, subject, dates
  • Full text search of content in the body of the message and many types of attachments
  • Search by message ID
  • Save searches
  • List and view recent searches and their results
  • List and view saved searches and their results
  • Export saved searches to an MBOX file, which can be imported into any MBOX-compatible email client (e.g., Mozilla Thunderbird)
  • Migration Facility: Import existing email into Enkive using Maildir format
  • WIKI: Help documentation (On line)
  • Only the Admin has access control to the archive