BM-23989: Fixes: Inconsistency in notification emails for modified events.
BM-23996: Fixes: Incorrect month in an event’s recurrence in an ICS export.
BM-24039: Fixes: Interface for the pending invitations counter when the user has a large number of shared calendars.
The pending invitations badge now correctly takes into account write-enabled shared calendars, including those shared via a group, to allow a delegate to reply to invitations on behalf of the owner.
BM-22982: Fixes: Empty blocks appearing when printing a shared calendar with ‘availability only’ sharing rights as a PDF.
BM-24075: Fixes: A user with access rights to a shared mailbox does not receive event invitations sent to that mailbox.
The day of the week for a weekly recurring rule is now displayed correctly again, regardless of the language configured on the server.
BM-24039: Fix: A CalDAV request to the calendar root no longer fails entirely due to a single subscription that is obsolete or whose owner has been suspended; only that resource is now ignored.
BM-23941: Performance improvements to prevent the generation of the offline address book (OAB) or the loading of contact records from overloading the server and slowing down Outlook/EWS clients.
BM-23623: Fixes: Duplication of emails after deletion in Outlook 2019.
BM-24025: Fixes: An event whose attachment has been moved to file storage is not correctly resynchronised in the organiser’s Outlook.
BM-24113: Fixes: When a manager confirms a resource booking, a notification of a cancelled booking is sent.
BM-24129: Fixes: When an import error occurs – for example, when creating a shared mailbox – the AD import task incorrectly reports that it has succeeded.
An Active Directory import no longer erroneously blocks the licence verification process for an administrator who does not have the subscription management role.
BM-23048: Fix/Improvement: Reports on scheduled jobs (e.g. backups) are no longer sent from the internal technical address no-reply@global.virt, which is often classified as spam; a dedicated sender address can now be configured.
BM-23878: Fixes: Malfunction of the ‘Log in as’ link in the administration console.
BM-24134: Fix: A re-indexing task scheduled before a domain switches to the new alias (ring) mode is now correctly skipped rather than running using outdated logic.
BM-24162: Fixes: Calendar restoration fails for events whose tag does not yet appear in the session.
BM-23953: Fixes: After an upgrade from version 4 to 5, the backup task reports that it has completed successfully even though some copy tasks have failed.
The anti-spam/Milter filter crashes when encountering certain unknown calendar events.
A concurrency bug that could cause the rewriting of sender addresses (SRS) to become unstable when several emails were being processed at the same time.
BM-24100: Fixes: Emails lost during multiple redirects.
BM-24138: Fixes: Some emails were marked as sent even though they had temporarily failed (e.g. server unreachable).
Fix: emails are now held in the queue and the server automatically retries after a delay.
Cloning an installation no longer causes the process to hang indefinitely whilst waiting for certain locally generated keys to be replicated on the cloned installation.
Tracking the progress of a clone is now structured and manageable, with a dedicated command to track its progress in real time and to resume or skip a record that has encountered an error.
The restoration of the directory, email bodies and the message queue is now carried out in parallel and in batches, enabling faster cloning.
When a shared mailbox is cloned, its data location, quota and routing are now correctly retained.
A clone no longer fails when a folder tree is temporarily deleted and then recreated during a shared mailbox conversion.
Fixes to several packages (bm-lifesize, simpleaccount, bm-tbird-autoconf) which were being delivered empty or were not installing correctly in RPM/Debian.
Certain unrecognised iCalendar settings (e.g. icon links added by Thunderbird) would lose their escaping when saved again, which could corrupt subsequent attachments for the same event.