Am 2015-01-07 23:57, schrieb Kevin J. McCarthy:
Óscar Pereira wrote:
The subject seems pretty self-explanatory. Use case, you're writing
an email, which is already marked as to be sent encrypted, but you
have to postpone it. In the meantime offlineimap runs and syncs you
mailboxes, and thus your mail which is to be sent encrypted ends up
in (say) Gmail's remote folder -- UNencrypted.
Googling yielded only a question with no answer [1]. The only
work-around I have to this is to disabled sync'ing the drafts folder
altogether. Is there another way?
Sorry to resurrect an old (and somewhat heated) thread, but I'd like
some feedback on the interface for a patch I'd like to push (attached,
or see ticket #3665). The patch was based off the one submitted by
Christian Brabandt, so thank you Christian!
Your welcome. I was interested in that functionality and thought
I contribute.
The patch adds two options: postpone_encrypt (boolean) and
postpone_encrypt_as (string).
If postpone_encrypt is set, and the message has the encryption
flag set, mutt will encrypt the message using the key specified in
postpone_encrypt_as. Currently, the interface is as simple as that.
Personally, I think that is enough and I wouldn't make it more
complicated.
I'm wondering if that is sufficient for people interested in the patch,
or whether a quadoption for postpone_encrypt would be more useful. For
a quadoption, I would keep the behaviour the same: the quadoption would
only be consulted if the message encryption flag was set.
Would it be useful to be able to encrypt, even if the message
encryption
flag is not set? If so, I could use some opinions, because defining
the
interface for that starts to get complicated.
I think, if you are going the quadoption way, it should be consulted
every time and not only when the message encryption flag is set.
Best,
Christian
