Bug 341465

Summary:	Signature setup confusing
Product:	[Applications] kmail2	Reporter:	Martin Tlustos <martin.tlustos>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	montel
Priority:	NOR
Version:	4.14.1
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Martin Tlustos 2014-12-01 15:43:04 UTC

There are three places you can fiddle with signatures:
Identities
Settings-Composer-General
Settings-Composer-Templates

I had to work hard (and look for a long time) to find the right solution so that my cursor does not end up after the signature all the time. I suppose the settings get straightened up a bit, or get a better documentation.

Reproducible: Always

Comment 1 Laurent Montel 2014-12-02 06:15:44 UTC

Identities allows you to create signature which be add to email
=> we will not change

After indeed we can specify in two settings how we can add signature.
Fixing it I don't have idea for the moment.

Comment 2 Martin Tlustos 2014-12-02 07:33:25 UTC

You can set automatic signature both in general settings and in the templates (via inserting the %signature wildcard). When you use both, the signature is inserted two times. The %signature wildcard should only have an effect if the automatic signature setting is activated, and should only control the place the signature is put into.

Also, if used, the %signature wildcard should not override the %cursor wildcard. Right now, the cursor is placed after the %signature, even if I have the %cursor somewhere above it.

Comment 3 Denis Kurz 2017-06-23 19:59:50 UTC

This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.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 oportunity 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 4 Denis Kurz 2018-01-31 16:52:00 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.