Bug 386904 - kMail 5.6.3: Signature is not replaced on identity changes after the message body text has been changed.
Summary: kMail 5.6.3: Signature is not replaced on identity changes after the message ...
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 5.6.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-14 12:58 UTC by Gunter Ohrner
Modified: 2022-11-11 07:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gunter Ohrner 2017-11-14 12:58:20 UTC
(Not talking about cryptographic signatures but traditional "--" mail signatures.)

If you open a new editor and have an auto-added signature, it's replaced properly if you select another identity.

However if you already edited some text above the signature and change the identity afterwards, the signature is left as-is and is not replaced.

This worked in earlier versions of kMail but was a regression sometime in the past (during 5.x?)
Comment 1 Justin Zobel 2022-11-10 08:52:46 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Gunter Ohrner 2022-11-10 09:33:50 UTC
Yes, this can still be confirmed - additionally, it also blocks the signature from changing if attachments were added to the message.

KMail
Version 5.21.3 (22.08.3)
KDE Frameworks 
Version 5.99.0
Qt 
Version 5.15.7 (kompiliert gegen 5.15.6)
Das Fenstersystem xcb
Comment 3 Gunter Ohrner 2022-11-11 07:35:47 UTC
(In reply to Gunter Ohrner from comment #2)
> Yes, this can still be confirmed - additionally, it also blocks the
> signature from changing if attachments were added to the message.

This latter case is especially inconvenient in case of forwarding another message as an attachment. The new forwarding message will always get the signature of the default identity, and switching to the correct / desired identity will then not update the signature.