Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#65,882 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
32/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
php
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
PHP
Estrellas
37.2k
Forks
5.3k
Merge medio
2 d 3 h
PR fusionados (30 d)
676

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nextcloud/server

Todos los issues de nextcloud/server

Issues similares

Más issues de PHP

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.