BM-23783: Fixes: The ‘Destination folder’ field does not display selectable folders.
BM-24249: Fixes: The AI assistant panel remains open after deleting a draft in conversation mode.
BM-24275: Fixes: Unnecessary full resynchronisation of the domain directory every time the application is opened or a change is made, in every tab/browser window.
BM-24276: Fixes: Recipient autocomplete returns a truncated result: an existing contact does not appear in the list.
BM-24277: Fixes: Synchronisation does not resume after a network outage.
BM-24278: Fixes: Placeholders (grey blocks appearing in place of certain words) appearing in search results.
BM-24281: Fixes: Display flickering (appears/disappears/reappears) when opening an email.
BM-24148: Fixes: The encoding of emails converted from Outlook (TNEF) results in unreadable text (garbled characters) when received or sent.
Fixes: Crash when logging into a shared mailbox when an email folder is out of sync, triggering an automatic repair loop every time a session is opened.
Fixes: Loss of the name of a shared secondary calendar when added to Outlook.
Pexip meetings now support recurring and rescheduled events.
Fixes: The description of a meeting (including the connection link) is partially deleted when the template contains an unrecognised variable.
BM-24253: Simplification of the Pexip meeting link (removal of a superfluous parameter).
[Nextcloud Talk]: Fixes: Display of the label and help text for the ‘API base URL’ field in the administration console.
[Nextcloud Talk]: Fix: Calls to Microsoft Graph now go through a simple HTTP client (the 60 MB Microsoft Graph SDK has been removed from bm-core) and therefore use the HTTP proxy configured in BlueMind.
Improvement: HTTP clients from video conferencing providers (Meet, Webex, Zoom, Pexip, Nextcloud Talk, Teams, LiveKit) are now closed after each call, which prevents the accumulation of threads and connections.
Organizational units deleted from the source no longer reappear on the clone as placeholders. Their deletions are correctly replicated, including for units that still contained members, children or administrators.
Subfolders now retain the correct path when a parent folder has been renamed on the source.
Calendar shares are correctly reflected in the clone’s Freebusy status.
Shared folders are once again visible to the user on the clone.
Users who have uploaded a photo will have their photo (rather than the default image) displayed on the clone.
Calendars and address books that have been renamed retain their new names on the clone.
Global settings (retention and maximum file hosting size, automatic detachment limit, tags ignored by DataProtect, password policy, etc.) are now cloned and flagged in ‘tail’ mode.
Contacts deleted by clearing an address book (or by resetting a calendar, to-do list or notes, or via bm-cli reset) are now also deleted on the clone.
Replication to Kafka no longer remains permanently blocked following a database error (loss of connection, restart or failover of PostgreSQL). Previously, clones and continuous backups would miss the relevant changes until bm-core was restarted. Records are now returned in the correct order (duplicates are possible, but the order is never reversed).
Performance and reliability: the container modification event (address books, calendars, tasks, notes) is no longer published twice, and HTTP clients (vCard certificates, OpenID URL verification, JWT tokens) are correctly closed, which fixes resource leaks.
A REST response split into chunks could be truncated without any error being returned. The issue has been fixed.
BM-24334: Improvements to system stability when sending a large email to a very large number of recipients (for example, a 30 or 40 MB email to several hundred people reading the message at the same time).
The symptoms were direct memory saturation on the IMAP side, a full memory pool and blocked BM-Core threads.
BM-24352: Fix: Emails with multiple recipients now retain their full ‘From’, ‘To’ and ‘Cc’ lists in the search index (up to 8,191 characters, for full recipient names only).
Note: Emails indexed prior to this fix will retain their truncated lists until the mailbox is re-indexed.
BM-24336: Fix: Elasticsearch purges (mailbox deletion, expunge) now run as flagged tasks.
Realms and repair: a temporary error no longer destroys a domain’s realm or its SSO sessions. The repair process no longer rebuilds realms unnecessarily (client secret and sessions are retained) and covers the connection flow. A realm is only created for a usable domain (neither global.virt without its own URL, nor CAS).
Login: this always goes through the domain’s authentication flow (including conditional OTP). A domain created with a URL works without restarting the core, and an incomplete OpenID configuration causes the login to fail immediately with an error naming the domain. Convergence no longer fails when Keycloak has named the user federation.
Performance and security: domain creation now twice as fast (one authentication instead of 20), core tokens with special characters (+, &, %) accepted, client secret more exposed in plain text, streamlined token verification, and BlueMind settings (Kerberos journaling, cache) correctly transmitted to Keycloak.
BM-24321: Fixes: Interruption of an incomplete backup.
Cancelling a backup (by an administrator or after 23 hours) now effectively stops the email backup process: this includes backing up mailboxes, downloading content and copying data to the backup storage.
A cancelled backup stops once the processing of the current mailboxes is completed; it no longer appears in the list of backups and ends with the message ‘Backup cancelled’.
Only one backup can run at a time: no new backup will start whilst another is in progress, even if that one has been cancelled. The task report will indicate the reason for this.
The progress made when downloading email content is now saved: the next backup resumes where it left off, rather than re-downloading the latest emails each time.
Pre-production subscriptions now behave in the same way as the production environments they replicate, whilst also displaying a permanent warning to all users stating that the installation must not be used in production.