From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/80615 Path: news.gmane.org!not-for-mail From: Adam Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus asking for key twice Date: Mon, 28 Nov 2011 23:40:18 +0100 Message-ID: <8762i36fig.fsf@earth.home> References: <87sjl8dt6t.fsf@earth.home> <878vmz7uvi.fsf@earth.home> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1322520052 15985 80.91.229.12 (28 Nov 2011 22:40:52 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 28 Nov 2011 22:40:52 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M28897@lists.math.uh.edu Mon Nov 28 23:40:48 2011 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RV9sT-0007Dm-OJ for ding-account@gmane.org; Mon, 28 Nov 2011 23:40:46 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1RV9sL-0007lQ-W9; Mon, 28 Nov 2011 16:40:38 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1RV9sK-0007lB-5k for ding@lists.math.uh.edu; Mon, 28 Nov 2011 16:40:36 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1RV9sJ-0001UF-6B for ding@lists.math.uh.edu; Mon, 28 Nov 2011 16:40:36 -0600 Original-Received: from nm3-vm3.bullet.mail.ne1.yahoo.com ([98.138.91.133]) by quimby.gnus.org with smtp (Exim 4.72) (envelope-from ) id 1RV9sH-0006DO-Bp for ding@gnus.org; Mon, 28 Nov 2011 23:40:33 +0100 Original-Received: from [98.138.90.57] by nm3.bullet.mail.ne1.yahoo.com with NNFMP; 28 Nov 2011 22:40:26 -0000 Original-Received: from [98.138.226.129] by tm10.bullet.mail.ne1.yahoo.com with NNFMP; 28 Nov 2011 22:40:26 -0000 Original-Received: from [127.0.0.1] by smtp216.mail.ne1.yahoo.com with NNFMP; 28 Nov 2011 22:40:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1322520026; bh=DkuR0cIuUNe7jJRj6EXV6Vqq1oDp8FIwtSUhgkHLXqs=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:From:To:Subject:In-Reply-To:Message-ID:References:Mail-Followup-To:Date:MIME-Version:Content-Type; b=Di6eKcX0q5Qpwebgy9HYZjBf1BSR9K+dEcpoFwf3ruvb3bXfSQqv18UeRBGPoT3bZHLGF1iL1Qm5HVnblfh05QCs7+xmqBIKjSvhwwBtLqnNUMmU7x4BNHc6k5+hWMUgVtwUbCjNOSYydlMmE/UdcATbBbKCF7TJ+gy7e30dSik= X-Yahoo-Newman-Id: 569718.43681.bm@smtp216.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: k2QuE3oVM1nU3oxCkFogh17cMI8II5qIseSPvrqk6I8Vwpl XjigD6Jbg7DM_AhUfO4PuFxtGOC3evzg461_uKk48yfbNCtC7Y9qGbN8bKG9 rjjOs8XorXEn5PvxCnb8oewX2vF9m4_pCLVNowtgnv6l2.hRjMHzcU0jRLSv gidzi2UncswiG.FZUnDh5dO8HXy2yk2MCmPOxugF1Puyji44XmOtZhOO95jD ip5XJ4Br4zLguV9cfAohrZGUtzvOajndEnU9Y1cC9BtcwujOVXxVJGvBRSfO ukwmA_GQlsQon66pwwzCQr0yMzCEP7qsSsQgUiSfuGWvKv5fZYwk5IsSfByw 0VctCC6RJt5RS2RTB7zNyEqT30XSw_n0NFc0L X-Yahoo-SMTP: Fed9kveswBC.fi0EvcUg6UnufDS8 Original-Received: from this (adam_w67@180.149.96.69 with plain) by smtp216.mail.ne1.yahoo.com with SMTP; 28 Nov 2011 14:40:24 -0800 PST In-Reply-To: <878vmz7uvi.fsf@earth.home> (Adam's message of "Mon, 28 Nov 2011 23:22:53 +0100") Mail-Followup-To: ding@gnus.org X-Spam-Score: -3.1 (---) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:80615 Archived-At: Adam writes: > Adam 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. The easiest solution is to add a new hook. It should be called in messages-send-mail right after the message has been dispatched to the server, with the current buffer being the actual message buffer that has been sent. Gnus then should add gnus-inews-do-gcc to this hook, and use the processed buffer to save. Do I sound reasonable? Whats a good name for such a new hook?