enable_forwarded_emails is a great feature for bringing existing conversations into Discourse, but for users who approach Discourse with a “Mailman-mind” - as many users on our instance do - this feature just doesn’t do what they’re expecting it to.
Within every email client I’ve used, forwarding an email intentionally excludes the original email address from the forward, and subsequent replies. Whereas with this feature, that original email address is included in the created post and subsequent replies.
If this feature isn’t enabled, then Discourse strips the actual forwarded email, which also doesn’t work for us.
My thought is there should be an alternative feature which doesn’t strip the forwarded email and posts it like so:
Yep, as both other options “show” the forwarded email, but this one quotes in in the original post.
What it says on the ! It’ll attempt to parse the forwarded email, then create a staged user from the original sender of the forwarded email, and post the forwarded email as the original topic and then any text the forwarder includes as a reply to that topic (at least that’s the way round I remember it working).
Aah, now I get it. It’s the text that the forwarder includes that becomes the reply! But that’s exactly one reply. Why does it say create replies?
Another reason why the terminology is somewhat confusing: both “hide” and “quote” refer to the forwarded text but “create replies” refers to the forwarders commentary om the forwarded text. So perhaps these options could be clarified somehow by saying
hide forwarded email
quote forwarded email
post forwarded mail with replies
As I write, I’m wondering whether this third option is really how it works. I don’t think it ever behaved like that for us but then again we don’t have a lot of forwarded mails, so I’m not sure. Does it even make sense to post the forwarders comment as a reply? Shouldn’t it somehow be made clear that the forwarded email was posted by the forwarder? This is not at all clear when you have the forwarder apparently reply to it.
So I’m using the quote setting and it definitely doesn’t work as described. Maybe I’m still misunderstanding the intended behaviour but this seems pretty clear:
and this is not what I’m getting. So let me be mote precise in what I’m getting: someone forwarded an email starting with a short note like “Look at this” followed by the forwarded email. The forwarded email included text as well as two pdf files as attachments. The post shown on the forum looked like this:
So the forwarded email was completely stripped with the exception of the file attachments. I was able to recover it manually and it even started with ---------- Forwarded message --------- so identifying it could not have been easier…
Okay, that looks just like I’d expect it. Good to see that it works at least under certain circumstances. But did your email include an attachment? If not, it seems plausible that discourse is confused by (certain?) attachments.
I’m still having issues with forwarded emails not being displayed. Since I do have at least one email with attachments that was correctly rendered, my guess is now that it has to do with whether the person forwarding the email added something to the email or not. From what I can see, emails that were forwarded without adding any text above the forwarded email were rendered correctly but if the forwarder added something like “FYI”, only the attachments are included in the post but not the text of the forwarded email.
In other words, this example still doesn’t work (because it includes “Thought you all should see this:”):
Instead of the above result, this email would be rendered as:
Thought you all should see this:
And nothing else.
Could someone confirm whether this problem is specific to my instance or whether it exists also elsewhere?
Please check emails with an attachment in particular (e.g. a pdf file) as it is possible that the problem only occurs when text is added AND there is an attachment.
I also am still confused what these different labels/features do – trying to set up incoming email to use with the Tickets Plugin but getting inconsistent behavior.
I feel like the default behavior should be that whatever gets forwarded in becomes a post by the (staged or regular user) that created the message. The reason it’s getting forwarded seems to most often be that someone who got the message felt it would be better addressed on Discourse, so that topic seems most appropriate to be started by the email’s author, not the forwarder.
It should work that way when you set enable_forwarded_emails to create_replies. The forwarded email will be the first post and it creates a reply if the forwarder wrote some text. Otherwise it creates a small action post, so that it is clear who forwarded the first post.
If create_replies is the chosen value for the forwarded emails behaviour site setting, then the original message becomes the opening post in the topic, and anything written in the email above the forwarded message, becomes a reply to the topic below the 3rd party message.
Q: Do any of the other values of this site setting – namely, hide or quote – just (only) process the original 3rd party message and nothing more?
I am wondering if the attempt to split out these “create replies” might be the cause of some weird errors I’ve been seeing when sending things in from a Microsoft Outlook client.
PS: I wonder, might this setting be worth a FAQ/howto entry to be linked from the description text below the site setting? It might just be me but I have rarely been so confused with a Discourse setting over the past 7 years. Or maybe I just need more
No. You will get a small action post when there’s no text before the forwarded message.
I believe this feature is still marked as experimental and there’s a good reason for it. Emails are usually forwarded inline. That makes it quite hard to extract the forwarded email, because each client forwards the original email headers differently. Some even hide the email address of the original From header or use localized headers.
It should work a lot better when emails are forwarded as attachment instead of inline (I’m 99% sure that Discourse supports this).
I would agree that would be a much cleaner way to ensure correct processing. I wonder why I can’t get Discourse to process the attachments when I do. (The content of the forwarded attachment comes through in the raw content tagged to the post, but only the ‘commentary’ is rendered, not the forwarded original. Again, at least for MS Outlook; I’ll have to try some other clients.)
Inline forwarded messages are getting trimmed away, with both quote and create_replies modes enabled.
Original message (some headers removed):
From: Jeffrey Lastname <firstname.lastname@example.org>
Subject: Fwd: Thank you for your support!
X-Mailer: MailMate (1.14r5745)
Content-Type: text/plain; format=flowed
Some really long sample text.
> From: Donations Team <email@example.com>
> To: firstname.lastname@example.org
> Subject: Thank you for your support!
> Dear Jeffrey,
> Our heartfelt thanks for your donation to Example Project,
> especially now. Together we will write the future.
Forwarding the message as an attachment doesn’t seem to work either. eml attachments are rejected. If eml attachments are authorized, then in “create_replies” mode, it attaches the eml and the forum visitor has the option to download it.