Issue Description
An external Microsoft Exchange Online organizer sends a VEVENT containing PRIORITY:5. Stalwart stores the organizer’s value.
When the attendee accepts the invitation in BusyCal on iOS, the client changes the local attendee from NEEDS-ACTION to ACCEPTED but omits PRIORITY from its CalDAV PUT.
Stalwart rejects the complete write with HTTP 412:
AllowedAttendeeObjectChange: Cannot modify property PRIORITY
The attendee remains NEEDS-ACTION and no iTIP METHOD:REPLY is generated. Two independent fresh Exchange Online invitations reproduced the result.
We understand that RFC 5545 defines PRIORITY:5 as medium priority, while an absent PRIORITY property defaults to 0/undefined. RFC 5546 also does not permit an attendee to modify optional organizer properties. The rejection is therefore defensible as strict validation.
The interoperability problem is that the client provides no event-priority control and drops the protected property while serializing an otherwise valid RSVP.
Could Stalwart safely preserve the original organizer-controlled PRIORITY:5 when an attendee client omits it, while applying only the permitted attendee changes? This would not authorize the attendee to change the priority. A different explicit priority value should continue to be rejected.
Expected Behavior
Stalwart accepts the attendee’s PARTSTAT change, retains the original organizer-controlled PRIORITY:5 in the stored event, and sends exactly one iTIP METHOD:REPLY.
Explicit attempts by the attendee to replace the organizer’s priority with another value remain rejected.
Actual Behavior
Stalwart rejects the complete CalDAV PUT with HTTP 412.
The local participant remains NEEDS-ACTION and no iTIP reply is generated.
Reproduction Steps
- Deliver a fresh external Microsoft Exchange Online invitation containing PRIORITY:5 to a Stalwart attendee.
- Let Stalwart automatically add the invitation and confirm that the attendee is NEEDS-ACTION.
- Fetch the attendee copy through CalDAV in BusyCal on iOS.
- Tap Accept.
- BusyCal sends the event with the local attendee set to ACCEPTED but without the PRIORITY property.
- Observe the HTTP 412 response.
- Verify that Stalwart still stores NEEDS-ACTION and emits no iTIP reply.
Relevant Log Output
WebDAV PUT request (web-dav.put) … type = “CalDAV”, code = 412, result = “AllowedAttendeeObjectChange”, reason = “Cannot modify property PRIORITY”
Stalwart Version
v0.16.x
Installation Method
Docker
Database Backend
RocksDB
Blob Storage
RocksDB
Search Engine
Internal
Directory Backend
Internal
Additional Context
The issue was reproduced with two independent, freshly created Exchange Online invitations.
As a controlled workaround, removing only PRIORITY:5 beforehand through a state-guarded JMAP update with sendSchedulingMessages=false allowed the otherwise identical acceptance to succeed.
Stalwart then stored ACCEPTED, generated exactly one iTIP reply, and Exchange Online accepted the reply with SMTP 250.
The same normalization path also allowed an invitation to be accepted using native Apple Calendar. This does not prove that Apple Calendar would omit PRIORITY without the normalization; the direct PRIORITY rejection was reproduced with BusyCal.
A public search on 2026-10-27 found no exact report for “Cannot modify property PRIORITY”. The existing DTEND/DURATION report is related but does not cover this property.
Static inspection of the official v1.0.0 tag (commit 47df4c0baeb88d83424dfda6aa7cf6040706999e) found the same restricted-property count check, and the v1.0.0 release notes do not identify a specific fix for this case. We have not runtime-tested v1.0.0, so this is not a claim that its released binary reproduces the issue.
This report intentionally covers the simple non-recurring case. A separate limitation involving PRIORITY:5 inside recurrence overrides and JMAP synthetic occurrence IDs should not obscure this minimal CalDAV reproduction.
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