Issue Description
When an external invitation is imported through JMAP with sendSchedulingMessages: false, subsequently accepting, tentatively accepting, or declining it with sendSchedulingMessages: true saves the participant status successfully but generates no reply to the organizer.
Expected Behavior
The participant status is saved and an iTIP METHOD:REPLY is generated for the external organizer.
Actual Behavior
All three updates return success, and the requested status is stored. No reply is generated. Each update logs the following error at DEBUG level:
DEBUG iTIP message error (calendar.itip-message-error)
reason = “Not the organizer of the event”
CalDAV confirms that these imported events have no schedule-tag.
As a control, creating an already-accepted event with sendSchedulingMessages: true generates an iTIP reply and a scheduling tag. Subsequently changing that control event to tentative generates another reply.
These control messages were generated inside the network-isolated instance; external delivery was not tested.
Reproduction Steps
- Import a future event through CalendarEvent/set with sendSchedulingMessages: false.
- Set organizerCalendarAddress to an external address that is not an alias of the local account.
- Include the local attendee using calendarAddress, initially with participationStatus: “needs-action”.
- Fetch the event and identify the returned participant ID for the local attendee.
- Update that participant’s status:
{
“using”: [
“urn:ietf:params:jmap:core”,
“urn:ietf:params:jmap:calendars”
],
“methodCalls”: [
[
“CalendarEvent/set”,
{
“accountId”: “ACCOUNT_ID”,
“sendSchedulingMessages”: true,
“update”: {
“EVENT_ID”: {
“participants/PARTICIPANT_ID/participationStatus”: “accepted”
}
}
},
“rsvp”
]
]
}
- Read the event back and inspect scheduling logs.
- Repeat with separate imported events using tentative and declined.
The event must remain in the future and must not be a draft.
Relevant Log Output
DEBUG iTIP message error (calendar.itip-message-error)
reason = “Not the organizer of the event”
Stalwart Version
v1.x
Installation Method
Docker
Database Backend
PostgreSQL
Blob Storage
Filesystem
Search Engine
Meilisearch
Directory Backend
LDAP
Additional Context
Root cause identified in the code
In the existing-event update path, scheduling dispatch depends on whether schedule_tag exists:
let result = if new_calendar_event.schedule_tag.is_some() {
itip_update(…)
} else {
itip_create(…)
};
Importing without scheduling leaves the tag unset. A subsequent attendee RSVP therefore calls itip_create(), which rejects an external organizer with ItipError::NotOrganizer.
NotOrganizer is not classified as a JMAP error. The update handler logs it at DEBUG level, continues without scheduling messages, persists the participant status, and returns success.
The new-event creation path already handles NotOrganizer with an itip_attendee_create() fallback. The existing-event update path lacks equivalent attendee handling.
The update path needs to support attendee replies for imported events without scheduling tags, including subsequent RSVP changes.
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