Bug 146975

Summary: comment mark ('>') inserted unsolicitedly in message body
Product: [Applications] kmail Reporter: reisenweber
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: finex, kollix
Priority: NOR Keywords: triaged
Version: 1.9.1   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description reisenweber 2007-06-19 20:21:45 UTC
Version:           1.9.1 (using KDE 3.5.1 Level "a" , SUSE 10.1)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.16.27-0.9-default

Kmail seems to insert ">" characters when receiving.

When sending a mail to myself like (body):
----- start --------
from twinklephone.com/about:
>Standards support
>  Twinkle supports the following standards (some partial).
> RFC 2327 - SDP: Session Description Protocol
> RFC 3264 - An Offer/Answer Model with the Session Description Protocol (SDP)
RFC 3264 is _not_ marked "partial", so usually you can expect twinkle to be 
fully conform to standard.

more text...
-------- end --------

then the received msg shows with an additional ">" in the first line. Like:
----- start --------
>from twinklephone.com/about:
>Standards support
>  Twinkle supports the following standards (some partial).
[...]
-------- end --------

This ">" is also visible in "message code" (V). But when others are CC:ed and are quoting my msg in their answer, it looks ok. Like:
----- start --------
[some OP's text...]
On 6/19/07, joerg <joerg.xxx@xmx.de> wrote:
>
> from twinklephone.com/about:
> >Standards support
> >  Twinkle supports the following standards (some partial).
[...]
-------- end --------

So i think this ">" is inserted while *receiving* the msg.
In the same msg the same effect (first non quote line in a quote block is quoted) occurs a second time.

WHEN I SIGN SUCH MESSAGE, THE SIGNATURE in rcvd msg IS SAID TO BE INVALID. (msg modified?)
Comment 1 Thomas McGuire 2007-06-20 19:07:24 UTC
I can confirm this (with 1.9.7).
Comment 2 FiNeX 2009-04-04 19:44:22 UTC
The bug is no more reproducible on KDE 4 (tested in current trunk r948595).
Comment 3 Martin Koller 2009-08-17 20:53:30 UTC
then let's close it.
Comment 4 reisenweber 2009-08-17 21:04:47 UTC
WORKSFORME too