Feature #12

"Encrypt to self" functionality

Added by Antonio Ospite over 1 year ago. Updated over 1 year ago.

Status:New Start date:01/06/2012
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:- Spent time: -
Target version:-

Description

Hi,

when sending an encrypted email the sender is not able to re-read it
later by default, this is by design of asymmetric encryption of course.
Some email clients have an "Encrypt to self" option to encrypt the
outgoing message with multiple keys, one being the sender's, and this
makes the message readable again by who sent it.

Can this be done in Sylpheed already? I've looked into:

Configuration -> Common Preferences -> Privacy

and

Configuration -> Preference for current account -> Privacy

and I can't find it.

This can also be done globally by configuring gpg:
http://wlug.org.nz/MuttGPGEncryptToSelf
but I think having it in the mail client still makes sense.

What do you think about this functionality?
Does it have any drawbacks that I haven't thought of?
Where should I add the option?

Configuration -> Common Preferences -> Privacy

or

Configuration -> Preference for current account -> Privacy

and can this be done by a plugin?

I am considering implementing it myself in Sylpheed, but I wanted to
test the waters first.

Thanks,
Antonio

History

#1
Updated by Hiroyuki Yamamoto over 1 year ago

Antonio Ospite wrote:

What do you think about this functionality?
Does it have any drawbacks that I haven't thought of?

There are many requests about this feature.
I think it's OK to have that in Sylpheed.

Where should I add the option?

Configuration -> Preference for current account -> Privacy

I think it should be placed here, because encryption key can vary between accounts.

and can this be done by a plugin?

I'm not sure, but it is probably difficult.

I am considering implementing it myself in Sylpheed, but I wanted to
test the waters first.

I have thought of implementing it myself too, but if you want, go for it :)

Also available in: Atom PDF