@tobiaseigen: I hadn’t tried clicking on the envelope icon. That’s neat, but it not feasible as a workaround. I can’t possibly go around looking for posts sent by email and looking for forwarded content. Especially because we have some private categories on our site which I purposefully ignore unless I am @mentioned.
@sam: No forwarded email works. They come out like this:
We just hit this problem in a test instance where we are assessing Discourse as a ticketing system.
The test was done using GMail, a pretty popular service. Getting emails forwarded is not unusual in our context. This problem is quite a blocker for us…
It’s a bit strange that nobody has complained in the last years. Maybe there is another thread with a workaround somewhere?
Ouch. I was about to file an issue upstream (nobody seems to have complained about forwarded emails there), but the lack of activity is discouraging. Maintaining a local patch isn’t a great prospect either.
Our users are totally external, people sending email to what they think is a normal mailbox.
If you post the raw email with all its headers (or send me a PM) and tell as what you saw and what you expected to see, we might be able to figure this out.
You did enable the enable forwarded emails site setting, right?
OK, I tested again with the same email and now the forward does appear, no problem. It appears in a different way than expected (the topic appears as created by the author of the email being forwarded, not the email being sent, an this has implications we have to consider).
In any case, thank you. The big blocker is now solved.
Maybe the solution is to skip any removal of content in mailing list mirror mode? Mirror is mirror, and the risk of missing content is way more expensive than the convenience of not showing signatures (especially when we are thinking that Discourse becomes the de facto archive of a mailing list).
I guess we could add a setting to disable trimming for mailing list mirrors. It could make sense for lists where members know how to behave and don’t include hundreds of useless lines of text from previous emails. Can you create a feature request for it?
Nevertheless, I’ll try figure out why forwarded emails do not work for mailing list mirrors.
I think the typical forward would match the embedded marker not followed by a quote rule which discards it. Discarding is reasonable behavior for the other cases mentioned there (e.g. huge quote) but not for forwards.
Pensé que esto ya estaba activado porque mi Discourse de hecho aceptó correos reenviados y creó publicaciones. Sin embargo, eliminó el contenido del correo reenviado. ¿Entonces mi entendimiento es correcto en que esta configuración cambia la forma en que se analizan los correos entrantes? O, más precisamente: ¿cómo se analizan los correos entrantes que no son respuestas a un tema existente?
En cualquier caso, espero que activar esta configuración resuelva el problema de que el contenido reenviado no aparezca en las publicaciones. Pero aún me pregunto: ¿No hay una forma sencilla de corregir manualmente las publicaciones donde Discourse colocó incorrectamente la línea de corte (entre el contenido mostrado y el eliminado)?
Edición: Acabo de encontrar esta nueva característica (que aún no tengo en esa instancia), así que actualizaré, pero ¿podría alguien aclarar cómo se relaciona esa nueva configuración con lo que se ha discutido aquí? ¿Es específica para listas de correo?
Edición 2: Después de investigar varios temas más creados por correo en los últimos meses, parece que el contenido de los correos reenviados se elimina solo si hay algún texto agregado antes del correo reenviado (por ejemplo, algo como: “FYI” o “aquí hay algo interesante”). Si el correo se reenvía sin comentarios, el contenido se muestra (sin embargo, las cabeceras de los correos reenviados se eliminan, de modo que parece que el reenviador escribió el contenido de la publicación). ¿Es todo esto un comportamiento intencional?
