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

Offen
#66,610 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
50/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
php
Bereich
backend

Rechercherichtung

The payload names no files, so start by searching the server code for where an incoming iMIP METHOD:REPLY is matched to an event's ATTENDEE, then compare how the address is compared with the stored one. Reproduce with an event whose attendee has mixed-case letters and a REPLY whose address differs only in case. Done when PARTSTAT changes to ACCEPTED in both the mixed-case and lowercase cases, with a test covering the mixed-case path.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

0. Needs triage 35-feedback bug feature: caldav
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, [email protected]).
  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.

Vorherrschende Sprache
PHP
Sterne
37.5k
Forks
5.4k
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
639

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus nextcloud/server

Alle Issues in nextcloud/server

Ähnliche Issues

Weitere Issues zu PHP

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.