Bug 287838 - Replies to in html does not properly quote original
Summary: Replies to in html does not properly quote original
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: Git (master)
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-29 14:06 UTC by Allen Winter
Modified: 2017-01-07 22:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Allen Winter 2011-11-29 14:06:59 UTC 
Version:           Git (master) (using Devel) 
OS:                Linux

replying to an html message does not prepend each line of the original with my quote string

Reproducible: Always

Steps to Reproduce:
make sure you have "Reply using HTML if present" configuration set
make sure your standard reply-to-sender template has a %QUOTE
reply to sender on an html message




Actual Results:  
the original message in the reply composer, but there are no prepended quote strings

if I change then to plaintext composing.. still no prepended quote strings

Expected Results:  
the original message should have each line prepended with my quote string
Comment 1 Allen Winter 2011-11-29 15:37:02 UTC 
Actually, most of the time things work as expected.

I do have one sample message I could give out privately if you want an example of where this happens
Comment 2 karaluh 2012-03-06 15:00:59 UTC 
I can confirm this behavior.
Comment 3 Denis Kurz 2016-09-24 18:14:47 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:22:14 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.