Previous Replies separator is not RFC-compliant

Contribute Bug

AI-generated summary

rriemann reported an issue with Discourse’s email replies not being RFC-compliant due to an incorrect separator. KMail, a mail application, expects -- (two dashes followed by a space) as the separator, but Discourse uses --- (three dashes) instead. This issue has been raised before in previous discussions. zogstrip downplayed the importance, noting that most people use HTML views, but rriemann provided relevant references, including an RFC document and a Discourse code snippet.

1

Continuing the discussion from Imdb embeds broken on other sites:

I just received two mails with practically the same content (that’s weird) due to a response linked above and noticed:

My mail application KMail doesn’t strip off the signature when I reply. The issue seems to be the separator.

KMail claims that RFC compliant is -- (dash dash space on a single line).

I think I found the source: https://www.ietf.org/rfc/rfc3676.txt (4.3)

However, Discourse uses “—” (triple dash without space) as a separator.

This issue has been raised before:

5개의 좋아요
E-Mail Signature not correct stripped out
2

I guess it doesn’t really matter since most people (except geeks) use HTML views :pizza:

https://github.com/discourse/discourse/commit/86819f08c3294313b9b414f3c38644e4a60284c8

4개의 좋아요