| Summary: | changing identity breakes e-mail content | ||
|---|---|---|---|
| Product: | [Applications] kmail2 | Reporter: | Silver Salonen <silver.salonen> |
| Component: | composer | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | normal | CC: | montel |
| Priority: | NOR | ||
| Version: | 4.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Silver Salonen
2011-08-07 18:11:00 UTC
Why do you create a mail with the content of your other signature ?:) Well, one of my signatures is just "Silver" and it happens to be my default identity. When I reply to my own e-mail, it has "On whatever date Silver Salonen wrote:" at the beginning. Then I change my identity that has some more official signature and that "Silver Salonen wrote" is changed to " Salonen wrote:" and the new signature is placed twice at the top of the quoted text. BTW, this has been like this for many years, but I've taken it just as something that KMail does. It's still a bug though. Still relevant in 4.8.0. One more symptom. I have a signature "Silver" and when I start forwarding an e-mail, my name is deleted from everywhere (or most places) in the contents and these deleted instances of my name are put where the signature should be at. Cannot KMail somehow remember where did it insert the signature and replace the signature only in there, if necessary? And doing some substitution on the beginning of forwarding an e-mail (without even changing identity) is unnecessary, isn't it? This is very annoying, I can't properly answer e-mails if I have a signature with my name configured, because the e-mail contents is altered. I'd change the priority of this bug to MAJOR if I could. Still relevant in 4.9.3. Another interesting issue: 1) I have set my signature to 'Silver' 2) I have disabled signature (without deleting it first) 3) When I reply to message that has my signature "Silver" in the content many-many times (as it's back-and-forth e-mail thread), all the signatures are deleted (just "--" is left in place) (In reply to comment #7) > Another interesting issue: > 1) I have set my signature to 'Silver' > 2) I have disabled signature (without deleting it first) How ? > 3) When I reply to message that has my signature "Silver" in the content > many-many times (as it's back-and-forth e-mail thread), all the signatures > are deleted (just "--" is left in place) So what do you want ? Remove it or not ? (In reply to comment #8) > (In reply to comment #7) > > Another interesting issue: > > 1) I have set my signature to 'Silver' > > 2) I have disabled signature (without deleting it first) > > How ? By unticking "Enable signature" :) > > 3) When I reply to message that has my signature "Silver" in the content > > many-many times (as it's back-and-forth e-mail thread), all the signatures > > are deleted (just "--" is left in place) > > So what do you want ? Remove it or not ? No, of course not. I'll make it clearer. I have an e-mail like this: ---------- Hi Silver. bla-bla. -- Someone On some date you wrote: > Hi Someone > Bla-bla. > > -- > Silver ---------- When I click reply to that e-mail, composer shows: ---------- -- On some date you wrote: > Hi Silver. > > bla-bla. > > -- > Someone > > On some date you wrote: >> Hi Someone >> Bla-bla. >> >> -- >> ---------- PS. My reply-template is set to: ---------- %CURSOR -- %SIGNATURE %REM="Default reply template"%- On %ODATE %OTIMELONG you wrote: %QUOTE ---------- Ok it removes your signature even if it's disabled. OK I saw. The simplest thing would be to at least limit the replacing to only 1 occurrence. Because there is no reason to replace all the occurrences of the signature, even if the signature-to-be-replaced is found elsewhere in the document. If signature is configured to be added at the end, the replacement should start from the end. Still happens in KDE 4.10. oops I forgot to look at it. Will add to my todo-list for 4.10.2 (I hope) 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. 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. |