Bug 2937 - Better Signature Handling
Summary: Better Signature Handling
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.9.1
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2013-06-05 08:24 CEST by Abhay S. Kushwaha
Modified: 2013-06-09 19:05 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Abhay S. Kushwaha 2013-06-05 08:24:37 CEST
Right now signatures are physical files (or outputs of shell commands acting like physical files) that are associated with accounts in a 1:1 relationship.

While this is probably a use-case that suffices for majority of people, there are still many people (like me) who may want to use different signatures at different times for a variety of reasons.

Currently a person has to "Insert" a file as text to mimic signatures. It's a simple thing but becomes a chore over time, especially if the file selector shows up in a folder far, far away from where one has stored the signature files.

What would be ideal is that if a "signature manager" tool of some sort was available from within CM that would allow me to create different signatures and associate them to being available to all or specific (one or many) accounts configured.

Then an "Insert Signature" command in the compose window with a simple drop-down listing those signatures would make it a painless process to insert appropriate signatures.
Comment 1 Ricardo Mones 2013-06-05 08:43:31 CEST
Not sure if _currently_ doable, but seems a task to be done with the python plugin.

I'm not sure because don't really know if python plugin can add menu options to newly created compose windows (to build your “signature selector”).
Comment 2 Paul 2013-06-05 09:01:39 CEST
Also Actions can be used for that.
For example...

Menu Name: Insert signature/Sig 1
Command: echo "\n-- \nMy first sig\nnew line\n\n" >

----

Menu Name: Insert signature/Sig 2
Command: echo "\n-- \nMy second sig\nnew line\n\n" >
Comment 3 Paul 2013-06-05 09:22:05 CEST
As a third option, Templates can also be used.
Comment 4 Holger Berndt 2013-06-09 19:05:55 CEST
So you have

- account-specific signature from file
- account-specific signature from custom command output
- global compose templates
- account-specific compose templates
- folder-specific compose templates
- message templates
- actions
- the Python plugin
- insert file as text

I probably forgot something. Anyways, looks like more than enough flexibility to me.