# Problems Parsing Emails from Seamonkey

**URL:** <https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567>\
**Category:** Feature\
**Created:** [19 september 2018 om 14:47 UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567 "2018-09-19T14:47:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jmana9](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jmana9/32/111273_2.png) [@jmana9](https://meta.discourse.org/u/jmana9)\
**Post date:** [19 september 2018 om 15:19 UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/3 "2018-09-19T15:19:50Z")

</div>

> [@LeoMcA](#):
>
> I imagine this is the same whitespace issue as caused by Thunderbird:

Yeah, I had a feeling it might be. Do you know if the whitespace problem is going to be worked on?

> [@LeoMcA](#):
>
> Inline replies are pretty hard to process, see here:

It seems so, but since so many of our users frequently reply inline, and enough of them want to continue using email that I’m starting to worry that Discourse might not be a good fit for us if this can’t be improved. Our users have come to hate Yahoo Groups, but I can hear the comments now, “well if awful Yahoo can parse my emails properly, why can’t this new thing?” I wish we could get people to change their habits, but it’s a losing battle.

I really like Discourse, but if our users that prefer email stop posting because their messages don’t come through properly, that would be a big loss for our community.

---

_[View the full topic](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567)._
