Skip to main content

5.5.9

Version published 2026/05/04​

Changelog published on 2026/05/04 - updated on 2026/05/11​

Update​

In version 5.5.8, an updater forced the resynchronization of all data modified through Outlook. In an environment with a large number of Outlook users, this resynchronization load could cause the server to become heavily overloaded. This is no longer the case as of version 5.5.9, which more precisely targets the data to be synchronized by limiting it to calendar events modified by Outlook over the past month.
For further information see the Jira ticket BM-23680.

  • BM-23656 : Fix: Make spool migration mandatory and prevent the deactivation of queries on the Cyrus spool if a cyrusspool-data-migration migration has failed or is still scheduled.
  • BM-23680: Fix: Apply PclRemediation only to calendar events created less than a month ago to prevent mass resynchronizations.

BlueMind Webmail (Mail App)​

  • BM-23542: Fixes: The message date appears unformatted in the print preview of an email.
  • BM-23634 : Fixes: The folder suggestion filter in the email move or copy dialog incorrectly excludes all folders with the same name even though they belong to a different mailbox.

Contacts​

  • BM-23029 : Fixes: The contents of an address book are not displayed in alphabetical order.

Thunderbird​

  • BM-23666: Fixes: The feature for importing contacts stored in Thunderbird's default address book prior to using the BlueMind connector no longer works in Thunderbird 78 once the connector is installed and that address book becomes the account's BlueMind address book.
  • Adds support for Thunderbird ESR 153.

Administration / Architecture​

Backup & restore​

  • BM-23599 : Fixes: Inconsistency in the configuration of the following values: Number of days for dual-bottom retention, Number of backups retained, Number of days for retention of deleted emails.
  • BM-23602: Fixes: An event's history is not bounded and can cause calendarHistory to grow indefinitely, which may result in OutOfMemoryError errors.
  • BM-23604 : Fix: Added a fallback solution that saves emails that cannot be found in backup folders during restoration.

bm-cli​

  • BM-23526 : Fixes: No results are returned when attempting to delete an email.

IMAP​

  • BM-22651 : Fixes: The response to a SEARCH command contains extra spaces.

kafka​

  • Fix: The creation of dirEntry ensured the consistency of organizational units, but this check was missing during the upgrade.
  • Fix: Ignore GROUP mailboxes and flat hierarchy nodes. This feature is rarely used and will be replaced in a future version. This issue may occur when cloning a version 5.6 to a version 5.5.
  • Fix: If there is a naming conflict between organizational units, rename the one that is "stealing" our name.
  • Fix: Restore resources using their internalId; otherwise, a subsequent upgrade to the topic could clear the calendar.

mapi​

  • BM-23636: Fixes: Handling of multi-valued TNEF variables causes the import of winmail.dat files to fail.

Migration​

  • FEATBL-3424: Feat: Support for new shared mailboxes in the ex-migration-tool
  • BM-23646 : Fix: ex-migration-tool, API keys not deleted

mmap​

  • New: Added the IWritableChunk.truncate() method — Clears all data written so far and resets the write position to zero without freeing the chunk. Allows for a smooth recovery when a streaming attempt fails during execution and a new attempt requires starting over from scratch without reallocating the address.

node​

  • BM-23673 : Fix: When data/by_hash is enabled on the processor, do not read email files from memory.

POP3​

  • BM-23669: Fixes: Emails not deleted via POP3 (incomplete byte-stuffing).

Object storage​

  • Fixes: "Chunk is released" access conflict when attempting to download zstd and the caller times out. Two separate access conflicts previously resulted in an IllegalStateException in the ZstdResponseTransformer pipeline.
  • Fixes: Thread leak in zstd-processing on exceptionOccurred in the AWS SDK. When the SDK reported errors via exceptionOccurred (instead of the Subscriber's onError), the decompProcess thread would remain blocked on PipedInputStream.read indefinitely—in production, thousands of zstd processing threads would accumulate.

Others​

  • BM-23468: Fixes: Deadlock when deleting a large number of conversations too quickly.