#3665: Encrypting postponed messages
--------------------------+----------------------
Reporter: Christian | Owner: kevin8t8
Type: enhancement | Status: assigned
Priority: major | Milestone:
Component: crypto | Version:
Resolution: | Keywords:
--------------------------+----------------------
Changes (by kevin8t8):
* owner: brendan => kevin8t8
* status: new => assigned
* component: IMAP => crypto
* type: defect => enhancement
Comment:
The initial patch that Christian Brabandt posted at
<20130909203426.gd15...@256bit.org> is probably a good starting point.
mutt_prepare_template() is capable of decrypting a message and stripping a
signature, since it's also used for resending a message.
One issue with the patch is that crypt_get_keys() returns a keylist for
the *recipients* of the message. I can only assume it "worked" for him
because he has an "encrypt-to" setting in his gpg.conf.
I think we could either use the from address, or perhaps better, have a
configuration variable like $postpone_encrypt_as (keyid).
In terms of the interface, should we have a configuration variable
$postpone_encrypt (boolean|quadaoption), or just check if $msg->security
has ENCRYPT set? I'm leaning towards the configuration variable, since
the user has to set $postpone_encrypt_as anyways, they should manually
turn this on too.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3665#comment:1>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
