@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.
저는 이 설정이 켜져 있다고 생각했습니다. 실제로 제 Discourse 인스턴스가 전달된 이메일을 받아들이고 게시물을 생성했기 때문입니다. 하지만 전달된 이메일의 본문 내용이 제거되어 있었습니다. 따라서 제 이해가 맞는지 확인하고 싶습니다. 이 설정이 변경하는 것은 수신된 이메일을 파싱하는 방식인가요? 아니면 더 정확히 말하면, 기존 주제에 대한 답장이 아닌 수신된 이메일을 파싱하는 방식을 변경하는 것인가요?
어쨌든, 이 설정을 활성화하면 전달된 내용이 게시물에 표시되지 않는 문제가 해결될 것이라 희망합니다. 하지만 여전히 궁금한 점이 있습니다. Discourse가 잘라내기선(표시되는 내용과 제거되는 내용 사이)을 잘못 배치한 게시물을 수동으로 쉽게 수정하는 방법이 없나요?
수정: 방금 이 새로운 기능을 발견했습니다(해당 인스턴스에는 아직 적용되지 않았습니다). 따라서 업데이트를 하겠지만, 누군가 이 새로운 설정이 여기서 논의된 내용과 어떤 관련이 있는지 설명해 주실 수 있을까요? 메일링 리스트에 특화된 기능인가요?
수정2: 지난 몇 달간 이메일을 통해 생성된 몇 가지 주제를 조사해 본 결과, 전달된 메일의 본문 내용이 제거되는 경우는 전달된 이메일 앞에 텍스트가 추가된 경우(예: “참고” 또는 “흥미로운 것이 있습니다” 등)인 것으로 보입니다. 주석 없이 메일을 전달하면 본문 내용은 표시됩니다(다만, 전달된 메일의 헤더는 제거되므로 전달자가 게시물 내용을 작성한 것처럼 보입니다). 이 모든 것이 의도된 동작인가요?
