Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: External attendee invitation marked failed (schedule-status 3.7) while SMTP test succeeds on Nextcloud 34.0.5

未关闭
  • 哪里不对？
#65,882 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
1-2 天
新手友好度
32/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
php
领域
backend

调研方向

Start by identifying which server code handles Calendar attendee invitations and how it records delivery status. The report does not identify a failing log entry or confirm that the observed SCHEDULE-STATUS=3.7 belongs to the original event, so first determine whether the status reflects address validation or an iMIP delivery failure. Done means reproducing the behavior and establishing its cause or the additional evidence needed to distinguish those paths.

由索引模型根据 Issue 内容生成。

描述

Bug description

When an external email attendee is added to an event using the Nextcloud Calendar web UI, the attendee shows "Failed to deliver invitation". The stored iCalendar attendee entry for the same external recipient (in another event) contains SCHEDULE-STATUS=3.7.

This is unexpected because the administration UI has Send invitations to attendees enabled, and a test email sent from the administration SMTP settings succeeds.

Important limitation: The SCHEDULE-STATUS=3.7 value was confirmed in a different event with the same external attendee; the iCalendar record of the originally reported event was not extracted. This issue reports a suspected invitation-delivery problem, not a confirmed root cause.

Environment
  • Nextcloud Hub 26 Spring, version 34.0.5
  • Calendar web UI (Calendar app version not yet established)
  • Self-hosted Nextcloud
  • Admin > Groupware > Calendar server: "Send invitations to attendees" enabled
  • Admin > Basic settings > Email server: SMTP, port 587; Send test email succeeded
  • External attendee email address omitted for privacy
Steps to reproduce / observed behavior
  1. Create or edit a calendar event in the Calendar web UI and add an external email attendee.
  2. Save the event.
  3. The external attendee is displayed as "Failed to deliver invitation".
  4. Independently, a database inspection of another event involving the same attendee shows an ATTENDEE property with PARTSTAT=NEEDS-ACTION;SCHEDULE-STATUS=3.7.
  5. An SMTP test email sent from Nextcloud's admin settings reports success.
Expected behavior

An email invitation should be delivered to a valid external email attendee, or the Calendar UI should provide an actionable reason for delivery failure.

Actual behavior

The Calendar UI reports failed invitation delivery despite an apparently operational SMTP test path. The underlying reason remains unconfirmed.

Diagnostics
  • ATTENDEE;...;SCHEDULE-STATUS=3.7:mailto:<external-address> (obtained from one calendar object; recipient redacted).
  • Recent Nextcloud log searches did not expose a clearly matching invitation-delivery exception.
  • No configuration changes were made during investigation.
  • RFC 6638 uses 3.7 for invalid calendar user, but that alone does not explain whether external email delivery was attempted or should have been.

Please advise which additional non-sensitive evidence would distinguish an expected scheduling-address validation outcome from an iMIP delivery failure.

主要语言
PHP
星标
37.2k
派生
5.3k
平均合并
2 天 3 小时
30 天内合并 PR
676

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

nextcloud/server 的其他 Issue

查看 nextcloud/server 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。