Bug 289896 - Reply mail: additional body part stripped off
Summary: Reply mail: additional body part stripped off
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-27 04:20 UTC by Bernd Oliver Sünderhauf
Modified: 2017-01-07 22:46 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Document structure with additional body part (56.22 KB, image/png)
2011-12-27 04:20 UTC, Bernd Oliver Sünderhauf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Oliver Sünderhauf 2011-12-27 04:20:04 UTC
Created attachment 67144 [details]
Document structure with additional body part

Version:           4.8 (using Devel) 
OS:                Linux

I received a (Thunderbird/9.0 created) MIME mail that consisted of an additional plain text body part added after an attached PDF file, which is a signature appended by the listserver.
Replying to this mail strips off the additional body part.

Reproducible: Always

Steps to Reproduce:
Reply to such a mail

Actual Results:  
The additional body part is missing

Expected Results:  
It should have been included into the quoted text of both the HTML and the plain text version
Comment 1 Bernd Oliver Sünderhauf 2011-12-27 04:22:10 UTC
Note:
- that this happens both if replying as HTML or not.
- that Thunderbird correctly includes the additional signature part into the main body part
Comment 2 Martin Koller 2013-02-10 13:53:37 UTC
can reproduce with 4.10.0
Comment 3 Denis Kurz 2016-09-24 18:05:52 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:46:02 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.