@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.
Je pensais l’avoir activé, car mon Discourse acceptait effectivement les emails transférés et créait des publications. Cependant, il supprimait le contenu de l’email transféré. Mon interprétation est-elle donc correcte : ce paramètre modifie la manière dont les emails entrants sont analysés ? Ou plus précisément : comment sont analysés les emails entrants qui ne sont pas des réponses à un sujet existant ?
Quoi qu’il en soit, j’espère que l’activation de ce paramètre résoudra le problème du contenu transféré qui n’apparaît pas dans les publications. Mais je me demande toujours : n’existe-t-il pas un moyen simple de corriger manuellement les publications où Discourse a mal placé la ligne de coupure (entre le contenu affiché et celui supprimé) ?
Édit : Je viens de découvrir cette nouvelle fonctionnalité (que je n’ai pas encore sur cette instance), je vais donc mettre à jour. Mais quelqu’un pourrait-il préciser comment ce nouveau paramètre se rapporte à ce qui a été discuté ici ? Est-il spécifique aux listes de diffusion ?
Édit 2 : Après avoir examiné plusieurs autres sujets créés par email au cours des derniers mois, il semble que le contenu des emails transférés soit supprimé uniquement s’il y a du texte ajouté avant l’email transféré (par exemple, quelque chose comme : « FYI » ou « voici quelque chose d’intéressant »). Si l’email est transféré sans commentaire, le contenu est affiché (bien que les en-têtes des emails transférés soient supprimés, de sorte que cela donne l’impression que la personne qui a transféré a écrit le contenu de la publication). Tout cela est-il un comportement intentionnel ?
