When the organizer (e.g. Bob) creates a recurring event and invites an attendee (e.g. Cedric) only to a specific occurrence (#2),
if the organizer later modifies another occurrence (#3) (which Cedric is not invited to),
SabreDAV still sends an iTIP REQUEST to Cedric — even though he should not receive any update.
✅ Expected behavior
• When the organizer modifies an occurrence that does not include the attendee in its ATTENDEE list,
→ No iTIP message should be sent to that attendee.
→ The attendee’s inbox should remain unchanged.
❌ Actual behavior
• SabreDAV currently sends a new iTIP REQUEST to uninvited attendees, even though they were not part of that specific RECURRENCE-ID.
🧪 Steps to reproduce
1. Organizer (Bob) creates a daily recurring event with 3 occurrences.
2. Bob invites Cedric only to occurrence #2
3. Bob modifies occurrence #3
4. Observe Cedric’s inbox: a new iTIP REQUEST appears unexpectedly.
📋 Test reference
linagora/twake-calendar-integration-tests#90
void shouldNotSendUpdateToUninvitedAttendeesWhenOrganizerModifiesOtherInstances() { ... }