A discussion on an email parsing issue with the ----Original message---- marker not being correctly stripped. DeanMarkTaylor reported the issue and offered to send raw emails to the Discourse Team for assistance. codinghorror suggested sending them to @techAPJ, who confirmed receipt and identified the issue as likely being a bug in the GitHub email_reply_parser library.
Another user, ashledombos, reported a similar issue with Yandex webmail and was asked to send the raw email source to @techAPJ for further investigation. The issue was eventually fixed via a pull request as reported by @techAPJ.
Email parsing reply not correctly handling ----Original message---- marker.
Here is a modified example (to protect privacy):
I have two examples of this now with the same user.
I’m willing to send via PM the raw original email replies to a one of the Discourse Team to help resolve this.
Cheers,
Dean.
Sure send it to @techapj if you have raw.
The raw emails have been sent to @techAPJ
Hi @techAPJ,
I haven’t had any feedback on this issue; if this has been forgotten about feel free to just let me know 
I have found out that the user causing the issue in my case uses the webmail client for “BT Mail”.
BT Mail is the optional free email service that comes with BT Broadband. When you register for BT Broadband you’ll be asked if you’d like a BT Mail address to use. If you choose this option you’ll then be given an email address that ends in @btinternet.com.
EDIT:
Not sure how many users they have now in 2015 - but I’m thinking it’s a few:
BT Group operates the BT Total Broadband brand and had 4.6 million accounts in January 2009.
Cheers,
Dean.
This issue is on my list, but low priority for now. Also, this issue is most probably due to bug in GitHub email_reply_parser library, so I will have to fix it upstream.
Hello, I have noted similar parsing problem with Yandex webmail, should I open another thread for it or just let it here?
@techAPJ Do you need also me to send raw message from yandex?
Sure, message me the raw email source.
Ok, I forward the reply to myself and copy paste the source to you, thank you
Fixed via:
