GNOME Bugzilla – Bug 629046
Empty reply quotation for HTML messages
Last modified: 2011-03-01 11:00:09 UTC
Created attachment 169758 [details] test email Moving this from a downstream bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=629119 Long story short: Having set in Mail Preferences, HTML Messages tab: [x] Show suppressed HTML parts as attachments [ Show plain text if present | v ] and in Composer Preferences, [ ] Format messages as HTML ... Reply style: [ Quoted | v ] then using the attached message and replying to it will create an empty body, with no quotation - body will contain only a line: On Wed, 2010-09-08 at 13:22 +0200, zyx wrote: and nothing else. This is doing it either when the message preview is on, or from a message window (double-clicking on the message itself), otherwise it does the correct thing too (with no preview pane). Unchecking "Show suppressed HTML parts as attachments" will let this work as expected with a preview pane too.
This issue is tracked as #596156 in the Debian BTS [1]. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596156
Created attachment 169832 [details] [review] evo patch for evolution; multipart/alternative is processed in a way to pick the best format evolution can show and use it. The prefer plain plugin modifies the original message in a way that for the above mentioned setup the best part, the html one, is marked as an attachment, which the formatter denied to format, because it skips attachments when formatting. So avoiding to pick the attachment part as the best part for multipart/alternative fixes the issue. It has also a little side-effect, because when having set to not showing HTML parts, and having the prefer-plain plugin set to format them as attachment, the message reply is constructed from a text/plain part, where not making HTML parts as attachment formats reply body from the HTML part. I believe this is a very nice side-effect. (It's partly fixing bug #481915 too.)
Created commit 19fb229 in evo master (2.31.92+)
*** Bug 633151 has been marked as a duplicate of this bug. ***
To confirm, this is fixed in 2.32.x. I cannot reproduce this problem with the backported patch to Evolution 2.30.3-3 in Debian Squeeze/stable or with Evolution 2.32.2 in Debian Sid/unstable.