[Bug] Events deleted in Webmail are not removed from macOS Calendar via CalDAV

Issue Description

When deleting an event from the Bulwark web interface, the event is not removed from Apple Calendar on macOS after CalDAV synchronization.

However, deletion synchronization (and deletion) works correctly with Android calendar clients.

Expected Behavior

The event should be removed from Apple Calendar after it is deleted in Bulwark.

Actual Behavior

The event remains visible in Apple Calendar even after it has been deleted from the Bulwark web interface.

Reproduction Steps

  1. Open the Bulwark calendar web interface.
  2. Create an event and wait for synchronization with Apple Calendar.
  3. Delete the event from the Bulwark web interface.
  4. Wait for synchronization to complete.
  5. Open Apple Calendar on macOS.

Stalwart Version

v0.16.x

Installation Method

Docker

Database Backend

PostgreSQL

Blob Storage

S3-compatible

Search Engine

Meilisearch

Directory Backend

OIDC

Additional Context

Environment

  • Bulwark version: 1.7.3
  • Stalwart Mail Server version: 0.16.7
  • macOS: 26.5
  • Calendar client: Apple Calendar
  • Synchronization protocol: CalDAV
  • Firefox: 151.0.2

Additional Information

  • Event creation is synchronized correctly between Bulwark and Apple Calendar.
  • Events deleted from the Bulwark web interface remain present in Apple Calendar.
  • Events deleted from Apple Calendar is correctly erased in Bulwark web interface.
  • Deletion synchronization works correctly on Android calendar clients.
  • Synchronization itself appears to be functioning correctly apart from event deletion on macOS.

I have reviewed the documentation and FAQ and confirm that my issue is NOT addressed there.

on

I have searched this support forum (open and closed topics) and confirm this is not a duplicate.

on

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

This has been fixed on the main branch. The fix will be included in v0.16.8.

Thanks a lot !

Maybe a link with this other issue ?