From: Nevin Kapur <nevin@jhu.edu>
Cc: ding@gnus.org
Subject: Re: GPG Failure from Evolution
Date: 26 Sep 2001 19:41:44 -0400 [thread overview]
Message-ID: <1001547704.2209.2.camel@bombay.dyndns.org> (raw)
In-Reply-To: <conectiva-linux.m3ofnxfsrw.fsf@godoy.laptop>
On Wed, 2001-09-26 at 19:15, Jorge Godoy wrote:
> Nevin Kapur <nevin@jhu.edu> writes:
>
> > I've noticed that when I send a PGP-signed email using Evolution, Gnus
> > can never successfully verify it.
> >
>
> I second that.
>
It seems like the reverse is true too. The message I am following up to
is verified successfully by Gnus, but Evolution complains:
This message is digitally signed but can not be proven to be
authentic.
gpg: armor header: Version: GnuPG v1.0.6 (GNU/Linux)
gpg: armor header: Comment: For info see http://www.gnupg.org
gpg: Signature made Wed 26 Sep 2001 07:15:31 PM EDT using DSA key ID
A4A30625
gpg: BAD signature from "Jorge Luiz Godoy Filho <godoy@7un.com>"
-Nevin
next prev parent reply other threads:[~2001-09-26 23:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 21:36 Nevin Kapur
2001-09-26 22:12 ` Neal H Walfield
2001-09-27 1:23 ` Jorge Godoy
2001-09-27 8:38 ` Simon Josefsson
2001-09-26 23:15 ` Jorge Godoy
2001-09-26 23:41 ` Nevin Kapur [this message]
2001-09-27 15:48 ` GPG and Mailcrypt (was: GPG Failure from Evolution) Fabien Penso
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=1001547704.2209.2.camel@bombay.dyndns.org \
--to=nevin@jhu.edu \
--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).