Problems Parsing Emails from Seamonkey

AI-generated summary

A user, jmana9, reported issues with email parsing from Seamonkey, where messages appeared incorrectly indented or quoted in Discourse, despite displaying normally in HTML view. Inline replies also failed to parse properly. LeoMcA suspected the issue stemmed from whitespace handling similar to Thunderbird’s known problems, and noted inline replies are inherently difficult to process. jmana9 expressed concern that without improvements, email-reliant users might abandon the platform, especially after transitioning from Yahoo Groups. zogstrip confirmed the whitespace issue was high on the todo list and planned to address it in early October. jmana9 asked whether fixing whitespace would also improve inline reply handling. Progress was later delayed, as noted by sam, but zogstrip eventually confirmed the fix was implemented via a merged PR (#9586), resolving the Seamonkey email parsing issues.

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:


The message looks normal, with no indentation, in the HTML view:

When he tried to reply inline, things didn’t work well there either:


And here’s the HTML view:

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!

1 Like

I imagine this is the same whitespace issue as caused by Thunderbird:

Inline replies are pretty hard to process, see here:

2 Likes

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

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.

It’s high on my todo list. I’ll work on it early October.

4 Likes

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?

Has there been any progress on this?

It is still on our radar as a high priority item… work has been delayed a bit due to other urgent work.

2 Likes

Thanks for the update Sam :slight_smile:

Finally got to it :slight_smile:

This will be fixed once this PR is merged :ok_hand:

https://github.com/discourse/discourse/pull/9586

2 Likes