CalDAV attendee RSVP rejected when client omits organizer PRIORITY:5

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

  1. Deliver a fresh external Microsoft Exchange Online invitation containing PRIORITY:5 to a Stalwart attendee.
  2. Let Stalwart automatically add the invitation and confirm that the attendee is NEEDS-ACTION.
  3. Fetch the attendee copy through CalDAV in BusyCal on iOS.
  4. Tap Accept.
  5. BusyCal sends the event with the local attendee set to ACCEPTED but without the PRIORITY property.
  6. Observe the HTTP 412 response.
  7. 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

Your analysis matches the source. I found no setting that relaxes this check, and nothing in the docs describes preserving an omitted organizer property.

In crates/groupware/src/scheduling/attendee.rs, the server compares the attendee’s PUT with the stored instance. Any property that can_attendee_modify_property doesn’t allow is counted. If one is added, or removed (the “Check removed fields” loop), the server returns ItipError::CannotModifyProperty. crates/dav/src/calendar/mod.rs maps that error to the AllowedAttendeeObjectChange precondition, which becomes the 412. So a missing PRIORITY is treated the same as an attendee deleting it.

Two things in the code bear on your proposal:

  • Explicit changes: an explicit different PRIORITY would still be caught by the add/remove count check, so rejecting those is separate from the omitted case.
  • Tolerating omission: this would mean either merging the stored value back in before comparing, or skipping the removed-field check for specific properties. Either is a code change, and I can’t tell from the docs whether the maintainers want it.

You’re on v0.16.x, and the report says v1.0.0 has the same check (I confirmed it for the current source). I’d retest on v1.0 using the upgrade guide, because behaviour and configuration differ between the two.

Your JMAP workaround of removing PRIORITY first with sendSchedulingMessages=false fits how the check works. The stored and submitted properties then match, so the PARTSTAT change goes through and the reply is sent.

A community or staff member will follow up on whether a fix is planned.

This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.

Stalwart only let attendees change a short list of properties (SUMMARY, DESCRIPTION, COMMENT, EXDATE, plus the task status fields on VTODO), and PRIORITY wasn’t on it. When BusyCal left it out of the PUT, that counted as the attendee removing an organizer property, so the whole RSVP got rejected with the 412.

I went a bit further than restoring the stored value. Attendees can now add, change or remove PRIORITY on their own copy. RFC 6638 section 3.2.2.1 only sets the minimum a server has to accept, and PRIORITY never goes into the iTIP REPLY, so the organizer sees exactly what they’d see today. A plain accept from BusyCal now stores ACCEPTED and sends one REPLY, and the next update from Exchange brings back the organizer’s PRIORITY anyway.

The same per-instance check runs on recurrence overrides, so a missing PRIORITY there shouldn’t trip it any more either. If the JMAP synthetic occurrence id problem is still there after you update, please open a separate topic for it with an example.

The fix ships in the next weekly Stalwart release.