5.3.3
Version published on 2025/06/24
If you wish to update your BlueMind from a previous minor or major version, please refer to the Release notes 5.3.
Webmail BlueMind (Mail App)
- BM-22220 : Fix: Prevent error when changing too quickly from an application to another
- BM-22309 : Fix: Do not reset user data on user change
- BM-22310 : Fixes: phishing attempt not detected when the full name is already known. The search now also includes the email address.
- BM-21003: Fix: Redirect composition to RC only if RC is available
- BM-21003 : Fix: Remove invalid roles on login
- BM-21003: Fixes: Add webmail dependency to bm-plugin-core-webmail Webmail is always on core, ensure that bm-webmail is installed if bm-plugin-core-webmail core plugin is installed.
- BM-22349 : Fixes: unable to expand the “CC” list if there is no recipient in the “To” field.
- BM-22215 : Fixes (partially): The signature is placed after the response quote.
- BM-21225 : Fixes: The signature is moved to the bottom of the composer when adding a recipient.
Calendar
- BM-22261 : Fixes: day starting hour not changed after setting update.
Contacts
- BM-22096 : Fixes: Reset certificates field when switching contacts.
Architecture
Backup / Restore
- FEATBL-3168 : Fixes: Create file structure in backup patch if necessary
Core
- BM-22323: Fixes: Translate Antarctica Casey to correct tz id
- BM-22323: Fixes: Don't try to match against real timezones when sanitzing event.
- Fix: Improve
filteredChangeset
SQL performance when changes count is small and item count is big
Dataprotect
- BM-22320: Propagates download messages exceptions
EAS
- BM-21259: Fixes: Decoding of PJ files with exotic file names is not done correctly.
Elasticsearch
- Fix: Incremental indexing is now deduplicated, resulting in a big performance boost on cloning instances.
IMAP
- BM-22298 : Fixes: Fetch problem for mails with attachment for some special cases
- BM-22306 : Fixes: Rework response of fetch command to be compliant with 4.9
Kafka
- FEATBL-3167: Fixes: Enforce usage of restore(Item) while cloning instead of create/update to ensure cloned-changesets are consistent with the source. Incremental sync should resume correctly after switching to a clone.
- Fixes: Disable all generic validators when cloning
- Fixes: Make resyncToKafka send a TRUNCATE event, and fix bad timestamp pushed in kafka
- Fixes: Disable MessageBodyPurgeQueue too old entries restoration for now
- Fixes: Pushes to kafka must always be in order. This patch fixes many cloning problems.
- Fix: Maintain phone synchronization status during cloning (previously, full synchronization was performed at each switchover)
Mail-API
- BM-22249: Fixes: When mailbox usage > 200G, return 200G instead of throwing an arithmetic exception.
Others
- Fixes: Add option to disable mailshare imip rejection
- Fixes: Keep committing to Kafka on Starvation