@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.
Pensavo di averla attivata, dato che il mio Discourse accettava effettivamente le email inoltrate e creava i post. Tuttavia, rimuoveva il contenuto delle email inoltrate. Quindi la mia comprensione è corretta: questa impostazione modifica il modo in cui vengono analizzate le email in arrivo? O, più precisamente, come vengono analizzate le email in arrivo che non sono risposte a un argomento esistente?
In ogni caso, spero che l’attivazione di questa impostazione risolva il problema del contenuto inoltrato che non appare nei post. Ma mi chiedo ancora: non esiste un modo semplice per correggere manualmente i post in cui Discourse ha posizionato erroneamente la linea di taglio (tra il contenuto visualizzato e quello rimosso)?
Modifica: Ho appena trovato questa nuova funzionalità (che non ho ancora su quell’istanza), quindi aggiornerò, ma qualcuno potrebbe chiarire come questa nuova impostazione si relazioni a quanto discusso qui? È specifica per le mailing list?
Modifica 2: Dopo aver esaminato diversi argomenti creati via email negli ultimi mesi, sembra che il contenuto delle email inoltrate venga rimosso solo se c’è del testo aggiunto prima dell’email inoltrata (ad esempio, qualcosa come: “FYI” o “ecco qualcosa di interessante”). Se l’email viene inoltrata senza commenti, il contenuto viene visualizzato (tuttavia, le intestazioni delle email inoltrate vengono rimosse, in modo che sembri che chi inoltra abbia scritto il contenuto del post). Tutto questo è un comportamento previsto?
