# Malformed bullet causes emailed in topic to be incorrectly truncated
**URL:** https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374
**Category:** Bug
**Created:** [February 18, 2015, 7:39pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374 "2015-02-18T19:39:27Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [February 18, 2015, 7:39pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/1 "2015-02-18T19:39:28Z")
I know that a line with two dashes truncates everything below it.
```
--
```
But it turns out that a line with a single dash immediately followed by text (no space) will also truncate everything below it. See screenshots.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [February 18, 2015, 7:41pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/2 "2015-02-18T19:41:54Z")
Well, that’s a malformed list in general.. looks like an interaction between malformed list and GitHub’s email library detecting it as a signature, maybe?
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [February 18, 2015, 10:00pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/3 "2015-02-18T22:00:25Z")
Yeah, that sounds right.
It’s a drag that the parser is so unforgiving! Why a dash with no space and a word would be interpreted as a signature is beyond me.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [February 19, 2015, 12:48am UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/4 "2015-02-19T00:48:10Z")
It’s a legit bug, perhaps @techAPJ can have a look.
---
### Author:  [@riking](https://meta.discourse.org/u/riking)
#### Post date: [February 19, 2015, 3:45am UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/5 "2015-02-19T03:45:07Z")
> [@tobiaseigen](#):
>
> Why a dash with no space and a word would be interpreted as a signature is beyond me.
```plaintext
thanks
-Bobby McSignature
```
---
### Author:  [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)
#### Post date: [February 19, 2015, 5:00am UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/6 "2015-02-19T05:00:52Z")
Hah. Smart guy. 🙂 You are right. But I never do this and if I did would want it included in my message. I was referring to the automated sig that gets skipped with the preceeding two dashes.
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [December 11, 2015, 2:32pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/7 "2015-12-11T14:32:15Z")
Fixed via:
> [@Better email reply parsing e-mail](https://meta.discourse.org/t/better-email-reply-parsing-email/36495):
>
> There are many open bugs on meta related to incorrect email reply parsing and I have been looking into them since past few days. Almost everytime the fix is to correct/modify something in GitHub’s [email\_reply\_parser](https://github.com/github/email_reply_parser) library. The GitHub’s email\_reply\_parser library is now abandoned. The last commit was over a year ago, and there are many open issues / pull requests. I propose that we include the email\_reply\_parser in core Discourse email library so that we can customize it as per our requireme…
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [December 11, 2015, 2:33pm UTC](https://meta.discourse.org/t/malformed-bullet-causes-emailed-in-topic-to-be-incorrectly-truncated/25374/8 "2015-12-11T14:33:40Z")