From: Adam <adam_w67@yahoo.com>
To: ding@gnus.org
Subject: Re: Gnus asking for key twice
Date: Mon, 28 Nov 2011 23:22:53 +0100 [thread overview]
Message-ID: <878vmz7uvi.fsf@earth.home> (raw)
In-Reply-To: <87sjl8dt6t.fsf@earth.home> (Adam's message of "Mon, 28 Nov 2011 19:02:29 +0100")
Adam <adam_w67@yahoo.com> writes:
> Whenever I send a signed mail which has a Gcc'ed header pointing to my
> archive group, I am asked to select the sign key twice - once before
> connecting to my smtp server, and once after actually sending the mail.
> mm-sign-option is set to guided. When there is no Gcc header, I am only
> asked once.
>
> Is this a bug or a feature?
I investigated. gnus-inews-do-gcc is calling
message-encode-message-body, which internally triggers the key selection
dialogue. This looks like a real design flaw to me. Gnus should encode
the message only once, and preserve the result.
next prev parent reply other threads:[~2011-11-28 22:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 18:02 Adam
2011-11-28 22:22 ` Adam [this message]
2011-11-28 22:40 ` Adam
2011-11-29 10:00 ` Katsumi Yamaoka
2011-11-29 10:19 ` Katsumi Yamaoka
2011-11-29 10:56 ` Adam
2011-11-30 11:45 ` Katsumi Yamaoka
2011-12-01 4:55 ` Katsumi Yamaoka
2011-12-01 11:17 ` Adam
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=878vmz7uvi.fsf@earth.home \
--to=adam_w67@yahoo.com \
--cc=ding@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.
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).