Skip to content

[Bug]: iMIP REPLY does not update attendee status when email address contains uppercase letters #66610

Open

Description

@svenbaer

Bug description

When an external attendee accepts a Nextcloud calendar invitation in Microsoft Outlook, Nextcloud does not update the attendee's participation status if the attendee email address was entered with uppercase letters when creating/sending the invitation.

Entering the same email address entirely in lowercase makes the workflow work correctly.

This suggests that attendee matching while processing an incoming iMIP METHOD:REPLY is case-sensitive, although email addresses are case-insensitive.

Steps to reproduce

  1. Create a calendar event in Nextcloud Calendar.
  2. Add an external attendee using an email address containing uppercase letters (for example, User.Name@example.com).
  3. Send the invitation.
  4. Accept the invitation in Microsoft Outlook using the normal Outlook Calendar Accept action.
  5. Let Nextcloud Mail process the incoming iMIP reply.

Actual behavior

The attendee remains in NEEDS-ACTION / "Waiting for response" in Nextcloud Calendar, even though Outlook has sent an acceptance reply.

Expected behavior

Nextcloud should match the attendee in the incoming iMIP reply independently of the letter casing of the email address and update the participation status to ACCEPTED.

Workaround

If the attendee email address is entered entirely in lowercase when sending the invitation, accepting it in Outlook works and the status is updated correctly.

Additional information

The issue was reproduced with Nextcloud-generated invitations and Outlook replies. The invitation and reply used the same event UID. The received reply contained METHOD:REPLY and an attendee with PARTSTAT=ACCEPTED.

The problem was also observed with other participants/domains, so it does not appear to be specific to one Outlook address.

Environment

  • Nextcloud Server: 35.0.2.2
  • Calendar app: 6.6.3
  • Mail app: 5.12.5
  • Deployment: Docker
  • Client accepting the invitation: Microsoft Outlook
  • Server platform: Raspberry Pi 5

Notes

This report concerns processing an incoming iMIP reply and matching its attendee address against the attendee stored in the calendar event.

Activity

  1. kabeer7121 commented on Nov 21, 2026

    @kabeer7121

    I think this comes from two places together.

    In CalendarImpl::handleIMipMessage() the sender of a REPLY is lowercased before it goes to the iTip broker:

    $sender = strtolower($vObject->VEVENT->ATTENDEE->getValue());

    Then sabre/vobject's Broker::processMessageReply() looks for the attendee in the stored event with a strict comparison ($attendee->getValue() === $itipMessage->sender, lines 366 and 427 in 4.5.6). So an event stored with mailto:User.Name@example.com never matches mailto:user.name@example.com. The attendee is treated as a new "party crasher" instead of being updated, and the original one stays at NEEDS-ACTION. That would also explain why lowercase addresses work.

    I opened sabre-io/vobject#817 to make that lookup case-insensitive, like the ORGANIZER check already is. Until that is released, a smaller change on the Nextcloud side would be to keep the original case for $sender and only lowercase where it is compared to the user's addresses. That would cover replies that use the same casing as the invite, though I'm not sure Outlook always keeps it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions