[Bug]: iMIP REPLY does not update attendee status when email address contains uppercase letters
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- Create a calendar event in Nextcloud Calendar.
- Add an external attendee using an email address containing uppercase letters (for example,
[email protected]). - Send the invitation.
- Accept the invitation in Microsoft Outlook using the normal Outlook Calendar Accept action.
- 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.
- 主要语言
- PHP
- 星标
- 37.5k
- 派生
- 5.4k
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 639
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
nextcloud/server 的其他 Issue
-
35-feedback
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
0. Needs triage 35-feedback bug
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
workflowengine: File entity reuses the node of the first "Tag assigned" event for all later events in the same process可能已有人在做 @lazerg 于 2 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
Contacts import aborts with TypeError when vCards have no UID (TextImporter structure)可能已有人在做 @SebastianKrupinski 于 6 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 72/100
nextcloud/server#66486 · 2 条评论 · 2 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
-
Unified search: screen reader hears "No matching results" on mobile even when there are results可能已有人在做 @lazerg 于 10 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
相似的 Issue
-
[Sync EN] stream: document the errors of the stream_context_*() and stream filter functions (#6091)未关闭sync-en
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 79/100
Automattic/blocks-engine#6318 ·
维护者通常 1 天内回复
-
Update: Laravel Cheat Sheet - middleware examples for the bootstrap/app.php layout (small update)未关闭
难度 2/5 1-3 小时 新手友好度 84/100
OWASP/CheatSheetSeries#2990 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复