When I reply to a message that includes any image the "reply" or "Forward" function doesn't cite the whole message. The citation stops exactly at the point where an image file was inserted in the original message: a message like: "bla bla bla bla <inserted image> bla bla bla bla greetings, blabla" gets cited as: "> bla bla bla > bla" and that's it. The serious problem is that if a message starts with a logo or background image (as many do) nothing gets cited at all. Also it seems to me that this leads to empty mails when a filter like spamassassin for example manipulates the header. These mails are marked as "non html mail" but I wonder whether this is correct (can you insert an image in a pure text mail?) Reproducible: Sometimes Steps to Reproduce: 1. receive a mail with image 2. press reply or forward 3. check the inline citation of the message with the original message Actual Results: everything behind the image is missing Expected Results: nothing should be missing, at most there should be a placeholder or marker at the image position funny thing is that just sometimes it works as expected with the same mail it hasn't worked correctly before ... I have no lue how this could be ... thx for reading, piedro
html message ? reply with html ? Could you attach a example (as mbox ) ?
i send you the mail and reply as attachment ... no, it is not a html message and my preferences is set to send as text message - I reply as plain text... p. p.s.: I had to erase all personal info, plz delete these atachments after it is fixed, thx
I send you the mail and reply as attachment ... no, it is not a html message and my preferences is set to send as text message - I reply as plain text... piedro p.s.: I had to erase all personal info, plz delete these atachments after it is fixed, thx
Created attachment 81672 [details] this is the original mail
Created attachment 81674 [details] this is the reply
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.
I switched to gnome for productive work, sry, I can not provide anymore specific information on later versions... thx anyway, p.
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.