From a4fefc725683b25a4fa5f694e823f687dbb06db9 Mon Sep 17 00:00:00 2001 From: djcb Date: Sat, 28 Oct 2017 11:23:57 +0300 Subject: [PATCH] mu4e: make mu4e-compose-crypto-reply-plain-policy nil by default Making it sign by default is a bit too aggressive. --- mu4e/mu4e-compose.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mu4e/mu4e-compose.el b/mu4e/mu4e-compose.el index 3694a6e6..620704eb 100644 --- a/mu4e/mu4e-compose.el +++ b/mu4e/mu4e-compose.el @@ -162,7 +162,7 @@ We have the following choices: :safe 'symbolp :group 'mu4e-compose)) -(defcustom mu4e-compose-crypto-reply-plain-policy 'sign +(defcustom mu4e-compose-crypto-reply-plain-policy nil "Policy for signing/encrypting replies to messages received unencrypted. We have the following choices: @@ -550,7 +550,7 @@ buffers; lets remap its faces so it uses the ones for mu4e." (defun mu4e~compose-crypto-reply (parent compose-type) "When composing a reply to an encrypted message, we can -automatically encrypt that reply. When the message is unencrypted, +automatically encrypt that reply. When the message is unencrypted, we can decide what we want to do." (if (and (eq compose-type 'reply) (and parent (member 'encrypted (mu4e-message-field parent :flags))))