Bug 353579

Summary: The signature gets appended, even if it is already contained in the template
Product: [Applications] kmail2 Reporter: jean-pierre.hoehmann
Component: composerAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: minor    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description jean-pierre.hoehmann 2015-10-05 22:45:28 UTC 
Kmail appends the users signature to the end of the message automatically. There is also a command (%SIGNATURE), that can be used to insert the signature at an arbitrary place in a custom template (for instance directly below the mail contents, instead of after the quote of all previous messages in the conversation). However if this command is used, the signature gets inserted twice, once in the place determined by the template and then a second time at the end of the message.


Reproducible: Always

Steps to Reproduce:
1. Add a signature to kMail.
2. Use the signature in a template.
3. Open a mail that will use the template.


Actual Results:  
The signature gets inserted twice.


Expected Results:  
The signature gets inserted only in the position the user wanted it to be inserted in.


As a workaround the user can copy-paste the signature into all the templates and deactivate the signature.
Comment 1 Denis Kurz 2017-06-23 20:22:31 UTC 
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:50:19 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.