From: Raymond Scholz <ray-2003@zonix.de>
Subject: Re: gpg signature problem
Date: Sun, 07 Dec 2003 23:04:15 +0100 [thread overview]
Message-ID: <geg.874qwc709s@hush.zonix.de> (raw)
In-Reply-To: <x74qwf26jt.fsf@capsicum.wsrcc.com>
· Wolfgang S. Rupprecht wrote:
> User-Agent: Gnus/5.10e+00 (Gnus v5.10.2) Emacs/21.3 (berkeley-unix)
Your Gnus version looks weird :)
> I can get gnus to verify some signatures (such as the signed cert
> postings) but it fails on others. Here is a recent message-id
> (2003/12/4) that fails for me:
>
> <cone.1070591734.311541.28205.501@ny.email-scan.com>
>
> Does this verify for other folks?
Yes, with recent CVS versions of Emacs and Gnus.
Cheers, Ray
--
It's a bit like shooting sparrows with a cannon (what's the English/US
idiom for this?) - Using Emacs to edit text files.
(Kai Großjohann and Per Abrahamsen on (ding))
next parent reply other threads:[~2003-12-07 22:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x74qwf26jt.fsf@capsicum.wsrcc.com>
2003-12-07 22:04 ` Raymond Scholz [this message]
[not found] ` <x7d6b0p8nq.fsf@capsicum.wsrcc.com>
2003-12-08 1:01 ` Jesper Harder
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=geg.874qwc709s@hush.zonix.de \
--to=ray-2003@zonix.de \
--cc=rscholz@zonix.de \
/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).