@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.
The answer you quoted is quite out of date. We stared using our own gem a long time ago.
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.
Eu achei que tinha isso ativado, pois meu Discourse de fato aceitava e-mails encaminhados e criava posts. No entanto, ele removia o conteúdo do e-mail encaminhado. Então, minha compreensão está correta ao dizer que essa configuração altera a forma como os e-mails recebidos são analisados? Ou, mais precisamente: como são analisados os e-mails recebidos que não são respostas a um tópico existente?
De qualquer forma, espero que ativar essa configuração resolva o problema de o conteúdo encaminhado não aparecer nos posts. Mas ainda me pergunto: não há uma maneira fácil de corrigir manualmente os posts onde o Discourse posicionou incorretamente a linha de corte (entre o conteúdo exibido e o removido)?
Edição: Acabei de encontrar este novo recurso (que ainda não tenho nessa instância), então vou atualizar, mas alguém poderia esclarecer como essa nova configuração se relaciona com o que foi discutido aqui? Ela é específica para listas de e-mail?
Edição 2: Após investigar mais alguns tópicos criados por e-mail nos últimos meses, parece que o conteúdo dos e-mails encaminhados é removido apenas se houver algum texto adicionado antes do e-mail encaminhado (por exemplo, algo como: “FYI” ou “aqui está algo interessante”). Se o e-mail for encaminhado sem comentários, o conteúdo é exibido (no entanto, os cabeçalhos dos e-mails encaminhados são removidos, de modo que parece que o encaminhador escreveu o conteúdo do post). Tudo isso é comportamento intencional?
