From: Christoph Groth <christoph@grothesque.org>
To: info-gnus-english@gnu.org
Subject: Gnus signs email two times
Date: Thu, 23 Jan 2020 00:13:37 +0100 [thread overview]
Message-ID: <8736c7dqzi.fsf@drac> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1476 bytes --]
Hi,
I’ve been signing all my outgoing email for many years. Not sure why,
since no one ever verifies this...
Anyway, since I got an OpenPGP keycard, I noticed that Gnus actually
performs two signing operations on each outgoing message. It first
signs and sends out the message, and then it signs the copy to be saved
locally.
Are things supposed to be like this, or is this a bug... somewhere (not
necessarily in Gnus)?
Cheers
Christoph
PS
My setup looks something like this
(defun my-gnus-message-setup ()
;; Sign all messages by default with the appropriate method.
;; gnus-summary-handle-replysign ignores mml-secure-method and runs later. It
;; will overrule whatever is done here. As only gnus-message-replyencrypt is
;; t (gnus-message-replysign is nil), this will only happen if we reply to an
;; encrypted PGP message.
(make-local-variable 'mml-secure-method)
(setq mml-secure-method (if (string-match "me@work\\.com"
(message-fetch-field "from"))
"smime" "pgpmime"))
(mml-secure-message-sign))
(add-hook 'gnus-message-setup-hook 'my-gnus-message-setup)
(require 'epg-config)
(setq mml2015-encrypt-to-self t
mml2015-always-trust nil
mml2015-sign-with-sender t
mm-verify-option 'always
mm-decrypt-option 'always
epg-debug t ;; then read the *epg-debug*" buffer
mml-smime-use 'epg)
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 162 bytes --]
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next reply other threads:[~2020-01-22 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 23:13 Christoph Groth [this message]
2020-02-19 14:12 ` Lars Ingebrigtsen
2020-02-19 15:31 ` Christoph Groth
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736c7dqzi.fsf@drac \
--to=christoph@grothesque.org \
--cc=info-gnus-english@gnu.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.
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 NNTP newsgroup(s).