# Problems Parsing Emails from Seamonkey **URL:** https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567 **Category:** Feature **Created:** [September 19, 2018, 2:47pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567 "2018-09-19T14:47:59Z") **Posts on this page:** 10 **Page:** 1
### 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: [September 19, 2018, 2:48pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/1 "2018-09-19T14:48:00Z")
I have a user who sends email through the built-in Seamonkey email client. When he emailed a message to my forum, the contents after the first line were indented and put into a quote block: ![image](https://global.discourse-cdn.com/meta/original/3X/4/8/48a5bf60874febe932d64194934c07ce417779b9.png) The message looks normal, with no indentation, in the HTML view: ![image](https://global.discourse-cdn.com/meta/original/3X/a/9/a97064528a70f80033d9c26dae21b00001c5cbe7.png) When he tried to reply inline, things didn’t work well there either: ![image](https://global.discourse-cdn.com/meta/original/3X/1/f/1f717a2617f24ebd86a0663e3964a8877e80ef16.png) And here’s the HTML view: ![image](https://global.discourse-cdn.com/meta/original/3X/5/5/5512017e84871c9964eeda15c2deb366e41564ff.png) If anyone would like to look into this, I will gladly PM the contents of the raw emails. This user is one of the most active users on our Yahoo Group who wants to continue to use email when we switch to Discourse, so I’m highly motivated to improve things for him - but I realize that probably doesn’t/shouldn’t translate to motivation on the development end! ---
### Author: ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA) #### Post date: [September 19, 2018, 2:55pm 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 \> \ ### 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: [September 19, 2018, 3:19pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/3 "2018-09-19T15:19:50Z") > [@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. ---
### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip) #### Post date: [September 19, 2018, 7:44pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/4 "2018-09-19T19:44:46Z")
> [@jmana9](#): > > Do you know if the whitespace problem is going to be worked on? It’s high on my todo list. I’ll work on it early October. ---
### 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: [September 19, 2018, 7:48pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/6 "2018-09-19T19:48:58Z")
> [@zogstrip](#): > > It’s high on my todo list. I’ll work on it early October. Awesome, thanks for the update Régis! Let me know if you need help testing anything or if you need copies of troublesome emails. Do you think improving whitespace parsing is likely to improve the handling of inline replies as well? ---
### 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: [October 30, 2018, 12:32am UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/9 "2018-10-30T00:32:00Z")
Has there been any progress on this? ---
### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam) #### Post date: [October 30, 2018, 5:15am UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/10 "2018-10-30T05:15:56Z")
It is still on our radar as a high priority item… work has been delayed a bit due to other urgent work. ---
### 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: [October 30, 2018, 11:41am UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/11 "2018-10-30T11:41:07Z")
Thanks for the update Sam 🙂 ---
### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip) #### Post date: [April 29, 2020, 3:34pm UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/12 "2020-04-29T15:34:58Z")
Finally got to it 🙂 This will be fixed once this PR is merged 👌 [https://github.com/discourse/discourse/pull/9586](https://github.com/discourse/discourse/pull/9586) ---
### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip) #### Post date: [April 30, 2020, 10:22am UTC](https://meta.discourse.org/t/problems-parsing-emails-from-seamonkey/97567/13 "2020-04-30T10:22:58Z")