# Problems Parsing Emails from Seamonkey
**URL:** https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567
**Category:** Feature
**Created:** [9월 19, 2018, 2: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:** 2
### Author:  [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [9월 19, 2018, 2:55오후 UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/2 "2018-09-19T14:55:18Z")
> [@jmana9](#):
>
> When he emailed a message to my forum, the contents after the first line were indented and put into a quote block
I imagine this is the same whitespace issue as caused by Thunderbird:
> [@Inline Image post via Thunderbird not processed properly](https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961/6):
>
> I _imagine_ what’s going on here is that somewhere in the HTML → Markdown conversion some whitespace is being added (or not removed) producing something like this:
>
> ```plaintext
> ![]()
>
> ```
>
> which is rendered like so:
>
> ```plaintext
> ![]()
>
> ```
> [@jmana9](#):
>
> When he tried to reply inline, things didn’t work well there either
Inline replies are pretty hard to process, see here:
> [@Reply by email and inline replies](https://meta.discourse.org/t/reply-by-email-and-inline-replies/90686):
>
> Recently, someone replied to one of my posts on our site, simply saying: Thanks, Dave. My comments are inline But that was it. On closer inspection, I noticed that the post was a reply by email. I clicked on the little email icon and saw the rest of what they had said, sprinkled in like: Thanks, Dave. My comments are inline On Thu, Jun 21, 2018 at 2:45 PM David McClure \ wrote: \> dmcclure \ David McClure \> \