From: Ivan Boldyrev <boldyrev+nospam@cgitftp.uiggm.nsc.ru>
Subject: Re: Automatically find right GPG record when signing/encrypting mail?
Date: Mon, 28 Jun 2004 12:11:31 +0700 [thread overview]
Message-ID: <ftl4r1xa8m.ln2@ibhome.cgitftp.uiggm.nsc.ru> (raw)
In-Reply-To: <86smch6ysu.fsf@rumba.de.uu.net>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On 8788 day of my life Kai Grossjohann wrote:
> I send mail to user foo, but my GPG keyring gives address bar for
> this person. I know that I can specify the recipient in the mml tag,
> but is there an automatic way?
>
> (There is perhaps a way to do it with GPG; that would be fine, as
> well. I don't want to use the email address given in the key, as it
> is old and will stop to work sooner or later.)
Add line to your ~/.gnupg/gpg.conf:
group recipient@host = 0xKEYID
--
Ivan Boldyrev
XML -- new language of ML family.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
parent reply other threads:[~2004-06-28 5:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86smch6ysu.fsf@rumba.de.uu.net>]
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=ftl4r1xa8m.ln2@ibhome.cgitftp.uiggm.nsc.ru \
--to=boldyrev+nospam@cgitftp.uiggm.nsc.ru \
/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).