Bug 1624834

Summary: Quoting of plain text mail into HTML mode mangles deeper levels
Product: Red Hat Enterprise Linux 7 Reporter: Milan Crha <mcrha>
Component: evolutionAssignee: Milan Crha <mcrha>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6CC: mbarnes, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: evolution-3.28.5-3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1624835 (view as bug list) Environment:
Last Closed: 2019-08-06 12:02:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1624835, 1656436    

Description Milan Crha 2018-09-03 12:12:00 UTC 
See downstream bug:
https://gitlab.gnome.org/GNOME/evolution/issues/86

If I receive a plain text email which contains some quoted text using standard quoting methods ">" so that it looks like this:

> here is a quote

and here is a response

Then when I reply to this message with my Composer preferences set to Use HTML by default, then all the quoting disappears from the email. It's as if the person I'm replying to wrote all the text. This is true regardless of whether I reply to the entire message or just select part of the message (that contains quoted text).

If I don't have Use HTML set then the plain-text reply is properly quoted (and I can switch to HTML mode and it stays properly quoted).

For example, if I replied to the above email with "Use HTML" set I'd see this in my composer window (except in HTML of course):

> here is a quote
>
> and here is a response

Note how the original quote has only one level of quoting deep instead of two; I would expect this:

> > here is a quote
>
> and here is a response
Comment 5 errata-xmlrpc 2019-08-06 12:02:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2018