From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: 18718@debbugs.gnu.org
Subject: bug#18718: acknowledged by developer (control message for bug #18718)
Date: Sun, 03 Jan 2016 15:57:35 +0100 [thread overview]
Message-ID: <87k2nqogm8.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <m3bn93ghdz.fsf@gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 03 Jan 2016 10:08:08 +0100")
[-- Attachment #1: Type: text/plain, Size: 156 bytes --]
On 2016-01-03, at 10:08, Lars Magne Ingebrigtsen wrote:
> Calling from message-send sounds better, I think. Could you send a
> patch?
This should do it.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Call-mml-secure-bcc-is-safe-for-bug-18718.patch --]
[-- Type: text/x-diff, Size: 1238 bytes --]
From c1cae98181cb05a001a4b0b3216f4aa072aaed6c Mon Sep 17 00:00:00 2001
From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
Date: Sun, 3 Jan 2016 15:48:43 +0100
Subject: [PATCH] Call mml-secure-bcc-is-safe for bug#18718
* lisp/gnus/message.el (message-send): Call mml-secure-bcc-is-safe
---
lisp/gnus/message.el | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lisp/gnus/message.el b/lisp/gnus/message.el
index a6c8282..1e2e3bd 100644
--- a/lisp/gnus/message.el
+++ b/lisp/gnus/message.el
@@ -4227,6 +4227,8 @@ Instead, just auto-save the buffer and then bury it."
(if message-return-action
(apply (car message-return-action) (cdr message-return-action))))
+(autoload 'mml-secure-bcc-is-safe "mml-sec")
+
(defun message-send (&optional arg)
"Send the message in the current buffer.
If `message-interactive' is non-nil, wait for success indication or
@@ -4241,6 +4243,7 @@ It should typically alter the sending method in some way or other."
(let ((inhibit-read-only t))
(put-text-property (point-min) (point-max) 'read-only nil))
(message-fix-before-sending)
+ (mml-secure-bcc-is-safe)
(run-hooks 'message-send-hook)
(when message-confirm-send
(or (y-or-n-p "Send message? ")
--
1.9.1
next prev parent reply other threads:[~2016-01-03 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878u4fd4zr.fsf@gnus.org>
[not found] ` <86y4sitzcx.fsf@informationelle-selbstbestimmung-im-internet.de>
2015-12-26 21:34 ` bug#18718: Encrypted messages expose Bcc identities Lars Ingebrigtsen
2015-12-27 15:51 ` Jens Lechtenboerger
2015-12-27 17:59 ` Lars Ingebrigtsen
2015-12-27 18:20 ` Eli Zaretskii
2015-12-27 18:26 ` Lars Ingebrigtsen
2015-12-27 20:09 ` Jens Lechtenboerger
2015-12-27 20:13 ` Lars Ingebrigtsen
[not found] ` <handler.18718.C.145124724816035.notifdonectrl.0@debbugs.gnu.org>
2016-01-02 14:49 ` bug#18718: acknowledged by developer (control message for bug #18718) Jens Lechtenboerger
2016-01-03 9:08 ` Lars Magne Ingebrigtsen
2016-01-03 14:57 ` Jens Lechtenboerger [this message]
2016-01-04 0:57 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2nqogm8.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--cc=18718@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).