# Cannot parse email correctly: another case

**URL:** https://meta.discourse.org/t/cannot-parse-email-correctly-another-case/57085
**Category:** Support
**Created:** [February 7, 2017, 7:02pm UTC](https://meta.discourse.org/t/cannot-parse-email-correctly-another-case/57085 "2017-02-07T19:02:23Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![elijah](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elijah/32/104055_2.png) [@elijah](https://meta.discourse.org/u/elijah)
#### Post date: [February 7, 2017, 9:51pm UTC](https://meta.discourse.org/t/cannot-parse-email-correctly-another-case/57085/2 "2017-02-07T21:51:46Z")

</div>

What happens with it?

I note it has:

> [@meglio](#):
>
> Content-Transfer-Encoding: binary

on the text part. That’s legit, but obscure. `Content-Transfer-Encoding: 8bit` is more common for raw content in MIME.

Edit: This is about [NoBodyDetectedError](https://meta.discourse.org/t/incoming-emails-getting-rejected-with-nobodydetectederror/56998/5) issues, I take it.

---

_[View the full topic](https://meta.discourse.org/t/cannot-parse-email-correctly-another-case/57085)._