From: "John A. Martin" <jam@jamux.com>
To: ding@gnus.org
Subject: gnus is smarter than I
Date: Fri, 14 Sep 2007 10:30:56 -0400 [thread overview]
Message-ID: <874phxz5cv.fsf@athene.jamux.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 651 bytes --]
How can I teach gnus to respect 'default-key' and 'encrypt-to' in my
~/.gnupg/gpg.conf rather than using (apparently) the newest key found
in secring.gpg for signing and the newest key on the public keyring
identified with my user id for "encrypt to self"?
If Gnus insists on being smarter than ~/.gnupg/gpg.conf how else can
it be coerced into doing what I want with respect to the choice of
keys used for signing ('default-key' in gpg talk) and encrypting to
self ('encrypt-to' in gpg talk)?
I'm using No Gnus v0.6 from the Debian package gnus-5.11+v0.5.dfsg-3
atop XEmacs 21.4 (patch 20) from the Debian xemacs21-21.4.20-2
package.
jam
[-- Attachment #2: Type: application/pgp-signature, Size: 154 bytes --]
next reply other threads:[~2007-09-14 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 14:30 John A. Martin [this message]
2007-09-15 2:06 ` Daiki Ueno
2007-09-15 18:30 ` John A. Martin
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=874phxz5cv.fsf@athene.jamux.com \
--to=jam@jamux.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).