Email replies from Outlook not stripping out original message

(Michael Downey) #1

Had a user reply to a post (in a restricted subcategory, for what it’s worth) via HTML email using Microsoft Outlook 2010, and the original message was not stripped out. Checked the incoming email and nothing out-of-the-ordinary about it. On our Discourse site (latest), the reply post appeared as follows.

The same thing happened when the user replied to a PM via email.

Interestingly, the reply wouldn’t (shouldn’t?) have been processed because the reply message was only “Agreed!” which is only 7 characters, well under the minimum character requirement of 20.


From: previousauthor []

Sent: Monday, October 13, 2014 8:56 AM

To: Recipient User

Subject: Re: [Category/Subcategory] The topic title


October 13

Let’s check it out Friday.

To respond, reply to this email or visit in your browser.

To unsubscribe from these emails, visit your user preferences.

A use-case with inconsistent "Reply through email" parsing
Outlook 365 and/or MobileIron causing email replies not to strip out earlier messages
Previous Replies separator is not RFC-compliant
Replied by mail from Outlook 2013 doesn't remove previous message
(Tobias Eigen) #2

I had exactly the same thing happen to me this morning. It’s not a great situation and requires some additional editing to clean posts that come in and also some personalized training of users. Time consuming.

(James Milligan) #3

Same here, can’t confirm he’s using Outlook but I’m pretty certain he is.

(Sam Saffron) #4

@techAPJ can you look at this ASAP

Everyone, we need clear steps to repro, we need the actual payloads of the email.

(Michael Downey) #5

Just sent to you & @techAPJ via PM.

(Clay Heaton) #6

I also sent you an example of this, in a PM, at the end of last week.

(Arpit Jalan) #7

Should be fixed now! :wink:

Can anyone please confirm?

(Clay Heaton) #8

I just installed the upgrade and will let you know if I see more problems with Outlook and replies. Thanks for your prompt attention to this issue!

(Arpit Jalan) #9

Should be (properly) fixed now :bug:

(Arpit Jalan) #10