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

[Bug] Received reply displays quoted previous message instead of the actual new message body

Abierto
  • ¿Algo no está bien?
#13,679 2 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
javascript
Área
frontend

Línea de trabajo

Comienza importando el archivo .eml anonimizado enlazado y comparando cómo Nextcloud Mail renderiza sus alternativas text/plain y text/html con Thunderbird. Sigue el punto de entrada del renderizado del cuerpo del mensaje y el manejo del contenido MIME citado; se considera terminado cuando se muestra la nueva respuesta mientras el mensaje citado anterior permanece excluido.

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

Descripción

1. to develop bug
Steps to reproduce
  1. Send a message to a system that includes the original message when replying. In this case the reply was generated by Stripe/Salesforce.
  2. Receive the reply.
  3. Open it in Nextcloud Mail.
  4. Nextcloud displays the body of the quoted previous message instead of the new reply.
  5. Use «View source» or download the .eml.
  6. The raw message contains the correct new reply before the quoted previous message.
  7. Open the same IMAP message in Thunderbird.
  8. Thunderbird displays the new reply correctly.
Expected behavior

Nextcloud Mail should display the new, non-quoted portion of the received message as the message body.

Actual behavior

Nextcloud Mail displays content from the quoted previous message and hides the actual newly received reply.

Mail app version

5.11.5

Nextcloud version

33.0.8 / Nextcloud AIO v13.6.0

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Nextcloud memory caching

No response

Web server

None

Database

None

Additional info

A newly received reply is displayed with the body of the previous message instead of the actual new reply.

The message itself was synchronized correctly. The raw message source in Nextcloud Mail contains the correct new reply, followed by the quoted previous message.

Thunderbird displays the exact same IMAP message correctly.

In Nextcloud Mail:
sender, recipient, timestamp and subject belong to the newly received message
the displayed body is taken from the previous quoted message
the actual new body is not shown

The downloaded .eml confirms that the new body is present and occurs before the quoted previous message in both the text/plain and text/html MIME alternatives.

MIME structure:

multipart/mixed
└── multipart/alternative
    ├── text/plain
    │   ├── actual new reply
    │   └── quoted previous message
    └── text/html
        ├── actual new reply
        └── quoted previous message

I was able to create an anonymized standalone reproducer based on the affected message.

The anonymized .eml preserves the relevant MIME structure and contains an explicit new reply followed by an older quoted message.

Expected visible body:
This is the actual NEW content of the received reply.

The quoted section later in the message contains:
This is the OLD, quoted message text.

I imported this anonymized .eml into a normal IMAP folder and opened it in Nextcloud Mail. Nextcloud Mail reproducibly displays the OLD quoted message as the visible body instead of the new reply.

Thunderbird displays the same anonymized .eml correctly.

This reproduces independently of the original Stripe message and independently of the original mailbox state.

One possibly relevant detail is that the HTML part of the quoted previous message contains another complete ... document.

Image

nextcloud-mail-anonymized-repro.eml

This therefore does not appear to be an IMAP synchronization or UID issue. The correct raw message is available to Nextcloud Mail, but the wrong part of its content is rendered as the visible body.

This may be related to #12811.

I also have #13590 open for a separate IMAP UID/cache issue, but based on the raw source this appears to be a different problem.

Lenguaje dominante
JavaScript
Estrellas
1k
Forks
364
Merge medio
1 d 11 h
PR fusionados (30 d)
100

Preparar el entorno

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/mail

Todos los issues de nextcloud/mail

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.